- From: Lucas Pardue <lucaspardue.24.7@gmail.com>
- Date: Thu, 11 May 2023 01:32:03 +0100
- To: Martin Thomson <mt@lowentropy.net>
- Cc: ietf-http-wg@w3.org
- Message-ID: <CALGR9oY85T0MGxAjbUsdt41mynwf9fLXt_QS2xYna7jzWo4Dvg@mail.gmail.com>
+1 to adoption and hoping for eventual consistency across our CONNECTed world On Thu, May 11, 2023 at 1:17 AM Martin Thomson <mt@lowentropy.net> wrote: > Thanks for the reminder Tommy. > > I'm in favour of normalizing in this direction also. I hold little hope > that we'll eliminate CONNECT as an HTTP feature, but one can maybe dream of > it being possible some day. > > On Thu, May 11, 2023, at 09:57, Tommy Pauly wrote: > > Hello all, > > > > To bubble this up in people’s email inboxes — does anyone else in the > > WG have an opinion on adopting this document or not? > > > > Best, > > Tommy > > > >> On Apr 17, 2023, at 2:08 PM, David Schinazi <dschinazi.ietf@gmail.com> > wrote: > >> > >> I support adoption. > >> David > >> > >> On Sun, Apr 16, 2023 at 8:15 PM Tommy Pauly <tpauly@apple.com> wrote: > >>> Hello, > >>> > >>> This email starts a call for adoption on > draft-schwartz-httpbis-connect-tcp ( > https://www.ietf.org/archive/id/draft-schwartz-httpbis-connect-tcp-01.html). > As discussed at IETF 116, this document defines a mechanism to use extended > CONNECT (which supports paths and URI templates) for proxying TCP, akin to > the UDP proxying support in RFC 9298. This does not deprecate the original > use of CONNECT for TCP proxying. > >>> > >>> Please reply to this email to indicate if you support adopting this > document in this working group. > >>> > >>> The call will last for 2 weeks, and end on Monday, May 1. > >>> > >>> Best, > >>> Tommy > >
Received on Thursday, 11 May 2023 00:32:20 UTC