[TLS] Re: Consensus Call: early code point request for draft-ietf-tls-tlsflags
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 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 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
[TLS] Consensus Call: early code point request for draft-ietf-tls-tlsflags
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] Re: Consensus Call: early code point request for draft-ietf-tls-tlsflags
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 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] Re: TLS Interim (was Re: interim-2024-tls-01 interim approved)
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/interim/?group=f3d0d4f9-2480-4bdc-8a2d-4765d8aedd73 See you then! spt * Thanks Chris! > On Sep 17, 2024, at 12:18, Sean Turner wrote: > > Hi! Another reminder that we have a virtual interim scheduled for 2024-10-01 > @ 9am Pacific time. We are still working out the details but the topic is > Trust Expressions / Trust Anchor Transition. > > Cheers, > spt > >> On Sep 10, 2024, at 13:33, Sean Turner wrote: >> >> Hi! We have scheduled a virtual interim to discuss Trust Expressions / Trust >> Anchors Transition. We are in the process of defining some ground rules for >> the meeting as well as setting some expected outcomes, but we wanted to get >> the interim on the calendar. >> >> Cheers, >> spt >> >>> On Sep 10, 2024, at 13:31, IETF Meeting Session Request Tool >>> wrote: >>> >>> >>> An interim meeting for tls has been approved or does not require additional >>> approval. >>> A message has been sent to the secretariat requesting the interim be >>> announced. >>> >>> >>> - >>> Working Group Name: Transport Layer Security >>> Area Name: Security Area >>> Session Requester: Sean Turner >>> >>> Meeting Type: Virtual Meeting >>> >>> Session 1: >>> >>> Date: 2024-10-01 >>> Start Time: 12:00 America/New_York >>> Duration: 03:00 >>> Remote Participation Information: >>> https://meetings.conf.meetecho.com/interim/?group=f3d0d4f9-2480-4bdc-8a2d-4765d8aedd73 >>> Agenda Note: >>> >>> - >>> >> > ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
[TLS] Re: TLS Interim (was Re: interim-2024-tls-01 interim approved)
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 retitled the topic in the agenda to be “Trust Tussle” to better reflect what we are actually going to discuss. Feel free to read the I-Ds we discussed at IETF 120, draft-davidben-tls-trust-expr and draft-beck-tls-trust-anchor-ids, for background but we are not planning on discussing the I-Ds specifically. Cheers, spt > On Sep 27, 2024, at 13:37, Sean Turner wrote: > > 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/interim/?group=f3d0d4f9-2480-4bdc-8a2d-4765d8aedd73 > > See you then! > > spt > > * Thanks Chris! > >> On Sep 17, 2024, at 12:18, Sean Turner wrote: >> >> Hi! Another reminder that we have a virtual interim scheduled for 2024-10-01 >> @ 9am Pacific time. We are still working out the details but the topic is >> Trust Expressions / Trust Anchor Transition. >> >> Cheers, >> spt >> >>> On Sep 10, 2024, at 13:33, Sean Turner wrote: >>> >>> Hi! We have scheduled a virtual interim to discuss Trust Expressions / >>> Trust Anchors Transition. We are in the process of defining some ground >>> rules for the meeting as well as setting some expected outcomes, but we >>> wanted to get the interim on the calendar. >>> >>> Cheers, >>> spt >>> On Sep 10, 2024, at 13:31, IETF Meeting Session Request Tool wrote: An interim meeting for tls has been approved or does not require additional approval. A message has been sent to the secretariat requesting the interim be announced. - Working Group Name: Transport Layer Security Area Name: Security Area Session Requester: Sean Turner Meeting Type: Virtual Meeting Session 1: Date: 2024-10-01 Start Time: 12:00 America/New_York Duration: 03:00 Remote Participation Information: https://meetings.conf.meetecho.com/interim/?group=f3d0d4f9-2480-4bdc-8a2d-4765d8aedd73 Agenda Note: - >>> >> > ___ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
