Re: [rfc-i] Referencing IANA registries

Joe Touch <touch@isi.edu> Sat, 17 December 2016 08: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 DD58E1294B2 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 17 Dec 2016 00:34:44 -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 6oJHyrxbeBcF for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 17 Dec 2016 00:34:43 -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 3578E1293E1 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sat, 17 Dec 2016 00:34:43 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DF6B1B80FE6; Sat, 17 Dec 2016 00:34:42 -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 CB471B80FE6 for <rfc-interest@rfc-editor.org>; Sat, 17 Dec 2016 00:34:41 -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 i_pB2UHoSunq for <rfc-interest@rfc-editor.org>; Sat, 17 Dec 2016 00:34:40 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by rfc-editor.org (Postfix) with ESMTPS id 94C8BB80FE5 for <rfc-interest@rfc-editor.org>; Sat, 17 Dec 2016 00:34:40 -0800 (PST)
Received: from [192.168.1.158] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id uBH8Y9Jv014560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 17 Dec 2016 00:34:10 -0800 (PST)
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@isi.edu>
X-Mailer: iPad Mail (14B100)
In-Reply-To: <4360F11C-C34A-4D50-AE41-54B352FDE45C@tzi.org>
Date: Sat, 17 Dec 2016 00:34:09 -0800
Message-Id: <4F375065-99CB-4CC9-BBE5-C2A2BE4C7213@isi.edu>
References: <CA+eFz_LeYwtafBKofgwqwjqpJPBn0KDj_5y24GdR=TV5+8rBTg@mail.gmail.com> <6e1d3bbe-2ccd-c393-6fae-a530f52bfde3@gmail.com> <bf7b2b2b-df18-9945-9916-c36ae0dd888f@isi.edu> <4360F11C-C34A-4D50-AE41-54B352FDE45C@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
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>
Cc: rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Most of the time we probably should be citing the RFC that created the registry, rather than the registry itself.

> On Dec 17, 2016, at 12:18 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
>> On 17 Dec 2016, at 01:37, Joe Touch <touch@isi.edu> wrote:
>> 
>> I don't think there's any useful convention for the citation label.
> 
> If we want to automate this from an authoring tool, I’d probably use the label
> 
> [IANA.SERVICE-NAMES-PORT-NUMBERS]
> 
> then lower-case the part after IANA, fetch
> 
> http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
> 
> and then build the References entry from '/registry/title/text()’ and that URI after removing the last path component.
> 
> Would that be a useful addition to an authoring tool?

I don't understand what you're building.  I thought the reference was to the table, not an entry. 

> 
> (I’m not sure what to make of the fact that this particular registry appears to have an alias; I’d rather use the official names.)

It's one of the few with a searchable index.

Joe

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