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 ]
Leo Vegoda
leo.vegoda at icann.org
Wed Aug 8 13:33:32 CEST 2007
Hi Greg, On 8 Aug 2007, at 23:15, Greg L. wrote: [...] > 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... What is the reasoning behind the minimum of five locations? Why would four be too few? Regards, Leo Vegoda
- 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 ]