TAFT will be moving to another time slot. TRTF will be taking up this time slot. No TAFT this week. Proposal by Drummond Reed to move tooff-week slot of the Technology Stack WG meeting. That slot is Mondays 08:00-09:00 PT / 16:00-17:00 UTC. First meeting 19th of December.

- thomsona provided feedback to Drummond that Monday at 8am PST does not work. Other time slot is required if possible.

Please review the TRTF Home Page updated yesterday by Drummond Reed to include a background section, updated leadership list, etc.

• thomsona what are the general requirements. Generate a list for the Trust Registry. Most likely some existing work.  
  • Categories
    • Requirements 
  • Google working document
    • Table which relevant people can add to.
  • Requirements:
    • Root of trust / agreement up front / Source of truth 
    • Relationship between TechArch is important. Needs to be compatible. 
  • Trust Registry Task Force
  • Early notes from discussions (Google Doc)
  • Andor keep other orgs informed about model Darrell O'Donnell no island

@Jacques Latour to give preso on TR definitions. 

• DIACC 
  • Cira: Issuer - Holder - Verifier
    • Allowed to issue credentials
    • Allowed to hold credentials
    • Allowed to verify credentails
• 
• Digital Identity Ecosystem : 
  • Digital Identification and Authentication Council of Canada
• Governance, Operation, and registration management
  • Governing authority: CUA
  • Academia trust registries
  • 
  • 
  • 
  • 
  • 
  • Victor: Is the global identifier necessary for the credential?
    • Jacques Latour Yes.
    • @Victor: Doesn't need to solve for impersonation to be effective.
    • Darrell O'Donnell DNS might be one of the best solutions on rigid heirarchy. 
    • Darrell O'Donnell Global trust anchor may be an island
    • @Victor   Not all formats have top anchors.
      • 3 jurisdictions.
      • 3 laws and governance structures.
  • thomsona 
    • Trust registries are setup by ecosystems that are set together.
      • Don't want trust registries connected. 
    • Missing peer to peer / arbitrary relationships
      • should use the same technologies that trust registries support
    • Andor village connection
  • Daniel Bachenheimer 
    • E-passports
      • Global uniqueness is hard
    • Trust Framework
      • Going back to wallets found it interesting.
  • Darrell O'Donnell 
    • WHO learned that the ICAO model is no longer feasible. Nation states are no longer willing to defer to the UN.
  • Daniel Bachenheimer 
    • Levels of trust
    • Granularity
  • @Victor. TRAIN allows viability. 
  • Chain of trust

APAC Discussion:

• Andor shared that there was a lot of great discussion in the NA/EU meeting based on Jacques Latour's presentation about DNS-based trust registries.
• Drummond Reed : 
  • Initial thought about decentralized, but open to learning more about DNSSEC and how it would work
  • Direct parallel: Technology Architecture Spec has three classes of identifiers. 
    • Verifiable Identifiers is the broadest category of identifiers, which intentionally includes HTTPS URLs
    • Decentralized Identifiers ← broadened the aperture to handle DNS
  • 1st Generation Work: Semantic interoperability 
    • Challenge for digital trust ecosystems
    • Can't rely on a statement from a TR unless you have agreement on the semantics.
      • Triple of identifiers (all 3 are URIs)
        • Governance should be an id
        • Verifier also an id
        • Credential type for issuers or presentation type for verifier.
• Daniel Bachenheimer 
  • Metadata and granularity. What are they allowed to issue. 
• Drummond Reed :
  
  • EU LOAs (levels of assurance) High, Substantial, Low
  • Judith Fleenor US: 3 levels defined by NIST 800-63 specifications
  • Drummond Reed that spec defines two types of LOA
    • Identity assurance
    • Authentication assurance
• @Andor 
  • Blank slate or work with existing system
  • Drummond Reed we shouldn't be redefining levels of assurance.
    • Provide a standard for framework, but leave it up to the governance framework 
    • ToIP ends at description of process\
  • Judith Fleenor 
    • What we provide, needs to have provisions for different choices.
  • Drummond Reed Enable interoperability with legacy infra w/o constraining new models. 
  • Judith Fleenor Needs to follow design principles
  • Listening sessions Drummond Reed 
  • Judith Fleenor DIF should come to ToIP to present and vise versa. 
  • Judith Fleenor rule: make sure that everyone is a member of DIF or ToIP
    
    • DIF: No EasyCLA
    • In lockstep and not cloned
  • Drummond Reed 
    • What are their proposed deliverables
    • Task Force: need to revisit 
  • Judith Fleenor 
    • Precursor deliverables. 
    • Prioritize the work items. 

• PROPOSAL: Create comparison table of various Trust registry / Trust list / Trust chain models.
  • Figure out if ToIP TR Spec could cover them all or if there are scoping/boundaries to set.