Re: [TLS] Request mTLS Flag

2023-11-17 Thread Viktor Dukhovni
On Fri, Nov 17, 2023 at 09:57:42AM +, Peter Gutmann wrote: > Viktor Dukhovni writes: > > >Indeed, Postfix 3.9 (release estimated Q1 '2024), when compiled against > >OpenSSL 3.2 (release estimated circa next week), will automatically signal > >client certificate types X.509(0) and RPK(2) iff

Re: [TLS] Early IANA Allocations for draft-ietf-tls-dtls-rrc

2023-11-17 Thread Salz, Rich
>> I assume you are concerned about the ContentType registry. I think it's okay >> to add something here. > Yes that’s the one. I mean we have 240+ spaces, but it is technically one of > our more scarce spaces. Yes but I still think it's fine. >> I missed the detail about the RRC Message Type

Re: [TLS] Early IANA Allocations for draft-ietf-tls-dtls-rrc

2023-11-17 Thread Sean Turner
> On Nov 15, 2023, at 14:12, Salz, Rich wrote: > > I assume you are concerned about the ContentType registry. I think it's okay > to add something here. Yes that’s the one. I mean we have 240+ spaces, but it is technically one of our more scarce spaces. > I missed the detail about the RRC

Re: [TLS] TLS chair update: Deirdre Connolly replacing Christopher Wood

2023-11-17 Thread Deirdre Connolly
Thanks Paul! Happy to contribute.  On Fri, Nov 17, 2023, 7:33 AM Paul Wouters wrote: > Hi everyone, > > At the IETF we try to change chairs regularly for a variety of reasons. We > like to encourage new participants to gain chairing experience alongside > more experienced chairs. This also

[TLS] TLS chair update: Deirdre Connolly replacing Christopher Wood

2023-11-17 Thread Paul Wouters
Hi everyone, At the IETF we try to change chairs regularly for a variety of reasons. We like to encourage new participants to gain chairing experience alongside more experienced chairs. This also prevents ossification of WGs :) Christopher Wood has stepped down as TLS WG chair and Deirdre

Re: [TLS] Request mTLS Flag

2023-11-17 Thread Peter Gutmann
Viktor Dukhovni writes: >Indeed, Postfix 3.9 (release estimated Q1 '2024), when compiled against >OpenSSL 3.2 (release estimated circa next week), will automatically signal >client certificate types X.509(0) and RPK(2) iff and only a client >certificate is configured (available). Could this