[Rfc-markdown] DOI.* references semibroken

Carsten Bormann <cabo@tzi.org> Wed, 06 July 2022 04:45 UTC

Return-Path: <cabo@tzi.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 06055C15C6A7 for <rfc-markdown@ietfa.amsl.com>; Tue, 5 Jul 2022 21:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 jcNd6JRfqiaL for <rfc-markdown@ietfa.amsl.com>; Tue, 5 Jul 2022 21:45:06 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 34106C14CF0B for <rfc-markdown@ietf.org>; Tue, 5 Jul 2022 21:45:04 -0700 (PDT)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Ld6R044qrzDCcB; Wed, 6 Jul 2022 06:45:00 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Wed, 06 Jul 2022 06:44:59 +0200
Message-Id: <B2E8B010-548C-49DB-9AEB-FAAC6F3CC302@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/jsnSsOoDNTFkEA4YPfAn7NrYK4o>
Subject: [Rfc-markdown] DOI.* references semibroken
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 04:45:10 -0000

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