Everyone on your corporate network has tons of globally unique, trackable IDs. They're called cookies.
Also, there are IPv6 privacy extensions.
> b) Allow outgoing connections in arbitrary ways but forbid random incoming connections.
Just as with IPv4?
> c) Some sort of central, highly secured network node where your admins can configure this stuff.
That's called a firewall. You need one with IPv4 as well.
> At this point you're close to reinventing NAT, except crappier.
None of that has anything to do with NAT.
- You can use IPv6 privacy extensions to randomize your IP address. Your computer can have a dozen IP addresses at a given moment, using a different one to access different services, as addresses are being rotated.
- Most corporate networks have static IPs. So while a specific IP might be shared with 100 devices, it's usually easy to fingerprint a visitor uniquely.
- There are tons of other ways to track people, other than their IP. Besides, you want to track them across networks, as they move around.
I'm also very sensitive to tracking, but I think at this point you have to start looking at how to improve your privacy with IPv6, sharing/encouraging good privacy-sensitive practices on IPv6.. not spreading FUD.
b) is a basic feature of the crappiest firewall (the free router from my ISP includes it)
c) is a standard feature of a business-level firewall; secure network access (e.g. with a VLAN) is orthogonal to the choice of IP protocol.
a) Mask end-user addresses somehow. You wouldn't want everyone on your corporate network to get a globally unique, trackable ID.
b) Allow outgoing connections in arbitrary ways but forbid random incoming connections.
c) Some sort of central, highly secured network node where your admins can configure this stuff.
At this point you're close to reinventing NAT, except crappier.