Well, we certainly can change it in 8446-bis. My put here would be: let's get consensus on the *semantics* we want for the various categories without worrying about the names (call them A, B, C, etc.) and then we can name them after.
-Ekr On Fri, Oct 29, 2021 at 2:14 PM Ira McDonald <blueroofmu...@gmail.com> wrote: > Hi Eric, > > Thanks for the background. I still sympathize with Hannes' point that > "Recommended" means "IETF Consensus". I have to explain this > too often in the insular automotive industry. > > But I certainly wouldn't write an RFC to change the title of a single > column in an IANA registry. I've been one of the Designated Experts > for the IANA Internet Printing Protocol (IPP) registry for 20 years and > we rename IANA fields as needed by a direct request to our IANA > folks (after consensus in the IEEE-ISTO Printer Working Group IPP > WG - successor to IETF IPP WG in the 1990s). > > Cheers, > - Ira > > > On Fri, Oct 29, 2021 at 3:18 PM Eric Rescorla <e...@rtfm.com> wrote: > >> Previous discussion is on this issue: >> https://github.com/tlswg/tls13-spec/issues/1214 >> >> On Fri, Oct 29, 2021 at 12:13 PM Salz, Rich <rs...@akamai.com> wrote: >> >>> >>> - I am actually not in favor of changing it to IETF Consensus. I >>> think these have different meanings. >>> >>> >>> >>> To be clear, I wasn’t expressing an opinion on whether or not to do >>> this, I was just showing folks how to start the change process. >>> >>
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
