Re: [Mtgvenue] Was Brisbane a success to be repeated ?

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 25 March 2024 04:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873EDC14F680 for <mtgvenue@ietfa.amsl.com>; Sun, 24 Mar 2024 21:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=sandelman.ca
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 T60a6uOmlCBK for <mtgvenue@ietfa.amsl.com>; Sun, 24 Mar 2024 21:16:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 7D43DC14F5EA for <mtgvenue@ietf.org>; Sun, 24 Mar 2024 21:16:21 -0700 (PDT)
Received: from dyas.sandelman.ca (27-33-182-58.static.tpgi.com.au [27.33.182.58]) by relay.sandelman.ca (Postfix) with ESMTPS id DD9961F448; Mon, 25 Mar 2024 04:16:19 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="JuIX8SWa"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id A18F9A190F; Mon, 25 Mar 2024 14:16:15 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711340175; bh=f3cY5xxRbwYw6cuxZFNXucxsIfrjen/CfqoUd1TCnyM=; h=From:To:Subject:In-reply-to:References:Date:From; b=JuIX8SWaDhyA+AB4q5sEvYUe1mIVBGOnbCRWbAhX4gR/9pSu+O1kjLGP0GzbzK2Jz MZwMkkVcd6hz9CvaK7ZLlED1j3Yoet5btv6yGoH1H7Obu2t+sQl2lfKx0BSQQAHBJ4 wJo3tGndWEukq3WnEVxl/+4F6vqnE8Mja1jYpv9IG81XbnzHPvc+YwpAMIN14Sqgcs hyBvjMXKIKSq7PTeQSAhBZp6YlSwdTap2Rfayp4X8KFzGpaXVPDuKS4OX1kwpQciT7 be1zVbOEaoinUzueSwQ6OTLHH3mpFJWHpi7fa10fDF0f3BiEPqRotd5q0mzWfFKFEA 0Nu01yicKTW6g==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 9F4C1A190E; Mon, 25 Mar 2024 14:16:15 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, mtgvenue@ietf.org
In-reply-to: <ZgCdcWGzgESGxj8v@faui48e.informatik.uni-erlangen.de>
References: <ZgCdcWGzgESGxj8v@faui48e.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Sun, 24 Mar 2024 22:38:57 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 25 Mar 2024 14:16:15 +1000
Message-ID: <383149.1711340175@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/fMdGWA5eLBxgTyvYDpxoSxMgLHo>
Subject: Re: [Mtgvenue] Was Brisbane a success to be repeated ?
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for email discussion of the IETF meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2024 04:16:27 -0000

Toerless Eckert <tte@cs.fau.de> wrote:
    > Sorry if subject question was asked and answered elswhere/earlier, please
    > provide pointers to summary thereof. If not:

    > Who will atually determine if Brisbane was a success to be repeted, and if so how ?

LLC+IESG.

    > Btw: I very much enjoyed Brisbane, but i was privileged in having to fly in only
    > from a location (SFO) that had a direct connection of <= 14 hours, whereas colleagues
    > from further east in the Americas and of course in Europe did report total travel
    > times even in excess of 30 hours. And i also managed to attach vacations to make
    > the travel very much worthwhile. And i do collaborate a lot with folks from east asia,
    > who of course also had a good presence.

I travelled for 38 hours.
That included some dumb layovers in Toronto and a really long in Vancouver,
probably as a result of the Dreamliner incident that Air NZ had two weeks
ago.
The flight from Toronto to Vancouver was actually the least pleasant of the
three.

    > That's especially why i would like to understand best how much effort the IETF puts into
    > deciding for this type of locations and especially how it will justify it to those for
    > whom it was inacceptable due to these travel issues.

Endless discussion.

I think that the right people to ask are the asians.
Was the trip from Tokyo or Nanjing or India significant more pleasant for you
than when we for instance, meet in Prague or Philadelpha/Montreal?

Clearly, it is unpleasant for Europeans and east-coastians to get to
Australia (or Bangkok).  But, it's also unpleasant for Australians to get to
Montreal.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*