Re: [xml2rfc] [EXTERNAL] Re: xml2rfc unable to resolve recently-submitted IDs

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 06 April 2021 21:59 UTC

Return-Path: <Fred.L.Templin@boeing.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 EFDF73A327C; Tue, 6 Apr 2021 14:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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=boeing.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 H65PC4p4z9km; Tue, 6 Apr 2021 14:59:11 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 DC2ED3A3283; Tue, 6 Apr 2021 14:59:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 136Lx7sr000356; Tue, 6 Apr 2021 17:59:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1617746348; bh=A9qOKnw+58e4Hha/rtprdVrm41HjCk9qezOQizrkqns=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=O8kO/+SRff4AN6D+Ef1H0tKSnTSk15SIAnChN3iXhb/WRlqhSNsmGR9MdVX5Cd+AJ cO4GTblnU3oOiycf+P5PIiT7mh5cqaNvKH3DWbd0v+JlHA7IQ4fHbs4ZukS/H4/GLT 9sTLwZV95xvliXoE/uLcUc0FJKHabNHmEWTq2pPlM1Ucdn377kQT09ZdCksJpXq/fh nGWvbrmVhCZbgZoKnyi5BwD8VYGtn9Rb+CiqOE0FPW9G+CXHMNtKsDbUfBbycC0wJb 3wyj3lpq0VcOMLB6Jr/zGR6CL++32GRG8PZTaNcWZGKkZMmSNZTkD/Wol9bFdkcHDI 6+M/tli43ABnQ==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 136Lx1nS032751 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 6 Apr 2021 17:59:01 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2176.2; Tue, 6 Apr 2021 14:59:00 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2176.009; Tue, 6 Apr 2021 14:59:00 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Carsten Bormann <cabo@tzi.org>
CC: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Thread-Topic: [EXTERNAL] Re: [xml2rfc] xml2rfc unable to resolve recently-submitted IDs
Thread-Index: AdcrC9Pj8GTZXK3IQumjH07JVh8wNwAWBBAAAA0gQSA=
Date: Tue, 6 Apr 2021 21:59:00 +0000
Message-ID: <e99c735259bd4905947ad19d5dd6ea5e@boeing.com>
References: <949531a81fad4e3d94de80b7b23f088e@boeing.com> <34FD3ED0-C8EE-4E08-A5A2-0A5A5C5AAE4B@tzi.org>
In-Reply-To: <34FD3ED0-C8EE-4E08-A5A2-0A5A5C5AAE4B@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 5736823BB3C216099930CDBD011DA76E752FA1B2E7D84CD2FDCD3612B84AD4662000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/NEw6GAyjEt1tELMRD1NZrp7eHWs>
Subject: Re: [xml2rfc] [EXTERNAL] Re: xml2rfc unable to resolve recently-submitted IDs
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Apr 2021 21:59:16 -0000

Thanks Carsten, but I am not familiar with working directly with the bibxml3
files. Currently in my draft xml source file I have:

      <?rfc include="reference.I-D.templin-6man-aero"?>
      <?rfc include="reference.I-D.templin-6man-omni"?>

which are failing to find the references at the default locations. How do I
revise those entries to point to the alternate locations you provided?

Fred

> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Tuesday, April 06, 2021 2:10 PM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: xml2rfc-dev@ietf.org; xml2rfc@ietf.org
> Subject: [EXTERNAL] Re: [xml2rfc] xml2rfc unable to resolve recently-submitted IDs
> 
> EXT email: be mindful of links/attachments.
> 
> 
> 
> On 2021-04-06, at 19:39, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> >
> > https://datatracker.ietf.org/doc/draft-templin-6man-aero/
> > https://datatracker.ietf.org/doc/draft-templin-6man-omni/
> 
> You might be running into issues around tools.ietf.org, which is not always updating at the rate needed.
> 
> You can use
> 
> https://datatracker.ietf.org/doc/bibxml3/draft-templin-6man-aero/xml
> https://datatracker.ietf.org/doc/bibxml3/draft-templin-6man-omni/xml
> 
> as your bibxml references instead.
> 
> Grüße, Carsten