Re: [Eligibility-discuss] Forced virtual IETF 109 as well as 107 (was: Re: NomCom eligibility & IETF 107)

S Moonesamy <sm+ietf@elandsys.com> Fri, 13 March 2020 18:26 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4455F3A0867 for <eligibility-discuss@ietfa.amsl.com>; Fri, 13 Mar 2020 11:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 bOsiKHNUbcdB for <eligibility-discuss@ietfa.amsl.com>; Fri, 13 Mar 2020 11:26:37 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A5B483A086A for <eligibility-discuss@ietf.org>; Fri, 13 Mar 2020 11:26:35 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.59.242]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 02DIQKTG004965 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Mar 2020 11:26:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1584123993; x=1584210393; i=@elandsys.com; bh=KT8mORCOQ9CVFJO51bzJwr6EkYcsUXdzaPbqCuI0D78=; h=Date:To:From:Subject:In-Reply-To:References; b=1zTiUw7gjriiKhLgTc/X/U8ZGEiELWFNdHWIDe3bSsOjNJLolYmduKnqlgT0ZyuJw yBJBq6m0DEJSyk6mx4tv08zc+8WTow548twd4qRYJ0uI3lTvUTHsD6i/z+MBg78PtE osVa2n4K9RoHgASDqhWpO/uQ5Yk0xMFBLnmRrAd0=
Message-Id: <6.2.5.6.2.20200313103636.0c6ec438@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 13 Mar 2020 11:25:47 -0700
To: John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <C9E8B3DAE355FAD80C21236C@PSB>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <C9E8B3DAE355FAD80C21236C@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/wntZdFk6IvagytUo4Xe8X0tuj58>
Subject: Re: [Eligibility-discuss] Forced virtual IETF 109 as well as 107 (was: Re: NomCom eligibility & IETF 107)
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 18:26:41 -0000

Hi John,

I moved the thread off ietf@.

At 07:45 AM 13-03-2020, John C Klensin wrote:
>We seem to be making strong assumptions that we will be able to
>hold IETF 108 as planned, with f2f meetings in Madrid in late
>July.  I suggest that the IESG (and the rest of us) think about
>that and so sooner rather than later.  Our implicit assumption
>is that things will settle down enough that IETF 108 can be held
>normally and that we do not need to worry about a "new normal".
>The infectious disease specialists and epidemiologists among my
>colleagues is this novel coronavirus really is new in several
>ways and, consequently, that we really cannot predict how
>quickly the period of maximal spread and risks will wind down by
>July.  That may be likely, but it is by no means certain.

I discussed the above question recently for reasons unrelated to the 
IETF.  There is a virus which is prevalent over the world.  There are 
health-related advisories from recognized agencies.  Is it reasonable 
to assume that a meeting can be held, as usual, four months from now?

>So, it seems to me that we should be sorting out possible issues
>and making contingency plans about the conditions under which
>IETF 108 would need to be virtual too, including both things
>tied to the first or second meeting of the year and to how we do
>things.   The circumstances that came upon us in the last six
>weeks gave us little choice other than making quick decisions.
>I personally think that, on balance, the IESG made reasonable
>decisions and handled things about as well as they could be
>handled, including the short-notice cancellation/ virtual
>conversion and reformed agenda.  But we'd best not have that
>"whoops, big surprise" situation followed by a scramble again,
>if only because of the damage that the loss of the cross-area
>review that has occurred at f2f meetings since the IETF started
>could do to the quality of our work.

The problem with "virtual" is that you (in general) end up with the 
"attendance" problem.  You also end up having to make rules which 
favors a large set of people and which are unfavorable to another 
large set of people.  If a person claims surprise, the person 
determining whether the request is valid would look up the 
credentials of the person and wonder who picked that person to make 
reasonable decisions.

>So, let us -- soon, even if not in the next two weeks -- ask
>ourselves such questions as to how the Nomcom will function if
>it cannot meet f2f at IETF 108 (or 109), whether the possible
>need for the Nomcom to do much more of its work remotely might
>affect whatever advice is given to the ISOC President/CEO about
>candidates for Nomcom Chair, and so on.   And then let's repeat
>that with a review of all of the other issues tied to the
>"second meeting" and how IETF 108 could be made maximally
>effective if we were forced to hold it virtually... including,
>of course, how that decision would be made and by whom.

One alternative is for the persons on the committee to fly to some 
location if they believe that their work is important enough for them 
to do that.  If I go by the numbers, there are currently 551 persons 
willing to do that.  I don't know how many of them are eligible and 
how many would volunteer.

>We could still view that as short-term with longer-term analysis
>and solutions to follow.  But July isn't that far away and, if
>things don't get better, we should not have to deal with any
>plausibly-foreseeable situations by being surprised and
>improvising.

The message from the IESG contains a set of choices instead of an 
analysis.  The current path leads to of inconsistent decisions.

Regards,
S. Moonesamy