To request independent resources, you will first need to find a sponsoring LIR who will maintain the necessary contractual relationship with the RIPE NCC and ensure the correct registration of any independent resources. More information on sponsoring LIRs can be found in “Contractual Requirements for Provider Independent Resource Holders.”
If you would like to request resources for your own infrastructure without going through a sponsoring LIR, you will need to become a member of the RIPE NCC.
The RIPE NCC stopped issuing IPv4 Provider Independent (PI) address
space in September 2012.
Provider independent resources are independent from any LIR. This means that you can change your sponsoring LIR at any time. To do this, you will need to complete the following steps:
*The sponsoring LIR can draft their own agreement as long as it meets the requirements.
In the event that your company name changes, you will need to inform your sponsoring LIR. The sponsoring LIR will then contact the RIPE NCC regarding the name change and send us legal documents confirming the name change.
The LIR can initiate the End User name change procedure by submitting a request with the required documents via the LIR portal.
This will allow us to update the independent resource objects in the RIPE Database and ensure that all records are up-to-date.
Independent resources that are no longer needed should be returned to the RIPE NCC. To do this, you can inform your sponsoring LIR.
Your sponsoring LIR will then contact the RIPE NCC regarding the changes and provide us with your written confirmation on the return of the specific resources.
Your LIR can initiate the return procedure by submitting a request with the required confirmation attached via the LIR portal.
This will enable the RIPE NCC to delete the independent resource objects from the RIPE Database and place the resources back into the free pool for reallocation.
If you want to add a maintainer, or change the admin-c or tech-c information for an independent resource object in the RIPE Database, you will need to ask the current maintainer of the object (mnt-by:) to make the updates for you.
If the current maintainer is not able to make the changes, your sponsoring LIR will need to contact the RIPE NCC on your behalf.
The RIPE community develops and sets policies through a long established, open, bottom-up process of discussion and consensus-based decision making. The RIPE Policy Development Process (PDP) is open to everyone to propose changes to current policies or propose new ones.
To participate, you should register on the respective working group mailing list.
To stay current with policy developments, you can subscribe to the Policy Development Process Announcements mailing list. This mailing list is for announcing policy proposals and tracking them through the RIPE Policy Development Process (PDP).