IETF Logo Mail Archive

Re: [OPSEC] opsec - Not having a session at IETF 119

Jen Linkova <furry13@gmail.com> Mon, 19 February 2024 04:29 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687E8C14F5EF; Sun, 18 Feb 2024 20:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=gmail.com
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 hadegnmueWqB; Sun, 18 Feb 2024 20:29:17 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 91A95C14F5F7; Sun, 18 Feb 2024 20:29:17 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2d22b8801b9so22712801fa.0; Sun, 18 Feb 2024 20:29:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708316956; x=1708921756; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=HMSusSJQhLCo6UdyFxB7wOcbQ1EkQY5YeSkkTqLsLUU=; b=SV+3Tspr+CkaX2S5li9X5JaShOd0cv2Dfai3L87zj1+DeZ0v/208+pz4ld+p95kS3v ujF3n378Xsy4CzE3BelxXVrFaJERs8tggLHyzUoMR/zZSg13Gbnmm4TjpaV9FyDEoorf OVNY+oWiN0U8Sm0BpyvQuBe5sfpNMMfhv1wVVD7TDBvr2Yx1Tjn2F4TkStj4fR38SEJV x84p/OzGjRC20BjKS3QLECiNdFVMkeVtIVG3euMGr8DaHoeP15YOfmri4orBz8Eiv3uc P2lhfj0tDZZCULLRLbDmisZ5mJIQ4xyMTEcC9MBVNJPAHb89X5hDJR/LcZqCEI7+Ukus 5LCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708316956; x=1708921756; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HMSusSJQhLCo6UdyFxB7wOcbQ1EkQY5YeSkkTqLsLUU=; b=sE20wQylLPOJNn4bsrs63Ig01X0oJyotkyouHuN2PEoG13w4z2OTiq7SJGbxiL703h RmJ2XZtz64qLv+3AoCS5FOxXPRRjJ5yWuCD2c/ypAgp/YCZwNgzv+76M+vu5oN1MSM2z 0wIFSBzK01pOSMVRVJPgpZcGo+UkAyGnQmOdLRx8ZDHBH/YoVCpyZW7EJa7dfZtb9EB/ 3YJRZj+MR/65ywupJ28KhkCssGhb7sG9CI+pTceitP1BHXLdygUbO1DcXO18CgGKGQjL 6ES/WZHQbkHIRRw24TnvGZ9mYC4unVAuMe08KmthB5GJMC4o/P+qm+dT71HhLPcVWKsx W+sw==
X-Forwarded-Encrypted: i=1; AJvYcCWiwm9Jo447pEOzQuxfnYsGlX0kVRhM/oR7mvE1fg8e2+vepmdD4+2bG3uMMyT4omztsHmIvzmv3cqpMN1TAA==
X-Gm-Message-State: AOJu0YxwHWBYDw+P3Ic4GlN/QsRAK8AclQayl6qmG4mpW33+3EUtPknJ cVRWp6sOVSgw44PE1ca1BS45Oy/uhWEmWIzKhk4N11TRmArsRUDquWCC93EUjr2B3pm0x1clYK6 /YY+uhhc+qTedeyRNIAnEG2+zmWS+FtKS
X-Google-Smtp-Source: AGHT+IH4AhNtXkLC6Tr2W9Qq0Zj/jk5I7A0eCTVqT/jtQm9Q32hcY3Ds8AyTE2HB7RzUzWjE7WcLNpP+gXWbB40n9Bs=
X-Received: by 2002:a2e:9790:0:b0:2d2:3db6:b168 with SMTP id y16-20020a2e9790000000b002d23db6b168mr357491lji.14.1708316955370; Sun, 18 Feb 2024 20:29:15 -0800 (PST)
MIME-Version: 1.0
References: <170673944562.42975.2108315044273027859@ietfa.amsl.com> <CWXP265MB5153BA61F96CE8A759DC649BC2422@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
In-Reply-To: <CWXP265MB5153BA61F96CE8A759DC649BC2422@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
From: Jen Linkova <furry13@gmail.com>
Date: Mon, 19 Feb 2024 15:29:13 +1100
Message-ID: <CAFU7BAQYyY6_Z4FfrtVKuYCYCO7a_HefaTa31UyuhC857qTkhg@mail.gmail.com>
To: Andrew Campling <andrew.campling@419.consulting>
Cc: "opsec-chairs@ietf.org" <opsec-chairs@ietf.org>, "warren@kumari.net" <warren@kumari.net>, "opsec@ietf.org" <opsec@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/75xr2-vzxhQfq_v9FS1me2xf4hI>
Subject: Re: [OPSEC] opsec - Not having a session at IETF 119
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Feb 2024 04:29:21 -0000

HI Andrew,

On Sat, Feb 3, 2024 at 2:54 AM Andrew Campling
<andrew.campling@419.consulting> 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 <opsec-bounces@ietf.org> On Behalf Of IETF Meeting Session Request Tool
> Sent: Wednesday, January 31, 2024 10:17 PM
> To: session-request@ietf.org
> Cc: warren@kumari.net; opsec-chairs@ietf.org; opsec@ietf.org
> 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
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec



-- 
Cheers, Jen Linkova

v2.23.0 | Report a Bug | By Email