IETF Logo Mail Archive

Re: [Rfc-markdown] 1.6.14 no longer gets DOI references from bib.ietf.org,

Kesara Rathnayake <kesara@staff.ietf.org> Wed, 06 July 2022 21:16 UTC

Return-Path: <kesara@staff.ietf.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABE3BC15A742 for <rfc-markdown@ietfa.amsl.com>; Wed, 6 Jul 2022 14:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.781
X-Spam-Level:
X-Spam-Status: No, score=-3.781 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4z9_n7eeFjid for <rfc-markdown@ietfa.amsl.com>; Wed, 6 Jul 2022 14:16:33 -0700 (PDT)
Received: from ietfx.amsl.com (ietfx.amsl.com [50.223.129.196]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA68C15A750 for <rfc-markdown@ietf.org>; Wed, 6 Jul 2022 14:16:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 1220B4343AF0; Wed, 6 Jul 2022 14:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.amsl.com ([50.223.129.196]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrX53VsCtBVj; Wed, 6 Jul 2022 14:16:32 -0700 (PDT)
Received: from [192.168.1.87] (122-58-89-179-vdsl.sparkbb.co.nz [122.58.89.179]) by ietfx.amsl.com (Postfix) with ESMTPSA id 7F8BD4342F82; Wed, 6 Jul 2022 14:16:32 -0700 (PDT)
Message-ID: <5f1904c0-38b3-1133-f792-bc19e8ec5594@staff.ietf.org>
Date: Thu, 07 Jul 2022 09:16:30 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.0
Content-Language: en-NZ
To: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
References: <B2E8B010-548C-49DB-9AEB-FAAC6F3CC302@tzi.org> <9C05F741-EB53-425E-B3E7-7635AD6C224D@tzi.org>
From: Kesara Rathnayake <kesara@staff.ietf.org>
Organization: IETF Administration LLC
In-Reply-To: <9C05F741-EB53-425E-B3E7-7635AD6C224D@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/_z4PEkUvvLnTlOGeVEUxIsIRdek>
Subject: Re: [Rfc-markdown] 1.6.14 no longer gets DOI references from bib.ietf.org,
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2022 21:16:33 -0000

I have update author tools [1] to use kramdown-rfc 1.6.14 and unset the 
`KRAMDOWN_USE_TOOLS_SERVER` environment variable.
Let me know if there are any issues.

[1] https://author-tools.ietf.org/

   --Kesara

On 7/07/22 12:38 am, Carsten Bormann wrote:
> 1.6.14 no longer gets DOI references from bib.ietf.org,
> unless environment variable KRAMDOWN_USE_TOOLS_SERVER is set.
> 
> 
> Note that kramdown-rfc builds a cache of reference entries.
> For DOI references, this cache is renewed after 1 day.
> 
> Set environment variable KRAMDOWN_USE_TOOLS_SERVER to fill the cache from $XML_RESOURCE_ORG_HOST (default bib.ietf.org) as before.
> 
> If something broken has already been fetched, remove it from the cache (or entirely flush the cache).
> The cache is located at $KRAMDOWN_REFCACHEDIR, or, if that is not set, in .refcache in the current directory.
> Many people set this to ~/.cache/xml2rfc to share a cache for all their documents, and also with xml2rfc.
> 
> Grüße, Carsten
> 
>> On 2022-07-06, at 06:44, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> As part of the migration away from the tools.ietf.org servers, a new bib.ietf.org service has been set up.
>> Kramdown-rfc switched to the new service with 1.6.12, on 2022-06-27.
>>
>> Unfortunately, it turns out there are heavy regressions with DOI.* references.
>> 5 days before I-D deadline is not the best time to deal with this.
>>
>> If that problem hits you:
>> As a workaround, you can manually use the command line tool doilit to generate YAML that can be copy-pasted into the YAML header references list.
>>
>> doilit 10.1145/2975159 > foo.yaml
>> Then update the label that defaults to “a”, or use
>> doilit -h=JUPITER 10.1145/2975159 > foo.yaml
>> to set it from the command line.
>>
>> In my copious free time, I plan to issue an emergency update of kramdown-rfc that does not use bib.ietf.org for DOI.*.
>> Of course, I don’t know how quickly this then will be picked up on author-tools.ietf.org, so the timing before IETF 114 is going to be unfortunate in any case.
>>
>> Grüße, Carsten
>>
> 
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF LLC
kesara@staff.ietf.org

v2.23.0 | Report a Bug | By Email