Re: Assessment criteria for decision on in-person/virtual IETF 108

Bron Gondwana <brong@fastmailteam.com> Fri, 08 May 2020 04:04 UTC

Return-Path: <brong@fastmailteam.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 4A8833A0ED2 for <ietf@ietfa.amsl.com>; Thu, 7 May 2020 21:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, SPF_PASS=-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=fastmailteam.com header.b=F9PGl9zP; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Z13QtahX
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 ez_5yYxikW5h for <ietf@ietfa.amsl.com>; Thu, 7 May 2020 21:04:55 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C38E3A0ED1 for <ietf@ietf.org>; Thu, 7 May 2020 21:04:55 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 59047FA8 for <ietf@ietf.org>; Fri, 8 May 2020 00:04:54 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Fri, 08 May 2020 00:04:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=VwWZlz7 IjvHdfmX8u2jgDqxE7/lAL7rxlZnFpIncTq0=; b=F9PGl9zPjyYQ1U0MCHISg+8 OvSjKhoC/91xTn0ST9el2Pj/5fmW4/AKNtRpTfNtxhNqxfYV1UdnOBOXWBjcsWP1 DnirSKQrjOlM23SL6bV9PVcCTMaxLYOTGpaReNaZjfdmbL+nRL3FKxUFH28mGVP9 +PhZdtCZF1MZU8/AS2GkQd5qrCr/bkUnbq9E2oBhXg31DTE6HKjY38pJyubvnDmr 8Baqx/C+X4CtnGRgHp2iFHkShuMIYR2iKVf1X4tJVG9P5CI30t8UvHqnR6FKhtNt e55Ul5iyO3CtorlgX0QgIc8D3VjlUWwjPOf+aQvHbe8I8v8Ql8nMCHA+BL9L9nQ= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=VwWZlz 7IjvHdfmX8u2jgDqxE7/lAL7rxlZnFpIncTq0=; b=Z13QtahX7EuGJcemz1i39K BV6uF284r9sdwtVVMBePIabEFZ++KqXWyHkAYCRLQkd3kbliAb5XPXsgFBihyRD5 CSJ5ZxQy6wSb+gHSO0plroGH8xy9XnZVf3k6Jket2/tm/71q5XJ2KRs0D60XnxAK UouUCkYM8VPf7PiikplTaSH9mNl23EcVdzgq+grMwXph6GmLbY3SGCQiDbSofO5a aqNc/ZmdiVVEaEPVNnwgDhPXBmYMEX/UtmGtckrderjHeKkF+LOiRygwMip2FoRI HNbExf77x1rIFcRKprHoGoIbUMOOx/wKS8uTB3uFnmVswR0LpFOLizIVKNiFxpnw ==
X-ME-Sender: <xms:Zdq0Xns896YPWYgBFJldd6460TeQiG7aUuKaI4Q8YQWNAGfwZ7r_Sg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrkedugdejiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnheptdehteegfeevte duffevteehfffghefhvdevkeeuhfehueetudehgfegieekjeetnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrih hlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:Zdq0XoIXh9lKOV3FEseX3PYC1DjzmO9wajKdSzYIQqRvsPvC_xcU4g> <xmx:Zdq0XlkUVrgINdC-o3ZSwKzdK1KGtNN7J__-Gs8-4FYHbasoJb7j8w> <xmx:Zdq0XopbS-FUUmcTheoQPncSCbDD3Yti2dGwCvOG7D8ZsugSxpKWYg> <xmx:Zdq0Xp_K9do9uHzBJm4KKSiVVT6mVCuDzsGMjqT0YgOows6bJW-6ag>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9BFCC18053F; Fri, 8 May 2020 00:04:53 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-413-g750b809-fmstable-20200507v1
Mime-Version: 1.0
Message-Id: <99fe4be1-756f-4258-be4d-3d62f215f0e1@dogfood.fastmail.com>
In-Reply-To: <8AC28C60-1A30-4136-8AA1-3154AA219231@consulintel.es>
References: <ca4cb8af-520a-5591-736d-ec8e812479d5@comcast.net> <00E686E5-C058-4CE4-962B-3D234BE0394F@ietf.org> <a087c0ef-29dd-129c-fd56-e407b189a754@comcast.net> <CAHbuEH4rpJEH7XHV3WF6oE4GNUkRH8rX5ZLpeAE_5khyewnYaA@mail.gmail.com> <BDC7D019-D274-48B2-A388-017F8659DA7A@ietf.org> <8AC28C60-1A30-4136-8AA1-3154AA219231@consulintel.es>
Date: Fri, 08 May 2020 14:04:19 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: ietf@ietf.org
Subject: Re: Assessment criteria for decision on in-person/virtual IETF 108
Content-Type: multipart/alternative; boundary="a016965c93284c898a89b8ba3b28189a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MAwv51rMlsd-OPjPsfwhGBD_zNM>
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, 08 May 2020 04:04:59 -0000

(up-front disclaimer: this is a drive by commentary and I don't have any specific knowledge or skill in this area, I'm just an opinionated jerk on the internet. In my experience this makes me fit right in here...)

On Fri, May 8, 2020, at 08:10, JORDI PALET MARTINEZ wrote:
> 
>  El 7/5/20 23:42, "ietf en nombre de Jay Daley" <ietf-bounces@ietf.org en nombre de jay@ietf.org> escribió:
> 
>  * Feedback not to use the Madrid Tourism Site because "while this is probably a good source, there may be some delay in some of the touristic activities re-opening, that should not be part of our assessment". 
>  => This site is the primary site for informing visitors on the status of hotels, restaurants, and local transport, all of which are necessities..
> 
> [Jordi] Is the wrong site. There is a very simple thing to observe: It has NOT been updated since around 14 of March, and obviously the situation is not the same. There is a confinement de-escalation process, with 4 phases (0-3, one every 2 weeks unless it goes wrong) which started 2 weeks ago. There are central government sites with much accurate information, daily updated, but unfortunately only in Spanish. I'm speaking with officials and other trustable information sources every few days and there are 2 daily press conferences from the government (morning and afternoon) to confirm the progress and actions being taken.

If I was the king of the IETF, I'd probably be using two primary sources here:
1. the conference hotel. They will speak the local language and have very current local information.
2. the sponsor/host. They also presumably have contacts and specific experience.

The argument that "English language information sites may fail to be updated in a timely manner" is definitely a legit complaint and I agree with Jordi here that saying "if this site indicates that any form of local emergency conditions still prevail" is a bad standard to use if it does not provide current data.

In the degenerate case that this site was abandoned but left up, it would be impossible to ever hold a meeting in Madrid, as this site would continue to say it's unsafe. To the extent that this isn't the canonical primary Government source, I would favour going with the more authoritative version.

Having said that, I trust Jay and those assessing risk to make the right call if everything else says "go ahead" (including local contacts and Spanish language official sources) and this site is still last updated March 14 and still saying not to go ahead.

>  * (paraphrasing multiple people) “drop the US CDC because it is unreliable and/or political”. 
>  => The US CDC is what is referenced in our contracts and we have not identified a better alternative.
> 
> [Jordi] Having it in contracts means "nothing" if is biased, as it has been proved. It will be interesting to review several countries that have already started to go the "new normal" to see if the website has been updated on time, or it takes several days or weeks. I understand that it is one of the information sources, but should not be the only one specially if there is contradictory trustable information.

"if there is contradictory trustable information" -- I think you hit the nail on the head there. There needs to be a reliable metric for determining which contradictory information is trustable. I note that you didn't propose an alternative actionable source here, and Jay made it clear that the IETF has also not identified an alternative which is more trustable than the US CDC. Everyone is unreliable/political to a greater or lesser extent.

I think I see a good point Jordi is making which I paraphrase as: "use this source, but apply your own bullshit filter".

However, "all of our contracts have a force majeure clause that specifically lists the US CDC." is a really strong point in favour of keeping the CDC as a key input, since practicality does matter.

>  * Feedback to refer to US CDC travel advisory “at level 2 or below" rather than “below level 3”. 
>  => The nature of level 3 (avoid unnecessary travel) is why it is a disqualifier and if this change is made then that explanation is hidden.

I mean, "below level 3" and "at or below level 2" are mathematically identical anyway unless there's a level between 2 and 3. Sheesh. Bikeshedders gonna bikeshed.

Bron.

--
 Bron Gondwana, CEO, Fastmail Pty Ltd
 brong@fastmailteam.com