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 wrote:
> I support thi
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 ne
I support this.
On Fri, Sep 27, 2024 at 9:00 PM Sean Turner 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 n
HI! Just another reminder that we have an interim scheduled for Oct 1st @ 9am
Pacific time. I have uploaded the agenda:*
https://datatracker.ietf.org/doc/agenda-interim-2024-tls-01-tls-01/
Here is a link to the remote meeting instructions (it’s MeetEcho):
https://meetings.conf.meetecho.com/interi
To add a little more context about the interim ...
We are taking a step back to focus on the problem statement/space. As you can
see from the agenda items, we are going to tease out whether we can agree on a
problem statement and then wether we should try to solve that problem. As a
result, I
