iljitsch.com

topics: all · BGP / IPv6 / more · settings · b&w · my business: inet⁶ consult · Twitter · Mastodon · LinkedIn · email · 🇺🇸 🇳🇱

This page has all posts about all subjects. Archive for 2011.

2010 IPv4 Address Use Report

As of January 1, 2011, the number of unused IPv4 addresses is 495.66 million. Exactly a year earlier, the number of available addresses was 721.06 million. So we collectively used up 225.4 million addresses in 2010.

Read the article - posted 2011-01-01

2010 IPv6 Address Use Report

In 2010, twice as many IPv6 address blocks were given out as in 2009, adding up to 5.5 times as much address space.

Read the article - posted 2011-01-01

2010 IPv4 Address Use Report

As of January 1, 2011, the number of unused IPv4 addresses is 495.66 million. Exactly a year earlier, the number of available addresses was 721.06 million. So we collectively used up 225.4 million addresses in 2010.

Read the article - posted 2011-01-04

2010 IPv6 Address Use Report

In 2010, twice as many IPv6 address blocks were given out as in 2009, adding up to 5.5 times as much address space.

Read the article - posted 2011-01-04

→ Understanding bufferbloat and the network buffer arms race

Routers, switches, and cable modems have buffers to temporarily store packets that can't be transmitted right away. As the buffers get bigger, however, latency gets worse. Ars explores the problem, some misconceptions about it, and what needs to be done to mitigate it.

Read the article - posted 2011-01-07

→ 25 years of IETF: setting standards without kings or votes

The Internet Engineering Task Force has been around for a quarter century. That translates to 70 Internet standards and 155 best practices—all without a single vote.

Read the article - posted 2011-01-18

→ How Egypt did (and your government could) shut down the Internet

Ars looks at how Egypt "turned off" the Internet within its borders and whether that could be accomplished in countries like the US and western Europe. The Internet is surprisingly hard to kill, but if a government is willing to power down routers, turn off DNS, and kill interconnects, it can be done.

Read the article - posted 2011-01-30

→ River of IPv4 addresses officially runs dry

It's official: the IPv4 well has run dry. The final five /8 blocks of IPv4 were handed with much pomp and circumstance at an event this morning, which means it's time to get serious about moving everyone to IPv6.

Read the article - posted 2011-02-03

End of the IANA global pool

And so it ends. With a ceremony in Miami. You can see the 13-minute video and also the press conference a little later here.

Also see my Ars Technica story: River of IPv4 addresses officially runs dry. Also see my story about World IPv6 Day on june 8 on Ars a few days earlier. Google, Yahoo and Facebook want to enable IPv6 for a day and then turn it off again. Not good enough.

With no more IPv4 addresses in IANA's global pool, and no policies for redistributing address space between the five RIRs in place (yet), each RIR is going to run out at its own rate. This will happen soon for APNIC, which is burning through address space at an unprecedented rate: 23.7 million addresses in january alone, about what APNIC used in a year in 2000 - 2002. As you can see on the statistics page, at this rate, they would burn through their remaining address space in three more months, and then one extra month for the legacy space administered by them. However, it's unclear who really gets to use the legacy space, and most RIRs have set aside their final /8 allocation or part of it for special purposes.

RIPE should have more than a year according to these numbers, but Geoff Huston and Tony Hain have different projections. Geoff's image shows bars that indicate the chance of the RIR in question running out that month. Tony also has a zoomed graph that shows the APNIC and RIPE NCC projected runout dates more clearly.

In the meantime, it's amazing to still hear tons of people say they see no need adopt IPv6. And there's the tired "IPv4 will be around for DECADES" predictions. I'm sure it will be possible to find stuff that can do IPv4 for many, many years, but I'm also quite confident that there will no longer be a meaningful IPv4 deployment on the public internet by the time the year 2020 comes around. In the 1990s, IPX, AppleTalk and DECNET disappeared pretty quickly after everyone connected to the internet. And these were protocols that were useful locally, regardless of external connectivity. Once you need IPv6 to connect to the rest of the world and your work stations are IPv6-enabled, there's really no reason to keep running an IPv4 network anymore. Sure, there will be some IPv4-to-IPv6 translators to allow access to legacy stuff, but routing IPv4 packets will no longer be a useful exercise.

Permalink - posted 2011-02-06

BGP in Egypt

Two weeks ago, I wrote this story for Ars Technica with some educated guessing about how the regime in Egypt disconnected the country from the internet three weeks ago. Now the New York Times has a three-page story about the same thing, with many more facts. But strangely, it's still unclear whether routers were turned off, cables were disconnected or maybe the BGP configs were changed. Still, highly recommended. Note that you need to sign up (for free) with the NYT to read their stories.

Permalink - posted 2011-02-16

Multi-path BGP: motivations and solutions

F. Valera, I. van Beijnum, A. García-Martínez, M. Bagnulo
Next Generation Internet Architectures and Protocols pages: 238 - 256, Ed., B. Ramamurthy, G. Rouskas, and K. Sivalingam, Cambridge University Press, 2010.

Permalink - posted 2011-02-28

Counting 32-bit AS numbers

I've had a page that shows how many autonomous system numbers the RIRs have given out for a while now. However, when updating the slides for monday's BGP training course I realized that the results are all AS numbers—regardless of whether they're 16- or 32-bit.

So I updated the page. You can now request either 16-bit AS numbers, 32-bit AS numbers, or both. The total number of AS numbers given out so far is 53780. 1744 of those are numbers above 65535, so they're 32-bit. I was actually surprised that the number is this high. So far this year, the RIPE NCC has given out 592 AS numbers (that's more than half of the world total!), 199 of which are 32-bit. So it looks like 32-bit AS deployment is finally picking up.

The number of 16-bit AS numbers given out is 52036, with some 4400 given out in both 2009 and 2010. So at this rate, the 16-bit AS number space will be exhausted in less than three years.

Perform your own queries on the data here. An interesting one is the number of AS numbers per country. For instance, organizations in the US got 302 AS numbers this year so far. And only two of those are 32-bit.

Permalink - posted 2011-03-17

Stadhuis Gouda

Image link - posted 2011-03-20

Death of the Internet predicted, film at your local cineplex

In this Ars Technica article I discuss some research about attacking BGP in the core of the internet by making BGP packets drop through overloading the data plane. The researchers make some unrealistic assumptions, but the data plane overload issue is real.

Read the article - posted 2011-03-23

→ No more addresses: Asia-Pacific region IPv4 well runs dry

APNIC is down to its last 17 million IPv4 addresses, so from now on ISPs in Asia, Australia, and the Pacific will only qualify for one final block of 1,024 addresses each.

Read the article - posted 2011-04-15

Lisbon Baixa-Chiado metro station

Image link - posted 2011-04-22

→ RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers

This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.

Read the article - posted 2011-04-27

→ RFC 6147: DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers

DNS64 is a mechanism for synthesizing AAAA records from A records. DNS64 is used with an IPv6/IPv4 translator to enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. This document specifies DNS64, and provides suggestions on how it should be deployed in conjunction with IPv6/IPv4 translators.

Read the article - posted 2011-04-27

RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers

M. Bagnulo, P. Matthews, I. van Beijnum
April 2011

Permalink - posted 2011-04-30

RFC 6147: DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers

M. Bagnulo, A. Sullivan, P. Matthews, I. van Beijnum
April 2011

Permalink - posted 2011-04-30

→ Yes to Lion, no to cruft: get a clean start with manual Mac migration

With every new Mac and every new Mac OS X version, the Migration Assistant dutifully copies all data from the old system to the new. But after almost a decade, the urge to make a clean start is too strong for our correspondent. Here's how to do it—but it's not for the faint of heart.

Read the article - posted 2011-07-13

→ Speed Matters: How Ethernet Went From 3 Mbps to 100 Gbps… and Beyond

"In 30 years, Ethernet conquered networking and accelerated from 3Mbps to 100Gbps—and Terabit Ethernet might not be far off." My Ars Technica feature about the history (and some future) of Ethernet, reprinted by Wired.

Read the article - posted 2011-07-16

Speed matters: how Ethernet went from 3Mbps to 100Gbps… and beyond

Story about the history (and future) of Ethernet, published by Wired and (first) on Ars Technica.

Permalink - posted 2011-07-16

Bat above the parking lot

Image link - posted 2011-09-22

→ Cutting the cord: how the world’s engineers built Wi-Fi

About the history and the inner workings of IEEE 802.11, written with Jaume Barcelo.

Read the article - posted 2011-10-10

Cat on the north shore of Mallorca

Image link - posted 2011-10-30

RFC 6384: An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation

I. van Beijnum
October 2011

Permalink - posted 2011-10-30

→ RFC 6384: An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation

The File Transfer Protocol (FTP) has a very long history, and despite the fact that today other options exist to perform file transfers, FTP is still in common use. As such, in situations where some client computers only have IPv6 connectivity while many servers are still IPv4-only and IPv6-to-IPv4 translators are used to bridge that gap, it is important that FTP is made to work through these translators to the best possible extent.

Read the article - posted 2011-11-05

Crazy iPhone 4 colors, train station close to Madrid

Image link - posted 2011-12-03

The "IPv6 Buddy" IPv6 keyboard

There's now a USB IPv6 keyboard called the IPv6 Buddy. It has the hexadecimal keys as well as the colon, double colon, slash, period, tab and enter keys. So everything you need to enter IPv6 addresses, including IPv4-mapped addresses and CIDR notation prefixes. It also works for MAC addresses.

"With all the time I save entering IPv6 addresses, I can concentrate on more exciting things! Like perfecting my BGP, OSPF and VRRP implementations."

Did I mention that my birthday is in a few weeks?

Permalink - posted 2011-12-13

Greenwich meridian between Madrid and Barcelona

Image link - posted 2011-12-25

Search for:

Archives: 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024