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, 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. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 58081 (57882) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299