Re: IETF in July
Victor Kuarsingh <victor@jvknet.com> Mon, 23 March 2020 14:27 UTC
Return-Path: <victor@jvknet.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 344BC3A0862 for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 07:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jvknet-com.20150623.gappssmtp.com
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 5jA6IplWxm0Y for <ietf@ietfa.amsl.com>; Mon, 23 Mar 2020 07:27:08 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85BE73A0433 for <ietf@ietf.org>; Mon, 23 Mar 2020 07:27:08 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id d5so4965864wrn.2 for <ietf@ietf.org>; Mon, 23 Mar 2020 07:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+YHIez8KjkYbIcNb5reBIgBtdXFy7K65fSqFzlkRvNc=; b=a7VAjBhXPS2/AeyPIVQ941aGrwGDCf4bs2a36drIEfDKrO1+NKtSgbn/eHCNXgr+47 N/nECPcU0exrsqZWj/qgvB7nHeZgdZO8G/TdC86SfpA5VQzpsZs+0xuF4/WYVJZ8xzN+ KruevfuQT8ZrxFxhzvCAvzk1uwcjddXPDFQu6kVU2ERoDavYudrIwD99KlDAM0tXNIGN JVcMOWwLwVT45XqlOMT5uh/ZUceLocvz8v2J0sFLOtfF8CHZbgT2eO0NmJip5jM6Ty6v BmjIOEh+UrriCiM99CdO9Nh4GKHPaOwmoWUq7hkLw0iVL1DIbZO4JeAc8sLyHXsJDESR iRYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+YHIez8KjkYbIcNb5reBIgBtdXFy7K65fSqFzlkRvNc=; b=WLLCbGzsZOBpx8OVSOGLhcSuCih0qcEQv2jKfH1ACJH33ChrpAtLGL4nKz+e2go179 qLMRw+uj0N9iXe5AbZMERatGHQv3EhEcYpogkkImF0qxBUMHJab1DYlk9nhcUKEwCln/ 2Myup1O4+WxvtF/BiOUq1Mb950+Q85fpYgtsBcuVeMTGHpjXtre5W52HF16820887CRA 6LYPdUfmj5FDk0caGEo5KEb91eJSChzMJMMqL5cgOHQMR1Wh9atCXuI5ZzyBCXHZ44xL ubG95FjBNzb+1XCUsx7EEKmpqLyWwwWuEjzt/Au2xRGEHrGJjcLJ26izFDsyeyreBDbv u4ag==
X-Gm-Message-State: ANhLgQ3hFp5u3rf/VROwq1ogE6tsHG0WqF2dKWZ8OLncHqtnpUh1oU5P TxDCJBhEvD8/4+i1lvOa34ILdydCoiE0TdiSQWzFTlF8y5e67g==
X-Google-Smtp-Source: ADFU+vtIvYR7VOgIqRiaWpF6pGOOvuLlwGMGDCHIvFbYGxWLP+orMudaPCasgrajgRpfaKRbUqtpnrJ4qSI5kF4gtBY=
X-Received: by 2002:adf:f50d:: with SMTP id q13mr14114246wro.374.1584973626550; Mon, 23 Mar 2020 07:27:06 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR05MB63488A5D5D14D11CBF145CEBAEF50@DM6PR05MB6348.namprd05.prod.outlook.com> <2E3DFE67-85D0-4259-85D5-09FF9A262B48@tzi.org> <B28C7981-1AF4-4299-AAA0-4ABA667D81B4@consulintel.es> <CAOj+MMHROy2UA7YUdRrTM240nQY4ykbYHtFME87FPznNDMdcUQ@mail.gmail.com> <0B0BBC48-1504-4847-85B1-36700873D78E@consulintel.es> <5134FD38-F675-4E81-8C57-1EBCBE475705@tzi.org> <37205051-dab1-d59e-5fb2-fbcef327302b@nostrum.com>
In-Reply-To: <37205051-dab1-d59e-5fb2-fbcef327302b@nostrum.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Mon, 23 Mar 2020 10:26:55 -0400
Message-ID: <CAJc3aaMFdyYxeX_6bZCmOJ8q8KBaHYmV79N70O85dHZ3AWUcaA@mail.gmail.com>
Subject: Re: IETF in July
To: Adam Roach <adam@nostrum.com>
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fd3bb505a1866db7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P9DkVlLMuOK7vWTsdTc3Jc0xchs>
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: Mon, 23 Mar 2020 14:27:11 -0000
On Mon, Mar 23, 2020 at 10:12 Adam Roach <adam@nostrum.com> wrote: > On 3/23/2020 1:28 AM, Carsten Bormann wrote: > >> Actually, I’m more and more convinced that we can make it without the > need of canceling. > > For those who didn’t see yet that the light at the end of the tunnel is > the light of an oncoming train: > > > > The impending postponement of the Olympics (which would have been > starting the same week) should lay these thoughts to a final rest. > > > More to the point: what might plausibly change in the next four months > that would reduce the need to restrict movement? > Likely not much. As much as I want to be optimistic, I suspect the reality will be that the current situation will continue for much longer then we had hoped for and even if the primary issues resolve, there will be lingering impacts from the sudden ramp down of the services industry and commercial air travel. I also think that many supporting businesses will restrict their employees from travel based on health and safety policies. It’s up to leadership on timing related to a decision on forgoing an in-person meeting for IETF108, but I think preparing for a remote meeting is the prudent thing to do at this point. Worst case, we would then have a play book on how to do this in the future. Regards, Victor K > /a > >
- IETF in July Ron Bonica
- Re: IETF in July Jared Mauch
- Re: IETF in July Keith Moore
- Re: IETF in July Carsten Bormann
- Re: IETF in July Kathleen Moriarty
- Re: IETF in July Fred Baker
- Re: IETF in July Job Snijders
- Re: IETF in July Phillip Hallam-Baker
- Re: IETF in July Tim Wicinski
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July Robert Raszuk
- Re: IETF in July Ole Jacobsen
- Re: IETF in July Olivier MJ Crépin-Leblond
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July Fernando Gont
- Re: IETF in July Fernando Gont
- Re: IETF in July Carsten Bormann
- Re: IETF in July Adam Roach
- Re: IETF in July Victor Kuarsingh
- Re: IETF in July Stewart Bryant
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July Bob Hinden
- Re: IETF in July Fernando Gont
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July Michael StJohns
- Re: IETF in July Phillip Hallam-Baker
- Re: IETF in July Fernando Gont
- Re: IETF in July Carsten Bormann
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July JORDI PALET MARTINEZ
- Re: IETF in July Adam Roach
- Re: IETF in July Fernando Gont
- Re: IETF in July Salz, Rich
- Re: IETF in July Michael Speer
- Re: IETF in July Alissa Cooper
- Re: IETF in July Michael Richardson
- Re: IETF in July Toerless Eckert
- Re: IETF in July Fernando Gont
- Re: IETF in July John Levine
- Re: IETF in July John C Klensin
- Re: IETF in July Brian E Carpenter
- Re: IETF in July Ross Finlayson
- Re: IETF in July Pete Resnick
- Re: IETF in July Toerless Eckert
- Re: IETF in July Toerless Eckert
- Re: IETF in July Toerless Eckert
- Re: IETF in July Randy Presuhn
- Re: IETF in July Fernando Gont
- Re: IETF in July Clint Chaplin
- Re: IETF in July Rich Kulawiec
- RE: IETF in July Maisonneuve, Julien (Nokia - FR/Paris-Saclay)
- Re: IETF in July Phillip Hallam-Baker
- Re: IETF in July Rich Kulawiec
- Re: IETF in July John Scudder
- Re: IETF in July Michael Richardson
- Re: IETF in July Brian E Carpenter
- Re: IETF in July Christer Holmberg
- Re: IETF in July Bajpai, Vaibhav