On Oct 30, 2025, at 06:12, Julian Reschke <[email protected]> wrote: > >> Or -you know- when it breaks on them. This is not the most important >> software we're talking about :) >> ... > > Well.
Indeed; the ability to author and publish I-Ds and RFCs *is* somewhat important to the IETF and the other streams. > And you're sure that there will be somebody around to fix these? Looking at https://github.com/ietf-tools/bibxml-service/issues/489 (not an RFC reference, but indicative of the velocity with which we are handling this kind of problem), I’m not so optimistic. > Also, will XML reference files change? If they do, re-generating HTML for > existing RFCs will yield different content. Published RFCs don’t have external references, so they will stay on RFC%04d if using that now. It’s fun to look at existing RFCs. Quick check: The oldest one that references RFC20 that I can quickly find is rfc4592 (from 2006), the newest one rfc9720 (2025). The oldest one that references RFC0020 appears to be rfc4627 (also 2006), the newest one rfc9804 (also 2025). So I’m not worried about us introducing any inconsistencies :-) The important part of this discussion is timelines. When do we expect to have moved all places that somehow constitute dependencies from RFC%04d to RFC%d, so we can throw the big switch on the software that somehow depends on this? Will this be a big flag day, or will we have the chaos monkey for a few months? And will this happen before RFC1nnnn is published? (At nearly 200 RFCs per year, and with RFC 9890 the highest number published and RFC-to-be 9904 the highest number allocated today, that will be right after IETF 125, no?) Grüße, Carsten _______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
