Re: phone numbers are easy
However - a /64 should be what's assigned to a host. While that's not as short or easy to type as 192.0.2.2, (colons suck for the shift component - can't type with a single hand on a 10-digit number pad, for example) FE80:CD00::0CDE is all that you should need to locate a single host on a network if you're not assigning /128's like a numpkin.
I think this is part of the challenge, ie human vs machine friendly representation. So as an example per wiki on CIDR-
the IPv4 block 198.51.100.0/22 represents the 1024 IPv4 addresses from 198.51.100.0 to 198.51.103.255.
the IPv6 block 2001:db8::/48 represents the block of IPv6 addresses from 2001:db8:0:0:0:0:0:0 to 2001:db8:0:ffff:ffff:ffff:ffff:ffff.
Once you've been working on networks for a while, you get to know the bit boundaries and netmasks, so configuring things like routes, subnets, ACL's etc is quick and easy. On v6 as an example though-
You would assign either an inbound ACL on VLAN 1 or an outbound ACL on VLAN 2 to filter a packet routed between subnets on different VLANs, that is, a packet sent from the workstation 2001:db8:0:111::2 on VLAN 1 to the server at 2001:db8:0:222::25 on VLAN 2. (An outbound ACL on VLAN 1 or an inbound ACL on VLAN 2 would not filter the packet.)
Where multiple subnets are configured on the same VLAN, you can use either inbound or outbound ACLs to filter routed IPv6 traffic between the subnets on the VLAN if the traffic source and destination IP addresses are on devices external to the switch.
Stolen from configuring ACLs on HP. Which can harder to parse, thus prone to errors and fat-fingering. But also depends on what range you're assigned. Some providers only assign a /64, others a /56 or /48. IPv6 does away with many of the concepts of subnetting, ie netmasks but also has some limitations. So a v6 subnet is assumed to be a minimum of a /64 to keep SLAAC happy, which means if you're only assigned a /64, you can't subnet. Or shouldn't.
But that isn't efficient, ie you're kinda wasting 64bits of the address space, which isn't really an issue. For now, anyway. But-
A 64-bit interface identifier can be derived from the interface's 48-bit MAC address, although stable privacy addresses are now recommended as a default instead. A MAC address 00-0C-29-0C-47-D5 is turned into a 64-bit EUI-64 by inserting FF-FE in the middle: 00-0C-29-FF-FE-0C-47-D5
Which is one of those 'but why?' questions, answered mostly by pointing at the mobile community, and their insistance that an IP address should include a MAC address. Which then lead to people pointing out that that was a tad insecure, and so kludges like generating privacy addresses. Which is mostly out of scope for the average user, except when maybe trying to do troubleshooting and being asked questions like 'What's your IP address?' or 'Can you ping.. err. wait..'. Or just other standard troubleshooting, like in the v4 world, I used to test for potential DNS problems, routing, or webservers just resting by telnet'ng to a to a web server on port 80 and seeing if it responds. Wiki gives an v6 example of-
https://[2001:db8:85a3:8d3:1319:8a2e:370:7348]:443/
as similar example, which is less human-friendly. But something I guess support types just have to get used to.