From: Sabrina Dubroca <sd@queasysnail.net>
To: David Miller <davem@davemloft.net>
Cc: dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: allow userspace to add IFA_F_OPTIMISTIC addresses
Date: Wed, 28 Feb 2018 00:22:18 +0100 [thread overview]
Message-ID: <20180227232218.GA2574@bistromath.localdomain> (raw)
In-Reply-To: <20180227.104708.1983037304358643327.davem@davemloft.net>
2018-02-27, 10:47:08 -0500, David Miller wrote:
> From: Sabrina Dubroca <sd@queasysnail.net>
> Date: Tue, 27 Feb 2018 15:13:28 +0100
>
> > 2018-02-26, 12:11:27 -0500, David Miller wrote:
> >> From: Sabrina Dubroca <sd@queasysnail.net>
> >> Date: Mon, 26 Feb 2018 17:56:19 +0100
> >>
> >> That's completely different to this case, which is a bonfide explicit
> >> allowance for userspace to take over these fundamental protocol tasks
> >> from the kernel.
> >
> > This is not letting userspace take over. On the contrary, it allows
> > userspace to take advantage of the kernel's DAD, without suffering the
> > delay. The alternative, without optimistic DAD, would be to completely
> > disable DAD done by the kernel.
> >
> > This follows RFC 4429, which explicitly allows optimistic DAD for
> > addresses generated by (among other mechanisms) DHCPv6.
>
> Fair enough.
>
> We can resume this conversation if and when problems pop up in the
> future :-)
Hehe :)
Thanks, I'll submit a v2 with the changes (the other) David asked for.
--
Sabrina
prev parent reply other threads:[~2018-02-27 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 16:43 [PATCH net-next] ipv6: allow userspace to add IFA_F_OPTIMISTIC addresses Sabrina Dubroca
2018-02-20 17:25 ` David Ahern
2018-02-20 18:17 ` Sabrina Dubroca
2018-02-21 20:34 ` David Miller
2018-02-26 15:41 ` Sabrina Dubroca
2018-02-26 15:57 ` David Miller
2018-02-26 16:56 ` Sabrina Dubroca
2018-02-26 17:11 ` David Miller
2018-02-27 14:13 ` Sabrina Dubroca
2018-02-27 15:47 ` David Miller
2018-02-27 23:22 ` Sabrina Dubroca [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=20180227232218.GA2574@bistromath.localdomain \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.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).