Am 14.01.2021 um 14:53 schrieb Magnus Westerlund:
Hi,
On Wed, 2021-01-13 at 20:06 +0100, Julian Reschke wrote:
Am 13.01.2021 um 19:55 schrieb Ted Hardie:
...
While they could theoretically pre-assign it, the RFC Editor won't
publish the document without the documents actually being available for
retrieval. That's a big reason you get clusters. This is why we do
downrefs to the drafts; since there is an onward pointer from the
referenced draft to the final RFC in the tools, that's considered okay
as anyone who seriously wants the reference can readily find it. [Note:
my opinion on that is separate from my recitation of what I think the
facts are.]
...
Maybe we need a separate discussion about easily (or even
semi-automatically) updating published RFCs when their downrefs become RFCs.
Which isn't done at all. The main body of the RFC when published is inmutable.
Thus, if you want to align any language changes or anything with the new HTTP
specs when going for do a "downref" means a new RFC.
...
I understand that this is the current state of things - but it might
makes sense to discuss in the context of other conversations we'll
hopefully have about RFC "immutability".
(and yes, that doesn't help with the current problem)
Best regards, Julian
