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

Magda <magda@qualcomm.com> Thu, 30 August 2001 22:15 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 SAA29106 for <avt-archive@odin.ietf.org>; Thu, 30 Aug 2001 18:15:06 -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 SAA12525; Thu, 30 Aug 2001 18:12:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA12496 for <avt@ns.ietf.org>; Thu, 30 Aug 2001 18:12:29 -0400 (EDT)
Received: from adept.qualcomm.com (adept.qualcomm.com [129.46.64.129]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAB29034 for <avt@ietf.org>; Thu, 30 Aug 2001 18:11:09 -0400 (EDT)
Received: from MLEUCA.qualcomm.com (mleuca.qualcomm.com [129.46.172.82]) by adept.qualcomm.com (8.11.3/8.11.3/1.0) with ESMTP id f7UMCUq10837 for <avt@ietf.org>; Thu, 30 Aug 2001 15:12:30 -0700 (PDT)
Message-Id: <5.1.0.14.2.20010830151146.00a84f38@illyana.qualcomm.com>
X-Sender: mleuca@illyana.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 30 Aug 2001 15:12:23 -0700
To: avt@ietf.org
From: Magda <magda@qualcomm.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_346519338==_.ALT"
Subject: [AVT] Common Format: draft-ietf-avt-evrc-07, draft-mathai-avt-smv-00, Purevoice, etc.
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

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.