Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Meeting Date

  •  
    • NA/EU 07:00-8:00 PT / 15:00-16:00 UTC 
    • APAC 1:00-2:00PM PT / 21:00-22:00 UTC  <== NOTE THE NEW TIME

Zoom Meeting Link / Recording

Attendees

Main Goal of this Meeting

Input from Dr. Sam Smith (if he's able to attend); determine what types of diagrams we will need and who is doing consolidated drafts of each; decide on holiday meeting schedule.

Agenda Items and Notes (including all relevant links)

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: Adrian Gropper
5 minReview of previous action itemsChairs
  • ACTION: ALL — Over the US Thanksgiving break, think about what other types of diagrams we need in addition to a protocol stack diagram, then if possible add your suggested version of other diagrams to the ToIP Protocol Stack Diagrams slide deck.
  • ACTION: ALL — review the outline of the ToIP Technology Architecture Specification draft and identify sections where you are interested in contributing text.
15 minsInput from Dr. Sam Smith

Sam Smith
(if able to attend)

Discuss Sam's thoughts on protocol layering and where KERI protocols, serialization formats (such as CESR), and KERI key management would fit.

  • Sam felt it was very important to "unpack" the trust spanning layers
  • To do this, he had to go over the "PAC Theorem" - see the slide screenshots #1-#6 below.
  • It means that authenticity and confidentiality and privacy
  • KERI layers it: authenticity, then confidentiality, then privacy
    • Privacy is achieved by using a combination of legal liability on participants
  • That could be two stacks - one for data in motion and one with data at rest
  • Antti Kettunen pointed out that you can link a transaction to one or more verifiable credentials in order to prove authenticity
  • Sam pointed out that can work, but it is based on reputational trust, because they are trusting recourse
  • Legal systems only recognize reputation associated with legal identity
  • The key conclusion from this is that we need to look at the layering of authenticity and confidentiality and privacy
  • Sam pointed out that we have the communication stack and the priority stack
  • Sam said, "The reason this is difficult is that security has always been a bolt-on, but if you want to make it critical."
  • Darrell pointed out that we need to decide about the three factors. And all ZKP-system will not provide authenticity.
  • Philip Feairheller said that different priorities work for different use cases.
  • Antti Kettunen thanked Sam for bringing the PAC Theorem.
5 minSquare white paper

Square (where Daniel Buchner recently left Microsoft to join) put out this white paper called tbDEX: A Liquidity Protocol v0.1. Quote:

At its core, the tbDEX protocol facilitates the formation of networks of mutual trust between counterparties that are not centrally controlled; it allows participants to negotiate trust directly with each other (or rely on mutually trusted third-parties to vouch for counterparties), and price their exchanges to account for perceived risk and specific requirements.

  •  Do TF members want to review and discuss at the next meeting?
20 minsTechnical architecture diagram typesAll

Discuss/decide what different types of diagrams we need for the ToIP Technology Architecture Specification. See this Medium article for more about types #2 thru #6 below.

  1. Protocol stack diagram
  2. Application architecture diagram
  3. Integration architecture diagram
  4. Deployment architecture diagram
  5. DevOps Architecture diagram
  6. Data Architecture diagram

NEEDS 

  • Verifiable Credentials Exchange - this is where things started, so not showing detail on it would be odd. 


10 minsPossible post-holiday special meetingsAll
  • Daniel Hardman will be returning to Utah over the holidays
  • Drummond Reed is thinking of making a trip down to Utah to meet with Daniel, Sam Smith, Phil Windley, and other architects to talk about DIDComm, KERI, and the ToIP Technology Architecture Specification
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Holiday meeting schedule:

  • Next meeting is on Dec 16 — should we hold it? (Drummond Reed will be on holiday)
  • Skip Dec 30th
  • First 2020 meeting Jan 13

ACTION ITEM: Think about PAC Theorem

ACTION ITEM: Read Square paper.

Screenshots/Diagrams (numbered for reference in notes above)

#1

#2

#3

#4

#5


Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels