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

[Carsten Bormann <[e-mail]>]

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 <[e-mail]> 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
>