[AVT] RFC 5188 on RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec
rfc-editor@rfc-editor.org Wed, 27 February 2008 19:40 UTC
Return-Path: <avt-bounces@ietf.org>
X-Original-To: ietfarch-avt-archive@core3.amsl.com
Delivered-To: ietfarch-avt-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02C1E28C54C; Wed, 27 Feb 2008 11:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.28
X-Spam-Level:
X-Spam-Status: No, score=-0.28 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkZE1ZHOhIcE; Wed, 27 Feb 2008 11:40:15 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB82828C30B; Wed, 27 Feb 2008 11:39:58 -0800 (PST)
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D72A228C309; Wed, 27 Feb 2008 11:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uk7VuhN5JD-M; Wed, 27 Feb 2008 11:39:52 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 625F73A6E80; Wed, 27 Feb 2008 11:39:52 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 2AB32116EB8; Wed, 27 Feb 2008 11:39:46 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080227193946.2AB32116EB8@bosco.isi.edu>
Date: Wed, 27 Feb 2008 11:39:46 -0800
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVT] RFC 5188 on RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5188
Title: RTP Payload Format for the
Enhanced Variable Rate Wideband Codec (EVRC-WB)
and the Media Subtype Updates for
EVRC-B Codec
Author: H. Desineni, Q. Xie
Status: Standards Track
Date: February 2008
Mailbox: hd@qualcomm.com,
Qiaobing.Xie@Gmail.com
Pages: 25
Characters: 44821
Updates: RFC4788
I-D Tag: draft-ietf-avt-rtp-evrc-wb-09.txt
URL: http://www.rfc-editor.org/rfc/rfc5188.txt
This document specifies Real-time Transport Protocol (RTP) payload
formats to be used for the Enhanced Variable Rate Wideband Codec
(EVRC-WB) and updates the media type registrations for EVRC-B codec.
Several media type registrations are included for EVRC-WB RTP payload
formats. In addition, a file format is specified for transport of
EVRC-WB speech data in storage mode applications such as email.
[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@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.
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.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt