Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source Flows in FEC Framework
draft-ietf-fecframe-pseudo-cdp-03

The information below is for an old version of the document
Document Type Active Internet-Draft (fecframe WG)
Last updated 2012-05-17
Replaces draft-kozat-fecframe-pseudo-cdp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists (IESG: Dead)
Telechat date
Responsible AD Martin Stiemerling
Send notices to fecframe-chairs@tools.ietf.org, draft-ietf-fecframe-pseudo-cdp@tools.ietf.org
FEC Framework                                                   U. Kozat
Internet-Draft                                           DoCoMo USA Labs
Intended status:  Standards Track                               A. Begen
Expires:  November 18, 2012                                        Cisco
                                                            May 17, 2012

 Pseudo Content Delivery Protocol (CDP) for Protecting Multiple Source
                         Flows in FEC Framework
                   draft-ietf-fecframe-pseudo-cdp-03

Abstract

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

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 18, 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

Kozat & Begen           Expires November 18, 2012               [Page 1]
Internet-Draft    Pseudo CDP for Multiple Source Flows          May 2012

   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.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 10
   8.  Normative References . . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Kozat & Begen           Expires November 18, 2012               [Page 2]
Internet-Draft    Pseudo CDP for Multiple Source Flows          May 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
   [I-D.ietf-fecframe-config-signaling]) on the other hand provides the
Show full document text