Forward Error Correction Grouping Semantics in Session Description Protocol (Obsoleted)

Network Working Group                                              A. Li
Request for Comments: 4756                                    Hyervision
Category: Standards Track                                  November 2006


              <span class="h1">Forward Error Correction Grouping Semantics</span>
                    <span class="h1">in Session Description Protocol</span>

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2006).

Abstract

   This document defines the semantics that allow for grouping of
   Forward Error Correction (FEC) streams with the protected payload
   streams in Session Description Protocol (SDP).  The semantics defined
   in this document are to be used with "Grouping of Media Lines in the
   Session Description Protocol" (<a href="./rfc3388">RFC 3388</a>) to group together "m" lines
   in the same session.

Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a>
   <a href="#section-3">3</a>. Forward Error Correction (FEC) ..................................<a href="#page-2">2</a>
   <a href="#section-4">4</a>. FEC Grouping ....................................................<a href="#page-3">3</a>
      <a href="#section-4.1">4.1</a>. FEC Group ..................................................<a href="#page-3">3</a>
      <a href="#section-4.2">4.2</a>. Offer / Answer Consideration ...............................<a href="#page-3">3</a>
      <a href="#section-4.3">4.3</a>. Example of FEC Grouping ....................................<a href="#page-3">3</a>
   <a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-4">4</a>
   <a href="#section-6">6</a>. IANA Considerations .............................................<a href="#page-4">4</a>
   <a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-5">5</a>
   <a href="#section-8">8</a>. References ......................................................<a href="#page-5">5</a>
      <a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-5">5</a>
      <a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-5">5</a>







<span class="grey">Li                          Standards Track                     [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc4756">RFC 4756</a>             FEC Grouping Semantics in SDP         November 2006</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The media lines in an SDP [<a href="#ref-3" title=""SDP: Session Description Protocol"">3</a>] session may be associated with each
   other in various ways.  SDP itself does not provide methods to convey
   the relationships between the media lines.  Such relationships are
   indicated by the extension to SDP as defined in "Grouping of Media
   Lines in the Session Description Protocol" (<a href="./rfc3388">RFC 3388</a>) [<a href="#ref-2" title=""Grouping of Media Lines in the Session Description Protocol (SDP)"">2</a>].  <a href="./rfc3388">RFC 3388</a>
   defines two types of semantics: Lip Synchronization and Flow
   Identification.

   Forward Error Correction (FEC) is a common technique to achieve
   robust communication in error-prone environments.  In this document,
   we define the semantics that allows for grouping of FEC streams with
   the protected payload streams in SDP by further extending <a href="./rfc3388">RFC 3388</a>.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Terminology</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD, "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title=""Key words for use in RFCs to Indicate Requirement Levels"">1</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Forward Error Correction (FEC)</span>

   Forward Error Correction (FEC) is a common technique to achieve
   robust communication in error-prone environments.  In FEC,
   communication uses a bandwidth that is more than payload to send
   redundantly coded payload information.  The receivers can readily
   recover the original payload even when some communication is lost in
   the transmission.  Compared to other error correction techniques
   (such as retransmission), FEC can achieve much lower transmission
   delay, and it does not have the problem of implosion from
   retransmission requests in various multicast scenarios.

   In general, the FEC data can be sent in two different ways: (1)
   multiplexed together with the original payload stream or (2) as a
   separate stream.  It is thus necessary to define mechanisms to
   indicate the association relationship between the FEC data and the
   payload data they protect.

   When FEC data are multiplexed with the original payload stream, the
   association relationship may, for example, be indicated as specified
   in "An RTP Payload for Redundant Audio Data" (<a href="./rfc2198">RFC 2198</a>) [<a href="#ref-4" title=""RTP Payload for Redundant Audio Data"">4</a>].  The
   generic RTP payload format for FEC [<a href="#ref-5" title=""An RFC Payload Format for Generic FEC"">5</a>] uses that method.

   When FEC data are sent as a separate stream from the payload data,
   the association relationship can be indicated in various ways.  This
   document on the FEC media line grouping specifies a mechanism for
   indicating such relationships.



<span class="grey">Li                          Standards Track                     [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc4756">RFC 4756</a>             FEC Grouping Semantics in SDP         November 2006</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  FEC Grouping</span>

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  FEC Group</span>

   Each "a=group" line is used to indicate an association relationship
   between the FEC streams and the payload streams.  The streams
   included in one "a=group" line are called a "FEC Group".

   Each FEC group MAY have one or more than one FEC stream, and one or
   more than one payload stream.  For example, it is possible to have
   one payload stream protected by more than one FEC stream , or
   multiple payload streams sharing one FEC stream.

   Grouping streams in a FEC group only indicates the association
   relationship between streams.  The detailed FEC protection
   scheme/parameters are conveyed through the mechanism of the
   particular FEC algorithm used.  For example, the FEC grouping is used
   for generic RTP payload for FEC [<a href="#ref-5" title=""An RFC Payload Format for Generic FEC"">5</a>] to indicate the association
   relationship between the FEC stream and the payload stream.  The
   detailed protection level and length information for the Unequal Loss
   Protection (ULP) algorithm is communicated in band within the FEC
   stream.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Offer / Answer Consideration</span>

   The backward compatibility in offer / answer is generally handled as
   specified in <a href="./rfc3388">RFC 3388</a> [<a href="#ref-2" title=""Grouping of Media Lines in the Session Description Protocol (SDP)"">2</a>].

   Depending on the implementation, a node that does not understand FEC
   grouping (either does not understand line grouping at all, or just
   does not understand the FEC semantics) SHOULD respond to an offer
   containing FEC grouping either (1) with an answer that ignores the
   grouping attribute or (2) with a refusal to the request (e.g., 488
   Not acceptable here or 606 Not acceptable in SIP).

   In the first case, the original sender of the offer MUST establish
   the connection without FEC.  In the second case, if the sender of the
   offer still wishes to establish the session, it SHOULD re-try the
   request with an offer without FEC.

<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>.  Example of FEC Grouping</span>

   The following example shows a session description of a multicast
   conference.  The first media stream (mid:1) contains the audio
   stream.  The second media stream (mid:2) contains the Generic FEC [<a href="#ref-5" title=""An RFC Payload Format for Generic FEC"">5</a>]
   protection for the audio stream.  These two streams form an FEC
   group.  The relationship between the two streams is indicated by the
   "a=group:FEC 1 2" line.  The FEC stream is sent to the same multicast



<span class="grey">Li                          Standards Track                     [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc4756">RFC 4756</a>             FEC Grouping Semantics in SDP         November 2006</span>


   group and has the same Time to Live (TTL) as the audio, but on a port
   number two higher.  Likewise, the video stream (mid:3) and its
   Generic FEC protection stream (mid:4) form another FEC group.  The
   relationship between the two streams is indicated by the "a=group:FEC
   3 4" line.  The FEC stream is sent to a different multicast address,
   but has the same port number (30004) as the payload video stream.

       v=0
       o=adam 289083124 289083124 IN IP4 host.example.com
       s=ULP FEC Seminar
       t=0 0
       c=IN IP4 224.2.17.12/127
       a=group:FEC 1 2
       a=group:FEC 3 4
       m=audio 30000 RTP/AVP 0
       a=mid:1
       m=audio 30002 RTP/AVP 100
       a=rtpmap:100 ulpfec/8000
       a=mid:2
       m=video 30004 RTP/AVP 31
       a=mid:3
       m=video 30004 RTP/AVP 101
       c=IN IP4 224.2.17.13/127
       a=rtpmap:101 ulpfec/8000
       a=mid:4

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   There is a weak threat for the receiver that the FEC grouping can be
   modified to indicate FEC relationships that do not exist.  Such
   attacks may result in failure of FEC to protect, and/or mishandling
   of other media payload streams.  It is recommended that the receiver
   SHOULD do integrity check on SDP and follow the security
   considerations of SDP [<a href="#ref-3" title=""SDP: Session Description Protocol"">3</a>] to only trust SDP from trusted sources.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  IANA Considerations</span>

   This document defines the semantics to be used with grouping of media
   lines in SDP as defined in <a href="./rfc3388">RFC 3388</a>.  The semantics defined in this
   document are to be registered by the IANA when they are published in
   standards track RFCs.

   The following semantics have been registered by IANA in Semantics for
   the "group" SDP Attribute under SDP Parameters.

   Semantics                  Token   Reference
   ------------------------   -----   ----------
   Forward Error Correction   FEC     <a href="./rfc4756">RFC 4756</a>



<span class="grey">Li                          Standards Track                     [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc4756">RFC 4756</a>             FEC Grouping Semantics in SDP         November 2006</span>



<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgments</span>

   The author would like to thank Magnus Westerlund, Colin Perkins,
   Joerg Ott, and Cullen Jennings for their feedback on this document.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  References</span>

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Normative References</span>

   [<a id="ref-1">1</a>]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-2">2</a>]  Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne,
        "Grouping of Media Lines in the Session Description Protocol
        (SDP)", <a href="./rfc3388">RFC 3388</a>, December 2002.

   [<a id="ref-3">3</a>]  Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
        Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006.

<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Informative References</span>

   [<a id="ref-4">4</a>]  Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., Handley, M.,
        Bolot, J., Vega-Garcia, A., and S. Fosse-Parisis, "RTP Payload
        for Redundant Audio Data", <a href="./rfc2198">RFC 2198</a>, September 1997.

   [<a id="ref-5">5</a>]  Li, A., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22An+RFC+Payload+Format+for+Generic+FEC%22'>"An RFC Payload Format for Generic FEC"</a>, Work in
        Progress.

Author's Address

   Adam H. Li
   HyerVision
   10194 Wateridge Circle #152
   San Diego, CA 92121
   U.S.A.

   Tel:    +1 858 622 9038
   EMail:  [email protected]












<span class="grey">Li                          Standards Track                     [Page 5]</span>

<span id="page-6" ></span>
<span class="grey"><a href="./rfc4756">RFC 4756</a>             FEC Grouping Semantics in SDP         November 2006</span>


Full Copyright Statement

   Copyright (C) The IETF Trust (2006).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST,
   AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
   EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
   THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
   IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
   PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   [email protected].

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.






Li                          Standards Track                     [Page 6]