Jan Lindquist and Paul Knowles will discuss the role of intermediaries in the ToIP stack; discuss a "plan of attack" for developing a consensus picture of ToIP protocol stack layering.
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.
New Members:
5 min
Review of previous action items
Chairs
ACTION: Chairs to develop a "plan of attack" for starting to refine the protocol stack diagram suggestions and begin drafting the ToIP Technology Architecture Specification.
30 mins
The potential role of intermediaries in the ToIP stack
Jan and Paul will take us deep into the question of the role of intermediaries in the ToIP stack. See this January 13th ToIP blog post — and especially diagram #1 below (taken from that post).
The blog post was inspired by the adoption of the Data Governance Act (DGA) in the EU.
It was written by members of the Inputs and Semantics WG.
The Data Governance Act builds on EU GDPR (General Data Protection Regulation).
See diagram #2 below for an overview of how the GDPR roles (data subject, data controller, data processor) map into the DGA architecture.
A very important aspect of the DGA is that all the intermediaries must be registered with the government.
To map the DGA architecture into the ToIP model, Jan and his co-authors created diagram #1 below.
The key new role in that diagram is the Intermediary. This is essentially a specialized form of agent.
The intermediary serves a number of key functions in this enhanced model.
One of the them is adding/enhancing the data semantics per the ISWG model.
Daniel Bachenheimer pointed out that one of the main points of the ToIP model is to "disintermediate" current intermediaries.
An example he used is the IATA Travel Pass architecture (and the Good Health Pass architecture) where the intermediary became another secondary issuer.
Jan was interested in how the intermediary could share the data in other forms besides verifiable credentials.
Darrell O'Donnell did not feel that this model needs to break anything in the ToIP model.
The intermediary model can fit within the ToIP model by becoming a credential.
He shared diagram #3 below.
His point was the key privacy issues are:
Awareness of connections.
Content of data communicated within for connections.
If both of these can be controlled by the subject/holder, then it can all fit the ToIP model.
Update on a conversation Drummond had with Samuel Smith about how we could start to "decompose" the components of KERI and DIDComm to assemble a unified stack.
5 mins
Review decisions/action items
Planning for next meeting
Chairs
Screenshots/Diagrams (numbered for reference in notes above)
#1
#2
#3
Sembly sample from last halfhour of last week AM meeting:
