Re: [IPsec] #123: Proposal to remove the IANA tables from IKEv2bis

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 24 November 2009 01:46 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43ED528C1C6 for <ipsec@core3.amsl.com>; Mon, 23 Nov 2009 17:46:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.971
X-Spam-Level:
X-Spam-Status: No, score=-5.971 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 NH8Ma2zmQ2kW for <ipsec@core3.amsl.com>; Mon, 23 Nov 2009 17:46:19 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 85C8B3A6AE9 for <ipsec@ietf.org>; Mon, 23 Nov 2009 17:46:19 -0800 (PST)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nAO1kDh1047458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Nov 2009 18:46:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240852c730eb0a0054@[10.20.30.158]>
In-Reply-To: <20091124013732.GD3457@mactavish>
References: <p06240847c730db1c447f@[10.20.30.158]> <20091124011228.GC3457@mactavish> <p0624084fc730e6cf0252@[10.20.30.158]> <20091124013732.GD3457@mactavish>
Date: Mon, 23 Nov 2009 17:46:12 -0800
To: Dan McDonald <danmcd@sun.com>, ipsec@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [IPsec] #123: Proposal to remove the IANA tables from IKEv2bis
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 01:46:20 -0000

At 8:37 PM -0500 11/23/09, Dan McDonald wrote:
>On Mon, Nov 23, 2009 at 05:27:36PM -0800, Paul Hoffman wrote:
>> >Can you move 'em to an appendix, with a permanent URL reference to the IANA
>> >up-to-date versions?
>>
>> As long as you mean "an appendix that clearly says 'these were in RFC 4306
>> but are now out-of-date but are here just for reference and you want to
>> look at <URL>'", I'm OK with that as well.
>
>I'd actually go one better -- snapshot what's on IANA today (or the day
>before RFC-editor pulls the switch) with the warning you quote ('... just
>for reference and you want to look at <URL>').  The warning and URL is the
>critical part.

Oh, yuck. No. I could see doing this to keep the "bis" nature of the document intact by providing the old tables, but not creating a clone of the IANA registry. I *really* don't think it is that hard for a developer to resolve a URL and read the tables there.

--Paul Hoffman, Director
--VPN Consortium