>>>>> On Fri, 27 Feb 2004 16:15:30 +0900,
>>>>> "S. Daniel Park" <[EMAIL PROTECTED]> said:
>> > And even with single id and new prefix this is not good: on
>> > RA with a new global prefix, every node on the link is going to do
>> > DAD based on its ID and new prefix. And, as far as I know,
>> > there is no delay requirement here, so everyone is doing it at
>> > same time.
>>
>> Hmm, this is a good point. An obvious workaround is to impose a
>> random delay when the node is starting a DAD process for an address
>> configured by multicasted RA.
>>
>> Does this kind of additional requirement make sense? > all
>> If so, should we include this in rfc2462bis?
> no change in the main sentence but add an appendix (or
> something) to discuss the issue on the random delays of
> the multiple RAs...but isn't bound for multi6 ?
We may be able to address this issue as a future extension in an
appendix. But please note that the problematic case can happen even
for a single RA (in that sense, there is no direct connection to
multi6).
p.s. I've registered a separate issue for this on the issue tracker.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
