Last Call: <draft-ietf-satp-usecases-10.txt> (Secure Asset Transfer (SAT) Use Cases) to Informational RFC
The IESG <iesg-secretary@ietf.org> Wed, 23 September 2026 20:01 UTC
Received: by mx.ietf.org (Postfix) id 1438F31; Wed, 23 Sep 2026 20:01:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1790193669; 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=Uj10+ruawSKcDcravGhY3risqhMmlIMdVIejsC4FXq8=; b=WI1/1s/II2l49mFKy3TkYWGaUwA0sBoWhehnoM39l5SJN2k709FG8CptZz76m5RRAzJ5Gz EyyEr9OfzSmQSVUUaFWUTecKizO5MYXNBg+9mVXNxZyyw44ihCKrKYOmuha84+xvHb6UFf Eh7Smz1NF5DgKMx0xmJgpzGoit+F7KY=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=iesg-secretary@ietf.org
Received: from [10.244.9.157] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id BE83A139BA7A1; Wed, 23 Sep 2026 13:01:08 -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-usecases-10.txt> (Secure Asset Transfer (SAT) Use Cases) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 12.77.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: <179019366848.205245.7094244379115008527@dt-datatracker-69f6c78549-jvtvd>
Date: Wed, 23 Sep 2026 13:01:08 -0700
Message-ID-Hash: OQQQKXRIHY3E7BW4C55SH3QM2ZZZPXDY
X-Message-ID-Hash: OQQQKXRIHY3E7BW4C55SH3QM2ZZZPXDY
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: claire.facer@quant.network, draft-ietf-satp-usecases@ietf.org, fun@snu.ac.kr, 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/Q6fHTlec8_iHo4WzZaeRTjNGNs4>
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 (SAT) Use Cases' <draft-ietf-satp-usecases-10.txt> as Informational RFC 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-07. Please retain the beginning of the Subject line to facilitate automated sorting. Abstract This document describes prominent scenarios where enterprise systems and networks maintaining digital assets require the ability to securely transfer assets or data to each other. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-satp-usecases/ No IPR declarations have been submitted directly on this I-D.