Versions Compared

Old Version 1

changes.mady.by.user Sam Curren

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Curran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt
  • QR / Invitations
    • How are we really going to do deep-links?
    • RFC 496 - Transition to OOB and DID Exchange
    • RFC 700 - sending out-of-band as query parameters and enable redirect back.
    • HTTP Mobile exemptions

Note: This call was recorded and the recording and chat transcript are at the bottom of the page.

Date

(7AM-9AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.


Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

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.

https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09j/93810537086

Attendees                                                                                                                                                            

Welcome / Introductions


Focus

QR Code & Invitations

Discussion Topics

  • 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
    RFC 700 
        • 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)
    • 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

...