-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10.05.2007 13:28, Jørgen Hovland wrote:
Only the organization hosting the DNS is eligible, i.e. a data centre operator who wants to provide hosting services is not eligible?
Not even with the existing policy.
This depends on the definition. If a network announce their /16 prefix world-wide and decide to assign a customer a /29 for the use of anycast, they are entirely free to do so. The internal routing for the /29 within this network obviously needs to be configured for anycast use directed to the closest of the 15 different datacenters. The /29 is of course not announced to dfz, only the aggregate /16 is.
Well, I was perhaps not precise enough. The existing DNS Anycasting Assignment policy is for dedicated Anycast assignments only for DNS Anycasting setups. Of course that doesn't mean that you can't anycasting others service, e.g. as you described above, but you cannot receive an own assignment for that. Tobias - -- Tobias Cremer M.A. IP Admin Engineer Cable & Wireless Telecommunication Services GmbH Landsbergerstr. 155 80687 Muenchen Germany Tel +49 89 926 99 0 -- FAX +49 89 926 99 180 -- COMNET 7 49 9169 Geschäftsführer Francois Goreux, Richard Pennal Amtsgericht München HRB 146 617 www.cw.com/de - -- Every message GnuPG signed -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGQxLyhC6y11CNwvcRAvCBAKCe1RZOdXFQPNGWAcWoiRlvOwrIHQCggqhE 5YCfUk3pqZoMJcfwd30KeUM= =+MuI -----END PGP SIGNATURE-----