Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

How to Write an RTP Payload Format (RFC8088)

IP.com Disclosure Number: IPCOM000249927D
Original Publication Date: 2017-May-01
Included in the Prior Art Database: 2017-May-03

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Westerlund: AUTHOR

Abstract

RTP [RFC3550] payload formats define how a specific real-time data format is structured in the payload of an RTP packet. A real-time data format without a payload format specification cannot be transported using RTP. This creates an interest in many individuals/ organizations with media encoders or other types of real-time data to define RTP payload formats. However, the specification of a well- designed RTP payload format is nontrivial and requires knowledge of both RTP and the real-time data format.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Internet Engineering Task Force (IETF)                     M. Westerlund Request for Comments: 8088                                      Ericsson Updates: 2736                                                   May 2017 Category: Informational ISSN: 2070-1721

                    How to Write an RTP Payload Format

Abstract

   This document contains information on how best to 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 document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8088.

Copyright Notice

   Copyright (c) 2017 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.

 Westerlund                    Informational                     [Page 1]
 RFC 8088               HOWTO: RTP Payload Formats               May 2017

 Table of Contents

   1. Introduction ....................................................4

      1.1. Structure ..................................................4

   2. Terminology .....................................................5

      2.1. Definitions ................................................5

      2.2. Abbreviations ..............................................5

      2.3. Use of Normative Requirements Language .....................6

   3. Preparations ....................................................6

     ...