Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

Suresh Krishnan <suresh.krishnan@gmail.com> Fri, 24 May 2019 23:55 UTC

Return-Path: <suresh.krishnan@gmail.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 087DC1200C1; Fri, 24 May 2019 16:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 emNZMg_LGH5T; Fri, 24 May 2019 16:55:01 -0700 (PDT)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62D45120020; Fri, 24 May 2019 16:55:01 -0700 (PDT)
Received: by mail-yb1-xb2c.google.com with SMTP id x32so1338648ybh.1; Fri, 24 May 2019 16:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bTxkL1ntqykS2gi3dTlta1+lJf6HYAma+TU8k0RG7M4=; b=GgArhd9W5m7AMAypT/p2h4tO8VrzB7GxuWLwukUjHfXB9r/rgdFuaVa71MbFWGR/WE vagOqJll1xHKzY+lBGUdgMeH1o2t3po0TnGtiqBaDgLIesvOrv39IntajUCI4TBFkcfV WiSV+9zoDCWBU2WURCr3+ak63AwEM66A9xny3sKFlSpkPPnZVRy1xLVD/AovvLGSvQ8O Ul6CbAWz3Ip8w2fk4SBzrSV7wDO0BsZ6+jMI8XXDeSvw1IvMkwVlH8Yu5tLqdae4hZsQ ZXdziFPaAEe0OpxCuUq/5bIJgGyuGofmQxno1Qj3pn04+lppDxxSgxhkF/zT6vO5fJWh Q/hQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bTxkL1ntqykS2gi3dTlta1+lJf6HYAma+TU8k0RG7M4=; b=mD9I3+74mqC/ZeaPyEl9RTR8JT5cDFIKb7m4wX3FKQgCQ0sHlYJOD97veheBe5g/0T zHwkTlCv470Myq+eQw4mojgzFKbEfd/o0L2WJ39OfdS7mQmNeTpucp7OM/gpn/xg9F/D T15rwo+oVhzLx0pGhRqbEdwha70JyD4ugfJQ19zqofozoJmxWw4mXH0K3rJkTLYvx5Dr VHsdhgU9OYhiU4UUwy8qADWBj6xDS2bOO7Ty1XVzoY5fVDMq+6YyYvLdu1oMkTEgVY2S 09patWYRlJmSyPS9vkLPfjzy4PF2tEwQJJmghFbNZ0dPmiU9HvlMcxBl6bQrI4YuapwB VhOA==
X-Gm-Message-State: APjAAAVydpjmhUodMOPJc24pGt0eVTNunZf1PGqMnJrHsJBsji7wDEil r9uH70ODk4pC9JKc6cCN/qI=
X-Google-Smtp-Source: APXvYqyuSHhHO1cG42OaKgWBpvO4ueQ+BiOdfsX1v+6XujyXat+9Q0N2exy/HGI23Q3LF2ca3K89uA==
X-Received: by 2002:a25:c6c1:: with SMTP id k184mr18426027ybf.93.1558742100544; Fri, 24 May 2019 16:55:00 -0700 (PDT)
Received: from [10.0.0.20] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id b14sm1048850ywb.1.2019.05.24.16.54.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 May 2019 16:54:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <6.2.5.6.2.20190518141450.1163e590@elandnews.com>
Date: Fri, 24 May 2019 19:54:56 -0400
Cc: chair@ietf.org, IETF Discussion <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/w5rW6l3rJ7DipHI6bz8umrXobro>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
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, 24 May 2019 23:55:04 -0000

Hi SM,

> On May 18, 2019, at 8:33 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> 
> Dear IETF Chair,
> 
> A few months ago, I submitted a short draft about the revision of the recall initiation model [1].  Last month, the recommendation of the IESG was to submit a BOF proposal [2].  I had an email exchange with one of the Area Directors about the request for an IAB shepherd.  If I am not mistaken, an IAB shepherd can provide a review of architectural consistency and integrity.  Does the short draft require that type of review?

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. 

> 
> The "we think" [2] from the IESG is expressed in one sentence.  Would it be possible for the IESG to explain its understanding of the in-depth problem statement so that there could be a discussion?

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

Thanks
Suresh

[0] https://en.wikipedia.org/wiki/Skin_in_the_game_(phrase)