Community survey on IETF 125 venue

IETF Chair <chair@ietf.org> Thu, 04 July 2024 12:58 UTC

Return-Path: <chair@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from [10.244.2.3] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id BA7B2C14CE4A for <ietf-announce@ietf.org>; Thu, 4 Jul 2024 05:58:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Community survey on IETF 125 venue
X-Test-IDTracker: no
X-IETF-IDTracker: 12.17.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172009790139.1179369.929314872942246373@dt-datatracker-5f88556585-g8gwj>
Date: Thu, 04 Jul 2024 05:58:21 -0700
Message-ID-Hash: EB4ON77B66WPHEZWPE4NFCHEN7G56OYG
X-Message-ID-Hash: EB4ON77B66WPHEZWPE4NFCHEN7G56OYG
X-MailFrom: chair@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
Reply-To: iesg@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Og9ESsfDWrhy5Ea8tso7HfaqY5A>
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>

Hi!

# Summary

The Internet Engineering Steering Group (IESG) needs input on planning IETF 125, the March 2026 meeting.  All registered participants in a past meeting between IETF 114 and 119 will receive an individual and non-shareable survey invitation via email with the subject “IETF Survey on IETF 125 venue” from “noreply@qemailserver.com”  The survey will close Saturday, 27 July 23:59 UTC, 2024, the day after the end of the IETF 120 meeting in Vancouver.

# Detailed Explanation

The IETF Administration LLC operationalized the responsibility given to it by RFC8718 of “arranging the selection … of the IETF plenary meeting venue” by creating the venue identification and selection process [1].

Consistent with Steps 1 - 3 of [1], the IETF LLC assessed and consulted the community on holding a meeting in China (Shenzhen or Beijing).  It concluded that such a meeting venue is within policy and financially viable.  See [2], [3], and [4] for a reference of these assessments, call for community input, and the two summaries of this community consultation.

Due to community concerns expressed with these venues, the IETF LLC has turned to the IESG per Step 4b of [1] to validate that the core values of “why we meet” of RFC8718 will be met.  

==[ from Section 2.1, Core Values, of RFC8718 ]==

Why we meet:
We meet to pursue the IETF's mission [RFC3935]. This is partly done by advancing the development of Internet-Drafts and RFCs. We also seek to facilitate attendee participation in multiple topics and to enable cross-pollination of ideas and technologies.

==[ end ]==

The IESG has assessed that it cannot answer this question of whether a given venue meets the core objective in RFC 8718 of “why we meet” without direct input from the community on their plans for attendance and engagement at the proposed IETF 125 venue.  Hence, a survey will be sent to all meeting participants since IETF 114 with the subject “IETF Survey on IETF 125 venue” from “noreply@qemailserver.com”

The IESG will synthesize this community feedback after the conclusion of the survey, and plans to answer the IETF LLC’s question about the venue by September 2024.   This decision will be shared with the community along with the aggregated survey results.  If the IESG decision is affirmative that the venue meets the core objective of RFC8718, then the IETF LLC will proceed to step 5 of [1].  If the decision is negative, the IETF LLC will not proceed with these venues in China for IETF 125 and will consider alternatives.

If you are a survey recipient, thank you in advance for your prompt input.  The survey deadline is Saturday, July 27 23:59 UTC, 2024.

Regards,
Roman
(as IETF Chair, for the IESG)

# References

[1] https://www.ietf.org/meeting/planning/

[2] https://mailarchive.ietf.org/arch/msg/ietf-announce/ph216mZaUexR18dj_pkZrtWwn_k/

[3] https://www.ietf.org/blog/proposed-response-to-meeting-venue-consultations-and-the-complex-issues-raised/

[4] https://www.ietf.org/blog/final-response-to-meeting-venue-consultations/