IETF Logo Mail Archive

Re: [xml2rfc] [django-project] RFC Bibtex format doi numbering incorrect

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 26 May 2017 02:06 UTC

Return-Path: <brian.e.carpenter@gmail.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 7715B12EB07 for <xml2rfc@ietfa.amsl.com>; Thu, 25 May 2017 19:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KFbRPYoqueJX for <xml2rfc@ietfa.amsl.com>; Thu, 25 May 2017 19:06:38 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 10B9D129C13 for <xml2rfc@ietf.org>; Thu, 25 May 2017 19:06:38 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id n23so183257571pfb.2 for <xml2rfc@ietf.org>; Thu, 25 May 2017 19:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=mMBF9ntFwnHeDTiCIe3hBDqHyEPzh0R7VRfRkp7nQdI=; b=lSzryoaK7Um8GG8hQbChmOLgoZqync15XUtVLIMeipKfqKGYHv77OvFl3FpDt/8wjN vJ2c7QSIwDrkRygG5Tsudqe1LPzr6GWgD9jXXsWjMYHf2ioBmHykmT8S+3qECt889qbM w7H5s75lKiC3pzD3xf7IPJja7cUO8+2WTdA01AeR48EUayGmm4tb1cCR1iX9BxakDZFh cT33eJ3KcrKwlVXSRmUlO7Y74a0PfIJvIhqqcnYO+c36hadZTfAxo7+dm7Dvmimnq0D2 1agLWxPqX1Wmrrea3/MJOYt/deNe+4ug8+GrcgCmmCtHq9Tcl1HiDA8Cs3C3+eGH+u+L hlHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=mMBF9ntFwnHeDTiCIe3hBDqHyEPzh0R7VRfRkp7nQdI=; b=jDw1JPf/rPl+YUnEz6GZIHDQ3/kMFTxZCQqml+6ZXIDNaZqLFv7MrlIXU7PSp5qyr4 tJhdhdrFfbSbchIYK2qhzsm/W10KMsfzpkdjDJC2jM/IE9/dXxtcmDxu2Ehc4ghfGbVp Y9KL3UAmkXCBHFRgnG220+VYCx7fo8e10RWk7ZCrHRC9uRd1UcQKi7q7r+v7TGORplrG kdv5G0HdeSvGtnguZm8Dy/P+hespMrOP1kUO6iqyWo4lQCWx29lqx509W9NZu9eOdbFE 3E0NAcgfuWqLuvKtuJkfFBvuyPVVshrY9zX1ytcPFri0BCa/NS+E29nEe5EAnCVTDfG3 GwYQ==
X-Gm-Message-State: AODbwcDfgW+cq6gQm2gW3X3ZZZC2m0nJPeZVAIylNZ4dWDwPg6XgsIIj jxttPvcdH7ZDjLOK
X-Received: by 10.84.194.34 with SMTP id g31mr16821724pld.89.1495764397425; Thu, 25 May 2017 19:06:37 -0700 (PDT)
Received: from [192.168.42.45] (smtp.acronym.co.nz. [219.88.101.26]) by smtp.gmail.com with ESMTPSA id a78sm17536129pfk.122.2017.05.25.19.06.34 for <xml2rfc@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 May 2017 19:06:36 -0700 (PDT)
To: xml2rfc@ietf.org
References: <15c2788f4d0.281d.7a19c564b98a554439c08072c0c083c8@informatik.uni-bonn.de> <b87d41d8-c4ec-1e35-de81-eb823152c467@nostrum.com> <12a1e67f-abb4-575a-1625-c8a31c677e62@gmx.de> <7399f585-6490-1575-810a-6069aeb09d9b@concordia.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <667e5874-b1ac-a58f-3ac5-4c7ae16a46e8@gmail.com>
Date: Fri, 26 May 2017 14:06:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <7399f585-6490-1575-810a-6069aeb09d9b@concordia.ca>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/tslquD0FXYhnfBVdFpXWalzQWAg>
Subject: Re: [xml2rfc] [django-project] 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: Fri, 26 May 2017 02:06:39 -0000

On 26/05/2017 12:49, William Atwood wrote:
> Whoever originated this message discovered that entering
> 
> 10.17487/rfc826
> 
> into the box on the website https://dx.doi.org/
> 
> gives a "not found" message.
> 
> Clearly there has to be agreement between the person who instantiated
> the IETF DOIs in the first place, and the person who maintains/generates
> the RFC BibTeX format.
> 
> As you say, I don't think that the person who generated the DOIs thought
> about RFC numbers greater than 9999.  And it will happen quite soon. 
> (Somewhat like exhausting IPv4 addresses...  :-) )

The suffix is any string that the originator (in this case, the RFC Editor)
happens to pick, and so far they have picked "RFC" followed by a four digit
number. But you can't rely on that; they could pick "fumbldook37" for
the next RFC published and still conform to the DOI standard.

Somebody, I think John Levine, explained this in detail on the rfc-interest
list a year or two ago.

   Brian

> 
>   Bill
> 
> 
> On 25/05/2017 5:19 PM, Julian Reschke wrote:
>> 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?
>>
>> Best regards, Julian
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>

v2.23.0 | Report a Bug | By Email