Hi! The chairs have judged that there is consensus to request an early code point for this draft-ietf-tls-tlsflags. I will send a message to the DEs and IANA to get this code point assigned.
The following PR creates the TLS Flags sub-registry where we can manage the actual flags. I asserted that the chairs control adding values, which won’t be true once (and if) the registry goes to IANA (it’ll be the DEs: Rich, Nick, and Yoav), and populated the 1st value from the draft: resumption_across_names. Assuming this is good, I will merge the PR. spt > On Sep 27, 2024, at 15:00, Sean Turner <s...@sn3rd.com> wrote: > > Hi! We paused progression of draft-ietf-tls-tlsflags until we had > implementations. We (the chairs) have gotten requests for an early IANA code > point; if you remember draft-ietf-tls-cross-sni-resumption, a WG I-D that is > now expired, and draft-jhoyla-req-mtls-flag, a individual I-D, would both > need this code point. Note that like draft-ietf-tls-dtls-rrc, > draft-ietf-tls-tlsflags also creates a new sub-registry, but IANA cannot > create a temporary registry and then manage it for us. We will do that in the > WG/I-D; there is not much to manage because at this point it’s only two > values. With that said …. > > We (the Chairs) would like to determine whether there is consensus to request > an early code point request for "tls_flags” in the TLS ExtensionType Values > registry registry; see Section 4 of the I-D [0]. The point of this consensus > call is to determine whether you think this I-D is stable enough to request a > code point from the DEs. Please let the list know by 11 October 2024 if you > support this request. > > Cheers, > spt > (as TLS Co-Chair) > > [0] https://datatracker.ietf.org/doc/draft-ietf-tls-tlsflags/ _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
