- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 25 Nov 2024 23:28:25 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 November 2024 07:28:29 UTC
From @rmisev: > This definition is obscure: it is not clear how to convert a 128-bit integer to a list of pieces and vice versa. Also, all algorithms use an IPv6 address as a list of pieces, not as a 128-bit integer. By the way, RFC4291 defines an IPv6 address slightly differently: "IPv6 addresses are 128-bit identifiers...". From @domenic: > I can see how it's "conceptually" a u128, or "corresponds to" a u128, but in practice every part of the spec treats it as a list of 8 u16s. This came up in #838. --- If we want to change this we should probably look at how the various IETF specifications deal with IPv6 addresses again as we wouldn't want to define a type here that couldn't be reused in those layers of the stack. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/839 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/issues/839@github.com>
Received on Tuesday, 26 November 2024 07:28:29 UTC