1) Discuss next steps with eIDAS 2.0 blog post, 2) review new and revised sections of theToIP Technology Architecture Specification, 3) agree on workplan to finish Working Draft 01 and prepare for a session at at Internet Identity Workshop #34 (April 26-28, Mountain View, CA)
Agenda Items and Notes (including all relevant links)
Time
Agenda Item
Lead
Notes
5 min
Start recording
Welcome & antitrust notice
Introduction of new members
Agenda review
Chairs
Antitrust Policy Notice:Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
ACTION: Drummond Reedto finish conversion of the storyline slide deck text into theToIP Technology Architecture Specification and then post to the TATF Slack channel that it is ready for review of those portions of content.
ACTION: Samuel Smithto post to the Meeting Notes and TATF Slack channel a link to his paper and/or slides on chain-link confidentiality.
Report on progress and plan for calls this afternoon and next Tuesday.
Drummond explained that the group working on the post got "stuck" with regard to the key messages.
Daniel Bachenheimer pointed out that the post was not specific about what we propose as solutions to the issues we have with the post.
Drummond explained that Viky Manaila suggested that the ToIP Foundation make a submission to the Toolbox Consultation portal offering our assistance.
Tim Bouma has a general concern about the European Digital Identity Wallets approach being too "authoritarian".
Antti Kettunen joined the call and shared that he has learned several things through this dialog about the blog post. For example, he has learned that the requirements for a wallet enable the credentials to be shared with non-governmental wallets.
His concern is focused that the approach the EU is taking is potentially going to make a digital identity wallet a high-value "luxury" instead of making it a commodity that is widely adopted.
He is looking forward to working out the key points of the post.
Darrell O'Donnell is advising several governments about digital identity wallets and said that there is a difference between a "high value credential" and a "high assurance credential".
He used the example of authorizing a $500K loan or money transfer — that requires a high-assurance credential. He questions whether that is in fact a real use case.
Allan asked about how the use cases that we will cite in the ToIP Technology Architecture Specification spec and compare them with the ones that the EU is focused on. He makes the point because if we want to try to influence them, we need to have something to influence them with.
The strongest position we could be in could be to have our own test suite.
Antti asked why they would listen to us. He said there are multiple EU member states who are supporters of SSI architecture, and ToIP can amplify those opinions.
Vlad Zubenko asked about the high-security use case and said that if the wallet was able to strongly prove the identity binding with the owner, then the bank or other relying party could in fact rely on the wallet and the high-assurance credential.
Darrell explained that it is a question of priorities — focusing on high-assurance credentials and use cases will have an order of magnitude lower adoption.
Daniel Bachenheimer confirmed that digital wallets are intended to provide that identity binding.
Allan Thomson shared the analogy of the initial very simple use case that the 802.11 wifi standards focused on: a person with a wifi-enabled phone being able to walk into a coffee shop and connect. Many more higher-value and complex uses cases then became possible. But you have to nail the very simple use cases first.
Discuss who is doing what to finish Working Draft 01 and prepare for a review session at Internet Identity Workshop #34 (April 26-28, Mountain View, CA)
5 mins
Review decisions/action items
Planning for next meeting
Chairs
Screenshots/Diagrams (numbered for reference in notes above)