RE: To DAD or not to DAD?

["Pascal Thubert (pthubert)" <[e-mail]>]

Hello Erik;

Same here, option 3, both a and b. The scenarios that demand it are out
there already.

And now is not a good time for the beach anyway. So let's do real progress
before summer!

I'd note that 3a and 3b are largely different in appearance, but maybe not
in the solution space.
It sounds really bad in a split-join scenario to have all devices chat at
the same time to figure out what's going on.
Which boils down to some degree of centralization/reflection which in turn
could allow 3b quite naturally...

Cheers,

Pascal


> -----Original Message-----
> From: ipv6 [mailto:[e-mail]] On Behalf Of Fernando Gont
> Sent: mardi 24 février 2015 23:01
> To: Erik Nordmark; [e-mail]
> Subject: Re: To DAD or not to DAD?
> 
> Hi, Erik,
> 
> On 02/18/2015 04:46 PM, Erik Nordmark wrote:
> >
> > The key questions in the design team report was what to do about DAD.
> > But we haven't had any discussion on this on the list and I'd like to
> > get some feedback from the WG to we can move forward.
> >
> > The slides offered these options:
> > 1. Deprecate DAD - it is expensive and duplicates are not common 2.
> > Only send and receive DAD for manually configured addresses 3. Improve
> > DAD  3a. Better at detecting duplicates (partition-join, etc)  3b.
> > Less network and host impact (allow sleep schedule) 4. Do nothing a.
> > aka go to the beach ;-)
> 
> I'm all for option 3.
> 
> 
> > Given that the beach is kind of cold this time of year, we can remove
> > the 4th choice from the list.
> > More seriously, the WG needs to decide how to move forward with DAD.
> >
> > Would it be helpful to present draft-yourtchenko-6man-dad-issues in
> > Dallas? Or can we have an email discussion without/prior to such a
> > presentation?
> 
> I'd suggest to start email discussion prior to the f2f meeting such that
we can
> probably frame the discussion and then mke more progress during the f2f
> meeting.
> 
> Thanks,
> --
> Fernando Gont
> e-mail: [e-mail] || [e-mail] PGP Fingerprint:
> 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------