## IETF Secure Asset Transfer Protocol (satp) WG   {#ietf-secure-asset-transfer-protocol-satp-wg}

Date: Friday 31 March, 09:30 - 11:30 Local  
Room: G314-G315

## AGENDA:   {#agenda}

*   5m - Chair Introduction (Wes)
    *   note takers - Andy Newton
    *   IETF document process reminders
    *   plans for monthly interims

*   5m - SATP Scope (Claire)
    *   charter reminder
    *   (currently) out-of-scope assumptions

Claire presented path to adoption for documents to be used in the
working group

John Levine: does transfer mean move or copy?  
Claire: answered affirmatively

*   20m - Agreement on terminology
    *   starting a definition list - (TBD by chairs)

Wes presented list of terms.

There was conversation about the meaning of "legal" in the terms.  
Should be the owner authorized to move an asset around the network.

*   75m - Proposed WG documents
    *   30m - \[architecture\] - Thomas
    *   15m - \[use cases\] - Venkatraman
    *   30m - \[protocol\] - Thomas?

### architecture doc   {#architecture-doc}

Show of hands for adoption of architecture document: 12 hands in
meetecho poll.

### uses cases   {#uses-cases}

A question on ISO 20022 which is used by the financial community. Two
Swift  
experts were at the bof and noted that 20022 does not handle NFTs. SATP
also  
has atomic transfer properties not present in 20022. Chairs have
suggested  
a comparison between 20022 and SATP.

Show of hands for adoption: 8 hands in favor, 0 hands

### protocol   {#protocol}

Show of hands for adoption: 8 raised hands, 1 not raised. Chairs invited
questions   
for why some did not raise hands.

Questions about errors in the document. Authors stated that the document
will need  
that information added to the document during the working group process.
Chairs  
clarified document process.

*   5m - document(s) call for adoption

This was covered during doc discussion.

*   AOB - time remaining
    *   update on flow of transfer, transaction IDs and contextID,
        sessionID \[Denis\]
    *   ledger state views and addressing - Venkatraman

### ledger state views   {#ledger-state-views}

There are 2 I-Ds explaining. sat-data-sharing sat-views

### thomas   {#thomas}

No equivalent of AS number for SATP. Work on gateway ID.

## Related documents:   {#related-documents}

\[architecture\]:
https://datatracker.ietf.org/doc/draft-hardjono-sat-architecture  
\[protocol\]:
https://datatracker.ietf.org/doc/draft-hargreaves-sat-core/  
\[use cases\]:
https://datatracker.ietf.org/doc/draft-ramakrishna-sat-use-cases/