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/[email protected]/
[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 23:50:58 CEST 2007
> > > Who needs a new /24 PI if you are only going to implement DNS anycast in > > your own network? > > I was speaking about global DNS anycast /24 PI allocation with min. ~5 > > disperse locations / networks, verified later by running traceroutes to > > see ASN, data path etc... >[...] >... and it shouldn't be linked to running ccTLD-Servers. Neither in IPv4 >nor in IPv6. Sure it shouldn't. ccTLD DNS hosting requirement for /24 PI anycast assignment already forces small companies into unfair competence with LIR members and big guys. Sincerely, Greg LinuxAdmin.org
- 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 ]