Re: IETF 107 Vancouver In-Person Meeting Cancelled

Kyle Rose <> Tue, 10 March 2020 19:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D111B3A099A for <>; Tue, 10 Mar 2020 12:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id thkevsWberAH for <>; Tue, 10 Mar 2020 12:26:06 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::c2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9AD793A0954 for <>; Tue, 10 Mar 2020 12:26:06 -0700 (PDT)
Received: by with SMTP id x5so13907946ywb.13 for <>; Tue, 10 Mar 2020 12:26:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kgYWKQq8+BEmBCgPmMYiwBM9TdBo+fKIxd9QLFFhVG0=; b=CpYN8IgaBir3IH+bEUBx4/PEp1FcIlUVjmO+aZQvlwH40JjfJUHmptqoXAauPXQLmy KzipFuFIwsts+noucgo9qQYa90xkRrPsSlN2Di6Fzl1ASqNLQAZ63r9uiDEexOwU3at9 eecrbMKyInHq2zF9h9jWbbPdreVQPWeqfiMtY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kgYWKQq8+BEmBCgPmMYiwBM9TdBo+fKIxd9QLFFhVG0=; b=t8QFEUIEmNOk+mqDt0q7OJeG0Cd76T0lSFmoCKQ7La7lRwwRYclPuJMlsBUAMEaJ19 /r5QDz78N7tniOpiEkeXRcSBa4USvPdHi5WEyqGmMCepBvNt2A4AFFeoNqhLRPcW1D4q c0U8RM1FHoKz4VEUJuKOJs717DHXjSXxD6YNwMzvOa3Bcp1UovgZhinoexo5nAmBYNzQ WV6P7Qnad3YYOANQUkhVVC0CPJO/3Rjh+KxhDVqHf4MwEDm+PPFGtCUsS73NECkhespI O0LNaj1IrJiMd/0EJEVguEkjCMKOQWvhnTBzgXUKsZL9TDJlZvtZrxcXtgotSnxIBnz3 UAXA==
X-Gm-Message-State: ANhLgQ0ZLYsaQXd85mCY1pY82rY4xl6zRP8aD4zIdopSV7u/Ml91BQZQ RcdvkpH7CCCGHQaKZ/9voKzkkffkliFwaF0V0caaSjnu
X-Google-Smtp-Source: =?utf-8?q?ADFU+vtToVA+IukBSegUrRDk8cFD2Jka/obKK2cJa7qB?= =?utf-8?q?nk3EnF5b5Fa1T0e6Ahxu7QdnsIumvqONKb/p78F5Z2f9tyI=3D?=
X-Received: by 2002:a05:6902:702:: with SMTP id k2mr17551235ybt.127.1583868364305; Tue, 10 Mar 2020 12:26:04 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Kyle Rose <>
Date: Tue, 10 Mar 2020 15:25:53 -0400
Message-ID: <>
Subject: Re: IETF 107 Vancouver In-Person Meeting Cancelled
Cc: IETF Discussion Mailing List <>
Content-Type: multipart/alternative; boundary="00000000000039d31505a085172f"
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: Tue, 10 Mar 2020 19:26:15 -0000

Trimming follow-ups.

Can we contain this shitstorm to a single thread on ietf@ so I can mute it
and not have to listen to everyone's sob story?

On Tue, Mar 10, 2020 at 3:15 PM JORDI PALET MARTINEZ <jordi.palet=> wrote:

> I don't think this is right.
> Not having an official ban from the Canada authorities makes impossible to
> get a refund for:
> 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.