Which would still require a redo of the line. To put into perspective how big a line is, it takes approximately 16 hrs for a car to reach the end of the line and be driven off the line.@wlanboy put a 6 instead of a 4. Legacy configurations/equipment do not need IPV6, they can change their software to use 10.0.0.0/8 instead of legacy ranges.Look at those /8 IPv6 nets: https://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks
e.g.: "19.0.0.0/8 Ford Motor Company" 16 million ips...
It may happen that all are assigned - but they are not used.
Not sure about Ford directly, but a lot of the older car plants have legacy equipment that isn't exactly capable of using IPv6. To redo an entire line would be expensive and not to mention would take time for each and every plant that would need it.
If I owned a legacy block, there's no way I'd hand it back considering 2/3 of the IPs would probably go to hoarders.
It's also more than just the manufacturing equipment. Every computer, printer/scanner/copier, phone, server, firewall, router, etc. has at least one of these addresses.Which would still require a redo of the line. To put into perspective how big a line is, it takes approximately 16 hrs for a car to reach the end of the line and be driven off the line.@wlanboy put a 6 instead of a 4. Legacy configurations/equipment do not need IPV6, they can change their software to use 10.0.0.0/8 instead of legacy ranges.Look at those /8 IPv6 nets: https://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks
e.g.: "19.0.0.0/8 Ford Motor Company" 16 million ips...
It may happen that all are assigned - but they are not used.
Not sure about Ford directly, but a lot of the older car plants have legacy equipment that isn't exactly capable of using IPv6. To redo an entire line would be expensive and not to mention would take time for each and every plant that would need it.
If I owned a legacy block, there's no way I'd hand it back considering 2/3 of the IPs would probably go to hoarders.
I wouldn't want to hand it back either.
Does this mean that people will not be able to host more websites in a couple years or that the cost will increase a lot so they can be accessed over ipv4?
Services will be behind nat/proxies. I don't believe that a database or a worker does need an ipv4 address.
Multiple sites can (for over 10 years now!) share the same IPv4 address, so the 'hosting' side of things isn't really going to be an issue - hostees will always be able to find a provider.
What will start to cause problems is when services/sites/systems _choose_ to only deliver their content over IPv6, which could preclude those connecting with v4 only to "miss out"
IPV6 is coming. we don't have to worry about that.
It may also be that many don't know what to make of IPv6 superabundance. Might feel overwhelming to be on the receiving end of such large allocations, not to mention the new & confusing 128 bit formatting.IPV6 is coming. we don't have to worry about that.
IPv6 isn't coming, it ALREADY is here. The issue is that majority of the ISPs still refuse to implement IPv6 and are relying on carrier grade NAT w/o IPv6. Many of these ISPs also have lousy excuses such as not having IPv6 equipment and deployment being difficult. IPv6 was out long ago and planning for implementation should have been done long ago. Same goes for the actual implementation.
Yeah, hopefully the way humans relate to fossil fuels doesn't end up manifesting analogously in the IPv4 market.It just seems that being human, we don't see any urgency to important things until it is too late. IPv6 might be one of them, and maybe global warming too.
My ISP does not have compatibility with ipv6 and they do not have plans to make it work when I asked. Does this mean that people will not be able to host more websites in a couple years or that the cost will increase a lot so they can be accessed over ipv4?