[Venue-selection] Beijing and Shenzhen

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 30 May 2023 21:24 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: venue-selection@ietfa.amsl.com
Delivered-To: venue-selection@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCA7C15198B for <venue-selection@ietfa.amsl.com>; Tue, 30 May 2023 14:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 v8FGosdSimhi for <venue-selection@ietfa.amsl.com>; Tue, 30 May 2023 14:24:19 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 A3EB0C151981 for <venue-selection@ietf.org>; Tue, 30 May 2023 14:24:19 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id 41be03b00d2f7-53fa455cd94so1234042a12.2 for <venue-selection@ietf.org>; Tue, 30 May 2023 14:24:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685481858; x=1688073858; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=3hKfa8nReLopLDzClkEg16pUaKSpjmo8WZkXq/Cp8Hc=; b=GFFGazBuXDBb/jCOwiuiPe5Vr2090e/YCCeARxtH0lcNr703cUQWHnvf6LxDB+wv8P jusInKmC0kGtwmuqBmjl4PV+MZb8PWWBWYVndq4pHcFWxa19kOS0aofsvf6n7zWq08NX nkFW4n0s9f8x5lteWsZtm120bUkVF5Vpc7QwcoMWRe1IwPs3xnoiaYY6Y/zlT9W9NX/o Yn1OEsj+fUdY30w7iLFI4XE+GVAvDlJfmcrBRf0f9hSHoBsElfQDe0XlfdMYpLctNGDb NckJGoGWSpqYEjDKZEkYnMS/OzV5lFu874cyQGruu8oATRF1q8xPVn2EAWYBaQD28M83 JhDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685481858; x=1688073858; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=3hKfa8nReLopLDzClkEg16pUaKSpjmo8WZkXq/Cp8Hc=; b=MaQ39GMBb0VFxgYerI0DmpW+BJCFZ1cHqbU/57ALCAOo5ouKA70EnMx13D1nHYJG09 mp2UT+7H2RxFxGR+Qi0vdkmuti+0DqhIarb3djRoIp9kx2GAaFHkJPu3FVZEtguAJFtb ybfUzzkr5tzYt05uhybFgSML+F5dAg+bc7jqTVf4RFQI8NQSz2Poe6yTMWGgzjvmicl+ So724R8KmDmVKIfuWb/xeCc7k9xbU1GcuKi5bf63doA6FBBt90Hk0XBogF2h3KwlUZJq Lr4hxQlV3boCYB/9bI/yY1Y2dDDHzAutxFsy1ejsm7XE2TDYco6U2lo2xIbM6wkT0ueK O/3A==
X-Gm-Message-State: AC+VfDzdq8rtIRXh+jshOPGIyiDHPudGWSnsTsm3Gkj+LPsB8ksqqgBR OjRzvQgq5taPDVkYFDbPDiz99PgsLLxJen+DNe90vWVg
X-Google-Smtp-Source: ACHHUZ6hRaS0qPBEQ5IZ9v4Ct9CoBI094FTTegeyxcrZnn2y6CWUUMrD24G9pK5OPiq/0kjPOHhFpy1cZgQEu/m1zX8=
X-Received: by 2002:a17:90b:1d92:b0:256:5d2b:1c48 with SMTP id pf18-20020a17090b1d9200b002565d2b1c48mr3720230pjb.43.1685481858419; Tue, 30 May 2023 14:24:18 -0700 (PDT)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 30 May 2023 16:23:52 -0500
Message-ID: <CAKKJt-dY4TyGFq6C0=Zmnii=A97bRxOgMx1JjxSjr=RXZxU_0w@mail.gmail.com>
To: venue-selection@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007251ed05fcefd3b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/venue-selection/z4L6m5cye_QyQquxUzKNSFu9qsM>
Subject: [Venue-selection] Beijing and Shenzhen
X-BeenThere: venue-selection@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Venue Selection <venue-selection.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/venue-selection>, <mailto:venue-selection-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/venue-selection/>
List-Post: <mailto:venue-selection@ietf.org>
List-Help: <mailto:venue-selection-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/venue-selection>, <mailto:venue-selection-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 May 2023 21:24:20 -0000

It will surprise literally no one that I have no concerns for myself about
attending IETF meetings in Beijing or Shenzhen. I have worked for Chinese
employers since 2005, and have traveled to those two cities more frequently
than any other cities in China.

I was working for Futurewei when the IETF met previously in China, and
although Huawei wasn't the local host, we were involved in a number of
discussions about the IETF's expectations for a Chinese meeting venue.

Other people may remember differently, but (this was pre-public venue
selection, remember) my memory is that the most consistent concerns
expressed by IETF participants, especially those involved in planning, were
about air quality/pollution and access to an unfiltered Internet.

   - Air quality in Beijing in 2005 was amazingly bad. I haven't seen
   measurements, but I'm glad that the evaluation says air quality has been
   acceptable since 2017.
   - Access to an unfiltered Internet was more complicated. As others have
   observed, we DID have unfiltered access to the Internet, but IIRC, no one
   in China would guarantee that in writing. The IETF took a deep breath and
   booked the meeting venue, based on verbal assurances, and those assurances
   turned out to be accurate.

Given that experience, and the experience of both IEEE 802 and 3GPP with
meetings in China over nearly two decades, I wouldn't disqualify either
venue at this time. Keeping them as eligible alternatives seems wise.

Editorial Note: there is a special place in hell for people who are
presented with consensus venue criteria and asked for input, but who
respond by either

   - providing input and commenting on the selection criteria, or
   - by just commenting on the selection criteria.

I apologize in advance for fitting into the first group of people.

ISTM that one of the unforeseen consequences of our determination to make
hybrid meetings work that the remote participation experience at IETF now
is far superior to either what that experience was, even as recently as
2019, and also far superior to the experience I had as a local attendee in
3GPP hybrid meetings last week in Berlin.

I would paraphrase our attitude since our hybrid meetings started, as "if
this venue isn't good for you, Do The Right Thing and attend remotely". I
absolutely understand the value of in-person participation, but none of us
are guaranteed that. The last in-person meeting I missed was in Montreal
when my wife had just been diagnosed with cancer, and I was able to do my
work as an AD effectively, even attending remotely.

I'm not sure if the venue selection process considers that or not, but if
it doesn't, maybe that's worth thinking about.

Do The Right Thing, of course.

Best,

Spencer