cabo / kramdown-rfc

An XML2RFC (RFC799x) backend for Thomas Leitner's kramdown markdown parser
MIT License
195 stars 83 forks source link

Wrong link to subscribe to IRTF mailing lists using venue #246

Open kesara opened 1 day ago

kesara commented 1 day ago

(From: https://github.com/ietf-tools/author-tools/issues/550#issue-2675286901 (reported by @emanjon))

When using "venue:" in markdown, the link to subscribe to the CFRG mailing list is wrong. I assume this applies to all IRTF RGs but I have not checked. When using

venue: group: "Crypto Forum" type: "Research Group" mail: "cfrg@irtf.org" arch: "https://mailarchive.ietf.org/arch/browse/cfrg/" github: "sfluhrer/ml-kem-security-considerations" latest: "https://sfluhrer.github.io/ml-kem-security-considerations/draft-sfluhrer-cfrg-ml-kem-security-considerations.html"

or

venue: group: "Crypto Forum" type: "Research Group" mail: "cfrg@ietf.org" arch: "https://mailarchive.ietf.org/arch/browse/cfrg/" github: "sfluhrer/ml-kem-security-considerations" latest: "https://sfluhrer.github.io/ml-kem-security-considerations/draft-sfluhrer-cfrg-ml-kem-security-considerations.html"

The following non-existing link is used:

Subscribe at https://www.ietf.org/mailman/listinfo/cfrg/.

The correct link is

https://mailman.irtf.org/mailman/listinfo/cfrg

cabo commented 1 day ago

On 2024-11-21, at 01:10, Kesara Rathnayake @.***> wrote:

Subscribe at https://www.ietf.org/mailman/listinfo/cfrg/.

The correct link is

https://mailman.irtf.org/mailman/listinfo/cfrg

I see this as a redirect failure on www.ietf.org:

Kramdown-rfc always generates a link: https://www.ietf.org/mailman/listinfo/#{mail_local}/

Normally, www.ietf.org redirects this legacy link to the right place, but not here. (I don’t want to hardwire links into the mailman3 infrastructure yet, which might be brittle. Also, the links need to continue to work for old I-Ds, so the redirect will continue to be required on www.ietf.org.)

Grüße, Carsten

rjsparks commented 1 day ago

The issue here isn't with the redirects into mailman3 - its the question of whether the mailman frontend (it was, several years ago, all one instance) would respond to an irtf list name at the www.ietf.org/mailman endpoint. It likely did. We'll go look at the redirect plumbing to see why that's not following the evolution of www.irtf.org/mailman to mailman.ietf.org (whose redirects do work).