>>>>> On Tue, 29 Mar 2005 07:46:01 -0800, >>>>> Bill Fenner <[email protected]> said:
> I usually think of the small home router configuration problem - > buy a box, plug it in, it wants you to configure it using a web > page, and it's probably fe80::1. With this type of usage, we would type, e.g., http://[fe80::1_de0]/ in "the URL bar" of our browser, right? Then the browser (parser) implementation would first extract "fe80::1_de0" and pass it to getaddrinfo(3) for converting it to an IPv6 address. So far, so good, but then the browser would also need to modify the entire URL to: http://[fe80::1]/ before sending it to the web server on the home router, since the "_de0" part is meaningless (or perhaps even harmful) for the remote server. This means the browser implementation, as well as getaddinfo(3), should understand the detailed meaning of the extended format for scoped IPv6 addresses. Indeed, this is exactly one of what we wanted to avoid in RFC4007: However, the typed URL is often sent on the wire, and it would cause confusion if an application did not strip the <zone_id> portion before sending. Note that the applications should not need to care about which kind of addresses they're using, much less parse or strip out the <zone_id> portion of the address. (Section 11.7) So, this example is not convincing to me to answer "YES" to the 0th question: 0. Should we solve this problem at all? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. [EMAIL PROTECTED] -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
