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
Thu Jun 14 16:16:06 CEST 2007
On Thu, 14 Jun 2007, Gert Doering wrote: > Hi, > > On Wed, Jun 13, 2007 at 10:53:01AM +0200, Mikael Abrahamsson wrote: >> 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. > > Can you point me to some documentation for that? Or some prefixes that > have been used for anycasting IRC servers? > > I'm really curious how well that works. 194.68.45.0/24. Afaik there are no official documentation. I ran an EFnet irc-server off of a similar /24 for a couple of years and it worked very well. We only announced it to peering partners in scandinavia though, so it was quite limited in announcement. Solved the ddos problem very nicely back then, though. What you cannot reach you cannot ddos. -- 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 ]