[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1389449224.4533.YahooMailBasic@web125506.mail.ne1.yahoo.com>
Date: Sat, 11 Jan 2014 06:07:04 -0800 (PST)
From: François-Xavier Le Bail <fx.lebail@...oo.com>
To: Christoph Paasch <christoph.paasch@...ouvain.be>
Cc: Alexey Kuznetsov <kuznet@....inr.ac.ru>, netdev@...r.kernel.org,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
"David S. Miller" <davem@...emloft.net>,
James Morris <jmorris@...ei.org>,
Hideaki Yoshifuji <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH net-next] IPv6: enable TCP to use an anycast address
On Sat, 1/11/14, Christoph Paasch <christoph.paasch@...ouvain.be> wrote:
>> On 11/01/14 - 05:06:10, François-Xavier Le Bail wrote:
>> On Sat, 1/11/14, Alexey Kuznetsov <kuznet@....inr.ac.ru> wrote:
>> As said in http://tools.ietf.org/html/draft-iab-anycast-arch-implications-12.html#section-2.1
>> (this informational draft is in RCF queue)
> This draft does not say that TCP should be used with anycast
> addresses. Rather the opposite:
> " This document does not treat in any depth
> the fact that there are deployed services with TCP transport using
> anycast today. Evidence exists to suggest that such practice is not
> "safe" in the traditional and architectural sense (as described in
> Section 4.2). "
> And Section 4.2 gives more information.
> http://tools.ietf.org/html/draft-iab-anycast-arch-implications-12.html#section-4.2
The draft say there are use cases for TCP with anycast services.
The DNS use case is widely deployed in real word.
I think enabled such possibility in Linux kernel is useful.
It's only a possibility for such use cases and it's dont break usual TCP usage.
Francois-Xavier
--
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