I do a lot of networking and I like being able to remember IPs and subnetting is a lot easier. I haven’t really realized any issues with latency. Haven’t really had to guess ports either as NAT handles that. I think IPv6 is a good idea and works great for computers, but as I human I prefer IPv4.
IPv6 doesn’t need to be hard. For one you can use DNS since it is probably Tue best in terms of readability.
For addressing you can do a few different things. If you are just looking for simple addresses you can do something like:
2001:ab6f:c5::5
2001:ab6f:c5::6
If you have multiple areas or vlans you also can separate them with site info in the address. Something like:
Site one: 2001:ab6f:1:1::1
Site two: 2001:ab6f:2:1::1
Site two vlan 666: 2001:ab6f:2:666::1
You also can use words like beef and cafe to make it more memorable.
Ipv6 is also nice since subnetting is much simpler. All subnets are /64 so it is very easy to know if an address is in a subnet. No more /19 and other crazy subnetting madness.
I do a lot of networking and I like being able to remember IPs and subnetting is a lot easier. I haven’t really realized any issues with latency. Haven’t really had to guess ports either as NAT handles that. I think IPv6 is a good idea and works great for computers, but as I human I prefer IPv4.
IPv6 doesn’t need to be hard. For one you can use DNS since it is probably Tue best in terms of readability.
For addressing you can do a few different things. If you are just looking for simple addresses you can do something like:
2001:ab6f:c5::5 2001:ab6f:c5::6
If you have multiple areas or vlans you also can separate them with site info in the address. Something like:
Site one: 2001:ab6f:1:1::1
Site two: 2001:ab6f:2:1::1
Site two vlan 666: 2001:ab6f:2:666::1
You also can use words like beef and cafe to make it more memorable.
Ipv6 is also nice since subnetting is much simpler. All subnets are /64 so it is very easy to know if an address is in a subnet. No more /19 and other crazy subnetting madness.