RE: [AVT] Re: Clearmode definition.

Rajesh Kumar <rkumar999@comcast.net> Tue, 23 March 2004 15:40 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 KAA04217 for <avt-archive@odin.ietf.org>; Tue, 23 Mar 2004 10:40:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5o0Q-0007kN-Dz for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:39:58 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NFds6a029778 for avt-archive@odin.ietf.org; Tue, 23 Mar 2004 10:39:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5nyT-00079R-B9; Tue, 23 Mar 2004 10:37:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5nxP-00072c-E1 for avt@optimus.ietf.org; Tue, 23 Mar 2004 10:36:47 -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 KAA04074 for <avt@ietf.org>; Tue, 23 Mar 2004 10:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B5nxI-0003cP-00 for avt@ietf.org; Tue, 23 Mar 2004 10:36:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B5nwZ-0003Ty-00 for avt@ietf.org; Tue, 23 Mar 2004 10:35:56 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1B5nvf-0003ED-00 for avt@ietf.org; Tue, 23 Mar 2004 10:34:59 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 23 Mar 2004 07:34:45 -0800
Received: from rkumar-w2k01.cisco.com (sjc-vpn4-814.cisco.com [10.21.83.45]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2NFYO8Q019471; Tue, 23 Mar 2004 07:34:25 -0800 (PST)
Message-Id: <4.3.2.7.2.20040323073131.024fff00@mail.comcast.net>
X-Sender: rkumar999@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 23 Mar 2004 07:34:24 -0800
To: Yaakov Stein <yaakov_s@rad.com>
From: Rajesh Kumar <rkumar999@comcast.net>
Subject: RE: [AVT] Re: Clearmode definition.
Cc: Rajesh Kumar <rkumar@cisco.com>, Colin Perkins <csp@csperkins.org>, avt@ietf.org
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52024E9E6E@exrad2.ad.rad.co. il>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_308128244==_.ALT"
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=FROM_ENDS_IN_NUMS, HTML_MESSAGE 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>

Yaakov,

At 01:36 PM 3/23/2004 +0200, Yaakov Stein wrote:
>
> > Yaakov,
> > One of the cases you mention include an RTP encapsulation of
> > Nx64. Unless you have already done so, I recommend you
> > register a MIME for it and allow its session-by-session
> > negotiation using SDP, H.245 or other means. My guess from
> > having read the PWE3 drafts in the past is that you are
> > limiting the application to a provisioned RTP Nx64 session.
> > While that is adequate in some applications, others will
> > require/prefer the signaled establishment of Nx64 sessions.
>
>Rajesh,
>
>Since this is a PW protocol, it works in the PWE fashion.
>Either the PW is manually provisioned, or it is set up
>using the PW control protocol.
>
>In either case it is not envisioned that this connection
>will be set-up and torn-down on a "session per session" basis,
>just as a T1 or E1 is not torn-down after a phone conversation.
>
>This is another difference between what we are doing in PWE3,
>and the typical AVT method of working.
>
>The point of my previous email was that even if it is decided
>that PWE is a proper place to standardize methods for
>transport of N*64 flows over IP, their treatment at PWE3
>may not be what you are looking for.
>
>In particular, MIME types and use of SDP are entirely
>alien to the PWE3 way of doing things.
>
>Hence if you have a need for an RTP encapsulation of N*64k,
>I would suggest that the AVT WG look into it,
>trying to keep the encapsulation compatible with the
>appropriate PWE draft.

This is what I requested from the AVT group but they indicated I go to the 
PWE3 group for it. However, if, between the two groups, we think that a 
MIME for nx64 over RTP will not be widely useful, then we can drop it. 
Registration of vendor-specific MIMEs is also possible, but is this the way 
we want to go? Either way, I would like us in AVT and PWE3 to make a 
conscious choice.

Rajesh


>Y(J)S
>
>_______________________________________________
>Audio/Video Transport Working Group
>avt@ietf.org
>https://www1.ietf.org/mailman/listinfo/avt