| Internet-Draft | SATP Implementation Guide | March 2025 |
| Song, et al. | Expires 4 September 2025 | [Page] |
This memo provides guidelines to developers of gateway systems, digital asset networks and client applications for the Secure Asset Transfer Protocol (SATP). Multiple gateways can represent the same digital asset network following the SATP standards, which necessitate basic implementation guidelines as outlined in this document. It also serves as an introduction to the SATP processing workflow for those new to the SATP standards.¶
(Note. the initial draft (00) is submitted for a brief review regarding the document's direction by SATP WG members during IETF 12 in Bangkok, Mar 2025)¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://anawhj.github.io/draft-song-satp-implementation-guide/draft-song-satp-implementation-guide.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-song-satp-implementation-guide/.¶
Discussion of this document takes place on the Secure Asset Transfer Protocol mailing list (mailto:sat@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/sat/. Subscribe at https://www.ietf.org/mailman/listinfo/sat/.¶
Source for this draft and an issue tracker can be found at https://github.com/anawhj/draft-song-satp-implementation-guide.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 2 September 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document proposes implementation guidance from the perspective of developers of peer gateways and digital asset networks.¶
The Secure Asset Transfer Protocol (SATP) facilitates communication between peer gateways and other entities such as digital asset networks and client applications. A digital asset network can be connected to multiple peer gateways to enable asset transfers while ensuring interoperability. To ensure consistency across multiple peer gateways, appropriate guidelines are necessary.¶
Peer gateways must implement a secure asset transfer mechanism that meets essential requirements related to atomicity, consistency, isolation, and durability (ACID). Security and privacy are also critical requirements. Therefore, this document involves several considerations beyond the SATP interface.¶
The existing SATP core documents ([SATcore], [SATarch]) provides most of the key implementation guidelines, but this document offers a more elaborated description of each phase within peer gateways and digital asset networks.¶
Originator Beneficiary
(Origin network) (Destination network)
| |
+------------------------+ +------------------------+
| Client | | Client |
| Application | | Application |
| (App1) | | (App2) |
+------------------------+ +------------------------+
| | | |
V V V V
+---------+ +---------+ +---------+ +---------+
| | | | | | | |
| | | | | | | |
| Digital | | | | | | Digital |
| Asset | | Gateway | | Gateway | | Asset |
| Network |<-->| GW1 | <------> | GW2 | | Network |
| NW1 | | | | | | NW2 |
| | | | | | | |
| | | | | | | |
+---------+ +---------+ +---------+ +---------+
Figure 1. Scope of the SATP implementation
¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
There are no IANA considerations related to this document.¶
TBA¶