In your previous mail you wrote: A simple question. When would you ever use global source and destination addresses for a neighbor solicitation.
=> there is no real constraint on addresses, only some special cases (unspecified source and multicast destination). This keeps the door open for some optimizations. And why? => if the two neighbors initiate a direct communication using global addresses, to use global addresses in neighbor solicitation avoid to create context (aka neighbor cache entries) for both global addresses and link-local addresses. IMO, link local addresses must be used. => please don't shut doors on our fingers (:-)... But RFC 2461 does not say this. It just says an address configured to the interface. That can mean global addresses. I saw such a packet at Connectathon (going on in San Jose). => yes, local traffic usually is with global addresses in NSs, not local one uses nearly always link-locals because routers are known by their link-local addresses (some implementations even enforce link-local addresses in the gateway field of routes). Regards [EMAIL PROTECTED] -------------------------------------------------------------------- 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] --------------------------------------------------------------------
