IPv6 stacks responds to all node link local multicast NS

[Hiroki Sato]

prabhakar lakhera <prabhakar.lakhera at gmail.com> wrote
  in <CALg+rhVZFc=vE+nZS-hsm+Uc54kZwzO6N8qThG9uv+e-e2uh5w at mail.gmail.com>:

pr> This probably is more of a compliance issue (or may be not as the NS
pr> receipt section of RFC 4861 http://tools.ietf.org/html/rfc4861#page-62 does
pr> not talk about it).
pr>
pr> The neighbor solicitation message format says this:
pr>
pr> http://tools.ietf.org/html/rfc4861#page-22
pr>
pr>
pr>       Destination Address
pr>                      Either the solicited-node multicast address
pr>                      corresponding to the target address, or the target
pr>                      address.
pr>
pr>
pr> Is it safe to assume that this is a MUST?
pr> If yes, nd6_ns_input right now only checks if the destination is a
pr> multicast or not (the check is more strict for DAD NS packets) and
pr> therefore allows all node link local multicast address resolution NS
pr> packets and process them completely (creates neighbor cache, responds
pr> with NA etc).

 What is the problem when accepting NS messages to ff02::1?

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20141018/1a2d3c33/attachment.sig>