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, 2 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>
Message-ID-Hash: STAZVTGQ236JE7GP3VGIFYRPA6A6XOZF
Precedence: list
Subject: =?utf-8?q?=5Bkm-fs-pcs=5D_CURRENT_BOF_Agenda_=28assuming_it_is_approved=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/km-fs-pcs/eHDY9VkpSjfrRe14CXo5rRupkfA>

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