Category: About The Book

Where did IPv6 grow in 2023? Where did it not? What countries led on IPv6 deployment?

Recently a colleague of mine at the Internet Society, Robbie Mitchell, laid all this out in a long post titled “Governments and Industry Driving IPv6 in 2023”. With data and many charts he walks through where IPv6 deployment is improving and where more work is needed.

I found it fascinating to see how much the Asia-Pacific region is growing, while here where I live in the USA the growth was minuscule (1.7%). Particularly since historically the ISPs in the USA have been strong drivers of IPv6 growth.

I’ll note that if you want to track IPv6 growth, the Internet Society’s Pulse platform has a page about technologies at: https://pulse.internetsociety.org/technologies – on that page you can see data and maps that show IPv6 deployment (as well as for other technologies).

Where did IPv6 grow in 2023? Where did it not? What countries led on IPv6 deployment?

Recently a colleague of mine at the Internet Society, Robbie Mitchell, laid all this out in a long post titled “Governments and Industry Driving IPv6 in 2023”. With data and many charts he walks through where IPv6 deployment is improving and where more work is needed.

I found it fascinating to see how much the Asia-Pacific region is growing, while here where I live in the USA the growth was minuscule (1.7%). Particularly since historically the ISPs in the USA have been strong drivers of IPv6 growth.

I’ll note that if you want to track IPv6 growth, the Internet Society’s Pulse platform has a page about technologies at: https://pulse.internetsociety.org/technologies – on that page you can see data and maps that show IPv6 deployment (as well as for other technologies).

When I looked at Google’s IPv6 stats recently, it was great to see that the peaks are now consistently all over 40%. Back in January, I wrote about crossing the 35% threshold, so there’s been a 5% growth over the space of the year.

Would we who advocate for IPv6 want it to grow quicker? Of course! And if you look at the per-country page, you can see that it has grown quicker in some countries than others.

But hey… we’ve been at this for a long time, so I’ll celebrate that 5% growth this year! Let’s see if it keeps on going more next year!

P.S. If you want another source of IPv6 statistics, colleagues of mine at the Internet Society are involved with measuring IPv6 on our Pulse measurement platform.

When I looked at Google’s IPv6 stats recently, it was great to see that the peaks are now consistently all over 40%. Back in January, I wrote about crossing the 35% threshold, so there’s been a 5% growth over the space of the year.

Would we who advocate for IPv6 want it to grow quicker? Of course! And if you look at the per-country page, you can see that it has grown quicker in some countries than others.

But hey… we’ve been at this for a long time, so I’ll celebrate that 5% growth this year! Let’s see if it keeps on going more next year!

P.S. If you want another source of IPv6 statistics, colleagues of mine at the Internet Society are involved with measuring IPv6 on our Pulse measurement platform.

Why is it that many of the “IPv6 books” are 10+ years old? Where can you find the most current info? Could a group of people using IPv6 today come together and create a new book about IPv6?

Brian Carpenter asked those questions … and then started a project on GitHub to do exactly this – create a “collaborative IPv6 book”. The idea is to capture current knowledge from people working with IPv6 – and then keep it up-to-date.

So far he’s had a number of people contribute text – and the work is underway. As the repository states:

The intention is a practical introduction to IPv6 for technical people, kept up to date by active practitioners.

The book will be available free of charge (and free of advertising) on-line, possibly with an option to obtain a printed copy at cost price.

This GitHub repository is a starting point. It may be replaced by a differently structured repo as the work progresses and we gain experience of how to do it.

You can read the book online, with the caveat that it is still very much in development. If you want to contribute text or edit, there are contributor guidelines that explain the process.

I think it’s great to see another book emerging, and I look forward to seeing how this collaborative model works for all involved.

Why is it that many of the “IPv6 books” are 10+ years old? Where can you find the most current info? Could a group of people using IPv6 today come together and create a new book about IPv6?

Brian Carpenter asked those questions … and then started a project on GitHub to do exactly this – create a “collaborative IPv6 book”. The idea is to capture current knowledge from people working with IPv6 – and then keep it up-to-date.

So far he’s had a number of people contribute text – and the work is underway. As the repository states:

The intention is a practical introduction to IPv6 for technical people, kept up to date by active practitioners.

The book will be available free of charge (and free of advertising) on-line, possibly with an option to obtain a printed copy at cost price.

This GitHub repository is a starting point. It may be replaced by a differently structured repo as the work progresses and we gain experience of how to do it.

You can read the book online, with the caveat that it is still very much in development. If you want to contribute text or edit, there are contributor guidelines that explain the process.

I think it’s great to see another book emerging, and I look forward to seeing how this collaborative model works for all involved.

What is the current state of application support for IPv6? What are challenges for applications migrating to IPv6, particularly for enterprise applications? What am I doing at the Internet Society with projects such as Open Standards Everywhere to promote IPv6?

I had the fun of being interviewed by Scott Hogg and Tom Coffeen on their IPv6 Buzz Podcast episode 53 to talk about all of this and more. You can listen here:

Thanks to Scott and Tom, as well as their other host Ed Horley, for having me on the show to geek out about IPv6. Please do give the show a listen – and send along any questions you may have. Thanks!

What is the current state of application support for IPv6? What are challenges for applications migrating to IPv6, particularly for enterprise applications? What am I doing at the Internet Society with projects such as Open Standards Everywhere to promote IPv6?

I had the fun of being interviewed by Scott Hogg and Tom Coffeen on their IPv6 Buzz Podcast episode 53 to talk about all of this and more. You can listen here:

Thanks to Scott and Tom, as well as their other host Ed Horley, for having me on the show to geek out about IPv6. Please do give the show a listen – and send along any questions you may have. Thanks!

With the changes to the book and my plans to develop a Second Edition, I also want to change the toolchain I’m using. When I wrote the book for O’Reilly back in 2011, I used DocBook XML as the source. However, these days I’m typically working in Markdown or another lightweight text markup format. So step one for the Second Edition is to migrate the DocBook XML into another format.

My current thinking is to use AsciiDoc, as it has support for footnotes and admonitions (ex. “Warning”), neither of which are supported in most Markdown variants. I’m still working through some plans, but hope to have the book converted over in the next few weeks. (I would welcome feedback on other text formats.)

I’m planning to make the book text available in a GitHub repository so that others can see the text and perhaps offer comments and feedback. If you would like to be notified when I do that, please sign up on my email list.

With the changes to the book and my plans to develop a Second Edition, I also want to change the toolchain I’m using. When I wrote the book for O’Reilly back in 2011, I used DocBook XML as the source. However, these days I’m typically working in Markdown or another lightweight text markup format. So step one for the Second Edition is to migrate the DocBook XML into another format.

My current thinking is to use AsciiDoc, as it has support for footnotes and admonitions (ex. “Warning”), neither of which are supported in most Markdown variants. I’m still working through some plans, but hope to have the book converted over in the next few weeks. (I would welcome feedback on other text formats.)

I’m planning to make the book text available in a GitHub repository so that others can see the text and perhaps offer comments and feedback. If you would like to be notified when I do that, please sign up on my email list.