Received: by mx.ietf.org (Postfix) id 2CD7F30;
	Fri, 25 Sep 2026 16:47:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail;
	t=1790354828;
	h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date:
	 message-id:message-id:to:to:cc:cc:  mime-version:mime-version:mime-version:
	 content-type:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:content-transfer-encoding;
	bh=Cc57axmpWOleb2xMi1Ucs/zLIZOvna/qkganJ7lY1KI=;
	b=iiz5ZKYAVGDlmoAgBpyT7p/N4E/qQ3hUNM5QpPvRDzr2cJmiKsDc/Y3VGUVU5a0pmNApIK
	GV1icMv4yP+srsAoWJncTOkibCCZDYgdKa28hUZXHmyTRympVbT+mNL+yzhK0zolO6CNGE
	51V3W0Ae4MRy+XjfX9+5xC8vtW0q1Rg=
Authentication-Results: ORIGINATING;
	auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=iesg-secretary@ietf.org
Received: from [10.244.9.165] (gaia.k8s.ietf.org [4.156.85.76])
	by mail2.ietf.org (Postfix) with ESMTP id EB97F139CE73D;
	Fri, 25 Sep 2026 09:47:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-satp-core-17.txt> (Secure Asset Transfer
 Protocol (SATP) Core) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 12.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: 
 <179035482786.90165.1063892020240576287@dt-datatracker-57df95fc99-fzjcz>
Date: Fri, 25 Sep 2026 09:47:07 -0700
Message-ID-Hash: 4SJ7OPQBMOVGSSJ4XTV2N5YHIYXNFHLQ
X-Message-ID-Hash: 4SJ7OPQBMOVGSSJ4XTV2N5YHIYXNFHLQ
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop;
 banned-address; header-match-ietf-announce.ietf.org-0; emergency;
 member-moderation; nonmember-moderation; administrivia; implicit-dest;
 max-recipients; max-size; news-moderation; no-subject; digests;
 suspicious-header
CC: draft-ietf-satp-core@ietf.org, liuchunchi@huawei.com, sat@ietf.org,
 satp-chairs@ietf.org
X-Mailman-Version: 3.3.10
Reply-To: last-call@ietf.org, sat@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ietf-announce/-KHFZ6Ltex6Dvp4eYZGscVCdXn4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>


The IESG has received a request from the Secure Asset Transfer Protocol WG
(satp) to consider the following document:
  'Secure Asset Transfer Protocol (SATP) Core'
  <draft-ietf-satp-core-17.txt> as Proposed Standard

The IESG plans to make a decision on this document in the coming weeks, and
solicits last-call comments. Please send substantive comments to the
last-call@ietf.org mailing list, with sat@ietf.org copied, no later than
2026-10-09.  Please retain the beginning of the Subject line to facilitate
automated sorting.

Abstract

   This memo describes the Secure Asset Transfer Protocol (SATP) for
   digital assets.  SATP is a protocol operating between two gateways
   that conducts the transfer of a digital asset from one gateway to
   another, each representing their corresponding digital asset
   networks.  The protocol establishes a secure channel between the
   endpoints and implements a 2-phase commit (2PC) to ensure the
   properties of transfer atomicity, consistency, isolation and
   durability.



The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-satp-core/


No IPR declarations have been submitted directly on this I-D.





