@martinthomson > Of note is this [draft that recommends the use of .local names instead](https://datatracker.ietf.org/doc/html/draft-schinazi-httpbis-link-local-uri-bcp-03). This resolves the interface issues by using a name, which could be unique. Unfortunately, that requires the use of mDNS, which is not supported enough to be consistently available. I'm not sure where this comes from - while we certainly had issues back in 2010 with ISP routers defaulting to blocking of multicast traffic, that hasn't been the case for a long time now. Every major client OS (Android, ChromeOS, iOS, Linux, macOS, and Windows) supports mDNS out-of-the-box. Almost all network printers, TVs, and cameras support mDNS. My Ubiquity network gear, Lutron gateway, Nest thermostat and smoke detectors, NAS, VoIP phones, and new washer and dryer all support it as well. So maybe we need to note that while *some* network equipment might not (yet) support mDNS, the vast majority of it *does*. Using mDNS hostnames is a viable alternative to using link-local addresses in URIs, and has been for a long time now... -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/989#issuecomment-2344359194 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/989/2344359194@github.com>
Received on Wednesday, 11 September 2024 18:12:20 UTC