Update on venue assessment process
IETF Executive Director <exec-director@ietf.org> Tue, 11 June 2024 17:00 UTC
Return-Path: <jay@staff.ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E63C19ECBF for <ietf-announce@ietfa.amsl.com>; Tue, 11 Jun 2024 10:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=staff-ietf-org.20230601.gappssmtp.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 otDNd6YbLKuZ for <ietf-announce@ietfa.amsl.com>; Tue, 11 Jun 2024 10:00:05 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 0A0AFC1D5C7A for <ietf-announce@ietf.org>; Tue, 11 Jun 2024 10:00:04 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-52bc274f438so1902117e87.0 for <ietf-announce@ietf.org>; Tue, 11 Jun 2024 10:00:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1718125202; x=1718730002; darn=ietf.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=gzYr2mW0ztf71E4AjNf4Txcf563U/AMFW0JbMaOJRmw=; b=zJcAGN8zC4jppYsPGNSHH1+JmiGmsiwZOqiUkRwC+soe/mcFJRETzxJ3CmPeEMWeBB K3wVtEQgtRqgpoCIFrSPu0RYgEgzh1f1V0ca9Jjnayy7Jl8npNWbxYvfe0Jgw9YkXeCU QboXYWVYg4qEB/tZeunLmJWYeKaMkYT4xvjNNaOZfKZZgaLIBOKo67aviaorhIuHuXZ1 5hqElRFNePK5H2KM0aJkPJF0dXbtsEJ45YhRPM8M/rR9/dnjYWBHA85nfreeLz5XwQJr EC71JICJr7bZldtIxzIoDFTmiCLzAB3xx910zJJSTgaJ2ADbmvJULzYQmA0JyVgeW2r0 FkFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718125202; x=1718730002; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=gzYr2mW0ztf71E4AjNf4Txcf563U/AMFW0JbMaOJRmw=; b=VekZ8r8zijcPo3VShpjIZeIYGY6YFW1h/ALmiRwDLX2xsFY/x602ZNpObBKjSdqsOe roTBdzbbzfGkBfiNMYQS3ngVTOzVxp+E+U+3q82BfffGTV1WsSjip/Kf+aerGyM8FPTy tBlY++RIZp4TVOP4B/aD5ZrhqtGg8iojKhZe5ZrBlB0WlqwBjalUA2ZDgry5ANAYeigD ZOruabIhuc711M8Xq0c/230oyq0h0+TFZzOAcTvWFNlQ7hyziZ8UX16xZR/59v04Q897 rpZDmVQevRlV0XFUwBEBMa2aqV/FL1Mk/djtvuQdKgmgCm6jk76R637luA/rxl8WIHSj t9Tg==
X-Gm-Message-State: AOJu0YzET/cY7J0E0f5dN9ky72MY/Fpo4CWm1uiLM8/UV9yBgdNLNn9k 9zfioCxMsH+ePlyljY0du7GgOSncwPM8yNd/E5C+PwhxZBZjDp3kvFI1Ta3UXrPciS9PI40SM8w adSs=
X-Google-Smtp-Source: AGHT+IEkCCXoVr8aSigyh2hryl64lXD5ALD0XQRj+hgz3Y+22Ocnuw5xI7tL11bwKZYxIHcfTf7F+A==
X-Received: by 2002:a05:6512:451:b0:52c:859c:91dd with SMTP id 2adb3069b0e04-52c859c9257mr4420271e87.5.1718125201875; Tue, 11 Jun 2024 10:00:01 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-42212f0723dsm57202805e9.34.2024.06.11.10.00.01 for <ietf-announce@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jun 2024 10:00:01 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Update on venue assessment process
Message-Id: <02633008-500D-4AC7-81E4-7B46CAFDD594@ietf.org>
Date: Tue, 11 Jun 2024 17:59:51 +0100
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Message-ID-Hash: ECUSI5E44JL2RLA2WDYIYMNBTG7LYWLX
X-Message-ID-Hash: ECUSI5E44JL2RLA2WDYIYMNBTG7LYWLX
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jKs_jylUPkffgN6IS4supoqXfN0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
In May of 2023 the IETF LLC issued a request for feedback [1] for four possible venues for an IETF Meeting: Beijing, Istanbul, Kuala Lumpur and Shenzhen. The feedback was such that a further consultation [2] was undertaken on proposed response to the issues raised and a final decision was announced [3] some months later. Two of the key outcomes from this process are a revised venue assessment process that now focuses much more on lived experience of IETF participants, and a new step in this process that, under specific circumstances, requires the IESG to make a determination before the IETF LLC can proceed with booking a venue. This new process is now documented on our website [4], and the template venue assessment report [5] has been updated and guidance added. Step 4a in this process is the new step involving the IESG. In addition, we have concluded our first venue assessment under this process, which is for Shenzhen, China [6]. This is an example of an assessment where the IESG step has been invoked and that is now with the IESG to consider. Finally, a general report that this work has slowed down our normal pipeline of venue assessment, which was set back by the pandemic. Looking forward though, we expect this work to pickup soon and we will be finishing off a number of partially complete assessments, reviewing some old assessments under the new process and looking at new cities in often requested countries such as India. Please feel free to contact me directly if you have any questions. [1] https://mailarchive.ietf.org/arch/msg/ietf-announce/ph216mZaUexR18dj_pkZrtWwn_k/ [2] https://mailarchive.ietf.org/arch/msg/ietf-announce/h0Aosxbo1B6JpEg2_5tYtWZqMC4/ [3] https://mailarchive.ietf.org/arch/msg/ietf-announce/-gewAEBtXqCHyAjfVWAfKSVcxYY/ [4] https://www.ietf.org/meeting/planning/ [5] https://www.ietf.org/media/documents/IETF_Venue_Assessment_Report_TEMPLATE_v3.pdf [6] https://www.ietf.org/media/documents/IETF_Shenzhen_Venue_Assessment_Report_2024-06-11.pdf -- Jay Daley IETF Executive Director exec-director@ietf.org
- Update on venue assessment process IETF Executive Director