Re: [Efficientnd-dt] Update to dad-issues draft

[Erik Nordmark <[e-mail]>]

I've done some updates based on the below comments plus the ones on the 
list.

I think the draft is good enough to be submitted but other comments are 
welcome.

    Erik

On 2/26/15 11:59 PM, Eric Vyncke (evyncke) wrote:
> Erik and Andrew,
>
> Some quick comments:
> - in intro: add xref to RFC 2460, worth to copy the description of DAD
> mechanism in your document if not too long? Also introduce the DAD acronym
> early in the intro
> - 2.3 should explicitly mention wireless? Should mention the I-D regarding
> the use/abuse of mcast traffic by NDP?
> - I like the classification by groups of issues rather than the long list
> - 3.2 in case of duplicate address, not only TCP is impacted. If the new
> host (with colliding address) does not listen on UDP port X while the old
> one does, then ICMP port unreachable will be sent which could have
> undesirable consequences
> - 4.3 readability/clarity could be improved, esp paragraph 4
> - 4.5 s/anywhere/anyway/ ?
>
> Hope it helps
>
> -éric
>
>
> On 27/02/15 07:52, "Erik Nordmark" <[e-mail]> wrote:
>
>> Andrew and I have made some updates to the dad-issues draft, mainly to
>> order the list to make it more clear which issues remain, which are
>> already (being) solved and which are more observations about DAD.
>>
>> Comments welcome,
>>      Erik
>>
> _______________________________________________
> Efficientnd-dt mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/efficientnd-dt
>