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
Email: daniel.karrenberg@ripe.net
Website: https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg
• 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.
• 1 min read
With Labs getting off the ground, it was time to find someone to power the building of a dynamic and diverse community.
• 1 min read
The forums in Drupal look good enough for the purpose and the web folks like the platform. Looks like RIPE Labs will be launched based on Drupal.
• 1 min read
Long before this sparkly site came along, the team with the ideas tested out other platforms and solutions to deliver RIPE Labs.
• 1 min read
Finally got everyone convinced of Robert's idea. I am excited. With RIPE Labs we will get more people involved in innovation at the RIPE NCC again ...
• 3 min read
Robert has gotten the RIPE Labs idea down as an outline now. Much discussion with him and in Science Group. Will present to senior management shortly.
• 2 min read
In this episode of the RIPE Labs podcast, three Internet pioneers talk about how they helped grow the Internet out of its early infancy, back when its purpose - and much of the excitement around its development - lay in the promise of connecting researchers from around the world.
• 7 min read
Our cloud strategy framework provides a starting point that we will use when developing cloud implementations in the future. It also forms a solid basis for discussions with the community on specific proposals relating to our services.
• 4 min read
Following the Facebook outage that took place on 4 October, we saw people looking to BGPlay to get a better view of what went on. Here's a look at what the RIPEstat visualisation has to show us about the event in question.
• 11 min read
Our draft cloud strategy framework is an attempt to bring everything together in a way that sets out some boundaries, identifies critical elements, and indicates where we need to be strict vs where we can afford to be a little more relaxed. This should hopefully support more clarity regarding how w…
• 8 min read
The community’s reaction to our cloud proposal at RIPE 82 was stronger than we expected. We think it’s worth re-starting this discussion, and the first step is to check that we’ve heard you correctly.
• 4 min read
At the Internet Governance Forum this week, we signed an MoU with CENTR, the European association of country-code Top Level Domains (ccTLDs). This seemed like a good opportunity to revisit some of the shared history between our two organisations.
• 8 min read
This article is intended to make RIPE Atlas users aware of ethical issues that could arise when using RIPE Atlas. We do not intend to propose any new formal processes or procedures to address the relevant ethical issues, but we do want to encourage members of the RIPE Atlas community to consider th…
• 3 min read
During the RIPE 70 Meeting in Amsterdam this week (on 13 May around 10:00 UTC), we experienced a network outage at AMS-IX. Let's see how this was monitored by various tools.
• 2 min read
Similar to an experiment done for IPv4 address space, Merit is now performing a darknet experiment with the IPv6 ranges that have been allocated to the RIRs. This also includes prefixes allocated to the RIPE NCC.
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)