Re: IETF in July

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Fri, 20 March 2020 23:23 UTC

Return-Path: <prvs=1348727322=jordi.palet@consulintel.es>
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 57DE53A0F3F for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 16:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 ZITEAJ8dKfTQ for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 16:23:21 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F7533A0F3A for <ietf@ietf.org>; Fri, 20 Mar 2020 16:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1584746593; x=1585351393; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=DLC/q79AvHIslyxkbHviaENqozomrcCtx8 m8YOAYC1I=; b=QS9lwuByhE5vZ9tmQ4JvCjOiKb6nKJXaqljcZuDllR+oPm4woa Q3ZDiYFGIhqUoHeuE5P+BXBiCR4xdTft/Se8RP0wXGjsqMI3fLfKmtkaVP5BrejO HODSLLhXnbJDEs8izzWrU7CRk8Ta4jTEO+X5jWN3VunnXHGWHSzKQh7BE=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sat, 21 Mar 2020 00:23:13 +0100
X-Spam-Processed: mail.consulintel.es, Sat, 21 Mar 2020 00:23:13 +0100
Received: from [10.10.10.130] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000098082.msg for <ietf@ietf.org>; Sat, 21 Mar 2020 00:23:11 +0100
X-MDRemoteIP: 2001:470:1f09:495:e5bd:b953:2c7f:e5b2
X-MDHelo: [10.10.10.130]
X-MDArrival-Date: Sat, 21 Mar 2020 00:23:11 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1348727322=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Sat, 21 Mar 2020 00:23:11 +0100
Subject: Re: IETF in July
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <4763AC94-40AB-459C-B71C-E262A01557B1@consulintel.es>
Thread-Topic: IETF in July
References: <DM6PR05MB63488A5D5D14D11CBF145CEBAEF50@DM6PR05MB6348.namprd05.prod.outlook.com> <1AAA027D-2EF1-4087-BBDB-E4C2BF564A36@puck.nether.net> <CAMm+LwiymYoPmiGvSNxmmmSMe+UGye5YtPrvKAf6ay49sb2DuQ@mail.gmail.com> <CADyWQ+FppGxAGum0aT0BgC0BUV3qYQaX6-0+2Lw7knCmkhG+ug@mail.gmail.com>
In-Reply-To: <CADyWQ+FppGxAGum0aT0BgC0BUV3qYQaX6-0+2Lw7knCmkhG+ug@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3667594991_1754194179"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b5TQ0REbwP0FnMPu-ntZuEIpPio>
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: Fri, 20 Mar 2020 23:23:27 -0000

The situation in Spain will be worst next week because the government, as I just explained in the previous email, didn’t taken the right decisions on-time, so they delayed the situation and increased the spread.

 

Other countries should have learned the lesson and avoid repeating the Italian and Spanish mistakes NOW.

 

Looking at other countries I can see that at least Germany and France will be next, surpassing the figures from Spain. They have reacted too late … but US, Switzerland, UK, and many other countries in EU, seems to not have taken the same measurements yet. They are right now in time. Any additional days delaying this decision count.

 

Regards,

Jordi

@jordipalet

 

 

 

El 20/3/20 22:34, "ietf en nombre de Tim Wicinski" <ietf-bounces@ietf.org en nombre de tjw.ietf@gmail.com> escribió:

 

>From CNBC earlier today:

 

Spain official warns 80% of people in Madrid will get coronavirus, as nationwide death toll surpasses 1,000

 

Yes, we should start planning now

 

 

On Fri, Mar 20, 2020 at 5:31 PM Phillip Hallam-Baker <phill@hallambaker.com> wrote:

On Fri, Mar 20, 2020 at 4:46 PM Jared Mauch <jared@puck.nether.net> wrote:

Ron,

Might I suggest we get through the next week first? :-)

I’ll wait to see the hotel announcement like everyone else, which I presume won’t be sent until travel normalizes, since many international borders are closed.

 

I strongly suggest that for purposes of planning WG work, everyone assume there won't be an in person IETF for the rest of the year unless we hear otherwise.

 

It is highly unlikely that travel bans will be lifted in a sufficient number of countries to make any IETF viable in July and Madrid is reportedly a hot spot. If the secretariat announces registrations are open then we can rethink. Spain just reported 104 deaths in 24 hours. The chance that Madrid is going to be in a state to receive visitors in 17 weeks is really small.

 

So don't blow off the virtual meetings assuming there will be a 'proper' IETF in July. Not unless you are ok with work being delayed for up to a year.

 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.