Re: IETF 127 San Francisco reassessment
Ted Hardie <ted.ietf@gmail.com> Thu, 12 June 2025 08:03 UTC
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A2F38340ED93; Thu, 12 Jun 2025 01:03:59 -0700 (PDT)
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 VyciTj8TtfpD; Thu, 12 Jun 2025 01:03:59 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 05A93340ED8C; Thu, 12 Jun 2025 01:03:59 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-607c5715ef2so1222718a12.0; Thu, 12 Jun 2025 01:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749715438; x=1750320238; 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=yd5fcL5OPE3gIspKWR18QtALM6MRalhUJYpQexeBJew=; b=BiMsWdP86ZZPyxAkACnjdelKlQgN0y1eScYrdYRw9aR0AEnRcSetqkt/YO+yCgCbRr vXQUVGl5liCP3jrDVMjX13fQUWlkn31WLKd8735PMPvZy5J14mXyAPlXzb5J5NyCfC5d iagNw7FVqfgRNtf9riPZ4Vs7/MDUjA3NNatsGdhO0w5FMEDjqbzKWWEZUAlWI6VIeSM1 pCg3HPNNKDcVVcAvsbX8UwPfD63T6EhDrZ+t2aYabtr4unZY3GdsBFCBuQnk55Lk/CGs S4fW+7c0iFpu1H1B3mfla4b8b/S4Fd1B/mmfP3aftf/lDjEEP9+T7sf/HsGhE9pCtQ/Q zxag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749715438; x=1750320238; h=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=yd5fcL5OPE3gIspKWR18QtALM6MRalhUJYpQexeBJew=; b=klg3DEGzneEj9sSZn47x3oOSZvEunUfc3gr4IZNwrLQAMANcCRRhSL7D/6Ykx3EaUj g9uj2c2T+lQ93HBzqjCD7G1r1fnnOFgE7hSmeecyQZPIYL27n0v8j0KcB0WvHmpFi1LF l17Yyc4iZlB/WPRwxVz67CpwlJrBikE/VC2MS65gJGFdLb3T0brtN75m48vG2DdqFAu7 1zOOf3hk+W5KpEiEtsBE+knkFkjdh8RqC2+uyjRjK5ubAxsmHqT2okz1ZpQT3vKCT++J deT5J/P50jXGqI8M3KjI8+VJYKFG4uQv7W50bFCsijYVJP87XHZA8bZzbTcNCFHf35Pl EyLw==
X-Forwarded-Encrypted: i=1; AJvYcCUm7gUj9wGj27NCllbUh13W4NL+ytshU5DGBKuY/Pki7Spex7nlMCsu3ySgpHuPul8gQml0@ietf.org
X-Gm-Message-State: AOJu0YyLoJleB8eYopoAiGSmnhNt1SYG5tgDa55CIyFn/5zB0fXPZZtR TcsGT7qC/6UobfXrS1IiS+KusDirX94v975zYyw2l+adnT7gFxDAMtHkKLcqmFDM8TkugKvdvJO ySHklsOopK8uvpetEL5/TVKLhVsQCWHSfvQ==
X-Gm-Gg: ASbGncuVoViGrJnXhRH3FAbAbLw5H5LSzzQhNylDqk4mzjvdMaBMY3uegKvaFlXTrO6 SxGLpoA8o5hZAsnc97+YZpHX2Xiw/9SM0pBxy684d24m492Lkw+Dah7FIGdigxV8XzBez+LY44f 6hDTDfC1N5sS4XGpXXxqerVeolZHFkEPWLXgxYEzEUJhYvKtjynwZULIo=
X-Google-Smtp-Source: AGHT+IGMjhbkwpAp8wfcfy6ulnMHkyM8mGZC/6faUYbNKKpvhl9DDwpiM3lRwJ3GCrneVEqC4MRzZNyHc+UuCvM1X6I=
X-Received: by 2002:a05:6402:2749:b0:608:493a:cccf with SMTP id 4fb4d7f45d1cf-6086b2f0322mr1735531a12.30.1749715437176; Thu, 12 Jun 2025 01:03:57 -0700 (PDT)
MIME-Version: 1.0
References: <0E13A03E-3B81-4C9C-976E-B8C68810B486@ietf.org> <CA+9kkMBoDhQq4GROSYQ0AjJ3Um-7XsL6D8s+R+rRDkX8fv-NnA@mail.gmail.com> <CA+9kkMA__=wsDz1w=y5OaG1-aD5TvsMDiPSG+Z-60MYQwrO2GQ@mail.gmail.com> <6C4A07E0-299A-48E5-91B2-8AB8E96B0908@ietf.org>
In-Reply-To: <6C4A07E0-299A-48E5-91B2-8AB8E96B0908@ietf.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 12 Jun 2025 09:03:30 +0100
X-Gm-Features: AX0GCFvh1x5bfhwHzjA08TyL5yutWz14jV69HwFyy-7mWuHRJ9zG-I5t8fwge_8
Message-ID: <CA+9kkMA32xWVW9r1xxVVfgMbo6pS3xk1h7kMZ7L2jkULsZRktQ@mail.gmail.com>
Subject: Re: IETF 127 San Francisco reassessment
To: Jay Daley <exec-director@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000174bff06375b5f1b"
Message-ID-Hash: USX6M3IT6EQRGNKUCCGCHTIQ52I3DKEB
X-Message-ID-Hash: USX6M3IT6EQRGNKUCCGCHTIQ52I3DKEB
X-MailFrom: ted.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: IETF <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l-zCNHRw1QdgsbdUZ7EMB-P67jc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
Hi Jay, A clarifying question below. On Wed, Jun 11, 2025 at 11:59 PM Jay Daley <exec-director@ietf.org> wrote: > Hi Ted > > This response is sent on behalf of the IETF LLC Board. > > > On 23 May 2025, at 20:12, Ted Hardie <ted.ietf@gmail.com> wrote: > > > > Dear Jay, Roman, and members of the IETF LLC board, > > > > In the statement below, you say: > > > >> It also considered the viability of the meeting and concluded that > there will be sufficient participation for the meeting to be financially > viable and to meet the threshold set by the IESG for a technically viable > meeting [3]. > >> > > The citation is to the IESG response for the community discussion for > Shenzhen, not for a decision by the IESG about San Francisco. In that > process the LLC was asked to “explicitly confirm with the IESG that the > core objective from RFC8718 of ‘Why we meet’ will be met”. > > > > Is this reference meant to indicate that the IETF LLC used the data from > the previous consultation to make this decision? Or did the IETF LLC > explicitly confirm with the IESG that the core objective from RFC8718 will > be met? > > > > Roman, if the latter, I would appreciate a citation from the IESG and a > summary similar to that in section E of > https://www.ietf.org/media/documents/IETF_125_Decision_and_Survey_Summary_version_2024-10-08.pdf > . I believe it is very important that the community understand the IESG's > conclusion here, in addition to the IETF LLC's, as the IESG is charged with > the standards process and part of the risk here is to the standards process. > > > > Jay, if the former, I would like to understand why the IESG was not > asked a similar question, given the community objections raised. > > > > My thanks for your attention, and I look forward to your responses, > > The IETF LLC introduced a new step in the venue selection process that > asked the IESG to assess if a meeting will be technically viable, in > response to community concerns about a meeting in China. This process was > followed for that meeting’s venue planning. In their decision, the IESG > effectively set a lower bound on participation by core contributors > necessary for a productive meeting. > > For clarity, do you believe the new lower bound to be that set by IETF 113, which is cited in the IESG's decision or the predicted attendance for China? If I am interpreting things correctly, the onsite attendance for IETF 113 was 22% and this occurred as the pandemic lockdowns were just beginning to be eased. (from appendix D of the IESG decision). The predicted attendance for the China meeting is 51% (from appendix E). > As part of the venue assessment process, the IETF LLC Board signs off on > estimates of onsite participation for every meeting and the corresponding > meeting space requirements and accommodation guarantees, taking on the risk > of over/under usage each time it does so. The IETF LLC Board, as part of > its broader review of the IETF 127 San Francisco meeting, concluded that > participation would be above the lower bound set by the IESG and therefore > the new step of asking the IESG was not required. > > I do not believe that this change was communicated to the community adequately, if it was communicated (I cannot find it in my archives). If the IESG has set a participation floor, I believe it would be appropriate for that to be communicated via an IESG note, which generally get community attention. My thanks for your response, Ted Hardie > kind regards > Jay > > -- > Jay Daley > IETF Executive Director > exec-director@ietf.org > >
- Re: IETF 127 San Francisco reassessment Eliot Lear
- Re: IETF 127 San Francisco reassessment Jeffrey Walton
- Fwd: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Phillip Hallam-Baker
- Re: Fwd: IETF 127 San Francisco reassessment S Moonesamy
- Re: Fwd: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Jay Daley
- Re: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Jay Daley
- Re: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Phillip Hallam-Baker
- Re: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Rob Sayre
- Re: IETF 127 San Francisco reassessment IETF Executive Director
- Re: IETF 127 San Francisco reassessment John C Klensin
- Re: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Corinne Cath
- Re: IETF 127 San Francisco reassessment Jay Daley
- Re: IETF 127 San Francisco reassessment John Levine
- Re: IETF 127 San Francisco reassessment Ted Hardie
- Re: IETF 127 San Francisco reassessment Jay Daley
- Re: IETF 127 San Francisco reassessment Ted Hardie