Test Plans

Plans of Record

The vendors supporting this TIP have outlined test plan milestones to help interested parties to understand the state of interoperability testing.

Wave 1

Our initial plan milestone will be for each vendor to demonstrate interoperability against the following:

1. Validation against Aries Protocol Test Suite for Aries Interop Profile v. 1.0
2. Core Aries Interop Profile v. 1.0 - See Aries RFC 302
3. DIDComm (did:sov)
4. Connection
5. Credentials
6. Proofs
7. Ephemeral Proofs: receive only
8. Service decorator
9. Needed for VC-Authn-OIDC (used by BC.gov)
10. Transition Message Type to HTTPs: receive
11. Aries RFC 348: Can receive messages with protocol definition of type http://didcomm.org

Wave 2

Our second milestone will be for each vendor to tackle the goals of AIP 2

• Aries PR 579 for RFC 302 - AIP 2.0
• Notes AIP 2.0
• Slide deck with current thinking
• Discussion in Aries WG B 2020-12-02
• Discussion in Aries WG B 2020-12-09

User Stories

• Able to provide a proof without creating a persistent connection.
• Out-of-Band Protocol

Other Technical Requirements

• Transition Message Type to HTTPs: send/receive
• Aries RFC 348: http://didcomm.org

Further Ideas

• Core Aries Interop Profile v. 2.0 (TBD)
• Out Of Band
• DID Exchange
• Credential Exchange Protocols (v2)
• feature discovery v2
• mime-types (to help transition to didcomm v2)
• Signed attachments
• New MIME Types
• BC-Gov Test Suite