40 likes | 199 Vues
This document summarizes the key points discussed during the IETF 77 meeting held from March 21-26, 2010, in Anaheim, California, concerning the FEC Framework (FECFrame) drafts. Mark Watson led the discussions, focusing on addressing comments from Vincent and Orly, improving terminology, defining syntax for FEC scheme configurations, and aligning updates for RaptorQ specifications. The document also emphasizes the importance of scheme-specific configuration elements and outlines the structured approach to defining payload IDs. The drafts aim to prepare for Working Group Last Call (WGLC) after incorporating all feedback.
E N D
IETF77, March 21-26 2010, Anaheim, CA, USAFECFRAMEdraft-ietf-fecframe-framework-07draft-ietf-fecframe-raptor-02draft-ietf-fecframe-rtp-raptor-03 Mark Watson
draft-ietf-fecframe-framework-07 • Address comments from Vincent and Orly • Improve terminology (e.g. “ADU”) • Define text syntax for FEC Scheme-specific configuration elements • E.g. “a:5,t:64” • Implies additional requirement on FEC Schemes to define names, types and text encodings for individual FEC Scheme-specific configuration elements • Update various references • Complete WGLC now ?
draft-ieft-fecframe-raptor-02 • Add FEC Schemes for RaptorQ • Address comments from Vincent • Define individual scheme-specific configuration elements as per new framework (“Kmax”, “T”, “P”) • Define two formats for FEC Source and Repair Payload IDs (Format A and Format B) to accommodate RaptorQ • Ready for WGLC ?
draft-ietf-fecframe-rtp-raptor-03 • Address comments from Vincent and Colin • Align with fecframe-raptor updates for RaptorQ • Add and define rate parameter • Better explain definition-by-reference of payload contents • Add text on SDP mapping, offer-answer and declarative SDP considerations • Explain absence of specific security requirements • Ready for WGLC ? Needs review in AVT