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

"Adam Li" <adamli@icsl.ucla.edu> Fri, 31 August 2001 02:09 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 WAA03119 for <avt-archive@odin.ietf.org>; Thu, 30 Aug 2001 22:09:35 -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 WAA18456; Thu, 30 Aug 2001 22:10:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA18424 for <avt@ns.ietf.org>; Thu, 30 Aug 2001 22:09:58 -0400 (EDT)
Received: from icsl.icsl.ucla.edu (icsl.ICSL.UCLA.EDU [128.97.90.20]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03110 for <avt@ietf.org>; Thu, 30 Aug 2001 22:08:37 -0400 (EDT)
Received: from scope (PC168.ICSL.UCLA.EDU [128.97.90.168]) by icsl.icsl.ucla.edu (8.8.8+Sun/8.8.8(ICSL0003)) with SMTP id TAA08646; Thu, 30 Aug 2001 19:09:52 -0700 (PDT)
From: Adam Li <adamli@icsl.ucla.edu>
To: Magda <magda@qualcomm.com>, avt@ietf.org
Subject: RE: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.
Date: Thu, 30 Aug 2001 19:10:07 -0700
Message-ID: <NEBBLMIKILMNOPFCPHHFMEIDCLAA.adamli@icsl.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <5.1.0.14.2.20010830151146.00a84f38@illyana.qualcomm.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Hi,

I suppose it would not be too hard to have a common format that works for
both EVRC and SMV. There is nothing in the current draft that is codec
specific which would prevent this. It does reduce the complexities of
protocols and implemenation. I am not sure if it is allright to design one
common RTP payload format for more than one codec. Have there been any such
case before? Are there any special issues need to pay additional attention
to?

Although based on RFC 2658 (for PureVoice), the current EVRC draft has some
significant difference from it already. There is an addition packet type, to
name one. Including the PureVoice in this draft may imply obsoleting RFC
2658 and possibly the devices that have implemented it. Maybe the Chairs and
Kyle (who authored RFC 2658, and is also an author for the EVRC draft) can
give us some more suggestion on what should we do.

Thanks,

Adam


----------
Adam H. Li
Image Communication Lab                    (310) 825-5178 (Lab)
University of California, Los Angeles      (310) 825-7928 (Fax)


-----Original Message-----
From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Magda
Sent: Thursday, August 30, 2001 3:12 PM
To: avt@ietf.org
Subject: [AVT] Common Format: draft-ietf-avt-evrc-07,
draft-mathai-avt-smv-00, Purevoice, etc.



There's been some discussion on a number of issues with the
draft-ietf-avt-evrc-07. Also the SMV RTP proposal (draft-mathai-avt-smv-00)
is up for discussion. The SMV proposal is very similar to the EVRC RTP
proposal.

Given the similarities between the EVRC and SMV proposals with each other
and also prior drafts (such as PureVoice), perhaps it would be useful to
develop a more generic RTP payload format capable of supporting any of these
vocoders.

By eliminating small differences between the formats, implementation
complexity is reduced, while the common format is capable of supporting both
EVRC and SMV (and likely PureVoice) as well as future vocoders.

-- magda.


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