From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, christoph.paasch@uclouvain.be,
fx.lebail@yahoo.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next v2] IPv6: enable bind() to assign an anycast address
Date: Mon, 17 Feb 2014 20:25:15 +0100 [thread overview]
Message-ID: <20140217192515.GG22833@order.stressinduktion.org> (raw)
In-Reply-To: <20140217.141949.1387848185062797150.davem@davemloft.net>
On Mon, Feb 17, 2014 at 02:19:49PM -0500, David Miller wrote:
> From: Alexey Kuznetsov <kuznet@ms2.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@uclouvain.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
next prev parent reply other threads:[~2014-02-17 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 13:38 [PATCH net-next v2] IPv6: enable bind() to assign an anycast address Francois-Xavier Le Bail
2014-02-13 0:16 ` Hannes Frederic Sowa
2014-02-17 5:15 ` David Miller
2014-02-17 9:32 ` Christoph Paasch
2014-02-17 10:02 ` Alexey Kuznetsov
2014-02-17 19:19 ` David Miller
2014-02-17 19:25 ` Hannes Frederic Sowa [this message]
2014-02-17 19:42 ` François-Xavier Le Bail
2014-02-17 19:48 ` David Miller
2014-02-17 19:52 ` François-Xavier Le Bail
-- strict thread matches above, loose matches on Subject: below --
2014-01-13 16:59 Francois-Xavier Le Bail
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=20140217192515.GG22833@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fx.lebail@yahoo.com \
--cc=kuznet@ms2.inr.ac.ru \
--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).