ability to set 2 different paths for links created

[alicerusso]

For the rfc2html output hosted on rfc-editor.org, ideally there would be 2 different paths depending on the input:

• For a link to an RFC: https://www.rfc-editor.org/rfc/
• For a link to an I-D: https://datatracker.ietf.org/doc/html/

Example of issue: rfc2html output https://www.rfc-editor.org/rfc/rfc8445.html#section-22.2
links to
https://www.rfc-editor.org/rfc/draft-ietf-mmusic-ice-sip-sdp-21 (which is 404).

For context: https://mailarchive.ietf.org/arch/msg/tools-discuss/GpSWwK8XhJmP7C7yoapmxVTxZ7A/

Scope: issue affects approx 1200 links to I-Ds in reference sections in RFC 7322 - RFC 8643 (html files on rfc-editor.org).

[rjsparks]

cc: @larseggert

[larseggert]

Yes, links to I-Ds should go to datatracker. And maybe the RFC Editor can stop hosting I-Ds then?

CC @JayDaley

[alicerusso]

To clarify, the URLs of the form https://www.rfc-editor.org/rfc/draft-foo-00 never worked; I-Ds were never hosted with that path. So, this enhancement request exists whether or not I-Ds are hosted on rfc-editor.org.

FWIW, there is a planned removal of the decades-old repo of I-D text files available from rfc-editor.org/in-notes/internet-drafts/. For over 5 years, the site links to datatracker for I-Ds (e.g., from the queue page).