How do we know which addresses are still unallocated or unassigned? Find below a proposal to include unallocated address space in the statistics files the Regional Internet Registries publish daily.
Each of the Regional Internet Registries (RIRs) publishes all addresses allocated or assigned on a daily basis based on a format agreed by all RIRs. These files are available as "stats files" (sometimes also called "delegated" files) on the RIR's ftp sites. Each published file lists a number of records that represent the cumulative assignments/allocations made until the publication date. The RIRs have been publishing these files going back as far as 2003. Example IPv4 records look like:
Currently, these records do not list any resources that have not yet been allocated or assigned. For a number of reasons, it would be useful for the RIRs and also for the community if these records would also include "free" resources.
The RIRs have agreed to extend these files with additional entries, listing the resources which are in the custody of the RIR but not yet allocated or assigned to any organisation. The union of all records in any given stats file therefore will be representative for all the address space managed by the issuing RIR at the date of publication. The union of all stats files issued on the same date will be representative for all the address space collectively managed by the RIRs. Implementing this proposal would require minor changes to syntax and semantics for these new records.
The RIPE NCC has now started to publish records on a daily basis listing the unallocated addresses.
The unallocated or unassigned records will be listed like this:
The extended version of the stats files is now online. Please note that this is a prototype and the format and location may move in the future based on feedback received.
Especially now with IPv4 address space running out, it is important to have a clear record of all address space in the RIR system, including the unallocated space. This change would also show the entire address space each RIR is responsible for. It would also allow to identify possible overlaps as well as gaps between addresses managed by different RIRs.
Comments are disabled on articles published more than a year ago. If you'd like to inform us of any issues, please reach out to us via the contact form here.
Does "agreed to extend these files with additional entries, listing the resources which are in the custody of the RIR but not yet allocated or assigned to any organisation" mean that the files will include the space distributed according to the spreadsheet here:<br /><br /><a href="http://www.icann.org/en/correspondence/pawlik-to-vegoda-gerich-23nov10-en.pdf" rel="nofollow">http://www.icann.org/[…]/pawlik-to-vegoda-gerich-23nov10-en.pdf</a>
Hide 3 replies
Hi Leo, these statistics include the various registry space distributed to the RIPE NCC. Although the RIPE NCC may be majority RIR for certain /8s, the 'holes' not issued to the RIPE NCC are not listed in the statistics.
Hide 2 replies
Hi Andrea, Thanks for your answer. Can you let us know what impact this has on the accuracy of these statistics files?<br /><br />Thanks,<br /><br />Leo
Hide one reply
Hi Leo, keeping in mind this is a prototype, we can say these files are accurate. All the resources distributed to the RIPE NCC are listed in these statistics files. Resources distributed to other RIRs are not listed in these statistics files. Cheers, Andrea
From the delegated-ripencc-extended-latest file:<br /><br />ripencc||ipv4|18.104.22.168|4194304||available<br />ripencc||ipv4|22.214.171.124|4194304||available<br />ripencc||ipv4|126.96.36.199|8388608||available<br /><br />What is the reason for this de-aggregation?<br /><br />Tore
Hide one reply
Hi Tore,<br /><br />This is the reason for the de-aggregation, the Debogonising project:<br /><br />inetnum: 188.8.131.52 - 184.108.40.206<br />netname: EU-ZZ-20101201<br />org: ORG-NCC1-RIPE<br />descr: RIPE NCC Test Announce<br />country: EU<br />admin-c: HU266-RIPE<br />tech-c: RISM-RIPE<br />status: ALLOCATED PA<br />mnt-by: RIPE-NCC-HM-MNT<br />mnt-by: RIPE-NCC-RIS-MNT<br />changed: <a href="mailto:firstname.lastname@example.org">email@example.com</a> 20101201<br />source: RIPE<br /><br />It is an artefact of our internal address space management system. It will disappear once the test announcements stop.<br /><br />Alex Le Heux