We need to create a new entry in the CELLAR documents https://datatracker.ietf.org/wg/cellar/documents/

@robUx4, thanks for starting this work. I'm not good at generating the EBML specifications, but I did poke around a bit.

If I could make a couple of suggestions (which you may have already taken care of - my apologies, if so):

• I'd suggest using draft-ietf-cellar-rfc8794-corrections as the output file name. Unless @mcr has "other thoughts" ("spencer-corrections"?), I don't see that we need to go through the "post as individual and see if the working group adopts it, and then rename" shuffle.
• It is going to be much easier to take this draft through the approvals process, at some point in time, if you actually cut-and-paste the text being modified, and then the complete text with corrections, for each correction, using "OLD" and "NEW" to prefix them, just as we would for errata (if we were doing the RFC errata process). If you're correcting a sentence in the middle of a paragraph, show the entire paragraph (OLD and NEW), so that it's obvious to the reader where this text is in the document.
• If you can summarize in a sentence or two about why the original text needs to be corrected, that would be very helpful. I see something like that (I think!), so thank you for that.
• Just looking at the corrections listed so far - I see that https://www.rfc-editor.org/rfc/rfc8141.html obsoletes RFC 2141, but I'm not seeing that RFC 2141 has been deprecated (unless I'm missing it). Is the goal here to make use of extensions that are allowed in RFC 8141 (https://www.rfc-editor.org/rfc/rfc8141.html#appendix-B),, or just to use the current version of the standards-track URN specification? Either way, we should talk about who deprecated RFC 2141, or change the wording to Obsolete.

• done
• OK, alhtough for the XML Schema it may look a bit odd
• will do
• use RFC 8141 instead of deprecated RFC 2141 #389 mentions deprecated but it's just obsolete. maybe we don't really need this change ?

Given how RFC errata work, I opted to keep updating the current document with changes, so it can be diff'ed with the current RFC to produce the errata text.

There is now an rfc8794 branch that collects all the errata so we can regenerate a plain with these errata applies.