HI Andrew, On Sat, Feb 3, 2024 at 2:54 AM Andrew Campling <[email protected]> wrote: > I hadn't seen any discussion on the Opsec list about potential agenda items > before this notification came out. If the issue is lack of bandwidth, I plan > to be in Brisbane and will be happy to help with any administrative tasks on > site. I'm sure that others will be happy to assist too.
Thank you for offering that. The main reason we didn't schedule the opsec session this time is lack of activity on the list. If there are drafts being actively discussed on the list, we are happy to have them on the agenda. > With that in mind, is it possible to tentatively request an hour agenda slot > before the cut-off later today to give time to poll the mailing list for > interest? The slot was carried over from 118 (see > https://mailarchive.ietf.org/arch/msg/opsec/7kZ7NHJxhJ1hPfMh4kcufh_Fxe4/) so > it would be good to reconvene this time if possible. Sorry, I was OOO and just read your email. I'm afraid now it's a bit late to ask for a slot. If you have any documents which might be of interest for the working group, please send them to the list! > -----Original Message----- > From: OPSEC <[email protected]> On Behalf Of IETF Meeting Session > Request Tool > Sent: Wednesday, January 31, 2024 10:17 PM > To: [email protected] > Cc: [email protected]; [email protected]; [email protected] > Subject: [OPSEC] opsec - Not having a session at IETF 119 > > > > Jen Linkova, a chair of the opsec working group, indicated that the opsec > working group does not plan to hold a session at IETF 119. > > This message was generated and sent by the IETF Meeting Session Request Tool. > > > > _______________________________________________ > OPSEC mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsec -- Cheers, Jen Linkova _______________________________________________ OPSEC mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsec
