IETF Logo Mail Archive

Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"HANSEN, TONY L" <tony@att.com> Wed, 31 May 2017 18:06 UTC

Return-Path: <tony@att.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 9451F124BE8 for <xml2rfc@ietfa.amsl.com>; Wed, 31 May 2017 11:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.58
X-Spam-Level:
X-Spam-Status: No, score=-1.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 q3_6ccly4xbX for <xml2rfc@ietfa.amsl.com>; Wed, 31 May 2017 11:06:41 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 E33BD1201FA for <xml2rfc@ietf.org>; Wed, 31 May 2017 11:06:40 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v4VI5HWZ004938 for <xml2rfc@ietf.org>; Wed, 31 May 2017 14:06:38 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049297.ppops.net-00191d01. with ESMTP id 2at1bm2yce-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <xml2rfc@ietf.org>; Wed, 31 May 2017 14:06:38 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v4VI6aqi006076 for <xml2rfc@ietf.org>; Wed, 31 May 2017 14:06:37 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v4VI6UUF005826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <xml2rfc@ietf.org>; Wed, 31 May 2017 14:06:32 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi409.sfdc.sbc.com (RSA Interceptor) for <xml2rfc@ietf.org>; Wed, 31 May 2017 18:06:14 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.110]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0319.002; Wed, 31 May 2017 14:06:14 -0400
From: "HANSEN, TONY L" <tony@att.com>
CC: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Thread-Topic: [xml2rfc] RFC Bibtex format doi numbering incorrect
Thread-Index: AQHS2YoDOdwsOkQSAkS3CdEFuRkePqINybcAgAAFTACAAGecAIAAduMAgAACRQCAAA5SgA==
Date: Wed, 31 May 2017 18:06:13 +0000
Message-ID: <47ACC700-F6B5-4357-81AC-F18EA48BD138@att.com>
References: <20170530211633.65372.qmail@ary.lan> <592E00D4.6070206@levkowetz.com> <alpine.OSX.2.21.1705301949420.56985@ary.qy> <ce470bca-4611-8503-9f70-0e3760299c57@gmx.de> <alpine.OSX.2.21.1705310903300.59664@ary.qy> <c96e3a97-3716-a52e-dbb0-389e882405ef@gmx.de>
In-Reply-To: <c96e3a97-3716-a52e-dbb0-389e882405ef@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.210.3.122]
Content-Type: text/plain; charset="utf-8"
Content-ID: <11D1A9F4C5828B41AB21B7D8096011D8@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-05-31_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705310328
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ougK-6beDKATzyK0Xh-rEQ5Pkrs>
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: Wed, 31 May 2017 18:06:41 -0000

On 5/31/17, 9:14 AM, "xml2rfc on behalf of Julian Reschke" <xml2rfc-bounces@ietf.org on behalf of julian.reschke@gmx.de> wrote:

    On 2017-05-31 15:06, John R Levine wrote:
    >> So if it's obvious, why do we have published RFCs with broken DOIs? 
    >> This is something that could have been avoided if the formatter had 
    >> done a sanity check.
    > 
    > Beats me.  If the references had come from bibtex, they'd be right, so 
    > who knows what other tools they haven't been using.  As you surely know, 
    > we can write all the tools we want but we can't force people to use them.
    > ...
    
    Well, we know that an xml2rfc processor *is* used. That processor could 
    do a sanity check on the DOIs, in which case the problem might have been 
    detected during AUTH48.


If the bibxml references from xml2rfc.ietf.org are used, the DOIs will be exactly what are created by John’s tools on the RFC Editor site.

	Tony

v2.23.0 | Report a Bug | By Email