draft-ietf-fecframe-config-signaling-07.txt   draft-ietf-fecframe-config-signaling-08.txt 
FECFRAME Working Group Rajiv Asati FECFRAME Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Informational Intended status: Informational
Expires: July 2012 Expires: July 2012
February 21, 2012 February 25, 2012
Methods to convey FEC Framework Configuration Information Methods to convey FEC Framework Configuration Information
draft-ietf-fecframe-config-signaling-07.txt draft-ietf-fecframe-config-signaling-08.txt
Abstract Abstract
FEC Framework document [RFC6363] defines the FEC Framework FEC Framework document [RFC6363] defines the FEC Framework
Configuration Information necessary for the FEC framework operation. Configuration Information necessary for the FEC framework operation.
This document describes using existing signaling protocols such as This document describes how to use signaling protocols such as
Session Announcement Protocol (SAP), Session Initiation Protocol Session Announcement Protocol (SAP), Session Initiation Protocol
(SIP), Real Time Stream Protocol (RTSP) etc. to determine and (SIP), Real Time Stream Protocol (RTSP) etc. for determining and
dynamically communicate the Configuration information between communicating the Configuration information between sender(s) and
sender(s) and receiver(s). receiver(s).
This document doesn't define any new signaling protocol.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. This document may contain the provisions of BCP 78 and BCP 79. This document may contain
material from IETF Documents or IETF Contributions published or made material from IETF Documents or IETF Contributions published or made
publicly available before November 10, 2008. The person(s) publicly available before November 10, 2008. The person(s)
controlling the copyright in some of this material may not have controlling the copyright in some of this material may not have
granted the IETF Trust the right to allow modifications of such granted the IETF Trust the right to allow modifications of such
material outside the IETF Standards Process. Without obtaining an material outside the IETF Standards Process. Without obtaining an
skipping to change at page 2, line 13 skipping to change at page 2, line 13
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on July 21, 2012. This Internet-Draft will expire on August 25, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Specification Language.........................................3 2. Specification Language.........................................4
3. Terminology/Abbreviations......................................4 3. Terminology/Abbreviations......................................4
4. FEC Framework Configuration Information........................4 4. FEC Framework Configuration Information........................5
4.1. Encoding Format...........................................6 4.1. Encoding Format...........................................6
5. Signaling Protocol Usage.......................................6 5. Signaling Protocol Usage.......................................7
5.1. Signaling Protocol for Multicasting.......................7 5.1. Signaling Protocol for Multicasting.......................8
5.1.1. Sender Procedure.....................................9 5.1.1. Sender Procedure.....................................9
5.1.2. Receiver Procedure..................................12 5.1.2. Receiver Procedure..................................12
5.2. Signaling Protocol for Unicasting........................13 5.2. Signaling Protocol for Unicasting........................13
5.2.1. SIP.................................................13 5.2.1. SIP.................................................13
5.2.2. RTSP................................................14 5.2.2. RTSP................................................14
6. Security Considerations.......................................15 6. Security Considerations.......................................15
7. IANA Considerations...........................................15 7. IANA Considerations...........................................15
8. Acknowledgments...............................................15 8. Acknowledgments...............................................15
9. References....................................................16 9. References....................................................16
9.1. Normative References.....................................16 9.1. Normative References.....................................16
skipping to change at page 3, line 26 skipping to change at page 3, line 26
This document describes how various signaling protocols such as This document describes how various signaling protocols such as
Session Announcement Protocol (SAP)[RFC2974], Session Initiation Session Announcement Protocol (SAP)[RFC2974], Session Initiation
Protocol (SIP)[RFC3261], Real Time Stream Protocol (RTSP)[RFC2326] Protocol (SIP)[RFC3261], Real Time Stream Protocol (RTSP)[RFC2326]
etc. could be used by the FEC scheme (and/or Content Delivery etc. could be used by the FEC scheme (and/or Content Delivery
Protocol (CDP))to communicate the Configuration information between Protocol (CDP))to communicate the Configuration information between
sender and receiver(s). The configuration information may be encoded sender and receiver(s). The configuration information may be encoded
in any compatible format such as SDP [RFC4566], XML etc., though in any compatible format such as SDP [RFC4566], XML etc., though
this document references to SDP encoding usage quite extensively. this document references to SDP encoding usage quite extensively.
Note that this document doesn't define any new signaling protocol;
rather it just provides examples of how existing protocols should
be used. Also, the list of signaling protocols for unicast is not
intended to be a complete list.
This document doesn't describe any FEC scheme specific information This document doesn't describe any FEC scheme specific information
(FSSI) (for example, how source blocks are constructed) or any (FSSI) (for example, how source blocks are constructed) or any
sender or receiver side operation for a particular FEC scheme (for sender or receiver side operation for a particular FEC scheme (for
example, whether the receiver makes use of one or more repair flows example, whether the receiver makes use of one or more repair flows
that are received). Such FEC scheme specifics should be covered in that are received). Such FEC scheme specifics should be covered in
separate document(s). This document doesn't mandate a particular separate document(s). This document doesn't mandate a particular
encoding format for the configuration information either. encoding format for the configuration information either.
This document is structured such that Section 2 describes the terms This document is structured such that Section 2 describes the terms
used in this document, section 4 describes the FEC Framework used in this document, section 4 describes the FEC Framework
 End of changes. 10 change blocks. 
12 lines changed or deleted 19 lines changed or added

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