IANA registrations of SDP 'proto' attribute for transporting RTP Media over TCP under various RTP profiles.
draft-ietf-mmusic-proto-iana-registration-02

The information below is for an old version of the document
Document Type Active Internet-Draft (mmusic WG)
Last updated 2015-11-20 (latest revision 2015-10-08)
Replaces draft-nandakumar-mmusic-proto-iana-registration
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: Dec 2015 - Submit IANA registra... )
Document shepherd Bo Burman
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Bo Burman" <bo.burman@ericsson.com>
MMUSIC                                                     S. Nandakumar
Internet-Draft                                         Cisco Systems Inc
Intended status: Standards Track                         October 8, 2015
Expires: April 10, 2016

 IANA registrations of SDP 'proto' attribute for transporting RTP Media
                  over TCP under various RTP profiles.
              draft-ietf-mmusic-proto-iana-registration-02

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.

   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'.

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 April 10, 2016.

Nandakumar               Expires April 10, 2016                 [Page 1]
Internet-Draft           SDP Proto Registrations            October 2015

Copyright Notice

   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.

Table of Contents

   1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Identifiers  . . . . . . . . . . . . . . . . . . . .   3
     3.1.  TCP/RTP/AVPF Transport Realization  . . . . . . . . . . .   4
     3.2.  TCP/RTP/SAVP Transport Realization  . . . . . . . . . . .   4
     3.3.  TCP/RTP/SAVPF Transport Realization . . . . . . . . . . .   4
     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 . . . . . . . . . .   5
     3.7.  TCP/TLS/RTP/AVPF Transport Realization  . . . . . . . . .   5
   4.  ICE Considerations  . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

Nandakumar               Expires April 10, 2016                 [Page 2]
Show full document text