5 ms·
Unless your plan is to change human nature, where the “blame” goes is pretty academic. The inertia is still an issue when going the RFC route, and less of an is
by johncolanduoni 6y ago
Unless your plan is to change human nature, where the “blame” goes is pretty academic. The inertia is still an issue when going the RFC route, and less of an issue when standards are developed first to fill a specific need for an interested party.
- jacquesm 6y agoThe inertia is a good measure for how successful a particular protocol version is. See for instance IPV4 and how hard it is to get rid of it. And that inertia is good, you don't want to rip up your standards every two years.
- shadowgovt 6y agoEvery two years, no. When the standard starts to actively limit further development, though... https://en.m.wikipedia.org/wiki/IPv4_address_exhaustion https://en.m.wikipedia.org/wiki/IPv4_address_exhaustion
- jacquesm 6y agoNobody stops you from adopting IPv6, the reason that many people don't do it is because they have legacy stuff that they can not reconfigure so they're stuck. But it will happen, and IPv6 adoption is steadily on the rise.
- josephg 6y agoHere in Australia my expensive fibre connection still has no ipv6 support. I file an issue every year or so to my ISP asking when they're going to add ipv6 support, so at least they know I care. But the answer is always "Its not on the roadmap". Its difficult to remember to write ipv6-compatible software when I can't use or test it myself. Short of writing to my member of parliament and asking them to legislate it, I'm not sure what else I can do.