14E/ Interop between SSI stacks - A proposed handshake protocol

Interop between SSI stacks - A proposed handshake protocol

Wednesday 14E

Convener: Christoph Eckl (Condatis), Richard Astley (Condatis)

Notes-taker(s):

Tags for the session - technology discussed/ideas considered: Interop, aries, siop, qr-code

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

Slides presented: https://www.slideshare.net/secret/xom5XYxnMLVpJW

Jace Hensley Uday Garud Dave Crocker Ian Costanzo Daniel Hardman By_Caballero Kalyan Kulkarni Ken Ebert Lynn Bendixsen Rory Martin Salvatore D’Agostino Sam Curren Taner Dursun

Chris outlined a UK project that given the public procurement nature is insisting on efforts in interoperability. In particular the project is currently built on Hyperledger Aries using Evernyms Verity and Connect.me but is also looking at MS Authenticator and SIOP.

A proposed solution to a QR code that can at least inform the RP or the Issuer of the wallet stack of the user was proposed that does not put the full initial communication request into the QR code payload but relies on a callback URI within the payload.

It was shown that MS already do this as part of their openid:// uri. Evernym also support a callback URI in their connect.me app.

The proposal was for any wallet provider to add an accept header based on https://tools.ietf.org/html/rfc7231#section-5.3.2 to the callback to the RP/issuer.

This enables the issuer to distinguish between wallets and therefore SSI stacks:

Condatis as part of their UK project already negotiated with Microsoft and Evernym the following content types:

Discussion:

RFC document proposal Discuss in the community Propose for Aries Interop Profile

Sample implementation helps get adoption Better to implement in AriesGo or similar to gain more traction

Join community call to circulate proposal

Where should it be socialised outside of Aries

Other discussions include adding full VC in QR Animated QR code to fit more data in

UX user expected to know the QR code should be scanned with any QR code scanner.

Accept Content-type not enough to identify intended stack, options to add subtypes: e.g. application/json+... (see current mime types: http://www.iana.org/assignments/media-types/media-types.xhtml)

Next steps:

Chris and Richard will propose an Aries RFC and will ask Daniel Hardman for review and advise in engaging the wider community.