IETF Logo Mail Archive

Re: [rfc-i] Referencing IANA registries

Joe Touch <touch@isi.edu> Sat, 17 December 2016 00:38 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 5D88F1294D4 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] 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 whYxXI2eH7Jm for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 16 Dec 2016 16:38:30 -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 9E3EF1294BB for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 16 Dec 2016 16:38:30 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5404EB808E6; Fri, 16 Dec 2016 16:38:30 -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 4F2FEB808E6 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
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 FneTs-cnSPnA for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:38:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by rfc-editor.org (Postfix) with ESMTPS id E561DB808E5 for <rfc-interest@rfc-editor.org>; Fri, 16 Dec 2016 16:38:27 -0800 (PST)
Received: from [128.9.184.247] ([128.9.184.247]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id uBH0br8N016579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Dec 2016 16:37:54 -0800 (PST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Adrian Hope-Bailie <adrian@hopebailie.com>, rfc-interest@rfc-editor.org
References: <CA+eFz_LeYwtafBKofgwqwjqpJPBn0KDj_5y24GdR=TV5+8rBTg@mail.gmail.com> <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <bf7b2b2b-df18-9945-9916-c36ae0dd888f@isi.edu>
Date: Fri, 16 Dec 2016 16:37:52 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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 12/16/2016 4:23 PM, Brian E Carpenter 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 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.

That's what we did in RFC6335:

   [PORTREG]         Internet Assigned Numbers Authority (IANA),
                                 "Service Name and Transport Protocol
Port Number
                                 Registry",
                                
<http://www.iana.org/assignments/port-numbers>.

I don't think there's any useful convention for the citation label.

Joe

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

v2.8.7 | Report a Bug | By Email