[rfc-dist] RFC 4598 on Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) Audio

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Jul 28 17:41:19 PDT 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4598

        Title:      Real-time Transport Protocol (RTP) Payload 
                    Format for Enhanced AC-3 (E-AC-3) Audio 
        Author:     B. Link
        Status:     Standards Track
        Date:       July 2006
        Mailbox:    bdl at dolby.com
        Pages:      17
        Characters: 39811
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-rtp-eac3-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4598.txt

This document describes a Real-time Transport Protocol (RTP) payload
format for transporting Enhanced AC-3 (E-AC-3) encoded audio data.
E-AC-3 is a high-quality, multichannel audio coding format and is an
extension of the AC-3 audio coding format, which is used in US
High-Definition Television (HDTV), DVD, cable and satellite
television, and other media.  E-AC-3 is an optional audio format in US
and world wide digital television and high-definition DVD formats.
The RTP payload format as presented in this document includes support
for data fragmentation.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list