Page History

<DAY> March <#>

Attendees

• Co-Leads: Darrell O'DonnellID2020 PM: Todd Gehrke Marie Wallace (IBM) and Dakota Gruener (ID2020)

• Participants: 

  • Stephan Baur 
  • RJ Reiser 
  • Steve Megennis
  • Sankarshan Mukhopadhyay
  • Drummond Reed
  • Karla McKenna
  • Michael Becker
  • Sid Mishra
  • Steven Milstein
  • Charlie Walton (Mastercard)
  • Dan Johnson (Mastercard)
  • Rebecca Distler (ID2020)
  • Andy Smith (SITA)
  • Julian Ranger (Digi.me)
  • Dan Bachenheimer (Accenture)
  • Daryl Thomas (Share.ring)
  • Drummond Reed

Agenda Items

Meeting Notes

...

1. Michael Becker (Identity Praxis) - consultant and advisor in personal information management space

...

1. [Darrell] This topic needs to be addressed through the Governance aspect and the Trust Framework
2. [Michael] Also - what about expiry? [Darrell] and thus revocation of entries
   1. Drummond - IATA is doing that for IATA travel pass
   2. [Steve Magennis] does IATA expose an API that can be accessed by the holder?
1. What happens the registry that issued a credential is revoked at the point a travel event is taking place? (see Trust Triangle) and the way in which rules engine works within the GF to decide whether the recipients get a window/runway of valid passes
2. [Stephan] Suggestions to modify the diagram
3. [Todd] We are discussing the rules engine assuming that there is a single instance. The way it could be seen is that once a test leads to an issuance of a credential from the lab, when you go to travel the verifier decides which rules engine and trust registry they want to point at. Rules engines are jurisdictional - each country will have a specific set of rules.This is different from CommonPass which intends to be a global centralized registry of rules. There are possibilities of augmented roles beyond the proof of vaccination. 
4. [Michael] How to conclude that rules are aligned with each other?
5. [Drummond] We need to clarify with the Rules Engine group that Rules Engines serve all 3 domains - issuer rules, holder rules, verifier rules

1. [Darrell] It doesn’t have to be, it is a source one can look-up to determine if one is an authorized issuer etc

1. [Darrell] A centralized trust registry cannot be imposed on any country
2. Inheritance avoids the need to walk through.
3. [Drummond] registry of registries would also need to consider where the root of trust is (eg. what DID chains can you walk for the whole chain of trust). Starting supposition is that the roots of trust is the governance frameworks
4. [Stephan] let’s differentiate the rule-logic that speaks to VC content vs. VC mechanisms like signature validation that is, logic that concerns identity attributes of the issuer

1. Discovery
2. Delegation of trust

...

Meeting Notes

1. Welcome and Linux Foundation antitrust policy - http://www.linuxfoundation.org/antitrust-policy
2. Round of introductions - most of this group now knows each other well
3. The group discussed the aims of the narrative group and the audience for the proposed document.
   1. Agreement that this must be consumable by a wide audience – policymakers, media, consumers – and cannot be too technical.
   2. Objectives:
      1. • Be educational and accessible
         • Provide framing/context for the materials that follow
         • Respond to the concerns we see raised in the media and public debate about health passes, vaccine passports
         • Walk people through many of the logical leaps that we’ve made about key design considerations and/or the best approach 
         • Give individuals/organizations trust that GHPC is asking all the key questions and setting the right bar for a “good” health pass.
4. Marie Wallace] provided an overview of the narrative flow that she has proposed:  https://drive.google.com/file/d/16hwx-CDO07bThZpT5HuaNWZovb7A4UAS/view?usp=sharing
5. The group workshopped the flow, adding sections and defining action items:
   1. Problem statement: people want to get back to life, get back to traveling.  Dan Johnson
   2. What does the world look like?   Andy Smith 
   • The international air travel ecosystem is messy. A huge # of potential verifiers. 
   • The world is even messier when you expand to other use cases. 
   3. Why is a health pass the right answer to this problem?  [respond to the concerns we’ve heard about inequities, scientific grounding]  Charles Walton
   4. What is a good health pass?  [respond to the concerns we’ve seen about privacy]  Marie Wallace
   • Privacy
   • Peer-to-peer
   • No callback to the issuer
   5. What are the key design considerations? [interoperability, messiness of the ecosystem] Julian Ranger
   • Pragmatic  
   • Decentralized data exchange 
   • Self-sovereign  note: there was an agreement to NOT use the term self-sovereign. 
   • Interoperable
   • Fit for purpose
   6. What are the technical challenges of achieving interoperability?  [point to the rest of the paper and make sure the logical leaps that the drafting groups have made are clear]  Rebecca Distler
   7. What are the recommendations and what is the path ahead for GHPC?  Dakota Gruener
   • Pragmatism: we’re defining what good is, but we’re not expecting perfect immediately. Certification.

Image Added

Resources

...

• Narrative Groups' Google Drive folder: https://drive.google.com/drive/folders/1GDkpL03rifJ89OnBfvqe96nKXMsGdkkd?usp=sharing
  • If you don't have access, request it and David Luchukshould be able to help.
• Working Document: 

• https://docs.google.com/document/d/

...

Keep in mind that we want to focus on short, medium, and long term goals: 

• Phase 1 (Within 30 Days)
• Phase 2 (Within 90 Days)
• Phase 3 (Within 6 Months)

Presentations 

• Initial Presentation (Google Slides)

Key Resources:

• GHPC Blueprint Outline v2 - The Trust Registries section is detailed on pages 25-26.
• WHO SVC Guidance

...

Notes

1. Welcome and Linux Foundation antitrust policy - http://www.linuxfoundation.org/antitrust-policy

2. Topic A

3. Topic B  

4. Topic C 

5. Wrap up 

• Next steps

Action Items

...

• 1dWrtdrbX6Yxqzbv3AQ0CT_e2_Tx4SEUyZOdBn02ffKQ/edit