PROPOSAL: Define support for DIDComm / WACI-PEx

[OR13]

WACI-PEx describes an alternate flow for exchanging verifiable presentations:

https://github.com/decentralized-identity/waci-presentation-exchange

Unlike the vc-http-api, it is built on top of message level encryption for DIDs, according to a spec called https://github.com/decentralized-identity/didcomm-messaging

The advantage of WACI-PEx is that messages can flow other transports other than HTTP.

The spec also makes use of https://github.com/decentralized-identity/presentation-exchange

Which defines extensions for verifiable presentations that a verifier can use to request specific kinds of presentations from holders.

I would like to define support for this once it stabilizes so we can establish interoperability with other DIF companies and TOIPs Good Health Pass.

I think for sanity sake, we would need new endpoints for this, luckily they would be generate "DIDComm" service endpoints.

[Therecanbeonlyone1969]

we should put this into a implementation guide @OR13

[OR13]

There is progress being made, but v0.1 release has still not shipped.

[mprorock]

There is progress being made, but v0.1 release has still not shipped.

discussed on call and will revist one v0.1 is in place

[OR13]

Status update: w3c-ccg/universal-wallet-interop-spec#99

[mkhraisha]

@OR13 can you maybe walk us through this proposal on a call

[nissimsan]

@OR13, we need to have you on the call for this.

[OR13]

I'm not in favor of adding DIDComm at this time.

I'm not in favor of adding WACI / Presentation Exchange at this time.

I am happy to leave this issue open or close it.

[OR13]

See also w3c-ccg/vc-api#245

[nissimsan]

There are valid requirements for having vc pushed to your wallet. But this may belong better on vc-api.

[OR13]

and w3c-ccg/vc-api#186

[TallTed]

I see issues similar to FTP(control,data) distinct connections, where special switches must be flipped in order to have the client initiate both connections, rather than having client initiate control and server initiate data. This will need strong consideration in the VC API world, along push+pull vs pure_push vs pure_pull vs pull+push

[nissimsan]

Keeping this ticket around for keeping us updated

[OR13]

We discussed implementation timeline for WACI / PEx / DIDComm.

There is no timeline for their implementation here.

These related PRs might impact our decisions in the future:

• Add section on automation via workflows. vc-api#254
• Add section on Interaction Types. vp-request-spec#13

[OR13]

as discsused, we are all awaiting didcomm v2 imps

[OR13]

didcomm v2 implementations still not available.

[OR13]

didcomm v2 implementations still not available.

[OR13]

openwallet-foundation/owl-agent-test-harness#444

Seems to be available now.

[OR13]

nearly there... https://github.com/hyperledger/aries-agent-test-harness/pull/449/files#diff-d758e1dd1d5111619dbff3cd50c095452bf9a0610c395909656138641d109e85R1349

[OR13]

decentralized-identity/waci-didcomm#14

[OR13]

We won't close this until the issue above is addressed.

[OR13]

We still have not addressed the issue.

[nissimsan]

If no one is planning to implement didcomm, we should stop spending time discussion this issue.

[mkhraisha]

Closed