[AVT] RE: I-D ACTION:draft-ash-avt-ecrtp-over-mpls-protocol-00.txt

"Ash, Gerald R (Jerry), ALABS" <gash@att.com> Tue, 10 February 2004 14:30 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 JAA19779 for <avt-archive@odin.ietf.org>; Tue, 10 Feb 2004 09:30:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqYtz-0006Mt-6o for avt-archive@odin.ietf.org; Tue, 10 Feb 2004 09:30:15 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1AEUFns024428 for avt-archive@odin.ietf.org; Tue, 10 Feb 2004 09:30:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqYtm-0006LF-Vc; Tue, 10 Feb 2004 09:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqYte-0006Ki-A9 for avt@optimus.ietf.org; Tue, 10 Feb 2004 09:29:54 -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 JAA19768 for <avt@ietf.org>; Tue, 10 Feb 2004 09:29:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqYtc-0005OO-00 for avt@ietf.org; Tue, 10 Feb 2004 09:29:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqYse-0005JM-00 for avt@ietf.org; Tue, 10 Feb 2004 09:28:52 -0500
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 1AqYsC-0005Ej-00 for avt@ietf.org; Tue, 10 Feb 2004 09:28:24 -0500
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id i1AEH7qV022253 for <avt@ietf.org>; Tue, 10 Feb 2004 08:27:54 -0600
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 40169495007D448A; Tue, 10 Feb 2004 09:27:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Feb 2004 08:27:54 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA02BA38E3@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
Thread-Index: AcPvKhdGaEmd/bjJQ4yVbbCc67m3RAAtkjhg
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: curtis@fictitious.org
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, avt@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] RE: I-D ACTION:draft-ash-avt-ecrtp-over-mpls-protocol-00.txt
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: quoted-printable

Curtis,

> > Please review and comment on 'Protocol Extensions for ECRTP over MPLS'
> > http://www.ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-00.txt 
> > The protocol extensions enable the use of MPLS to route enhanced compressed 
> > RTP (ECRTP) compressed packets over an MPLS LSP without 
> > compression/decompression cycles at each router.
> > 
> > The proposed extensions are based on the requirements documented in 
> > 'Requirements for ECRTP over MPLS' 
> > http://www.ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-reqs-01.txt.
> > 
> > Thanks,
> > Jerry

> Jerry,
> 
> This looks to be a very good direction to go in.

Thanks Curtis!

> In your encapsulations you should make sure to avoid any values in the
> first byte that could be mistaken as IPv4 or IPv6 or any of the
> encapsulations being worked on by those working on VPN and PW.  See
> "The PWE3 Control Word", Jonathan Stein, 22-Oct-02,
> draft-stein-pwe3-controlword-00.txt, for some early discussion on
> that.  Note though that "Payload Type" is something that many
> providers require so that multipath can be used on IP traffic which
> constitutes the majority of traffic yet reordering is avoided for
> traffic which cannot be split based on what appears to be an IP header
> and the IP src/dst pair.
> 
> It might be best to reserve a single fixed first byte for the "Packet
> Type" (and I suggest you make up a name for this shim such as
> SCID_Packet_Type) and use the second byte for the packet types that
> you have defined.  Just as you have to get numbers for SCID_Request
> Object and Header_Compression_Reply Object from IANA, you'll have to
> coordinate with others over this number space, though it is less clear
> if IANA is the authority on this quite yet.

All good suggestions, will incorporate in the next Rev.

Thanks a lot for your careful review,
Jerry

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