IETF Logo Mail Archive

Re: [Sat] agenda for Tuesday's SATP meeting

Wes Hardaker <wjhns1@hardakers.net> Fri, 05 April 2024 15:02 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 60577C15106A for <sat@ietfa.amsl.com>; Fri, 5 Apr 2024 08:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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 1HNfn3nkoOjn for <sat@ietfa.amsl.com>; Fri, 5 Apr 2024 08:02:36 -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 66EF6C14F726 for <sat@ietf.org>; Fri, 5 Apr 2024 08:02:36 -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 EF9B420C79; Fri, 5 Apr 2024 08:02:35 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net EF9B420C79
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1712329356; bh=PhakK3LFDPetFAv5MsNqIoPZSo7Uu7SCGUxvySfWcYY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pinnsNu4vx4rKnuZFpHZ8sXHTdQhqy/FrXCHeHeOs2so7ckSbl6qoturwzJCTYcsV kmyLeITpKh4UupTne8PhIa7C3nfiAUu+cuipAepFh2H5H58jp1OH4f3hMDjDopR2FZ NHyg/33BhXyctOcK9hMuR7Ect6WEGlimVNN1nEds=
From: Wes Hardaker <wjhns1@hardakers.net>
To: VENKATRAMAN RAMAKRISHNA <vramakr2@in.ibm.com>
Cc: Wes Hardaker <wjhns1@hardakers.net>, "sat@ietf.org" <sat@ietf.org>
In-Reply-To: <SJ0PR15MB51321BFFCE9F469A9BDC506FB8032@SJ0PR15MB5132.namprd15.prod.outlook.com> (VENKATRAMAN RAMAKRISHNA's message of "Fri, 5 Apr 2024 14:54:31 +0000")
References: <yblv84v7uli.fsf@wd.hardakers.net> <SJ0PR15MB51321BFFCE9F469A9BDC506FB8032@SJ0PR15MB5132.namprd15.prod.outlook.com>
Date: Fri, 05 Apr 2024 08:02:35 -0700
Message-ID: <yblh6gf7sz8.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/sat/p2IXJQSDRyseYLIONFDmqdFnFqU>
Subject: Re: [Sat] agenda for Tuesday's SATP meeting
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, 05 Apr 2024 15:02:40 -0000

VENKATRAMAN RAMAKRISHNA <vramakr2@in.ibm.com> writes:

> I'd assumed that agenda items from the previous (cancelled) interim
> meeting would be added to this meeting's agenda, so I did not
> explicitly ask for a slot to give an update on the use cases document.

Sorry about that; can you give the topics you want to cover and rough
times?  Certainly the usage document should take precedence as it's on
the active deliverables for the working group.
-- 
Wes Hardaker
USC/ISI

v2.23.0 | Report a Bug | By Email