IETF Logo Mail Archive

Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John Levine" <johnl@taugh.com> Tue, 30 May 2017 21:16 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 CF6D012944B for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 14:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qgwIjyipz39f for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 14:16:56 -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 EAA031293FD for <xml2rfc@ietf.org>; Tue, 30 May 2017 14:16:55 -0700 (PDT)
Received: (qmail 52509 invoked from network); 30 May 2017 21:16:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 30 May 2017 21:16:55 -0000
Date: Tue, 30 May 2017 21:16:33 -0000
Message-ID: <20170530211633.65372.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
In-Reply-To: <592CC79E.8080804@levkowetz.com>
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/n0mP7DNwPgZ8QC6mW3XlvakMns4>
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: Tue, 30 May 2017 21:16:58 -0000

In article <592CC79E.8080804@levkowetz.com> you write:
>In general, there's no problem in that.  There _is_ a problem in not even being
>able to talk about when that might or might not be feasible, and how to handle
>such a situation.  There is also a problem that there does not seem to be an
>authoritative URL for such lookups.

I answered this privately, but in case anyone else was wondering,
they're in https://www.rfc-editor.org/rfc-index.xml along with the
rest of the bibliographic info for all of the RFCs.

The per-document pages on the RFC editor's web site are generated from
that file (I updated a bunch of them to include DOIs) so anyone who
wants the info might as well get it from the original source.

R's,
John

v2.23.0 | Report a Bug | By Email