You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Summary:

Planned Topics:

  • Issue Game: Can we close this? (15 min -)
  • Generic JSON Protocol (RFC 351) and HTTP over DIDComm (RFC 335)
  • Concern with RFC 302 Aries Interop Profile v1.0

Note: This call is being recorded.

Date

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

  • Name (Organization) <email>

Welcome / Introductions - Stephen Curran

Announcements

Related Meetings Review

  • Ursa - 
  • Semantics -
  • 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) - 
  • Identity WG / Identity WG Implementer calls (Wed / Thurs)

Upcoming Releases and Work Updates

Agenda

  • Issue Game: Can we close this? (15 min -) - issues (as time permits): 
  • Generic JSON Protocol (RFC 351) and HTTP over DIDComm (RFC 335) - SecureKey Team
  • Concern with RFC 302 Aries Interop Profile v1.0 Richard Esplin Stephen Curran
    • Non-interactive protocols require more thought to avoid compromising the privacy of end users. Issue link.
    • Concerns with the Service Decorator. PR link.
  • If there is time: Separating "Invitation" from Connection/DID Exchange / Ephemeral Challenge
  • Open Discussion / Next Week Topics

Next Week

Future Topics

Action items

Call Recording

  • No labels