Ben Schwartz <[email protected]> wrote: > Local SOCKS5 proxies are conventionally discovered via WPAD [1], which > returns a PAC file [2]. I'm no great fan of WPAD, but it is widely > implemented in browsers and OSes.
Yeah, that's not going to fly. } [1] https://datatracker.ietf.org/doc/html/draft-ietf-wrec-wpad-01 1) draft-ietf-wrec-wpad is a 22 year old ID which specifies use of a private-use DHCP option (252). While one think one can get away with an SRV entry, that requires local DNS to be working, which is exactly the kind of thing that IoT manufacturers are having trouble relying upon. (Yes, if a MUD controller is present, we can expect local DNS to be more reliable, but it is exactly in the opposite case that there is concern) 2) Once you find the CFile, according to the URL you dug up (Thank you. The link in the 22 year old ID is long dead) > https://developer.mozilla.org/en-US/docs/Web/HTTP/Proxy_servers_and_tunneling/Proxy_Auto-Configuration_PAC_file The PAC file is javascript? -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
