As I've said before, the actual requirement is that the lower 64 bitsIs it useful to define the requirement this narrow? For a server, I would think it's hard to work with non-globally unique correspondents as potentially every host connected to the network can open a session at any time, creating a collision where there wasn't one previously.
be mutually unique among the set of correspondents (two for normal cases,
N for p2p cases).
Don't forget return routability. Ingress filtering and RPF checks aren't done everywhere, but return routability protection is relatively good except when the attacker shares a subnet.But indeed it is a general point that non-topological fields are more readily spoofed than topological fields, since ingress filtering and RPF checks don't apply.
So we agree that breaking return routability and not repairing the resulting gap with something else isn't an option?The consequence is not automatically that they can't be used, but that if they are used, an additional layer (such as HIP) is needed.
I'm getting there... It's still more than a month before the draft cutoff for Vienna. :-)I think that is what you should say.