This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Wed Jun 13 10:53:01 CEST 2007
On Wed, 13 Jun 2007, Sander Steffann wrote: > Can you give more details of how this works with anycast? I am > interested in examples of non-DNS anycast applications. In the past > there have been questions about which protocols/applications other than > DNS can benefit from anycasting, and you seem to be the first with a > concrete example. IRC uses a single TCP session and several IRC networks have deployed anycast as a way to limit amount of clients that can potentially ddos a single server. It seems to routing subsystem is stable enough for most users that even long lived TCP sessions as IRC (that might be up for weeks) work well with anycast. It works best with regionally limited announcements though, as these tend to be more stable (direct peering relationships between ISPs). -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]