RFC 3558 on RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)

rfc-editor@rfc-editor.org Wed, 30 July 2003 00:08 UTC

Message-Id: <200307300002.h6U02QJ18091@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3558 on RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)
Cc: rfc-editor@rfc-editor.org, avt@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 29 Jul 2003 17:02:26 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3558

        Title:      RTP Payload Format for Enhanced Variable Rate
                    Codecs (EVRC) and Selectable Mode Vocoders (SMV)
        Author(s):  A. Li
        Status:     Standards Track
        Date:       July 2003
        Mailbox:    adamli@icsl.ucla.edu
        Pages:      23
        Characters: 49787
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-avt-evrc-smv-03.txt

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


This document describes the RTP payload format for Enhanced Variable
Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV)
Speech.  Two sub-formats are specified for different application
scenarios.  A bundled/interleaved format is included to reduce the
effect of packet loss on speech quality and amortize the overhead of
the RTP header over more than one speech frame.  A non-bundled format
is also supported for conversational applications.

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

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.


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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3558.txt"><ftp://ftp.isi.edu/in-notes/rfc3558.txt>

RFC 3558 on RTP Payload Format for Enhanced Varia… rfc-editor