June 12, 2020 archive

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.