IETF Logo Mail Archive

Re: "Management team"

ned+ietf@mauve.mrochek.com Wed, 22 April 2020 18:51 UTC

Return-Path: <ned+ietf@mauve.mrochek.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 214313A1369 for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 11:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 h94sRplmZcKF for <ietf@ietfa.amsl.com>; Wed, 22 Apr 2020 11:51:21 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0165C3A1363 for <ietf@ietf.org>; Wed, 22 Apr 2020 11:51:20 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RK090CVRK0005SMA@mauve.mrochek.com> for ietf@ietf.org; Wed, 22 Apr 2020 11:46:17 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RJM3XSTRLC000058@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 22 Apr 2020 11:46:14 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: ietf@ietf.org
Message-id: <01RK090BEE78000058@mauve.mrochek.com>
Date: Wed, 22 Apr 2020 11:44:11 -0700
Subject: Re: "Management team"
In-reply-to: "Your message dated Wed, 22 Apr 2020 12:53:36 -0400" <a27cab38-8a1e-4088-fa1e-20c702b9b0c3@network-heretics.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>
To: Keith Moore <moore@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ig_hZyJsWYfXcltPpE5LN-dQ35Q>
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 18:51:23 -0000

> On 4/22/20 12:33 PM, S Moonesamy wrote:

> > It is ironic that the Internet Engineering Steering Group gave its
> > approval for IETF attendees to "sign the blue sheets" by typing in
> > their names in a web-based collaborative real-time editor which does
> > not provide verification process.

> 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.

Admittedly my tolerance for crapware is essentially zero right now, so the
amount of time I devoted to this task would best be measured in milliseconds.

				Ned

v2.23.0 | Report a Bug | By Email