[irtf-discuss] Reviewing conflicts from IETF 115 in session request tool

Liz Flynn <lflynn@amsl.com> Fri, 06 January 2023 20:36 UTC

Return-Path: <lflynn@amsl.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70821C14CE3F for <irtf-discuss@ietfa.amsl.com>; Fri, 6 Jan 2023 12:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 0a8B_1QAVDzI for <irtf-discuss@ietfa.amsl.com>; Fri, 6 Jan 2023 12:36:51 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 980E2C1524C3 for <irtf-discuss@irtf.org>; Fri, 6 Jan 2023 12:35:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4872A4243E46; Fri, 6 Jan 2023 12:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fzjz8FN6LqMn; Fri, 6 Jan 2023 12:35:45 -0800 (PST)
Received: from smtpclient.apple (23-93-200-249.fiber.dynamic.sonic.net [23.93.200.249]) by c8a.amsl.com (Postfix) with ESMTPSA id 3342B424FFE9; Fri, 6 Jan 2023 12:35:45 -0800 (PST)
From: Liz Flynn <lflynn@amsl.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Message-Id: <32DEA208-69DD-4898-B612-687E5B5F1F13@amsl.com>
Date: Fri, 06 Jan 2023 12:35:45 -0800
Cc: irtf-discuss@irtf.org, mimi@ietf.org
To: irtfopen-chairs@ietf.org, mimi-chairs@ietf.org
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/NQT8n9mnYPu7q48rcZPW6OePkqI>
Subject: [irtf-discuss] Reviewing conflicts from IETF 115 in session request tool
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2023 20:36:51 -0000

Hi IRTFOPEN and MIMI chairs and participants,

In the IETF 115 meeting survey seven respondents called out IRTFOPEN and MIMI when answering Q19, “How many times did you have a conflict between two sessions that were scheduled in the same time slot?" However, to date, these groups have not listed each other as Conflicts to Avoid in the Session Request tool. (Not a surprise, since one is a BOF!)

As we start to plan for IETF 116, we are asking you to consider this feedback and update your Conflicts to Avoid as appropriate. If you need assistance, the Secretariat is happy to make updates in the Datatracker on your behalf, but we do need clear guidance on what changes to make, and how to record any new conflicts (i.e. chair conflict, technology overlap or key participant conflict). 

Finally, we’d like to remind everyone that the wg mailing list receives a copy of each session request, and we encourage you to review the noted Conflicts to Avoid at the time of request, so that you can reach out to the working group chairs if you feel something is missing or incorrect.


Thank you,

Liz
IETF Secretariat