Re: Call for comment: <draft-iab-doi-04.txt> (Assigning Digital Object Identifiers to RFCs)

"John Levine" <johnl@taugh.com> Sat, 04 July 2015 00:30 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD2D1A92AF for <ietf@ietfa.amsl.com>; Fri, 3 Jul 2015 17:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 HxKwPL_jgNrm for <ietf@ietfa.amsl.com>; Fri, 3 Jul 2015 17:29:59 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 717471A923E for <ietf@ietf.org>; Fri, 3 Jul 2015 17:29:59 -0700 (PDT)
Received: (qmail 96229 invoked from network); 4 Jul 2015 00:30:12 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 4 Jul 2015 00:30:12 -0000
Date: Sat, 04 Jul 2015 00:29:36 -0000
Message-ID: <20150704002936.1550.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Call for comment: <draft-iab-doi-04.txt> (Assigning Digital Object Identifiers to RFCs)
In-Reply-To: <55959F1A.4010508@cisco.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sJWpYADQrnzfqI8kMIaxtGSsreQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jul 2015 00:30:00 -0000

>Can you explain where such a suggestion is made?  As to the form that
>comes AFTER the prefix, THAT is worthy of discussion, but that indeed
>may be too late.

As I note in the draft, the part after the prefix is opaque.  The DOIs
that the ACM assigns are two numbers that have no connection to
anything else I can figure out.  The IEEE uses some combination of a
short abbreviation of the journal name, the year, and a sequence
number that does not tell you what issue the article is in.

In retrospect, rather than making them look like RFC numbers I should
have used a pseudo-random 10 digit hash of the date, authors, and
document title so people would stop complaining about RFC123 vs.
RFC0123.

R's,
John