[Venue-selection] Beijing and Shenzhen

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 15 June 2023 16:02 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: venue-selection@ietfa.amsl.com
Delivered-To: venue-selection@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 40B1FC14CF12 for <venue-selection@ietfa.amsl.com>; Thu, 15 Jun 2023 09:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Status: No, score=-2.094 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DUXOniF1Ldld for <venue-selection@ietfa.amsl.com>; Thu, 15 Jun 2023 09:02:04 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 906A4C14EB19 for <venue-selection@ietf.org>; Thu, 15 Jun 2023 09:02:04 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id ada2fe7eead31-43b3b30bd55so1148921137.3 for <venue-selection@ietf.org>; Thu, 15 Jun 2023 09:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686844923; x=1689436923; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Cweo2DhX5gWMR2qfCz9bWrrje4A/zp2CXl1cWe9NOP8=; b=e3XAcaVy/Ot7vzoynxnxwCiRu9gfrXJQr5GYNeM/84t9jFayvIk5fsYi0HC6pB1BJw BZyQsKMP2b/iNAHUAAGgjix3k9n4whv1SqJlgljpFFSvXAb+++tjn04lA5VfsQ6JLSuc xAv2q1KKOUHd600QhuMk2lm4Y49VF6XHZXzMFAvAsbBZN20WheX6sf3EPX/zCaadR3m3 yOQ0532UD4ykPb747Fu57AzEMkvlecRIk+1AtsHZwn7gBg1zsN60+ltk1w/D2hQ5s5Ij gAcSTTlFrzt9moq8pF6n5Dp+lWHsaiGH2rmD9uEjvT792jzABDK9mtNvuE28xDRGuBWF pJag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686844923; x=1689436923; h=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=Cweo2DhX5gWMR2qfCz9bWrrje4A/zp2CXl1cWe9NOP8=; b=QR76NwCOl8SdLf8DPEHV0hU1WCoWcHKm7tFupVAe+Q6MbeoclNeJeRprJhLyUL10cW ItIEhIgvH4N9vAGaOztZtaSgFuK6oku8r2Wm75KuWVwRvVzjR/JPA48/gmDEWyZe4OAP qMNvBGfLiWpNtf93rumeQFbDqgvKguboZbAq53+aioiCMG20I4qoHR5PtDTeUACKQpkG ISC0u+NIU7BxdlU2w09ryNIncfgew8F0YXZFscTvmDJN4j0/TlOZxzMd3Ap6gfGZFVYq SVYqOJjfdBNeXg9N/eX+0sYPys/o5Pj7JLJ1dYnSbkXjzoZCqLmNbkDuPWlq7pEkw8mf npTg==
X-Gm-Message-State: AC+VfDxKkJEWtm7Cde0FjwmZMM0JDW+cYJCQ09rbywt93KnstqdfEblC pn29NjWVX1SjeIwzWydOOYRZQsJKfgQ41zsdJod2XwWNGYs=
X-Google-Smtp-Source: ACHHUZ7r+brlZqZHNUYrmKs/reqE511RzsbF7f+mviXGI4KhH4wFfZUOwKvtEMprOJWo4hknK6X8BAG8EmgNFLOwdcc=
X-Received: by 2002:a67:e286:0:b0:43f:5e76:7789 with SMTP id g6-20020a67e286000000b0043f5e767789mr897951vsf.24.1686844922390; Thu, 15 Jun 2023 09:02:02 -0700 (PDT)
MIME-Version: 1.0
References: <7B7E7C75-FE6A-4B2B-B960-6AA81D5655D6@ietf.org>
In-Reply-To: <7B7E7C75-FE6A-4B2B-B960-6AA81D5655D6@ietf.org>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 15 Jun 2023 21:31:25 +0530
Message-ID: <CAB75xn5FwFWdQBcz5iuh3qZd3Q0mmkDhy25xP=WkybNJ9meZ9g@mail.gmail.com>
To: venue-selection@ietf.org
Content-Type: multipart/alternative; boundary="00000000000063ece205fe2d30af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/venue-selection/7iUnn0Ypu29dt55c3DRZytUAPjE>
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: Thu, 15 Jun 2023 16:02:08 -0000


Full disclosure: I work for a Chinese company but I am based in India (a
country that has its share of troubles with China). I also identify as
queer and non-binary. I serve as an IAB member but this email is without
any hats!

I have been travelling to China since 2003 and thus wanted to share my
first-hand experience. I have been to both Beijing and Shenzhen, with more
time spent in Beijing. I have not travelled to China since Covid so my
experiences are from before but from what I hear anecdotally that things
are returning back to normal.

In all my travels, I have not faced any issue while travelling in and out
of China. I have not faced any racial or homophopic treatment by any
officials or the locals. In the report there is mention of religious
intolerance, but for all practical purposes in Beijing/Shenzhen, I
don't think it to be a problem. The visa process was easy enough, much
easier than some western countries for me (I have applied 18 times, just
counted :)).

I did attend the Beijing IETF back in the day and I thought it went well,
especially the issue of internet access was handled. I am sure this could
be arranged again. I know it would still be an issue outside the meetings
but I think it is manageable, though not ideal.

I do understand the concerns of some who work for governments that consider
China as hostile or are active in the public policy space and would find it
difficult or choose not to travel.  But, as someone who has been working
towards IETF outreach and cares deeply about increasing participation in
IETF from Asia, I would like us to return to China. The participation from
China has been increasing and it has scope for more. We see many Chinese
proponents bringing in new work in IETF and for the future of IETF we need
to strengthen it. We don't have perfect venues in Asia but having meetings
in this part of the world is important and I hope we go back to China. I
understand that there are human rights concerns, we do like the internet
policies in place, but a decision to have a IETF meeting is orthogonal to
that. It should be more about IETF participants and the community in China
rather than the actions of the government in charge.

On Tue, May 23, 2023 at 11:58 PM IETF Executive Director <
exec-director@ietf.org> wrote:

> The IETF Administration LLC is seeking community input on the cities of
> Beijing China; Istanbul,Turkiye; Kuala Lumpur, Malaysia; and Shenzhen,
> China, which it is considering as future meeting venues. All of these
> cities are being considered for IETF 125 , March 14-20, 2026.  Other cities
> may also be considered for that meeting.
> In line with our venue selection process we present assessment reports and
> preliminary recommendations for each city:
>         Beijing, no recommendation, report at [1]
>         Istanbul, not recommended as suitable, report at [2]
>         Kuala Lumpur, recommended as suitable, report at [3]
>         Shenzhen, no recommendation, report at [4]
> Community input is now sought on these assessment reports and preliminary
> recommendations. To provide input, please email venue-selection@ietf.org
> with the name of the city in the subject line. This is a publicly visible
> one-way e-mail address: You can read the input [5], but you cannot
> subscribe to it. Additionally, all feedback is collated and published on a
> public Trello board [6].
> This call for input closes on 16 June 2023.
> Finally, details of the selection process [7] and completed and
> outstanding location assessments [8] are on our website.
> [1]
> https://www.ietf.org/media/documents/IETF-Beijing-VenueAssessmentReport-2023-05-22.pdf
> [2]
> https://www.ietf.org/media/documents/IETF-Istanbul-VenueAssessmentReport-2023-05-22.pdf
> [3]
> https://www.ietf.org/media/documents/IETF-KualaLumpur-VenueAssessmentReport-2023-05-22.pdf
> [4]
> https://www.ietf.org/media/documents/IETF-Shenzhen-VenueAssessmentReport-2023-05-22.pdf
> [5] https://mailarchive.ietf.org/arch/browse/venue-selection
> [6] https://trello.com/b/whq8I098/venue-selection-input
> [7] https://www.ietf.org/how/meetings/planning/
> [8]
> https://www.ietf.org/how/meetings/planning/meeting-location-assessment/
> --
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce