2021-06-24 TRTF Meeting Notes

Meeting Date

• 2021-06-24

NOTE: Meeting start (nominally 10am ET) started late today due to a Good Health Pass meeting required to approve the Good Health Pass Blueprint for recommendation to the ToIP Foundation Steering Committee. 

Attendees

• @Drummond Reed

• @Darrell O'Donnell 

• @Ken Adler (Deactivated)

• @Vitor Pamplona

• @John Walker

• @Jim StClair

• @Kaliya Young

• @Lucy Yang

• @Scott Perry

• @Savita Farooqui

• @Steven Milstein

• @Vitor Pamplona

Main Goal of this Meeting:

Discuss the primary deliverables and action items to be performed until the next meeting.

Agenda 

Recording

weblink

Notes

1. Member introductions

2. NOTES FROM LAST WEEK'S MEETING—REPEATED HERE FOR NEW MEMBERS: Orientation: mission and deliverables of this Task Force

   • Review of the Trust Registry recommendations from the 

     Good Health Pass Interoperability Blueprint

   • Key Deliverables - @Darrell O'Donnell guidance via Loom video. Key Links for Discussion:

     • GitHub Repo - https://github.com/trustoverip/tswg-trust-registry-tf

     • GitHub.IO specs - https://trinsic-id.github.io/tswg-trust-registry-tf/ 

       • NOTE: we need to move this github.io site under ToIP.

     • Swagger - https://app.swaggerhub.com/apis/darrellodonnell/GHP.TrustRegistry/0.1.0

       • NOTE: we need to move this Swagger under ToIP control, or find an alternative OpenAPI host.

3. Discovering Trust Registries (TRs)

   1. We discussed different options for how a verifier can discover other TRs

   2. One option is directories that list the DIDs for TRs

      1. These directories themselves are not TRs, but are as authoritative as the directory publisher chooses to make them (and verifiers choose to use them)

      2. Interfaces for such directories are out of scope for this Task Force

   3. Another option is "super registries" that aggregate entries from other TRs

      1. We need to decide if this is in scope or not—this is potentially a LARGE increase in scope

   4. A third option is a "trust web", i.e., TRs containing entries (DIDs) referencing other trusted TRs

4. Registry queries

   1. @Vitor Pamplona asked if a verifier may need to go to multiple TRs?

   2. We did not arrive at any clear answer, however we agreed that the goal is to make it as simple as possible for verifiers

5. DID-based vs. X.509-based TRs

   1. @Savita Farooquiasked what we do about interacting with non-compliant TRs (e.g., the EU Gateway if it ends out using a different protocol)

   2. @Drummond Reed explained that the Good Health Pass Trust Registry group recommended a way for X.509-based registries that could be supported

   3. DECISION: We will create a wiki page for an X.509 PKD interop spec

   4. ACTION: @Drummond Reed to create the X.509 PKD interop wiki page and baseline proposal 

6. Swagger API

   1. ACTION: @Darrell O'Donnell to move .json OpenAPI file into github as Swagger tooling is not free.

   2. ACTION: @Darrell O'Donnell to move the Swagger into the GitHub Project.

7. Trust Registry Relay

   1. ACTION: @Darrell O'Donnell will create a Google doc and Loom video discussing the design options for trust relay

8. Call for Developers

   1. @Ken Adler (Deactivated) is looking for Rust developers to work on the code base they are developing

   2. They plan to have their "thin slice" showcase ready to show by roughly this weekend

   3. They are looking for developers to integrate front ends, write tests, and get into containers

9. Meeting schedule

   1. We will continue with one plenary meeting a week

   2. However we will strive to accelerate async progress 

10. Agenda items for next meeting

    1. @Lucy Yang shared with this group the GCCN Trust Registry Network Definition document that includes the questions that we need to discuss and answer with the stakeholders and the community.

    2. ACTION: ALL: Read the GCCN Trust Registry Network Definition document

    3. ACTION: @Darrell O'Donnell and @Drummond Reed to figure out about reposting a fresh calendar entry for the Trust Registry Task Force weekly Thursday meeting.

Decisions

Action Items