IETF Logo Mail Archive

[km-fs-pcs] CURRENT BOF Agenda (assuming it is approved)

Russ Housley <housley@vigilsec.com> Tue, 02 June 2026 19:50 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: km-fs-pcs@mail2.ietf.org
Delivered-To: km-fs-pcs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8697AF98D6E2 for <km-fs-pcs@mail2.ietf.org>; Tue, 2 Jun 2026 12:50:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780429841; bh=YHFDYlcZ231oE5yxhfYRlbJzSk8tjm3XF/et4E0Yrjg=; h=From:Subject:Date:References:To:In-Reply-To; b=Rn3JqGW+XgIzevZlabuNhrgvVeMqJA4Z0+bTaKLdPdvoL0t40Zw74KlD/LAiSdSee 385LOsRFlHyIc4Rnv0P4uZECjAcyXkM09gLWkYrwUvcGFe0s4c49C04jU/SeXK9rsT TZ0YjO5Z0VpGGCRgf9YrnTiU+uR5jsGtFsDI2RIc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
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 0-enJDcefNym for <km-fs-pcs@mail2.ietf.org>; Tue, 2 Jun 2026 12:50:41 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 63331F98C0F9 for <km-fs-pcs@ietf.org>; Tue, 2 Jun 2026 12:45:51 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 454EC1A084E for <km-fs-pcs@ietf.org>; Tue, 2 Jun 2026 15:45:51 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 330291A18BB for <km-fs-pcs@ietf.org>; Tue, 2 Jun 2026 15:45:51 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Date: Tue, 02 Jun 2026 15:45:40 -0400
References: <FF0C4275-FF7B-4D21-98F4-1D4C1B9A2F91@vigilsec.com>
To: km-fs-pcs@ietf.org
In-Reply-To: <FF0C4275-FF7B-4D21-98F4-1D4C1B9A2F91@vigilsec.com>
Message-Id: <65E1255D-DC8B-48ED-9BE3-2A840C731184@vigilsec.com>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:content-transfer-encoding:mime-version:subject:date:references:to:in-reply-to:message-id; s=pair-202402141609; bh=01f8N8Y9vmzJziHRhXv0Rjr+m22L/zGCu8bZG6l1FHs=; b=mqaLc6I/K/7r1dQxBrDXYIC/tJOkeEkZGtQ0YDlq5QMiYa3TYoSU0Im3mAWlVUgLxybdLCQL0IsQTQFbE1YGWWKYxgjUhynC7MQyr3otfBml2SOm/M5QkS+cuT24KTVNVM6aN6i6944JjTp8P+sxKZZK71EVS0nZkTEbdIuvDTcqtbelZMIBaSf8QnhbmQ32Ib9i8C/5B/ivEZYEluIWDMwX0qIeDPctpnyBU9IOOtwbvPYYbFaCpUFqgNdKYa23/HbCL+odPcjRbvXoiXBT1T7uYda+e5jY94gAsLhKmmO8sjXe5IhhmgPpbUoOix0KevyjJ7bNM0Oo3kI/1LPGTw==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: STAZVTGQ236JE7GP3VGIFYRPA6A6XOZF
X-Message-ID-Hash: STAZVTGQ236JE7GP3VGIFYRPA6A6XOZF
X-MailFrom: housley@vigilsec.com
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [km-fs-pcs] CURRENT BOF Agenda (assuming it is approved)
List-Id: Key management that provides forward security and post compromise security <km-fs-pcs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/km-fs-pcs/eHDY9VkpSjfrRe14CXo5rRupkfA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/km-fs-pcs>
List-Help: <mailto:km-fs-pcs-request@ietf.org?subject=help>
List-Owner: <mailto:km-fs-pcs-owner@ietf.org>
List-Post: <mailto:km-fs-pcs@ietf.org>
List-Subscribe: <mailto:km-fs-pcs-join@ietf.org>
List-Unsubscribe: <mailto:km-fs-pcs-leave@ietf.org>

Here is the proposed agenda for the requested CURRENT BOF:

  1. What has happened since the SECDISPATCH presentation at IETF 125.
  2. Use Cases
  3. Draft charter

The requested BOF slot is one hour.

I have put together a few slides that will catch up anyone that did not attend the SECDISPATCH session at IETF 125 and covers what happens afterwards.  I am please to present them.

We need volunteers for presentation about use cases.  I think that the presentations by Konrad and Ben could be customized for this part.  Are there others?

The draft charter text is short and sweet.  I think we can ask the BOD Chair to present that.  The AD will usually ask the questions at the end to determine if there is sufficient interest to move forward.

Russ

v2.46.0 | Report a Bug | By Email | System Status