How to Write an RTP Payload Format
draft-ietf-payload-rtp-howto-14

 
Document Type Active Internet-Draft (payload WG)
Last updated 2015-05-04
Replaces draft-ietf-avt-rtp-howto
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Ali Begen
Shepherd write-up Show (last changed 2013-10-11)
IESG IESG state RFC Ed Queue
Telechat date
Responsible AD Richard Barnes
Send notices to payload-chairs@ietf.org, draft-ietf-payload-rtp-howto@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state MISSREF

Email authors IPR References Referenced by Nits Search lists

Payload Working Group                                      M. Westerlund
Internet-Draft                                                  Ericsson
Updates: 2736 (if approved)                                  May 4, 2015
Intended status: Informational
Expires: November 5, 2015

                   How to Write an RTP Payload Format
                    draft-ietf-payload-rtp-howto-14

Abstract

   This document contains information on how to best write an RTP
   payload format specification.  It provides reading tips, design
   practices, and practical tips on how to produce an RTP payload format
   specification quickly and with good results.  A template is also
   included with instructions.

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 November 5, 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

Westerlund              Expires November 5, 2015                [Page 1]
Internet-Draft         HOWTO: RTP Payload Formats               May 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Structure . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Use of Normative Requirements Language  . . . . . . . . .   6
   3.  Preparations  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Read and Understand the Media Coding Spec . . . . . . . .   6
     3.2.  Recommended Reading . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  IETF Process and Publication  . . . . . . . . . . . .   7
       3.2.2.  RTP . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.3.  Important RTP Details . . . . . . . . . . . . . . . . . .  12
       3.3.1.  The RTP Session . . . . . . . . . . . . . . . . . . .  13
       3.3.2.  RTP Header  . . . . . . . . . . . . . . . . . . . . .  13
       3.3.3.  RTP Multiplexing  . . . . . . . . . . . . . . . . . .  15
       3.3.4.  RTP Synchronization . . . . . . . . . . . . . . . . .  16
     3.4.  Signalling Aspects  . . . . . . . . . . . . . . . . . . .  18
       3.4.1.  Media Types . . . . . . . . . . . . . . . . . . . . .  18
       3.4.2.  Mapping to SDP  . . . . . . . . . . . . . . . . . . .  20
     3.5.  Transport Characteristics . . . . . . . . . . . . . . . .  22
       3.5.1.  Path MTU  . . . . . . . . . . . . . . . . . . . . . .  22
       3.5.2.  Different Queuing Algorithms  . . . . . . . . . . . .  23
       3.5.3.  Quality of Service  . . . . . . . . . . . . . . . . .  24
   4.  Standardisation Process for an RTP Payload Format . . . . . .  24
     4.1.  IETF  . . . . . . . . . . . . . . . . . . . . . . . . . .  24
       4.1.1.  Steps from Idea to Publication  . . . . . . . . . . .  24
       4.1.2.  WG meetings . . . . . . . . . . . . . . . . . . . . .  26
       4.1.3.  Draft Naming  . . . . . . . . . . . . . . . . . . . .  26
       4.1.4.  Writing Style . . . . . . . . . . . . . . . . . . . .  27
       4.1.5.  How to speed up the process . . . . . . . . . . . . .  28
     4.2.  Other Standards Bodies  . . . . . . . . . . . . . . . . .  29
     4.3.  Proprietary and Vendor Specific . . . . . . . . . . . . .  29
     4.4.  Joint Development of Media Coding Specification and RTP
           Payload Format  . . . . . . . . . . . . . . . . . . . . .  30
   5.  Designing Payload Formats . . . . . . . . . . . . . . . . . .  30
     5.1.  Features of RTP Payload Formats . . . . . . . . . . . . .  31
Show full document text