Fwd: [address-policy-wg] 2007-02 New Policy Proposal (Change in IP Assignments for Anycasting DNS Policy)

Hi,

On Thu, May 10, 2007 at 01:28:02PM +0200, Jørgen Hovland wrote:
> 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.

Indeed, this could be a workable solution for entities that already
operate a large network, and would want to have all of the anycast
nodes inside their network ("under their direct control").

In that case, we don't need anything special policywise, as the whole
anycast setup would not be visible in the global routing system, and
we don't need special prefixes, etc. etc.

This isn't possible for most of the TLD operators (as they do not have
a large network, usually, but host their boxes at other networks, IXPs,
etc.) - but it might be a workable approach for service providers that 
just want to provide reliable DNS service, and do not want/need an
external routing table slot.

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  113403

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279