Re: IETF 107 and Corona Virus?

Jay Daley <jay@ietf.org> Sun, 16 February 2020 20:15 UTC

Return-Path: <jay@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F106312002E for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2020 12:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wg6eeHIzV9dS; Sun, 16 Feb 2020 12:15:57 -0800 (PST)
Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 79AF912001B; Sun, 16 Feb 2020 12:15:56 -0800 (PST)
From: Jay Daley <jay@ietf.org>
Message-Id: <066A4043-1390-4895-A3F8-0D6849A9967F@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_212416A7-352D-49C6-B321-1E7AE07FB902"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: IETF 107 and Corona Virus?
Date: Mon, 17 Feb 2020 09:15:54 +1300
In-Reply-To: <26EBAC6A-46CA-4DFE-B198-F3EB0AA49AD9@me.com>
Cc: IETF Discussion <ietf@ietf.org>
To: Ole Jacobsen <olejacobsen@me.com>
References: <BD3C4818-43FD-47F4-A705-56AE11E55176@ietf.org> <26EBAC6A-46CA-4DFE-B198-F3EB0AA49AD9@me.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ML6QHPbNMXKzZCSoQ_0b8Y3KOYU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Feb 2020 20:15:59 -0000

Ole

> On 17/02/2020, at 9:07 AM, Ole Jacobsen <olejacobsen@me.com> wrote:
> 
> Just to add one aspect of this: 
> 
> Several high-profile companies have imposed blanket travel restrictions on their staff. I am currently at APRICOT in Melbourne, Australia, and a regular conference speaker from Amsterdam, The Netherlands is unable to attend regardless of which route he takes to get here. Neither Australia nor The Netherlands are considered high-risk for this virus. I would expect that a refund for reg fees would apply for such cases too if a blanket travel ban were to include Canada.
> 
> Right?

Yes.  A blanket travel ban is a government imposed travel restriction and so we will provide a full refund in that instance.  To confirm, the list of possible government imposed travel restrictions now includes (but is not limited to):

	- denial of exit
	- denial of entry
	- diversion
	- repatriation
	- isolation
	- quarantine.
	- blanket travel bans

Jay

> 
> Ole J. Jacobsen
> Editor & Publisher
> The Internet Protocol Journal
> Cell: +1 415 370-4628
> T-Mobile: +1 415 889-9821
> Docomo: +81 90 3337 9311‬
> http://protocoljournal.org
> 
> Sent from my iPhone
> 
>> On 14 Feb 2020, at 14:57, Jay Daley <jay@ietf.org> wrote:
>> 
>> Just in case anyone is confused by this, the recently announced policy is for a full refund in the case of *any* government imposed travel restrictions that prevent someone attending the meeting, which may include, but are not limited to, denial of exit, denial of entry, diversion, repatriation, isolation and quarantine.
>> 
>> Jay
>> 
>> -- 
>> Jay Daley
>> IETF Executive Director
>> jay@ietf.org <mailto:jay@ietf.org>

-- 
Jay Daley
IETF Executive Director
jay@ietf.org
+64 21 678840