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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 12 April 2021 15:34 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 E3C333A22B0; Mon, 12 Apr 2021 08:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 RPwj0QgrLNUh; Mon, 12 Apr 2021 08:33:56 -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 D94E93A2352; Mon, 12 Apr 2021 08:33:42 -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 13CFXcct016107; Mon, 12 Apr 2021 11:33:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1618241621; bh=XN92MAEowIjYhcuHZmoIAzp/7xsA+yqOXqp4E2m1eqU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=XL4sj/BK9kv92Rtiv91EGNShsNraFDmvyeBtCSPm4zpqqVZpnNn6rZWdVdLl7PirM /5FlE5znnK7Z0EF5zbXDRnwnZ/HaLawns+tHKbg8Na/Prby6nxfBQHx6iQkpZnzwKp EwF0tP+uml8Itib7dIdO1J7NtqvWLcJ9vv4VKzB+v51ZYKBTUqTxBXMDEe4Gsr4c6d VG6g0GyABjKVF4icfYfrb32eLhwQ6kfoYg52jzHMwmR52LqLLT3V2nnacnSuvubOi4 rBJ7iTFPcF96HpPpdHQgRrrCdevQ+1tqcMpKKhXVh17wxlCvHodBEafjVgod3oy970 FbiHltfB+vJZw==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 13CFXTP1015898 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 12 Apr 2021 11:33:29 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2176.2; Mon, 12 Apr 2021 08:33:28 -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; Mon, 12 Apr 2021 08:33:28 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "HANSEN, TONY L" <tony@att.com>, Carsten Bormann <cabo@tzi.org>
CC: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Robert Sparks <rjsparks@nostrum.com>, "Henrik Levkowetz" <henrik@levkowetz.com>
Thread-Topic: [xml2rfc-dev] [xml2rfc] xml2rfc unable to resolve recently-submitted IDs
Thread-Index: AQHXK73+a+Z9+PESzEuPxmOZpR414aqxCi5g
Date: Mon, 12 Apr 2021 15:33:28 +0000
Message-ID: <9b8a00a5d4cb41ca8ff07afb167b9385@boeing.com>
References: <949531a81fad4e3d94de80b7b23f088e@boeing.com> <34FD3ED0-C8EE-4E08-A5A2-0A5A5C5AAE4B@tzi.org> <AFAC39F0-62B5-4EF9-9548-2796EE42D6CF@att.com>
In-Reply-To: <AFAC39F0-62B5-4EF9-9548-2796EE42D6CF@att.com>
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: B9B2490F9B0CE0825CBAE7967D0301A325D84E0B4A09FDF2D223EE65CD654ACE2000: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/W0HEX3psEEfSG94Jo4Gtu9XOZvQ>
Subject: Re: [xml2rfc] [xml2rfc-dev] 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: Mon, 12 Apr 2021 15:34:07 -0000

> I just delivered a fix to the bibxml3/bibxml-ids issue on the xml2rfc.tools.ietf.org servers.
> 
> 	Tony

Hi Tony, it was working for a while after your posted this message but now
once again I am unable to resolve the new draft references. Has something
changed such that the system has reverted - if so, can you re-apply the fix?

Thanks - Fred

> -----Original Message-----
> From: HANSEN, TONY L [mailto:tony@att.com]
> Sent: Wednesday, April 07, 2021 7:55 AM
> To: Carsten Bormann <cabo@tzi.org>rg>; Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: xml2rfc@ietf.org; xml2rfc-dev@ietf.org; Robert Sparks <rjsparks@nostrum.com>om>; Henrik Levkowetz <henrik@levkowetz.com>
> Subject: [EXTERNAL] Re: [xml2rfc-dev] [xml2rfc] xml2rfc unable to resolve recently-submitted IDs
> 
> EXT email: be mindful of links/attachments.
> 
> 
> 
> On 4/6/2021, 5:11 PM, "xml2rfc-dev on behalf of Carsten Bormann" <xml2rfc-dev-bounces@ietf.org on behalf of cabo@tzi.org> wrote:
> 
>     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.
> 
> I just delivered a fix to the bibxml3/bibxml-ids issue on the xml2rfc.tools.ietf.org servers.
> 
> 	Tony
>