Identity Statement: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
There are a variety of existing statements about a [[NSTIC Strategy|Trusted Identity in Cyberspace]] that can be used to guide the development of a common understanding about what a [[Identity Statement]] should contain. Some of those are listed together with the relevant parts of each to this topic. | There are a variety of existing statements about a [[NSTIC Strategy|Trusted Identity in Cyberspace]] that can be used to guide the development of a common understanding about what a [[Identity Statement]] should contain. Some of those are listed together with the relevant parts of each to this topic. | ||
===DID Document=== | ===DID Document=== | ||
Security | |||
DID architecture should enable sufficient security for relying parties to depend on DID Documents for their required level of assurance. | |||
Proof-based | |||
DID architecture should enable an entity to provide cryptographic proof of authentication and proof of authorization rights. | |||
Discoverability | |||
DID architecture should make it possible for entities to discover DIDs for other entities to learn more about or interact with those entities. | |||
Interoperability | |||
DID architecture should use interoperable standards so DID infrastructure can make use of existing tools and software libraries designed for interoperability | |||
===Software Statement=== | ===Software Statement=== | ||
Revision as of 20:28, 13 December 2018
Full Title
An Identity Statement will return the metadata that backs a canonical Identifier on the web.
Context
There are a variety of existing statements about a Trusted Identity in Cyberspace that can be used to guide the development of a common understanding about what a Identity Statement should contain. Some of those are listed together with the relevant parts of each to this topic.
DID Document
Security
DID architecture should enable sufficient security for relying parties to depend on DID Documents for their required level of assurance.
Proof-based
DID architecture should enable an entity to provide cryptographic proof of authentication and proof of authorization rights.
Discoverability
DID architecture should make it possible for entities to discover DIDs for other entities to learn more about or interact with those entities.
Interoperability
DID architecture should use interoperable standards so DID infrastructure can make use of existing tools and software libraries designed for interoperability