Fwd: New Version Notification for draft-schwartz-modern-http-proxies-00.txt

Hi HTTP and MASQUE,

I haven't seen any responses to this draft notice in HTTPBIS, so I figured
I would stir the pot again.

This is a "connect-tcp" proposal, which has an idea that has come up
occasionally in MASQUE, plus it also defines a template form for an "HTTP
request proxy", as needed by OHTTP.  This is basically straightforward, but
there are a few notable design choices in -00:
* CONNECT-TCP allows multiple IP addresses to be specified, for Happy
Eyeballs and fallback.
* The port variable is named "tcp_port" instead of "target_port" to make
the template distinguishable from CONNECT-UDP.
* Recursive "HTTP request proxing" is not supported.  An alternate design
based on Binary HTTP Messages (RFC 9292) could support that...

Please review,
Ben Schwartz

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Fri, Oct 14, 2022 at 2:49 PM
Subject: New Version Notification for
draft-schwartz-modern-http-proxies-00.txt
To: Benjamin M. Schwartz <bemasc@google.com>



A new version of I-D, draft-schwartz-modern-http-proxies-00.txt
has been successfully submitted by Benjamin Schwartz and posted to the
IETF repository.

Name:           draft-schwartz-modern-http-proxies
Revision:       00
Title:          Modernizing HTTP Forward Proxy Functionality
Document date:  2022-10-14
Group:          Individual Submission
Pages:          10
URL:
https://www.ietf.org/archive/id/draft-schwartz-modern-http-proxies-00.txt
Status:
https://datatracker.ietf.org/doc/draft-schwartz-modern-http-proxies/
Html:
https://www.ietf.org/archive/id/draft-schwartz-modern-http-proxies-00.html
Htmlized:
https://datatracker.ietf.org/doc/html/draft-schwartz-modern-http-proxies


Abstract:
   HTTP proxying features have long been part of the core HTTP
   specification.  However, the core proxying functionality has several
   important deficiencies in modern HTTP environments.  This
   specification defines alternative proxy service configurations for
   HTTP requests and TCP connections.  These services are identified by
   URI Templates and designed for parallelism with DoH, MASQUE, and
   Oblivious HTTP.




The IETF Secretariat