Let us show you the RIR assigned and allocated IPv4 space, and some indication on how that's routed in the Internet. Get out the popcorn! Satisfaction guaranteed!
Look at a race showing, in a unique way, how the IPv4 address space (by /8s) have been allocated by the RIRs over time. The data is taken from the "delegations" files published by the RIRs, and processed in INRDB.
Race cars may move backwards, which illustrates address space returned to or transferred from an RIR.
For full effect, you might want to listen to music in the background. Yello: The race might be an appropriate choice...
Time scale is December 2003 - mid-September 2009.
RIPE NCC assignments/allocations
This movie shows all assignments and allocations done by the RIPE NCC, according to our published "delegated" files, from the /8s that are either "allocated to" the RIPE NCC (28), or "administered by" the RIPE NCC (4).
Each bar represents one /8.
- A blue label means "administered by" the RIPE NCC
- A black label means "allocated to" the RIPE NCC
Each bar turns green at the point IANA allocated that /8 to the RIPE NCC. Each prefix the RIPE NCC has allocated or assigned to an LIR or an end user appears as a blue slot. The position and size of the slot accurately represents the allocation/assignment of the prefix within the /8.
The movie also shows transfers to AfriNIC. They are marked in red.
The percentages on the right hand side show the usage ratio of that /8 according to the RIPE NCC delegations files.
The time frame is December 2003 - mid-September 2009.
Routed RIPE NCC space vs. RIPE NCC assignments/allocations
This movie is really similar to the previous one, but it also shows what prefixes are seen in the routing tables, as seen by the RIPE NCC RIS service. If a prefix is considered to be "widely seen" in RIS (meaning that enough RIS peers saw it), then it's shown as red in the appropriate position and size.
The time frame is December 2003 - mid-September 2009.
All RIRs' assignments/allocations
Shows all the /8s that are either "allocated to" or "administered by" an RIR. Each bar represents one /8:
- A blue label means "administered by" an RIR
- A black label means "allocated to" an RIR
Each prefix the RIRs have allocated/assigned to an LIR or end user (ie. it appears in some RIR's "delegated" files) turns up as a coloured slot. The colour of the slot represents the RIR (see legend at the bottom). The position and size of the slot accurately represents the allocation/assignment of the prefix within the /8.
While you can see nicely how blocks of /8s have been allocated to individual RIRs, the colourful section at the bottom left and top right illustrate the address space under early registration transfer project (ERX).
Time scale is December 2003 - mid-September 2009.
(Note that these videos are here for your viewing pleasure only - they might not be perfectly accurate!)
Comments 4
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.
Anonymous •
<div class="content legacycomment"> <p> I added a <a href="https://labs.ripe.net/node/71"> blog entry to explain how the movies were made </a> , in case someone is interested. </p> </div>
Anonymous •
<div class="content legacycomment"> <p> I can't view flash movies from IPv6-only connection :) and you? </p> </div>
Hide replies
Anonymous •
<div class="content legacycomment"> <p> You should really talk to the YouTube guys then, and convince them of the benefits of IPv6 :-) </p> </div>
Hide replies
Anonymous •
<div class="content legacycomment"> <p> It was accomplished! :-) </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::71 </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::8a </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::65 </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::66 </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::8b </p> <p> youtube-ui.l.google.com has AAAA address 2a00:1450:8007::64 </p> <div> </div> </div>