You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the difficulties I had with SharedSignal and I think DADE will face is that there is no single protocol that clearly define what an ACCOUNT is and describe the status of that ACCOUNT.
Yes we do have eKYC and IDA to describe how it was registered and assured and SharedSignal describes how to transmit security signal relating to an ACCOUNT. But there isn’t a protocol for describing and ACCOUNT. ISO/IEC 24760-1:2019, for example, provides a framework for identity management and includes definitions for identity-related terms. It defines “identity” as a set of attributes related to an entity, which can be a person or an organization, but does not provide a specific definition for “ACCOUNT.” Verifiable Credential defines trust model of an ACCOUNT. NIST 800 63 does not clearly define ACCOUNT.
When designing the guideline for DADE, I think this question of “How to describe an ACCOUNT” will come up and I think, it will be useful to for OIDF to just define it, once and for all.
Here is a list of attributes related to ACCOUNT.
Who is the owner of that account?
Person
Organization
Government
Custody of administrator or guardian
AI
etc
What is the active status of the account?
Active and in use
Disabled
Dormant (and for how long)
Does not exit
Deleted
Dead
In administration
In guardianship
What is this account of
Bank account
Wedapp
Mobile account
Verifiable credentials
Passport
etc
What are the attributes of the account?
Email
2. Phone number
3. Person’s name
4. Address
5. Etc
Who is the issuer of that account?
IdP
2. CSP
3. Webapp
4. Government
5. Etc (edited)
The text was updated successfully, but these errors were encountered:
One of the difficulties I had with SharedSignal and I think DADE will face is that there is no single protocol that clearly define what an ACCOUNT is and describe the status of that ACCOUNT.
Yes we do have eKYC and IDA to describe how it was registered and assured and SharedSignal describes how to transmit security signal relating to an ACCOUNT. But there isn’t a protocol for describing and ACCOUNT. ISO/IEC 24760-1:2019, for example, provides a framework for identity management and includes definitions for identity-related terms. It defines “identity” as a set of attributes related to an entity, which can be a person or an organization, but does not provide a specific definition for “ACCOUNT.” Verifiable Credential defines trust model of an ACCOUNT. NIST 800 63 does not clearly define ACCOUNT.
When designing the guideline for DADE, I think this question of “How to describe an ACCOUNT” will come up and I think, it will be useful to for OIDF to just define it, once and for all.
Here is a list of attributes related to ACCOUNT.
Who is the owner of that account?
Person
Organization
Government
Custody of administrator or guardian
AI
etc
What is the active status of the account?
Active and in use
Disabled
Dormant (and for how long)
Does not exit
Deleted
Dead
In administration
In guardianship
What is this account of
Bank account
Wedapp
Mobile account
Verifiable credentials
Passport
etc
What are the attributes of the account?
Email
2. Phone number
3. Person’s name
4. Address
5. Etc
Who is the issuer of that account?
IdP
2. CSP
3. Webapp
4. Government
5. Etc (edited)
The text was updated successfully, but these errors were encountered: