Re: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.
Colin Perkins <csp@isi.edu> Wed, 05 September 2001 01:16 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 VAA01702 for <avt-archive@odin.ietf.org>; Tue, 4 Sep 2001 21:16:29 -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 VAA14389; Tue, 4 Sep 2001 21:17:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14358 for <avt@ns.ietf.org>; Tue, 4 Sep 2001 21:17:22 -0400 (EDT)
Received: from purple.nge.isi.edu ([65.114.168.32]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01697 for <avt@ietf.org>; Tue, 4 Sep 2001 21:15:53 -0400 (EDT)
Received: from purple.nge.isi.edu (localhost [127.0.0.1]) by purple.nge.isi.edu (8.9.3/8.9.3) with ESMTP id VAA01306; Tue, 4 Sep 2001 21:17:09 -0400
Message-Id: <200109050117.VAA01306@purple.nge.isi.edu>
To: Randall Gellens <randy@qualcomm.com>
cc: avt@ietf.org
Subject: Re: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.
In-Reply-To: Your message of "Tue, 04 Sep 2001 17:49:06 PDT." <5.1.0.14.0.20010904173339.01e9e308@flagg.qualcomm.com>
Date: Tue, 04 Sep 2001 21:17:09 -0400
From: Colin Perkins <csp@isi.edu>
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
--> Randall Gellens writes: >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. If the codecs are sufficiently similar, it may make sense for the payload formats to be similar. It's possible that they may be identical in some cases (e.g. AMR and AMR-WB use the same format, even though they are different codecs with different MIME types). >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. No! Each codec should have a separate MIME type, otherwise lots of things will break... Colin _______________________________________________ Audio/Video Transport Working Group avt@ietf.org http://www1.ietf.org/mailman/listinfo/avt
- [AVT] Common Format: draft-ietf-avt-evrc-07, draf… Magda
- RE: [AVT] Common Format: draft-ietf-avt-evrc-07, … Adam Li
- Re: [AVT] Common Format: draft-ietf-avt-evrc-07, … Colin Perkins
- Re: [AVT] Common Format: draft-ietf-avt-evrc-07, … Randall Gellens
- Re: [AVT] Common Format: draft-ietf-avt-evrc-07, … Colin Perkins
- RE: [AVT] Common Format: draft-ietf-avt-evrc-07, … Randall Gellens
- RE: [AVT] Common Format: draft-ietf-avt-evrc-07, … Pete McCann
- RE: [AVT] Common Format: draft-ietf-avt-evrc-07, … Randall Gellens
- RE: [AVT] Common Format: draft-ietf-avt-evrc-07, … Eric C. Rosen