Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in the Forward Error Correction (FEC) Framework
RFC 6801

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 02
• 03
• 04
• 05

Internet Engineering Task Force (IETF)                          U. Kozat
Request for Comments: 6801                            DOCOMO Innovations
Category: Informational                                         A. Begen
ISSN: 2070-1721                                                    Cisco
                                                           November 2012

               Pseudo Content Delivery Protocol (CDP) for
                Protecting Multiple Source Flows in the
                Forward Error Correction (FEC) Framework

Abstract

   This document provides a pseudo Content Delivery Protocol (CDP) to
   protect multiple source flows with one or more repair flows based on
   the Forward Error Correction (FEC) Framework and the Session
   Description Protocol (SDP) elements defined for the framework.  The
   purpose of the document is not to provide a full-fledged protocol but
   to show how the defined framework and SDP elements can be combined
   together to implement a CDP.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6801.

Kozat & Begen                 Informational                     [Page 1]
RFC 6801          Pseudo CDP for Multiple Source Flows     November 2012

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1. Introduction ....................................................3
   2. Definitions/Abbreviations .......................................3
   3. Construction of a Repair Flow from Multiple Source Flows ........3
      3.1. Example: Two Source Flows Protected by a Single
           Repair Flow ................................................6
   4. Reconstruction of Source Flows from Repair Flow(s) ..............9
      4.1. Example: Multiple Source Flows Protected by a
           Single Repair Flow .........................................9
   5. Security Considerations ........................................10
   6. Acknowledgments ................................................10
   7. Normative References ...........................................11

Kozat & Begen                 Informational                     [Page 2]
RFC 6801          Pseudo CDP for Multiple Source Flows     November 2012

1.  Introduction

   The Forward Error Correction (FEC) Framework (described in [RFC6363])
   and SDP Elements for FEC Framework (described in [RFC6364]) together
   define mechanisms sufficient enough to build an actual Content
   Delivery Protocol (CDP) with FEC protection.  Methods to convey FEC
   Framework Configuration Information (described in [RFC6695]), on the
   other hand, provide the signaling protocols that may be used as part
   of CDP to communicate FEC-Scheme-Specific Information from FEC sender
   to a single as well as multiple FEC receivers.  This document
   provides a guideline on how the mechanisms defined in [RFC6363] and
   [RFC6364] can be sufficiently used to design a CDP over a non-trivial
   scenario, namely, protection of multiple source flows with one or