Reusing Returned Internet Number Resources

This document describes how the RIPE NCC reuses returned and reclaimed Internet number resources.

IPv4

The RIPE NCC has been allocating IPv4 address space from 185.0.0.0/8 since September 2012 in accordance with RIPE Policy “IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region”.

We delete all related RIPE Database objects for the returned or reclaimed IPv4 address space and keep it in quarantine for six months or as long as the space is globally routed.

Address space from 185.0.0.0/8 is reused once a block’s quarantine ends.

Address space from all other blocks will be reused once 185.0.0.0/8 block is exhausted

IPv6

The RIPE NCC deletes all related RIPE Database objects for the returned or reclaimed IPv6 address space and keeps it in quarantine for six months or as long as the space is globally routed.  

32-bit ASNs

The RIPE NCC deletes all RIPE Database objects where the returned or reclaimed 32-bit ASN is the primary or inverse key.

All returned and reclaimed 32-bit ASNs are kept in quarantine for six months or as long as they are globally routed or referenced in any other RIPE Database objects (for example in import/export attributes of aut-num objects).

16-bit ASNs

The RIPE NCC deletes all RIPE Database objects where the returned or reclaimed 16-bit ASN is the primary or inverse key.

All returned and reclaimed 16-bit ASNs are kept in quarantine for six months or as long as they are globally routed or referenced in any other RIPE Database objects (for example in import/export attributes of aut-num objects).

The RIPE NCC expects to run out of available unreferenced 16-bit ASNs in the future.

In accordance with the decision of RIPE Working Groups Chairs the RIPE NCC will start reassigning referenced ASNs once the pool of unreferenced 16-bit ASNs has been exhausted.

The RIPE NCC will still keep returned and reclaimed 16-bit ASNs in quarantine for six months or as long as they are visible in the global routing table.