The IOTA DIDComm Specification is in the RFC phase and may undergo changes. Suggestions are welcome at GitHub #464.
- Version: 0.1
- Last Updated: 2021-10-29
The IOTA DIDComm Specification standardizes how Self-Sovereign Identities (SSIs) can interact with each other and exchange information. Any applications that implement this standard will naturally be interoperable with each other. This reduces fragmentation in the ecosystem and therefore it is highly recommended to use this for any application built on top of the IOTA Identity framework. The specification defines several protocols, that can be used for common interactions like issuing and presenting verifiable credentials as well as supporting functions, such as connection establishment and authentication. Cross-cutting concerns like error handling and credential negotiation are discussed in the resources section.
The IOTA DIDComm Specification builds on the DIDComm Messaging Specification developed by the Decentralized Identity Foundation (DIF) and utilises external protocols from the messaging specification for well-established interactions like feature discovery.
This specification is meant to be a complete solution for common use cases and therefore contains protocols for common SSI interactions. It is possible to extend the specification with custom protocols and custom methods in existing protocols to support application-specific requirements.
The specification itself is technology agnostic. Much like the DIDComm Messaging Specification there are no restrictions on transport layers and a concrete implementation can be done with many different technologies.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in BCP 14[RFC 2119].
Protocols follow Semantic Versioning 2.0 conventions.
The specification defines several DIDComm protocols that can be used for common SSI interactions:
|Connection||0.1||Establishes a DIDComm connection between two parties.|
|Authentication||0.1||Allows two parties to mutually authenticate, verifying the DID of each other.|
|Presentation||0.1||Allows presentation of verifiable credentials that are issued to a holder and uniquely presented to a third-party verifier.|
|Issuance||0.1||Allows the exchange of a verifiable credential between an issuer and a holder.|
|Signing||0.1||Allows a trusted-party to request the signing of an unsigned verifiable credential by an issuer.|
|Revocation||0.1||Allows to request revocation of an issued credential, either by the holder or a trusted-party.|
|Revocation Options||0.1||Allows discovery of available |
|Post||0.1||Allows the sending of a single message with arbitrary data.|
|Termination||0.1||Indicates the graceful termination of a connection.|
In addition to the protocols defined in this specification, we RECOMMEND implementors use the following well-known protocols:
|Discover Features||2.0||Describes how agents can query one another to discover which features they support, and to what extent.|
|Trust Ping||1.0||A standard way for agents to test connectivity, responsiveness, and security of a DIDComm channel.|
Additionally, general guidelines on concerns across protocols are provided:
|Problem Reports||Definitions of expected problem reports and guidance on global handling.|
|Credential Info||Definition of methods to negotiate a specific kind of verifiable credential.|
◈ If necessary, discuss ways for some agent to request the start of an interaction. This has narrow use cases, but might be interesting in the long run. ◈ Add section or article on anonymous encryption, sender authenticated encryption, signed messages. Include a table of comparisons with guarantees? E.g. authentication, eavesdropping protection, integrity etc.