Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
RFC 4856

Document Type RFC - Proposed Standard (February 2007; Errata)
Obsoletes RFC 3555
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4856 (Proposed Standard)
Telechat date
Responsible AD Cullen Jennings
Send notices to avt-chairs@ietf.org, casner@acm.org
Network Working Group                                          S. Casner
Request for Comments: 4856                                 Packet Design
Obsoletes: 3555                                               March 2007
Category: Standards Track

           Media Type Registration of Payload Formats in the
              RTP Profile for Audio and Video Conferences

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document specifies media type registrations for the RTP payload
   formats defined in the RTP Profile for Audio and Video Conferences.
   Some of these may also be used for transfer modes other than RTP.

Table of Contents
   1. Introduction ....................................................2
      1.1. IANA Considerations ........................................2
      1.2. Terminology ................................................3
   2. Registrations for "Audio/Video Profile" .........................3
      2.1. Audio Type Registrations ...................................3
      2.2. Video Type Registrations ..................................24
   3. Changes from RFC 3555 ..........................................25
   4. Security Considerations ........................................26
   5. References .....................................................27
      5.1. Normative References ......................................27
      5.2. Informative References ....................................27

Casner                      Standards Track                     [Page 1]
RFC 4856      RTP Payload Formats for Audio/Video Profile     March 2007

1.  Introduction

   This document updates the media type registrations initially
   specified in RFC 3555 for the Real-time Transport Protocol (RTP)
   payload formats defined in the RTP Profile for Audio and Video
   Conferences, RFC 3551 [1], as subtypes under the "audio" and "video"
   media types.  This document does not include media type registrations
   for the RTP payload formats that are referenced in RFC 3551 but
   defined in other RFCs.  The media type registrations for those
   payload formats are intended to be updated by including them in
   revisions of the individual RFCs defining the payload formats.

   The media type registrations specified here conform to the updated
   template format and procedures in RFC 4288 [2] and RFC 4855 [3].
   This update makes no technical changes in the registrations.
   Together with RFC 4855, this document obsoletes RFC 3555.

1.1.  IANA Considerations

   As a consequence of the generalized applicability of the media types
   registry as specified in RFC 4288, some changes in nomenclature are
   needed in the RTP Payload Format section of the registry.  In the
   registry title "RTP Payload Format MIME types" and the introductory
   text, "MIME" should be changed to "media". "MIME" should be deleted
   from the table headings, leaving just "media type" and "subtype".

   This document updates the media type registrations listed below to
   conform to the revised registration format specified in RFC 4288 and
   RFC 4855, so the reference for these media types should be changed
   from RFC 3555 to this document.  Some media type registrations
   contained in RFC 3555 are omitted from this document; the existing
   registrations for those types continue to be valid until updated by
   other RFCs.  There are no new registrations contained here.

Casner                      Standards Track                     [Page 2]
RFC 4856      RTP Payload Formats for Audio/Video Profile     March 2007

      audio/DVI4
      audio/G722
      audio/G723
      audio/G726-16
      audio/G726-24
      audio/G726-32
      audio/G726-40
      audio/G728
      audio/G729
      audio/G729D
      audio/G729E
      audio/GSM
      audio/GSM-EFR
      audio/L8
      audio/L16
      audio/LPC
      audio/PCMA
      audio/PCMU
      audio/VDVI
      video/nv

   Media type audio/L16 was initially registered via RFC 2586 for
   transports other than RTP.  That registration is incorporated here
   and augmented with additional information for RTP transport.

1.2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text