Tom
I think the concern is more around having a system that provides a
potentially public interface that maps identifiers, even ephemeral
ones, to an identity. When this is the identity of a end user device,
such as a phone, this becomes a system that does maps identifier to
user identities. This naturally leads to concerns about how to secure
such a system and how to prevent abuse of the information that goes
beyond the needs of connectivity. Both the proposed charter and the
related drafts are sketchy as to how the system can be secured and who
will be authorized to access the system.
Let's clarify again
1. IDy is NOT human identities but the "user(temporal) of an (temporal) identifier" who is authorized to update or look up identities.
2. It is not mandatory to authenticate but desirable.
3. In some cases, like in a private or closed when you need to track your devices/planes, do accounting or whatever, you should be able to do this on a need to know basis.
Using the cell phone example to tie an end device to a human. Today, doesn't SIM cards tie at some level you as a subscriber to your device and do the accounting? The SIM database is not publicly accessible are they?
Thanks
Padma
Tom