Re: [Eligibility-discuss] Fwd: The "eligibility" list, and a virtual meeting

Eric Rescorla <ekr@rtfm.com> Tue, 17 September 2019 18:15 UTC

Return-Path: <ekr@rtfm.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 9944F12098C for <eligibility-discuss@ietfa.amsl.com>; Tue, 17 Sep 2019 11:15:00 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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=rtfm-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 u25c2OhS3NYO for <eligibility-discuss@ietfa.amsl.com>; Tue, 17 Sep 2019 11:14:57 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 DA3C81209AB for <eligibility-discuss@ietf.org>; Tue, 17 Sep 2019 11:14:52 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id e17so4486372ljf.13 for <eligibility-discuss@ietf.org>; Tue, 17 Sep 2019 11:14:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BHmp/hQAqJBLV12Q0QXQ6xL6lpqVkLjW/aq3jhz1R2Q=; b=aPt27yYzqgCgQvHhmCakatWl5FM5sOJW84+dnwIFle9EwDbjUCPP7PP/FciN7BWdFm 3vHvhFWM2IWeVi1SabsfJQYE0puRbEpCLov+0bfVZyDk425PuEmNBhzy/bz/YYX7SUWF vusFhis5tm+/R+VEx79EFD0q1pPkb77uFD9/5Y7yaXw4feaoLHQKjEW+kpxsTq455Oqs Z9LMb5OVUFEG710JlM4L7aK5YNYsTWA3a0/eg2CL29tSFm8orOjRBwd8/yBWmp2vMRCV A9Flcj7sf3aNxvcZAdoXXyZLB9s9mklU9YR1j6z75nurMS+W8qfaA3DG2Mewpwv5gzOK EXdQ==
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=BHmp/hQAqJBLV12Q0QXQ6xL6lpqVkLjW/aq3jhz1R2Q=; b=UoRW1Z7iZdfb2mZ6+VK+QlEyLL7HPJKcbcxNP9kCmF71cEYErdiVKd2Y8axJAMHRYP BNWI4FxXnNWUDsx459pgfkyKQ3r7g5AXfrZD3okAsopmRhlpD+Cf9wdhHvvJQmWn+QDy co0N78WgpXGvdXK/TH5tFMCNfzE2PsN2TnbUp/f566oF2FsrkioEOWF1/58foC6RHZ7N A7lgFtLVN7ZoUjbDEujDBM0T4Ivbm+EYM6X0jD1iNqaRiBnpldaQdN49sXVmv+a16CRj /s7Bghx88w+fkPtZIzSydJfk+/kIn5/MwsNGHjceq3tdneFb9jaENlKXDaAqNZr4SDVE rFvg==
X-Gm-Message-State: APjAAAWSAH4nlm7ed6M36+P0w9l/hESof9PnX2t6ordzj/7VYNNwGV3V 0j6qXPalF6yGXMDhrUtvwR+YqKFzqBZzQsN5OJ/Y7XpC
X-Google-Smtp-Source: APXvYqw75/R/LsvOGmpnx+KNxE9kVTrks81w1b6WRnOxabe8iwIEmaPrSd392wjCIwweDV5c9dW2iTFkS5Dfdbf4N7A=
X-Received: by 2002:a2e:9750:: with SMTP id f16mr2687723ljj.239.1568744091071; Tue, 17 Sep 2019 11:14:51 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+BEoDd5aas9VfAmfcF+H_54w4ETNafVwFAObhY_A2v-Q@mail.gmail.com> <C90E6D6D-D058-40A5-AA3B-2D2002077016@episteme.net> <CALaySJJggQqYhVHSdKCx4BvpiR31oodx9C9NkzfMoFGbUv+gmg@mail.gmail.com> <CALaySJKxbwYXnE7gcgwmuBUWg_Q+QSx-yYtTCOLoQesB6JLojg@mail.gmail.com> <CALaySJJh7zvuuuxcs-kE=LaaZP1aXiaT3HpQ30tt4DNOMMP0oQ@mail.gmail.com>
In-Reply-To: <CALaySJJh7zvuuuxcs-kE=LaaZP1aXiaT3HpQ30tt4DNOMMP0oQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Sep 2019 11:14:14 -0700
Message-ID: <CABcZeBMrnPv9AMhQgv4ciq2DypyB_rkqdwNkyuXgNqyHVGcpzQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004acf3e0592c3b22d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/icf4FaP1iw1hsjWtyaF3kzH3dsA>
Subject: Re: [Eligibility-discuss] Fwd: The "eligibility" list, and a virtual meeting
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: Tue, 17 Sep 2019 18:15:01 -0000

On Tue, Sep 17, 2019 at 9:34 AM Barry Leiba <barryleiba@computer.org> wrote:

> Hi, all.
>
> I am serving as the responsible AD for a virtual meeting (via WebEx)
> and ongoing work to address what's been discussed on this list (the
> "eligibility" list).  See below for the problem statement that will
> drive the virtual meeting, and let's see where we get from there.
>

I assume we'll start by discussing whether these claimed problems in fact
need to be addressed?



> The rules for virtual meetings require that we give two weeks' notice
> of the meeting time, but I'd like to do closer to four weeks, so we
> need to nail down a date very soon.  It's going to be challenging to
> find a time of day that works for enough of us, and I'll have to ask
> people to be very flexible about times, realizing that *someone* is
> likely to have to participate at a pretty awful hour, local time.
>
> I'd like to get feedback on this plan in the next few days, and then
> put out a doodle around the end of the week to try to pick a day and
> time.  If you intend to participate, please post to this thread your
> intent and your time zone (as "UTC-4", "UTC+1", and so on, relative to
> UTC).
>
> I think we do need to decide, as a group, whether the limited update
> to the recall process is important enough to stand on its own... or
> whether it makes more sense to address the broader issue of
> enfranchising remote participants, and to update the recall process as
> part of that.


Or whether any change is needed at all, right?

-Ekr