Re: AD Sponsorship of draft-moonesamy-recall-rev

S Moonesamy <sm+ietf@elandsys.com> Sat, 25 May 2019 01:18 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 20DF6120177; Fri, 24 May 2019 18:18:52 -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=X0oz77Gs; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=znEnLISa
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 3FQ7qsyqOk94; Fri, 24 May 2019 18:18:50 -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 AE0C012001E; Fri, 24 May 2019 18:18:50 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.49.188]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x4P1IY5i017319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2019 18:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1558747127; x=1558833527; bh=a7PMsXTeo3RfQk4VB/Z3Sb4SINIa76lCp3W/eUonZbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=X0oz77Gs1yXCgDbYdOLTJq5XeQ03nu0CNQ0flmQyZWS6is/nRqtp4CpztZF7mBfU1 UoEWlmkU6g+Wn7afw8bxPLO5sbP/g06EYb64+g0dlh7sNCO+/LN8cgjVPDjhs6wlCB pD3Jd0VLw2wgonMTFlnSb/JZttc2lhirc+7W25bo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1558747127; x=1558833527; i=@elandsys.com; bh=a7PMsXTeo3RfQk4VB/Z3Sb4SINIa76lCp3W/eUonZbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=znEnLISayWHNxjGrZktQBeNNsUEI4hJJDbEiwrXjGwxgmpPlR4zCHCc5R3j+G5vnp jLItiR7ndu17t4lGA2NVNOCzFNHz1E1Fi40YZtIUDybZGicuvsxjohS+9zb3SFptc2 kBRekLbPleQF5JAro8kzAMRn1WYgWmx6tBeU08Ro=
Message-Id: <6.2.5.6.2.20190524165848.0e67b2e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 May 2019 18:17:18 -0700
To: Suresh Krishnan <suresh.krishnan@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Cc: chair@ietf.org, ietf@ietf.org, John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
In-Reply-To: <82E6BD6B-41F4-4827-8E18-3FF63511DFEA@gmail.com>
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB> <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com> <E85C84CF-DB0B-410E-A0B2-A7C7E705E469@kaloom.com> <6.2.5.6.2.20190518141450.1163e590@elandnews.com> <82E6BD6B-41F4-4827-8E18-3FF63511DFEA@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9N2tn3HZ4uaLF2BdbRfBbJtx9a8>
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, 25 May 2019 01:18:52 -0000

Hi Suresh,
At 04:54 PM 24-05-2019, Suresh Krishnan wrote:
>I am not talking for the whole IESG but I will 
>tell you my opinion as a sitting IESG member on 
>why I did not want to AD sponsor this draft in 
>its current condition. I think the proposal in 
>the draft sets the bar too low specifically on 
>the Section 2.2 front. One of the things that 
>has kept the recall petitions rare is that that 
>the people who initiate the petition need to 
>have some accountability for doing so (I would 
>call this "skin in the game" [0] but it does 
>not translate well across cultures). Otherwise 
>there will be no bar to filing frivolous 
>petitions. This brings me to the elephant in the 
>room. It is fairly trivial for someone to sign 
>up 10 remote participant identities to initiate 
>a recall petition without incurring much effort, 
>for the *sole purpose* of starting a recall 
>petition. I would like to see some suggestions 
>as to how we can ensure that this would not happen.

Thank you for sharing your opinion openly.

There isn't a "skin in the game" hurdle for 
appeals.  It is trivial to file five frivolous 
appeals and get 15 Area Directors to respond to the appeals.

There is the following sentence in Section 3.1: 
"All signatories must have registered to attend 
and have participated physically or remotely at 
least three out of the previous five IETF 
meetings".  Those 10 remote participants (please 
see above) cannot just sign up  as that would be 
considered as attending a meeting.  If a person 
was participating remotely in a WG session, the 
WG Chair and some of the regular WG participants 
would likely know who the person is.

If the IETF community is uncomfortable with the 
"remote only" signatories, that could be 
addressed by setting a restriction on the number 
of signatories who are "remote only".

>There were some concerns that were brought up 
>during the discussion on the ietf@ietf.org list 
>and I would like to see a proposal (or a revision) to resolve them. One of the

Could Alexey, Warren or you please list the 
concerns so that they can be addressed?

>other things that came up during the discussion 
>was that some of us felt that a path to Nomcom 
>eligibility for remote participants was a much 
>better way of preventing disenfranchisement of 
>remote participants. I think Barry stated this 
>explicitly in one of his emails. Given that 
>there are multiple potential way to go about 
>achieving the goals, I do not see that harm in 
>having further discussion to see what we should pick as a base.

Since Barry sent his email about Nomcom 
eligibility there hasn't been any draft about 
that topic.  There isn't anything which could be picked as base.

Regards,
S. Moonesamy