[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-sjoberg-avt-rtp-amr)   00 01 02         Standards Track
          03 04 05 06 07 08 09 10 11 12 13 rfc3267                      
A new Request for Comments is now available in online RFC libraries.

        RFC 3267

        Title:      Real-Time Transport Protocol (RTP) Payload Format
                    and File Storage Format for the Adaptive
                    Multi-Rate (AMR) and Adaptive Multi-Rate Wideband
                    (AMR-WB) Audio Codecs
        Author(s):  J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie
        Status:     Standards Track
        Date:       June 2002
        Mailbox:    Johan.Sjoberg@ericsson.com,
                    ari.lakaniemi@nokia.com, qxie1@email.mot.com
        Pages:      49
        Characters: 110652
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-avt-rtp-amr-13.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3267.txt

This document specifies a real-time transport protocol (RTP)
payload format to be used for Adaptive Multi-Rate (AMR) and
Adaptive Multi-Rate Wideband (AMR-WB) encoded speech
signals.  The payload format is designed to be able to interoperate
with existing AMR and AMR-WB transport formats on non-IP
networks.  In addition, a file format is specified for transport of
AMR and AMR-WB speech data in storage mode applications such as
email.  Two separate MIME type registrations are included, one for
AMR and one for AMR-WB, specifying use of both the RTP payload
format and the storage format.

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

This is now a Proposed Standard Protocol.

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@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@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.