How to Get IP Addresses

From RIPE NCC Translated
Jump to navigation Jump to search
This page contains changes which are not marked for translation.
Other languages:
English • ‎Türkçe • ‎español • ‎italiano • ‎русский • ‎العربية • ‎فارسی

Background Information

The RIPE NCC is the Regional Internet Registry (RIR) for Europe, the Middle East and parts of Central Asia. We provide Internet number resources to our members- IPv6 and IPv4 addresses as well as Autonomous System Numbers (ASNs).


Become a Member to Request IP

You need to become a member to directly request Internet number resources from us. Read our How to Become a Member page to find out if you’re eligible, what you will need and how to apply. Members pay an annual membership fee and a one-off sign-up fee. You can find out about fees on our Billing, fees and payments page.

Any legal entity or natural person can become a member of the RIPE NCC and request IP addresses and AS Numbers. Members are usually Internet Service Providers (ISPs), mobile operators or organisations with significant networks such as financial institutions, government departments and universities.

An organisation that needs IPv6 address space or an AS Number does not necessarily need to become a member of the RIPE NCC and can get an assignment of independent resources via a sponsoring LIR (Local Internet Registry).


How to Request IP Resources

Below we explain how to request IPv6, ASNs and how our [IPv4] waiting list works.

Allocating and Assigning IP Resources

RIPE NCC members can request IP addresses either as an allocation or an assignment. There are important differences between the two.

Allocations

To “allocate” means to distribute IP address space to LIRs for the purpose of subsequent distribution. An allocation is a range of IP addresses for an Internet Registry to sub-allocate and assign to End Users or to the member’s own network.

Assignments

An assignment is a range of IP addresses registered for a specific purpose, either for an End User or for a member’s network infrastructure.

To “assign” means to delegate address space to an ISP or End User for specific use within the Internet infrastructure they operate. Assignments must only be made for specific purposes documented by specific organisations and are not to be sub-assigned to other parties.


Request IPv6

Assignments

The minimum size of an IPv6 IP [assignment] is /48. If you need a larger [assignment], you will need to provide documentation justifying the need for additional subnets or define special routing requirements for the additional sites which need an additional /48 independent IPv6 prefix.

While it is possible to further assign separate addresses (/128) from the [assignment] to external parties, it is not possible to assign a prefix.

[PI] (Provider Independent) [Assignment] uses

You CAN use an IPv6 [PI assignment] for:

  • Large organisation networks (organisations having separate legal sub-entities within their network)
  • Governmental organisation networks having other entities within their network
  • Co-location services
  • Assigning a subnet to another entity

You can NOT use an IPv6 [PI assignment] for:

ISPs offering broadband services

  • Large organisation networks (organisations having separate legal sub-entities within their network)
  • Governmental organisation networks having other entities within their network
  • Co-location services
  • Assigning a subnet to another entity

If you would like to use IPv6 for any of these cases, you can become a member of the RIPE NCC and request an IPv6 [allocation], or you can obtain IPv6 address space from your upstream provider.


Request an IPv6 [PI Assignment]

To request an IPv6 [PI assignment], you will need to provide the following documents:

  • A copy of the End User's registration in the Commercial Trade Register or an equivalent document.
  • A fully signed Independent Assignment Request and Maintenance Agreement

You will also need to provide your sponsoring LIR with the following RIPE Database objects information for the request:

  • An organisation object with the full legal name of the End User organisation.
  • A maintainer object (mntner) to protect the assignment.
  • The NIC handle of a role or person object. This object will specify which End User contact is administratively or technically responsible for the assignment.

Once you’ve collected this information, you will need to ask your sponsoring LIR to start the request on your behalf.

Allocations

If your organisation is a member of the RIPE NCC, you already qualify for an IPv6 allocation.

The minimum [allocation] size is a /32. You can request up to a /29 without providing any additional justification. If you need an IPv6 [allocation] bigger than a /29 we will assess your request.

Request IPv6


Request IPv4

IPv4 Waiting List

We have run out of IPv4 addresses. However, we do recover addresses sometimes. These addresses are distributed to members via a waiting list. Only RIPE NCC members who have never received an IPv4 allocation directly from us can request a single IPv4 /24 [allocation].

Information you need:

Make sure you have the following information to hand as you will need it for the request form:

  • Details of the people responsible for your LIR and number resources [(admin-c and tech-c contacts)] and a maintainer object [(mntner)] that would prevent other people from changing your registration information in the RIPE Database
  • You agree to register [assignments] in the RIPE Database to show your actual usage;
  • You have an active network element in our service region and you can demonstrate it

You can fill in the IPv4 request form by clicking the button below. (The form is in English.)

Request IPv4


Request an AS Number

Any individual or organisation can request ASNs, though a contractual agreement with the RIPE NCC is required.

Any individual or organisation can request [Autonomous System Numbers] (ASNs).

To request an ASN, you will need:

  • a contractual agreement with the RIPE NCC
  • to become a member

You must provide the AS Numbers of at least two of your peering partners, their contact details (including email addresses) and the routing policy in Routing Policy Specification Language (RPSL). For further details on RPSL, please see RFC 2622.

A new ASN should only be used if a new external routing policy is required. Please see RFC 1930 for more information. A network must also be multihomed to qualify for an ASN.

Click the link below to request an ASN or find a sponsoring LIR to request one on your behalf.

Request an AS Number