[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140217192515.GG22833@order.stressinduktion.org>
Date: Mon, 17 Feb 2014 20:25:15 +0100
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: David Miller <davem@...emloft.net>
Cc: kuznet@....inr.ac.ru, christoph.paasch@...ouvain.be,
fx.lebail@...oo.com, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [PATCH net-next v2] IPv6: enable bind() to assign an anycast address
On Mon, Feb 17, 2014 at 02:19:49PM -0500, David Miller wrote:
> From: Alexey Kuznetsov <kuznet@....inr.ac.ru>
> Date: Mon, 17 Feb 2014 14:02:02 +0400
>
> > Hello!
> >
> > On Mon, Feb 17, 2014 at 1:32 PM, Christoph Paasch
> > <christoph.paasch@...ouvain.be> wrote:
> >> I don't have strong opinions for or against this patch.
> >>
> >> I was only involved in the original thread because F-X claimed that
> >> draft-iab-anycast-arch-implications (now RFC 7094) allows the use of anycast
> >> addresses for TCP, which is not what RFC 7094 is saying. There is no
> >> recommendation concerning TCP in the RFC and the situation is rather unclear.
> >
> > The same is here.
> >
> > Using anycast as source or bind address, why not?
> >
> > Use of anycast with TCP? Logically impossible, ergo prohibited.
> > If someone wants to play with fire, the option can be left hidden behind
> > a sysctl disabled by default.
>
> Agreed.
If a knob seems necessary I would vote for per address flags on those
anycast addresses (via setsockopt and netlink) so an application can
decide itself if it wants to do so.
Greetings,
Hannes
--
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