From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: sat@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: Secure Asset Transfer Protocol (satp)
A new IETF WG has been proposed in the Applications and Real-Time Area. The
IESG has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send your
comments to the IESG mailing list (iesg@ietf.org) by 2023-01-30.
Secure Asset Transfer Protocol (satp)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
Wes Hardaker <ietf@hardakers.net>
Assigned Area Directors:
Paul Wouters <paul.wouters@aiven.io>
Murray Kucherawy <superuser@gmail.com>
Applications and Real-Time Area Directors:
Murray Kucherawy <superuser@gmail.com>
Francesca Palombini <francesca.palombini@ericsson.com>
Mailing list:
Address: sat@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/sat
Archive: https://mailarchive.ietf.org/arch/browse/sat/
Group page: https://datatracker.ietf.org/group/satp/
Charter: https://datatracker.ietf.org/doc/charter-ietf-satp/
OBJECTIVE
There is currently an interoperability problem in many digital asset
networks (frequently shortened to "network" below for simplicity), where
assets in one network cannot be moved easily to another network. The
problem is more acute in the case of private asset networks, where
external entities have no visibility into the state of an asset in the
private network. An example is regulated digital representations of
real-world private assets, such as property ownership certificates, and
regulated government-issued digital currencies.
The goal of the Secure Asset Transfer Protocol (SATP) working group will
be to develop a standard protocol which operates between two peer
gateways for the purpose of transferring digital assets between an
originator in the origin network to a beneficiary in destination
network. The resulting protocol that will be agnostic with respect to
the type of asset being transferred although.
PROBLEM SPACE AND ARCHITECTURE
To begin addressing these challenges, SATP will employ the gateway
paradigm as a means for digital assets to be moved from one network to
another through a standardized asset transfer protocol implemented
between peer gateways.
Each gateway represents one digital asset network, and SATP allows
gateways to perform a voluntary transfer of a digital asset from the
origin network to a destination network in such a way that evidence of
the transfer can be verified by a third-party audit in the case of
disputes. Both the origin and destination networks are assumed to share
a common understanding of the digital asset.
There might be several gateways representing the same digital asset
network. It is assumed that the same peer gateways representing the
networks are participating in the entire asset transfer sequence from
the beginning to the end.
A key requirement for transferring assets is ensuring that the digital
asset is valid in one network only at any given time. This means that
SATP must ensure that the properties of atomicity, consistency,
isolation, and durability (ACID) of the underlying networks are
satisfied in an asset transfer. Commitments and rollbacks must be
supported in the case of an asset mid-transfer failure.
DELIVERABLES
The deliverables of the SATP Working Group will be as follows:
SATP Architecture: The immediate scope of work for SATP will be a base
architecture that utilizes the gateway paradigm that ensures a common
semantic understanding to be shared among the modes of asset transfers,
data sharing and coordinated asset exchanges. The starting point for the
architecture document will be draft-hardjono-sat-architecture.
Secure Asset Transfer Protocol: Concurrent with the development of the
SATP architecture will be the Secure Asset Transfer Protocol that
implements the transfer of a digital asset from one gateway to another,
satisfying the ACID properties.
SATP Use-Cases: Various real-world use-cases will be collected and
described succinctly, with the goal of providing the background to the
SATP work.
SATP will define common identifiers, message flows and payloads for
transferring digital assets. A common terminology will be defined in the
architecture document.
SATP will reuse existing IETF standards for various aspects of the
protocol modes, including but not limited to secure channel
establishment (TLS), payload formats (e.g., JSON, CBOR, ProtoBuf, etc.),
digital signature and encryption (e.g., JOSE, COSE, etc.), digital
certificates and tokens (e.g., PKIX, JWT, etc.), and others. SATP may
also reuse existing standards from other organizations (e.g., W3C with
DIDs).
Note that for the protocol to work, agreements will likely be needed
between participating digital asset networks that intend to use SATP;
these legal or other frameworks are outside of the scope of the SATP.
This assumption is akin to how the BGP protocol is frequently run
between parties that have previously agreed to route IP packets.
Milestones:
Jan 2024 - SATP Use-Cases document
Jul 2024 - SATP Architecture document
Jul 2024 - ATP Asset Transfer Protocol document
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
sat@ietf.org,
satp-chairs@ietf.org
Subject: WG Action: Formed Secure Asset Transfer Protocol (satp)
A new IETF WG has been formed in the Applications and Real-Time Area. For
additional information, please contact the Area Directors or the WG Chairs.
Secure Asset Transfer Protocol (satp)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
Wes Hardaker <ietf@hardakers.net>
Claire <claire.facer@quant.network>
Assigned Area Directors:
Paul Wouters <paul.wouters@aiven.io>
Murray Kucherawy <superuser@gmail.com>
Applications and Real-Time Area Directors:
Murray Kucherawy <superuser@gmail.com>
Francesca Palombini <francesca.palombini@ericsson.com>
Mailing list:
Address: sat@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/sat
Archive: https://mailarchive.ietf.org/arch/browse/sat/
Group page: https://datatracker.ietf.org/group/satp/
Charter: https://datatracker.ietf.org/doc/charter-ietf-satp/
Objective
There is currently an interoperability problem in many digital asset
networks (frequently shortened to "network" below for simplicity),
where assets in one network cannot be moved easily to another
network. The problem is more acute in the case of private asset
networks, where external entities have no visibility into the state of
an asset in the private network. An example is regulated digital
representations of real-world private assets, such as property
ownership certificates, and regulated government-issued digital
currencies.
The goal of the Secure Asset Transfer Protocol (SATP) working group
will be to develop a standard protocol which operates between two peer
gateways for the purpose of transferring digital assets between an
originator in the origin network to a beneficiary in a destination
network. The resulting protocol shall be agnostic with respect to
the type of asset being transferred.
Problem space and architecture
To begin addressing these challenges, SATP will employ the gateway paradigm as
a means for digital assets to be moved from one network to another through a
standardized asset transfer protocol implemented between peer gateways.
Each gateway represents one digital asset network, and SATP allows
gateways to perform a voluntary transfer of a digital asset from the
origin network to a destination network in such a way that evidence of
the transfer can be verified by a third-party audit in the case of
disputes. Both the origin and destination networks are assumed to
share a common understanding of the digital asset.
There might be several gateways representing the same digital asset
network. It is assumed that the same peer gateways representing the
networks are participating in the entire asset transfer sequence from
the beginning to the end.
A key requirement for transferring assets is ensuring that the digital asset
is valid in one network only at any given time. This means that SATP must
ensure that the properties of atomicity, consistency, isolation, and
durability (ACID) of the underlying networks are satisfied in an asset
transfer. Commitments and rollbacks must be supported in the case of an asset
mid-transfer failure.
Relationship with other IETF Working Groups
The Transfer dIGital cREdentialS Securely (TIGRESS) working group is
focused on transferring digital credentials, which is akin to but not
equal to SATP's goals of transferring digital assets. An additional
difference is TIGRESS is a wallet-to-wallet transfer, while SATP's
proposed solution involves a gateway-to-gateway transfer. The SATP
working group will work with TIGRESS proponents to ensure reuse of
existing TIGRESS outputs are used within SATP to promote technology
reuse.
Deliverables
The deliverables of the SATP Working Group will be as follows:
SATP Architecture: The immediate scope of work for SATP will be a base
architecture that utilizes the gateway paradigm that ensures a common
semantic understanding to be shared among the modes of asset transfers,
data sharing and coordinated asset exchanges. The starting point for the
architecture document will be draft-hardjono-sat-architecture.
Secure Asset Transfer Protocol: Concurrent with the development of the
SATP architecture will be the Secure Asset Transfer Protocol that
implements the transfer of a digital asset from one gateway to another,
satisfying the ACID properties.
SATP Use-Cases: Various real-world use-cases will be collected and
described succinctly, with the goal of providing the background to the
SATP work.
SATP will define common identifiers, message flows and payloads for
transferring digital assets. A common terminology will be defined in
the architecture document.
SATP will reuse existing IETF standards for various aspects of the protocol
modes, including but not limited to secure channel establishment (TLS),
payload formats (e.g., JSON, CBOR, etc.), digital signature and encryption
(e.g., JOSE, COSE, etc.), digital certificates and tokens (e.g., PKIX, JWT,
etc.), and others. SATP may also reuse existing standards from other
organizations (e.g., W3C with DIDs).
Note that for the protocol to work, agreements will likely be needed
between participating digital asset networks that intend to use SATP;
these legal or other frameworks, along with proof of their proper
implementation, are outside of the scope of the SATP. This assumption
is akin to how the BGP protocol is frequently run between parties that
have previously agreed to route IP packets.
Milestones:
Jan 2024 - SATP Use-Cases document
Jul 2024 - SATP Architecture document
Jul 2024 - ATP Asset Transfer Protocol document