Proposal #4: DIDComm Protocol as the basis for a Trust Spanning Layer Protocol

[mwherman2000]

Proposal 4 to ToIP TSL TF 0.2: Web 7.0 Trust Spanning Layer Framework++
(https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/)

is a summary presentation of the conversations that have been taking place here:

• Proposal 4: Web 7.0 TSLF Proposal as a Picture: Separate (but parallel) Inbound and Outbound Message Processing Stacks
• Proposal 4 Addendum: Separating the intent of Layer 2 from the intentions of Layer 3

Cheers,
Michael Herman (Web 7.0)

[mwherman2000]

[neiljthomson]

Link to the ToIP Layer 2 Trusted Spanning Protocol Assessment Checklist document?

[mwherman2000]

I'm continually updating and refining the Proposal 4 presentation. I've now updated the presentation to version 0.10.

Primary changes:

• Clarified the meanings and application of: (with examples)
  • Layer 3 Super Protocols
  • Layer 2 Base (Trust Spanning) Protocol
  • Layer 1 Subprotocols
• Several other small changes

Version 0.10 can be found at the same URL: https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

[mwherman2000]

Version 0.14 of Proposal 4 presents a compelling story (with irrefutable evidence and examples) supporting the selection of the DID Communications (DIDComm) protocol as the basis for the Layer 2 Trust Spanning Protocol for any/all decentralized system ecosystems:

• Web 7.0 DIDComm Architecture Reference Model
• ToIP Technical Architecture Specification (ToIP TAS),
• etc.

Please enjoy the following video podcast and downloadable presentation. I look forward to your comments and feedback.

Version 0.14 of Proposal 4 (video podcast and downloadable presentation) can be found at the same/usual URL:

https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

NOTE: The above video podcast references version 0.11 of Proposal 4.

NOTE: Version 0.14 of the presentation added a small number of feature changes/additions; most notably, the addition of several Layer 1 Subprotocol and Layer 3 Super Protocol use cases including the Issuer-Holder-Verifier model (starting near slide 51).

[Willem-de-kok]

Thank you for your explanations! The relation between repudiation and reputation is a lot clearer. And I can see how this contributes to privacy in a positive way.

[mwherman2000]

As you summarize at the end, your proposal is that we should "select the DID Communications (DIDComm) protocol as the Layer 2 Trust Spanning Protocol for any/all decentralized system ecosystems".

@talltree I'm going to stick with my recommendation that the DID Communications (DIDComm) protocol server as the basis for the Layer 2 Trust Spanning Layer. Based on @dhh1128 comments above, I believe he also supports using the DIDComm protocol as a basis - albeit with some additional refinements/improvements.

As of today, the DIDComm protocols meets all of the requirements stipulated by ToIP for a Layer 2 Trust Spanning Protocol and goes well beyond. My Proposal 4 also "goes well beyond" in making a compelling (irrefuatable?) presentation for the DIDComm protocol to be the basis for the Layer 2 Trust Spanning Protocol. Some of the previous proposal presentations very much lack this latter quality.

[mwherman2000]

For all of these reasons, I think that DIDComm by itself, while very good and useful, should not be where the conversation ends. The core of DIDComm, integrated with KERI, feels like something even better to me. That's why my proposal was a little more nuanced than proposal 4. But they have a lot in common. :-)

A key (lethal?) issue for KERI is that over the past 2 or so years, I have yet to consume what I consider to be a truly understandable and digestible presentation of "how" KERI works at a detailed level. I have watched a lot of meetings and recordings as well as in-person meetings at IIW34. I get the very basics but I'm a smart guy and for the most part, 90% of what I hear and see describing KERI is unintelligiable. This past week's re-presentation of Proposal 1 is another example of this IMO.

p.s. If I could grasp it, I would love to be able to produce my style of clear, developer-focused content for KERI - which would benefit a lot of folks.

[Willem-de-kok]

@mwherman2000 this presentation might be useful.

[mwherman2000]

There's 51 slides in this deck. Which ones are you specifically refering to?
I've probably watched/listened/read a dozen previous Keri presentations.

[mwherman2000]

Version 0.17 of Proposal 4 presents a compelling story (with irrefutable evidence and examples) supporting the selection of the DID Communications (DIDComm) protocol as the basis for the Layer 2 Trust Spanning Protocol for any/all decentralized system ecosystems:

• Web 7.0 DIDComm Architecture Reference Model
• ToIP Technical Architecture Specification (ToIP TAS),
• etc.

Please enjoy the following video podcast and downloadable presentation. I look forward to your comments and feedback.

Version 0.17 of Proposal 4 (video podcast and downloadable presentation) can be found at the same/usual URL:

https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

NOTE: The above video podcast references version 0.11 of Proposal 4 (the most current version of the video postcast produced to date).

NOTE: Version 0.17 of the presentation added a small number of feature changes/additions; most notably, the addition of Layer 3 Message Processing Overlays and Layer 3 Protocol Overlays (Protocol Specializations) on slides 46, 47, and 48 (73).

[mwherman2000]

The final version (version 0.26) of today's Proposal 4 contribution and presentation can be found here: https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

• Proposal 4 webcast to the ToIP TSLP TF NA/EU meeting: https://zoom.us/rec/share/vGaCQMp4xITsAVKsxqv3H1sURX5ZXWd-LjFd2yMaj-PNZlG8rsAyzfdWOZDqEBQ7.55xZUhhvqKIkSZCV
• Proposal 4 webcast to the ToIP TSLP TF APAC meeting: https://zoom.us/rec/share/IgAXxwX57hj_gGYmKt7qykFh4wuobFJEZuVka5G-dGrxt0axUzZlXpyebqjMuR7c.qLHz7yAF8FILimZw
• Proposal 4 presentation (and contribution to ToIP): https://hyperonomy.files.wordpress.com/2023/03/web-7.0-tslf-proposal-4-toip-0.26-finalx2.pdf (old version. see below for updated versions)
• Proposal 4 GitHub discussion thread: Proposal #4: DIDComm Protocol as the basis for a Trust Spanning Layer Protocol #27 (this thread)

[mwherman2000]

Version 0.27 updates/change log: Version 0.27 incorporates some changes based on feedback from yesterday's 2 presentations to the ToIP TSL Task Force. The "FINAL 2" version 0.27 of the presentation can be found in the usual spot: https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

Cc: @wenjing

[mwherman2000]

NOTE: The "Implementation View" inspired by Joe Spencer strongly suggests that only 3 layers are required in the Trust Spanning Layer Framework:

• Trust Agent Layer [4]

• Trust Spanning Layer 2

• Trust Foundation Layer 1

• Layer 1 and Layer 2 are connected by a family of TSL Subprotocols.

• Later 2 and Layer [4] are connected by families of TSL Super Protocols.

• TSL Subprotocols and TSL Super Protocols are protocol overlays built on top of the TSL Base Protocol (DIDComm Messaging V2 and the Credential Sender-Reciever Pattern)

Cc: @dhh1128 @wenjing @talltree

[mwherman2000]

Version 0.28 updates/change log: Version 0.28 adds Appendix B. See below. The "FINAL 3" version 0.28 of the presentation can be found in the usual spot: https://hyperonomy.com/2023/02/22/proposal-4-to-toip-tsl-tf-web-7-0trust-spanning-layerframework/

NOTE: If you want to create your own version of the Appendix B slide 106, the above page also contains a link to a downloadable version of the DIDComm Notation graphical design language for decentralized systems.

Appendix B is a partial response to this Proposal 3 discussion thread: #25 (reply in thread)

Cc: @dhh1128 @wenjing @talltree