• Issue Game: Can we close this?
  • ~service decorator
  • Connection Blues continued.
  • ACApy Performance Evaluation

Note: This call is being recorded.


(12PM Los Angeles, 3PM New York, Tuesday at 7AM Sydney)

Remember 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 . 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.


Welcome / Introductions


Related Meetings Review

  • Ursa - No calls since the last Aries meeting.
  • Semantics - yesterday's call: Handling big data in an Indy Credential - workaround - Hashlink. Link to Paper
  • DID UX Call - Slack/Mailing list - details in the shared document as well minutes and additional information, currently focus on Purpose Based Services
  • SSI in IoT WG
  • Indy Contributors - Richard Esplin (Mon) - Notes
  • Identity WG / Identity WG Implementer calls (Wed / Thurs) - no calls since last Aries meeting
  • DIF DIDComm WG - Monday's at Noon US/Pacific Outline happening next week.

Upcoming Releases and Work Updates


  • Issue Game: Can we close this? (15 min -) -  issues (as time permits): 290, 77, 225, 122
    • Decisions 122 closed, 290 BCGov will pursue, 77 and 225
  • Should the ~service decorator be part of AIP 1.0.0? PR linkRichard Esplin
    • Evernym reviewed the RFC and discussed the ACApy implementation. Our concerns are resolved.
      • New ACApy test showing how a return response endpoint would be routed through two or more mediators.
  • Proposal for adding RFC 348 to AIP 1.0
    • Advantages:
      • Would start a transition period to the new approach.
      • Reduces pressure on the next version of Aries Interop Profile
    • Concerns:
      • Doesn't seem to fit the scope of AIP 1.0 (define credential exchange in practice today)
      • What does it mean to require support of a transitional feature from a compliance perspective?
  • Connection Blues - Continued - Sam CurrenStephen Curran
    • Using DIDs to use existing invitation
      • When an invitation starts from a Public DID, this should be retained by the agent. 
      • Future invitation Public DIDs can be looked up to see if an existing relationship exists.
      • New DID Exchange Message from invitee saying "I'm going to use this existing connection, but exercise a new invitation"
    • Connect→Then Invitations
      • How to best compose messages?
      • Nicely accommodate connectionless messages.
      • The Then is more semantically important than the Connection
    • Safe URL redirectors
      • What to avoid
      • Is there a way to do this safely?
      • Can we do this with DIDComm? (An Expand Message Protocol?)
      • Attachment? (Can fetch from place x), with integrity check and possibly decryption key
  • ACApy/Credential F2 Registry HighVolume Performance Testing - Stephen Curran
  • Open Discussion / Next Week Topics

Next Week

  • AIP 1.0.0 

Future Topics

Action items

Call Recording

  • No labels