>> >>=> The router doesn't need to know the host's route table, it knows which >> address it included in its RAs, which is what the host records. >> I'm not sure why you think that there is no way the router can construct >> that message reliably. If it uses the same address it uses for its RAs, >>it >> can construct the message. > >Ah. Well, that will certainly help, but consider a situation where there >are no RAs,
=> Where is that situation possible/deployed? It's hard to consider something that is against the spec you're commenting on :) >or the host has a manual static route. Arguably misconfigured, I know, >but if we have that situation a router cannot know what address the host >was sending to, only that it is one of its own. For that matter, there >may be many RAs being generated through that interface, and do we >necessarily know which it was that caused the host/peer to route through >us? => Well, it depends on your implementation I guess. If your router randomly assigns src addresses to RAs with arbitrary prefixes then I can see where it would get confusing very quickly. But if they're doing it in a structured way it will work. That's why I raised a comment against your premise of "no way to do it reliably". There is definitely a way to do it reliably. Hesham -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
