Bill Fenner wrote: > 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. I don't have any systems in my > house that have fewer than two non-loopback interfaces. Since > this is presumably a one-off, I guess the default interface > configuration is an option, if a little clumsy.
I don't understand this use case. Assuming I have a router and it's manual says type in http://<some-link-local-address><some-delimiter>de0/ it's going to fail on my Linux machine that uses eth0, and if it says use "eth0" it's going to fail on the other Linux machine that has eth1 on that network. Link local addresses (that include an interface identifier) don't make sense outside of the local machine, including in printed documentation. I don't think that URI's that don't make sense off a single machine are a good idea in general, but assuming that we do want this, are we expecting users to transcribe these addresses? how about just using (fe80::1,de0) as http://de0.1.0.0.0.0.0.0.0.fe80.fin6.arpa/ no special delimiters are needed, and it "looks" like a normal IP, normal software doesn't need to be upgraded to handle this format, libraries can be easily upgraded to support this format easily and shortcut the round trip to a DNS server, the fin6.arpa (forward in6) tree can be automatically populated with AAAA's on the fly for software that doesn't work, it can be easily cut and pasted between url's and applications that expect a "hostname". the only downside I see is that it's a pain to take an address (not a hostname) and make a hostname out of it (as you have to reverse it). -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
