A root (the person) uses multiple systems on which possibly multiple core identifiers are created and from each of those potentially many *contact* identifiers are created and then associated with the communications service points to which the person wishes them to be established.
a.k.a: A tree: a person, with multiple devices, with multiple "core" identifiers yealding multiple end-point identifiers which are bound to selected communications services. So long as the person gets to choose how one end-point identifier leads to others, you're on the right track. I suggest that as a minimum, no end-point identifier should every be able to be found to lead to another which originates from a different "core" identifier (traffic analysis and general op-sec notwithstanding). /Hugo _______________________________________________ Endymail mailing list [email protected] https://www.ietf.org/mailman/listinfo/endymail
