Secure Asset Transfer Protocol
draft-hargreaves-sat-core-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Hargreaves , Thomas Hardjono , Rafael Belchior | ||
| Last updated | 2022-11-07 (Latest revision 2022-05-02) | ||
| Replaced by | draft-ietf-satp-core, draft-ietf-satp-core | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo This memo describes the Secure Asset Transfer (SAT) Protocol for digital assets. SAT is a protocol operating between two gateways that conducts the transfer of a digital asset from one gateway to another. The protocol establishes a secure channel between the endpoints and implements a 2-phase commit to ensure the properties of transfer atomicity, consistency, isolation and durability.
Authors
Martin Hargreaves
Thomas Hardjono
Rafael Belchior
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)