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] Re: PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] Re: Revising Centrally Assigned ULA draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mattias Ahnberg
mattias at ahnberg.pp.se
Thu Jun 14 20:00:13 CEST 2007
> DALnet announces the same prefix in several places in an identical > fashion as the one I described. So no, it's not anycast as it's not > globally reachable. Other than 194.68.45.0/24 that can't be reached from anywhere we also have another netblock (194.14.236.0/24) that CAN be reached from everywhere i.e. more "true anycast". The obvious problem we face is ofcourse when a server dies and a user ends up on another one and the first comes back again they will be disconnected from the latter and forced onto the first. We're not very bothered by this compared to the advantages it gives us. For others it may be too bad of a setup, ofcourse. -- /ahnberg.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] Re: Revising Centrally Assigned ULA draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]