[Sat] next steps for draft-ietf-satp-architecture

Wes Hardaker <wjhns1@hardakers.net> Fri, 19 April 2024 18:26 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: sat@ietfa.amsl.com
Delivered-To: sat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D651C1D61FA for <sat@ietfa.amsl.com>; Fri, 19 Apr 2024 11:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzvCkbxz_-Qg for <sat@ietfa.amsl.com>; Fri, 19 Apr 2024 11:26:49 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AB14C14F6A6 for <sat@ietf.org>; Fri, 19 Apr 2024 11:26:49 -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 BA9BC201EA for <sat@ietf.org>; Fri, 19 Apr 2024 11:26:48 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net BA9BC201EA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1713551208; bh=E1nx88C/+Bs77EPk8YbcACzmdOmAAlZYocD70ixO1Rw=; h=From:To:Subject:Date:From; b=q8DmiSoVxtQNTAECCMadHBXnehxgxii8gLTjZtvSgvm7jHNqQXYtQOLC9Qge6GPOH esj7zJ7KEocZKQ2D9clBLAZ5fxfiI4ArHJMT/0XtGst9ynBI//bNWdFiv5cfMS/qp9 dwQJ/uNOXeYJdsNNDBy2Q8XzzmBnO3skDubnnqK8=
From: Wes Hardaker <wjhns1@hardakers.net>
To: sat@ietf.org
User-Agent: Gnus/5.13 (Gnus v5.13)
Date: Fri, 19 Apr 2024 11:26:48 -0700
Message-ID: <yblcyqltdhz.fsf@wd.hardakers.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/aLss_-RAMlt-y61scLEEEqiQYAI>
Subject: [Sat] next steps for draft-ietf-satp-architecture
X-BeenThere: sat@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "The purpose of this mailing-list is to discuss the secure asset transfer \(SAT\) protocol and related aspects." <sat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sat>, <mailto:sat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sat/>
List-Post: <mailto:sat@ietf.org>
List-Help: <mailto:sat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sat>, <mailto:sat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2024 18:26:53 -0000

The consensus reached during the WG last call for the architecture
document is that there is additional information needed around the
security model of the architecture, etc.  As such, I've put the document
back into a "WG document" state with an "update needed" tag.  When the
document authors believe that the text has been revised accordingly,
we'll do another short 2 week last call again after which we'll likely
push it toward publication (assuming positive LC conclusions of course).

Cheers,
-- 
Wes Hardaker
USC/ISI