Re: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.

Randall Gellens <randy@qualcomm.com> Wed, 05 September 2001 00:49 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01428 for <avt-archive@odin.ietf.org>; Tue, 4 Sep 2001 20:49:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13699; Tue, 4 Sep 2001 20:49:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13668 for <avt@ns.ietf.org>; Tue, 4 Sep 2001 20:49:10 -0400 (EDT)
Received: from strange.qualcomm.com (strange.qualcomm.com [129.46.64.124]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01409 for <avt@ietf.org>; Tue, 4 Sep 2001 20:47:44 -0400 (EDT)
Received: from randy-nt.qualcomm.com (randy-nt.qualcomm.com [129.46.156.238]) by strange.qualcomm.com (8.11.3/8.11.3/1.0) with ESMTP id f850n7k21817 for <avt@ietf.org>; Tue, 4 Sep 2001 17:49:07 -0700 (PDT)
Message-Id: <5.1.0.14.0.20010904173339.01e9e308@flagg.qualcomm.com>
X-Sender: randy@flagg.qualcomm.com@flagg.qualcomm.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 04 Sep 2001 17:49:06 -0700
To: avt@ietf.org
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.
In-Reply-To: <5.1.0.14.2.20010830151146.00a84f38@illyana.qualcomm.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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
X-BeenThere: avt@ietf.org

Is it useful to have a common format for EVRC and SMV and possibly other 
codecs?  This probably depends on sub-questions: Are there likely to be 
implementations which must support multiple codecs?  Is it simpler for such 
implementations if the formats are identical?

If it is useful to have a common format, is it harmful to have multiple 
formats for the same codec?  If so, we probably want to roll the current 
EVRC and SMV drafts into the new common one.

As for MIME registration, it occurs to me that we may be able to have one 
new MIME type for the common format, with a parameter specifying which 
particular codec is being used.  For example, "audio/foo; codec=bar".  The 
common format specification can include in the IANA Considerations section 
instructions on registering new values for the codec parameter for future 
codecs which want to use the common format.  Presumably such registration 
would include the mapping between frame type and frame length, which 
hopefully would be about the only difference from one codec to another.

Making EVRC and SMV use the same format is probably an easier question than 
including PureVoice as well, and so should be discussed separately, I think.


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