From: David Miller <davem@davemloft.net>
To: nordmark@arista.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org, gilligan@arista.com,
hannes@stressinduktion.org
Subject: Re: [PATCH net-next v2] ipv6 addrconf: Implemented enhanced DAD (RFC7527)
Date: Wed, 30 Nov 2016 10:58:06 -0500 (EST) [thread overview]
Message-ID: <20161130.105806.461585801662945197.davem@davemloft.net> (raw)
In-Reply-To: <4936dca6-c55d-809e-a032-f78e23ce6b49@arista.com>
From: Erik Nordmark <nordmark@arista.com>
Date: Mon, 28 Nov 2016 15:26:05 -0800
> Implemented RFC7527 Enhanced DAD.
> IPv6 duplicate address detection can fail if there is some temporary
> loopback of Ethernet frames. RFC7527 solves this by including a random
> nonce in the NS messages used for DAD, and if an NS is received with
> the
> same nonce it is assumed to be a looped back DAD probe and is ignored.
> RFC7527 is enabled by default. Can be disabled by setting both of
> conf/{all,interface}/enhanced_dad to zero.
>
> Signed-off-by: Erik Nordmark<nordmark@arista.com>
> Signed-off-by: Bob Gilligan<gilligan@arista.com>"
> ---
>
> v2: renamed sysctl and made it default to true, plus minor code review
> fixes
This doesn't apply to net-next, please respin.
Also, please format your signoffs correctly, there must be a space
between your name and the <> enclosed email address.
I always wonder why people elide spaces when formatting text, is
there a global shortage of space characters that I am unaware of?
prev parent reply other threads:[~2016-11-30 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161128060811.1E49FD341C60@us153.sjc.aristanetworks.com>
2016-11-28 23:26 ` [PATCH net-next v2] ipv6 addrconf: Implemented enhanced DAD (RFC7527) Erik Nordmark
2016-11-30 15:58 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161130.105806.461585801662945197.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gilligan@arista.com \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=nordmark@arista.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).