Re: IETF 107 Vancouver In-Person Meeting Cancelled

Alexandre Petrescu <> Wed, 11 March 2020 10:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9305D3A163E for <>; Wed, 11 Mar 2020 03:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rMqGtSQ14t3H for <>; Wed, 11 Mar 2020 03:11:03 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8C60F3A1639 for <>; Wed, 11 Mar 2020 03:11:03 -0700 (PDT)
Received: from ( []) by (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 02BAB1Zt033182 for <>; Wed, 11 Mar 2020 11:11:01 +0100
Received: from (localhost []) by localhost (Postfix) with SMTP id 839E920533D for <>; Wed, 11 Mar 2020 11:11:01 +0100 (CET)
Received: from ( []) by (Postfix) with ESMTP id 77E68205328 for <>; Wed, 11 Mar 2020 11:11:01 +0100 (CET)
Received: from [] ( []) by (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 02BAB1l5031128 for <>; Wed, 11 Mar 2020 11:11:01 +0100
Subject: Re: IETF 107 Vancouver In-Person Meeting Cancelled
References: <> <>
From: Alexandre Petrescu <>
Message-ID: <>
Date: Wed, 11 Mar 2020 11:11:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Mar 2020 10:11:06 -0000

Le 10/03/2020 à 20:14, JORDI PALET MARTINEZ a écrit :
> I don't think this is right.
> Not having an official ban from the Canada authorities makes
> impossible to get a refund for:

I suspect Canada authority has no ban on travel because WHO (World
Health Organisation, and 'OMS' in French) has not advised so.

The March 7th advice from WHO with respect to travel can be digged out
of the web site.  A phrase says "We must stop, contain, control, delay
and reduce the impact of this virus at every opportunity. Every person
has the capacity to contribute, to protect themselves, to protect
others, whether in the home, the community, the healthcare system, the
workplace or the transport system."

As I read it, they put the responsibility on individuals, who would in
turn expect decision responsibility from them.  Could be a loop.

A possible way to scape from the loop would be if Canada told WHO they
need a decision.  Canada could need a decision because there are some
problems.  Some of the problems relate to individuals and small and
medium enterprise being hit with risk of loosing money, effectively
another way to 'kill' SMEs.

That matter is as urgent as the other medical needs, because if not
dealt with in time it might bite back badly.

That is a matter between Canada and WHO.

Canada is a representative organisation, their leaders represent
majorities.  A Canadian should contact Canada.  I suppose only Canadians
could contact Canada gov't.  I suppose travellers to Canada are not
Canadians.  This is a problem.

A way to escape this problem might be a need to contact directly WHO,
and skip Canada.

The press contact at WHO about this matter is:
Tarik Jasarevic <>

If you make contact, I am ready to co-sign, because I think I share the
feeling of your IETF situation as you present it.


> 1) Flight 2) Hotel
> So, for those that have paid that from their own pocket, in advance,
> to make it cheaper, is the IETF insurance going to cover that?
> Regards, Jordi @jordipalet
> El 10/3/20 20:11, "IETF-Announce en nombre de The IESG"
> < en nombre de>
> escribió:
> The IESG and the IRTF Chair have decided to cancel the in-person IETF
> 107 Vancouver meeting. This decision is based on input we gathered
> from Working Group (WG) and Research Group (RG) chairs about our
> ability to hold productive WG and RG sessions at IETF 107. Our
> assessment of this feedback is that a majority of sessions would not
> be viable if we were to hold the in-person IETF meeting. On this
> basis, we believe we cannot hold an effective in-person meeting.
> As a result of this cancellation, the in-person Hackathon, Code
> Sprint, all other in-person events planned for the weekend of March
> 21-22, the chairs training scheduled for March 20, and all other
> in-person sessions during the week are cancelled.
> The IESG is working on an alternative all-virtual agenda for the week
> of March 21-27 with a limited schedule adapted to accommodate the
> time zones of as many participants as possible. We are also planning
> to support an increased volume of virtual interim meetings during the
> weeks that follow. We will send another update to the community soon
> with more information about these plans. The Hackathon organizers are
> also considering plans for virtual Hackathon support.
> We have re-opened Internet-Draft submissions, which had been closed
> on March 9 in anticipation of the in-person meeting. Internet-Drafts
> may be submitted at <>.
> A separate announcement from the IETF Executive Director will follow
> with details about registration cancellations and refunds.
> These are unusual times given the circumstances created by the spread
> of COVID-19.  We hope that everyone remains safe and healthy.
> Regards, The IESG and the IRTF Chair
> _______________________________________________ IETF-Announce mailing
> list 
> ********************************************** IPv4 is over Are you
> ready for the new Internet ? The IPv6
> Company
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the exclusive
> use of the individual(s) named above and further non-explicilty
> authorized disclosure, copying, distribution or use of the contents
> of this information, even if partially, including attached files, is
> strictly prohibited and will be considered a criminal offense. If you
> are not the intended recipient be aware that any disclosure, copying,
> distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited, will be
> considered a criminal offense, so you must reply to the original
> sender to inform about this communication and delete it.