[rfc-dist] RFC 5219 on A More Loss-Tolerant RTP Payload Format for MP3 Audio

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Feb 14 18:10:57 PST 2008


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

        
        RFC 5219

        Title:      A More Loss-Tolerant RTP Payload 
                    Format for MP3 Audio 
        Author:     R. Finlayson
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    finlayson at live555.com
        Pages:      22
        Characters: 42830
        Obsoletes:  RFC3119  

        I-D Tag:    draft-ietf-avt-rfc3119bis-05.txt

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

This document describes an RTP (Real-Time Protocol) payload format for
transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III
audio (commonly known as "MP3").  This format is an alternative to
that described in RFC 2250, and performs better if there is packet
loss.  This document obsoletes RFC 3119, correcting
typographical errors in the "SDP usage" section and pseudo-code
appendices.  [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 unlimited.

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
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list