Re: "Management team"

John C Klensin <john-ietf@jck.com> Wed, 22 April 2020 21:09 UTC

Return-Path: <john-ietf@jck.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 DF43A3A0A00 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 14:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5SVBQNss2pRE for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 14:09:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B072B3A0A06 for <ietf@ietf.org>; Wed, 22 Apr 2020 14:09:12 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jRMcF-0004BO-FC; Wed, 22 Apr 2020 17:09:07 -0400
Date: Wed, 22 Apr 2020 17:09:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Keith Moore <moore@network-heretics.com>
cc: ietf@ietf.org
Subject: Re: "Management team"
Message-ID: <69249B15FC435328F4D9BD4E@PSB>
In-Reply-To: <01RK090BEE78000058@mauve.mrochek.com>
References: <47A0EEE1BBB8EF41FD8B07E0@PSB> <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org> <6.2.5.6.2.20200421022015.0ba531d0@elandnews.com> <17E08229-CE52-434E-B2FF-22992E95DD30@ietf.org> <BD7D0BDB-C8EB-4113-B379-5B2095C7F9FA@episteme.net> <64A28988-B8DC-4DA3-90FF-FBE658AE620E@ietf.org> <6.2.5.6.2.20200422083137.0c226b08@elandnews.com> <a27cab38-8a1e-4088-fa1e-20c702b9b0c3@network-heretics.com> <01RK090BEE78000058@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Hw5ubpDcGZn0_XnwGCpr0wLZajQ>
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: Wed, 22 Apr 2020 21:09:14 -0000


--On Wednesday, April 22, 2020 11:44 -0700
ned+ietf@mauve.mrochek.com wrote:

>> Well, neither did the paper blue sheets provide any
>> verification.
> 
> And all it took was a functioning writing tool to operate it.
> I can't get this to work in Brave, so I'm not signing the
> sheet for the sessions
> I attend.

This suggests something else that may be relevant.  If there is
_any_ chance that we might want to use session attendance
information for IETF 107 for anything at all, including but
definitely not limited to Nomcom eligibility in the future (not
this year's NomCom), it would probably be wise to either merge
to information from the Etherpad with Jabber logins and/or to
explicit ask people who were unable (or sufficiently
inconvenienced by technology) to record their presence on the
Etherpad to identify themselves to the Secretariat in some
appropriate way (I hope not on this mailing list).

Jay, is that feasible?

    thanks,
   john