cabo
Wrong link to subscribe to IRTF mailing lists using venue
(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: "[email protected]" 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: "[email protected]" 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
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
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).
Indeed the issue is that right now www.ietf.org/mailman/* gets redirected to mailman3.ietf.org/... . Mailman3's UI (postorius) doesn't show non-ietf lists at the ietf domain the way mailman2 would.
New IRTF lists will never have had a working www.ietf.org/mailman/acronym style URL.
The solution we are likely to pursue to preserve old links is to put an explicit, static, list of redirects in for old non-ietf group acronyms to their stream domain (e.g. mailman3.irtf.org).
Please consider starting to use the mailman3.{domain}.org variants, or perhaps point to the datatracker to find the lists for the drafts.
On 23. Nov 2024, at 00:11, Robert Sparks @.***> wrote:
Please consider starting to use the mailman3.{domain}.org variants, or perhaps point to the datatracker to find the lists for the drafts.
For the future, sure.
(There are quite a few I-Ds out there still referencing the old URLs, so the idea of a static mapping would be good.)
How can datatracker find the lists for me? Or is there a stable URI that I can compute from the mail address?
Grüße, Carsten