On 3/6/17 10:16 AM, valdis.kletni...@vt.edu wrote:
On Mon, 06 Mar 2017 03:08:35 -0500, Joly MacFie said:
routing hardware layer that will be hit & miss. Nevertheless, since much of
the world is still IPv4 dependent, it just could take off.
For it to "take off", the very same people who have dragged their heels
deploying IPv6 will need to suddenly jump up and upgrade all their gear
and personnel to support a *third* protocol.
Oh, and you're going to need support buy-in from *at least* Microsoft, Apple,
Linux, Cisco, Juniper, and a significant chunk of major makers of CPE gear.
What's the business case for all these stakeholders to buy into EZIP? For
both the "We already do IPv6" and "We don't do IP6v" cases?
Lets not even get into the fact that we still can't fully utilize things
like already established standards such as ECN, EDNS, and PMTUD
effectively because firewall and security vendors still can't extricate
their heads from backside and handle basic functionality of IPv4 without
throwing the packets on the floor.
If the average 'security' device these days chokes and drops a packet
due to not recognizing the ECN option, what makes anyone think shoving
more special stuff in the headers just for IoT crap is a good idea?
Wouldn't it just be easier to use IPv6 tunneled over Teredo?
Oh wait, that would require the IoT vendors to actually build decent
products with software that works.
--
Brielle Bruns
The Summit Open Source Development Group
http://www.sosdg.org / http://www.ahbl.org
