[RPSEC] I-D Action:draft-ietf-rpsec-bgp-session-sec-req-00.txt

Joe Touch <touch@ISI.EDU> Thu, 13 December 2007 19:27 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2tiG-0005NH-Ps; Thu, 13 Dec 2007 14:27:16 -0500
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1J2tiF-0005JN-Nl for rpsec-confirm+ok@megatron.ietf.org; Thu, 13 Dec 2007 14:27:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2tiF-0005Gn-C3 for rpsec@ietf.org; Thu, 13 Dec 2007 14:27:15 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J2tiD-00065X-R9 for rpsec@ietf.org; Thu, 13 Dec 2007 14:27:15 -0500
Received: from [70.213.233.175] (175.sub-70-213-233.myvzw.com [70.213.233.175]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id lBDJQupl002871; Thu, 13 Dec 2007 11:26:57 -0800 (PST)
Message-ID: <4761877F.6060504@isi.edu>
Date: Thu, 13 Dec 2007 11:26:55 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: rpsec@ietf.org
X-Enigmail-Version: 0.95.5
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [RPSEC] I-D Action:draft-ietf-rpsec-bgp-session-sec-req-00.txt
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1320485052=="
Errors-To: rpsec-bounces@ietf.org

It would be useful to update this doc's discussion of TCP MD5 and its
successors with respect to work in the TCPM WG reported in Vancouver, in
particular:

- there is a newer version of Bellovin's ID

- the TCPM ID on TCP-AO supercedes Ron's and is the intended replacement
to TCP MD5; I believe Ron's has been withdrawn at this point

Joe

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec