2007-01 - Phase 3 Draft Procedures & Call For Feedback
As announced during the RIPE NCC Services Working Group session at RIPE 60, the RIPE NCC will provide the RIPE community with a draft procedure for Phase 3 of the policy implementation for "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".
Please note that the draft document describes an internal RIPE NCC procedure and is provided for informational purposes.
If you have any feedback for the RIPE NCC regarding the procedure for Phase 3 of the policy implementation, please send an email to enduser-contract _at_ ripe _dot_ net.
This procedure document describes the steps to be taken for holders of independent Internet number resources who have not signed an End User Assignment Agreement with either a sponsoring Local Internet Registry (LIR) or the RIPE NCC regarding independent Internet number resources assigned to them before or during Phase 2 of the policy implementation "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region".
In October 2008, the RIPE community accepted a policy change which states that a contractual relationship must be established between an End User and a sponsoring LIR or the RIPE NCC before the End User can receive independent Internet number resources (AS Numbers, PI address space, Anycast assignments or IPv6 Internet Exchange Point (IXP) address space). This policy also states that it applies to all independent Internet number resources previously assigned to an End User by the RIPE NCC or by a RIPE NCC LIR.
In order to fulfil its mandate as manager of Internet number resources and to implement this policy, the RIPE NCC requires End Users to have a contractual relationship in place with either a sponsoring LIR or directly with the RIPE NCC.
The procedures listed in this document are subject to RIPE Policies.
In Phase 3 of the policy implementation of "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region", the RIPE NCC will contact all holders of independent Internet number resources for which the required documentation was not submitted by a sponsoring LIR or who have not signed a RIPE NCC End User Assignment Agreement during Phase 2 of the policy implementation. This means holders of resources that are marked as one of the following at the end of Phase 2 of the policy implementation will be contacted:
- Not My End User
- My End User (but the LIR has not submitted the required documentation by the end of Phase 2)
- Not marked
The RIPE NCC will contact the resource holders based on their contact details registered in the RIPE Database. Different levels of contact details ("admin-c:", "tech-c:", "mnt-by:", etc.) will be used to ensure reasonable attempts are made to reach the resource holder. The method of contact will be email.
The RIPE NCC will contact resource holders in batches to ensure the provided feedback can be processed in a timely manner. The visibility of the resources in the global routing table and the results from the previous batches will be taken into account when planning and prioritising the next batch runs.
The RIPE NCC will email the resource holders a link to a web interface where they can give feedback and updates regarding the status of the independent Internet resources assigned to them. In order to implement this policy, the RIPE NCC must know whether the resource holders still exist and can be reached using the contact information registered in the RIPE Database. This makes it necessary to monitor the activity on the webpages and keep logs of the activities due to the possible consequences if resource holders fail to provide feedback within the given time period. End Users will also be able to contact the RIPE NCC directly by email in case they need assistance during this process.
Resource holders will have to reply to the questions listed below:
a) Still a contact person for the resource?
The contacted persons can inform the RIPE NCC if they are the responsible contact for the resource.
b) Email address for future contact?
The resource holder/contact person can provide a main contact email address and will also be asked to update the contact details in the RIPE Database accordingly.
c) Resource used for resource holder's network infrastructure?
Independent Internet number resources can only be used for the network infrastructure of the organisation the resources are assigned to.
d) Resource used by another organisation?
If the resources are in use by another organisation, the contact persons can provide more information about the current resource user, including their contact details.
e) Resource holders who (now) operate a LIR can provide their LIR's regid.
It is possible that an organisation later became an LIR after independent Internet number resources were assigned to them. In such cases, the resources can be moved to the resource holder's registry and approved as resources used for the LIR's network infrastructure.
f) Resource holders have the option to become a Direct Assignment User (DAU) and sign a RIPE NCC End User Assignment Agreement.
If a resource holder cannot find or cannot sign an agreement with a sponsoring LIR for special reasons, they also have the option to become DAU and sign a RIPE NCC End User Assignment Agreement regarding the independent Internet resources assigned to them. More information on how to become a DAU and the fee structure involved.
g) Information if the resource holder has already entered or will soon enter a contractual relationship with a sponsoring LIR and provide the LIR's details.
Resource holders are free to choose with which LIR they will sign an agreement.
Please note that resource holders can also check with their ISPs whether they operate as an LIR, in which case they can also sign an End User Assignment Agreement with that ISP.
Should the End User not react within three months and several attempts by the RIPE NCC to contact the resource holder, including reminders by email and using different contact details registered in the RIPE Database related to the resource, the RIPE NCC will:
- Change the maintainers on the End User’s records to the status “deregistered maintainer”; and/or
- Add a warning statement to the relevant records in the RIPE Database mentioning the upcoming deregistration of the resources; and/or
- Withdraw the reverse delegation; and/or
- Contact the upstream to investigate possible hijacking of resources; and/or
- Delete all relevant objects in the RIPE Database including aut-num/inetnum and route objects
Should the End User confirm with the RIPE NCC that they will sign an agreement with a sponsoring LIR, but the agreement is not provided to the RIPE NCC within three months of that confirmation, then the RIPE NCC will also start