- From: Josh Cohen <joshco@gmail.com>
- Date: Mon, 8 Jul 2024 20:34:36 -0400
- To: int-area@ietf.org, ietf-http-wg@w3.org
- Message-ID: <CAF3KT4QFxgNK=kLw_jZ06B85-3sUXqHmHQK03i-jWOZS-jCszw@mail.gmail.com>
Greetings, I've submitted a new draft of Web Proxy Automatic Discovery Next Generation (WPADNG) https://www.ietf.org/archive/id/draft-joshco-wpadng-01.html *Changes:* I've removed the old DNS A TXT, SRV discovery mechanisms The current discovery mechanisms are DHCP (v4/v6), and DNSSD. In terms of priority it is DHCP then DNSSD. For DNSSD the key is new _wpadng._tcp.example.com. DNS "devolution" remains, eg: first "dev.example.com" then "example.com" I've added the use of a URN for the proxy config URI to indicate "there is no proxy and stop discovery" to prevent discovery of rogue proxies. *I'm seeking feedback on the following:* Is the priority of DHCP, DNSSD best? For DNSSD, is domain devolution common practice? Eg, eg: first " dev.example.com" then "example.com". If not, what are other common practices to deal with subdomain scenarios? For DNSSD and DHCPv6, we can include more than just a URL, since we have key/value pairs in DNSSD and from my read, it looks like there is room to do the same for DHCPv6. Is there other information the client should know that we should add? Are there other URNs that we should add? -- --- *Josh Co*hen
Received on Tuesday, 9 July 2024 00:34:51 UTC