-----Original Message----- From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of james woodyatt Sent: Tuesday, March 15, 2011 1:28 PM To: Markus Hanauska Cc: ipv6@ietf.org Subject: Re: Why has RFC 4941 been designed in such a way,that it might cause address conflicts?
>Duplicate Address Detection (DAD) is the mechanism by which address conflicts are resolved in IPv6. DAD as per RFC 4862 does not resolve conflicts but detects the conflicts. See section 5.4.5 which punts a duplicate detected event to the admin of the network to deal with. >If you set DupAddrDetectTransmits to zero on an interface where DAD is required to prevent address conflicts, then the network isn't required to work properly when you do that. If the subscriber >aggregation network by which you're connecting a mobile node to the Internet requires a DAD proxy to prevent address conflicts, and the DAD proxy is malfunctional, then you can expect damaged network >service as a result. Speaking of a mobile network (cellular) where it does make sense to set DupAddrDetectTransmits to zero since the hosts use p2p and hosts use the Modified EUI-64 format for Interface Identifier (IID) - see RFC 2472. Modified EUI-64 uses a global token to generate the IID and thus the IID is likely to be unique. Hemant -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
