[Sat] Re: Updated SATP Core draft uploaded --- Re: I-D Action: draft-ietf-satp-core-11.txt

Wes Hardaker <wjhns1@hardakers.net> Tue, 19 August 2025 20:45 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: sat@mail2.ietf.org
Delivered-To: sat@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 289BD562CA0A for <sat@mail2.ietf.org>; Tue, 19 Aug 2025 13:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nBVZud4Tqci for <sat@mail2.ietf.org>; Tue, 19 Aug 2025 13:45:47 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id F3201562CA05 for <sat@ietf.org>; Tue, 19 Aug 2025 13:45:46 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 3EA28206AF; Tue, 19 Aug 2025 13:45:46 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 3EA28206AF
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1755636346; bh=I9MPE+tX8qtrPNzkOFwWdwwalgSBv01nDFrV1Z3Itdw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hHwFcY4WkCgAy6Odz9H6PH9qd0wGAJ5kGmu9BMDbxGKW4ayv42zIw6w0yLvrO1kMk 9x1mxcFMGOi2B8BIFurytYqOg2KvofulC7XNowShitRZzmVGS/36MOOgbRct5DMCGy a4JaYeUtwjIO9lO/0RDtEWiv0LkxYsw0Fx4+LcdQ=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Thomas Hardjono <hardjono@mit.edu>
In-Reply-To: <DM6PR01MB43959A853D20AC3174DF5912CB2AA@DM6PR01MB4395.prod.exchangelabs.com> (Thomas Hardjono's message of "Wed, 13 Aug 2025 13:45:49 +0000")
References: <175458743010.1520462.3449240072240275889@dt-datatracker-5bd446d5fd-c47nq> <DM6PR01MB43959A853D20AC3174DF5912CB2AA@DM6PR01MB4395.prod.exchangelabs.com>
Date: Tue, 19 Aug 2025 13:45:46 -0700
Message-ID: <ybly0rff3b9.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: Y4D2Z3TQDJQI55GL6HLQYGQJBMHVPOHU
X-Message-ID-Hash: Y4D2Z3TQDJQI55GL6HLQYGQJBMHVPOHU
X-MailFrom: wjhns1@hardakers.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "sat@ietf.org" <sat@ietf.org>, Claire Facer <claire.facer@quant.network>, Wes Hardaker <wjhns1@hardakers.net>, "orie@or13.io" <orie@or13.io>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sat] Re: Updated SATP Core draft uploaded --- Re: I-D Action: draft-ietf-satp-core-11.txt
List-Id: "The purpose of this mailing-list is to discuss the secure asset transfer (SAT) protocol and related aspects." <sat.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/EiIOSkOLPhAtAzbaYN3ye5DrmxE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sat>
List-Help: <mailto:sat-request@ietf.org?subject=help>
List-Owner: <mailto:sat-owner@ietf.org>
List-Post: <mailto:sat@ietf.org>
List-Subscribe: <mailto:sat-join@ietf.org>
List-Unsubscribe: <mailto:sat-leave@ietf.org>

Thomas Hardjono <hardjono@mit.edu> writes:

> The revised core draft (now draft-11) has a new IANA Considerations section (Section 14).
> 
> This includes action for IANA  (i.e., the request to IANA for a URN/namespace and registry for
> SATP)
> 
> (Please let us know if the wording of the IANA Considerations section
> needs to be corrected).

Thanks Thomas.

Sorry for the delay...  The good news is that I'm two weeks away from
having a lot more time!

Anyway, I'll check it over and get back to you shortly.
-- 
Wes Hardaker
USC/ISI