FAQ: Resource Requests

Show/Hide all

According to the IP Resource Analyst (IPRA), my request is not yet complete. Am I required to send a completely new request form? →

No. The IPRA will indicate the incomplete information. The IPRAs prefer you to provide the necessary information attached underneath the text of the message you receive.

Why does the RIPE NCC require so much detailed information about my network? →

The RIPE NCC is bound to ensure that address space, which is a shared public resource, is managed responsibly in this region and used in accordance with the policies and practices that have been developed to protect the health of the Internet and the conservation of its resources.

Therefore, the RIPE NCC needs detailed information so that it can properly evaluate your request.

The information is essential in enabling the RIPE NCC to determine whether your plans are based on best current practice and consistent with the goals of global Internet management.

How do I determine what counts as my infrastructure, and what is considered to be a customer's network? →

IP addresses used solely to connect an end-user to a provider's network can be counted as part of the provider's infrastructure. They can be registered to the provider in the RIPE Database as part of a single aggregated block within their allocated IP space.

For example: a point-to-point link between a provider and an end-user's network could be registered to the provider. However, IP addresses used by an end-user for their own network need to be registered to that end-user.

This means that if a provider has an access router with 64 ports for connecting customer leased lines and they want to use a /30 network for point-to-point links for each leased line, they could register the network as a single /24 assignment. However, should the customer have a /30 network on their side of the router this would need to be registered to the end-user in the database.

Is it required to provide the planned usage of a network for the entire period? →

Yes. In order to demonstrate the predicted growth of your network, your request must provide an estimate of the address space you will require over three distinct periods: Immediate, Intermediate and the Entire period.

These periods are not fixed, and should be regarded as guidelines.

However, starting on 1 January 2010, a gradual reduction in the assignment period will be applied. As the assignment period changes, so too will the information required:

Up to 30 June 2010, assignments are for a period of up to 12 months. Therefore, your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for the coming 12 months.

As of 1 July 2010, assignments are for a period of up to 9 months. Your request should reflect your immediate requirements, predicted requirements for the coming 6 months, and predicted requirements for the coming 9 months.

As of 1 January 2011, assignments are for period of up to 6 months. Your request should reflect your immediate requirements, predicted requirements for the coming 3 months, and predicted requirements for the coming 6 months.

As of 1 July 2011, assignments are for a period of up to 3 months. Your request should reflect your immediate requirements, predicted requirements for the coming 2 months, and predicted requirements for the coming 3 months.

The utilisation rate of an assignment must be such that at least 50% of the total space shall have been utilised halfway through the assignment period applied at the time of the assignment.

Can I split up assignments? How? →

In many cases it's no problem to split assignments. You can create two (or more) new objects for the parts you want to seperate, and delete the original object afterwards. When your assignment is approved by the RIPE NCC, please keep in mind that assignments are only valid as long as the original assignment criteria does not change.

It is NOT permitted to split approved assignments for other organizations, or to split them for other purposes than they were approved for. When splitting an approved assignment, please keep the original approved netname for all objects. The assignments are only valid as long as the netnames in the database match EXACTLY the approved netname. If you change one or more of the netnames, or if you are unsure, please contact hostmaster@ripe.net.

Can I combine assignments? How? →

If you make a new assignment for the same organization with the same netname, it is permisible to combine the objects.

You can create one new object for the whole range, and delete the original object(s) for the smaller range(s). Please note that if you received approvals from the RIPE NCC for your assignments, the netname in the database needs to match EXACTLY the netnames that were approved, and the first changed line date must be on or later than the most current approval date. If one or more of the netnames are changed, or if you are unsure, please contact hostmaster@ripe.net.

I have just received approval for my IP request. Do I have to inform the RIPE NCC on which IP range I am going to assign to this network ? →

No, there is no need to inform the RIPE NCC on the IP range you choose. The RIPE NCC only keeps a record of the approved netname and the size of the approved IP request.

As long as you don't increase the size of the assignment or change the netname the assignment will remain valid. This means if you ever were re-organising your allocation, you can move an approved network to another part of your allocation without having to inform us.

I received approval for my assignment but you tell me that the INETNUM object is invalid. What went wrong? →

The most likely cause of the problem is that the netname was changed without informing hostmaster@ripe.net - or the inetnum object(s) have a first changed date prior to the date of approval.

As an example, if you had a /24 Assignment Window and requested a /21 from us for "NATIONAL-MEGAPOP" we would expect to see a /21 entry in the database for "NATIONAL-MEGAPOP" on or after the date of approval.

If you had changed the design and entered two /22 netnames: "MEGAPOP-NORTH" and "MEGAPOP-SOUTH" into the database five days prior to approval we would see errors based on the following criteria:

• Assignments exceed your Assignment Window
• Assignments have a different netname than was approved
• Assignments entered into the database before approval was granted

If you want to change a netname approved then reply to hostmaster@ripe.net in the same ticket as the approval with details of the change you will make.

How and when do I request an allocation? →

When approximately 80% of your first allocation is used up, you can then request an additional allocation. Send an email to hostmaster@ripe.net with the keyword "NEWBLOCK" in the subject line.

Do not send a standard IP Address Space Request Form, but do supply us with a summary of ALL the assignments from your present allocation.

Requesting an additional allocation is covered on our "Quick Tips" page.

All the procedures involved in obtaining an additional allocation are covered in section 5.3.3 of the RIPE Document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region", which is available from the RIPE Document Store.

What are the criteria for obtaining an AS number? →

RFC 1930 states: "An AS is only needed when you have a routing policy which is different from that of your border gateway peers".

This means that you will be connecting to two or more Autonomous Systems with different routing policies.

In your request you must show us details of the routing policy you will have when you multi-home in the very near future.

The template(s) you need to complete are found in the "RIPE NCC Autonomous System Number Request Form", which is located at:

http://www.ripe.net/ripe/docs/asnrequestform.

More information can be found in the RIPE Document "Autonomous System (AS) Number Assignment Policies and Procedures" available at:

http://www.ripe.net/ripe/docs/asn-assignment

How do I request an AS Number? →

The template you need to complete is found in the RIPE Document "RIPE NCC Autonomous System Number Request Form", which is located at:

http://www.ripe.net/ripe/docs/asnrequestform.

AS Numbers need to be requested through LIRs.

Send the template to hostmaster@ripe.net.

Do not forget to include your RegID.

Now that our request is approved, who will enter the assignment-object in the database? →

The LIR should enter the inetnum in the database, after receiving the approval message from the RIPE NCC.

"Each assignment and allocation for public Internet address space must be registered in a publicly accessible whois database. Allocations and assignments in the RIPE NCC service region are registered in the RIPE Database. This is necessary to ensure uniqueness and to support network operations".

My request has bounced, what have I done wrong? →

There may be several reasons why your request was bounced. The bounce message should contain additional information as to the kind of bounce, e.g. a NOSERVICEBOUNCE or a NOREGIDBOUNCE.

Further information about what these mean and how to correct the problem can be found in the "auto-mailbox Help Page" at:

http://www.ripe.net/rs/status.html

I am not happy with the way my request has been evaluated. What can I do? →

The RIPE NCC has an internal escalation procedure for handling concerns about the way your request has been handled. You can ask for any request to be escalated by sending an email to hostmaster@ripe.net and quoting the relevant NCC# ticket number. Your request will then be reviewed and assessed by senior staff.

If your concern is of a more serious nature, please refer to the RIPE NCC's Conflict Arbitration Procedure.