Re: [AVT] File format for EVRC/SMV vocoder

Mark Baugher <mbaugher@cisco.com> Thu, 06 March 2003 13:01 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10890 for <avt-archive@odin.ietf.org>; Thu, 6 Mar 2003 08:01:05 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h26DC7802150 for avt-archive@odin.ietf.org; Thu, 6 Mar 2003 08:12:07 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26DBgO02092; Thu, 6 Mar 2003 08:11:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26DATO02035 for <avt@optimus.ietf.org>; Thu, 6 Mar 2003 08:10:29 -0500
Received: from syd-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10628 for <avt@ietf.org>; Thu, 6 Mar 2003 07:58:55 -0500 (EST)
Received: from cscoamera13263.cisco.com (localhost [127.0.0.1]) by syd-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h26CtmPp016337; Thu, 6 Mar 2003 23:55:52 +1100 (EST)
Message-Id: <5.1.1.5.2.20030306043913.06c676b8@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Thu, 06 Mar 2003 04:46:05 -0800
To: Adam Li <adamli@icsl.ucla.edu>
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] File format for EVRC/SMV vocoder
Cc: Ietf-Avt <avt@ietf.org>, 3GPP2 TSG-C <tsgc@3gpp2.org>
In-Reply-To: <008d01c2e353$a044cf50$4500a8c0@divxnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>

Adam
   I have a question:  Why take a file format specification through the IETF?

Best regards, Mark
At 12:13 PM 3/5/2003 -0800, Adam Li wrote:
>Hi folks,
>
>One issue just recently been raised about the file format for EVRC and
>SMV data, which is specified the MIME registration for them. We very
>much would like to hear your ideas and comments on this issue.
>
>As you may have known, we are working the IETF specification on the RTP
>Payload Format for EVRC/SMV. It specifies how the EVRC/SMV payload is
>carried in RTP sessions, and it also registered the MIME format for the
>EVRC and SMV vocoders. The draft (draft-ietf-avt-evrc-smv) is currently
>at the final editing stage at the IETF FRC Editor's queue.
>
>There has been a file format defined in the draft-ietf-avt-evrc-smv at
>the MIME registration for EVRC/SMV. The file format specified there
>hasn't been changed much since the first version of the draft in 2000.
>
>There is a new Internet Draft, draft-garudadri-qcp-00.txt, specifies a
>different way of storage using the QCP file format, which has been used
>for QCEPL-13K and EVRC by some applications.
>
>Currently, it has been proposed to remove the file format specification
>in the draft-ietf-avt-evrc-smv, and to expand the draft-garudadri-qcp to
>be the only formal specification for the file format for EVRC/SMV. On
>the other hand, there are also suggestions to keep the file format at it
>is specified in the draft-ietf-avt-evrc-smv.
>
>We would like to hear your suggestions, and hear from you how you think
>would be the best way to proceed. Your comments are very much
>appreciated.
>
>Adam
>
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt