Browse Prior Art Database

RTP Payload Format for MPEG-4 Audio/Visual Streams (RFC6416)

IP.com Disclosure Number: IPCOM000213174D
Original Publication Date: 2011-Oct-01
Included in the Prior Art Database: 2011-Dec-07
Document File: 70 page(s) / 77K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Schmidt: AUTHOR [+4]

Abstract

The RTP payload formats described in this document specify how MPEG-4 Audio [14496-3] and MPEG-4 Visual streams [14496-2] are to be fragmented and mapped directly onto RTP packets.

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

Internet Engineering Task Force (IETF)                        M. Schmidt Request for Comments: 6416                            Dolby Laboratories Obsoletes: 3016                                               F. de Bont Category: Standards Track                            Philips Electronics ISSN: 2070-1721                                                S. Doehla                                                           Fraunhofer IIS                                                                   J. Kim                                                      LG Electronics Inc.                                                             October 2011

            RTP Payload Format for MPEG-4 Audio/Visual Streams

Abstract

   This document describes Real-time Transport Protocol (RTP) payload    formats for carrying each of MPEG-4 Audio and MPEG-4 Visual    bitstreams without using MPEG-4 Systems.  This document obsoletes RFC    3016.  It contains a summary of changes from RFC 3016 and discusses    backward compatibility to RFC 3016.  It is a necessary revision of    RFC 3016 in order to correct misalignments with the 3GPP Packet-    switched Streaming Service (PSS) specification regarding the RTP    payload format for MPEG-4 Audio.

   For the purpose of directly mapping MPEG-4 Audio/Visual bitstreams    onto RTP packets, this document provides specifications for the use    of RTP header fields and also specifies fragmentation rules.  It also    provides specifications for Media Type registration and the use of    the Session Description Protocol (SDP).  The audio payload format    described in this document has some limitations related to the    signaling of audio codec parameters for the required multiplexing    format.  Therefore, new system designs should utilize RFC 3640, which    does not have these restrictions.  Nevertheless, this revision of RFC    3016 is provided to update and complete the specification and to    enable interoperable implementations.

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

 Schmidt, et al.              Standards Track                  ...