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

Carsten Bormann <cabo@tzi.org> Tue, 06 April 2021 22:57 UTC

Return-Path: <cabo@tzi.org>
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 DF20A3A349E; Tue, 6 Apr 2021 15:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 xeuf02RN4I7M; Tue, 6 Apr 2021 15:57:11 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0449A3A349C; Tue, 6 Apr 2021 15:57:10 -0700 (PDT)
Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FFNFc5KNjzyTl; Wed, 7 Apr 2021 00:57:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <e99c735259bd4905947ad19d5dd6ea5e@boeing.com>
Date: Wed, 7 Apr 2021 00:57:08 +0200
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 639442627.245929-01f7ff916d69855a5342c1111168e9d1
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F13207D-B855-485F-A1E9-33325F259819@tzi.org>
References: <949531a81fad4e3d94de80b7b23f088e@boeing.com> <34FD3ED0-C8EE-4E08-A5A2-0A5A5C5AAE4B@tzi.org> <e99c735259bd4905947ad19d5dd6ea5e@boeing.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/LNl4nfcXlN0LxGHQ2M-FapELCDs>
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 22:57:16 -0000

I hope someone who is more familiar with xml2rfc can answer this authoritatively.

When I was still using xml2rfc directly, I used the canonical way based on XML entities as described on slide 37 of
https://www.rfc-editor.org/materials/tools_ids_rfcs_94.pdf

Replace the URI after the SYSTEM with the one I gave below.

(Of course, I have been authoring I-Ds with kramdown-rfc for a decade now, and all this is handled behind the scene.)

However, I don’t know how much of the PI stuff (<?rfc…) survived into the RFCXMLv3 age, so maybe you want to switch to entities anyway.

Grüße, Carsten




> On 2021-04-06, at 23:59, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> 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
>