IETF Logo Mail Archive

Re: [rfc-i] Referencing IANA registries

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 17 December 2016 00:23 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3BD71294A2 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.984
X-Spam-Level:
X-Spam-Status: No, score=-6.984 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=gmail.com
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 Pg59CPWKptNi for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:23:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D2511293F2 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Dec 2016 16:23:20 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EAF95B808CA; Fri, 16 Dec 2016 16:23:19 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id BD896B808CA for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1J7-UhjkHPGd for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:23:17 -0800 (PST)
Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) by rfc-editor.org (Postfix) with ESMTPS id 704EEB808C9 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:23:17 -0800 (PST)
Received: by mail-pg0-x242.google.com with SMTP id p66so11179792pga.2 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:23:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=tvu8YvwjWEd6wMi5ylBMu+Fm2lg7nKXX4M5en1H81QE=; b=MfeDKpy04d1WioqGcdrsC1P+UFYLtsOFAbXCrzZNNKjKTEhXpuGZVi7egflgCgMVv8 63m7cBEOgweGJ7W3qA9Mi5OjyoEHAFKUUrsGt/PmnKdsLIJMEej1K5BjjMnzil7BMdjc ElLLWCppRXpsOeMnF7QGY8XOAJEfSCtE4SHZz95jtTBLYXXPz5PvCsjFelwmYamCjMSs WSmRCRpjt4rlSKga+qGRVoR88B0BSiDQKKPnpKvEXpwAjPKEbNh9JJYoT4WmftQz1yew TvJPM3/fuoH7yJKlJEOG2vwIK1bViI7JJvcm1OzQHMkf3LdoJEHFvdJIGHNGb1u2CTjq B+Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=tvu8YvwjWEd6wMi5ylBMu+Fm2lg7nKXX4M5en1H81QE=; b=bIMjtYBfw7dZ+iE9Q2An3cGWCd04sMrTuf5EFjC1uJW4PPin7BPtLyT66hN0yEOZgL +fkuaFyKmjzZ+VZeiV979HE7guptQ7zxgtRClrVWsc0/v7T0q0f7lieebtFDFVhFtjiP T3EkjC/ht9ru4y446k8jEIyrs1Vfo3cExppj2o6uJ9ky5Trg3YtSmD6Mc6QEZVuZiaAy cZix+s17ZkRLb++ujgQa4npDHQUu4NQMP0nD/aQl1dnPl5BO/aVeTpgDYSU9kr/Va/bG z9sMCQmzC7Vl9l44oPptmekGahTwoBL9l/u5BSFxsoO/W4iRcTk2uZaK18fA0+XjdpN2 4YWQ==
X-Gm-Message-State: AKaTC01+m1uahABAl9VR4tzOFO/n8G2MNAyw3mnv2xnldN9EnsI/GrUaItcrhJIlDKk5mQ==
X-Received: by 10.98.75.11 with SMTP id y11mr5629947pfa.30.1481934197012; Fri, 16 Dec 2016 16:23:17 -0800 (PST)
Received: from [192.168.178.27] ([118.148.120.5]) by smtp.gmail.com with ESMTPSA id a66sm12313946pfa.64.2016.12.16.16.23.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Dec 2016 16:23:16 -0800 (PST)
To: Adrian Hope-Bailie <adrian@hopebailie.com>, rfc-interest@rfc-editor.org
References: <CA+eFz_LeYwtafBKofgwqwjqpJPBn0KDj_5y24GdR=TV5+8rBTg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com>
Date: Sat, 17 Dec 2016 13:23:26 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <CA+eFz_LeYwtafBKofgwqwjqpJPBn0KDj_5y24GdR=TV5+8rBTg@mail.gmail.com>
Subject: Re: [rfc-i] Referencing IANA registries
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 17/12/2016 12:13, Adrian Hope-Bailie wrote:
> Hi,
> 
> I can't seem to find instructions on the correct way to reference an
> existing IANA registry in an RFC. How is this supposed to be done?
> 
> For example RFC 4147 has the following references:
> 
>    [iana-ipv6-registry]  IANA, "IANA IPv6 Address Registry",
>                          December 2004.
> 
>    [iana-ipv6-tla]       IANA, "IANA Registry of IPv6 Top Level
>                          Aggregation Identifier Assignments",
>                          December 2004.
> 
> But there is no specification of those formats.

Answer 1: When I hit one of these, I go to http://www.iana.org/protocols
and search within the page. But it isn't black and white; the first one doesn't
exist today under that name. Probably this:
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml

(I sincerely hope you are not really trying to use the highly obsolete TLA format.)

Answer 2: Some RFCs now cite the relevant URLs. For example, RFC 7217 cites:

   [IANA-RESERVED-IID]
              IANA, "Reserved IPv6 Interface Identifiers",
              <http://www.iana.org/assignments/ipv6-interface-ids>.

I think this is a Good Idea and should be done whenever possible.

    Brian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email