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 ]
Greg L.
bgp2 at linuxadmin.org
Wed Aug 8 21:38:44 CEST 2007
I would say IPv4 anycast /24 PI must be allocated for anycasting DNS service only. You simply can't add more nameservers if you hit the max limit... The rules for IPv6 anycast allocations must be not that strict in the future... why? The address space will be more than enough, the router HW will be more powerful to handle large routing tables ... Sincerely, Greg L. >On Tue, Aug 07, 2007 at 08:36:06PM -0700, Greg L. wrote: > > Ps. If Ripe will allow anycast /24 PI allocation for syslog and ddos, and > > other UDP based services, then expect all free /24 blocks taken in a year > > or less for sure ;) > >So what's your message? Do you support handing out /24 PI for "these" >applications, or do you oppose it, due to address space / routing table >slots usage? > >Your e-mail was a bit unclear in that respect... > >Gert Doering > -- APWG chair >-- >Total number of prefixes smaller than registry allocations: 113403 > >SpaceNet AG Vorstand: Sebastian v. Bomhard >Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann >D-80807 Muenchen HRB: 136055 (AG Muenchen) >Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- 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 ]