Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Henrik Levkowetz <henrik@levkowetz.com> Mon, 29 May 2017 22:07 UTC

Return-Path: <henrik@levkowetz.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 3C3E3129413 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 15:07:21 -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] 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 S8-9TBHAyY7q for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 15:07:20 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D534120726 for <xml2rfc@ietf.org>; Mon, 29 May 2017 15:07:20 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:50484 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1dFSop-0004hx-L9; Mon, 29 May 2017 15:07:19 -0700
To: John Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <20170526165214.45384.qmail@ary.lan>
Cc: julian.reschke@gmx.de
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <592C9B8F.2050504@levkowetz.com>
Date: Tue, 30 May 2017 00:07:11 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20170526165214.45384.qmail@ary.lan>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="sDWDXIuL3xBLBK2942krqRD82kpcwr38V"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: julian.reschke@gmx.de, xml2rfc@ietf.org, johnl@taugh.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/MbQ4y1aE5qiV2VTrwqB8rddkK58>
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: Mon, 29 May 2017 22:07:21 -0000

Hi John,

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

Whatever was used, once you wrote the code, wouldn't it make sense to
publish where/how lookups should happen?  Has this been done?


And no matter how opaque the DOI series identifiers are in general, there's
still nothing that prevents the RFC Editor from _having_ a defined mapping
from RFC numbers to DOI and vice versa, if a decision is made that this
would be helpful, right?


	Henrik