[address-policy-wg] IPv4 Maintenance Policy

On 04/19/2012 04:42 PM, Milton L Mueller wrote:
> "Leave data as it is in the RIPE Registry. The Legacy Resource Holder will not be able to add to or alter their data and will not have access to any RIPE NCC services such as reverse delegation and certification."
> 
> It is likely that in response to this policy legacy holders will choose to use an alternate registrar for the services you are precluding them from using (e.g., reverse delegation and certification). In that case RIPE NCC will need to negotiate an interoperability or interconnection agreement with these service alternate providers to ensure that a globally applicable unique registration occurs. 

the space referred to is allocated to (or administered by if you prefer) ripe. reverses for this space are delegated to ripe (one single exception with no relevance to this subject). alternate service providers can't delegate from this space.

to choose an alternate provider for reverse delegation, the ip space in question will have to be returned, and a new allocation (from the alternate reverse delegation provider) will have to be done.
would work nicely: the 'legacy' is removed, the user will get a normal new allocation. everyone should be happy with such a case.

all this aside: you seem to try to express the 'threat of competition'. ripe isn't a business. there is no competition. ncc coordinates for the community, that's all. in case of users where it's actually an option to choose between some rirs, it's not important to ripe whether he chooses ripe or some other rir. actually, if this user chooses a different rir, the result is less work for ncc, and more free space for ripe.

on the other hand, dropping the paragraph or the whole legacy paragraph is probably best anyway.

> If RIPE NCC is not willing to do that, it appears to be attempting to leverage its monopoly to force legacy holders into purchase and use of their services, something that raises obvious competition policy issues. I wouldn't advise you to do down that path. 

community ip coordination isn't a business.

regards,

	Chris