draft-ietf-fecframe-framework-09.txt   draft-ietf-fecframe-framework-10.txt 
FEC Framework Working Group M. Watson FEC Framework Working Group M. Watson
Internet-Draft Qualcomm, Inc. Internet-Draft Netflix, Inc.
Intended status: Standards Track July 6, 2010 Intended status: Standards Track September 7, 2010
Expires: January 7, 2011 Expires: March 11, 2011
Forward Error Correction (FEC) Framework Forward Error Correction (FEC) Framework
draft-ietf-fecframe-framework-09 draft-ietf-fecframe-framework-10
Abstract Abstract
This document describes a framework for using forward error This document describes a framework for using forward error
correction (FEC) codes with applications in public and private IP correction (FEC) codes with applications in public and private IP
networks to provide protection against packet loss. The framework networks to provide protection against packet loss. The framework
supports applying Forward Error Correction to arbitrary packet flows supports applying Forward Error Correction to arbitrary packet flows
over unreliable transport and is primarily intended for real-time, or over unreliable transport and is primarily intended for real-time, or
streaming, media. This framework can be used to define Content streaming, media. This framework can be used to define Content
Delivery Protocols that provide Forward Error Correction for Delivery Protocols that provide Forward Error Correction for
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2011. This Internet-Draft will expire on March 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 26, line 7 skipping to change at page 26, line 7
instance of the FEC Framework. Other packets MUST NOT be sent within instance of the FEC Framework. Other packets MUST NOT be sent within
this flow i.e. all packets in the FEC repair flow MUST be FEC repair this flow i.e. all packets in the FEC repair flow MUST be FEC repair
packets as defined in Section 5.4 and MUST relate to the same FEC packets as defined in Section 5.4 and MUST relate to the same FEC
Framework instance. Framework instance.
In the case that RTP is used for repair packets, the identification In the case that RTP is used for repair packets, the identification
of the repair packet flow MAY also include the RTP Payload Type to be of the repair packet flow MAY also include the RTP Payload Type to be
used for repair packets. used for repair packets.
FEC Scheme-specific information elements MAY be encoded into a text FEC Scheme-specific information elements MAY be encoded into a text
string for transport within Content Delivery Protocols as according string for transport within Content Delivery Protocols. See Section
to the following ABNF [RFC5234]: 4.5 of [I-D.ietf-fecframe-sdp-elements] for the ABNF [RFC5234]
syntax.
scheme-specific-info = [ element *( ',' element ) ]
element = name ':' value
name = token
token = 1*<any CHAR except CTLs or separators>
value = *<any CHAR except CTLs or separators>
separators = "(" | ")" | "<" | ">" | "@"
| "," | ";" | ":" | "\" | <">
| "/" | "[" | "]" | "?" | "="
| "{" | "}" | SP | HT
5.6. FEC Scheme requirements 5.6. FEC Scheme requirements
In order to be used with this framework, an FEC Scheme MUST be In order to be used with this framework, an FEC Scheme MUST be
capable of processing data arranged into blocks of Application Data capable of processing data arranged into blocks of Application Data
Units (source blocks). Units (source blocks).
A specification for a new FEC scheme MUST include the following A specification for a new FEC scheme MUST include the following
things: things:
skipping to change at page 36, line 52 skipping to change at page 36, line 52
Reports (XRs)", RFC 5725, February 2010. Reports (XRs)", RFC 5725, February 2010.
[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hakenberg, "RTP Retransmission Payload Format", RFC 4588, Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
July 2006. July 2006.
[RFC2736] Handley, M. and C. Perkins, "Guidelines for Writers of RTP [RFC2736] Handley, M. and C. Perkins, "Guidelines for Writers of RTP
Payload Format Specifications", BCP 36, RFC 2736, Payload Format Specifications", BCP 36, RFC 2736,
December 1999. December 1999.
[I-D.ietf-fecframe-sdp-elements]
Begen, A., "Session Description Protocol (SDP) Elements
for FEC Framework", draft-ietf-fecframe-sdp-elements-08
(work in progress), August 2010.
[MBMSTS] 3GPP, "Multimedia Broadcast/Multicast Service (MBMS); [MBMSTS] 3GPP, "Multimedia Broadcast/Multicast Service (MBMS);
Protocols and codecs", 3GPP TS 26.346, April 2005. Protocols and codecs", 3GPP TS 26.346, April 2005.
Author's Address Author's Address
Mark Watson Mark Watson
Qualcomm, Inc. Netflix, Inc.
3165 Kifer Road 100 Winchester Circle
Santa Clara, CA 95051 Los Gatos, CA, CA 95032
U.S.A. U.S.A.
Email: watson@qualcomm.com Email: watsonm@netflix.com
 End of changes. 7 change blocks. 
20 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/