Here’s what I think is a fascinating read. I’m excited about QUIC, and less excited that well-intentioned (sometimes draconian) protocol enforcement encourages software engineers to move nearly all protocols to run on top of HTTP or HTTPS — as a way to bypass the enforcement.<\/p>\n
https:\/\/blog.apnic.net\/2017\/12\/12\/internet-protocols-changing\/<\/p>\n
\nWhen a protocol can\u2019t evolve because deployments \u2018freeze\u2019 its extensibility points, we say it has ossified. TCP itself is a severe example of ossification; so many middleboxes do so many things to TCP \u2014 whether it\u2019s blocking packets with TCP options that aren\u2019t recognized, or \u2018optimizing\u2019 congestion control.<\/p>\n
It\u2019s necessary to prevent ossification, to ensure that protocols can evolve to meet the needs of the Internet in the future; otherwise, it would be a \u2018tragedy of the commons\u2019 where the actions of some individual networks \u2014 although well-intended \u2014 would affect the health of the Internet overall.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"
Here’s what I think is a fascinating read. I’m excited about QUIC, and less excited that well-intentioned (sometimes draconian) protocol enforcement encourages software engineers to move nearly all protocols to run on top of HTTP or HTTPS — as a way to bypass the enforcement. https:\/\/blog.apnic.net\/2017\/12\/12\/internet-protocols-changing\/ When a protocol can\u2019t evolve because deployments \u2018freeze\u2019 its … <\/p>\n