Re: [AVT] Re: Clearmode definition.

Colin Perkins <csp@csperkins.org> Fri, 26 March 2004 12:47 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 HAA17282 for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 07:47:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6qk0-0001RZ-Ir for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:17 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QClGsE005539 for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 07:47:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6qjl-0001PS-5w; Fri, 26 Mar 2004 07:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6pwY-0006Xr-6M for avt@optimus.ietf.org; Fri, 26 Mar 2004 06:56:11 -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 GAA14950 for <avt@ietf.org>; Fri, 26 Mar 2004 06:56:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6pwT-0000p5-00 for avt@ietf.org; Fri, 26 Mar 2004 06:56:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6pvb-0000jg-00 for avt@ietf.org; Fri, 26 Mar 2004 06:55:11 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 1B6pux-0000cj-00 for avt@ietf.org; Fri, 26 Mar 2004 06:54:31 -0500
Received: from pub-243.nesc.ed.ac.uk ([129.215.30.243]:2339 helo=mangole.dcs.gla.ac.uk) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.04) id 1B6puK-0007Ri-00; Fri, 26 Mar 2004 11:53:52 +0000
Date: Fri, 26 Mar 2004 11:02:38 +0000
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar@cisco.com>
Cc: rkumar999@comcast.net, yaakov_s@rad.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040326110238.5e8aeba2.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
References: <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net> <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net> <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co.il> <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net> <4.3.2.7.2.20040323080205.02475ab8@mail.comcast.net> <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

--> Rajesh Kumar <rkumar@cisco.com> writes:
> At 04:11 PM 3/23/2004 +0000, Colin Perkins wrote:
> >--> Rajesh Kumar <rkumar999@comcast.net> writes:
> > > At 03:42 PM 3/23/2004 +0000, Colin Perkins wrote:
> > > >What would be the use case for having the MIME type registered? I've
> > > >not heard a reason why the mechanisms being developed in PWE3 are
> > > >insufficient.
> > >
> > > Say you set up an 384 kbps call via SIP for your video. You do not
> > > use the relevant video MIME because what gets put in RTP is nx64 and
> > > the video/audio is one step removed.
> > >
> > > You may not want to proliferate signaling in your network.
> >
> >Again, what is the application scenario? Why the need to signal Nx64
> >kbps clearmode, rather than the appropriate video format?
> 
> Because in this case you would encapsulate a 384 kbps clear channel in
> RTP. The video and other streams would be within this Nx64 container.

Right - you have a pseudo-wire emulation, running multiple streams within
the pseudo-wire. This would seem to be a typical application for the PWE3
mechanisms, rather than something AVT should consider. 

-- 
Colin Perkins
http://csperkins.org/

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