[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1388731742.39393.YahooMailBasic@web125506.mail.ne1.yahoo.com>
Date: Thu, 2 Jan 2014 22:49:02 -0800 (PST)
From: François-Xavier Le Bail <fx.lebail@...oo.com>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki Yoshifuji <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH net-next v2] IPv6: add option to use Subnet-Router anycast addresses as source addresses
On Fri, 1/3/14, Hannes Frederic Sowa <hannes@...essinduktion.org> wrote:
On Thu, Jan 02, 2014 at 10:19:24PM -0800, François-Xavier Le Bail wrote:
>> Some setup may use a ping to Subnet-Router anycast
>> address and expect a reply to discover a unicast address
>> (not very secure, but ...).
>>
>> It is the reason why, I want to keep existing default.
> Yep, with pre-defined anycast address I actually meant the
> subnet router
> anycast address. We currently don't need to deal with more
> than that one:
> https://www.iana.org/assignments/ipv6-anycast-addresses/ipv6-anycast-addresses.xhtml
> As soon as this patch gets applied, we have to keep the knob stable
> in its semantic. So my proposal would be to change the knob to just
> control the behaviour of ping replies and also change its
> name to reflect this.
> Leave datagram sending with specific anycast address as
> source just open and
> don't protect it with this knob. Would that be a plan?
But service discovery may be done also with UDP, so I see the knob as a router policy:
It enable or not anycast source.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists