• Concepts & Terminology tools & guides to be included in TRTF work 
  • Drummond Reed | Neil Thomson : Proceeding development of tools. Tools need another 2 months.
    • Terminology toolbox. Required for final glossary but terms wiki can happen in parallel. 
    • Require a mental model : Picture or diagram that shows how the group of terms relate and helps make terms clear. Drummond Reed added an example (screenshot #1 below) from this eSSIF-Labs Glossary page.
    • Neil Thomson TR: simple lookup list. Complexity comes in proving the trust.  
    • Related Chat:
      • Scott Perry Mental models are not a trivial task to build.  If this is a core requirement, we need a drafting session.  Unless we have Rieks do them for every group.
      • Tim Bouma :
        • DNS: Name Lookup
          Trust Registry: Authority Lookup
      • Darrell O'Donnell : authenticity/provenance chain - to me that’s a post v2 capability. It’s helpful to back up the basic answers, but not required. Further for many systems it would be a blocker.
      • Vladimir Simjanoski +1 for mental model. not defining it explicitly doesn't mean we don't have one when designing the underlying spec / API. getting it right is difficult, though (agreed with Scott)
      • Neil Thomson @ Darrell - agreed on post v2. However, how do we gradually incorporate governance with that goal in mind. Separate discussion - will bring up in Gov Stack WG.
      • Darrell O'Donnell : 

      • @Neil - I think we can get there relatively easily. When you ask “is this an Authoritative Issuer of credential type X, under EGF Y?” you may be able to ask “and how do you do this?”

        The answer for many will be “because I am the authority” but for some it would be “see this chain of provenance”.

      • Over time I believe systems will prefer one or the other path. Less formal ecosystems will likely stay light, while more formal/regulated ecosystems would lean towards authentic provenance.

Chairs will lead discussion on recapping & reviewing the various discussions happening in the TF meetings and Github discussions.
This includes recap on Trust Registry component & Trust Task model.

Review: 

• Relevant TR Lead Stuff:
  • https://github.com/trustoverip/tswg-trust-registry-tf/discussions/68#discussioncomment-4919723
  • Leaders got together to make sure alignment.
    • Antti Kettunen descriptive work of what TR work looks like today.
    • Darrell O'Donnell discussed his concept of the TR framework as a way for governance and technical stacks to align across all 4 layers of the ToIP stack
    • Andor Kesselman and Antti Kettunen : How do you build the context for a decision?
    • https://github.com/trustoverip/tswg-trust-registry-tf/discussions/68#discussioncomment-4919723
  • @Jacques: https://www.cira.ca/cira-dnssec-practice-statement-ca

•  Define TRTF Deliverables for V2 #61
  • Daniel Hardman: Drew a distinction between Layer 2 and Layer 3, as  relationship oriented vs. task oriented, respectively. Defined the scope of a TR: "Is this piece of evidence grounded in conventions and entities that I consider trustworthy?"

• • Tim Bouma expanded on that model, defining Layer 4 as rights oriented, and layer 1 as commitment oriented. Is what I am relying on is accurate/legitimate and based on intentions of: 1) the rules of a governance framework, and 2) an authorized action/assertion of an actor based on those rules?
  • Darrell provided a useful diagram and also shared that the TR says: "what do I need to participate in this ecosystem?".
• Model the process for TRTF w/ Milestones #67
  •   Andor Kesselman did some process refinements here. And Drummond provided a helpful link to relevant work happening in the TSPTF related to the process flow.
• Model Trust Decision Data Flow Process #68

• • Andor Kesselman with a proposal last week around trust chaining and trust discovery. Neil added some helpful commentary about vectors of trust, with data chaining, data processing chain, signing officer, and governance process.
  • Scott Whitmire : Some concerns about "What is a trust registry?".
  • What does interoperability mean across trust registry: Darrell O'Donnell and Drummond Reed 
•  Define Requirements and/or Goals For You As a Stakeholder #69
  • Tim Bouma drew a descriptive diagram on "trust things" that has resonated with quite a few people: https://github.com/trustoverip/tswg-trust-registry-tf/discussions/69#discussioncomment-4799881
  • Eric Drury  added some requirements around the goals and wants to know: 
    • What is the minimum data / meta-data (if any) contained in a trust registry?
    • What is the minimum data essential for the functioning of a trust registry?
  • Drummond Reed also added some good clarification on requirements in this comment here related to the quad model of holder, verifier, issuer, and registry. 
    • Bouma: "An actor is authorized to carry out an action, either on its own behalf, or on behalf of another actor."
  • Jo Spencer also added some requirements here, with a lot of requirements around cross domain VDRs. 
• Relevant Work In TSPTF:
  • Andor Suggests a Layer Above TSP that addresses reputation trust. This would be a layer above TSP and below TR.