Re: [IPsec] normative references to IANA registries

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 31 July 2017 20:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBB31327B2 for <ipsec@ietfa.amsl.com>; Mon, 31 Jul 2017 13:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaA5K4cbWtyq for <ipsec@ietfa.amsl.com>; Mon, 31 Jul 2017 13:09:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61491131CA0 for <ipsec@ietf.org>; Mon, 31 Jul 2017 13:09:37 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4D82DE200 for <ipsec@ietf.org>; Mon, 31 Jul 2017 16:11:22 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A72CF80243 for <ipsec@ietf.org>; Mon, 31 Jul 2017 16:09:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: ipsec@ietf.org
In-Reply-To: <523.1501530916@obiwan.sandelman.ca>
References: <523.1501530916@obiwan.sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 31 Jul 2017 16:09:36 -0400
Message-ID: <4018.1501531776@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/nw8cOoXMe_c5gUIH_kT6LLM-R6Y>
Subject: Re: [IPsec] normative references to IANA registries
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 31 Jul 2017 20:09:39 -0000

I meant to CC ipsec@, but I'm not sure I actually succeeded.
My email to ietf@ietf.org was really about doing this kind of thing in
general, and having reference.*.xml files for the registries to make
this easy.

I noticed that actually in rfc7296, we actually have a reference:

https://tools.ietf.org/html/rfc7296#ref-IKEV2IANA
   [IKEV2IANA]
         IANA, "Internet Key Exchange Version 2 (IKEv2)  Parameters",
         <http://www.iana.org/assignments/ikev2-parameters/>.

I wonder if adding such a reference (or references with #anchors) would be an
acceptable AUTH48 addition.
    https://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xhtml#ikev2-parameters-6

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > I'm implementing draft-ietf-ipsecme-rfc4307bis.
    > It basically sets MUST/SHOULD/etc. values for various algorithms. The IPsec(ME)
    > WG updates things as the world evolves.

    > "References to the specification
    > defining these algorithms are in the IANA registry."

    > It would be nice if it gave the actual name of the Registry.
    > But, I think in this hyperlinked internet, it really should reference the
    > registry itself directly.

    > So I wonder out loud: shouldn't all of the IANA registries have clear
    > reference files that could be normatively referenced?

    > --
    > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
    > -= IPv6 IoT consulting =-





--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-