...
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
Dial-in link
https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09j/93810537086
Attendees
- Sam Curren <sam@indicio.tech>
- Kalyan Kulkarni <kalyan@ayanworks.com>
- Bruno Hivert<bruno.hivert@idlab.org>
- Regis Eloi<regis.eloi@idlab.org>
- Brent Zundel
- Akiff Manji <amanji@petridish.dev>
- Jason Leach (BC Gov) <jason.leach@fullboar.ca>
- Clecio Varjao <clecio.varjao@gov.bc.ca>
- Berend Sliedrecht <berend@animo.id>
- Bruce Conrad <bruce_conrad@byu.edu>
- James Ebert <james.ebert@indicio.tech>
- Sai Ranjit Tummalapalli<sairanjit.tummalapalli@ayanworks.com>
- Troy Ronda <troy.ronda@securekey.com>
- Rolson Quadras<rolson.quadras@securekey.com>
- Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Welcome / Introductions
Focus
...
- RFC 496 - Transition to OOB and DID Exchange
- Connect.Me - Evernym
- Bifold/AFJ - James Ebert and the Awesome Canadians
- ATB Proof (AFJ) - Alberta
- Trinsic / eSatus / Lissi / IDRamp - .Net Framework
- Findy Wallet
- iGrant Sweden
- Northern Block Orbit
- DIT - https://digitalidentitytrust.org/
- Mattr
- Liquid Avatar
- SecureKey/TrustBloc/AFG (already on OOB and DID Exchange)
- Process
- Seek Status (where is your code now)
- Is the Proposed Date Reasonable?
- Step 1 Date Dec 31st 2021
- Stephen Curran will chase this proposal.
- Contact each wallet author
- Post notifications to the Aries Community - email and list
- Update the RFC with: Status and new date.
- Request updates to the implementation table in the RFC
- RFC 700 - sending out-of-band as query parameters and enable redirect back.
- How are we really going to do deep-links?
- https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0268-unified-didcomm-agent-deeplinking/README.md
- Two methods - custom scheme (didcomm://) or associated domains
- custom scheme
- works well for Android.
- iOS with two apps on the same scheme, message reception is undefined. No end user choice or config.
- no associated app, this fails out.
- associated domains
- register URL with app (example.com/happycattle)
- do something based on navigated URL
- tight coupling
- community managed domain
- nascar selection
- auto-redirect to custom scheme, detect failure.
- can also redisplay QR code.
- redirect from within iframe
- also works with web wallets/agents (in association with RFC 700)
- custom scheme
- Writeup of proposed process James / Clecio / Sam
- and issue that links to it.
- James will do science on the proposed process.
- HTTP Mobile exemptions
- DIDComm allows HTTP endpoints
- Mobile platforms require an exemption to call http links instead of https
- How do we resolve this for mediators and mobile apps?
- jason volunteered for a PR with a SHOULD for HTTPS.
Action items
Call Recording
...