[Rats] FW: IETF 107 Vancouver In-Person Meeting Cancelled

"Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com> Tue, 10 March 2020 22:48 UTC

Return-Path: <ncamwing@cisco.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98FF3A07A3; Tue, 10 Mar 2020 15:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=e9u1rvYi; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cisco.onmicrosoft.com header.b=LFDZKJzH
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 QlS8iOaB6DRN; Tue, 10 Mar 2020 15:48:05 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E72453A07A5; Tue, 10 Mar 2020 15:48:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27016; q=dns/txt; s=iport; t=1583880484; x=1585090084; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=U1tHkdBSlXBs1e6dGE5mnYi6mEC/Vk14c2J7OesQvoY=; b=e9u1rvYiKFc6rodjlMe9xWUG9g8FmYDqfXu+OCxbiPdvyVIrDMEQNUp7 1S2q1+l3EAhclb33wcijQhAkgRu8C8xjC4nN/qt/CUf7PilSI7Ro+oGSB EWAqeJ/FpzefCi+uH5KFV07lzcEIP9NUx/ol48n/qkYBTNUyrgm+dxF5j I=;
IronPort-PHdr: 9a23:FzB2HR3lrG1jSQ1ssmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQD0byKeHraSMSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALEgDyF2he/40NJK1gBoQVJCwFbFggBAsqhBWDRQOKcU6VcoQ0gUKBEANUCQEBAQwBARgLCgIEAQGEQwIXgW8kOBMCAwEBCwEBBQEBAQIBBQRthVYMhWQCAQMBARARHQEBJAgMDwIBCEICAgIlCxsBBgMCBAESDgYIBoMEAYJKAy4BDp5cAoE5iGJ1gTKCfwEBBYEvAYEUgkYYggUHAwaBOIwsGoIAgREnIIJNPoEEgWABAQOBLQELBwERgyEygiyCR4FEiUcQNwiBSIEChXJyGA2BNoZwkBMKgjyDcYNjigCFFh2CSjGHc5BMjnmBTocvjkGEFAIEAgQFAg4BAQWBaSJncXAVOyoBgg0BATJQGA1YjVEMC4NQhRSFQAF0D4EaixQEgj8BAQ
X-IronPort-AV: E=Sophos;i="5.70,538,1574121600"; d="scan'208";a="724191684"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Mar 2020 22:48:03 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 02AMm3dM003603 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 Mar 2020 22:48:03 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Mar 2020 17:48:03 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Mar 2020 18:48:02 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 10 Mar 2020 17:48:02 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KtxTpKDrd8YS87FzyKNNJa1XZPcryjFmx7q4eYy1oe9qMAPU3yaSJlTA2B6nZkNPTjb4xXQ+5pyCOmhUyrbHTJwp3PnDqRaqj8QG8Gk97h4iySa6Uct7S+Lb1UVU3yjtIOyJGxJctdJBKmGM92A3VSLGjz6nG1gVhp6TxKj4MVrivzAcmgz0jERZFMNrEMoQKOhmTtvw1p8e+KGLKSwzHotztJPcnDMU5s7Z8cMiBIuVTHgw8XmGDipaWCV3m9iEr780N6uxtDqAhUcLB7UV+q/lZJG7/+rbCm1dtYQgEcYdcyYsrnoUSYfsH/QFCrqKDVpuHsSYsDrCV8CfC77TUg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=degozZ64aaC71rHKExJO0SZB7qrPuLdEwU13O3XxhwU=; b=FyMpF7mfU9p5CjSeGVstUEODN72vUwwGRkF6bmRsy3T8qpmwNKM9UYAbIOJ31kFxiB+OszWT/ngWOdQo0rN0qhjzVVXyqgegCXTiDFkr/QTHPlCIVrPiOZLuhs9efobU3Z/YEVDUyJcgTU03QueKATPRnUubhSMOZM+lWWFM0hamHIkMVgyj4bR+yZI+07I4dE3ip64y+AGvp0Uff50ZqExNU9kVXwJ8tRz0fabLIqgSN3CiH7pHhUI/45hhBb8ClzT9sVKCOteiflJbYKm4rXB/iNXnMjDFyrpfM0r+K6MNgmYB4N1RQ1e9Z8cFssQnCb0h2gvnOpc7zoYBWb0XXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=degozZ64aaC71rHKExJO0SZB7qrPuLdEwU13O3XxhwU=; b=LFDZKJzH0M/ioYW1BrKvWZwqWnNU9SpmpNGK7rXpYj+UL9MvkbEGWUSUEA/ErXE7iO/iA7GzF8ZoXVQ0MmR1RLK1w0TiaSU0+0Y8j7vyX4iEkbuatzeTM46ghcYEta4ca6gWsrp3CtBnVRICP7gozfbgxsLJCMknsgAUxjKB09Q=
Received: from BY5PR11MB4070.namprd11.prod.outlook.com (2603:10b6:a03:181::16) by BY5PR11MB4242.namprd11.prod.outlook.com (2603:10b6:a03:1c1::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.17; Tue, 10 Mar 2020 22:48:01 +0000
Received: from BY5PR11MB4070.namprd11.prod.outlook.com ([fe80::852d:fab4:18c1:72d2]) by BY5PR11MB4070.namprd11.prod.outlook.com ([fe80::852d:fab4:18c1:72d2%7]) with mapi id 15.20.2793.013; Tue, 10 Mar 2020 22:48:01 +0000
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: "teep@ietf.org" <teep@ietf.org>, "rats@ietf.org" <rats@ietf.org>
Thread-Topic: IETF 107 Vancouver In-Person Meeting Cancelled
Thread-Index: AQHV9w+q0HAch6dk4kKL4K6Vd2lV5qhB+G0A
Date: Tue, 10 Mar 2020 22:48:01 +0000
Message-ID: <485FFD12-151A-40BB-8CBA-7F26DBB9F444@cisco.com>
References: <158386742797.16091.1025684270011519738@ietfa.amsl.com>
In-Reply-To: <158386742797.16091.1025684270011519738@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.13.200210
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ncamwing@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::18a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d03d3d53-01f8-42fb-0c6d-08d7c5451644
x-ms-traffictypediagnostic: BY5PR11MB4242:
x-microsoft-antispam-prvs: <BY5PR11MB4242E8392BD5D0F98792AE24D6FF0@BY5PR11MB4242.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 033857D0BD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(39860400002)(376002)(136003)(396003)(189003)(199004)(478600001)(316002)(66574012)(110136005)(66476007)(66446008)(64756008)(33656002)(6506007)(71200400001)(66556008)(66616009)(86362001)(6512007)(5660300002)(66946007)(76116006)(2616005)(2906002)(450100002)(186003)(6486002)(36756003)(8936002)(81166006)(8676002)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4242; H:BY5PR11MB4070.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fIAkYp1ToQWkcIE4yn9lBeYvNYs7vwy8lF60PBEoY/J5Yg1imp67s4Pq3YFEXge9oJThSb3ilz+84W3goTeAJEKIZ6IuIDFLQUn46nIf+AAszvdgPkb9Cw5B2pztBqfyP3BjXdTiA0UOkw9fdXhcQ4v0XBTOBlIJB+Mld2VPawJiUojrv6HRZLc7/QFLemzFRcqgxx7gsdF1BGM6rGeCxzBvgsjYJvjMBXvosnWPiiIKWeFTqKXEwFUPjK4+vve8wjYe4V78Fh0G9gPmbAGNsq+KVCoWB0aVtDffigKlJjxD9O3GYlC6lCXhr1cJBmVZTXfZu/rncgnMxHARgm/3Ue5k0aTxsWoVHWfnguosTtDP3t3c7zVS4ACwAWbrkLxPgi1fcej83qYEpaqmxOurCpNlPyWvKdwR5X+WDKbeOlzXXVogq/aNwZG9Mu0/vBJ2E7TbBlahfzhVdwuqJstwqE735UUjYtrRsDDqxQjDwb/ezfXp0QP+WI3QotqzzwAZ19CTCvdG6EcMGK36HcOYsA==
x-ms-exchange-antispam-messagedata: cIB/wfS9Fw4S6OwOsfzOAywbAgedX8NZRrW/O2B4Xr53VbFPWwJPYegSBeoQi0vi4O8yfpAKk7TX5hNLTZ2aTWsdWRJRx8Q8bQ7C2ST2Bxgz2xpqfGpD38SthzdwanBxcaPooj9TkfdB/nfAbhevTMr9Mqpckei9Lr7fhlew2W4=
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_002_485FFD12151A40BB8CBA7F26DBB9F444ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d03d3d53-01f8-42fb-0c6d-08d7c5451644
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Mar 2020 22:48:01.1519 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: lILsDTLeSemGW/bOuzdUhh2MBxYqLsGVs2M2zjNfUzY9rCVvbESu3OqZmlWrVNg1srXVqihhN2aWkfMaQN9EsQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4242
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/Hc25vI9OthHDcAtdlUspEmOaeOY>
Subject: [Rats] FW: IETF 107 Vancouver In-Person Meeting Cancelled
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 22:48:10 -0000

FYI,
In case there are those that do not follow the ietf@ietf.org mailer.  There is also a follow-up on cancellation policies which I've attached in this email too.

The chairs are awaiting further input, but be assured that virtual meetings will be scheduled sometime in the not too distant timeframe.

Warm regards,
	Nancy

On 3/10/20, 12:11 PM, "ietf on behalf of The IESG" <ietf-bounces@ietf.org on behalf of iesg@ietf.org> wrote:

    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 <https://datatracker.ietf.org/submit/>.
    
    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
    
    

--- Begin Message ---
Following the announcement by the IESG and the IRTF Chair that the in-person IETF 107 Vancouver meeting is being cancelled, this is an update on various financial and administrative details.

1. Meeting registration fees:

- Starting now we will be refunding any cancellation fee that we have retained for the cancellation of an in-person registration.

- Starting in 48 hours time we will begin to refund in full all registration fees for those registered to participate in-person.  

- Unfortunately we are not able to roll forward the registration fee to IETF 108 Madrid for a number of administrative and financial reasons, most notably the different taxation requirements between Canada and Spain.

- We are aware that some people do not want their registrations fees refunded and have asked us to convert it to a donation, which we will do.  Anyone else who prefers this option please let us know at ietf-registrar@ietf.org before the refund process starts.

- The delay of 48 hours is to give us time to see if we can process all refunds  automatically, but if that is not possible then each registration will be processed manually by the Secretariat team and this will take some time. 

2. Hotel bookings in contracted hotels:

- If you are booked at the Hyatt, Metropolitan or Sutton Place hotels then you can cancel with 72 hours notice and no cancellation fee.

- If you are booked at the Fairmont hotel and have paid the one-night non-refundable deposit, they have informed us that they will refund this deposit.  

- If you are booked at the Coast Coal Harbour Hotel then we understand that they retain the right to keep the deposit.  We are working with them to see if they will consider waiving that given the extraordinary circumstances.

- Contact information for each of the IETF hotels is available on the IETF 107 Vancouver hotel webpage [1]. Should you experience any difficulty cancelling your reservation, please contact us at ietf-registrar@ietf.org for assistance. 

3. Financial impact on the LLC:

- We are discussing with the venue the possibility of rescheduling the meeting to a later year.  Doing this may mean back-to-back North American meetings.

- We particularly want to thank the meeting host, Huawei, for supporting us fully in these difficult circumstances. 

- Our sponsors have been contacted and a number have already responded that they wish to sponsor the virtual meeting or roll forward their sponsorship to the next in-person meeting, for which we want to express our thanks. 

- We have comprehensive insurance and are exploring what claims we can make.

- We expect that we will still need to dip into reserves to cover substantial unavoidable costs but we do not anticipate any significant financial impact from doing so.


If you have any questions or comments then please feel free to contact me directly.  

[1] https://www.ietf.org/how/meetings/107/hotel/

-- 
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

--- End Message ---