[Venue-selection] Beijing / Shenzhen

Vittorio Bertola <vittorio.bertola@open-xchange.com> Tue, 30 May 2023 14:28 UTC

Return-Path: <vittorio.bertola@open-xchange.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 849D3C1522C8 for <venue-selection@ietfa.amsl.com>; Tue, 30 May 2023 07:28:41 -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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=open-xchange.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 fhT2uN_eS_CU for <venue-selection@ietfa.amsl.com>; Tue, 30 May 2023 07:28:37 -0700 (PDT)
Received: from mx4.open-xchange.com (mx4.open-xchange.com [87.191.57.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F39FAC1522C4 for <venue-selection@ietf.org>; Tue, 30 May 2023 07:28:36 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx4.open-xchange.com (Postfix) with ESMTPSA id B1CEB6A0CD for <venue-selection@ietf.org>; Tue, 30 May 2023 16:28:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1685456914; bh=ee9K1rIaz4hofbqi9dpCXjA7pxtgep70SSNSJEtK4dM=; h=Date:From:To:Subject:From; b=EH3u5BMs1Pc5ezuUp9n1mgCEuBkwx9COdlDlovUbM7zJ8UIiTMSXQajwcmtHYWUvT 8R6eSmtiLYEOwAK7+u3d10eQ7SQZUlQGb+jaV+sKRFF8YJR24WuGSjjxRXVdh6AKxI /zrdm9edGN3392xvx5q5lMiettfTM4mG0Vxab32Eha6JkCBVk81od0Pid22dzCSasp UaAtvkhuv/lzEkk0LQLCIF2BUHB8f1Bwx16bNBA9m9hu65qi3fK8tX5oCHRSa3IIyg FVmRkomSR/uPuD3tTP8sm+xheU8f10LaKrHj+hltbcfp+FD9y0SUadKXzc9v0dUICf uoJfx6UkwcBoA==
Received: from appsuite-gw1.open-xchange.com ([10.20.28.81]) by imap.open-xchange.com with ESMTPSA id 31P6JxIIdmT94QEA3c6Kzw (envelope-from <vittorio.bertola@open-xchange.com>) for <venue-selection@ietf.org>; Tue, 30 May 2023 16:28:34 +0200
Date: Tue, 30 May 2023 16:28:34 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: "venue-selection@ietf.org" <venue-selection@ietf.org>
Message-ID: <1917458021.86465.1685456914615@appsuite-gw1.open-xchange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev44
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/venue-selection/Vmm9sPCXtI13vo7P9VR3HXMYO1E>
Subject: [Venue-selection] Beijing / 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 14:28:41 -0000

Hello,

I understand that no final conclusion has been made, but I would like to provide some thoughts on why judging the two Chinese cities unsuitable would be in my opinion a mistake.

First of all, if the IETF decided that China were not suitable as a country for meeting, it would be an outlier in the industry. For example, the IEEE is holding several conferences in China this year, and the GSM Association has a MWC Shanghai event. There is nothing bad in making opposite evaluations, but the IETF should make sure to have firm ground for them.

Interestingly, the reasons against accepting the two cities do not seem to be related to the availability of unfiltered Internet access, which apparently the local organizers have guaranteed, or to visa hardships. On this latter point, the 80% criterion seems skewed in favour of having meetings in countries where most of the participants come from; indeed, getting a U.S. visa for Chinese and Indian citizens can be as hard as getting a Chinese visa for European and North American citizens, but since we have fewer participants from Asia than from the Western countries, only the latter situation fails the test. In practice, the assessment of this test relates to how much the IETF wants to broaden the geographical diversity of its participation.

Anyway, the only two criteria that are not met are the one on the U.S. government assessment of travel safety, and the one on religious freedom.

The first criterion was already problematic in times of covid; I remember several participants from Europe challenging the meaningfulness of assessing the safety of travel only from an American point of view. I also remember that the secretariat pointed out that such test is mandated by our insurance agreements, yet, in the end, asking the U.S. government alone whether we should or should not go to a country makes for a strong geopolitical statement.

Moreover, the assessment that Beijing or Shenzhen are less safe than Philadelphia or San Francisco, to mention places where we just went or will go soon, is impossible to justify on any factual ground. The violent death rate in the two American cities is 20.0 and 6.4 per 100'000, compared with 0.5 in China. Similar comparisons can be made for more or less any type of crime. Declaring China so dangerous that nobody should ever go there sounds like a form of prejudice.

As for religious freedom, it is honestly hard to understand how Malaysia (still, one of my favourite Asian countries) can be assessed as "green" and China can be assessed as "red" at the same time. Specialized organizations (see e.g. https://www.opendoors.org/en-US/persecution/countries/ ) put the two countries more or less at the same level of religious persecution. Also, as a non-religious person, I am sincerely disturbed by religious considerations informing any choice at the IETF; religion is an optional private practice and should never influence the public sphere. I am even more disturbed as I discover that failing the LGBT+ tolerance test is not a problem (see Kuala Lumpur's assessment) but failing the religious tolerance test is.

In the end, I have been several times to China (lastly in January 2020) and I would enjoy going there again, but I would also enjoy Kuala Lumpur and even Istanbul. I do not have a strong opinion, but I am worried that the IETF is creating itself problems with its own hands, both internally and externally.

Internally, China is by far the second country in terms of origin of our participants and community, and having at least one meeting in China every now and then would just be normal. Not doing so would feel like a statement of second class citizenship in this organization.

Externally, in times of extreme sensitivity, showing hostility towards China - no matter how and why - will be perceived as a choice of geopolitical camp, with the IETF conceiving itself not as the SDO of the global Internet, but as the SDO of the Western Internet only. While Internet fragmentation is here to stay, there is no need to add more of it on our own - in fact, we need to build bridges, not burn them.

A more sensible course of action, in my view, would be to accept the two Chinese cities as suitable and then evaluate them in comparison with other Asian cities whenever a meeting in Asia is expected to happen. This would perhaps lead to the same result of not meeting in China, but with a general sense of better fairness and respect for the Chinese Internet and IETF community.

Kind regards,

-- vb.