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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 11 Jan 2014 05:06:10 -0800 (PST)
From:	Fran├žois-Xavier Le Bail <>
To:	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, Alexey Kuznetsov <> wrote:

> Hello!

> I am just curious: since when is TCP allowed to use anycast addresses?

As said in
(this informational draft is in RCF queue)

"  No firm conclusion was reached regarding
   use of TCP with anycasted services, but it was observed that
   anycasting was useful for DNS, although it did introduce some new

For this works, there is need for appropriate routing (BGP, ...).

Many DNS root-servers use TCP with anycast (IPv4 and IPV6).

see :

"   L-Root service is provided using a single IPv4 address (
   and a single IPv6 address (2001:500:3::42).  It should be noted that
   it is preferable to refer to the service using its DNS name (L.ROOT-
   SERVERS.NET) rather than literal addresses, since addresses can
   change from time to time."

Fran├žois-Xavier Le Bail
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