[address-policy-wg] RIPE Access Policy Change Request to allow allocations to critical infrastructure

Hi,

On Fri, Jan 23, 2004 at 02:15:33PM +0100, Joao Damas wrote:
> >>IPs around until you have a clean /24 for this sort of use.
> >>Last, Gert missed the point by reducing the discussion to only the /24
> >>that would be used for the service IP, because with anycast you will
> >>always need a different IP address to be able to access each of the
> >>anycast instances,
> >
> >To the contrary.  *This* can (and should) be done with PA space,
> 
> It may or it may not be possible. When anycasting a service you want to 
> keep the origin ASN the same, so you need your own routing 
> infrastructure, separating your anycasted equipment from that of the 
> rest of the net.  This means that the management addresses will be 
> inside that separate routing infrastructure and so your statement "can 
> and should" can not and should not be made a pre-condition.

This is certainly one way to setup things.

But even so there is no reason not to use PA space for the management 
side of things - announcing the PA block to your host network, if you 
feel like having to announce the management IPs somewhere, but no reason
to pollute the global table with local information.

> >Strong disagreement.
> See above

Indeed :-)

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  58081  (57882)

SpaceNet AG                 Mail: netmaster at Space.Net
Joseph-Dollinger-Bogen 14   Tel : +49-89-32356-0
80807 Muenchen              Fax : +49-89-32356-299