Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt
Lars Eggert <lars.eggert@nokia.com> Wed, 24 October 2007 14:36 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkhLG-0000jW-ET; Wed, 24 Oct 2007 10:36:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkhLE-0000jP-A4 for ietf@ietf.org; Wed, 24 Oct 2007 10:36:16 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkhLD-0006hJ-OB for ietf@ietf.org; Wed, 24 Oct 2007 10:36:16 -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 l9OEa8fo011892; Wed, 24 Oct 2007 17:36:11 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Oct 2007 17:35:11 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh103.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Oct 2007 17:35:10 +0300
Received: from [172.21.34.120] (esdhcp034120.research.nokia.com [172.21.34.120]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l9OEZ65r025305; Wed, 24 Oct 2007 17:35:09 +0300
In-Reply-To: <ldvejfmjrg2.fsf@cathode-dark-space.mit.edu>
References: <5.2.1.1.2.20071019165431.018d18c8@pop3.jungle.bt.co.uk> <ldvejfmjrg2.fsf@cathode-dark-space.mit.edu>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <08E0F075-B798-4224-A689-8BB1CCE657AD@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Date: Wed, 24 Oct 2007 17:35:03 +0300
To: ext Tom Yu <tlyu@MIT.EDU>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 24 Oct 2007 14:35:10.0497 (UTC) FILETIME=[14A7F910:01C8164B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: Bob Briscoe <rbriscoe@jungle.bt.co.uk>, tsvwg-chairs@tools.ietf.org, secdir@MIT.EDU, bsd@cisco.com, ietf@ietf.org
Subject: Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1438152484=="
Errors-To: ietf-bounces@ietf.org
Authors, if you want to change the draft based on the sec-dir or gen-art reviews, please let me know and either send me a corresponding RFC Editor Note or tell me that you're submitting a new draft. Lars On 2007-10-23, at 9:06, ext Tom Yu wrote: >>>>>> "Bob" == Bob Briscoe <rbriscoe@jungle.bt.co.uk> writes: > > Bob> Tom, > Bob> You're analysis of the impact on the ECN nonce is accurate. > Below is > Bob> our reasoning for not including the ECN nonce capability in this > Bob> proposal... > > [...] > > Thanks for the detailed rationale of your decision to not include the > ECN nonce. Given that the question of detecting disruption of > end-to-end ECN signaling within an MPLS domain occurred to me from the > mention of RFC3540 in the Security Considerations, other readers of > this document may have similar questions. I suggest that you add a > sentence or two to the Security Considerations summarizing your > decision to exclude the ECN nonce capability from this particular > proposal. However, I will not object to the passage of this document > if you choose not to include such a summary. > > ---Tom
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf