Re: [w3ctag/design-reviews] Entering IPv6 Zone Identifiers in User Interfaces (Issue #989)

Keeping in mind that I know very little about the details of IPv6:
* It does seem unfortunate to lack a unified URL syntax to express this sort of IP address.
* That said, since these URLs can only be interchanged between programs within a single node, they're arguably not part of the _Web's_ architecture, and so outside of the TAG's scope. (Right? IP addresses that can be interchanged within a local network would use a prefix other than `fe80:`?)
* Entering a local device address into a browser _is_ a sensible use case. That doesn't prove that it's worth implementing given the complications, but I don't see a reason to question that some users would find value in doing that.
* It's not clear to me how many and what kind of users this affects. Is it mostly technical users interacting with specialized hardware? Novice users trying to configure their router? Only users with multiple network cards? (Seems like Linux's lack of a default zone eliminates that last one, but maybe this is a Linux bug rather than a URL bug.) I think we'd need to know more about who we're leaving behind in order to judge whether it's worth supporting on the web platform. 
* Even if the TAG were convinced, to actually get it supported in browsers, the browser developers would need to be convinced to prioritize it. It seems like browsers have several possible paths to supporting this sort of IP address, even without changes to the URL standard. For example, they could provide a devtools interface to specify a default zone, or they could allow defining petname hosts that map to particular IP addresses.
* I don't think I know enough about the problems with deploying mDNS to be able to judge whether it makes more sense.

So, overall, I don't feel like the TAG should raise any objections to @becarpenter's draft. But I could easily be missing something.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/989#issuecomment-2342605311
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/989/2342605311@github.com>