IETF Logo Mail Archive

Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

worley@ariadne.com (Dale R. Worley) Sun, 28 May 2017 14:30 UTC

Return-Path: <worley@alum.mit.edu>
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 5FC00126E3A for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 07:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level:
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 IW6XqI_zFmCO for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 07:30:36 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C23512426E for <xml2rfc@ietf.org>; Sun, 28 May 2017 07:30:35 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-09v.sys.comcast.net with SMTP id EzDHdtY5MQe9cEzDHdWOuG; Sun, 28 May 2017 14:30:35 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-09v.sys.comcast.net with SMTP id EzDFdL4w7jCS0EzDGdiB25; Sun, 28 May 2017 14:30:34 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v4SEUW1P009774; Sun, 28 May 2017 10:30:32 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v4SEUVPP009769; Sun, 28 May 2017 10:30:31 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Julian Reschke <julian.reschke@gmx.de>
Cc: johnl@taugh.com, xml2rfc@ietf.org
In-Reply-To: <c08be30c-253a-47d6-a9f9-c89741073a8c@gmx.de> (julian.reschke@gmx.de)
Sender: worley@ariadne.com
Date: Sun, 28 May 2017 10:30:31 -0400
Message-ID: <87shjphx4o.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfObwKjUTrJ9bwrIyU7eSHLmWOs+DajU/KCgTP5RhdxOfKRpzQ/81U2+3Lf017Vsh3hRgQ9jXzAsh4I4IfFnvCyRL6nI/BhC4m0bWTF8J5XE1zvE32wLG wP2Dx4GR7M1VAshXPziJ2uCxxe46Lq3275lxU/iCfzwua7tcLISF7u/lnUnQUKyPy+AeF2WLhLDWYCraA+Df733f0ErZw04ckSM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/rhsfjOApX9Ta81moiCIadza8Jus>
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 14:30:37 -0000

Julian Reschke <julian.reschke@gmx.de> writes:
>> 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?

I don't know why, but presumably because it allows future flexibility.
In any case, the DOIs for existing RFCs have been *assigned*.  If you
use rsync to fetch ftp.rfc-editor.org::rfcs/rfc-index.txt, you seen
entries like this:

    0826 Ethernet Address Resolution Protocol: Or Converting Network Protocol
         Addresses to 48.bit Ethernet Address for Transmission on Ethernet
         Hardware. D. Plummer. November 1982. (Format: TXT=21556 bytes)
         (Updated by RFC5227, RFC5494) (Also STD0037) (Status: INTERNET
         STANDARD) (DOI: 10.17487/RFC0826) 

I would assume that the bibtex information for RFCs contains the DOIs as
Just Another Field.  But indeed, the "doi" field in
http://datatracker.ietf.org/doc/rfc826/bibtex/ doesn't match
rfc-index.txt:

	doi =		{10.17487/rfc826},

Dale

v2.23.0 | Report a Bug | By Email