> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner- > [EMAIL PROTECTED] On Behalf Of Bound, Jim > > The solution that will work for now is make a statement in the > IETF and in industry IPv6 implementation documentation that > link-local addresses SHOULD not be used as an IPv6 address > type by applications. That link-local addresses SHOULD not be > included in the DNS. That link-local adddresses SHOULD be > restricted to IETF protocols on Hosts to perform Neighbor > Discovery, Stateless Address Configuration, DHCPv6, or other > operation protocols to bring a Host up on a network. The bottom > line is link-local address are not usable for applications. > > Would like to hear what my colleagues in IETF IPv6 WG think > about this issue?
Networks can be formed ad-hoc. I meet two friends, and all three of us want to use our laptops to play a networking game, or maybe exchange files. In the absence of a router (for RA) or a DHCPv6 server, we all will be forced to use link-local addresses. It might not be that difficult to use the link-local addresses, if there were a "network neighborhood" kind of application existed which would detect all the nodes on the network, maybe even gets their name using NI queries, and somehow pass (maybe /etc/hosts) the hostnames to the applications. Convenience will any day override IETF statements. We might be better off if we develop an API through which the kernel can inform the applications about an ambiguous address. A call to connect() could return EAMBIGUOUS. Ofcourse, this error will only happen if the user did not specify the scope. Comments? CP -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
