Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John Levine" <johnl@taugh.com> Fri, 26 May 2017 16:52 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A79A129AE7 for <xml2rfc@ietfa.amsl.com>; Fri, 26 May 2017 09:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 D1ekreiUIVsY for <xml2rfc@ietfa.amsl.com>; Fri, 26 May 2017 09:52:37 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B99A128DF6 for <xml2rfc@ietf.org>; Fri, 26 May 2017 09:52:37 -0700 (PDT)
Received: (qmail 2476 invoked from network); 26 May 2017 16:52:36 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 26 May 2017 16:52:36 -0000
Date: Fri, 26 May 2017 16:52:14 -0000
Message-ID: <20170526165214.45384.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
Cc: julian.reschke@gmx.de
In-Reply-To: <12a1e67f-abb4-575a-1625-c8a31c677e62@gmx.de>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/DSMGXntYTLoTkOIX7_2t7FYkdrY>
Subject: Re: [xml2rfc] RFC Bibtex format doi numbering incorrect
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2017 16:52:39 -0000

In article <12a1e67f-abb4-575a-1625-c8a31c677e62@gmx.de> you write:
>On 2017-05-25 21:49, Robert Sparks wrote:
>> Forwarding to what I hope is the best list...
>
>Out of curiosity: why is it incorrect? Do we have a precise description 
>about what the format should be? Hopefully including RFC#s > 9999?

DOIs are opaque identifiers.  The DOI of any RFC is whatever is in the
DOI field of the RFC Editor's database.  Any code that attempts to
guess the DOI from the RFC number is broken.

The DOI gemeration code uses the editor database internal identifier
as the last component of the DOI, because the code was easy to write.
Those identifiers currently all look like RFCnnnn but they may change
at any time without notice, since they're purely for the editor's
internal use.  In retrospect, using them was a mistake.  I should have
used something obviously opaque like a hash of the title and issue
date for the DOI.

In response to the question of what DOIs of RFCs past RFC9999 will be,
it doesn't matter.  If your code tries to guess, it is still broken.
The DOI is whatever the DOI is.  Don't guess, look it up.

R's,
John