Re: [tcpm] RE: TCP secure

Joe Touch <touch@isi.edu> Fri, 11 January 2008 03:29 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDAaa-0003pm-V5; Thu, 10 Jan 2008 22:29:48 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1JDAaa-0003ph-Bn for tcpm-confirm+ok@megatron.ietf.org; Thu, 10 Jan 2008 22:29:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDAaa-0003pZ-29 for tcpm@ietf.org; Thu, 10 Jan 2008 22:29:48 -0500
Received: from usfws1.systemmetrics.com ([66.135.227.114] helo=vbn.0059755.lodgenet.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDAaY-0004Pf-La for tcpm@ietf.org; Thu, 10 Jan 2008 22:29:48 -0500
Received: from [10.2.5.165] (helo=[10.2.5.165]) by vbn.0059755.lodgenet.net with esmtp (Exim 3.34 #1) id 1JDAaQ-0000Gn-00; Thu, 10 Jan 2008 17:29:38 -1000
Message-ID: <4786E29B.7060608@isi.edu>
Date: Thu, 10 Jan 2008 19:29:31 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Alfred_=3F?= <ah@tr-sys.de>
Subject: Re: [tcpm] RE: TCP secure
References: <200801110208.DAA11330@TR-Sys.de>
In-Reply-To: <200801110208.DAA11330@TR-Sys.de>
X-Enigmail-Version: 0.95.6
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: tcpm@ietf.org, rrs@cisco.com, mdalal@cisco.com, ananth@cisco.com
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1040780268=="
Errors-To: tcpm-bounces@ietf.org

The references continue to be out of date.

1. antispoof has been an RFC (4953) since July.

2. TCP-MD5 has a replacement (TCP-AO) that was discussed in Nov in 
Vancouver; that I-D should be noted, esp. where TCP-MD5 is discussed as 
an alternate solution.

Joe

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