Re: [Masque] New Version Notification for draft-schwartz-masque-access-descriptions-03.txt

[Tommy Pauly <[e-mail]>]

Thanks for sharing, Ben!

I appreciate the simplifications. I wonder if we can go a bit further and not include DoH, since that also seems to be a bit of an odd one out, but we can discuss that more.

If we have this scoped to the use case of “I know a URL or hostname for proxying, but I don’t know how to get the right URL for TCP vs UDP vs IP proxying”, then I think that can work in MASQUE.

I see that one of the ways to fetch this is off a well-known URI — something we should try to avoid adding more of, if possible, although we’ve gone down that road for UDP and IP. How are you imagining clients would fetch this JSON in the case they are not using a well-known? Would it be something where clients would be configured with a specific URL that only gets them access to the access description? Or could clients request this content type from some proxy URL they know (let’s say they just know a connect-udp URL and want to check for connect-ip…)?

Thanks,
Tommy



> On Oct 18, 2022, at 1:35 PM, Ben Schwartz <bemasc=[e-mail]> wrote:
> 
> Hi MASQUE,
> 
> At the last meeting, I presented a simple JSON blob format for representing multiple related proxyish services.  I recall the following feedback:
> 
> * This format is trying to do too many different things.
> * Configuration of all these things is not in-charter for MASQUE.
> * We need a better explanation of how this can be used for access-controlled services.
> 
> In this version, I've made the following changes:
> 
> * Removed any mention of Oblivious HTTP.
> * Added support for HTTP request proxies and TCP proxies (via "Modern HTTP Proxies" [1]).
> * Added instructions on how to use this format with access-controlled proxies (via "Popup Authentication" [2]).
> 
> Hopefully this makes the purpose and utility of the draft clearer.
> 
> I would like to present this draft at IETF 115.  Perhaps the chairs can advise whether MASQUE, HTTPBIS, or DISPATCH would be the best venue.
> 
> Please review,
> Ben Schwartz
> 
> [1] https://datatracker.ietf.org/doc/draft-schwartz-modern-http-proxies/
> [2] https://datatracker.ietf.org/doc/draft-schwartz-httpapi-popup-authentication/
> 
> ---------- Forwarded message ---------
> From: <[e-mail] <mailto:[e-mail]>>
> Date: Tue, Oct 18, 2022 at 4:25 PM
> Subject: New Version Notification for draft-schwartz-masque-access-descriptions-03.txt
> To: Benjamin M. Schwartz <[e-mail] <mailto:[e-mail]>>
> 
> 
> 
> A new version of I-D, draft-schwartz-masque-access-descriptions-03.txt
> has been successfully submitted by Benjamin Schwartz and posted to the
> IETF repository.
> 
> Name:           draft-schwartz-masque-access-descriptions
> Revision:       03
> Title:          HTTP Access Service Description Objects
> Document date:  2022-10-18
> Group:          Individual Submission
> Pages:          6
> URL:            https://www.ietf.org/archive/id/draft-schwartz-masque-access-descriptions-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-schwartz-masque-access-descriptions/
> Html:           https://www.ietf.org/archive/id/draft-schwartz-masque-access-descriptions-03.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-schwartz-masque-access-descriptions
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-schwartz-masque-access-descriptions-03
> 
> Abstract:
>    HTTP proxies can operate several different kinds of access services.
>    This specification provides a format for identifying a collection of
>    such services.
> 
> About This Document
> 
>    This note is to be removed before publishing as an RFC.
> 
>    Status information for this document may be found at
>    https://datatracker.ietf.org/doc/draft-schwartz-masque-access-
>    descriptions/.
> 
>    Source for this draft and an issue tracker can be found at
>    https://github.com/bemasc/access-services.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> -- 
> Masque mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/masque