RE: 6MAN Adoption call on raft-chakrabarti-nordmark-6man-efficient-nd-04

[Samita Chakrabarti <[e-mail]>]

Hi Lorenzo:

Mikael>  This would be a big win, especially if it could be done with minimal changes to the clients.

You don't need to modify ND to do that, though. You can defend against that sort of attack by having the ND implementation:

1. Prioritize preserving ND cache entries over making new address resolution attempts.
2. Glean ND cache entries from DAD packets (and if need be, NS/NA packets), and prioritize those gleaned entries over new address resolution attempts.

Some of these measures are documented in RFC 6583.
[SC>]
[SC>] I understand that you have a view point.  But  there are  many folks/vendors who have expressed interest/supported this work, see a need to improve ND  as it has operational issues for IPv6 deployment on large scale, wireless switches, virtualized environments. RFC 6583 (mentioned above) discusses ND operational issues and tips for implementation. There are number of drafts, RFC and pieces discussing improvements on different ND usecases and scenarios. It does not help implementers to understand and deploy Ipv6 ND easily in many scenarios – including M2M, wireless phones, monitoring cameras and so on. A revised/improved ND is needed for IPv6.
We started on this draft  sometime ago, after an IOT IAB workshop where  people felt that clearly there is a need to clarify IPv6 ND behavior to 1) reduce multicast messages 2) allow removal of DAD in some situations 3) allow registration of nodes for reliable ND operation when multicast is reduced.
There are some real wireless and  wired  deployments which will benefit if the ND registration/optimization for IPv6 is specified in one document as a standard without affecting the legacy ND implementations or deployment. [ Check out the appendix section]

Our solution is looking into minimal changes to the clients and most of the changes are in the Router implementation and  some implementations already exist through RFC6775 – however that does not directly address IPv6 legacy networks. So the purpose is to provide options to a section of Ipv6 enabled devices/routers/servers that can optionally implement efficient-ND behavior to improve their Ipv6 networks (single hop LAN).

I know we can clarify these in the document and improve the text to be precise going forward.
-Samita