Re: [whatwg/url] Support IPv6 zone identifiers (#392)

[RFC-5952](https://tools.ietf.org/html/rfc5952) mentions some of the problems that arise due to the flexibility of textual IPv6 addresses and the benefits of having a single, canonical textual representation. Given that zone IDs are opaque ASCII strings, I guess that no normalization can be applied to them, correct?

In other words, `[::1234%EN0]` and `[::1234%en0]` must considered distinct addresses, and URLs containing those addresses must also be considered distinct. It would seem unwise for an operating system to allow case-sensitive interface names, but I don't think it is technically banned as far as IPv6 is concerned.

This also means that the hostname in general would become case-sensitive, contrary to RFC-3986:

>  The host subcomponent of authority is identified by an IP literal
   encapsulated within square brackets, an IPv4 address in dotted-
   decimal form, or a registered name.  **The host subcomponent is case-
   insensitive.**

https://www.rfc-editor.org/rfc/rfc3986.html#section-3.2.2

> When a URI uses components of the generic syntax, the component
   syntax equivalence rules always apply; namely, that **the scheme and
   host are case-insensitive and therefore should be normalized to
   lowercase**.  For example, the URI <HTTP://www.EXAMPLE.com/> is
   equivalent to <http://www.example.com/>.

https://www.rfc-editor.org/rfc/rfc3986.html#section-6.2.2.1

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/392#issuecomment-1297293843
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/392/1297293843@github.com>