On Fri, 2013-04-12 at 09:52 -0400, Brian Haberman wrote: > > Coming late to this but - DAD NS frames are sent to solicited node > > multicast addresses, so how is the first hop router seeing them? > > What am I missing? > > The proxy would have to maintain a list of nodes being proxied. In that > case, the proxy can join the solicited-node multicast address for those > nodes.
I'm still missing something then. How does the BNG build the list? I just re-read the draft and can see no mechanisms mentioned except snooping on DAD (which won't work except unless the proxy is already listening on the relevant SNMA) and unsolicited NAs. Nor is there any statement in the draft (for example in the "data structures" section, 4.1) that the proxy should join any solicited node multicast groups. Solicited node multicast addresses are mentioned in only two places: In section 3.1, which describes DAD in a misleadingly rather vague way under the circumstances (DAD packets go to "other nodes on the same link"), and in section 4.2.2 only in a negative sense (a case where a packet "other than a solicited Neighbor Advertisement" is received). Apologies if I'm missing something really obvious. Humbly asking for enlightenment :-) Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (ka...@biplane.com.au) http://www.biplane.com.au/kauer http://twitter.com/kauer389 GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017 -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
