IETF Secure Asset Transfer Protocol (satp) WG
Date: Tuesday 2024-04-09 14:00 UTC
Room:
https://meetings.conf.meetecho.com/interim/?group=a2aa0d2f-a9f1-4c2b-9e6e-72bf96e595d5

Chair Introduction (Wes Hardaker and Claire Facer)

• Note takers needed
• IETF process reminders

Last Call responses to architecture document - Chairs

• will extend for another 2 weeks
• David Millman and Thomas: architecture document needs more
  information with respect to the security considerations.

SATP Core - Thomas Hardjono

• APIs are renamed
• moved discussion to appendix
• API1/3 will be future work, and out of scope now
• API2 will work without standardization of API1/3
• David: in the diagram isn't the client within the network?
  • Yes, there are two versions of this diagram
  • Denis: reusing network is a problem here. There are both an
    asset network and a network client and a network client might be
    outside the logical network where the asset network is actually
    run.
  • Rama: API3 is outside, but API1 is inside.
  • Wes: need to move this discussion to the list, but it's an
    important one.

Use Cases Draft Additions - Venkatraman Ramakrishna

• Multiple new use cases being added and will appear soon

Identifier Design Team Update - Thomas Hardjono

• Team is wrapping up but there is problems to be solved still
• Will be writing up results and sending to WG
• Extensible mechanism for defining any needed IDs
• Want to encode with CBOR at some point

Asset profiles - Denis Avrilioni

• draft-avrilionis-satp-asset-schema-architecture-03
• Future architecture for API3
• Figure 2 from document discusses flow needed for asset transfer
  within the asset network
• Gets asset into control of the gateway
• Defines how verification can be happen via a registry
• Registry will contain the artifacts necessary for SATP

Hyperledger Cacti open source implementation - Rafael Belchior

• Multiple implementations of SATP
• Typescript and Rust
• a little overlap between developers, but otherwise fairly separate
  implementations
• versioning was a problem to determine what versions of a protocol
  were being used -- ended up using the draft version numbers for now