Re: [AVT] Re: Clearmode definition.
Colin Perkins <csp@csperkins.org> Mon, 29 March 2004 08: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 DAA18969 for <avt-archive@odin.ietf.org>; Mon, 29 Mar 2004 03:47:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B7sQJ-00036U-24 for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 03:47:11 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T8lB2D011924 for avt-archive@odin.ietf.org; Mon, 29 Mar 2004 03:47:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B7sQ9-000336-EZ; Mon, 29 Mar 2004 03: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 1B7s5y-0008Gg-Jy for avt@optimus.ietf.org; Mon, 29 Mar 2004 03:26: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 DAA18058 for <avt@ietf.org>; Mon, 29 Mar 2004 03:26:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B7s5w-00051V-00 for avt@ietf.org; Mon, 29 Mar 2004 03:26:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B7s4y-0004ta-00 for avt@ietf.org; Mon, 29 Mar 2004 03:25:09 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 1B7s41-0004fk-00 for avt@ietf.org; Mon, 29 Mar 2004 03:24:09 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:63511 helo=mangole.dcs.gla.ac.uk) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.04) id 1B7s3L-0002iD-00; Mon, 29 Mar 2004 09:23:29 +0100
Date: Mon, 29 Mar 2004 09:24:18 +0100
From: Colin Perkins <csp@csperkins.org>
To: Rajesh Kumar <rkumar999@comcast.net>
Cc: rkumar@cisco.com, yaakov_s@rad.com, avt@ietf.org
Subject: Re: [AVT] Re: Clearmode definition.
Message-Id: <20040329092418.651fe50b.csp@csperkins.org>
In-Reply-To: <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
References: <4.3.2.7.2.20040323082359.02513448@vtg-um-e2k1.cisco.com> <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> <4.3.2.7.2.20040326083424.0267af00@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.6 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 <rkumar999@comcast.net> writes: > At 11:02 AM 3/26/2004 +0000, Colin Perkins wrote: > > >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. > > In some applications, this places a demand for two, not one, signaling > mechanisms at the multimedia endpoints for RTP media e.g. SIP and PWE3 > control. These are applications where it might set up nx64 sessions and > other (not necessarily simultaneous) sessions outside the pseudo-wire. > > Perhaps, the PWE3 group should MIME this RTP media so that SIP and H.248 > can be used for setting up nx64 sessions. Is that sufficient? You don't need to signal anything about the contents of the pseudo-wire? Before proposing solutions, what are your requirements? > However, if there is no > wide-spread demand for the SIP or H.248 signaling of the nx64 codec, the > vendors may define their proprietary MIMEs in the 'vnd' tree. Or, perhaps, the vendors should work with PWE3 to define an appropriate signalling mechanism (be that using SIP or otherwise)? -- Colin Perkins http://csperkins.org/ _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] RE: Clearmode definition. Kreuter Ruediger
- RE: [AVT] Re: Clearmode definition. Yaakov Stein
- RE: [AVT] Re: Clearmode definition. Rajesh Kumar
- RE: [AVT] Re: Clearmode definition. Yaakov Stein
- RE: [AVT] Re: Clearmode definition. Rajesh Kumar
- Re: [AVT] Re: Clearmode definition. Colin Perkins
- Re: [AVT] Re: Clearmode definition. Colin Perkins
- Re: [AVT] Re: Clearmode definition. Colin Perkins
- Re: [AVT] Re: Clearmode definition. Rajesh Kumar
- Re: [AVT] Re: Clearmode definition. Colin Perkins
- Re: [AVT] Re: Clearmode definition. Christian Groves