| MMUSIC | S. Nandakumar |
| Internet-Draft | Cisco Systems Inc |
| Intended status: Standards Track | January 26, 2016 |
| Expires: July 29, 2016 |
IANA registrations of SDP 'proto' attribute for transporting RTP Media over TCP under various RTP profiles.
draft-ietf-mmusic-proto-iana-registration-05
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'.
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 July 29, 2016.
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 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.
RTP provides end-to-end network transport functions suitable for applications transmitting real-time data such as audio, video or simulation data, 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.
SDP [RFC4566] provides a general-purpose format for describing multimedia sessions in announcements or invitations. [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). [RFC4572] extends [RFC4145] for describing TCP-based media streams that are protected using Transport Layer Security (TLS) [RFC5246].
This specification describes additional SDP transport protocol identifiers for transporting RTP Media over TCP as defined in Section 3.
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].
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> ...
The TCP/RTP/AVPF transport describes RTP Media with RTCP-based Feedback [RFC4585] over TCP.
It is realized as described below:
The TCP/RTP/SAVP transport describes Secure RTP (SRTP) Media [RFC3711] over TCP.
It is realized as described below:
The TCP/RTP/SAVPF transport describes Secure RTP Media with RTCP-based Feedback [RFC5124] over TCP.
It is realized as described below:
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:
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:
The TCP/TLS/RTP/AVP transport describes RTP Media on top of TLS over TCP.
It is realized as described below:
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:
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].
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 the 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 |
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].
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.