On Thu, Aug 23, 2012 at 11:11:04PM +0100, Nick Hilliard wrote:
On 23/08/2012 22:48, Nick Hilliard wrote:
RIPE NCC rights: - the right to charge for RIR services over and above those listed by the proposal as ERX holder rights
Apologies, I omitted the following:
- the right for the RIPE NCC to withdraw a basic service if and only if an equivalent other service is provided, potentially charging the ERX holder for the new service (section 5.1.2)
I think there may be a conflict in the proposal here between the proposed rights of the ERX holders (i.e. the NCC must provide the basic services as stated and must not coerce the ERX holder into paying in any circumstance), and this suggestion (the RIPE NCC may completely withdraw a specific service and replace it with something equivalent, and by doing so may potentially coerce the ERX holder into paying for the new service). Or did I read it incorrectly?
A possible issue one can infer from the outlined text is a future discussion about what comprises what the draft calles "basic services": the means for resource holders to maintain the registry data relating to their resources; publication, of this data and the provisioning of relevant delegation records in the reverse DNS. Variances of this topic are already an occasional matter of RIPE mailing lists discussions. Martin