[Gendispatch] Re: Fwd: New Version Notification for draft-hardie-venue-reassessment-00.txt

Ted Hardie <ted.ietf@gmail.com> Fri, 07 November 2025 22:22 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7826285C8047 for <gendispatch@mail2.ietf.org>; Fri, 7 Nov 2025 14:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8HHokoxbiUZ for <gendispatch@mail2.ietf.org>; Fri, 7 Nov 2025 14:22:07 -0800 (PST)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 9AD2685C7FA7 for <gendispatch@ietf.org>; Fri, 7 Nov 2025 14:21:51 -0800 (PST)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-7866bca6765so11466047b3.1 for <gendispatch@ietf.org>; Fri, 07 Nov 2025 14:21:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762554105; x=1763158905; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c4nf9D2mazPgI2Ce1Ll8BP1SuhEiLoeDVMrI37XBtro=; b=lUUaAV8qZ2hti2HlaDXDNFzG7+5F02nPzoZnC+Y0qNFQQMR8rvUFptPvqQ+qK+A9x9 rKIRtclW2MrfCRbIlUP48LBnabGk5Dl2ovEkEqinDdjgJfa4pH7Usvy8YTlNNP0xZdji JjG04G0xlLbBcW/Uu0LROD8ZkJ8fzbHJ3e0/Zc+4TURhQVIx/nhwD35iny/YIJgU4YYT /1zo1Sx+j1iBrLdCydg13EQzMnL/2Lg8qS29yqpmU/Mn2ZFrDgxFN/gUBSb6cYo/SlRd 0HIcZ8W8tAOTm+6Z5JfNYcd93kl/EXbp4tIwxen4LveaCY+RqLM7pnWaj5zerWrxEuIg dxSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762554105; x=1763158905; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=c4nf9D2mazPgI2Ce1Ll8BP1SuhEiLoeDVMrI37XBtro=; b=MClLvOfe5jLGtK4rCywwN+GHL7AnqlFgP9y34Q13HmrWVzSM/qzlNaVIgH5yl030uN ZD2r8G3VqhrYhVwnoU51sjR6YZmqizhfL9biOZLJusecFWOHv5KN88Q2i+I+rYTDDMwH P85GWC+BI8X1XziF6g+PwGOM+uDFFA2r9FTFWO5EYfBGOowY7WNRQwI44OKsrf1RNH17 zUjMKpVebkaz4rV6VOVKRCbZrNpfcsIJr9LF+Ykjj+dfwIRG3RGnFS7237kjNNgBhvbZ 7u1ZC16gv2hMUuFTUJZyvBtcwhXlsIMCI/UA7ypBb+Pl6ZHDfo7x4JKnyMPJa9YCsUxw f2YQ==
X-Gm-Message-State: AOJu0YxtZjN9fzcXj610NbL1lSk8t8hl7WCzcHkQTN0X7WWatHogep95 Cn4kS3IvlSj2Ywtbi1QRyMSmHoMgLrQW3Smcn2xVipwStkElRfArur8s7UM7Cx+rGNrcpAJRk8B qCfc0w0OV+3zM8NARhf9DK0u/9yxiyki78EceVnY=
X-Gm-Gg: ASbGncs23q8pWij/qrH7X9Y22ofefZ47UIbFaVV/5VScfGj4wYwGPEAHBFdUnMxcNfS p2ObSbs7wSRRWf+GcZmkdNSCLeR50vdy8jOdQHK8iT7xgB3y1dz5thS/w5/y1N0Yq2OIRhMekLJ 9SyIGLrQtz3pe4H2NPt41cBQ61QtlU0uSG1D2GDtZYSVspdhhsuJIb6TCHX8G06UXKmbxPEgTGV BhIYxbP7hF0wkln3MXM0I1ZrtWEmLzloFtveCLtEN+Mr24RRy/L3uRjTU53EMNUer/ztG0goIBl GIt5vm7x9pfVjAST4Keh4sqL8g==
X-Google-Smtp-Source: AGHT+IGQiGwmVtNQyavb6YeXqetsCK26jHPaYmbrp3yCYdeg7Q/E2ldekyVUzna8adQAeodDpzauZi9lAYMhACKVav4=
X-Received: by 2002:a05:690c:402e:b0:784:991e:4913 with SMTP id 00721157ae682-787d5363b14mr7423147b3.13.1762554104935; Fri, 07 Nov 2025 14:21:44 -0800 (PST)
MIME-Version: 1.0
References: <176254221005.1445829.11389276097832508430@dt-datatracker-5df8666cb-7l4w5> <CA+9kkMB1AXhcpqcpNUPNuijn16ctQWPrBqT50Dxqd1M3KnYb5A@mail.gmail.com> <916109102.2733.1762549907603@appsuite.open-xchange.com>
In-Reply-To: <916109102.2733.1762549907603@appsuite.open-xchange.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 07 Nov 2025 17:21:18 -0500
X-Gm-Features: AWmQ_blzQDLCTc_KHK9X7I3A8N2P_8zHKUiIPRVqmy2vxXUqlVxQOhdLL_Flclc
Message-ID: <CA+9kkMCsb_huO9Axw7B+KuS8ziBe9bAaHfMtSRTHwbMeUSAk3A@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Content-Type: multipart/alternative; boundary="0000000000005279310643089bba"
Message-ID-Hash: MJWA5BHW4FWMXUV6KAD7ZFYF6XXRIRW4
X-Message-ID-Hash: MJWA5BHW4FWMXUV6KAD7ZFYF6XXRIRW4
X-MailFrom: ted.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: GENDISPATCH List <gendispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: Fwd: New Version Notification for draft-hardie-venue-reassessment-00.txt
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/2bHxqHpUungancmgKi6-Hf4LGa0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

Hi Vittorio,

Thanks for reading and commenting.  The amount of time between the request
for reconsideration and the meeting will certainly be taken into account by
the IETF LLC and the IESG in assessing the next steps after a request has
been received.  The issue that this is trying to address is that we don't
have a stated process to request reconsideration at this point, even though
we have had reconsiderations in the past (e.g. IETF 102's move to Montreal
from San Francisco).  Without any clarity on what qualifies as a reason to
request reconsideration or the process that is followed, we have even less
certainty now than we would if we had one, or at least that's my view.

I understand your concern that a relatively small number of people could
make this request, but I will point out that our history is that formal
requests that require coordination (like leadership recalls) are very rare;
the community takes them seriously and does not present them frivolously.

Lastly, I will point out that one of the reasons for reconsideration if
this is approved is exactly equivalent to the one you raised: folks who
were originally able to meet in person finding out after venue selection
that this is no longer the case and their travel plans being disrupted as a
result.  I hope your concerns about the potential impact on your plans help
you empathize with their issues.  As noted above, very short time scales
for action after a reconsideration request may result in different
responses by the IETF LLC and IESG, and we may want to note that in the
draft.  Like all -00s, it is just an initial proposal for consideration.

regards,

Ted Hardie

On Fri, Nov 7, 2025 at 4:11 PM Vittorio Bertola <
vittorio.bertola@open-xchange.com> wrote:

>
>
> Il 07/11/2025 14:04 EST Ted Hardie <ted.ietf@gmail.com> ha scritto:
>
>
> Howdy GENDISPATCH,
>
> Roman and I chatted some time ago about this draft, and this is the
> mailing he suggested that I post it to for initial discussion.  I'm also
> happy to receive private comments, if you have any.
>
> Please don't do this. Maybe I am the only one, but I have to get funding
> for travel to IETF meetings in the previous year, as part of a budgeting
> cycle, and I need to know with certainty when and where they will be,
> whether I can attach other things to the same trip, and so on. Any change
> in location less than 12 months in advance will create problems, so it
> should be strictly limited to real force majeure situations such as global
> pandemic or war, and I am sure that the LLC is already authorized to assess
> whether such situations arise and deal with them. (ICANN did this recently
> for its planned Muscat meeting due to mlitary clashes in neighbouring
> countries, and even in that case, a lot of people were financially damaged
> and vocally unhappy, there were claims of unfairness and prejudice against
> certain areas of the world, and so on.)
>
> The idea that any 10 IETF participants (i.e. 0,1-0,2% of the average
> attendance) could force a period of uncertainty on travel plans at any time
> and at short notice is IMHO really disruptive. I could understand an appeal
> right after a new location is announced, and in fact we have seen several
> objections after some announcements, which have been addressed multiple
> times already. But after a while, certainty over our collective plans
> becomes more important than allowing a small group of people to challenge a
> specific venue selection for the Nth time.
>
> -- vb.
>