Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions

S Moonesamy <sm+ietf@elandsys.com> Fri, 25 October 2019 11:25 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 764DC12086B for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 04:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 Dych9END-W9a for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 04:25:17 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7FD1200C3 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 04:25:17 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.185.148]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x9PBOnCJ024286 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Oct 2019 04:24:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1572002703; x=1572089103; i=@elandsys.com; bh=62qZB2Ocj1ytlOG30v4LgaFxvVuAdhmottulTgFcD3A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=au6fkzbuovXx8VFP7vzR1PfhqneUFRVlnlrFfZvbgAYLz8FLYgTP4xXUvmGYo41+N nKvdmAHEgq+ArQPh251BZ0W+Dyty70jYSfcW+NkXqzqQ1OScSvxIN7W2OE+7m+f/5Y i1/vDEDBMV973Zb2bvS4soqLKm9ImEUYV34at9TE=
Message-Id: <6.2.5.6.2.20191025040458.12702e48@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 25 Oct 2019 04:24:20 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: adrian@olddog.co.uk, Eliot Lear <lear@cisco.com>
In-Reply-To: <dc3bf13f-0178-8e4c-6680-ae3258ac1a9b@gmail.com>
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk> <CB806045-0E5E-4445-A377-7CD547B9DD90@cisco.com> <010a01d58ac1$c0ab2320$42016960$@olddog.co.uk> <dc3bf13f-0178-8e4c-6680-ae3258ac1a9b@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/RxQIRo1ikw3_pFWSOqwoB2303FY>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
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, 25 Oct 2019 11:25:18 -0000

Hi Brian,
At 07:55 PM 24-10-2019, Brian E Carpenter wrote:
>Personally I'm more worried about that than the risk of gaming or DOSsing
>the system. Now while it's true that a non-attendee might have frequently
>met the recallee at (say) ITU-T meetings, it's still probably the best proxy
>we've got for "very limited personal knowledge". Assuming, of course, that
>we think such personal knowledge is needed.

The Ombudsteam can decide that a person is no longer permitted to 
participate in IETF activities.  Given that the Ombusteam can make 
such a decision, should there be a requirement that the Ombusteam 
have personal knowledge of the person?  I looked up 7776 and I could 
not find such a requirement.

If there is a significant risk that the system can be bring the IETF 
to a halt, it means that the system is not well designed.  As Adrian 
pointed out in an email, it is possible to make a timely change to 
the system if there is an evidence that it is being misused.  It may 
be possible to add a clause to curtail misused.  However, that 
increases the complexity of the system.  It also opens the door to 
creating a system which might not work when it is actually needed.

Regards,
S. Moonesamy