I support this as well. As an implementer interested in providing an implementation, I would like to help progress draft-ietf-tls-tlsflags, but I cannot do so without a codepoint, so this seems necessary to break the deadlock.
On Fri, Sep 27, 2024 at 3:03 PM Bas Westerbaan <bas= 40cloudflare....@dmarc.ietf.org> wrote: > I support this. > > On Fri, Sep 27, 2024 at 9:00 PM 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 >> > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-le...@ietf.org >
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
