> So ... yes you need unique identifiers -- many of them at many layers -- > but AA functions do not need to have an identifier thrown at them again > and again, all they really need is for packets to have something that > uniquely maps to that unique identifier at a particular time in their > particular scope.
Fair points all. Allow me to modify and restate: I think that a fixed, unchangeable, global identifier that is exposed in any way is a privacy issue. Users need a way to be wholly anonymous to the network. They should be able to (privately) arrange their access connectivity and then be able to access the network without concerns that they can be identified based on their link layer or network layer information. I have no problems with a cryptographic private key being used as a globally unique identifier, as long as users have the ability to have multiple keys. Certainly someone who wants to be anonymous can generate a temporary key. Tony _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
