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 ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Wed Aug 8 14:05:31 CEST 2007
Greg L. wrote: > > > Leo: > > >>> 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? > > > No problem, it was just a suggestion. I remember reading email in the > list with 8+ disperse location requirement. So, we are rolling the dice again to come up with another "magic", arbitrarily chosen figure which is supposed to discriminate between those who "qualify" and those which don't? > Greg > IIRC, we spent a lot f effort recently to get rid of one of those magic numbers in one policy... IMHO, anycast becomes anycast, as opposed to unicast, as soon as you've got more than one, i.e. 2 (two) - or more. Right? Wilfried.
- 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 ]