**Session Date/Time:** 08 Oct 2024 14:00

# [SATP](../wg/satp.html)

## Summary

The SATP Working Group met to discuss the status of `draft-ietf-satp-core-06` and `draft-ietf-satp-use-cases`, with a strong inclination from authors to initiate Working Group Last Call (WGLC) for both drafts at the upcoming IETF 121 meeting in Dublin. Key updates to `core-06` include streamlining API references, adding example code, and updating UUID versions. Discussions also covered IANA considerations for an SATP URI and the possibility of a hackathon to test the protocol. The group plans to begin discussions at IETF 121 about the scope and desired items for a potential future WG charter.

## Key Discussion Points

*   **`draft-ietf-satp-core-06` Updates:**
    *   **Automated System Figure Issues:** Noted that the automated submission system currently "crunches up" figures when converting from Markdown to text. The figures in `core-06` remain identical to `core-05` and this issue will require improvements to the submission system.
    *   **API Reference Simplification:** All mentions of hypothetical API 1 and API 3 were removed, with the draft now focusing solely on API 2 to avoid promising future work items.
    *   **Example Code Addition:** Example code snippets for each message type and message flow (e.g., lock assertion messages) were added for clarity.
    *   **Bug Fixes:** A bug where Gateway G2 was in some instances omitting signatures on receipts was corrected.
    *   **Architecture Document Prerequisite:** Explicit text was added to the document's introduction, directing readers to consult the SATP architecture document prior to reading `core-06`.
    *   **New References:** Important external references were added, including the European Union's MiCA (Markets in Crypto-Assets) regulation.
    *   **UUID Version Update:** Unique Identifiers (UUIDs) were updated from V2 to V4 throughout the draft. This change was made to address V2's constraints (e.g., 60 new UUIDs per seven minutes), which were deemed insufficient for SATP's potential throughput.
    *   **Casing Consistency:** Message field labels were standardized to camelCase, which resulted in many diffs but represented a syntactic rather than functional change.
    *   **Outstanding TODOs:** An outstanding TODO regarding a missing signature in messages has been addressed in an unreleased version of the draft.
*   **`draft-ietf-satp-use-cases` Status:**
    *   Authors indicated the `use-cases` draft is ready for WGLC, with no significant changes since the last IETF meeting.
    *   Limited reviews have been received to date, suggesting that a WGLC would be an effective trigger for broader community feedback.
    *   Minor updates are pending, primarily the addition of specific links identified by Peter.
*   **IANA Considerations:**
    *   Discussion arose regarding the blank Section 14 (IANA Considerations) in `core-06`.
    *   A proposal was made to claim a URI namespace for SATP (e.g., `satp://`) to facilitate the clear definition of structural concepts such as gateways and networks within the protocol.
*   **Hackathon Idea:**
    *   The idea of hosting a hackathon to "road test" the SATP protocol and gather implementation feedback was raised. The co-chair noted that this would likely require a sponsor and is an area where the Area Director (AD) would provide expertise.

## Decisions and Action Items

*   **Decision:** The authors of `draft-ietf-satp-core-06` and `draft-ietf-satp-use-cases` intend to request Working Group Last Call (WGLC) for both drafts at IETF 121 in Dublin.
*   **Action Item:** Claire (Co-chair) to liaise with AD Wes regarding the process for initiating Working Group Last Call (WGLC) for `draft-ietf-satp-core-06` and `draft-ietf-satp-use-cases`.
*   **Action Item:** Dennis to initiate a discussion on the SATP mailing list concerning IANA considerations for Section 14, specifically exploring the proposal for a dedicated SATP URI namespace (`satp://`).
*   **Action Item:** Rama (author of `use-cases`) to prepare an updated version of `draft-ietf-satp-use-cases` for submission by the October 18th IETF 121 deadline, incorporating any feedback received and adding pending links.
*   **Action Item:** Anthony to provide feedback on `draft-ietf-satp-use-cases` to Rama as soon as possible, ideally before the IETF 121 submission deadline.
*   **Action Item:** Claire (Co-chair) to consult with AD Wes regarding the feasibility and process for organizing a hackathon for SATP.

## Next Steps

*   The co-chairs will prepare the agenda for the SATP WG session at IETF 121 in November.
*   At IETF 121, the WG plans to hold a preliminary discussion to formulate a "wish list" and scope for a potential future SATP Working Group charter, considering items currently designated as future scope.