One document matched: draft-nandakumar-mmusic-proto-iana-registration-00.txt
MMUSIC S. Nandakumar
Internet-Draft Cisco Systems Inc
Intended status: Standards Track September 18, 2014
Expires: March 22, 2015
IANA registration of SDP 'proto' attribute for transporting RTP Media
over TCP under various RTP profiles.
draft-nandakumar-mmusic-proto-iana-registration-00
Abstract
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.
This document describes how to express RTP media transport over TCP
in SDP (Session Description Protocol) under various configurations.
This document defines 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/
SAVPF', 'TCP/TLS/RTP/SAVP', 'TCP/TLS/RTP/SAVPF' protocol identifiers
for SDP.
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 March 22, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
Nandakumar Expires March 22, 2015 [Page 1]
Internet-Draft SDP Proto Registrations September 2014
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.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Identifier . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Overview
SDP (Session Description Protocol) [RFC4566] provides a general-
purpose format for describing multimedia sessions in announcements or
invitations. [RFC4145] specifies a general mechanism for describing
and establishing TCP (Transmission Control Protocol) streams 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
(Transport Layer Security).
Nandakumar Expires March 22, 2015 [Page 2]
Internet-Draft SDP Proto Registrations September 2014
The RTP specification [RFC3550] establishes a registry of profile
names for use by higher-level control protocols, such as the Session
Description Protocol (SDP), to refer to transport methods. This
document 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.
TCP/RTP/SAVP: to describe Secure RTP Media [RFC3711] over TCP.
TCP/RTP/SAVPF: to describe Secure RTP Media with RTCP-based Feedback
[RFC5124] over TCP.
TCP/TLS/RTP/SAVP: to describe Secure RTP Media [RFC3711] on top of
TLS [RFC5246] over TCP.
TCP/TLS/RTP/SAVPF: to describe Secure RTP Media with RTCP-based
Feedback [RFC5124] on top of TLS over TCP.
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 Identifier
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.
This specification defines new protocol identifiers 'TCP/RTP/AVPF',
'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 'TCP/TLS/RTP/SAVP', 'TCP/TLS/RTP/
SAVPF' which indicates that the media described will use TCP as the
transport protocol.
When a RTP/AVPF stream is transported over the TCP transport, the
proto identifier SHALL be 'TCP/RTP/AVPF'.
When a RTP/SAVP stream is transported over the TCP transport, the
proto identifier SHALL be 'TCP/RTP/SAVP'.
When a RTP/SAVPF stream is transported over the TCP transport, the
proto identifier SHALL be 'TCP/RTP/SAVPF'.
Nandakumar Expires March 22, 2015 [Page 3]
Internet-Draft SDP Proto Registrations September 2014
When RTP/SAVP stream is transport over TLS with TCP transport, the
proto identifier SHALL be 'TCP/TLS/RTP/SAVP'.
When RTP/SAVPF stream is transport over TLS with TCP transport,
the proto identifier SHALL be 'TCP/TLS/RTP/SAVPF'.
An 'm' line that specifies these new proto identifiers MUST further
qualify the application-layer protocol using an fmt identifier.
4. IANA Considerations
This document describes five new proto values: 'TCP/RTP/AVPF',
'TCP/RTP/SAVP', 'TCP/RTP/SAVPF', 'TCP/TLS/RTP/SAVP', 'TCP/TLS/RTP/
SAVPF' as defined in the section Section 3. These proto values
should be registered by the IANA under "Session Description Protocol
(SDP) Parameters" under "proto".
5. 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. These additional SDP "proto" identifiers does not
introduce any security considerations beyond those detailed in
Section 7 of [RFC4566].
6. Acknowledgements
Author would like to thank Cullen Jennings and Alissa Cooper for
their early reviews and suggested improvements.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006.
[RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP)
and RTP Control Protocol (RTCP) Packets over Connection-
Oriented Transport", RFC 4571, July 2006.
Nandakumar Expires March 22, 2015 [Page 4]
Internet-Draft SDP Proto Registrations September 2014
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the
Transport Layer Security (TLS) Protocol in the Session
Description Protocol (SDP)", RFC 4572, July 2006.
7.2. Informative References
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, June
2002.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, March 2004.
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145,
September 2005.
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer
Security", RFC 4347, April 2006.
[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, July
2006.
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for
Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008.
Author's Address
Suhas Nandakumar
Cisco Systems Inc
707 Tasman Drive
San Jose, CA 95134
USA
Email: snandaku@cisco.com
Nandakumar Expires March 22, 2015 [Page 5]
| PAFTECH AB 2003-2026 | 2026-04-23 21:35:32 |