On May 27, 2010, at 09:54, Brian Zill wrote: > > [...] > Typically, any reasonable protocol that uses link-local addresses will learn > any peer's addresses by receiving packets from that peer on that particular > link. The protocol will then keep both the link-local address *and* the > scope-id for that address for later use in contacting that peer. > [...]
And this is where I step in and mention that both <http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns> and <http://tools.ietf.org/html/draft-cheshire-dnsext-dns-sd> comprise an excellent and field-proven example of such a protocol, and I hope it isn't too controversial to suggest that it's worth looking to, at least, for inspiration. Of course, one hopes those drafts will emerge from IESG review sometime before the they're old enough to buy whiskey. -- james woodyatt <[email protected]> member of technical staff, communications engineering -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
