16-bit ASN Exhaustion, Some Data
• 4 min read
We look at the consumption rate of 16-bit ASNs and try to make an educated guess on how long they would last if the current allocation rules would be extended.
Based in Western Europe, NL&DE mostly
Articles
Likes on articles
>>>>>>>>>>>> https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg <<<<<<<<<<<< Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE; 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net; 2000s: dnsmon nsd ris internet+society rssac; 2010s: ripe+labs ripestat ripe+atlas
They are suggestions, so do not take them as instructions! Especially the defaults I suggested should be subject to discussion and community feedback. As to keeping the probes visible: I do not think that this is what the typical user wants when they are interested in the topology close to the *target*. In any case what I was interested in when I used traceroutes like that was a simple representation of the topology close to the target, never mind how the packets got close. Daniel
Suggestions: a) add an option to limit to h hops from the target and then show paths from all probes providing data during the interval b) use 'network names' as a label option c) use AS 'names' as a label option d) use a colour scale (better visual resolution than greyscale) for the number of paths along an edge e) add an option to only show endgs used by at least p % of all probes providing data during the interval f) make h=4 and p=25 the default view For examples of all that see https://labs.ripe.net/Members/dfk/map-a-ripe-atlas-anchor Daniel
Showing 22 comment(s)