IPv4 Not Declared Historic

What happened at the sunset4 working group discussion at IETF95. You may remember my previous post about declaring IPv4 historic. IPv4 and IPv6 were specified in RFCs published by consensus at the IETF, the Internet Engineering Task Force. Changes required a new internet-draft to be written and discussed, and if it achieves consensus (usually after edits), it is […]

Continue reading


Declaring IPv4 Historic

I’ve posted a new internet-draft, “IPv4 Declared Historic”. I thought I would describe the document, and why I chose to say what I said. First, the definition of historic: A specification that has been superseded by a more recent specification or is for any other reason considered to be obsolete is assigned to the “Historic” level. […]

Continue reading


Define “Runout”

This week, ARIN allocated another /12, bringing their inventory to less than half of a /8. Since they allocate based on 3-month need, this is “Last Call” for allocations. My friend @toreanderson pointed out that runout date varies based on the size block you need–something I’ve noted before, but haven’t detailed. So I built a spreadsheet. What if […]

Continue reading


IPv6 is Faster

A couple of weeks ago, I ran a panel at NANOG60 about the IPv6 Performance Bonus. First, Geoff Huston showed some results from his experiments. He buys Google ads which run a bit of code, telling the browser to fetch a v6-only object and a v4-only object, and compares the times. He notes that in IPv4, a host will send […]

Continue reading


IPv6 for Consumers

Whenever a group of people talks about IPv6, eventually one of them says, “What we really need is a killer app, something that will get consumers to want IPv6.” I disagree with this. As a technology transition, if you’re waiting for consumers to ask, you’re doing it wrong. I’ve pointed out what I think are […]

Continue reading