Quote:
|
So, why would this be happening, and why didn't it happen sooner if IPv4 could handle it?
|
Again, just because it
didn't happen sooner (or did and you didn't hear about it) does not mean it's attributable to IPv6. The same scenario is just as plausible (and in fact is done) under IPv4. The taxi (like the Home) need only have ONE real, public IP address. The wipers, tires, radio, AC, windows, and trunk can be assigned private addresses behind the taxi's firewall. Giving each component it's own public addressable address just doesn't make sense--and wouldn't be given the thumbs-up by any competent SysAdmin.
Basically I don't accept the premise of the article in question. It's misguided and makes illogical assumptions.
Quote:
|
And why assume a home network can't be altered to accept multiple signals from IP-enabled devices?
|
I
don't assume that. Of course it can be altered to accept multiple signals from IP-enabled devices. That happen right now already. But public addresses can't easily be assigned to devices on a private network that sits behind a NATing router. That's a routing nightmare.
Having a publically registered IP address assigned to a device does not equal "having an internet connection." And there's no way that a device that had a public IP address could
automatically connect to a user's home network. Each device would need to have its own separate and independent internet connection (wireless cellular modem) for it to be plausible.