Suresh, > I would not say it is a problem with the deployment architecture. As I > said in mails to Thomas and Woj, the issue occurs in other deployment > architectures that need to use different prefixes over the same shared > L2 domain (e.g. WLAN AP with 2 SSIDs mapped into 2 VLANs on the fixed > side connected to the edge router).
This is not a helpful comment. Neighbor Discovery is simply not designed to operate cleanly in an environment where different PIOs are advertised to different clients over a shared LAN. The fact is, any protocol is based on underlying assumptions (whether stated explicitely or not). If you break those assumptions, but use the protocol anyway, the protocol may not work so well any more. E.g., try running TCP across a path where 50% of the packets are lost due to corruption. The problem with the deployment architecture at issue is that it has chosen to use RAs in such an environment. The fact that the same issue would occur on other deployments that made the same (broken) assumption, doesn't somehow mean the architecture isn't broken. Sheesh! Thomas -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
