From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [RFC] IPV6 address management
Date: Thu, 8 Jan 2009 13:44:02 -0800 [thread overview]
Message-ID: <20090108134402.6e88438f@extreme> (raw)
In-Reply-To: <20090108.125830.142298950.davem@davemloft.net>
On Thu, 08 Jan 2009 12:58:30 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Thu, 8 Jan 2009 12:12:20 -0800
>
> > What about this?
> >
> > If it works (still testing), I'll submit it.
>
> So what is your plan?
>
> Make the routing daemons depend upon the non-default
> behavior in order to act correctly?
routing daemons don't deal with addresses directly now,
and getting them to do it would be painful.
> Or is it to gradually get people to use the non-default
> (via distribution sysctl settings etc.) and eventually
> make it the default?
No plan to ever change the default. Just ship with sysctl.conf
setting.
> I disagree with both plans, and with that the facility
> is basically useless.
>
> We absolutely have to live with the behavior we have now,
> and for a long time if not forever.
next prev parent reply other threads:[~2009-01-08 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 17:34 [RFC] IPV6 address management Stephen Hemminger
2009-01-08 19:24 ` David Miller
2009-01-08 20:12 ` Stephen Hemminger
2009-01-08 20:58 ` David Miller
2009-01-08 21:11 ` Ben Greear
2009-01-08 21:44 ` Stephen Hemminger [this message]
2009-01-08 21:51 ` David Miller
2009-01-08 21:56 ` Stephen Hemminger
2009-01-08 21:58 ` David Miller
2009-01-08 22:01 ` Stephen Hemminger
2009-01-08 22:03 ` David Miller
2009-01-08 22:56 ` Stephen Hemminger
2009-01-09 1:14 ` [PATCH] ipv6: address preservation on link down Stephen Hemminger
2009-01-09 8:02 ` Rémi Denis-Courmont
2009-01-09 17:31 ` Stephen Hemminger
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=20090108134402.6e88438f@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--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 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).