Today, I come up with a few updates regarding this blog. First, all the contents is now licensed under the terms of a Creative Commons 3.0 License. Second, this website is now available over IPv6.
The Creative Commons Share-alike 3.0 Unported (CC-BY-SA) license allow you to freely copy and distribute derivative work of this blog's content, as soon as you give proper attribution to the author(s). So, practically speaking, you can by example copy the diagrams present in a article and put them in your company's training slides, but you will have to cite all the authors and to distribute your work (could be limited to a single slide) under the exact same license.
I also made some minor updates to the blog code to ease browsering and navigation on mobile and tablet devices, which account for more than 50% of the visits at this time of writing. I don't own any tablet, so I will push major changes only after proper testing and feedback. If you've any suggestions on that side, feel free to contact me on Twitter @e3prom, by leaving a comment on this page, or by any other means deemed appropriate.
Finally, I inserted a AAAA record for 'www.netflask.net' and all its affiliated sub-domains. I also reconfigured nginx (the HTTP proxy/cache behind this website) to listen on an IPv6 socket, so you can entirely browse this blog over an IPv6-only network, as the latter is entirely self-hosted, outside of the Disqus comment system. BTW: Is there anyone who get a native IPv6 connectivity on his mobile data network? People who know me, knows how I like to bug Service Providers about their lack of commitments regarding v6. To be coherent with my own ideas and opinions, I decided to enable support for the unloved network-layer protocol, so nobody can argue I'm an adept of the 'do what I say, but not what I do' philosophy.
I'm also planning to enable SCTP and SPDY, two very interesting protocols I would like to see running behind this website for the sake of personally covering them, and to demonstrate they are supported at varying levels in internet browsers, operating systems, network routers, firewalls and other intermediary devices. Both protocols should allow to reduce the pages' load times significantly.
Also, as I'm a victim of my own success, I will probably come with more frequent updates in the future. In the meantime, I hope you all enjoy reading my articles. You can now freely distribute them if you like to, but if you do, please drop me a line, so I can know what you do with them.