Re: [Mipshop] Re: New revision of draft-ietf-mipshop-fmipv6-rfc4068bis
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mipshop] Re: New revision of draft-ietf-mipshop-fmipv6-rfc4068bis
Hi Rajeev,
Rajeev Koodli wrote:
I was only providing the design rationale..
In sum, a) proxy ND is used to defend an address like in an HA (it could
also be used to maintain a pool of duplicate-free addresses for which
the protocol provides a transport message for), and b) DAD could be
turned off depending on specific deployment consideration (i.e., address
collision is not an issue)
I think this should be explained in more detail. How about the
following?
The NAR checks if the address is unique before starting
defending it. The NAR sends a DAD (neighbor solicitation) message
for the NCoA to check if the address is unique on the NAR link.
If there are other mechanisms by which the NAR can figure out if
the address is unique or if it is known that the probability of
collisions is very low or non-existent, then the parameter
DupAddrDetectTransmits is set to 0 on the NAR.
Vijay
_______________________________________________
Mipshop mailing list
Mipshop at ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.