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

Mark Baugher <mbaugher@cisco.com> Mon, 10 March 2003 17:35 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 MAA04809 for <avt-archive@odin.ietf.org>; Mon, 10 Mar 2003 12:35:28 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2AHmW731954 for avt-archive@odin.ietf.org; Mon, 10 Mar 2003 12:48:32 -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 h2AHfdO31614; Mon, 10 Mar 2003 12:41:39 -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 h2AHeeO31527 for <avt@optimus.ietf.org>; Mon, 10 Mar 2003 12:40:40 -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 MAA04463 for <avt@ietf.org>; Mon, 10 Mar 2003 12:27:04 -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 h2AHOwPj015721; Tue, 11 Mar 2003 04:25:01 +1100 (EST)
Message-Id: <5.1.1.5.2.20030310092026.04c98f10@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 10 Mar 2003 09:25:00 -0800
To: Harinath Garudadri <hgarudad@qualcomm.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [AVT] File format for EVRC/SMV vocoder
Cc: Adam Li <adamli@icsl.ucla.edu>, Ietf-Avt <avt@ietf.org>, 3GPP2 TSG-C <tsgc@3gpp2.org>
In-Reply-To: <5.1.0.14.2.20030307094345.01de9ed8@mail1.qualcomm.com>
References: <5.1.1.5.2.20030306043913.06c676b8@mira-sjc5-6.cisco.com> <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>

Hari,

At 09:57 AM 3/7/2003 -0800, Harinath Garudadri wrote:
>At 04:46 AM 3/6/2003 -0800, Mark Baugher wrote:
>>Adam
>>   I have a question:  Why take a file format specification through the IETF?
>
>Hi Mark,
>did you mean AVT above?

No, I meant the IETF.  I asked the question because I don't think of the 
IETF as having a lot of file-format expertise so it's not the obvious place 
to develop file-format technology.

>We were not sure if draft-garudadri-qcp-00.txt should go in to AVT or as 
>an independent submission. I do not think this has been resolved yet.
>
>If you meant IETF, our motivation was if a multimedia object (message?) 
>was delivered over some mechanism other than RTP/UDP, (e.g. http, ftp, 
>etc.) the receiver should be able to render the multimedia content 
>appropriately. One example is if you create a voice attachment in Eudora 
>email client, it is stored as a qcp file described in 
>draft-garudadri-qcp-00.txt. If you send this email to someone who uses a 
>different email client, that person could play the attachment in the 
>QuickTime player, as QuickTime supports the above format.

Is it related to MP4, then?

Best Regards, Mark


>Thanks,
>hari.
>
>
>>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
>
>Dr. Hari Garudadri
>phone : 858-651-6383
>mobile : 858-229-2801
>pager  : 858-653-0963 or hgarudadri@pager.qualcomm.com

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