idnits 2.17.1 draft-ietf-mmusic-proto-iana-registration-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 8, 2016) is 3023 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4566 (Obsoleted by RFC 8866) ** Obsolete normative reference: RFC 4572 (Obsoleted by RFC 8122) ** Obsolete normative reference: RFC 5245 (Obsoleted by RFC 8445, RFC 8839) -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MMUSIC S. Nandakumar 3 Internet-Draft Cisco Systems Inc 4 Intended status: Standards Track January 8, 2016 5 Expires: July 11, 2016 7 IANA registrations of SDP 'proto' attribute for transporting RTP Media 8 over TCP under various RTP profiles. 9 draft-ietf-mmusic-proto-iana-registration-04 11 Abstract 13 Real-time Transport Protocol (RTP) provides end-to-end network 14 transport functions suitable for applications transmitting real-time 15 data such as audio, video or simulation data, over multicast or 16 unicast network services. The data transport is augmented by RTP 17 Control Protocol (RTCP), to allow monitoring of the data delivery in 18 a manner scalable to large multicast networks, and to provide minimal 19 control and identification functionality. 21 The RTP specification establishes a registry of profile names for use 22 by higher-level control protocols, such as the Session Description 23 Protocol (SDP), to refer to the transport methods. This 24 specification describes the following new SDP transport protocol 25 identifiers for transporting RTP Media over TCP: 'TCP/RTP/AVPF', 26 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/ 27 SAVPF', 'TCP/TLS/RTP/AVP', 'TCP/TLS/RTP/AVPF'. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on July 11, 2016. 46 Copyright Notice 48 Copyright (c) 2016 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 3. Protocol Identifiers . . . . . . . . . . . . . . . . . . . . 3 66 3.1. TCP/RTP/AVPF Transport Realization . . . . . . . . . . . 4 67 3.2. TCP/RTP/SAVP Transport Realization . . . . . . . . . . . 4 68 3.3. TCP/RTP/SAVPF Transport Realization . . . . . . . . . . . 4 69 3.4. TCP/DTLS/RTP/SAVP Transport Realization . . . . . . . . . 4 70 3.5. TCP/DTLS/RTP/SAVPF Transport Realization . . . . . . . . 4 71 3.6. TCP/TLS/RTP/AVP Transport Realization . . . . . . . . . . 4 72 3.7. TCP/TLS/RTP/AVPF Transport Realization . . . . . . . . . 5 73 4. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 5 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 76 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 77 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 78 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 79 8.2. Informative References . . . . . . . . . . . . . . . . . 7 80 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 82 1. Overview 84 SDP [RFC4566] provides a general-purpose format for describing 85 multimedia sessions in announcements or invitations. [RFC4145] 86 specifies a general mechanism for describing media transport over 87 Transmission Control Protocol (TCP) using SDP with [RFC4571] defining 88 a method for framing RTP and RTCP packets [RFC3550] onto a 89 connection-oriented transport (such as TCP). [RFC4572] extends 90 [RFC4145] for describing TCP-based media streams that are protected 91 using Transport Layer Security (TLS) [RFC5246]. 93 This specification describes the following new SDP transport protocol 94 identifiers for transporting RTP Media over TCP: 96 TCP/RTP/AVPF: to describe RTP Media with RTCP-based Feedback 97 [RFC4585] over TCP, as defined in Section 3.1. 99 TCP/RTP/SAVP: to describe Secure RTP (SRTP) Media [RFC3711] over TCP, 100 as defined in Section 3.2. 102 TCP/RTP/SAVPF: to describe Secure RTP Media with RTCP-based Feedback 103 [RFC5124] over TCP, as defined in Section 3.3. 105 TCP/DTLS/RTP/SAVP: to describe Secure RTP Media [RFC3711] using 106 Datagram Transport Layer Security (DTLS) SRTP [RFC5764] (DTLS-SRTP) 107 over TCP, as defined in Section 3.4. 109 TCP/DTLS/RTP/SAVPF: to describe Secure RTP Media with RTCP-based 110 Feedback [RFC5124] using DTLS-SRTP over TCP, as defined in 111 Section 3.5. 113 TCP/TLS/RTP/AVP: to describe RTP Media on top of TLS over TCP, as 114 defined in Section 3.6. 116 TCP/TLS/RTP/AVPF: to describe RTP Media with RTCP-based Feedback 117 [RFC5124] on top of TLS over TCP, as defined in Section 3.7. 119 2. Terminology 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 3. Protocol Identifiers 127 The 'm=' line in SDP specifies, among other items, the transport 128 protocol to be used for the media in the session. See the "Media 129 Descriptions" section of SDP [RFC4566] for a discussion on transport 130 protocol identifiers. 132 The following is the format for an 'm=' line, as specified in 133 [RFC4566]: 135 m= ... 137 3.1. TCP/RTP/AVPF Transport Realization 139 The TCP/RTP/AVPF is realized as described below: 141 o RTP/AVPF stream over the TCP transport is realized using the 142 framing method defined in [RFC4571]. 144 3.2. TCP/RTP/SAVP Transport Realization 146 The TCP/RTP/SAVP is realized as described below: 148 o RTP/SAVP stream over the TCP transport is realized using the 149 framing method defined in [RFC4571]. 151 3.3. TCP/RTP/SAVPF Transport Realization 153 The TCP/RTP/SAVPF is realized as described below: 155 o RTP/SAVPF stream over the TCP transport is realized using the 156 framing method defined in [RFC4571]. 158 3.4. TCP/DTLS/RTP/SAVP Transport Realization 160 The TCP/DTLS/RTP/SAVP is realized as described below: 162 o RTP/SAVP using DTLS-based key establishment is realized according 163 to the procedures defined in [RFC5764]; and 165 o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP. 167 3.5. TCP/DTLS/RTP/SAVPF Transport Realization 169 The TCP/DTLS/RTP/SAVPF is realized as described below: 171 o RTP/SAVPF using DTLS-based key establishment is realized according 172 to the procedures defined in [RFC5764]; and 174 o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP. 176 3.6. TCP/TLS/RTP/AVP Transport Realization 178 The TCP/TLS/RTP/AVP is realized as described below: 180 o RTP/AVP packets are framed using the procedures from [RFC4571]; 181 and 183 o [RFC4571] framed RTP/AVP packets are transported as Application 184 data messages over the TLS association setup using the procedures 185 from [RFC4572]. 187 3.7. TCP/TLS/RTP/AVPF Transport Realization 189 The TCP/TLS/RTP/AVPF is realized as described below: 191 o RTP/AVPF packets are framed using the procedures from [RFC4571]; 192 and 194 o [RFC4571] framed RTP/AVPF packets are transported as Application 195 data messages over the TLS association setup using the procedures 196 from [RFC4572]. 198 4. ICE Considerations 200 When procedures from [RFC6544] are used to setup Interactive 201 Connectivity Establishment (ICE) [RFC5245] candidates for a TCP 202 transport, the framing mechanism from [RFC4571] MUST be used for 203 framing Session Traversal Utilities for NAT (STUN) packets (for keep- 204 alives, consent checks), as defined in section 3 of [RFC6544]. 206 5. IANA Considerations 208 This specification describes the following new SDP transport protocol 209 identifiers :'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 210 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', 211 'TCP/TLS/RTP/AVPF', as defined in the Section 3. These proto values 212 should be registered by the IANA under the "proto" subregistry in the 213 "Session Description Protocol (SDP) Parameters" registry. 215 [To RFC Editor: Remove this note prior to publication. This 216 registration should take place at the following location: 217 http://www.iana.org/assignments/sdp-parameters/sdp- 218 parameters.xhtml#sdp-parameters-2. Replace XXXX in the table below 219 with the assigned number of this RFC] 220 +--------+---------------------+-----------+ 221 | Type | SDP Name | Reference | 222 +--------+---------------------+-----------+ 223 | proto | TCP/RTP/AVPF | RFCXXXX | 224 | | | | 225 | proto | TCP/RTP/SAVP | RFCXXXX | 226 | | | | 227 | proto | TCP/RTP/SAVPF | RFCXXXX | 228 | | | | 229 | proto | TCP/DTLS/RTP/SAVP | RFCXXXX | 230 | | | | 231 | proto | TCP/DTLS/RTP/SAVPF | RFCXXXX | 232 | | | | 233 | proto | TCP/TLS/RTP/AVP | RFCXXXX | 234 | | | | 235 | proto | TCP/TLS/RTP/AVPF | RFCXXXX | 236 +--------+---------------------+-----------+ 238 6. Security Considerations 240 The new "proto" identifiers registered by this document in the SDP 241 parameters registry maintained by IANA is primarily for use by the 242 offer/answer model of the Session Description Protocol [RFC3264] for 243 the negotiation and establishment of RTP based Media over the TCP 244 transport. These additional SDP "proto" identifiers does not 245 introduce any security considerations beyond those detailed in 246 Section 7 of [RFC4566]. 248 7. Acknowledgements 250 Author would like to thank Cullen Jennings, Alissa Cooper, Justin 251 Uberti, Mo Zanaty, Christer Holmberg, Jonathan Lennox, Flemming 252 Andreason, Roni Even and Bo Burman for their reviews and suggested 253 improvements. 255 8. References 257 8.1. Normative References 259 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 260 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 261 RFC2119, March 1997, 262 . 264 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 265 Description Protocol", RFC 4566, DOI 10.17487/RFC4566, 266 July 2006, . 268 [RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP) 269 and RTP Control Protocol (RTCP) Packets over Connection- 270 Oriented Transport", RFC 4571, DOI 10.17487/RFC4571, July 271 2006, . 273 [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the 274 Transport Layer Security (TLS) Protocol in the Session 275 Description Protocol (SDP)", RFC 4572, DOI 10.17487/ 276 RFC4572, July 2006, 277 . 279 [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment 280 (ICE): A Protocol for Network Address Translator (NAT) 281 Traversal for Offer/Answer Protocols", RFC 5245, DOI 282 10.17487/RFC5245, April 2010, 283 . 285 [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer 286 Security (DTLS) Extension to Establish Keys for the Secure 287 Real-time Transport Protocol (SRTP)", RFC 5764, DOI 288 10.17487/RFC5764, May 2010, 289 . 291 [RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach, 292 "TCP Candidates with Interactive Connectivity 293 Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544, 294 March 2012, . 296 8.2. Informative References 298 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 299 with Session Description Protocol (SDP)", RFC 3264, DOI 300 10.17487/RFC3264, June 2002, 301 . 303 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 304 Jacobson, "RTP: A Transport Protocol for Real-Time 305 Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, 306 July 2003, . 308 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 309 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 310 RFC 3711, DOI 10.17487/RFC3711, March 2004, 311 . 313 [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in 314 the Session Description Protocol (SDP)", RFC 4145, DOI 315 10.17487/RFC4145, September 2005, 316 . 318 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 319 "Extended RTP Profile for Real-time Transport Control 320 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI 321 10.17487/RFC4585, July 2006, 322 . 324 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 325 Real-time Transport Control Protocol (RTCP)-Based Feedback 326 (RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February 327 2008, . 329 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 330 (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/ 331 RFC5246, August 2008, 332 . 334 Author's Address 336 Suhas Nandakumar 337 Cisco Systems Inc 338 707 Tasman Drive 339 San Jose, CA 95134 340 USA 342 Email: snandaku@cisco.com