idnits 2.17.00 (12 Aug 2021) /tmp/idnits51257/draft-ietf-mmusic-proto-iana-registration-06.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 (February 29, 2016) is 2266 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 February 29, 2016 5 Expires: September 1, 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-06 11 Abstract 13 The Real-time Transport Protocol (RTP) specification establishes a 14 registry of profile names for use by higher-level control protocols, 15 such as the Session Description Protocol (SDP), to refer to the 16 transport methods. This specification describes the following new 17 SDP transport protocol identifiers for transporting RTP Media over 18 TCP: 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 'TCP/DTLS/RTP/ 19 SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', 'TCP/TLS/RTP/AVPF'. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 1, 2016. 38 Copyright Notice 40 Copyright (c) 2016 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Protocol Identifiers . . . . . . . . . . . . . . . . . . . . 3 58 3.1. TCP/RTP/AVPF Transport Realization . . . . . . . . . . . 3 59 3.2. TCP/RTP/SAVP Transport Realization . . . . . . . . . . . 3 60 3.3. TCP/RTP/SAVPF Transport Realization . . . . . . . . . . . 3 61 3.4. TCP/DTLS/RTP/SAVP Transport Realization . . . . . . . . . 4 62 3.5. TCP/DTLS/RTP/SAVPF Transport Realization . . . . . . . . 4 63 3.6. TCP/TLS/RTP/AVP Transport Realization . . . . . . . . . . 4 64 3.7. TCP/TLS/RTP/AVPF Transport Realization . . . . . . . . . 4 65 4. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 5 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 68 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 69 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 71 8.2. Informative References . . . . . . . . . . . . . . . . . 7 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Overview 76 Real-time Transport Protocol (RTP) provides end-to-end network 77 transport functions suitable for applications transmitting real-time 78 data such as audio, video over multicast or unicast network services. 79 The data transport is augmented by RTP Control Protocol (RTCP), to 80 allow monitoring of the data delivery in a manner scalable to large 81 multicast networks, and to provide minimal control and identification 82 functionality. 84 Session Description Protocol (SDP) [RFC4566], provides a general- 85 purpose format for describing multimedia sessions in announcements or 86 invitations. TCP-Based Media Transport in the SDP [RFC4145], 87 specifies a general mechanism for describing media transport over 88 Transmission Control Protocol (TCP) using SDP with [RFC4571] defining 89 a method for framing RTP and RTCP packets [RFC3550] onto a 90 connection-oriented transport (such as TCP). Connection-Oriented 91 Media Transport over the Transport Layer Security (TLS) Protocol in 92 the SDP [RFC4572], extends [RFC4145] for describing TCP-based media 93 streams that are protected using Transport Layer Security (TLS) 94 [RFC5246]. 96 This specification describes additional SDP transport protocol 97 identifiers for transporting RTP Media over TCP as defined in 98 Section 3. 100 2. Terminology 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 3. Protocol Identifiers 108 The 'm=' line in SDP specifies, among other items, the transport 109 protocol (identified via the 'proto' field) to be used for the media 110 in the session. See the "MediaDescriptions" section of SDP [RFC4566] 111 for a discussion on transport protocol identifiers. 113 The following is the format for an 'm=' line, as specified in 114 [RFC4566]: 116 m= ... 118 3.1. TCP/RTP/AVPF Transport Realization 120 The TCP/RTP/AVPF transport describes RTP Media with RTCP-based 121 Feedback [RFC4585] over TCP. 123 It is realized as described below: 125 o RTP/AVPF stream over the TCP transport is realized using the 126 framing method defined in [RFC4571]. 128 3.2. TCP/RTP/SAVP Transport Realization 130 The TCP/RTP/SAVP transport describes Secure RTP (SRTP) Media 131 [RFC3711] over TCP. 133 It is realized as described below: 135 o RTP/SAVP stream over the TCP transport is realized using the 136 framing method defined in [RFC4571]. 138 3.3. TCP/RTP/SAVPF Transport Realization 140 The TCP/RTP/SAVPF transport describes Secure RTP Media with RTCP- 141 based Feedback [RFC5124] over TCP. 143 It is realized as described below: 145 o RTP/SAVPF stream over the TCP transport is realized using the 146 framing method defined in [RFC4571]. 148 3.4. TCP/DTLS/RTP/SAVP Transport Realization 150 The TCP/DTLS/RTP/SAVP transport describes Secure RTP Media [RFC3711] 151 using Datagram Transport Layer Security (DTLS) SRTP (DTLS-SRTP) 152 [RFC5764] over TCP. 154 It is realized as described below: 156 o RTP/SAVP using DTLS-based key establishment is realized according 157 to the procedures defined in [RFC5764]; and 159 o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP. 161 3.5. TCP/DTLS/RTP/SAVPF Transport Realization 163 The TCP/DTLS/RTP/SAVPF transport describes Secure RTP Media with 164 RTCP-based Feedback [RFC5124] using DTLS-SRTP over TCP. 166 It is realized as described below: 168 o RTP/SAVPF using DTLS-based key establishment is realized according 169 to the procedures defined in [RFC5764]; and 171 o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP. 173 3.6. TCP/TLS/RTP/AVP Transport Realization 175 The TCP/TLS/RTP/AVP transport describes RTP Media on top of TLS over 176 TCP. 178 It 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 transport describes RTP Media with RTCP-based 190 Feedback [RFC5124] on top of TLS over TCP. 192 It is realized as described below: 194 o RTP/AVPF packets are framed using the procedures from [RFC4571]; 195 and 197 o [RFC4571] framed RTP/AVPF packets are transported as Application 198 data messages over the TLS association setup using the procedures 199 from [RFC4572]. 201 4. ICE Considerations 203 When procedures from [RFC6544] are used to setup Interactive 204 Connectivity Establishment (ICE) [RFC5245] candidates for a TCP 205 transport, the framing mechanism from [RFC4571] MUST be used for 206 framing Session Traversal Utilities for NAT (STUN) packets (for keep- 207 alives, consent checks), as defined in section 3 of [RFC6544]. 209 5. IANA Considerations 211 This specification describes the following new SDP transport protocol 212 identifiers :'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 213 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', 214 'TCP/TLS/RTP/AVPF', as defined in Section 3. These proto values 215 should be registered by the IANA under the "proto" subregistry in the 216 "Session Description Protocol (SDP) Parameters" registry. 218 [To RFC Editor: Remove this note prior to publication. This 219 registration should take place at the following location: 220 http://www.iana.org/assignments/sdp-parameters/sdp- 221 parameters.xhtml#sdp-parameters-2. Replace XXXX in the table below 222 with the assigned number of this RFC] 224 +--------+---------------------+-----------+ 225 | Type | SDP Name | Reference | 226 +--------+---------------------+-----------+ 227 | proto | TCP/RTP/AVPF | RFCXXXX | 228 | | | | 229 | proto | TCP/RTP/SAVP | RFCXXXX | 230 | | | | 231 | proto | TCP/RTP/SAVPF | RFCXXXX | 232 | | | | 233 | proto | TCP/DTLS/RTP/SAVP | RFCXXXX | 234 | | | | 235 | proto | TCP/DTLS/RTP/SAVPF | RFCXXXX | 236 | | | | 237 | proto | TCP/TLS/RTP/AVP | RFCXXXX | 238 | | | | 239 | proto | TCP/TLS/RTP/AVPF | RFCXXXX | 240 +--------+---------------------+-----------+ 242 6. Security Considerations 244 The new "proto" identifiers registered by this document in the SDP 245 parameters registry maintained by IANA is primarily for use by the 246 offer/answer model of the Session Description Protocol [RFC3264] for 247 the negotiation and establishment of RTP based Media over the TCP 248 transport. This specification doesn't introduce any additional 249 security considerations beyond those specified by the individual 250 transport protocols identified in the "proto" identifiers and those 251 detailed in Section 7 of [RFC4566]. 253 7. Acknowledgements 255 Author would like to thank Cullen Jennings, Alissa Cooper, Justin 256 Uberti, Mo Zanaty, Christer Holmberg, Jonathan Lennox, Flemming 257 Andreason, Roni Even Ben Campbell and Bo Burman for their reviews and 258 suggested improvements. 260 Author would also like to thank Adam Montville for SECDIR review, 261 Meral Shirazipour for Gen-Art review and Sarah Banks for the OPS-Dir 262 review. 264 8. References 266 8.1. Normative References 268 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 269 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 270 RFC2119, March 1997, 271 . 273 [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session 274 Description Protocol", RFC 4566, DOI 10.17487/RFC4566, 275 July 2006, . 277 [RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP) 278 and RTP Control Protocol (RTCP) Packets over Connection- 279 Oriented Transport", RFC 4571, DOI 10.17487/RFC4571, July 280 2006, . 282 [RFC4572] Lennox, J., "Connection-Oriented Media Transport over the 283 Transport Layer Security (TLS) Protocol in the Session 284 Description Protocol (SDP)", RFC 4572, DOI 10.17487/ 285 RFC4572, July 2006, 286 . 288 [RFC5245] Rosenberg, J., "Interactive Connectivity Establishment 289 (ICE): A Protocol for Network Address Translator (NAT) 290 Traversal for Offer/Answer Protocols", RFC 5245, DOI 291 10.17487/RFC5245, April 2010, 292 . 294 [RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer 295 Security (DTLS) Extension to Establish Keys for the Secure 296 Real-time Transport Protocol (SRTP)", RFC 5764, DOI 297 10.17487/RFC5764, May 2010, 298 . 300 [RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach, 301 "TCP Candidates with Interactive Connectivity 302 Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544, 303 March 2012, . 305 8.2. Informative References 307 [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model 308 with Session Description Protocol (SDP)", RFC 3264, DOI 309 10.17487/RFC3264, June 2002, 310 . 312 [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. 313 Jacobson, "RTP: A Transport Protocol for Real-Time 314 Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, 315 July 2003, . 317 [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. 318 Norrman, "The Secure Real-time Transport Protocol (SRTP)", 319 RFC 3711, DOI 10.17487/RFC3711, March 2004, 320 . 322 [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in 323 the Session Description Protocol (SDP)", RFC 4145, DOI 324 10.17487/RFC4145, September 2005, 325 . 327 [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, 328 "Extended RTP Profile for Real-time Transport Control 329 Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI 330 10.17487/RFC4585, July 2006, 331 . 333 [RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for 334 Real-time Transport Control Protocol (RTCP)-Based Feedback 335 (RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February 336 2008, . 338 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 339 (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/ 340 RFC5246, August 2008, 341 . 343 Author's Address 345 Suhas Nandakumar 346 Cisco Systems Inc 347 707 Tasman Drive 348 San Jose, CA 95134 349 USA 351 Email: snandaku@cisco.com