All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bram Bonné" <brambonne@google.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
	hannes@stressinduktion.org, netdev@vger.kernel.org,
	Lorenzo Colitti <lorenzo@google.com>,
	Jeffrey Vander Stoep <jeffv@google.com>
Subject: Re: [RFC PATCH] ipv6: Use dev_addr in stable-privacy address generation
Date: Fri, 27 Mar 2020 12:50:07 +0100	[thread overview]
Message-ID: <CABWXKLwamYiLhwUHsb5nZHnyZb4=6RrrdUg3CiX7CZOuVime7g@mail.gmail.com> (raw)
In-Reply-To: <20200326.114550.2060060414897819387.davem@davemloft.net>

On Thu, Mar 26, 2020 at 7:45 PM David Miller <davem@davemloft.net> wrote:
> I think the current behavior is intentional in that it's supposed to use
> something that is unchanging even across arbitrary administrator changes
> to the in-use MAC address.

Thank you for your feedback David.

Could you help me understand the use cases where the admin / user
chooses to use MAC address randomization, but still wants an IPv6
link-local address that remains stable across these networks? My
assumption was that the latter would defeat the purpose of the former,
though it's entirely possible that I'm missing something.

  reply	other threads:[~2020-03-27 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  9:42 [RFC PATCH] ipv6: Use dev_addr in stable-privacy address generation Bram Bonné
2020-03-26 18:45 ` David Miller
2020-03-27 11:50   ` Bram Bonné [this message]
2020-03-27 13:06     ` Hannes Frederic Sowa
2020-03-27 17:15       ` Bram Bonné
2020-03-27 20:51         ` Hannes Frederic Sowa
2020-04-03 14:40           ` Bram Bonné
2020-03-27 22:46     ` David Miller

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='CABWXKLwamYiLhwUHsb5nZHnyZb4=6RrrdUg3CiX7CZOuVime7g@mail.gmail.com' \
    --to=brambonne@google.com \
    --cc=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=jeffv@google.com \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=lorenzo@google.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.