Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John R Levine" <johnl@taugh.com> Tue, 30 May 2017 23:50 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 D914212941C for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 16:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=OTbFOkDx; dkim=pass (1536-bit key) header.d=taugh.com header.b=j1DJm5Pe
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 SUQPixYM0wyW for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 16:50:32 -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 3623E129329 for <xml2rfc@ietf.org>; Tue, 30 May 2017 16:50:32 -0700 (PDT)
Received: (qmail 69500 invoked from network); 30 May 2017 23:50:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=10f7a.592e0547.k1705; bh=Wb90NqWshj1xzZn2SWiYiggNwwFbtcdIhk+DzcEfpWo=; b=OTbFOkDxElhkCw/xl5tptHdw+ndVgU30aQZULiarFW228QJSrDCGRWPfW1YDuUKON0JL2l+rDfLR0RBt8PsTcT2JWWw/br+VVAAfDVSZ6iq6u0EMGzL9BiI8NjWbuXVDH+eU1AgCSDTMtJpmVUusX0tP5W5FimGG1Pw2QvsfGMEsbaAgh/8goTNwCubBya8HBBgoboQWOmdgBVblTjSOXTfaScILHwpUORTpnhTJcYhFG0SInywwaFuluYFm0SSb
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=10f7a.592e0547.k1705; bh=Wb90NqWshj1xzZn2SWiYiggNwwFbtcdIhk+DzcEfpWo=; b=j1DJm5Pe0uMzLUZMpkLBO1aS3pMuvk+Eoq2pE+1HiRbpR+w9oi6s2CyPXDlZK7aKR0nZTpL/cR/EWKBqqQ8OD4J5yrKq1u2f0wSg8C0W9MM2gvI8tAlxcLdZnaj3jGRaZ3Nf6SHTk8u3Lj6KfkYS40I264N+Kep/WQ55xCSfIp91nqiwfA8bTAhqDvLaFMPm0MFZh2j8T2LTJCA1vblKOUMftILq27a3p/0DflCIWnPOws/uWAdErFqeOjpUt2Is
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 30 May 2017 23:50:31 -0000
Date: Tue, 30 May 2017 19:50:30 -0400
Message-ID: <alpine.OSX.2.21.1705301949420.56985@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
In-Reply-To: <592E00D4.6070206@levkowetz.com>
References: <20170530211633.65372.qmail@ary.lan> <592E00D4.6070206@levkowetz.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/UA6z2xFe4CKl_CblzqCN_aCFg9w>
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 23:50:34 -0000

> However, please note that this is not a lookup resource which encourages
> on-the-fly lookups and caching.  It requires you to download the whole
> corpus information every time you need an update ...

Sure, but I expect it's obvious how you'd cache a copy locally for 
lookups.  Downloading it once a day would be plenty.

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

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly