Re: [rfc-i] Referencing IANA registries

Adrian Hope-Bailie <adrian@hopebailie.com> Sat, 17 December 2016 00:34 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 260D312945C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.986
X-Spam-Level:
X-Spam-Status: No, score=-6.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=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 (1024-bit key) reason="fail (body has been altered)" header.d=hopebailie.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 2CdzVR9_zgKV for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:34:13 -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 2D8CC1293F2 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Dec 2016 16:34:13 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DD5DCB808DE; Fri, 16 Dec 2016 16:34:12 -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 B9504B808DE for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopebailie.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 LNy8vexrLvNf for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:34:10 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) by rfc-editor.org (Postfix) with ESMTPS id 00C46B808DD for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:34:09 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id f82so52083191wmf.1 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:34:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopebailie.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Vxq99AAFbR8aPb2IPngE5NfRzIODXa5tb1pZhMYEGzQ=; b=Rfk2Yfo0CdwMIZRS9pEbibIp4M5TVdl/KrvcE0q0OXjSzfTC+AgwEsN5d+s6OQSXgI Ir77uxtroMAOtcZUNndMSnaXtEJN3stFn7IsXCnqGCj9X5vEi6F7/k1KqsfMnlGe7Ido /1zfi1N+4TPhZDqtvQqNGe4DzXEQyZbso9o6k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Vxq99AAFbR8aPb2IPngE5NfRzIODXa5tb1pZhMYEGzQ=; b=k9yeWFVPka8u/IJcNj0dDB6fFtH7tlK+vqLTApGRsUALOHuk9d6bPIKqnYyIbmN2EZ T4N5OuV929BrH+s57y4h9auTtZnxRiDHvwOx+r2pn4CMEJRhG9SpSUK+W6QWa1muV7Nc EB6zQHw6Zarkz9OECMZo5v2t0Rsni20YKqaLoubRoVODmvMIZQZ4ODh4Ms1v1/I00CrK /PZmvQdxQSzUROkmVK3LkXQsGIllgJs/xJ5qugoTwlcjLrC3W+yVhEjLo2GGVPFtGmH4 074cfrkopp1d5Vl5JQGTPb1UuMr41e9Fs6QUKIeAURixKW+6+Vcp5mO2sTR6BEKvUB7U hbCw==
X-Gm-Message-State: AIkVDXL7hQHaxhGg9BkYLqpCQWQnHMeO6P3fZVN/dQa6ausPtAuHc+YQqFogJktbfyHOE1RM/mhbF7vHFBZvAw==
X-Received: by 10.28.35.14 with SMTP id j14mr5058426wmj.24.1481934848373; Fri, 16 Dec 2016 16:34:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.248.137 with HTTP; Fri, 16 Dec 2016 16:34:07 -0800 (PST)
In-Reply-To: <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com>
References: <CA+eFz_LeYwtafBKofgwqwjqpJPBn0KDj_5y24GdR=TV5+8rBTg@mail.gmail.com> <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com>
From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Fri, 16 Dec 2016 16:34:07 -0800
Message-ID: <CA+eFz_KpeGOeDiS39qRM-uPHLv5aVqDwpviCgVedL4ZTGXuu4A@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@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>
Cc: rfc-interest@rfc-editor.org
Content-Type: multipart/mixed; boundary="===============0462679830031818527=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Thanks, I was looking for something like Answer 2.

Where does the reference title ( [IANA-RESERVED-IID] ) come from in that
instance?
Should I just make something up that looks sensible?

Those references were just examples I found online, the registries I want
to reference are the "Named Information Hash Algorithm Registry" and "Named
Information URI Parameter Definitions" which (to make things more complex)
are both at the same URL:
https://www.iana.org/assignments/named-information/named-information.xhtml


On 16 December 2016 at 16:23, Brian E Carpenter <brian.e.carpenter@gmail.com
> wrote:

> 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