> It would be a pain to use ipv6 internally. So.. Have you ever actually used ipv6? With ipv6 your organization gets a prefix assigned, usually a /32 or a /48

> It would be a pain to use ipv6 internally. So.. Have you ever actually used ipv6? With ipv6 your organization gets a prefix assigned, usually a /32 or a /48 So you would get assigned a prefix like 2626:32:400::/48 With ipv4 where if you were lucky you had a /16 that had 65,536 addresses - with "simple" /24 subnetting for 256 subnets of 256 hosts each. With ipv6 you minimally have a /48 that has 65,536 subnets. So you can just start subnetting things like 2626:32:400:0/64 is headquarters, 2626:32:400:1/64 is marketing. And you never have to worry about running out of address space on each subnet, since each subnet has room for 18,446,744,073,709,551,616 addresses. And since there is room for 65,536 subnets, you can easily do things like immediately carve that up into blocks of 512 subnets for every geographical location and project... once. And not end up with "10.1.3.0 is marketing, but also 10.1.58.0 because we ran out of room" So really, if you can type 192.168.x.y, you can type 2626:32:400:x:y.