Page History

Updates of general interest to TATF members.

• Daniel Bachenheimer just presented on part of a panel at London Identity Week. The panel was hosted by Nick Mothershaw of Open Identity Exchange. The panel focused on the common themes for how to move digital identity and digital wallets forward.
  • Dan had a side meeting with Singapore's gov tech team that was very interested in trust frameworks.
  • ISO SC-17 is working on travel documents and SC-10 is mDL. Dan is suggesting that they look at a common, broader standard on personal identity documents.
  • Tim Bouma met with UK DCMS this week and feels there's going to be movement forward on some common views. He suggested it would be good to meet with DanB regarding progress at ISO.
• Drummond Reed said there will a major announcement from the W3C next week.
• Allan Thomson asked whether the scope of the TATF included authentication; if so, should we include consideration of FIDO2 passkeys, of which there was a great deal of focus at Identiverse last week.
  
  • Wenjing Chu said that it would definitely be a consideration in our architecture work. He made two points:
    • In the TSWG meeting on Monday, the FIDO2 protocol was discussed, and we definitely want to include it in our scope.
    • The other consideration was that passkey sync was being handled by the OS platform vendors; it is not a FIDO2 standard.
    • Tim brought up that there are other options for cross-device authentication.
    • Daniel Bachenheimer pointed out that the European Digital Identity Wallets initiative is broader than FIDO, which is specific to edge authentication. This was a consideration in the KTDI work that Accenture did with the Netherlands. So our architecture should be more generic.
    • Allan felt that authentication needed to happen at Layer 2. The spec should include that.
    • Drummond Reed agreed with Allan that ToIP authentication architecture should be broader than passkey.

•  ACTION: All members of the Technology Architecture TF to add their proposed use cases to the Google doc as soon as possible.
•  ACTION: Tim Bouma and Drummond Reed to prepare a proposed name and scope for this "policymaker" deliverable (Allan Thomson's suggestion is "ToIP Technology Introduction for Policymakers") and document this in a wiki page for next week's meeting.
  •  Tim has been working on an early version as a Google doc that outlines the basic ideas for policymakers.
•  ACTION: Neil Thomson to proceed with initial population of the TSWG terms wiki with assistance from Drummond Reed. 
•  ACTION: Drummond Reed to schedule Kaliya Young for our June 30th meeting to speak on her perspective that the ToIP stack is very "Hyperledger Aries architecture focused" and thus not friendly to other "stacks".
•  ACTION: Kevin Griffin to assist Wenjing Chu check into the issue with the TechArch repo not rendering the ToIP stack graphic.
•  ACTION: Neil Thomson to add text to the Motivations and Use Cases section to explicitly talk about what is out-of-scope.
•  ACTION: Wenjing Chu to add a new GitHub issue to propose the terms agreed to on this call: "Endpoint System", "Intermediary System", and "Supporting System".
  •  This was revised in the Google doc except for the diagrams.
  •  We had a discussion about the application of the End-to-End Principle.
  •  ACTION: Allan Thomson to propose a new term.
•  ACTION: Wenjing Chu to add a new GitHub issue to propose the rational for why the spec needs Intermediary Systems by including references to DIDCOMM V2 - https://didcomm.org/book/v2/routing and Web5 node - https://identity.foundation/decentralized-web-node/spec/

Discussion of progress on the working draft of the ToIP Technical Architecture Spec and outstanding issues.

• DECISION: We will deliver a first Public Review Draft by Thursday 8 Sept 2022 in order to present it at the Hyperledger Global Forum in Dublin beginning Sept 12.
  • Wenjing pointed out that we will need to pick up the pace on the spec if we are going to meet that deadline. This means we'll need to work at resolving the comments that we have first. He doesn't want to add new content if there is not yet agreement over current content.
  • Drummond said he intended to lean into editing and issues management in July.
  • Vlad Zubenko asked about issues management.
  • Wenjing said that we need to start posting more and working through them.
• Allan pointed out that it is not yet a spec that can be directly implemented; it is an architecture spec. So it's important to set the audience and the scope.
  • Vladimir Simjanoski felt that a strong scope statement will help us close a bunch of open issues. It will also be very useful as an educational.
• ACTION: Allan Thomson and Drummond Reed to draft an Audience and Scope section that clarifies that it is a higher-level architecture spec.
  • Wenjing felt this spec can help make it clear what the purpose of the document is in terms of limiting interoperability choices, including guidance to protocol designers.
  • Tim Bouma pointed out that four layer models are well established, but we need to get down to more specifics of the boundaries of the layers.

Wenjing Chu Darrell O'Donnell Drummond Reed