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

5 mins

Logistics of coordinating NA/EU & APAC meeting each week

Chairs

Suggestions to simplify admin and note-taking:

• Publish one Meeting Notes page for each set of Thursday meetings (not two separate pages).

• Keep the notes from the first (NA/EU) meeting, then save the page.

• Re-open editing of the page for the second (APAC) meeting and append notes for each agenda item.

• Post the combined notes and Action Items after the APAC meeting.

DECISION: We will use one Meeting Notes page for each pair of weekly NA/EU and APAC meetings.

5 mins

Special find from Darrell—an A16Z podcast that touches indirectly on ToIP and directly on DIDs!

@Darrell O'Donnell

• Listen to the Oct 15 A16Z podcast "Crypto Security and the New Web3 Mindsets for Users". If you don't have time for all 30 mins:

  • Start at 27:00 and listen to 28:30 to hear the part about "a security network" (which pretty much exactly describes what we are building with ToIP).

  • Then listen from 28:55 to 30:45 to understand why they recommend using DIDs to have as many keys as you want and be able to rotate keys.

15 mins

Review of Design Principles relevant to the Protocol Stack

@Drummond Reed

• The Community Review draft of Design Principles for the ToIP Stack is ready.

• ACTION: ALL — Please review the Community Review draft of Design Principles for the ToIP Stack in the next week.

20 mins

Discuss how the Hourglass Principle affects the layering

All

We had this list of questions to discuss:

• Do we have consensus about the Hourglass Principle?

• Do we agree on Sam Smith's "waist and neck" diagram (that he got from another paper)?

• If so, how does this affect the layering of the protocols immediately above and below?

• Is there agreement that the trust-spanning layer is a DID-to-DID communications protocol?

• What are the candidates for that protocol?

Given the small group—due to the calendaring challenges with the US/EU time changes—discussion focused on the following slides from the ToIP Protocol Stack Diagram:

• @Antti Kettunen's new diagram

• The DIF stack diagram that Darrell added

• The "waist and neck" diagram from @Sam Smith's  KERI white paper (which Sam himself got from another source)

• @Wenjing Chu's stack diagram with his depiction of DID-to-DID communications

Our conclusions and action items:

• There are multiple ways to look at the stack diagrams depending on what components you are focused on.

• The "waist and neck" diagram needs to be extended beyond TCP/IP as a transport.

• The Hourglass Principle does apply, but we need to be specific about the requirements at the "waist".

• ACTION: @Drummond Reed to draw a new version of the "waist and neck" diagram showing multiple transport layer protocol options.

• ACTION: @Drummond Reed to talk with @Daniel Hardman to prep for a discussion of DIDComm at the next meeting.

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs

• @Daniel Hardman will attend the next meeting to talk about his view of the protocol stack and DIDComm (of which he is a key architect).