Re: [107all] Update on IETF 107 Vancouver and COVID-19
"Ramesh Sivakolundu (sramesh)" <sramesh@cisco.com> Wed, 04 March 2020 21:38 UTC
Return-Path: <sramesh@cisco.com>
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 556FA3A098A; Wed, 4 Mar 2020 13:38:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 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, 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=Pj65z0RD; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=WebOiych
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 uUw-8nBXip9A; Wed, 4 Mar 2020 13:38:16 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F443A098D; Wed, 4 Mar 2020 13:38:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5136; q=dns/txt; s=iport; t=1583357895; x=1584567495; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=p7sQKUj5Rw6wIF0cWe9prRElnVDoTHLDTRDSdIvkUrM=; b=Pj65z0RD8g1rtD5dX0BlHH4YFfElbtM6CIZBGQcW5NKIthwfwB6HTFRn DU180qAdRs0G5OGmAWtEqk+5S+CcDQguCZqulV+Nff79dB8tzOTacV5cf BLFEA/x9bn2ocQywODs8HjbMdDg5KAeQywWFY64y/sn2xm53vg3CLs+Zi I=;
IronPort-PHdr: 9a23:eqpZAxKFNOkqA9WgTdmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFbhJfvndCwSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CACwBEH2Be/4MNJK1fBx0BAQEJAREFBQGBe4FUJAUnBWxYIAQLKgqEC4NGA4ppTpVyhDSCUgNUCQEBAQwBARgPBgIEAQGDfkUCF4FqJDgTAgMBAQsBAQUBAQECAQUEbYVWDIVkAgEDAQEQEREMAQEkAgYMDwIBCBoCJgICAiULFRACBAESIoMEAYJKAy4BDqJiAoE5iGJ1gTKBO4FEAQEFgS8BAwWBDIJYGIIMAwaBDiqMGA8aggCBEScggh8uPoEEgWABAQEBGoE0FYMRMoIsjU0FgxSGLTWISZAPCoI8lBuCSxyCSYgfkEmOcoEzGphCgTwCBAIEBQIOAQEFgWkigVhwFTsqAYINAQEyUBgNjh0YgQ8BCYFuVIJfgjWFQAF0AoEnilwEJ4EIATBfAQE
X-IronPort-AV: E=Sophos;i="5.70,515,1574121600"; d="scan'208";a="728649551"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Mar 2020 21:38:14 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 024LcEef003138 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Mar 2020 21:38:14 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Mar 2020 15:38:14 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Mar 2020 16:38:13 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 4 Mar 2020 16:38:13 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Sz+sKIH4d3bzFCQhbYkcxTdwG0Q58S1SK2vZIigB3UQfGk8eULBYYPgIY1tlKzpcbK7w1PDOk9P56thUTXy5vQ4QElaLznvMV6nmuCL0NA4IBcZrdP8R9Ji1sbHJn+veIoC3V7wdeIYtTSf+oEqFK3lx2sF60981PFQUyUaB6RubJbwzs560KYslom1kwCeJH2H7ybAKuVPDbz6k9dSwUCXTCfso2/U1qyGMLF6vxqNsNZSGJrEPAvjzzdmFcpGyAtFIfSCN9hH34wFUNiL7lkvNJPWNniU2y9xqX12pRfNI10UZWWU/6D02GPwLIEg43myydThGVE0hLo3mDmPC2w==
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=p7sQKUj5Rw6wIF0cWe9prRElnVDoTHLDTRDSdIvkUrM=; b=Lck1UqIJpv2KuYrnl4yGMoDBSFGbrrfDsE08t7oGLfZqMJBVILkeJ28W02OxsuW0Lrz9CRKPyVquE2mmJBfjhffjkzm22Hq4QaziRIoxle6ZAyEMJo+mpTKB/TLAMPlK0m2WvIZ/1UjYEPGUfwmwCsaCGiwne1T7MOB5V5vp9XT8ZFaxFKwYQlgI6/I9hHSf9DAzw1vADKT64Pk06/cN530+U2eAV6YJKs43qt+IY7Tuj1lvze3xG52JZ11mcgkjtQyKvAL7mvE6ugJ+ItHMKULW3skWc0S8YfOIXgwV9wLRcUggUveO4hJsG/D1ZqbCeBffs2JrkACpF3JN0sUCJg==
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=p7sQKUj5Rw6wIF0cWe9prRElnVDoTHLDTRDSdIvkUrM=; b=WebOiychlVj3Uw2BImAchu69u23QSXcj1iFji6Cxp3NBb2NwbgcU/IQ6QaZVqkgAu6A7fnlP3qj9LA7rHbZgpZkG4OHe83LlaYVtDjow34f8cvHFyyWlPDdseZKcDD4PxdIE1XmN2ka9Za8UgFGfkth74Q/gTGy/3nXc/L4lCNw=
Received: from BYAPR11MB2792.namprd11.prod.outlook.com (2603:10b6:a02:c3::14) by BYAPR11MB3079.namprd11.prod.outlook.com (2603:10b6:a03:92::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.19; Wed, 4 Mar 2020 21:38:12 +0000
Received: from BYAPR11MB2792.namprd11.prod.outlook.com ([fe80::19b7:cad8:eb31:12b7]) by BYAPR11MB2792.namprd11.prod.outlook.com ([fe80::19b7:cad8:eb31:12b7%3]) with mapi id 15.20.2772.019; Wed, 4 Mar 2020 21:38:12 +0000
From: "Ramesh Sivakolundu (sramesh)" <sramesh@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Subject: Re: [107all] Update on IETF 107 Vancouver and COVID-19
Thread-Topic: [107all] Update on IETF 107 Vancouver and COVID-19
Thread-Index: AQHV8l45EwPIluh2R0KEIIGsfdcGtag4b46A
Date: Wed, 04 Mar 2020 21:38:12 +0000
Message-ID: <D4FDE701-CE29-44BE-877A-B45266FEFF08@cisco.com>
References: <158335136585.29295.1109218817393181187@ietfa.amsl.com>
In-Reply-To: <158335136585.29295.1109218817393181187@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sramesh@cisco.com;
x-originating-ip: [128.107.241.168]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 53aade35-e2e4-4dba-d5cf-08d7c08456f5
x-ms-traffictypediagnostic: BYAPR11MB3079:
x-microsoft-antispam-prvs: <BYAPR11MB30795526B40D3B215927CB55B3E50@BYAPR11MB3079.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0332AACBC3
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(346002)(39860400002)(376002)(396003)(199004)(189003)(86362001)(316002)(6512007)(71200400001)(478600001)(66946007)(66446008)(2616005)(110136005)(76116006)(66556008)(5660300002)(64756008)(966005)(26005)(66476007)(186003)(450100002)(36756003)(8676002)(33656002)(81166006)(81156014)(8936002)(6506007)(15650500001)(66574012)(2906002)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3079; H:BYAPR11MB2792.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: 5/K33x/odtsodicyTF6QOXupTpYwMkQNojRYrrEe6cLk7JaK7GiDBDdhVD/iw3I4PC2wPwTk2GIUKJ/WsvsLUTqcGEuDAZCdNCFtr/fPKSueTch8QlHUvU8k00JtmK8TMOJl/TmSHa7fnSLHQSrKj4wHLYuU1V6hHXv3vA0CiHlvFW+nNQlatqSlWL8r90ekT+I3XDc9UCZuSV3Xd/tM+87McpEfSf2CMDAP3HYiJ4GR/xLBONijcBtr0+zsnyT+SOzXzT4Aqr8RDndSLjoNt39qQcZcPCQbKH36auVGESMmTJPXl57jGdTNcg0bmL9+GSv1Lga6BNO1WdpBqSF2oBvZ5bbKASJHehqFhTopPJQWkoS3HXwk06XHTPgO1n9hbg/90UPJuRq06Rn11ee2xuS7xZ+kThDkgcPaf8N48/wUXAeZ5DVOips5K9ZzenkSZXQU4bUPIqUjNPdXFwhqamSbGs8/TzVq27hQeSKoVEbXJYeSquToPXza1oGB1FhlFKvr83tLmY632hmp7Qp9ZQ==
x-ms-exchange-antispam-messagedata: qlXN3Lvop0OuTjjwHfS1tobThXtjK2CrVWjfT7V35t8kzfM/SiKQmYAzDme6HZalnhybEE25A09WIfGf1i0Vo2LJg6WKnL7395emZSxAUqiTuDxPrRAYNYr0vwBn8DlUTLZyeyD4e+Z1OHgE3XdvMA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <C2E52B21A32A5A408F5C3CBB314930FA@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 53aade35-e2e4-4dba-d5cf-08d7c08456f5
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2020 21:38:12.1863 (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: XiCS5Ea8Nu02tJHixtv3peIv6ssu6ZOTX2c/fI4EksDOeFB6y9S1RJHg64p4LkAssCXXppNvUcZeMmowmTkXDQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3079
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0zdFOo7tWzdPpuNpcUz8byIdW94>
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: Wed, 04 Mar 2020 21:38:19 -0000
What is the procedure to cancel a registration. As per Cisco Travel Policy, cross-border international travel has been suspended till Apr 15th, 2020. Thanks Regards, -Ramesh On 3/4/20, 11:50 AM, "107all on behalf of IETF Executive Director" <107all-bounces@ietf.org on behalf of exec-director@ietf.org> wrote: This is a further update on IETF 107 Vancouver and the ongoing situation with COVID-19 (Coronavirus). It is still our intention to go ahead with IETF 107 Vancouver as the public health advice remains that we do not need to cancel conferences in Vancouver or avoid travel to Vancouver. The Public Health Agency of Canada (PHAC) continues to classify the risk of infection in Canada as low [1] and the World Health Organization (WHO) continues to recommend against travel restrictions [2]. As shared earlier, special measures are being put into place for IETF 107 in Vancouver following public health recommendations for meetings of this nature [3]. We continue to monitor the situation and will respond quickly if the public health advice changes. While it is clear that the situation is deteriorating, the public health advice from the WHO, which is very consistent and evidence-based, is that local containment of outbreaks is both feasible and demonstrated to work. To hear more about the evidence-based guidance being provided by the WHO we recommend watching a WHO press briefing [4] or reading their daily situation reports [5]. We are aware that more companies have imposed travel restrictions and in some cases those are dependent on who else will be attending the conference. However, we will not be imposing travel restrictions on IETF participants from specific countries or regions as it is for the Canadian government to decide who can enter their country. The current PHAC advisory page for visitors [6] is that those arriving from Hubei province of China or from Iran should self-isolate for 14 days on arrival and monitor their health. That advisory may be updated at any time and so we advise anyone travelling from a country with an infection cluster to check that page before travel. We continue to receive new registrations every day but those are now being offset by cancellations and the number of registered in-person participants is hovering at around 625 [7] with over 200 registered remote participants. The Internet Engineering Steering Group (IESG) and IETF Administration LLC continue to monitor the situation and the IESG is currently seeking input from working group and research group chairs to understand the extent of expected session cancellations. If we are required to cancel then the IESG is considering options for virtual meeting support, which it will report on in due course. Please feel free to contact me directly if you have any questions or comments. [1] https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection.html [2] https://www.who.int/ith/2019-nCoV_advice_for_international_traffic-rev/en/ [2] https://www.ietf.org/how/meetings/107/ietf107-health-measures/ [3] https://www.youtube.com/watch?v=SAo9Nooi69E (about 55 minutes in) [4] https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports/ [5] https://www.canada.ca/en/public-health/services/diseases/2019-novel-coronavirus-infection/latest-travel-health-advice.html [6] https://www.ietf.org/registration/ietf107/attendance.py -- Jay Daley IETF Executive Director exec-director@ietf.org -- 107all mailing list 107all@ietf.org https://www.ietf.org/mailman/listinfo/107all
- Re: [107all] Update on IETF 107 Vancouver and COV… Ramesh Sivakolundu (sramesh)
- Re: [107all] Update on IETF 107 Vancouver and COV… Jay Daley
- Re: [107all] Update on IETF 107 Vancouver and COV… Robert Raszuk
- Re: [107all] Update on IETF 107 Vancouver and COV… Warren Kumari
- Re: [107all] Update on IETF 107 Vancouver and COV… Marc Petit-Huguenin
- Re: [107all] Update on IETF 107 Vancouver and COV… Carlos M. Martinez
- Re: [107all] Update on IETF 107 Vancouver and COV… Paul Wouters
- Re: [107all] Update on IETF 107 Vancouver and COV… Spencer Dawkins at IETF
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Alessandro Amirante
- Re: [107all] Update on IETF 107 Vancouver and COV… Stewart Bryant
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Alessandro Amirante
- Re: [107all] Update on IETF 107 Vancouver and COV… JORDI PALET MARTINEZ
- Re: [107all] Update on IETF 107 Vancouver and COV… Meetecho IETF support
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [107all] Update on IETF 107 Vancouver and COV… Alvaro Retana
- Re: [107all] Update on IETF 107 Vancouver and COV… Carsten Bormann
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Jared Mauch
- Re: [107all] Update on IETF 107 Vancouver and COV… Vittorio Bertola
- Re: [107all] Update on IETF 107 Vancouver and COV… Jared Mauch
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Christer Holmberg
- Re: [107all] Update on IETF 107 Vancouver and COV… Carsten Bormann
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- RE: [107all] Update on IETF 107 Vancouver and COV… Ron Bonica
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- RE: [107all] Update on IETF 107 Vancouver and COV… Ackermann, Michael
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexa Morris
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexandre Petrescu
- Re: [Manycouches] [107all] Update on IETF 107 Van… Phillip Hallam-Baker
- Re: [Manycouches] [107all] Update on IETF 107 Van… Mary B
- Re: [107all] Update on IETF 107 Vancouver and COV… Eliot Lear
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Phillip Hallam-Baker
- Re: [107all] Update on IETF 107 Vancouver and COV… Christian
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Touch
- Re: [107all] Update on IETF 107 Vancouver and COV… Lou Berger
- Re: [107all] Update on IETF 107 Vancouver and COV… Alexander Mayrhofer
- Re: [107all] Update on IETF 107 Vancouver and COV… Stephen Farrell
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Eliot Lear
- Re: [107all] Update on IETF 107 Vancouver and COV… John C Klensin
- Re: [107all] Update on IETF 107 Vancouver and COV… Joseph Potvin
- Re: [107all] Update on IETF 107 Vancouver and COV… Toerless Eckert