| MMUSIC | S. Nandakumar |
| Internet-Draft | Cisco Systems Inc |
| Intended status: Standards Track | July 3, 2015 |
| Expires: January 4, 2016 |
IANA registrations of SDP 'proto' attribute for transporting RTP Media over TCP under various RTP profiles.
draft-ietf-mmusic-proto-iana-registration-01
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 a 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.
The RTP specification [RFC3550] establishes a registry of profile names for use by higher-level control protocols, such as the 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 January 4, 2016.
Copyright (c) 2015 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.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
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 TCP using SDP with [RFC4571] defining a method for framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) packets onto a connection-oriented transport (such as TCP) . [RFC4572] extends [RFC4145] for describing TCP-based media streams that are protected using TLS [RFC5246].
This specification describes the following new SDP transport protocol identifiers for transporting RTP Media over TCP:
TCP/RTP/AVPF: to describe RTP Media with RTCP-based Feedback [RFC4585] over TCP, as defined in Section 3.1.
TCP/RTP/SAVP: to describe Secure RTP Media [RFC3711] over TCP, as defined in Section 3.2.
TCP/RTP/SAVPF: to describe Secure RTP Media with RTCP-based Feedback [RFC5124] over TCP, as defined in Section 3.3.
TCP/DTLS/RTP/SAVP: to describe Secure RTP Media [RFC3711] using DTLS-SRTP [RFC5764] over TCP, as defined in Section 3.4.
TCP/DTLS/RTP/SAVPF: to describe Secure RTP Media with RTCP-based Feedback [RFC5124] using DTLS-SRTP over TCP, as defined in Section 3.5.
TCP/TLS/RTP/AVP: to describe RTP Media on top of TLS over TCP, as defined in Section 3.6.
TCP/TLS/RTP/AVPF: to describe RTP Media with RTCP-based Feedback [RFC5124] on top of TLS over TCP, as defined in Section 3.7.
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 to be used for the media in the session. See the "Media Descriptions" 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> ...
An 'm' line that specifies these new proto identifiers MUST further qualify the application-layer protocol using an fmt identifier.
The TCP/RTP/AVPF is realized as described below:
The TCP/RTP/SAVP is realized as described below:
The TCP/RTP/SAVPF is realized as described below:
The TCP/DTLS/RTP/SAVP is realized as described below:
The TCP/DTLS/RTP/SAVPF is realized as described below:
The TCP/TLS/RTP/AVP is realized as described below:
The TCP/TLS/RTP/AVPF is realized as described below:
When procedures from [RFC6544] are used to setup ICE [RFC5245] candidates for a TCP transport, the framing mechanism from [RFC4571] is used for framing 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:
Additionally the following proto values described in [RFC5764] should be registered under the "RTP Profile Names" subregistry in the "Real-Time Transport Protocol (RTP) Parameters" registry: 'UDP/TLS/RTP/SAVP' , 'DCCP/TLS/RTP/SAVP', 'UDP/TLS/RTP/SAVPF', 'DCCP/TLS/RTP/SAVPF'.
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. These additional SDP "proto" identifiers does not introduce any security considerations beyond those detailed in Section 7 of [RFC4566].
Author would like to thank Cullen Jennings, Alissa Cooper, Justin Uberti, Mo Zanaty, Christer Holmberg, Jonathan Lennox for their reviews and suggested improvements.