Session Date/Time: 22 Jul 2024 16:30

satp

Summary

The SATP working group meeting focused on the progress of three core drafts: the core protocol document, the architecture document, and the use case document. Discussions covered the demarcation of stage one from stage zero, updates to the architecture figure, the concept of context ID, security considerations, and the next steps for each document. The working group also discussed milestones and rechartering possibilities.

Key Discussion Points

Milestone Dates: The working group reviewed and adjusted milestone dates. The architecture and protocol documents are estimated to be ready in six months (January 2024), while the use case document needs a year (July 2024).
Stage Zero vs. Stage One: Discussions clarified the boundary between stage zero (out of scope for the current charter, focusing on pre-SATP context establishment) and stage one (the core SATP protocol). All stage zero negotiations will be moved out before stage one.
Architecture Diagram Update: The architecture diagram was updated to include a direct interaction path between the application and the gateway (API 1), aligning with the core document.
Context ID: Context ID was made mandatory in the core protocol. The discussion clarified its role in linking related asset transfers at the application level across multiple sessions, even though atomic commitment is out of scope of the current charter.
Security: Security was discussed, with emphasis on the need to ensure end-to-end atomicity and integrity of asset transfers. The group acknowledged the lack of a separate threat modeling document.
Core and Architecture Document Relationship: The relationship between the core and architecture documents was discussed. It was decided that the core document will be updated to include more pointers to the architecture document, and it will be recommended that readers read the architecture document first.
Use Cases Document: A new section on use cases that augment existing internet protocols with more trust by using distributed ledgers was added. Additional use cases that do not focus on DLTs and blockchains will be added.
Stage Zero Draft: An existing internet draft for stage zero was discussed.
Network vs Asset Network: The term "network" was clarified as being an "asset network". All documents will be updated to reflect this.

Decisions and Action Items

Action Item: The chair will work with the area director on the implications of releasing Core and Architecture documents together.
Action Item: Editors add sufficient pointers in the core document back to the architecture document. State in the Core document that readers should read Architecture first before Core.
Action Item: Add more text about use cases that do not focus on DLT/Blockchain to the use case document.
Action Item: Implementors of SATP to provide clarity to authors on any assumptions made. Claire to reach out to an intern at Quantum to get their feedback on the documentation.
Action Item: Add any links that showcase the Peter Liu proposed pay as you watch use case to the Use Case document.
Action Item: Update all documents to use the term "asset network" instead of "network".
Decision: Milestone dates were adjusted with Architecture and Protocol documents targeted for January 2024 and Use Case for July 2024.
Decision: Context ID was made mandatory.

Next Steps

Incorporate feedback from the meeting, especially on dependencies between the architecture and core documents, and on expanding the use case document.
Open the use case document for working group last call as soon as new use cases are added.
Authors to address any remaining directorate review comments.
Consider a rechartering discussion in November.
Schedule an interim meeting in approximately one month.