draft-ietf-fecframe-config-signaling-05.txt   draft-ietf-fecframe-config-signaling-06.txt 
FECFRAME Working Group Rajiv Asati FECFRAME Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Proposed Standard Intended status: Experimental
Expires: July 2011 Expires: July 2011
May 30, 2011 September 24, 2011
Methods to convey FEC Framework Configuration Information Methods to convey FEC Framework Configuration Information
draft-ietf-fecframe-config-signaling-05.txt draft-ietf-fecframe-config-signaling-06
Abstract Abstract
FEC Framework document [FECARCH] defines the FEC Framework FEC Framework document [FECARCH] defines the FEC Framework
Configuration Information necessary for the FEC framework operation. Configuration Information necessary for the FEC framework operation.
This document describes how to use existing signaling protocols to This document describes how to use existing signaling protocols to
determine and dynamically communicate the Configuration information determine and dynamically communicate the Configuration information
between sender(s) and receiver(s). between sender(s) and receiver(s).
Status of this Memo Status of this Memo
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 30, 2011. This Internet-Draft will expire on March 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
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...........................................6 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. 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
9.2. Informative References...................................16 9.2. Informative References...................................16
Author's Addresses...............................................17 Author's Addresses...............................................17
1. Introduction 1. Introduction
skipping to change at page 14, line 24 skipping to change at page 14, line 24
5.2.2. RTSP 5.2.2. RTSP
Real-Time Streaming Protocol (RTSP) [RFC2326] is an application- Real-Time Streaming Protocol (RTSP) [RFC2326] is an application-
level signaling protocol for control over the delivery of data with level signaling protocol for control over the delivery of data with
real-time properties. RTSP provides an extensible framework to real-time properties. RTSP provides an extensible framework to
enable controlled, on-demand delivery of real-time data, such as enable controlled, on-demand delivery of real-time data, such as
audio and video. RTSP runs on either TCP or UDP transports. audio and video. RTSP runs on either TCP or UDP transports.
RTSP already provides an ability to extend the existing method with RTSP already provides an ability to extend the existing method with
new parameters. This specification defines 'FEC Protection Required' new parameters. This specification defines 'FEC Protection Needed'
option-tag (please see section 6 for IANA Considerations) and option-tag (please see section 7 for IANA Considerations) and
prescribes including it in the Require (or Proxy-Require) header of prescribes including it in the Require (or Proxy-Require) header of
SETUP (method) request message, so as to request for FEC protection SETUP (method) request message, so as to request for FEC protection
for the data. for the data.
The node receiving such request either responds with "200 OK" The node receiving such request either responds with "200 OK"
message that includes offers i.e., available FEC options (e.g. FEC message that includes offers i.e., available FEC options (e.g. FEC
Framework Configuration Information for each Instance) or "551 Framework Configuration Information for each Instance) or "551
Option not supported" message. A sample of related message exchange Option not supported" message. A sample of related message exchange
is shown below - is shown below -
Node1->Node2: SETUP < ... > RTSP/1.0 Node1->Node2: SETUP < ... > RTSP/1.0
CSeq: 1 CSeq: 1
Transport: <omitted for simplicity> Transport: <omitted for simplicity>
Require: FECprotectionRequired Require: FEC-protection-needed
Node2->Node1: RTSP/1.0 200 OK Node2->Node1: RTSP/1.0 200 OK
CSeq: 1 CSeq: 1
Transport: <omitted for simplicity> Transport: <omitted for simplicity>
The requesting node (Node1) may then send a new SETUP message to The requesting node (Node1) may then send a new SETUP message to
convey the selected FEC protection to Node2, and proceed with convey the selected FEC protection to Node2, and proceed with
regular RTSP messaging. regular RTSP messaging.
Suffice to say, if the requesting node (Node1) received '551 Option Suffice to say, if the requesting node (Node1) received '551 Option
skipping to change at page 15, line 24 skipping to change at page 15, line 24
This document recommends SAP message(s) be authenticated to ensure This document recommends SAP message(s) be authenticated to ensure
sender authentication, as described in section 5. sender authentication, as described in section 5.
There is no additional security consideration other than what's There is no additional security consideration other than what's
already covered in [RFC2974] for SAP, [RFC2326] for RTSP, and already covered in [RFC2974] for SAP, [RFC2326] for RTSP, and
[RFC3261] for SIP. [RFC3261] for SIP.
7. IANA Considerations 7. IANA Considerations
This document requests IANA to register a new option-tag for FEC This document requests IANA to register a new RTSP Option tag
protection required, as described in section 5.2.2 earlier, and (option-tag) listed below in the RTSP/1.0 Option Tags table of the
provides the following information in compliance with section 3.8.1 "Real Time Streaming Protocol (RTSP)/1.0 Parameters" registry
in [RFC2326]: available from http://www.iana.org/, and provides the following
information in compliance with section 3.8.1 in [RFC2326]:
. Name of option = FECprotectionRequired . Name of option-tag = FEC-protection-needed
. Description = See section 5.2.2
. Change of Control = IETF . Change of Control = IETF
8. Acknowledgments 8. Acknowledgments
Thanks to Colin Perkins for pointing out the issue with the time- Thanks to Colin Perkins for pointing out the issue with the time-
interval for the SAP messages. Additionally, thanks to Vincent Roca, interval for the SAP messages. Additionally, thanks to Vincent Roca,
Ali Begen, Mark Watson and Ulas Kozat for greatly improving this Ali Begen, Mark Watson, Ulas Kozat and David Harrington for greatly
document. improving this document.
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-10 (work in progress), May draft-ietf-fecframe-framework-15 (work in progress), Sep
2011. 2011.
[FECSDP] Begen, A., "SDP Elements for FEC Framework", draft-ietf- [FECSDP] Begen, A., "SDP Elements for FEC Framework", draft-ietf-
fecframe-sdp-elements-11 (work in progress), April 2011. 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
 End of changes. 11 change blocks. 
16 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/