Hi Doug and list, Doug Barton <do...@dougbarton.us> writes:
> On 06/29/2013 03:18 AM, Benedikt Stockebrand wrote: >> >> IPv4 doesn't have link-local addresses or anything similar (unless you >> want to consider 192.169/16 "similar" in this context). > > > https://tools.ietf.org/html/rfc3927 s/192\.169/169\.254/g Sorry, that was a long day. Anyway, Zeroconf implicitly assumes that a node has only one active physical interface; section 3.2 (Address Ambiguity) of RFC 3927 pretty much makes it plain that using multiple physical interfaces with Zeroconf addresses doesn't really work. IPv6 uses the scope ID for that purpose, either as fe80::1%eth0 (Unix interface name) or as fe80::1%11 (Windows interface number). Even more important however is probably the fact that the Zeroconf is aimed at applications in ad-hoc networks, while the link-local scope with IPv6 is really aimed at network layer functionalities, like ND and RD; applications should rarely if ever actually use it. Cheers, Benedikt -- Business Grade IPv6 Consulting, Training, Projects Benedikt Stockebrand, Dipl.-Inform. http://www.stepladder-it.com/
