Re: secdir review of draft-ietf-tsvwg-ecn-mpls-02.txt

Tom Yu <tlyu@MIT.EDU> Tue, 23 October 2007 06:07 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 1IkCv9-0003jn-6A; Tue, 23 Oct 2007 02:07:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkCv4-0003gj-I5 for ietf@ietf.org; Tue, 23 Oct 2007 02:07:14 -0400
Received: from biscayne-one-station.mit.edu ([18.7.7.80]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IkCv4-0004il-8R for ietf@ietf.org; Tue, 23 Oct 2007 02:07:14 -0400
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id l9N66HVG021789; Tue, 23 Oct 2007 02:06:25 -0400 (EDT)
Received: from cathode-dark-space.mit.edu (CATHODE-DARK-SPACE.MIT.EDU [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id l9N665kR001222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Oct 2007 02:06:06 -0400 (EDT)
Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9.20060308) id l9N6650m006728; Tue, 23 Oct 2007 02:06:05 -0400 (EDT)
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <5.2.1.1.2.20071019165431.018d18c8@pop3.jungle.bt.co.uk>
From: Tom Yu <tlyu@MIT.EDU>
Date: Tue, 23 Oct 2007 02:06:05 -0400
In-Reply-To: <5.2.1.1.2.20071019165431.018d18c8@pop3.jungle.bt.co.uk> (Bob Briscoe's message of "Fri, 19 Oct 2007 17:41:46 +0100")
Message-ID: <ldvejfmjrg2.fsf@cathode-dark-space.mit.edu>
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Scanned-By: MIMEDefang 2.42
X-Spam-Flag: NO
X-Spam-Score: 0.00
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: secdir@mit.edu, ietf@ietf.org, bsd@cisco.com, tsvwg-chairs@tools.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>
Errors-To: ietf-bounces@ietf.org

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