Re: Gaming the System [Was: AD Sponsorship of draft-moonesamy-recall-rev]

S Moonesamy <sm+ietf@elandsys.com> Sat, 20 April 2019 20:41 UTC

Return-Path: <sm@elandsys.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 7A33B12027A; Sat, 20 Apr 2019 13:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1] 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=opendkim.org header.b=PqzlOi55; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Dewii777
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 1jkZA5wwK8PK; Sat, 20 Apr 2019 13:41:45 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4BB120277; Sat, 20 Apr 2019 13:41:45 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.53.132]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x3KKfWQ5003780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Apr 2019 13:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1555792904; x=1555879304; bh=tn8AQxjaHm17Ykop+Caj5wDQmZ4uvUJBFkS8C25N+qg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PqzlOi5520MulzdPxF/duZzoG8xFKbE5hWtqfk/xqkMQxOqvqbqOL1lGA61U/cZ9G LGKK2nfmhZsC6btWQ/Oo0WF/A4KPxAXaGwhUu5rcYZfAMl9RyaWPRwpn6nptvUXAJF bXWin8ktgRktV2wJk9+D/TXL1o4lKrdYEyUJk86o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1555792904; x=1555879304; i=@elandsys.com; bh=tn8AQxjaHm17Ykop+Caj5wDQmZ4uvUJBFkS8C25N+qg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Dewii777VOlL5o05yKkPnBmeCCTKYqWTcM+s0KgB59Lt15NwE1asBIHoiUqu6AllO PFsWdqab63WS3Hi0Q4UoFQ0JuEuwOruezDgdUeeGCBm4QOa4r3W8XLz65Utz4O+u/1 afXYZs5+Tk5CvNwy4xGMSwCna+umhkTICmfKZmpI=
Message-Id: <6.2.5.6.2.20190420123441.122da2c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Apr 2019 13:28:01 -0700
To: adrian@olddog.co.uk, iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Gaming the System [Was: AD Sponsorship of draft-moonesamy-recall-rev]
Cc: ietf@ietf.org
In-Reply-To: <033401d4f76f$1ce49540$56adbfc0$@olddog.co.uk>
References: <033401d4f76f$1ce49540$56adbfc0$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/podIWG9z_iWuM3Jq-fHDBDmBqOk>
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: Sat, 20 Apr 2019 20:41:47 -0000

Hi Adrian,
At 04:49 AM 20-04-2019, Adrian Farrel wrote:
>Pretty much the whole of the IETF consensus process is equally open to such
>gaming because all decisions are taken on the mailing list. It might be that
>gaining positive consensus is not easily gamed, but objecting to progress
>would be easily attacked in this way.

Yes.

>Yet I can only recall two attempts to introduce "sock puppets" to the IETF
>consensus process. Both were spotted early and both resulted in minimal
>impact on the IETF process. So few attempts in such a long period does not
>suggest that this is a major cause for concern.

The IETF has a term to describe such attempts.  I doubt that such an 
attempt would fly under the radar.

>Additionally, the complete absence of recalls of seated and active
>Nomcom-appointed people suggests that either the process remains unlikely to
>be executed, or that the current bar to execution is too high to enable the
>necessary petitions.

Yes.

>I would suggest the same ethos applies in this situation. The IESG is in a
>good position to work with each Nomcom chair to understand the frequency of
>recall petitions and the drain on the community that they cause.
>Furthermore, to obtain a view of the balance between successful recalls and
>petitions that might be judged frivolous. If the level of mendacious recall
>petitions becomes a problem then the IESG could report this to the community
>and steps could be taken to further strengthen the protection.

In my opinion, it would take around six weeks to solve that problem, 
if it is indeed a problem.

One of the reasons to "protect the system" might be because it is 
"informally" viewed as weak by the IESG.  That might explain why the 
IETF's unofficial motto only mentions the second part of the sentence.

Regards,
S. Moonesamy