RFC2223 mostly defines the function of the tag (providing a reference from an existing RFC to a new RFC) but doesn’t really provide clear rules. However, looking ad RFC2223 again now, I noted that in the intro text of section 12 it says a bit more than in the definition. The definition only says that the new RFC “cannot be used alone”. However, I don’t think that really capture the right aspect; any extension or usage guidance or such things cannot stand on its own. But, that’s what normative references are for. The intro text however says that:
"A document that merely updates an earlier document cannot stand on its own; it is something that must be added to or inserted into the previously existing document, and has limited usefulness independently.” By saying “added or inserted" I guess this suggests a more narrow usage, basically reflected by the question: would this new RFC be integrated into a new revision of the updated RFC? However, “updates" is used much broader than this and I believe there are people who would want to retain this broader use. Also it doesn’t align with current practice on how “updates” is already used in the RFC series. So I don’t think relying on this definition will help the problem, neither addressing people needs nor resolving the confusion that already exists in the RFC series. The sentence above would align with the proposed “amends” tag and that would make it more clear then in future uses. > On 7. Jul 2026, at 19:22, S Moonesamy <[email protected]> wrote: > > Hi Mirja, > At 05:28 AM 07-07-2026, Mirja Kuehlewind (IETF) wrote: >> For the "updates" tag no rules are written down anywhere. Without agreed >> rules is no way to apply it consistently. > > There are some instructions in RFC 2223 (Page 12). There are also some > instructions in draft-rfc-editor-rfc2223bis-08 (Page 13). > > Regards, > S. Moonesamy > -- > rswg mailing list -- [email protected] > To unsubscribe send an email to [email protected]
-- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
