Only half facetiously, should we propose a new RFC type which does malicious compliance for downstream SDOs and agencies which "need" an RFC, and is entirely parameterized boilerplate?
Status: Informational (or new: IANA Registration Acknowledgement) Authors: IANA Registrar or RFC Editor or something This RFC acknowledges that $DRAFT_VANITY_CRYPTO_xy registers codepoints in "$IANA_REGISTRY". Per [RFC8126], $DRAFT_VANITY_CRYPTO_xy has been reviewed by a designated expert and is considered a permanent and readily available public specification, in sufficient detail so that interoperability between independent implementations is possible. Other than this, the authors of $DRAFT_VANITY_CRYPTO_xy are solely responsible for that document's contents. Publication of such an RFC would require an SDO or other agency liaison statement specifying $DRAFT_VANITY_CRYPTO_xy and $IANA_REGISTRY after the codepoints have been assigned, and the rest would be auto-generated by someone at the IETF. The liaison statement is required to demonstrate actual desire for the RFC. Daniel ________________________________ From: Rob Sayre <[email protected]> Sent: Wednesday, February 25, 2026 5:56 PM To: Ben Schwartz <[email protected]> Cc: <[email protected]> <[email protected]> Subject: [TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt On Wed, Feb 25, 2026 at 9:38 AM Ben Schwartz <[email protected]<mailto:[email protected]>> wrote: I think part of the underlying problem here is that using an expired individual draft as a "stable specification" feels extremely unsatisfying, even when it is explicitly permitted: It is not only that it is unsatisfying. As I'm sure you know, when you get up to "Senior Staff" or "Principle Engineer" levels at a big company, "industry-level impact" is usually in there. A consensus RFC (even if Informational) does show this. So there's a financial impact for the authors. Martin has the expiry part here: https://martinthomson.github.io/no-expiry/draft-thomson-gendispatch-no-expiry.html I agree with that draft, but I don't think it will solve these issues. thanks, Rob
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
