Internet DRAFT - draft-ietf-mmusic-proto-iana-registration
draft-ietf-mmusic-proto-iana-registration
MMUSIC S. Nandakumar
Internet-Draft Cisco Systems Inc
Intended status: Standards Track February 29, 2016
Expires: September 1, 2016
IANA registrations of SDP 'proto' attribute for transporting RTP Media
over TCP under various RTP profiles.
draft-ietf-mmusic-proto-iana-registration-06
Abstract
The Real-time Transport Protocol (RTP) specification establishes a
registry of profile names for use by higher-level control protocols,
such as the Session Description Protocol (SDP), to refer to the
transport methods. This specification describes the following new
SDP transport protocol identifiers for transporting RTP Media over
TCP: 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 'TCP/DTLS/RTP/
SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', 'TCP/TLS/RTP/AVPF'.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 1, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Nandakumar Expires September 1, 2016 [Page 1]
Internet-Draft SDP Proto Registrations February 2016
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Identifiers . . . . . . . . . . . . . . . . . . . . 3
3.1. TCP/RTP/AVPF Transport Realization . . . . . . . . . . . 3
3.2. TCP/RTP/SAVP Transport Realization . . . . . . . . . . . 3
3.3. TCP/RTP/SAVPF Transport Realization . . . . . . . . . . . 3
3.4. TCP/DTLS/RTP/SAVP Transport Realization . . . . . . . . . 4
3.5. TCP/DTLS/RTP/SAVPF Transport Realization . . . . . . . . 4
3.6. TCP/TLS/RTP/AVP Transport Realization . . . . . . . . . . 4
3.7. TCP/TLS/RTP/AVPF Transport Realization . . . . . . . . . 4
4. ICE Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Overview
Real-time Transport Protocol (RTP) provides end-to-end network
transport functions suitable for applications transmitting real-time
data such as audio, video over multicast or unicast network services.
The data transport is augmented by RTP Control Protocol (RTCP), to
allow monitoring of the data delivery in a manner scalable to large
multicast networks, and to provide minimal control and identification
functionality.
Session Description Protocol (SDP) [RFC4566], provides a general-
purpose format for describing multimedia sessions in announcements or
invitations. TCP-Based Media Transport in the SDP [RFC4145],
specifies a general mechanism for describing media transport over
Transmission Control Protocol (TCP) using SDP with [RFC4571] defining
a method for framing RTP and RTCP packets [RFC3550] onto a
connection-oriented transport (such as TCP). Connection-Oriented
Media Transport over the Transport Layer Security (TLS) Protocol in
the SDP [RFC4572], extends [RFC4145] for describing TCP-based media
streams that are protected using Transport Layer Security (TLS)
[RFC5246].
Nandakumar Expires September 1, 2016 [Page 2]
Internet-Draft SDP Proto Registrations February 2016
This specification describes additional SDP transport protocol
identifiers for transporting RTP Media over TCP as defined in
Section 3.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. Protocol Identifiers
The 'm=' line in SDP specifies, among other items, the transport
protocol (identified via the 'proto' field) to be used for the media
in the session. See the "MediaDescriptions" section of SDP [RFC4566]
for a discussion on transport protocol identifiers.
The following is the format for an 'm=' line, as specified in
[RFC4566]:
m=<media> <port> <proto> <fmt> ...
3.1. TCP/RTP/AVPF Transport Realization
The TCP/RTP/AVPF transport describes RTP Media with RTCP-based
Feedback [RFC4585] over TCP.
It is realized as described below:
o RTP/AVPF stream over the TCP transport is realized using the
framing method defined in [RFC4571].
3.2. TCP/RTP/SAVP Transport Realization
The TCP/RTP/SAVP transport describes Secure RTP (SRTP) Media
[RFC3711] over TCP.
It is realized as described below:
o RTP/SAVP stream over the TCP transport is realized using the
framing method defined in [RFC4571].
3.3. TCP/RTP/SAVPF Transport Realization
The TCP/RTP/SAVPF transport describes Secure RTP Media with RTCP-
based Feedback [RFC5124] over TCP.
It is realized as described below:
Nandakumar Expires September 1, 2016 [Page 3]
Internet-Draft SDP Proto Registrations February 2016
o RTP/SAVPF stream over the TCP transport is realized using the
framing method defined in [RFC4571].
3.4. TCP/DTLS/RTP/SAVP Transport Realization
The TCP/DTLS/RTP/SAVP transport describes Secure RTP Media [RFC3711]
using Datagram Transport Layer Security (DTLS) SRTP (DTLS-SRTP)
[RFC5764] over TCP.
It is realized as described below:
o RTP/SAVP using DTLS-based key establishment is realized according
to the procedures defined in [RFC5764]; and
o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP.
3.5. TCP/DTLS/RTP/SAVPF Transport Realization
The TCP/DTLS/RTP/SAVPF transport describes Secure RTP Media with
RTCP-based Feedback [RFC5124] using DTLS-SRTP over TCP.
It is realized as described below:
o RTP/SAVPF using DTLS-based key establishment is realized according
to the procedures defined in [RFC5764]; and
o [RFC4571] framing is used to transport DTLS-SRTP packets over TCP.
3.6. TCP/TLS/RTP/AVP Transport Realization
The TCP/TLS/RTP/AVP transport describes RTP Media on top of TLS over
TCP.
It is realized as described below:
o RTP/AVP packets are framed using the procedures from [RFC4571];
and
o [RFC4571] framed RTP/AVP packets are transported as Application
data messages over the TLS association setup using the procedures
from [RFC4572].
3.7. TCP/TLS/RTP/AVPF Transport Realization
The TCP/TLS/RTP/AVPF transport describes RTP Media with RTCP-based
Feedback [RFC5124] on top of TLS over TCP.
It is realized as described below:
Nandakumar Expires September 1, 2016 [Page 4]
Internet-Draft SDP Proto Registrations February 2016
o RTP/AVPF packets are framed using the procedures from [RFC4571];
and
o [RFC4571] framed RTP/AVPF packets are transported as Application
data messages over the TLS association setup using the procedures
from [RFC4572].
4. ICE Considerations
When procedures from [RFC6544] are used to setup Interactive
Connectivity Establishment (ICE) [RFC5245] candidates for a TCP
transport, the framing mechanism from [RFC4571] MUST be used for
framing Session Traversal Utilities for NAT (STUN) packets (for keep-
alives, consent checks), as defined in section 3 of [RFC6544].
5. IANA Considerations
This specification describes the following new SDP transport protocol
identifiers :'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF',
'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP',
'TCP/TLS/RTP/AVPF', as defined in Section 3. These proto values
should be registered by the IANA under the "proto" subregistry in the
"Session Description Protocol (SDP) Parameters" registry.
[To RFC Editor: Remove this note prior to publication. This
registration should take place at the following location:
http://www.iana.org/assignments/sdp-parameters/sdp-
parameters.xhtml#sdp-parameters-2. Replace XXXX in the table below
with the assigned number of this RFC]
+--------+---------------------+-----------+
| Type | SDP Name | Reference |
+--------+---------------------+-----------+
| proto | TCP/RTP/AVPF | RFCXXXX |
| | | |
| proto | TCP/RTP/SAVP | RFCXXXX |
| | | |
| proto | TCP/RTP/SAVPF | RFCXXXX |
| | | |
| proto | TCP/DTLS/RTP/SAVP | RFCXXXX |
| | | |
| proto | TCP/DTLS/RTP/SAVPF | RFCXXXX |
| | | |
| proto | TCP/TLS/RTP/AVP | RFCXXXX |
| | | |
| proto | TCP/TLS/RTP/AVPF | RFCXXXX |
+--------+---------------------+-----------+
Nandakumar Expires September 1, 2016 [Page 5]
Internet-Draft SDP Proto Registrations February 2016
6. Security Considerations
The new "proto" identifiers registered by this document in the SDP
parameters registry maintained by IANA is primarily for use by the
offer/answer model of the Session Description Protocol [RFC3264] for
the negotiation and establishment of RTP based Media over the TCP
transport. This specification doesn't introduce any additional
security considerations beyond those specified by the individual
transport protocols identified in the "proto" identifiers and those
detailed in Section 7 of [RFC4566].
7. Acknowledgements
Author would like to thank Cullen Jennings, Alissa Cooper, Justin
Uberti, Mo Zanaty, Christer Holmberg, Jonathan Lennox, Flemming
Andreason, Roni Even Ben Campbell and Bo Burman for their reviews and
suggested improvements.
Author would also like to thank Adam Montville for SECDIR review,
Meral Shirazipour for Gen-Art review and Sarah Banks for the OPS-Dir
review.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <http://www.rfc-editor.org/info/rfc4566>.
[RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP)
and RTP Control Protocol (RTCP) Packets over Connection-
Oriented Transport", RFC 4571, DOI 10.17487/RFC4571, July
2006, <http://www.rfc-editor.org/info/rfc4571>.
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", RFC 4572, DOI 10.17487/
RFC4572, July 2006,
<http://www.rfc-editor.org/info/rfc4572>.
Nandakumar Expires September 1, 2016 [Page 6]
Internet-Draft SDP Proto Registrations February 2016
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, DOI
10.17487/RFC5245, April 2010,
<http://www.rfc-editor.org/info/rfc5245>.
[RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer
Security (DTLS) Extension to Establish Keys for the Secure
Real-time Transport Protocol (SRTP)", RFC 5764, DOI
10.17487/RFC5764, May 2010,
<http://www.rfc-editor.org/info/rfc5764>.
[RFC6544] Rosenberg, J., Keranen, A., Lowekamp, B., and A. Roach,
"TCP Candidates with Interactive Connectivity
Establishment (ICE)", RFC 6544, DOI 10.17487/RFC6544,
March 2012, <http://www.rfc-editor.org/info/rfc6544>.
8.2. Informative References
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, DOI
10.17487/RFC3264, June 2002,
<http://www.rfc-editor.org/info/rfc3264>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <http://www.rfc-editor.org/info/rfc3550>.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, DOI 10.17487/RFC3711, March 2004,
<http://www.rfc-editor.org/info/rfc3711>.
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145, DOI
10.17487/RFC4145, September 2005,
<http://www.rfc-editor.org/info/rfc4145>.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
"Extended RTP Profile for Real-time Transport Control
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI
10.17487/RFC4585, July 2006,
<http://www.rfc-editor.org/info/rfc4585>.
Nandakumar Expires September 1, 2016 [Page 7]
Internet-Draft SDP Proto Registrations February 2016
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February
2008, <http://www.rfc-editor.org/info/rfc5124>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/
RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>.
Author's Address
Suhas Nandakumar
Cisco Systems Inc
707 Tasman Drive
San Jose, CA 95134
USA
Email: snandaku@cisco.com
Nandakumar Expires September 1, 2016 [Page 8]
