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

"Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se> Fri, 07 March 2003 12:24 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 HAA25118 for <avt-archive@odin.ietf.org>; Fri, 7 Mar 2003 07:24:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h27Ca8E18760 for avt-archive@odin.ietf.org; Fri, 7 Mar 2003 07:36:08 -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 h27CXdO18584; Fri, 7 Mar 2003 07:33: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 h27CChO17153 for <avt@optimus.ietf.org>; Fri, 7 Mar 2003 07:12:43 -0500
Received: from penguin.wise.edt.ericsson.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22793 for <avt@ietf.org>; Fri, 7 Mar 2003 07:00:42 -0500 (EST)
Received: from esealnt612.al.sw.ericsson.se (alteon-nat1.sw.ericsson.se [153.88.254.118]) by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h27C2Twx001896; Fri, 7 Mar 2003 13:02:30 +0100 (MET)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55) id <F5W9928C>; Fri, 7 Mar 2003 13:02:29 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9028@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: Adam Li <adamli@icsl.ucla.edu>
Cc: Ietf-Avt <avt@ietf.org>
Subject: RE: [AVT] File format for EVRC/SMV vocoder
Date: Fri, 07 Mar 2003 12:58:04 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain; charset="iso-8859-1"
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 and others,

I thought the reason for defining also the file format in the IETF
was to make it in line with the transport format, and also because
you would get it almost "for free" when you define the transport
format. The proposed new approach seems to take away those motives,
and then I do not understand why we should do it in the IETF.

Further, I wonder what would be the rationales for using this new
QCP format instead of the file format defined in the EVRC/SMV draft?

If we are to standardize a file format in this body, I can not see
why we should not stick to the format that is already finalized and
has been taken through our standards process. 

/L-E


> -----Original Message-----
> From: Mark Baugher [mailto:mbaugher@cisco.com]
> 
> Adam
>    I have a question:  Why take a file format specification 
> through the IETF?
> 
> Best regards, Mark
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt