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

On 21 Jan, 2004, at 14:03, Gert Doering wrote:

> Hi,
>
> On Wed, Jan 21, 2004 at 01:48:16PM +0100, Joao Damas wrote:
>> In addition, in some cases, this can be worked around by moving 
>> service
>> 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.

> as for
> any other machine round the world that needs remote access.  There is
> nothing special about the administrative IP, so there is *no* need to
> do *anything* special in the policy here.
>
>> and as for the service /24, some people may be able
>> to work around this using address space they already have and some 
>> will
>> not, so any policy discussion needs to take into account both
>> requirements as they are not independent.
>
> Strong disagreement.
>

See above

Joao