Markdown Version | Recording 1 | Recording 2 | Recording 3 | Recording 4 | Recording 5

Session Date/Time: 11 Apr 2023 14:00

SATP

Summary

The SATP working group meeting discussed takeaways from the recent Yokohama meeting, including the need to compare SATP with ISO 20022 standards and a proposed new use case for multi-CBDC networks. A call for a mailing list vote to adopt the current working documents as official group documents was announced. A significant portion of the meeting was dedicated to a presentation on Private Certified Intersection (PCI), a privacy-preserving cryptographic mechanism for establishing trust between permissioned networks. Discussions also covered potential updates to SATP for error message schemas and a proposal for modeling the protocol using state diagrams to ensure comprehensive error handling.

Key Discussion Points

• Yokohama Meeting Review: Thomas provided an overview of the Yokohama meeting, noting it was largely uneventful but served as a semi-tutorial for new participants.
  • ISO 20022 Comparison: A key action item from Yokohama was to compare SATP with ISO 20022. John Levine had raised this point. Rama explained that ISO 20022 primarily defines standardized messaging formats where messages are "promises," which differ from SATP's semantics of extinguishing an asset in one network and recreating a replica in another. This comparison is intended to be documented in the architecture document.
  • Message Flow Diagram Typo: Thomas identified a typo in the message flow diagram (version 17), specifically misnumbering in steps 2.3/2.4, which he committed to fixing and re-uploading.
  • Multi-CBDC Use Cases: Thomas noted private discussions in Japan regarding multi-CBDC networks and how SATP could facilitate asset movement between them. He plans to add a sub-use case for multi-CBDC in the use cases document. Dennis emphasized that the SATP solution should be agnostic to asset type (fungible vs. non-fungible) and cover both creation/destruction and direct exchange.
• Document Adoption: Claire and Wes announced that a call for a mailing list vote would be initiated to adopt the current working documents as official working group documents. This is the first step in moving documents through the IETF process.
• Vocabulary Document: Wes inquired about making the GitHub-hosted vocabulary document an official working group document. It was agreed that this document should be moved to the official working group repository after the main documents are adopted.
• Error Messages and State Modeling:
  • Rama suggested discussion on an error schema for SATP messages to enable gateways to employ error handling protocols beyond just success cases.
  • Dennis proposed modeling the SATP protocol using state modification diagrams (e.g., UML state charts) to exhaustively capture all possible Gateway states and ensure comprehensive coverage of error and rollback cases. This idea was supported, with Thomas suggesting a focus on pairing states between the two sides.
• Privacy-Preserving Certified Intersection (PCI) Presentation:
  • Biswajeet and Rama presented their paper "Private Certified Intersection," published at NDSS 2023.
  • Problem: How permissioned networks can establish a trust basis without revealing unnecessary private information about their certificate authorities (certifiers), particularly in the context of decentralized identity management (DIDs and Verifiable Credentials). When parties present credentials, the issuer (certifier) is inherently revealed, leading to privacy loss for the first presenter.
  • Solution: PCI allows two or more parties to efficiently identify a common set of certifiers, while validating certificates, without leaking any information about certifiers not in the output intersection. It handles malicious participants and is designed for efficiency. Three variants (PCI any, PCI any DC, PCI all) were described based on claim validation requirements.
  • Implementation and Performance: Protocols were implemented using ECDSA and BLS signature schemes. Performance tests in AWS instances across continents showed usability in practice, with BLS performing better for increasing numbers of claims due to signature aggregation.
  • Relevance to SATP: The presenters clarified that PCI is offered as research to inform the community, potentially useful for future work on the discovery part of cross-network interactions, specifically in establishing trusted identity planes between blockchain networks. It is agnostic to network type but requires adherence to cryptographic standards and certificate formats. Issues are generally external to asset ledgers, not necessarily gateways themselves.

Decisions and Action Items

• Thomas:
  • Fix typo in Message Flow Diagram (v17), specifically relabeling steps 2.3/2.4. (Due today: 00:06:01)
  • Add a sub-use case to the Use Cases document explaining how SATP could address multi-CBDC networks. (Due by next meeting)
• Claire / Wes:
  • Initiate a mailing list call for a vote on adopting the current working documents as official SATP working group documents. (Due within 2 weeks after meeting)
  • Facilitate moving the vocabulary document from GitHub to the official working group repository once documents are adopted. (After document adoption)
• Rama:
  • Write a more substantial comparison of SATP with ISO 20022 on the mailing list and, eventually, in the architecture document. (Due by next meeting)
  • Share the link to the "Private Certified Intersection" paper, presentation slides, and YouTube video on the mailing list. (Due shortly after meeting)
• Dennis:
  • Start a mailing list discussion proposing the use of state modification diagrams (e.g., UML state charts) to model the SATP protocol for comprehensive error and rollback case analysis. Potentially form a small subgroup to work on this. (Due by next meeting)
• Alex (Note Taker): Circulate meeting notes to the working group and upload to the data tracker. (Due shortly after meeting)

Next Steps

• Working group members are encouraged to participate in the upcoming mailing list vote on document adoption.
• Engage in the mailing list discussion regarding an error schema and the proposed state modeling of the SATP protocol.
• Review the shared resources (paper, slides, video) on Private Certified Intersection.
• Authors to progress on their assigned action items (diagram fixes, new use cases, ISO 20022 comparison).
• The next official meeting will be held in approximately one month, with mailing list discussions continuing in the interim.

Session Date/Time: 11 Apr 2023 14:00

SATP

Summary

The SATP working group meeting discussed takeaways from the recent Yokohama meeting, including the need to compare SATP with ISO 20022 standards and a proposed new use case for multi-CBDC networks. A call for a mailing list vote to adopt the current working documents as official group documents was announced. A significant portion of the meeting was dedicated to a presentation on Private Certified Intersection (PCI), a privacy-preserving cryptographic mechanism for establishing trust between permissioned networks. Discussions also covered potential updates to SATP for error message schemas and a proposal for modeling the protocol using state diagrams to ensure comprehensive error handling.

Key Discussion Points

• Yokohama Meeting Review: Thomas provided an overview of the Yokohama meeting, noting it was largely uneventful but served as a semi-tutorial for new participants.
  • ISO 20022 Comparison: A key action item from Yokohama was to compare SATP with ISO 20022. John Levine had raised this point. Rama explained that ISO 20022 primarily defines standardized messaging formats where messages are "promises," which differ from SATP's semantics of extinguishing an asset in one network and recreating a replica in another. This comparison is intended to be documented in the architecture document.
  • Message Flow Diagram Typo: Thomas identified a typo in the message flow diagram (version 17), specifically misnumbering in steps 2.3/2.4, which he committed to fixing and re-uploading.
  • Multi-CBDC Use Cases: Thomas noted private discussions in Japan regarding multi-CBDC networks and how SATP could facilitate asset movement between them. He plans to add a sub-use case for multi-CBDC in the use cases document. Dennis emphasized that the SATP solution should be agnostic to asset type (fungible vs. non-fungible) and cover both creation/destruction and direct exchange.
• Document Adoption: Claire and Wes announced that a call for a mailing list vote would be initiated to adopt the current working documents as official working group documents. This is the first step in moving documents through the IETF process.
• Vocabulary Document: Wes inquired about making the GitHub-hosted vocabulary document an official working group document. It was agreed that this document should be moved to the official working group repository after the main documents are adopted.
• Error Messages and State Modeling:
  • Rama suggested discussion on an error schema for SATP messages to enable gateways to employ error handling protocols beyond just success cases.
  • Dennis proposed modeling the SATP protocol using state modification diagrams (e.g., UML state charts) to exhaustively capture all possible Gateway states and ensure comprehensive coverage of error and rollback cases. This idea was supported, with Thomas suggesting a focus on pairing states between the two sides.
• Privacy-Preserving Certified Intersection (PCI) Presentation:
  • Biswajeet and Rama presented their paper "Private Certified Intersection," published at NDSS 2023.
  • Problem: How permissioned networks can establish a trust basis without revealing unnecessary private information about their certificate authorities (certifiers), particularly in the context of decentralized identity management (DIDs and Verifiable Credentials). When parties present credentials, the issuer (certifier) is inherently revealed, leading to privacy loss for the first presenter.
  • Solution: PCI allows two or more parties to efficiently identify a common set of certifiers, while validating certificates, without leaking any information about certifiers not in the output intersection. It handles malicious participants and is designed for efficiency. Three variants (PCI any, PCI any DC, PCI all) were described based on claim validation requirements.
  • Implementation and Performance: Protocols were implemented using ECDSA and BLS signature schemes. Performance tests in AWS instances across continents showed usability in practice, with BLS performing better for increasing numbers of claims due to signature aggregation.
  • Relevance to SATP: The presenters clarified that PCI is offered as research to inform the community, potentially useful for future work on the discovery part of cross-network interactions, specifically in establishing trusted identity planes between blockchain networks. It is agnostic to network type but requires adherence to cryptographic standards and certificate formats. Issues are generally external to asset ledgers, not necessarily gateways themselves.

Decisions and Action Items

• Thomas:
  • Fix typo in Message Flow Diagram (v17), specifically relabeling steps 2.3/2.4. (Due today: 00:06:01)
  • Add a sub-use case to the Use Cases document explaining how SATP could address multi-CBDC networks. (Due by next meeting)
• Claire / Wes:
  • Initiate a mailing list call for a vote on adopting the current working documents as official SATP working group documents. (Due within 2 weeks after meeting)
  • Facilitate moving the vocabulary document from GitHub to the official working group repository once documents are adopted. (After document adoption)
• Rama:
  • Write a more substantial comparison of SATP with ISO 20022 on the mailing list and, eventually, in the architecture document. (Due by next meeting)
  • Share the link to the "Private Certified Intersection" paper, presentation slides, and YouTube video on the mailing list. (Due shortly after meeting)
• Dennis:
  • Start a mailing list discussion proposing the use of state modification diagrams (e.g., UML state charts) to model the SATP protocol for comprehensive error and rollback case analysis. Potentially form a small subgroup to work on this. (Due by next meeting)
• Alex (Note Taker): Circulate meeting notes to the working group and upload to the data tracker. (Due shortly after meeting)

Next Steps

• Working group members are encouraged to participate in the upcoming mailing list vote on document adoption.
• Engage in the mailing list discussion regarding an error schema and the proposed state modeling of the SATP protocol.
• Review the shared resources (paper, slides, video) on Private Certified Intersection.
• Authors to progress on their assigned action items (diagram fixes, new use cases, ISO 20022 comparison).
• The next official meeting will be held in approximately one month, with mailing list discussions continuing in the interim.

Session Date/Time: 11 Apr 2023 14:00

SATP

Summary

The SATP working group meeting discussed takeaways from the recent Yokohama meeting, including the need to compare SATP with ISO 20022 standards and a proposed new use case for multi-CBDC networks. A call for a mailing list vote to adopt the current working documents as official group documents was announced. A significant portion of the meeting was dedicated to a presentation on Private Certified Intersection (PCI), a privacy-preserving cryptographic mechanism for establishing trust between permissioned networks. Discussions also covered potential updates to SATP for error message schemas and a proposal for modeling the protocol using state diagrams to ensure comprehensive error handling.

Key Discussion Points

• Yokohama Meeting Review: Thomas provided an overview of the Yokohama meeting, noting it was largely uneventful but served as a semi-tutorial for new participants.
  • ISO 20022 Comparison: A key action item from Yokohama was to compare SATP with ISO 20022. John Levine had raised this point. Rama explained that ISO 20022 primarily defines standardized messaging formats where messages are "promises," which differ from SATP's semantics of extinguishing an asset in one network and recreating a replica in another. This comparison is intended to be documented in the architecture document.
  • Message Flow Diagram Typo: Thomas identified a typo in the message flow diagram (version 17), specifically misnumbering in steps 2.3/2.4, which he committed to fixing and re-uploading.
  • Multi-CBDC Use Cases: Thomas noted private discussions in Japan regarding multi-CBDC networks and how SATP could facilitate asset movement between them. He plans to add a sub-use case for multi-CBDC in the use cases document. Dennis emphasized that the SATP solution should be agnostic to asset type (fungible vs. non-fungible) and cover both creation/destruction and direct exchange.
• Document Adoption: Claire and Wes announced that a call for a mailing list vote would be initiated to adopt the current working documents as official working group documents. This is the first step in moving documents through the IETF process.
• Vocabulary Document: Wes inquired about making the GitHub-hosted vocabulary document an official working group document. It was agreed that this document should be moved to the official working group repository after the main documents are adopted.
• Error Messages and State Modeling:
  • Rama suggested discussion on an error schema for SATP messages to enable gateways to employ error handling protocols beyond just success cases.
  • Dennis proposed modeling the SATP protocol using state modification diagrams (e.g., UML state charts) to exhaustively capture all possible Gateway states and ensure comprehensive coverage of error and rollback cases. This idea was supported, with Thomas suggesting a focus on pairing states between the two sides.
• Privacy-Preserving Certified Intersection (PCI) Presentation:
  • Biswajeet and Rama presented their paper "Private Certified Intersection," published at NDSS 2023.
  • Problem: How permissioned networks can establish a trust basis without revealing unnecessary private information about their certificate authorities (certifiers), particularly in the context of decentralized identity management (DIDs and Verifiable Credentials). When parties present credentials, the issuer (certifier) is inherently revealed, leading to privacy loss for the first presenter.
  • Solution: PCI allows two or more parties to efficiently identify a common set of certifiers, while validating certificates, without leaking any information about certifiers not in the output intersection. It handles malicious participants and is designed for efficiency. Three variants (PCI any, PCI any DC, PCI all) were described based on claim validation requirements.
  • Implementation and Performance: Protocols were implemented using ECDSA and BLS signature schemes. Performance tests in AWS instances across continents showed usability in practice, with BLS performing better for increasing numbers of claims due to signature aggregation.
  • Relevance to SATP: The presenters clarified that PCI is offered as research to inform the community, potentially useful for future work on the discovery part of cross-network interactions, specifically in establishing trusted identity planes between blockchain networks. It is agnostic to network type but requires adherence to cryptographic standards and certificate formats. Issues are generally external to asset ledgers, not necessarily gateways themselves.

Decisions and Action Items

• Thomas:
  • Fix typo in Message Flow Diagram (v17), specifically relabeling steps 2.3/2.4. (Due today: 00:06:01)
  • Add a sub-use case to the Use Cases document explaining how SATP could address multi-CBDC networks. (Due by next meeting)
• Claire / Wes:
  • Initiate a mailing list call for a vote on adopting the current working documents as official SATP working group documents. (Due within 2 weeks after meeting)
  • Facilitate moving the vocabulary document from GitHub to the official working group repository once documents are adopted. (After document adoption)
• Rama:
  • Write a more substantial comparison of SATP with ISO 20022 on the mailing list and, eventually, in the architecture document. (Due by next meeting)
  • Share the link to the "Private Certified Intersection" paper, presentation slides, and YouTube video on the mailing list. (Due shortly after meeting)
• Dennis:
  • Start a mailing list discussion proposing the use of state modification diagrams (e.g., UML state charts) to model the SATP protocol for comprehensive error and rollback case analysis. Potentially form a small subgroup to work on this. (Due by next meeting)
• Alex (Note Taker): Circulate meeting notes to the working group and upload to the data tracker. (Due shortly after meeting)

Next Steps

• Working group members are encouraged to participate in the upcoming mailing list vote on document adoption.
• Engage in the mailing list discussion regarding an error schema and the proposed state modeling of the SATP protocol.
• Review the shared resources (paper, slides, video) on Private Certified Intersection.
• Authors to progress on their assigned action items (diagram fixes, new use cases, ISO 20022 comparison).
• The next official meeting will be held in approximately one month, with mailing list discussions continuing in the interim.

Session Date/Time: 11 Apr 2023 14:00

SATP

Summary

The SATP working group meeting discussed takeaways from the recent Yokohama meeting, including the need to compare SATP with ISO 20022 standards and a proposed new use case for multi-CBDC networks. A call for a mailing list vote to adopt the current working documents as official group documents was announced. A significant portion of the meeting was dedicated to a presentation on Private Certified Intersection (PCI), a privacy-preserving cryptographic mechanism for establishing trust between permissioned networks. Discussions also covered potential updates to SATP for error message schemas and a proposal for modeling the protocol using state diagrams to ensure comprehensive error handling.

Key Discussion Points

• Yokohama Meeting Review: Thomas provided an overview of the Yokohama meeting, noting it was largely uneventful but served as a semi-tutorial for new participants.
  • ISO 20022 Comparison: A key action item from Yokohama was to compare SATP with ISO 20022. John Levine had raised this point. Rama explained that ISO 20022 primarily defines standardized messaging formats where messages are "promises," which differ from SATP's semantics of extinguishing an asset in one network and recreating a replica in another. This comparison is intended to be documented in the architecture document.
  • Message Flow Diagram Typo: Thomas identified a typo in the message flow diagram (version 17), specifically misnumbering in steps 2.3/2.4, which he committed to fixing and re-uploading.
  • Multi-CBDC Use Cases: Thomas noted private discussions in Japan regarding multi-CBDC networks and how SATP could facilitate asset movement between them. He plans to add a sub-use case for multi-CBDC in the use cases document. Dennis emphasized that the SATP solution should be agnostic to asset type (fungible vs. non-fungible) and cover both creation/destruction and direct exchange.
• Document Adoption: Claire and Wes announced that a call for a mailing list vote would be initiated to adopt the current working documents as official working group documents. This is the first step in moving documents through the IETF process.
• Vocabulary Document: Wes inquired about making the GitHub-hosted vocabulary document an official working group document. It was agreed that this document should be moved to the official working group repository after the main documents are adopted.
• Error Messages and State Modeling:
  • Rama suggested discussion on an error schema for SATP messages to enable gateways to employ error handling protocols beyond just success cases.
  • Dennis proposed modeling the SATP protocol using state modification diagrams (e.g., UML state charts) to exhaustively capture all possible Gateway states and ensure comprehensive coverage of error and rollback cases. This idea was supported, with Thomas suggesting a focus on pairing states between the two sides.
• Privacy-Preserving Certified Intersection (PCI) Presentation:
  • Biswajeet and Rama presented their paper "Private Certified Intersection," published at NDSS 2023.
  • Problem: How permissioned networks can establish a trust basis without revealing unnecessary private information about their certificate authorities (certifiers), particularly in the context of decentralized identity management (DIDs and Verifiable Credentials). When parties present credentials, the issuer (certifier) is inherently revealed, leading to privacy loss for the first presenter.
  • Solution: PCI allows two or more parties to efficiently identify a common set of certifiers, while validating certificates, without leaking any information about certifiers not in the output intersection. It handles malicious participants and is designed for efficiency. Three variants (PCI any, PCI any DC, PCI all) were described based on claim validation requirements.
  • Implementation and Performance: Protocols were implemented using ECDSA and BLS signature schemes. Performance tests in AWS instances across continents showed usability in practice, with BLS performing better for increasing numbers of claims due to signature aggregation.
  • Relevance to SATP: The presenters clarified that PCI is offered as research to inform the community, potentially useful for future work on the discovery part of cross-network interactions, specifically in establishing trusted identity planes between blockchain networks. It is agnostic to network type but requires adherence to cryptographic standards and certificate formats. Issues are generally external to asset ledgers, not necessarily gateways themselves.

Decisions and Action Items

• Thomas:
  • Fix typo in Message Flow Diagram (v17), specifically relabeling steps 2.3/2.4. (Due today: 00:06:01)
  • Add a sub-use case to the Use Cases document explaining how SATP could address multi-CBDC networks. (Due by next meeting)
• Claire / Wes:
  • Initiate a mailing list call for a vote on adopting the current working documents as official SATP working group documents. (Due within 2 weeks after meeting)
  • Facilitate moving the vocabulary document from GitHub to the official working group repository once documents are adopted. (After document adoption)
• Rama:
  • Write a more substantial comparison of SATP with ISO 20022 on the mailing list and, eventually, in the architecture document. (Due by next meeting)
  • Share the link to the "Private Certified Intersection" paper, presentation slides, and YouTube video on the mailing list. (Due shortly after meeting)
• Dennis:
  • Start a mailing list discussion proposing the use of state modification diagrams (e.g., UML state charts) to model the SATP protocol for comprehensive error and rollback case analysis. Potentially form a small subgroup to work on this. (Due by next meeting)
• Alex (Note Taker): Circulate meeting notes to the working group and upload to the data tracker. (Due shortly after meeting)

Next Steps

• Working group members are encouraged to participate in the upcoming mailing list vote on document adoption.
• Engage in the mailing list discussion regarding an error schema and the proposed state modeling of the SATP protocol.
• Review the shared resources (paper, slides, video) on Private Certified Intersection.
• Authors to progress on their assigned action items (diagram fixes, new use cases, ISO 20022 comparison).
• The next official meeting will be held in approximately one month, with mailing list discussions continuing in the interim.

Session Date/Time: 11 Apr 2023 14:00

SATP

Summary

The SATP working group meeting discussed takeaways from the recent Yokohama meeting, including the need to compare SATP with ISO 20022 standards and a proposed new use case for multi-CBDC networks. A call for a mailing list vote to adopt the current working documents as official group documents was announced. A significant portion of the meeting was dedicated to a presentation on Private Certified Intersection (PCI), a privacy-preserving cryptographic mechanism for establishing trust between permissioned networks. Discussions also covered potential updates to SATP for error message schemas and a proposal for modeling the protocol using state diagrams to ensure comprehensive error handling.

Key Discussion Points

• Yokohama Meeting Review: Thomas provided an overview of the Yokohama meeting, noting it was largely uneventful but served as a semi-tutorial for new participants.
  • ISO 20022 Comparison: A key action item from Yokohama was to compare SATP with ISO 20022. John Levine had raised this point. Rama explained that ISO 20022 primarily defines standardized messaging formats where messages are "promises," which differ from SATP's semantics of extinguishing an asset in one network and recreating a replica in another. This comparison is intended to be documented in the architecture document.
  • Message Flow Diagram Typo: Thomas identified a typo in the message flow diagram (version 17), specifically misnumbering in steps 2.3/2.4, which he committed to fixing and re-uploading.
  • Multi-CBDC Use Cases: Thomas noted private discussions in Japan regarding multi-CBDC networks and how SATP could facilitate asset movement between them. He plans to add a sub-use case for multi-CBDC in the use cases document. Dennis emphasized that the SATP solution should be agnostic to asset type (fungible vs. non-fungible) and cover both creation/destruction and direct exchange.
• Document Adoption: Claire and Wes announced that a call for a mailing list vote would be initiated to adopt the current working documents as official working group documents. This is the first step in moving documents through the IETF process.
• Vocabulary Document: Wes inquired about making the GitHub-hosted vocabulary document an official working group document. It was agreed that this document should be moved to the official working group repository after the main documents are adopted.
• Error Messages and State Modeling:
  • Rama suggested discussion on an error schema for SATP messages to enable gateways to employ error handling protocols beyond just success cases.
  • Dennis proposed modeling the SATP protocol using state modification diagrams (e.g., UML state charts) to exhaustively capture all possible Gateway states and ensure comprehensive coverage of error and rollback cases. This idea was supported, with Thomas suggesting a focus on pairing states between the two sides.
• Privacy-Preserving Certified Intersection (PCI) Presentation:
  • Biswajeet and Rama presented their paper "Private Certified Intersection," published at NDSS 2023.
  • Problem: How permissioned networks can establish a trust basis without revealing unnecessary private information about their certificate authorities (certifiers), particularly in the context of decentralized identity management (DIDs and Verifiable Credentials). When parties present credentials, the issuer (certifier) is inherently revealed, leading to privacy loss for the first presenter.
  • Solution: PCI allows two or more parties to efficiently identify a common set of certifiers, while validating certificates, without leaking any information about certifiers not in the output intersection. It handles malicious participants and is designed for efficiency. Three variants (PCI any, PCI any DC, PCI all) were described based on claim validation requirements.
  • Implementation and Performance: Protocols were implemented using ECDSA and BLS signature schemes. Performance tests in AWS instances across continents showed usability in practice, with BLS performing better for increasing numbers of claims due to signature aggregation.
  • Relevance to SATP: The presenters clarified that PCI is offered as research to inform the community, potentially useful for future work on the discovery part of cross-network interactions, specifically in establishing trusted identity planes between blockchain networks. It is agnostic to network type but requires adherence to cryptographic standards and certificate formats. Issues are generally external to asset ledgers, not necessarily gateways themselves.

Decisions and Action Items

• Thomas:
  • Fix typo in Message Flow Diagram (v17), specifically relabeling steps 2.3/2.4. (Due today: 00:06:01)
  • Add a sub-use case to the Use Cases document explaining how SATP could address multi-CBDC networks. (Due by next meeting)
• Claire / Wes:
  • Initiate a mailing list call for a vote on adopting the current working documents as official SATP working group documents. (Due within 2 weeks after meeting)
  • Facilitate moving the vocabulary document from GitHub to the official working group repository once documents are adopted. (After document adoption)
• Rama:
  • Write a more substantial comparison of SATP with ISO 20022 on the mailing list and, eventually, in the architecture document. (Due by next meeting)
  • Share the link to the "Private Certified Intersection" paper, presentation slides, and YouTube video on the mailing list. (Due shortly after meeting)
• Dennis:
  • Start a mailing list discussion proposing the use of state modification diagrams (e.g., UML state charts) to model the SATP protocol for comprehensive error and rollback case analysis. Potentially form a small subgroup to work on this. (Due by next meeting)
• Alex (Note Taker): Circulate meeting notes to the working group and upload to the data tracker. (Due shortly after meeting)

Next Steps

• Working group members are encouraged to participate in the upcoming mailing list vote on document adoption.
• Engage in the mailing list discussion regarding an error schema and the proposed state modeling of the SATP protocol.
• Review the shared resources (paper, slides, video) on Private Certified Intersection.
• Authors to progress on their assigned action items (diagram fixes, new use cases, ISO 20022 comparison).
• The next official meeting will be held in approximately one month, with mailing list discussions continuing in the interim.