ISP Related FAQs

1. My ISP is about to close down. I want to keep the IP addresses they issued to me. Am I allowed to do that?
2. My ISP is about to close down. I have a new ISP and they need to add a route object in the Database but cannot do this. Can you add the route object for us?
3. My organisation is/was multi-homed but our aut-num and route objects were maintained by an ISP that is no longer operating. Can you change the objects for us?
4. Is the RIPE NCC accountable for the operation of its Local Internet Registries (LIRs)?
5. What are Provider Aggregatable (PA) addresses and Provider Independent (PI) addresses?
6. What happens to my PA address space if my LIR or ISP ceases operation?
7. What will happen to my pending request for Internet resources if my LIR ceases operation?
8. Can I take my address range with me when I change ISPs (i.e. renumbering)?
9. I have a range of IP addresses but my ISP says the range belongs to them. Who owns the IP addresses I use?
10. I want to use my IP addresses for a specific purpose. Does the RIPE NCC allow this?
11. I want to route my IP addresses under another Autonomous System Number (ASN). Is this allowed?
12. I have IP addresses issued to me a long time ago. The records are not up-to-date in the RIPE Database.
13. How much should an LIR be charging for requesting IP space on my behalf?
14. Why does the RIPE NCC not deal with the customers of an LIR?
    

My ISP is about to close down. I want to keep the IP addresses they issued to me. Am I allowed to do that?

If the IP addresses you received from your ISP have a status of "ASSIGNED PI" they are Provider Independent. That means you can take them with you when you change ISP. If your IP addresses have a status of "ASSIGNED PA" they are Provider Aggregatable; that means you will not be able to take them with you. You will have to renumber.

The status of the addresses is visible in the inetnum object in the RIPE Whois Database. You can query the Database on our web site at:

http://www.ripe.net/db/whois/whois.html

You can read more about PA and PI address space in the RIPE document "Provider Independent versus Provider Aggregatable Address Space" which is available from the RIPE Document Store.


My ISP is about to close down. I have a new ISP and they need to add a route object in the Database but cannot do this. Can you add the route object for us?

The data in the RIPE Whois Database is owned by the people who enter it and not by the RIPE NCC. The RIPE NCC is not permitted to change user data. There is a security mechanism called RPSS controlling the creation of route objects. RPSS is designed to stop the creation of route objects (amongst other things) without the agreement of the the person controlling the AS number and the person controlling the IP addresses.

If the IP addresses and AS number are from different ISPs those ISPs will need to work together to create a route object for you.

My organisation is/was multi-homed but our aut-num and route objects were maintained by an ISP that is no longer operating. Can you change the objects for us?

The RIPE NCC will not change user data in the RIPE Whois Database. If you have a maintainer object in the Database which you do not control, you will need to contact the RIPE Database Department who will guide you through the process of regaining control of the maintainer.

An explanation on how to contact the RIPE Database managers is available on our web site at:

http://www.ripe.net/db/ticketing-dbm.html

Is the RIPE NCC accountable for the operation of its Local Internet Registries (LIRs)?
The RIPE NCC is a Regional Internet Registry (RIR) providing global Internet resources and related services. We are not a regulator of the Internet community in our service region nor do we police the quality of service provided by ISPs in our service region. In situations where an LIR or Internet Service Provider (ISP) ceases operation our response is governed by the policies that are set by the RIPE community. These polices are detailed in the RIPE document "IPv4 Address Allocation and Assignment Policies in the RIPE NCC Service Region" found at:

What are Provider Aggregatable (PA) addresses and Provider Independent (PI) addresses?
Provider Aggregatable addresses are assigned from an LIR's allocation. PA assignments are registered in the RIPE Database by the LIR. The advantage of PA addresses is that the routing information for many customers can be aggregated once it leaves the provider's routing domain.

Provider Independent address space is assigned separately, most often from RIRs and not from an LIR's PA allocation. All PI assignments are registered in the RIPE Database. PI ranges are usually small; they cannot be aggregated into larger blocks. The disadvantage of this is that networks operators throughout the Internet may choose not to route them.

More information is found in the RIPE document "Smallest RIPE NCC Allocation /Assignment Sizes" found at:

The status of the addresses is visible in the inetnum object in the RIPE Whois Database.

More information can be found in the following sections of the RIPE document "Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR" located at:

http://www.ripe.net/ripe/docs/mergers.html#3.6

http://www.ripe.net/ripe/docs/mergers.html#3.7

What will happen to my pending request for Internet resources if my LIR ceases operation?
As soon as the LIR decides to close it should halt any open requests for IP address space. Customers with pending requests should approach another LIR in their region.

Can I take my address range with me when I change ISPs (i.e. renumbering)?
If the customer has PI addresses the assignment will remain valid providing the criteria for the original assignment are met.

Customers with PA addresses are recommended to obtain a new address space assignment from another LIR and return the PA address space that was assigned by their original LIR. In this way full use of aggregation is made. When a customer renumbers into an address allocation held by another LIR, their assignments can be routed as part of that LIRs allocation. At the same time the aggretability of the original LIRs allocated block is maintained.

It is the responsibility of an LIR to make it clear to their customers which type of address space is assigned to them.

I have a range of IP addresses but my ISP says the range belongs to them. Who owns the IP addresses I use?
IP addresses are a shared public resource.

The LIRs assign IP address space to meet the needs of network operators, including themselves. The hierarchical manner in which the public Internet addresses are distributed permits the aggregation of routing information. Aggregation ensures proper operation of Internet routing.

A clear contractual arrangement that specifies the validity and duration of the address assignment is strongly recommended for every address assignment.

I want to use my IP addresses for a specific purpose. Does the RIPE NCC allow this?
The RIPE NCC requires that LIRs adhere to the RIPE community's policies in their use of the Internet resources that are allocated to them. The RIPE NCC does not act as a regulator of the Internet in its service region. Any disputes that arise over the correct usage of Internet resources can be posted on the RIPE LIR Working Group mailing list: lir-wg@ripe.net.

I want to route my IP addresses under another Autonomous System Number (ASN). Is this allowed?
The RIPE NCC does not control any ISP's routing policies. This is left to the discretion of the ISPs involved.

I have IP addresses issued to me a long time ago. The records are not up-to-date in the RIPE Database.
Organisations using such assignments should contact an LIR in their region who can contact our Registration Services department on their behalf. Requests will be handled on a case-by-case basis. A list of LIRs in the RIPE NCC service region can be accessed at:

http://www.ripe.net/membership/indices/index.html

How much should an LIR be charging for requesting IP space on my behalf?
IP addresses are a public resource and should not be bought or sold. It is reasonable, however, for an LIR to charge a fee for administering the address space that they assign to you. The RIPE NCC has not stipulated a charging schedule. This is left to the discretion of the membership.

Further information on the RIPE community's policy on charging by LIRs can be found in the RIPE document "Charging by Local Internet Registries".

Why does the RIPE NCC not deal with the customers of an LIR?
The LIRs represent the RIPE NCC on a local level. They are responsible for the distribution and registration of Internet resources within their local areas. The LIRs must also ensure that policies and procedures are followed. ISP customers should direct any questions to the LIR from which they take service.