[AVT] RE: Clearmode definition.

Kreuter Ruediger <ruediger.kreuter@siemens.com> Fri, 19 March 2004 11:53 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28073 for <avt-archive@odin.ietf.org>; Fri, 19 Mar 2004 06:53:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4IYi-0002bv-1X for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:53:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JBr4RF010034 for avt-archive@odin.ietf.org; Fri, 19 Mar 2004 06:53:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4IYf-0002bI-S2; Fri, 19 Mar 2004 06:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4IYI-0002aj-RX for avt@optimus.ietf.org; Fri, 19 Mar 2004 06:52:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28049 for <avt@ietf.org>; Fri, 19 Mar 2004 06:52:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4IYD-0000Mw-00 for avt@ietf.org; Fri, 19 Mar 2004 06:52:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B4IX0-0000GK-00 for avt@ietf.org; Fri, 19 Mar 2004 06:51:21 -0500
Received: from david.siemens.de ([192.35.17.14]) by ietf-mx with esmtp (Exim 4.12) id 1B4IVx-0000Ae-00 for avt@ietf.org; Fri, 19 Mar 2004 06:50:13 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.7/8.11.7) with ESMTP id i2JBo4E27473; Fri, 19 Mar 2004 12:50:04 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id i2JBo3V22577; Fri, 19 Mar 2004 12:50:03 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id <FF52RAT5>; Fri, 19 Mar 2004 12:49:18 +0100
Message-ID: <BB70B8DDF080D511AFB50003474B8D390168ED7F@MCHP9GRAS>
From: Kreuter Ruediger <ruediger.kreuter@siemens.com>
To: 'Rajesh Kumar' <rkumar@cisco.com>
Cc: avt@ietf.org, Colin Perkins <csp@csperkins.org>, magnus.westerlund@ericsson.com, dea@cisco.com, hisham@cisco.com, rbiskner@cisco.com, miriyala@cisco.com
Date: Fri, 19 Mar 2004 12:48:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
Subject: [AVT] RE: Clearmode definition.
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>

I introduced Nx64kbit/s into one of the early
versions of the Clearmode draft, to open a 
discussion about this issue (after an according
request in the AVT mailing list).
In response we had a discussion about this issue
in AVT and PWE3 and finaly decided to reduce
the Clearmode draft to 1X64kbit/s - for several
reasons.

1)
There were several drafts to this time 
dealing with Nx64kbit/s and PWE3 was in the 
process to harmonize them into one. We didn't 
want to come up with an additional approach.

2)
Just introducing a parameter N for Nx64kbit/s
is not enough. For N>1 you must describe how
the channels are packed in the RTP packet.
And there are several alternatives.
Additionally other information is needed.

There was a controverse discussion in PWE3
which leaded to reason
3)
When we discussed this issue with PWE3, it
became clear that the Nx64kbit/s would need
much more time to finish then a pure
Clearmode draft and we wanted to speed up
the MIME type registration for Clearmode.


So I agree with Colin, that we leave Nx64kbit
the the PWE3 group.

Regards, Ruediger





> -----Original Message-----
> From: Rajesh Kumar [mailto:rkumar@cisco.com] 
> Sent: Thursday, March 18, 2004 9:18 PM
> To: Colin Perkins
> Cc: Kreuter Ruediger; avt@ietf.org; 
> magnus.westerlund@ericsson.com; dea@cisco.com; 
> hisham@cisco.com; rbiskner@cisco.com; miriyala@cisco.com
> Subject: Re: Clearmode definition.
> 
> 
> At 08:12 PM 3/18/2004 +0000, Colin Perkins wrote:
> >--> Rajesh Kumar <rkumar@cisco.com> writes:
> > > Are there plans to address N x 64 clear mode (N > 1) in 
> > > draft-ietf-avt-rtp-clearmode-04.txt ?
> > >
> > > One method might be to have N as a MIME parameter.
> > >
> > > I recommend that we do.
> >
> >No. This is explicitly out of scope of AVT, and will be addressed in 
> >the PWE3 working group.
> 
> I do not understand why 64 kbps clearmode is any different 
> from 384 kbps. 
> Both can be negotiated codecs for a session type. N x 64 should be 
> negotiable session by session and not just relegated to the 
> provisioned 
> tunnel category. I recommend a MIME definition for it if you 
> do not want to 
> fold it into the MIME for 64 kbps clear mode, although I 
> would prefer the 
> latter.
> 
> 
> 
> >--
> >Colin Perkins
> >http://csperkins.org/
> 

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