**Session Date/Time:** 19 Mar 2025 06:00

# satp

## Summary
The SATP working group meeting covered progress on existing drafts, feedback from the chair's review, re-chartering goals, a stage zero discussion led by Thomas, a SAPP implementation guide proposal from Hau Housin Song, and potential next steps. The main topics included encoding formats, acceptable values, asset ID, network requirements, gateway requirements, metadata sharing, data sharing, rechartering goals, and implementation guides.

## Key Discussion Points

*   **Document Readiness:** The core documents have improved significantly, but issues remain regarding encoding formats and lists of acceptable values.
*   **Encoding Formats:** There needs to be explicit definition of encoding for all fields, especially regarding public keys (e.g., base64, hex, DER encoded certificate).
*   **Acceptable Values:** Agreement is needed on acceptable values for fields with limited options (e.g., network lock type). Options include listing values in the document, referencing external lists (RFCs), or creating an IANA registry table.
*   **IANA Registry Table:** Should be used if multiple standards or documents might need to add entries to a list of values.
*   **Re-chartering Goals:** Brainstorming session to identify topics for the re-charter, including stage zero negotiation, bill of lading support, bidirectional transfers, data sharing, metadata attachment, asset ID definition, and network identification.
*   **AD Considerations:** The AD emphasized the need for multiple independent implementations and interoperability when selecting re-charter items. Focus should be on scenarios requiring interoperability, not internal descriptions within a single software boundary.
*   **Asset ID:** A discussion on what an asset ID is, especially if it's a tokenized asset and if it has its own unique ID.  Need for defining what an asset ID looks like and where it comes from. Also a discussion about standardizing the structure of SIDID.
*   **Network Identification:**  The need for an encoded way for code to process it outside the network
*   **Implementation Guide:** A proposal for an implementation guide was presented. This would contain guidelines and best practices for implementing the SATP protocol.
*   **Gateway vs Network Requirements:** Discussed whether minimum requirements should be placed on the network or the gateway.

## Decisions and Action Items

*   **Authors:** Address encoding format issues and list of acceptable values issues in the core document, taking into account the feedback from the chair's review.
*   **Chairs:** Post the brainstormed list of re-chartering items to the mailing list for further discussion and prioritization.
*   **Authors:** Provide sentence descriptions for each re-chartering item.
*   **Chairs and Authors:** Discuss whether an interim meeting should be scheduled before the meeting in Madrid.
*   **Chairs:** Talk and sort of divvy up the shepherd work between Peter and Howshen.
*   **Clara and Wes:** Figure out what to do with the list of 14 items to potentially consider.

## Next Steps

*   The chair will bring the list of proposed re-chartering items to the mailing list for further discussion and prioritization.
*   Authors should work on resolving the issues raised during the chair review for the existing drafts.
*   Authors should provide sentence descriptions for each re-chartering item on the list.
*   The SAPP implementation guide proposal will be considered as a potential focus area.