Ekr (and others from off-list msgs), Don’t worry the chairs are paying attention.
And, yeah we’ll need to start something formal, but this thread is doing its job for now. BTW since we’d talked to Devon and Co. a lot about this I-D, I took inclusion of that phrase as a slip of the tongue so to speak. But, going forward a “hey are you interested in my I-D” emails shouldn’t read “hey I’m kicking off a WG adoption call” ;) spt > On Apr 29, 2024, at 09:43, Eric Rescorla <e...@rtfm.com> wrote: > > Hi folks, > > I haven't yet formed an opinion on this document yet, but I did want to > observe that calls for adoption are issued by the chairs, not by individual > participants. Of course, anyone can start a thread and comments in this > thread are information for the chairs, but if adoption does happen, it will > be via some separate process. > > -Ekr > > > On Sat, Apr 27, 2024 at 11:42 AM Brendan McMillion > <brendanmcmill...@gmail.com> wrote: > Hi Devon > > I support adoption > > On Fri, Apr 26, 2024 at 7:38 PM Andrei Popov > <Andrei.Popov=40microsoft....@dmarc.ietf.org> wrote: > I support adoption. > > Cheers, > > Andrei > > -----Original Message----- > From: TLS <tls-boun...@ietf.org> On Behalf Of Watson Ladd > Sent: Friday, April 26, 2024 7:13 PM > To: Devon O'Brien <asymmetric=40google....@dmarc.ietf.org> > Cc: tls@ietf.org; Bob Beck <b...@google.com> > Subject: [EXTERNAL] Re: [TLS] WG Adoption for TLS Trust Expressions > > On Tue, Apr 23, 2024 at 1:39 PM Devon O'Brien > <asymmetric=40google....@dmarc.ietf.org> wrote: > > > > After sharing our first draft of TLS Trust Expressions and several > > discussions across a couple IETFs, we’d like to proceed with a call for > > working group adoption of this draft. We are currently prototyping trust > > expressions in BoringSSL & Chromium and will share more details when > > implementation is complete. > > > > > > As we mentioned in our message to the mailing list from January, our > > primary goal is to produce a mechanism for supporting multiple subscriber > > certificates and efficiently negotiating which to serve on a given TLS > > connection, even if that ends up requiring significant changes to the draft > > in its current state. > > > > > > To that end, we’re interested in learning whether wg members support > > adoption of this deployment model and the currently-described certificate > > negotiation mechanism or if they oppose adoption (and why!). > > We absolutely need to solve the problem and the draft is a good starting > point. > > > > > > > Thanks! > > > > David, Devon, and Bob > > > > > > _______________________________________________ > > TLS mailing list > > TLS@ietf.org > > https://www/. > > ietf.org%2Fmailman%2Flistinfo%2Ftls&data=05%7C02%7CAndrei.Popov%40micr > > osoft.com%7C6ca75aa932344f322d9f08dc665fa375%7C72f988bf86f141af91ab2d7 > > cd011db47%7C1%7C0%7C638497808164901299%7CUnknown%7CTWFpbGZsb3d8eyJWIjo > > iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C% > > 7C&sdata=2n8iljUXBtb4Jf%2FZTqN2Nl5j81WoatTYA64c5%2FRoH0A%3D&reserved=0 > > > > -- > Astra mortemque praestare gradatim > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
