2019-05-15 Aries Working Group Call

Summary:

Credential Based Access Use Case

Aries RFC Process

Date

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

NameOrganizationEmail
Stephen CurranCloud Compass/BC Govswcurran@cloudcompass.ca
Sam CurrenSovrin Foundationsam@sovrin.org
Troy RondaSecureKeytroy.ronda@securekey.com
Tobias LookerMattrtobias.looker@mattr.global
Paul KnowlesDativapaul.knowles@dativa.com
Duane JohnsonMedici Land Governancedujohnson@mediciland.com
Ken EbertSovrin Foundationken@sovrin.org
Kyle Den HartogMattrindy@kyledenhartog.com
Daniel BluhmSovrin Foundationdaniel.bluhm@sovrin.org
TNOoskar.vandeventer@tno.nl

 Alexander Blom

Bloqzone alexander.blom@bloqzone.com 
Helen GarneauSovrin Foundation

helen@sovrin.org

Sovrin Foundationadam@sovrin.org
Albert SolanaValidated Idalbert.solana@validatedid.com
Tomislav MarkovskiStreetcredtmarkovski@gmail.com
Gary de BeerSAFBCdibbs.za@gmail.com
Cody MaceAnonyome Labscmace@anonyome.com
Danube Technader.helmy@danubetech.com
Audrius Ramoska123c Consultingaudrius@123c.eu
Alexi FalquierSpaceman IDalexis@spaceman.id
Markus SabadelloDanube Techmarkus@danubetech.com
Daniel HardmanEvernymdaniel.hardman@evernym.com
George AristySecureKey Technologiesgeorge.aristy@securekey.com
Robert MitwickiLab10 Collectiverobert@lab10.coop
Nathan GeorgeKivanathang@kiva.org


Announcements

  • Aries announced at Consensus in NY

Agenda

ItemWhoNotes
Credential Access Use CaseStephen Curran

Aries RFC Process

Selection of DID Comms Related RFCs for Ratification

Sam Curren

https://github.com/hyperledger/aries-rfcs/pull/2

bring over did comms related HIPEs (v1, under the knowledge that the conversation is continuing)


--- stuff we didn't get to below ---

Credential Exchange Protocol UpdateStephen Curran
DIDCom over XMPP - new draft HIPE

Oskar van Deventer (TNO)

Alexander Blom (Bloqzone)

https://github.com/Oskar-van-Deventer/indy-hipe/tree/didcom-over-xmpp/text/didcom-over-xmpp

Purpose: have DIDCom messages traverse firewalls.

Discussion

-Use DID in userpart of XMPP address for better privacy?

-Fast XMPP service endpoint rotation for even more privacy?

 Peer DID discussion - updateOskar, Daniel, Kyle

 Current status:

• Understanding Peer DID (Oskar): https://docs.google.com/document/d/1SgKvuG7u0r5UkaDRnnkQmnarVylCx5VF5y0eIyV-I6Y
• Pairwise to N-Wise (Daniel): https://docs.google.com/document/d/1BjYdivGQ9GxIz9CJ2ymNvMA68uHZm8bFOTyCHDmziOU
• Use cases for n-wise (Daniel): https://docs.google.com/document/d/17wn4zah37ATGXClWfbvTu07v_YmkDgQfGEWhBiROZBo
• Peer-DID based microledger (Oskar): https://docs.google.com/presentation/d/1VwVWGMjbTR51HPFx1_k4Pe1hHBDnpPa-qGuzJN5UFUw

Result will be likely set of PRs to Peer DID, and possibly other HIPEs




Open Discussion


Next Week

Review of DID Comms Related RFCs

Future Topics



Action items

Call Recording

  File Modified

Text File GMT20190515-190242_Indy-Agent.txt

May 16, 2019 by Sam Curren


Participant log