Re: [AVT] Re: Clearmode definition.

Rajesh Kumar <rkumar999@comcast.net> Fri, 26 March 2004 16:44 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 LAA00707 for <avt-archive@odin.ietf.org>; Fri, 26 Mar 2004 11:44:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6uRI-0007fc-EZ for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:44:13 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QGiCOB029456 for avt-archive@odin.ietf.org; Fri, 26 Mar 2004 11:44:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6uR7-0007cH-6r; Fri, 26 Mar 2004 11:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6uQC-0007XN-GD for avt@optimus.ietf.org; Fri, 26 Mar 2004 11:43:04 -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 LAA00607 for <avt@ietf.org>; Fri, 26 Mar 2004 11:43:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6uQB-00024t-00 for avt@ietf.org; Fri, 26 Mar 2004 11:43:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6uPH-00021h-00 for avt@ietf.org; Fri, 26 Mar 2004 11:42:07 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1B6uOP-0001wh-00 for avt@ietf.org; Fri, 26 Mar 2004 11:41:13 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 26 Mar 2004 08:40:47 -0800
Received: from rkumar-w2k01.cisco.com (sjc-vpn2-785.cisco.com [10.21.115.17]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2QGedex011277; Fri, 26 Mar 2004 08:40:40 -0800 (PST)
Message-Id: <4.3.2.7.2.20040326083424.0267af00@vtg-um-e2k1.cisco.com>
X-Sender: rkumar999@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 26 Mar 2004 08:40:38 -0800
To: Colin Perkins <csp@csperkins.org>
From: Rajesh Kumar <rkumar999@comcast.net>
Subject: Re: [AVT] Re: Clearmode definition.
Cc: rkumar@cisco.com, yaakov_s@rad.com, avt@ietf.org
In-Reply-To: <20040326110238.5e8aeba2.csp@csperkins.org>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS autolearn=no version=2.60
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>

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. 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.

Rajesh



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