Meeting recording

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

Attendees

Resources

Status updates

Agenda

  • Record the meeting
  • DIDComm v2 discussion
    • DIDComm v2 crypto implemented using Aries Askar, Indy SDK not supported
    • Wallet takes resolved DIDDocument for now (will be reworked as planned API refactor)
    • No support for sessions, queue, or priority yet
    • Supported protocols: OOB create invitation, trust ping send/receive
    • Specify DIDComm version when creating an invitation
    • did:peer:2 for p2p connections
    • how do we want to handle connections?
      • connection can be useful, but it can also be useful to be able to send a message to another connection
      • are we conflating a contact with a connection?
      • what if we receive a message from a did we've never seen before?
        • configuration to allow/disallow certain messages? → simple default behaviour
        • create dynamic connection?
        • allow application layer to decide whether the message is accepted, or discard the message → more complex custom behaviour
        • don't want junk in your connection list
    • DIDComm v2 protocols for issuance / etc..
    • issue: need to resolve our own did to send message
    • Can it be used with AFGO mediator?
  • Open Wallet Foundation
  • Wallet API discussion continued
  • Documentation and getting started – continued
  • Revocation PR, other open issues/PRs

Meeting Notes

Recording / Slides

Future topics

Future Topics:


  • It would be good to discuss OCA implementation in AFJ and in Aries Bifold and where should be a boundary between the two in this feature.
  • Extracting parts of AFJ into generic libraries
  • Cheqd integration (Daev Mithran )
  • AFJ Interop tests not running


DSR_AFJ_DIDCommV2.pptx


  • No labels