* Well, don't we want to say how this is supposed to work somewhere? I doubt this will take much time. The authors may want to, but could this be an independent submission, rather than WG item? It seems that the real goal here is to enable a specific scenario between a cloud provider and a search engine… Furthermore, it appears that the authors recommend against general-purpose TLS stacks implementing this:
* Recommended shall be set to no (N) Cheers, Andrei From: TLS <tls-boun...@ietf.org> On Behalf Of Watson Ladd Sent: Tuesday, April 2, 2024 10:37 PM To: Eric Rescorla <e...@rtfm.com> Cc: Christopher Patton <cpatton=40cloudflare....@dmarc.ietf.org>; TLS List <tls@ietf.org> Subject: [EXTERNAL] Re: [TLS] Adoption call for TLS Flag - Request mTLS On Tue, Apr 2, 2024, 5:08 PM Eric Rescorla <e...@rtfm.com<mailto:e...@rtfm.com>> wrote: Adoption should not be required to register a code point [0], as the policy is Specification Required. I'm mildly negative on adopting this document. What is the reason we need to spend WG time on this, rather than just having a code point assignment? Well, don't we want to say how this is supposed to work somewhere? I doubt this will take much time. -Ekr [0] As an aside the IANA considerations of draft-ietf-tls-tlsflags-13 should clearly have a policy which matches 8447 S 7, which is to say that an I-D is sufficient. On Tue, Apr 2, 2024 at 12:59 PM Christopher Patton <cpatton=40cloudflare....@dmarc.ietf.org<mailto:40cloudflare....@dmarc.ietf.org>> wrote: I'd like to see this problem solved. There was some discussion about whether an I-D is needed or all we needed was to register a code point somewhere. If most agree that an I-D is needed, then let's adopt it. I'm happy to review. Chris P. On Tue, Apr 2, 2024 at 12:22 PM Sean Turner <s...@sn3rd.com<mailto:s...@sn3rd.com>> wrote: At the IETF 119 TLS session there was some interest in the mTLS Flag I-D (https://datatracker.ietf.org/doc/draft-jhoyla-req-mtls-flag/); also, see previous list discussions at [0]. This message is to judge consensus on whether there is sufficient support to adopt this I-D. If you support adoption and are willing to review and contribute text, please send a message to the list. If you do not support adoption of this I-D, please send a message to the list and indicate why. This call will close on 16 April 2024. Thanks, Deirdre, Joe, and Sean [0] https://mailarchive.ietf.org/arch/msg/tls/9e2S95H9YgtHp5HhqdlNqmQP0_w/ _______________________________________________ TLS mailing list TLS@ietf.org<mailto:TLS@ietf.org> https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org<mailto:TLS@ietf.org> https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org<mailto:TLS@ietf.org> https://www.ietf.org/mailman/listinfo/tls
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
