Re: [tcpm] status of TCP-MD5 after TCP-AO publication
Iljitsch van Beijnum <iljitsch@muada.com> Tue, 04 August 2009 15:56 UTC
Return-Path: <iljitsch@muada.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 798233A6828; Tue, 4 Aug 2009 08:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.328
X-Spam-Level:
X-Spam-Status: No, score=-6.328 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hwnfGuDYceg; Tue, 4 Aug 2009 08:56:15 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 8F6113A67E7; Tue, 4 Aug 2009 08:56:15 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.55]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n74FtsZD043640 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Aug 2009 17:55:54 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <75E968CA-1D9A-40BD-9C3E-534518B13BCF@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Ron Bonica <rbonica@juniper.net>
In-Reply-To: <4A777220.3070507@juniper.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 04 Aug 2009 17:56:11 +0200
References: <6BB76CFA-4134-4D3E-BE20-3A90A5111CBD@nokia.com> <FB33B8FD-308B-4867-902E-131382969C35@muada.com> <4A777220.3070507@juniper.net>
X-Mailer: Apple Mail (2.935.3)
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
Subject: Re: [tcpm] status of TCP-MD5 after TCP-AO publication
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 15:56:16 -0000
On 4 aug 2009, at 1:26, Ron Bonica wrote: > The HISTORIC nomenclature doesn't mean that there is no longer an > installed base. It just means that something more recent is available. I still think it's premature to change the status of RFC 2385 before a replacement is widely available operationally. And yes, that can take a decade, see 32-bit AS numbers. Iljitsch
- [tcpm] status of TCP-MD5 after TCP-AO publication Lars Eggert
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Iljitsch van Beijnum
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Lars Eggert
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… David Borman
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Joe Touch
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Ron Bonica
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Iljitsch van Beijnum
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Smith, Donald
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Joe Touch
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Chaks Chigurupati (chaks)
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Smith, Donald
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Chaks Chigurupati (chaks)
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… toby.moncaster
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Iljitsch van Beijnum
- Re: [tcpm] status of TCP-MD5 after TCP-AO publica… Pekka Savola