It's as much of a mental shift as replacing street addresses with Latitude/Longitude coordinates.
So I've avoided IPv6 as much as possible.
It's as much of a mental shift as replacing street addresses with Latitude/Longitude coordinates.
So I've avoided IPv6 as much as possible.
Can you elaborate a bit? Where do you find frustration with IPv6? I've been using IPv6 for probably close to 10 years now, and I can't say it's been frustrating
At this point, though, you may be able to find an IPv6 capable ISP and just switch to them. Your phone might also have IPv6 too, especially if it's 4G/LTE.
Any amount of exposure is better than none. If you're using AWS, I can help you setup IPv6 in your VPC and use it with EC2 which can let you get some first hand experience. My email is in my profile if you want to take me up on that offer.
Lat/lon is a data set primarily used by applications. IP addresses are much the same way aside from private networks and experimentation. If you need to describe a private space in IPv6 you have link local addresses that begin with fe80.
Modern routing tables are primarily defined by dynamic protocols, such as OSPF. If you really need to express a static IP address directly, such as for remote access to a switch, the IP address will be provided to you. This is why Cisco now requires Python for the CCNP.