Versions Compared

Old Version 1

changes.mady.by.user Drummond Reed

Saved on

compared with

New Version Current

changes.mady.by.user Elisa Trevino

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Zoom Meeting Link / Recording

Attendees

Main Goal of this Meeting

...

TimeAgenda ItemLeadNotes
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 minReview of previous action itemsChairs
  •  ACTION: Drummond Reed to see if 15:00-16:00 PT / 23:00-24:00 UTC (after daylight savings) will work for APAC members and then set up the calendar invite starting Thursday Nov 4.
  •  ACTION: Drummond Reed to work with LF staff to add TF members to the TSWG mailing list.
  •  ACTION: Drummond Reed to add edit permission for Scott Perry and offer it up to any other member who wants to offer their proposal.
  •  ACTION: ALL to submit any new or revised proposals to the Protocol Stack Diagram slide deck before our meeting next week.
5 minsLogistics of coordinating NA/EU & APAC meeting each weekChairs

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 minsSpecial 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 minsReview of Design Principles relevant to the Protocol StackDrummond Reed
20 minsDiscuss how the Hourglass Principle affects the layeringAll

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
a DID-to-DID communications protocol?
  • 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:

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

Screenshots/Diagrams (numbered for reference in notes above)

#1

Decisions

  • Sample Decision Item

Action Items

  •  Sample Action Item
  • 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).

Decisions

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

Action Items