[Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-mpls
Lars Eggert <lars.eggert@nokia.com> Thu, 13 September 2007 11:28 UTC
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVmsG-00047y-2p; Thu, 13 Sep 2007 07:28:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IVmsF-00045b-3y for tsvwg-confirm+ok@megatron.ietf.org; Thu, 13 Sep 2007 07:28:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVmsE-00045R-QO; Thu, 13 Sep 2007 07:28:42 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVmsD-0001RE-49; Thu, 13 Sep 2007 07:28:42 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8DBSJcB005729; Thu, 13 Sep 2007 14:28:34 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Sep 2007 14:28:26 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Sep 2007 14:28:26 +0300
Received: from [172.21.39.122] (esdhcp039122.research.nokia.com [172.21.39.122]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8DBSOpr013108; Thu, 13 Sep 2007 14:28:25 +0300
In-Reply-To: <811AD799-26F9-4B21-A673-2F3ABAF4EECD@cisco.com>
References: <46AF4DB6.6000304@ericsson.com> <46DECF4D.9080006@ericsson.com> <4B38544B-D006-4110-90A3-39B13836090C@nokia.com> <811AD799-26F9-4B21-A673-2F3ABAF4EECD@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-126-922297653"; protocol="application/pkcs7-signature"
Message-Id: <71FD3EB9-9BA6-491D-AF8B-28DC349958DA@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Thu, 13 Sep 2007 14:28:14 +0300
To: ext Bruce Davie <bdavie@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 13 Sep 2007 11:28:26.0402 (UTC) FILETIME=[338F0020:01C7F5F9]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: mpls@ietf.org, tsvwg WG <tsvwg@ietf.org>, draft-ietf-tsvwg-ecn-mpls@tools.ietf.org
Subject: [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-mpls
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org
Hi, Bruce, On 2007-9-12, at 17:04, ext Bruce Davie wrote: > Thanks for the comments. Before I respond to them, I wanted to > mention one change that Bob and I want to make in the next revision > in addition to the changes you request. It is just a small point of > clarification, but we don't want to surprise anyone. The proposed > new text, which would appear at the end of Section 6, is included > below: > > We note that in a network where L-LSPs are used, ECN marking SHOULD > NOT cause packets from the same microflow but with different ECN > markings to be sent on different LSPs. As discussed in [RFC3270], > packets of a single microflow should always travel on the same LSP > to avoid possible misordering. Thus, ECN marking of packets on L- > LSPs SHOULD only affect the EXP value of the packets. thanks for the heads-up. This clarification seems fine to me. (I'm cutting things from your reply that I agree with.) > On Sep 11, 2007, at 5:40 AM, Lars Eggert wrote: >> (1) Section 8.3 doesn't really discuss an "example use", which is >> what the title of Section 8 is. Suggest to cut it or move the >> content elsewhere. > > In my mind, section 8.3 is an example of how you can use ECN in > MPLS networks. I think the problem here is that we didn't say > enough to make that apparent. At the same time, I don't really see > any harm in dropping the section. I'd prefer clarifying the example over removing it. If that's doable, great. >> (3) My recollection was that there was an agreement to move the >> discussion of how one would use this to support PCN to an >> appendix. Some of this has happened, but Section 8.4 still exist >> in the main body of the document, and is longer than all the other >> example uses. I suggest to replace the content of Section 8.4 with >> a pointer to the appendix, and move the PCN details there. > > We certainly moved all the protocol details around PCN support to > an appendix as previously agreed. I have no problem moving most of > this section to an appendix too. I'm not saying you should move all of it. Leave a sentence or two in Section 8.4, but move more of the details to the appendix. My basic concern was that there is still a lot of emphasis on the PCN usage example compared to the other ones, which could make it look as if PCN was _the_ intended usage, instead of one possible use case. (I might be nitpicking here. If so, feel free to let me know.) I tagged this as "Revised ID Needed" in the tracker. I fully expect the next revision that fixes these nits to directly go to IETF last call. Lars
- [Tsvwg] WG last call: draft-ietf-tsvwg-ecn-mpls-01 Magnus Westerlund
- Re: [Tsvwg] WG last call: draft-ietf-tsvwg-ecn-mp… Magnus Westerlund
- [Tsvwg] AD review: draft-ietf-tsvwg-ecn-mpls Lars Eggert
- [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-mpls Bruce Davie
- Re: [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-m… James M. Polk
- [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-mpls Lars Eggert
- Re: [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-m… Bob Briscoe
- Re: [Tsvwg] Re: AD review: draft-ietf-tsvwg-ecn-m… Lars Eggert