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

Harinath Garudadri <hgarudad@qualcomm.com> Mon, 10 March 2003 17:10 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 MAA03692 for <avt-archive@odin.ietf.org>; Mon, 10 Mar 2003 12:10:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h2AHNgD29488 for avt-archive@odin.ietf.org; Mon, 10 Mar 2003 12:23:42 -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 h2AHGiO28698; Mon, 10 Mar 2003 12:16:44 -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 h27ICiO21516 for <avt@optimus.ietf.org>; Fri, 7 Mar 2003 13:12:44 -0500
Received: from numenor.qualcomm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20262 for <avt@ietf.org>; Fri, 7 Mar 2003 13:00:35 -0500 (EST)
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.12.8/8.12.5/1.0) with ESMTP id h27HvdKn016644; Fri, 7 Mar 2003 09:57:39 -0800 (PST)
Received: from HGARUDAD.qualcomm.com (hgarudad.qualcomm.com [129.46.74.119]) by crowley.qualcomm.com (8.12.8/8.12.5/1.0) with ESMTP id h27HvaZJ004667; Fri, 7 Mar 2003 09:57:37 -0800 (PST)
Message-Id: <5.1.0.14.2.20030307094345.01de9ed8@mail1.qualcomm.com>
X-Sender: hgarudad@mail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 07 Mar 2003 09:57:36 -0800
To: Mark Baugher <mbaugher@cisco.com>, Adam Li <adamli@icsl.ucla.edu>
From: Harinath Garudadri <hgarudad@qualcomm.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: <5.1.1.5.2.20030306043913.06c676b8@mira-sjc5-6.cisco.com>
References: <008d01c2e353$a044cf50$4500a8c0@divxnetworks.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_1210941==_.ALT"
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>

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? 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.

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