[address-policy-wg] IPv4 Maintenance Policy

This aspect of the policy regarding legacy holders needs clarification:

"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. 

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. 

> -----Original Message-----
> From: address-policy-wg-bounces at ripe.net [mailto:address-policy-wg-
> bounces at ripe.net] On Behalf Of Rob Blokzijl
> Sent: Friday, April 13, 2012 7:34 AM
> To: address-policy-wg at ripe.net
> Subject: [address-policy-wg] IPv4 Maintenance Policy
> 
> Dear Colleagues,
> 
>     on the agenda for the Adress Policy WG next week is a presentation
> of
>     a document titled "IPv4 Maintenance Policy", attached to this mail.
> 
>     This is a document that is slightly different from or usual type of
>     policy documents: it is an attempt to consolidate those policies and
>     practices that will still be relevant after the depletion of the
> IPv4
>     free pool.
> 
>     The aim is to have a consistent and complete collection of all
> things
>     relevant to IPv4 for the years to come.
> 
>     Read, digest, enjoy - and discuss :-)
> 
> Best regards,
> 
>     Rob Blokzijl