lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 11 Jan 2014 06:07:04 -0800 (PST)
From:	Fran├žois-Xavier Le Bail <>
To:	Christoph Paasch <>
Cc:	Alexey Kuznetsov <>,,
	Hannes Frederic Sowa <>,
	"David S. Miller" <>,
	James Morris <>,
	Hideaki Yoshifuji <>,
	Patrick McHardy <>
Subject: Re: [PATCH net-next] IPv6: enable TCP to use an anycast address

On Sat, 1/11/14, Christoph Paasch <> wrote:

>> On 11/01/14 - 05:06:10, Fran├žois-Xavier Le Bail wrote:
>> On Sat, 1/11/14, Alexey Kuznetsov <> wrote:
>> As said in
>> (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.

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.


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists