I can tell you that when the big switch happens, at least in the flyover states, its gonna be a big fucking mess. Can you HONESTLY say that if someone showed you a pile of IP V6 addresses and said "One of these has a problem in either the address or the subnet" you could just pick it out on the fly? But I bet even your average teen wouldn't have a problem spotting the 184 address in a pile of 192 addresses because it would stick out like a sore thumb.
Without specifically addressing your example, I'd like to say that I (as a sysadmin, who has been running v6 servers for ~3 years) MUCH prefer v6 addresses.
Let's take 2001:44b8:8020:ff00::84. I remember that one off the top of my head, as it happens. And, actually, I remember a LOT of the v6 addresses for servers I look after, off the top of my head. Why? Because they make sense.
2001:44b8::/32 belongs to the organisation I currently work for. "80" is always in there for our Adelaide datacentres. (b0 for Sydney, c0 for Melbourne, etc). Different prefixes are allocated for customer use. "20" is because it's the second DC (Our primary DC is 8060, aka ADL6). :ff00: designates a VLAN interface - :ffxx: VLANs are all ones for Systems Infrastructure. ::84? Primary DNS resolver. ::85 is a secondary. Other system types have other common IP groupings.
The IPv4 address is 126.96.36.199. Utterly meaningless in comparison.
In other instances, I can recognise at a glance that something is part of a particular VLAN behind a particular ASA. IPs can finally actually have meaning beyond just squeezing them in. Not to mention the pain when you fill a /28, because new requirements popped up 6-12 months after the address-space was carved up...
The best part? It's not set in stone, there's plenty of address space for us to use a different scheme just by toggling a bit or two near the top of the address space.
PS. Of course this is all my opinion, not my employer's, yada yada :-)