draft-ietf-fecframe-config-signaling-03.txt   draft-ietf-fecframe-config-signaling-04.txt 
FECFRAME Working Group Rajiv Asati FECFRAME Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Standards Track Intended status: Experimental
Expires: July 2010 Expires: July 2011
June 23, 2010 January 11, 2011
Methods to convey FEC Framework Configuration Information Methods to convey FEC Framework Configuration Information
draft-ietf-fecframe-config-signaling-03.txt draft-ietf-fecframe-config-signaling-04.txt
Abstract
FEC Framework document [FECARCH] defines the FEC Framework
Configuration Information necessary for the FEC framework operation.
This document describes how to use existing signaling protocols to
determine and dynamically communicate the Configuration information
between sender(s) and receiver(s).
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. the provisions of BCP 78 and BCP 79. 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.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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."
skipping to change at page 1, line 26 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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 23, 2010. This Internet-Draft will expire on July 11, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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.
Abstract
FEC Framework document [FECARCH] defines the FEC Framework
Configuration Information necessary for the FEC framework operation.
This document describes how to use existing signaling protocols to
determine and dynamically communicate the Configuration information
between sender(s) and receiver(s).
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Specification Language.........................................3 2. Specification Language.........................................3
3. Terminology/Abbreviations......................................4 3. Terminology/Abbreviations......................................4
4. FEC Framework Configuration Information........................4 4. FEC Framework Configuration Information........................4
4.1. Encoding Format...........................................5 4.1. Encoding Format...........................................6
5. Signaling Protocol Usage.......................................6 5. Signaling Protocol Usage.......................................6
5.1. Signaling Protocol for Multicasting.......................7 5.1. Signaling Protocol for Multicasting.......................7
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. RSTP................................................14 5.2.2. RSTP................................................14
6. Security Considerations.......................................15 6. Security Considerations.......................................15
7. IANA Considerations...........................................15 7. IANA Considerations...........................................15
8. Acknowledgments...............................................15 8. Acknowledgments...............................................15
skipping to change at page 6, line 27 skipping to change at page 6, line 35
octets that can be embedded within the payload of the signaling octets that can be embedded within the payload of the signaling
protocol message(s). The length of the encoding format MUST either protocol message(s). The length of the encoding format MUST either
be fixed, or derived by examining the encoded octets themselves. be fixed, or derived by examining the encoded octets themselves.
For example, the initial octets may include some kind of length For example, the initial octets may include some kind of length
indication. indication.
Independent of what all encoding formats supported by an FEC scheme, Independent of what all encoding formats supported by an FEC scheme,
each instance of the FEC Framework MUST use a single encoding format each instance of the FEC Framework MUST use a single encoding format
to describe all of the configuration information associated with to describe all of the configuration information associated with
that instance. The signaling protocol specified in this document that instance. The signaling protocol specified in this document
SHOULD not validate the encoded information, though it may validate SHOULD NOT validate the encoded information, though it may validate
the syntax or length of the encoded information. the syntax or length of the encoded information.
The reader may refer to the SDP elements document [FECSDP], which The reader may refer to the SDP elements document [FECSDP], which
describes the usage of 'SDP' encoding format as an example encoding describes the usage of 'SDP' encoding format as an example encoding
format for FEC Framework Configuration Information. format for FEC Framework Configuration Information.
5. Signaling Protocol Usage 5. Signaling Protocol Usage
FEC Framework [FECARCH] requires certain FEC Framework Configuration FEC Framework [FECARCH] requires certain FEC Framework Configuration
Information to be available to both sender and receiver(s). This Information to be available to both sender and receiver(s). This
skipping to change at page 11, line 11 skipping to change at page 11, line 11
IP address as the 'originating source' address to identify the FEC IP address as the 'originating source' address to identify the FEC
streams (i.e., source or repair flows). Please refer to IANA streams (i.e., source or repair flows). Please refer to IANA
assignments for multicast addresses. assignments for multicast addresses.
The sender MUST periodically send the 'SAP announcement' message to The sender MUST periodically send the 'SAP announcement' message to
ensure that the receiver doesn't purge the cached entry(s) from the ensure that the receiver doesn't purge the cached entry(s) from the
database and doesn't trigger the deletion of FEC Framework database and doesn't trigger the deletion of FEC Framework
Configuration Information. Configuration Information.
Please note that the deletion of FEC Framework Configuration Please note that the deletion of FEC Framework Configuration
Information SHOULD not mean that the receiver stops its FEC Information SHOULD NOT mean that the receiver stops its FEC
processing for the instance for which it had already got the processing for the instance for which it had already got the
configuration information. configuration information.
While the time interval between repetitions of an announcement can While the time interval between repetitions of an announcement can
be calculated as per the very sophisticated but complex method be calculated as per the very sophisticated but complex method
explained in [RFC2974], the preferred and simpler method recommended explained in [RFC2974], the preferred and simpler method recommended
by this specification is to let the user specify the time interval by this specification is to let the user specify the time interval
from the range of 1-200 seconds with suggested default being 60 from the range of 1-200 seconds with suggested default being 60
seconds. The time interval MUST be chosen to ensure that SAP seconds. The time interval MUST be chosen to ensure that SAP
announcement messages are sent out before the corresponding announcement messages are sent out before the corresponding
skipping to change at page 16, line 13 skipping to change at page 16, line 13
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[FECARCH] Watson, M., "Forward Error Correction (FEC) Framework", [FECARCH] Watson, M., "Forward Error Correction (FEC) Framework",
draft-ietf-fecframe-framework-05 (work in progress), Jan draft-ietf-fecframe-framework-10 (work in progress), May
2010. 2011.
[FECSDP] Begen, A., "SDP Elements for FEC Framework", draft-ietf- [FECSDP] Begen, A., "SDP Elements for FEC Framework", draft-ietf-
fecframe-sdp-elements-04 (work in progress), Feb 2010. fecframe-sdp-elements-11 (work in progress), April 2011.
[RFC2974] Handley, M., Perkins, C. and E. Whelan, "Session [RFC2974] Handley, M., Perkins, C. and E. Whelan, "Session
Announcement Protocol", RFC 2974, October 2000. Announcement Protocol", RFC 2974, October 2000.
9.2. Informative References 9.2. Informative References
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
skipping to change at page 16, line 47 skipping to change at page 16, line 47
[RFC4601] Fenner, etc., "Protocol Independent Multicast - Sparse [RFC4601] Fenner, etc., "Protocol Independent Multicast - Sparse
Mode (PIM-SM): Protocol Specification", RFC 4601, August Mode (PIM-SM): Protocol Specification", RFC 4601, August
2006. 2006.
[RFC3547] Baugher, etc., "The Group Domain of Interpretation", RFC [RFC3547] Baugher, etc., "The Group Domain of Interpretation", RFC
3547, July 2003. 3547, July 2003.
[SAP-REQ] Asaeda, etc., "Requirements for IP Multicast Session [SAP-REQ] Asaeda, etc., "Requirements for IP Multicast Session
Announcement in the Internet, draft-ietf-mboned-session- Announcement in the Internet, draft-ietf-mboned-session-
announcement-req-02, April 2010. announcement-req-03, September 2010.
Author's Addresses Author's Addresses
Rajiv Asati Rajiv Asati
Cisco Systems, Cisco Systems,
7025-6 Kit Creek Rd, RTP, NC, 27709-4987 7025-6 Kit Creek Rd, RTP, NC, 27709-4987
Email: rajiva@cisco.com Email: rajiva@cisco.com
 End of changes. 14 change blocks. 
23 lines changed or deleted 33 lines changed or added

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