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] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Erik Lindqvist
kurtis at kurtis.pp.se
Tue Jan 20 20:07:56 CET 2004
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joao, On 2004-01-20, at 16.50, Joao Damas wrote: > This goal could very well be achieved by keeping the addresses of the > servers you are already using and migrating all other active IP's out > of the /24 that contains the address you want to "anycast". After all, > none of the root servers that are anycasting today have renumbered > (one that is not anycasting today will renumber soon because they > can't apply what I just described, which was unfortunate). > This was actually spelled out as a problem with NEW services (TLDs) moving to anycast. That is people who do not have their own addresses at all at this point. Best regards, - - kurtis - -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 iQA/AwUBQA18j6arNKXTPFCVEQKIgQCfdI0l1TMNy2mmCWtP/umLcpr23K0An2FL J7KQTOTKYhprMKX9QV7sutrO =1b17 -----END PGP SIGNATURE-----
- Previous message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]