Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Julian Reschke <julian.reschke@gmx.de> Sun, 28 May 2017 12:56 UTC

Return-Path: <julian.reschke@gmx.de>
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 945AD1293EE for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 05:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 n5Cj7ijdDMQl for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 05:55:59 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E280B1286B2 for <xml2rfc@ietf.org>; Sun, 28 May 2017 05:55:58 -0700 (PDT)
Received: from [172.16.38.233] ([46.183.103.17]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MNIO5-1dHRlx0dMf-006u5W; Sun, 28 May 2017 14:55:38 +0200
To: John Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <20170526165214.45384.qmail@ary.lan>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <c08be30c-253a-47d6-a9f9-c89741073a8c@gmx.de>
Date: Sun, 28 May 2017 14:55:28 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20170526165214.45384.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:VFETYWmPDTPrbqUSFsCnrXNaMIEWVyDYoOBZZ9A19HSKQeQGpOm hsg8VU+pOa6puzrHkBMD8LV7+JpZFlWG/h7nGnsymgTWVz2UJC1YrbAr+YAH+DfHcE1t+FX ijp3k4jJ8o6kq20NyU8AGGNXBwBfjG404GVTsGXI+A1qsxpcD/uxrVm0Z2JXdKtp5zur265 ceHWkpFFuhF7MoKaDbISw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:OLQBY2mVyBQ=:h9RUwODX7jc7nDZWYJReQJ aJKkYI9rpY1+wfm/YWrklIS1f4F2PPQ4/824q7DrrHmXhczfp9ueFbCUf5y25R9cVxcJhNwmp 4zFR3HyVzvX3xwL9oUAWIb/CAY0waych2WZyD4Pbsm7fzksRK5l+lr+llj4aePUP2qhMn0BxJ UCaDf+N4OJhKSqmJ+CdIEZ4rHJqnGcFC5KUS1YmdtLGssgrPKjym2TeEnydKbT0zevEU3I14D 1jO9oShTgPjzi5D+8+RcvGZdZyqB3lFTlsHcCyGY24+iaWtGh2S4q5BlKnmWi/QvLUUOg6SRd oIsLCCTFi/BIpRI2JQto9etBR4yiH6J5rw17JYkKUCnf3vGu3a3y5tlv3MRgGx1Qp5+gdln/8 KRo2rlYjSEN6caJCt+L0JlVERRRZIJLupiyHBkDCAsOgiBFck705+GUuDMwVY9ARTghDsx5eF Zl5fO/jUueXQKeDbsabaRXaeVWRt9O4SuOkfihWD86X6oYxu4PseigzmUOmhAbBgnLhN06LlW Q36Z7sAX9ZfgnsMlJe2AROu6j7GGXjCN90t+3IPiK5XkX7THChMK9TcPlkbALjMLUZF5/T2ak 448Hr+dxYGjDxDLjtiRyQj3ReaHjHdzWrd3C+3SPrmzKpfDEG7QNx76xcVUz0GYH2uyCzxQxL jMKrzBWKIA4HO4gJtDVtcz9RJfMh9FLOlUV41XRN9SujgV+dJs1v8DNnS904MNJw+XBwci58H alMY9PuBi5VFcYw++VvjsbCTrBhXS4prXJmuZYTDhzpiQtfEjPvLGa3+dPBJ5mQgAf7B18d1M gEyQyDA1oJ86tkxzAfgZth/0utU1w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1-e0NNFFeU57NahD8llPuNZ_GcI>
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: Sun, 28 May 2017 12:56:01 -0000

On 2017-05-26 18:52, John Levine wrote:
> 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.

Wow. Really? Why not just define the mapping precisely?

> 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.

Right. So if they are for the editor's internal use only, what's the 
correct way to compute the DOI for a RFC then?

> 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.

Where? I thought you just said the database is for internal use only?

Once again: just define the mapping precisely.

Best regards, Julian