
From nobody Sat Jun  1 20:54:11 2019
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 99A79120025 for <eligibility-discuss@ietfa.amsl.com>; Sat,  1 Jun 2019 20:54:09 -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, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=opendkim.org header.b=oMtzh7N8; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=nMvClc3m
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 AcodrgB4_uqU for <eligibility-discuss@ietfa.amsl.com>; Sat,  1 Jun 2019 20:54:08 -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 3BF7712008F for <eligibility-discuss@ietf.org>; Sat,  1 Jun 2019 20:54:08 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.51.5]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x523rjXZ011811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Jun 2019 20:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1559447639; x=1559534039; bh=uel/jkMBPMhxA3hkDAVpJkcXjMsa+kZcPuTDZrJHKgc=; h=Date:To:From:Subject:In-Reply-To:References; b=oMtzh7N8nXFbDRGUzg+owzyxZIhJko3tb+Pai7PYlsJ5TTfYK/tkEgYVyNmNLIEfE iCMM4Pcb/0shiE/3ElA1BzMvHJ3rlFUEBW71OGcdnLedkLsg/VL2tFj5csWbDSL2X/ 373BdZsIqVOi1wCOthUtzkOiz2gsgec9dMkekwH4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1559447639; x=1559534039; i=@elandsys.com; bh=uel/jkMBPMhxA3hkDAVpJkcXjMsa+kZcPuTDZrJHKgc=; h=Date:To:From:Subject:In-Reply-To:References; b=nMvClc3m+YpvzpQ7zSyHFiu0lJ+xmkx+A+MNtvNkB/651CTIGQe8ggXesACl2/Jr9 F5hO6DVHFBdlngpt5tu5gTTpKC7xEmW/HwrG3LQlBi+huf70atL29Atb4SS7GSNWSy bn/LCDSkPzOwKjc3/46Mv/6hfiWm+qrUBvMEhgV4=
Message-Id: <6.2.5.6.2.20190601204707.0bf89070@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 01 Jun 2019 20:53:28 -0700
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Suresh Krishnan <suresh.krishnan@gmail.com>, Warren Kumari <warren@kumari.net>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/SCNeqbR118tzezmSTV24ysONYMg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Sun, 02 Jun 2019 03:54:10 -0000

Dear Area Directors,

Over a week ago, I sent you a proposal for a virtual BOF [1].  Would 
it be possibel to get some feedback from you?

Regards,
S. Moonesamy

1. Please see https://mailarchive.ietf.org/arch/browse/eligibility-discuss/


From nobody Mon Jun  3 20:22:15 2019
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 E781D12004B for <eligibility-discuss@ietfa.amsl.com>; Mon,  3 Jun 2019 20:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 NmvQpYg1xznO for <eligibility-discuss@ietfa.amsl.com>; Mon,  3 Jun 2019 20:22:10 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 901FD120033 for <eligibility-discuss@ietf.org>; Mon,  3 Jun 2019 20:22:10 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id m29so6884391qtu.1 for <eligibility-discuss@ietf.org>; Mon, 03 Jun 2019 20:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NjZ6gB0lR8RnbTDkuxy5LMyvoxzJt4xXZYTTNR6tpBg=; b=Ca07VfK78ArVUSs8cA0tPiMXq3oPHrVwdffnCob8Mw2BRBRy/E+kgze788a0cx57DB zktzanpEje9DtVeH9l4z7b9UdOCl79ahqW46CxfJzsr7p6qs0fN7de4hTuODUd8EYPJT 9k6i9lp9upcL8uiGGvNMx72JfVrhLi5gjfvvdZ5wnncZiCs8wPWhUIFWe58UzSCZEHk2 RAAoJi1qJtIJ927kxVWbPL5MufPo2DbzP3dJuf6MyB5Pl1A5umUInTGqsuXDlwxjN+d7 mKVucTGhCMmP69+oYXvBgu5z5/UUqeSB83O37ETLB3O9oanRrxbXW2Gp7Yxqv23a/rxw +06g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NjZ6gB0lR8RnbTDkuxy5LMyvoxzJt4xXZYTTNR6tpBg=; b=r6WH9/TNgy9Ja2pCh11uKT5CDRBv7M/zApJwS1xoqOuD84DCjM8Dlmb+5qqAchVY+l Hr16AyujvBfcVzD4rZU/Ojd6QBtB7vDwp2qbNClRLn27NOE4kE3hVpXYQUryLpJ6w6Oz puMCjMco/sUhAGjNGAdNtmhINbXBEsG0LxpwYwe2j+zJCLTgAcbVRr5czz+AW/eD9GjO OBngJcWUaiD82MmiHgSYB68mED2iRi9AuG2DqMW9HE9AgT1mIero+4O1l+v48M+1ebNz MXycILD5Cg0/btMKaTpK0eXp+c3X6TfWGad04Nvz1SejzaNKGW2ZeRmpUaHZjCeZ6v4M wkag==
X-Gm-Message-State: APjAAAWs5xZAgnfyX1wx+0btEAZ39b1dkchwQsIcjS2IxuDlqx8ap6Sf NoCcvuS0SwWQpVVcLVMbGYg=
X-Google-Smtp-Source: APXvYqzapMX1lW1aNWJOGObfbXS8An1XIy5NYn4Vx6p0DtSkR2eaNi1ioKvnBOk8blWf9edV6sBfJw==
X-Received: by 2002:a0c:b92f:: with SMTP id u47mr24457106qvf.94.1559618529466;  Mon, 03 Jun 2019 20:22:09 -0700 (PDT)
Received: from [10.0.0.15] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id z12sm1151059qkf.20.2019.06.03.20.22.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jun 2019 20:22:08 -0700 (PDT)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Message-Id: <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4C25BAF3-58BB-4C03-9CC8-DC6FD39CC3CC"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 3 Jun 2019 23:22:07 -0400
In-Reply-To: <6.2.5.6.2.20190601204707.0bf89070@elandnews.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Warren Kumari <warren@kumari.net>, eligibility-discuss@ietf.org
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/8UWSQB6T_9gjxIn2rUTo3gv4RSs>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 04 Jun 2019 03:22:13 -0000

--Apple-Mail=_4C25BAF3-58BB-4C03-9CC8-DC6FD39CC3CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

HI SM,
  First of all, let me state that I am supportive of a proposal for a =
virtual BoF that covers the topics you mentioned. I have gone over the =
proposal and I think it needs to be refined further. In my mind, a =
virtual BoF proposal needs to have the same amount of thinking put into =
the problem statement, the deliverables, the questions to be answered as =
a in-person BoF proposal in order to be successful. i.e. As an AD I =
would expect the virtual BoF proposal to receive the same level of =
scrutiny as an in-person BoF proposal.=20

The problem statement in your mail concerning the virtual BoF, IMHO, =
does not fully cover the intent of the draft. e.g. It does not talk =
about why you are reducing the number of signatories. I think some text =
is required in this regard.=20

I would like the virtual BoF to clarify the following aspects

1) Does the community believe there is a problem to solve?
2) Which of the change proposals does the community support. I think =
some of the proposals in your draft are fairly non-controversial (e.g. =
reducing the number of signatories) while the others (e.g. Allowing I* =
to do so) might be more controversial.
3) What are the deliverables you expect to have?
4) How much support and energy is there in the community to make this =
change?

Also, mention whether you would like this to be a working group forming =
BoF or not. One other suggestion I would make is to put the virtual BoF =
request into=20

https://trac.tools.ietf.org/bof/trac/ =
<https://trac.tools.ietf.org/bof/trac/>

So that it can be considered along with the other BoF proposals when the =
IESG and IAB meet to consider the proposals for the Montreal IETF on =
June 11.

Thanks
Suresh

> On Jun 1, 2019, at 11:53 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Dear Area Directors,
>=20
> Over a week ago, I sent you a proposal for a virtual BOF [1].  Would =
it be possibel to get some feedback from you?
>=20
> Regards,
> S. Moonesamy
>=20
> 1. Please see =
https://mailarchive.ietf.org/arch/browse/eligibility-discuss/
>=20
> --=20
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss


--Apple-Mail=_4C25BAF3-58BB-4C03-9CC8-DC6FD39CC3CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">HI =
SM,<div class=3D"">&nbsp; First of all, let me state that I am =
supportive of a proposal for a virtual BoF that covers the topics you =
mentioned. I have gone over the proposal and I think it needs to be =
refined further. In my mind, a virtual BoF proposal needs to have the =
same amount of thinking put into the problem statement, the =
deliverables, the questions to be answered as a in-person BoF proposal =
in order to be successful. i.e. As an AD I would expect the virtual BoF =
proposal to receive the same level of scrutiny as an in-person BoF =
proposal.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">The problem statement in your mail concerning the virtual =
BoF, IMHO, does not fully cover the intent of the draft. e.g. It does =
not talk about why you are reducing the number of signatories. I think =
some text is required in this regard.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">I would like the virtual BoF to clarify =
the following aspects</div><div class=3D""><br class=3D""></div><div =
class=3D"">1) Does the community believe there is a problem to =
solve?</div><div class=3D"">2) Which of the change proposals does the =
community support. I think some of the proposals in your draft are =
fairly non-controversial (e.g. reducing the number of signatories) while =
the others (e.g. Allowing I* to do so) might be more =
controversial.</div><div class=3D"">3) What are the deliverables you =
expect to have?</div><div class=3D"">4) How much support and energy is =
there in the community to make this change?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Also, mention whether you would like =
this to be a working group forming BoF or not. One other suggestion I =
would make is to put the virtual BoF request into&nbsp;</div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://trac.tools.ietf.org/bof/trac/" =
class=3D"">https://trac.tools.ietf.org/bof/trac/</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">So that it can be =
considered along with the other BoF proposals when the IESG and IAB meet =
to consider the proposals for the Montreal IETF on June 11.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks</div><div =
class=3D"">Suresh<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Jun 1, 2019, at 11:53 PM, S =
Moonesamy &lt;<a href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Dear =
Area Directors,<br class=3D""><br class=3D"">Over a week ago, I sent you =
a proposal for a virtual BOF [1]. &nbsp;Would it be possibel to get some =
feedback from you?<br class=3D""><br class=3D"">Regards,<br class=3D"">S. =
Moonesamy<br class=3D""><br class=3D"">1. Please see <a =
href=3D"https://mailarchive.ietf.org/arch/browse/eligibility-discuss/" =
class=3D"">https://mailarchive.ietf.org/arch/browse/eligibility-discuss/</=
a><br class=3D""><br class=3D"">-- <br class=3D"">Eligibility-discuss =
mailing list<br class=3D""><a href=3D"mailto:Eligibility-discuss@ietf.org"=
 class=3D"">Eligibility-discuss@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss<br =
class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_4C25BAF3-58BB-4C03-9CC8-DC6FD39CC3CC--


From nobody Mon Jun  3 20:27:03 2019
Return-Path: <Suresh@kaloom.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 C4F7D12004B for <eligibility-discuss@ietfa.amsl.com>; Mon,  3 Jun 2019 20:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kaloom.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 GT5HZcfo0gUw for <eligibility-discuss@ietfa.amsl.com>; Mon,  3 Jun 2019 20:27:00 -0700 (PDT)
Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660122.outbound.protection.outlook.com [40.107.66.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B96A0120033 for <eligibility-discuss@ietf.org>; Mon,  3 Jun 2019 20:26:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaloom.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2wpK+xGrzS7os9DPKHFqZsVAYP7Rr2gkNxP87SYeQT4=; b=dOGff1HoQQ+6ctHlRqbmB67sOF62OvG91aMMMNSjrUDUDboHarDzowgJHTqQ3qIPWA918E9v6D2CHGY4LUBugB00q/At5lGfX01G1/NA+LwLdePDe0R/2vE4uZMDhDqATWUq5/AoCcIAZXhiff0JNn7PSbadaykFcVvegendZXo=
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM (52.132.45.144) by YTOPR0101MB2073.CANPRD01.PROD.OUTLOOK.COM (52.132.49.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Tue, 4 Jun 2019 03:26:57 +0000
Received: from YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::e11f:e72a:8da2:ea29]) by YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM ([fe80::e11f:e72a:8da2:ea29%7]) with mapi id 15.20.1943.018; Tue, 4 Jun 2019 03:26:57 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: Adrian Farrel <adrian@olddog.co.uk>
CC: "Eliot Lear (elear)" <elear@cisco.com>, "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
Thread-Topic: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev
Thread-Index: AQHVE0Oz6aSSoT6KkkabJwidjbUDl6Z8ZVeAgAAIH4CAAL8wAIAABuOAgAAbN4CAAAY5AIANjzgA
Date: Tue, 4 Jun 2019 03:26:56 +0000
Message-ID: <286F859E-2BC5-4810-9CFB-7447E4F32575@kaloom.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <FDDEFD82-E276-4874-896E-490397EDA735@akamai.com> <6.2.5.6.2.20190525151934.0c0099e0@elandnews.com> <7D195412-2A8E-44FC-9144-B7C48F33EE5C@cisco.com> <067001d513ad$09739f60$1c5ade20$@olddog.co.uk> <1F0265EE-0686-4DF7-9A74-93F6D6C8CA47@cisco.com> <067701d513bd$c1bec7b0$453c5710$@olddog.co.uk>
In-Reply-To: <067701d513bd$c1bec7b0$453c5710$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Suresh@kaloom.com; 
x-originating-ip: [45.19.110.76]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5443586a-1d01-4fb1-6e25-08d6e89c7f7b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(2017052603328)(7193020); SRVR:YTOPR0101MB2073; 
x-ms-traffictypediagnostic: YTOPR0101MB2073:
x-microsoft-antispam-prvs: <YTOPR0101MB207311088FD2C3366C95C1FCB4150@YTOPR0101MB2073.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-forefront-prvs: 0058ABBBC7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(376002)(396003)(39850400004)(366004)(189003)(199004)(446003)(14454004)(102836004)(508600001)(73956011)(53546011)(76176011)(53936002)(6246003)(2906002)(6916009)(54906003)(99286004)(2616005)(66446008)(64756008)(66556008)(66476007)(25786009)(476003)(486006)(66946007)(71190400001)(316002)(71200400001)(83716004)(3846002)(6116002)(91956017)(11346002)(72206003)(82746002)(76116006)(81156014)(68736007)(81166006)(8936002)(6486002)(66066001)(6506007)(86362001)(5660300002)(6436002)(7736002)(229853002)(26005)(8676002)(186003)(6512007)(256004)(36756003)(4326008)(33656002)(305945005)(80792005); DIR:OUT; SFP:1102; SCL:1; SRVR:YTOPR0101MB2073; H:YTOPR0101MB1819.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: kaloom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: yg60KEa5HZkQyMhIjmzABvKGjDsC5nSQeIhbdBpPOt/LrJoDw0a4j/BIJ4uw4wUFrkFTtcymb3rRnUVn3SnTI3vY3cIcizjmZN+F5/wQIrhL+IPO2gwuHW73r7OcSYJ4sExFQ75IwgcMbhiioDpMN7M60dmcOXvjhuE3wyh9/C/UDIMf/jvA1uQLhwtqjk9CdRKhX9zBVO4eNkTYdo0wvpuKM38vg+SmgvnDvYXHP2plCfA7FNPQ8Tt7FaMMq8yo6JE/7zQAkSmMh52Zi+dDPBPpCjtOKS9v/4mJ6D4KFfSFog8/U2ACHsTJ4rOwKUZLtMGeLZV+3rDiJAwDUa2ruSz4DSSPGKmj6QYb0QHim4lNxPK5VPiwSTRJJ8zE33FEgNyVmt0EodxjXF/6MVEQS7U2TcBagMb4mKUT8DOa3r0=
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C7E1BBE7A84BDC4E8BCEF8CFE90892E5@CANPRD01.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5443586a-1d01-4fb1-6e25-08d6e89c7f7b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2019 03:26:56.9632 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 47d58e26-f796-48e8-ac40-1c365c204513
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Suresh@kaloom.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2073
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/NvgD3h-3JMmKYgN5MaOgw5vXV1E>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 04 Jun 2019 03:27:02 -0000

Hi Adrian,

<No Hats>

> On May 26, 2019, at 8:22 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>=20
> I probably can't speak to the cases you describe.
>=20
> I did once start to put together a recall petition for an AD (so long ago=
 that we need not dwell on the details). I found that collecting cosignator=
ies was slow, but for good reasons. People generally said "Yes, bad stuff i=
s happening, but recall is pretty serious. Can we think about other ways of=
 handling this?". And, indeed, once the seriousness got discussed a bit, th=
e AD concerned modified their behaviour (coincidence is not causation).
>=20
> The process did not seem unwieldy to me, but making it more wieldy (for e=
xample by reducing the number of signatures needed) does not seem to be a b=
ad idea to me. In fact, it is part of SM's draft, IIRC.=20

 I agree with you. I think this could be a fairly non-baseline improvement.=
=20

>=20
> However, adding a new process that allows removal of a community appointm=
ent by other than the community looks like a way of just increasing the cha=
nces of appeals and additional recalls.

I am not entirely sure about this. I think the body in question might have =
more information than the community at large in some cases. In these cases =
allowing the body to self-correct may be useful. But I do see the concerns =
about potential ways in which this can be abused.

> I think it is a discussion we could have, but I also think it is independ=
ent of SM's proposals.

Agree.

Thanks
Suresh


From nobody Tue Jun  4 12:49:43 2019
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 719B61205D9 for <eligibility-discuss@ietfa.amsl.com>; Tue,  4 Jun 2019 12:49:41 -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, 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=opendkim.org header.b=V2HblGad; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=JymFnpxR
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 MxvsugwFVV0l for <eligibility-discuss@ietfa.amsl.com>; Tue,  4 Jun 2019 12:49:40 -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 6C5FB12013B for <eligibility-discuss@ietf.org>; Tue,  4 Jun 2019 12:49:40 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.54.167]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x54JnIhP016734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jun 2019 12:49:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1559677771; x=1559764171; bh=qCyQRMZAly2FtvYxKjRl0Db8JCEBDb0bTSTV+XDrvn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=V2HblGadZhNE+Lu8XN1sQS+sEWFY40BOIsaUGK5Y2SQaelLMZRiW8VX1APIFrQqoC xGMOx0DmbmcLXoRQidulrIcZKQmBcShDud3TNyjekAwoGSLQOuUG/1CTU3qbP8VOiz HsXZCTrBZv9PTNwoL19zqMLoo5Rq5S73ue9LMYuI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1559677771; x=1559764171; i=@elandsys.com; bh=qCyQRMZAly2FtvYxKjRl0Db8JCEBDb0bTSTV+XDrvn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JymFnpxRB7ZF8se31SN9uQczu0uJBoxwXgiNaYs4EUoO2DIFuM+DgjTlYYeHcq2ui DzJzgvrnoTEG2l+8JhjH6BTf/0aXpAe/xSE5Nalz7NfWa4fk5kUaUvbBdrVMy9Ud1k xjFhZNiMX3nkoI5130BLpvrKV40I8lCpKJhz+3Y0=
Message-Id: <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 04 Jun 2019 12:49:01 -0700
To: Suresh Krishnan <suresh.krishnan@gmail.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Warren Kumari <warren@kumari.net>
In-Reply-To: <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@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/nP-Ds6bhQqmEjdvrlSrdWng2KAY>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 04 Jun 2019 19:49:42 -0000

Hi Suresh,
At 08:22 PM 03-06-2019, Suresh Krishnan wrote:
>Also, mention whether you would like this to be a working group 
>forming BoF or not. One other suggestion I would make is to put the 
>virtual BoF request into

Thank you for responding.

The advice from the IETF Chair was to have a BOF to process the 
draft.  I approached the Area Directors, as suggested by the IETF 
Chair, about the BOF.  Could Warren, Alexey or you provide some 
expert advice on whether a working group forming BoF should be requested?

Regards,
S. Moonesamy 


From nobody Wed Jun  5 07:11:09 2019
Return-Path: <john-ietf@jck.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 3F04D1200B3 for <eligibility-discuss@ietfa.amsl.com>; Wed,  5 Jun 2019 07:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 GBRcHoctUE3n for <eligibility-discuss@ietfa.amsl.com>; Wed,  5 Jun 2019 07:11:06 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4656C120046 for <eligibility-discuss@ietf.org>; Wed,  5 Jun 2019 07:11:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hYWd3-000DSn-KI; Wed, 05 Jun 2019 10:11:01 -0400
Date: Wed, 05 Jun 2019 10:10:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
cc: eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <35ECCB711814EE331938E6C7@PSB>
In-Reply-To: <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/-Z9DUeA06AB8xSH7k4EbCJtLWIc>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Wed, 05 Jun 2019 14:11:08 -0000

Suresh (and Alexey and Warren),

It seems to me that there are two, quite different, possible BOF
proposals and that the community could use a little guidance
from the three of you about what the IESG is looking for.

One is the result of the direction in which Subramanian seems to
be heading and that reflects the actual content of
draft-moonesamy-recall-rev.  That is a very narrow set of
changes to fine-tune the existing recall procedure to allow a
set of people who do not meet the "Nomcom eligibility"
requirement because they do not attend sufficient f2f meeting no
matter how active they are in the IETF, to reduce the number of
signatures required to initiate a recall because the current
number is seen as burdensome (especially for people who can't
collect them by, e.g., passing a sheet of paper around at a
plenary), and by allowing people in the leadership to initiate
recall efforts (not only for the bodies on which they sit but
for other bodies).  The latter, which has almost nothing to do
with remote participants, could easily be dropped if there was
no support for it but I note that, draft-rescorla-istar-recall
is largely orthogonal to the change proposed in the present
draft: even if it were adopted, the proposed change would still
be worth careful consideration for cases in which, e.g., the
IESG felt there was a serious problem in the LLC Board.  The
proposal doesn't "fix" the recall procedure, it merely tunes its
first step a bit.

My personal opinion is that, if the scope is as narrow as the
"fine-tune the recall procedure in that way" implied above, a
BOF, virtual or otherwise, would be a waste of time -- there has
already been enough discussion to indicate community interest
and we should move forward to discussing the draft (and not
procedures for doing so).  If you are convinced that needs a
short-lived WG to, e.g., avoid getting sidetracked, we should be
working on a charter for that WG with the expectation that its
approval will be expedited, not going through an elaborate set
of rituals that are not required by IETF procedures.  On the
other hand, if you are convinced that a quick virtual BOF would
be helpful, let's get on with it.

At the other extreme, perhaps the posting of this draft has
convinced the IESG that it is time to open up the entire
candidate selection and removal process and review it.  That
would (or at least might) include the nomcom eligibility
criteria; questions about whether the nomcom model itself is
appropriate in a contemporary IETF for which the implied
assumption that most of the nomcom members would have personal
knowledge of most of the candidates is no longer valid;
questions of term lengths, limits (or preferences), and
incumbent preferences; questions of whether, as the number of
bodies and slots for which the nomcom is expected to make
appointments has risen, having a single body do all of that work
in a single cycle is still appropriate; examination of whether,
in the environment of the IETF LLC having the ISOC President and
CEO appoint the Nomcom (and Recall Committee) chairs is still
appropriate both practically and from the standpoint of optics;
whether we can devise a mechanism for mid-term removal of people
who have misbehaved that is faster and more plausible than the
present petition, chair appointment, and two consecutive
committee model (or whether no such procedure is needed); and
perhaps even some issues that overlap into the old NEWTRK
effort.   That is obviously not a complete list: I'm confident
that you could add some things to it and that, given a few
hours, I probably could too.   

If that is the BOF proposal/charter you and the rest of the IESG
want, then it probably would benefit from a f2f discussion and
some of us should see if we can get a proposal for a BOF in
Montreal together within the next 48 hours.  However, any of us
who have either tried writing I-Ds that propose adjustments in
those areas or who have been through opening up some of the
issues in WGs know that it will be a long, time and resource
intensive, trek with many passionately-expressed opinions.
Based on experience with POISSON, I think it would be
unrealistic to expect a WG with that task list to converge and
complete its work in less than two or three years. Even were
that much time to be available, it would be nearly impossible to
get to significant conclusions without enthusiastic IESG support
for reviewing things and making changes as needed, support that
would need to be independent of whatever changes the WG and
community select.   Unless you can assure us that the conviction
and enthusiasm exist, even holding a BOF, much less chartering a
WG, would, IMO, be a waste of time that the IETF could better
spend on technical work.

Even if a BOF proposal for this larger effort were wanted and if
only because how long that effort would take, I think there is a
very strong case for addressing the fine-tuning proposal now and
getting it done with.  They really are separate efforts even
though we might reasonably expect the larger one to make changes
that would obsolete some or all of the smaller and faster one.

So, what would you like to see and how are you and the IESG
thinking about this?

Just my opinion but, perhaps unfortunately, one that is informed
by experience.

   john



--On Tuesday, June 4, 2019 12:49 -0700 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> Hi Suresh,
> At 08:22 PM 03-06-2019, Suresh Krishnan wrote:
>> Also, mention whether you would like this to be a working
>> group  forming BoF or not. One other suggestion I would make
>> is to put the  virtual BoF request into
> 
> Thank you for responding.
> 
> The advice from the IETF Chair was to have a BOF to process
> the draft.  I approached the Area Directors, as suggested by
> the IETF Chair, about the BOF.  Could Warren, Alexey or you
> provide some expert advice on whether a working group forming
> BoF should be requested?
> 
> Regards,
> S. Moonesamy 





From nobody Thu Jun  6 19:28:21 2019
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 DD6441200FF for <eligibility-discuss@ietfa.amsl.com>; Thu,  6 Jun 2019 19:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 Vl6oxSIOZur8 for <eligibility-discuss@ietfa.amsl.com>; Thu,  6 Jun 2019 19:28:17 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 811ED1200F8 for <eligibility-discuss@ietf.org>; Thu,  6 Jun 2019 19:28:17 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id i34so623200qta.6 for <eligibility-discuss@ietf.org>; Thu, 06 Jun 2019 19:28:17 -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=5PVuoL9v7OfKt0I13jP0aaT9EKp3S0BobshJnObK5O0=; b=B6g34JVVWn2UST9TzXi86m19KuPgty4F4/TYPHCQ/bq6qU9GqVNvc9xSDfcbGUFxmz 9SUVE6oUYGlQVQmup65yUIpQ0YJvc3tpLJWkShBjCuPasxjuufPbRVBD5WPm41wBVOpO l3AD0dS7o4BqA2UHQZetju37UUObLUA/vE9zb/yzTDMOFveAK81m4pHkc+NwKjxbt0OD AY/cjCXYwxX2b7vHtOZmmXFwPUrEdkhk/QvqeKAT5JA567KNgauT2xyB+9t7Y9Dlc1ss J39iApVa/dXxCcPgbMMEE5j3Df7JcY/TaURV5uGYf8Z9Dcfaw8ieqUmMAYLYj5utnZR3 j7NA==
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=5PVuoL9v7OfKt0I13jP0aaT9EKp3S0BobshJnObK5O0=; b=MqOj5uh2cTZFMey0zx0In4wH46euU/sbMKORypTbb+Q2PNDHXWnAR5yloj4MNbwLSD Vp8KsvlNlAhq7VNRfhCwb5+lwwAbIekoqnhOHDU7hczfx4C3jIfm1cf+RjevlU3bhkKS v1eWIFUw6uBxpgioYCpu76Ms66kcEHsp4V8p3qBlpIOE0qNshEelWOArjXvLO1zbotoX AUqpSFrz8uVzuScBfgNboAxefiXcBIHDwaw1H0LZtUJuF2KEKFINmREX94NJdtTtg8ov 67fKeeJ0ehz2l9n0T7jETV+9TgK88ikHstcEKeI08QYTm9hhVImp1yoxwdRvA8UrfH9Y +iPg==
X-Gm-Message-State: APjAAAUMjQr2N6w9pFdcqRN9mFrEl+8OEmaWZLlALtNP6qV61eDutOa2 6hTyrTmhm3lDKDCxDACc6s4=
X-Google-Smtp-Source: APXvYqzA3hiLrwlYKQQuALUwuR8pPX2rTZkt+OxCrsR9V2WIb5tYkkH8ufWzORLXEh2apXJyySsOpA==
X-Received: by 2002:ac8:7652:: with SMTP id i18mr35719513qtr.10.1559874496581;  Thu, 06 Jun 2019 19:28:16 -0700 (PDT)
Received: from [10.0.0.15] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id v186sm376664qkc.36.2019.06.06.19.28.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 19:28:15 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
Date: Thu, 6 Jun 2019 22:28:14 -0400
Cc: eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Transfer-Encoding: quoted-printable
Message-Id: <942E0B4F-1A9D-4154-84E4-2CDCD8876BF4@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/_3FIkyAPgQUpvfbynwojUlHuJgg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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, 07 Jun 2019 02:28:19 -0000

Hi SM,

> On Jun 4, 2019, at 3:49 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Hi Suresh,
> At 08:22 PM 03-06-2019, Suresh Krishnan wrote:
>> Also, mention whether you would like this to be a working group =
forming BoF or not. One other suggestion I would make is to put the =
virtual BoF request into
>=20
> Thank you for responding.
>=20
> The advice from the IETF Chair was to have a BOF to process the draft. =
 I approached the Area Directors, as suggested by the IETF Chair, about =
the BOF.  Could Warren, Alexey or you provide some expert advice on =
whether a working group forming BoF should be requested?

Just speaking for myself here. I think this depends on how you want to =
scope the discussion. If you can go with a fairly narrow set of goals =
with a defined scope and deliverables, I think a WG forming BoF would be =
a good idea. If you want to explore the problem space a bit, I think a =
non-WG forming BoF might be a better fit.

Thanks
Suresh


From nobody Thu Jun  6 20:14:46 2019
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 03E261200F8 for <eligibility-discuss@ietfa.amsl.com>; Thu,  6 Jun 2019 20:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 Ilmo6Mypg6Yv for <eligibility-discuss@ietfa.amsl.com>; Thu,  6 Jun 2019 20:14:41 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 9D43812010D for <eligibility-discuss@ietf.org>; Thu,  6 Jun 2019 20:14:41 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id b18so406254qkc.9 for <eligibility-discuss@ietf.org>; Thu, 06 Jun 2019 20:14:41 -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=8+k6bbJzM+9STsQfFsAQFq+YAHL2C0AD85BYrMDeoHY=; b=LBxi8yJjQ7jUuUdpmgfc0rUmX288oLgm1EfoMrJqlP7MsZ0Ij/YysUdiJy4ljXx1tZ zj5j4/XDqul5F6DU0w3/7UgLYRH54CEm8Xim/uHGErWY5ksYpAW4Hoh835ECwF4+GoeQ bjrkGEbUttWH1FDetMjsBGn8krQKU1UPaH7Lewwsb/0Y9wjh7j3Ypozmgd3j2FvL9KeT FafaqeUm+1Zyitt/ZRYkoH0Qj+BLNAkpqQFG6r3gKiTZ2yQ9Cx0c0sBmjB0j/Li46Ba1 PcpXk1lSJ8kT8eqHzJCIfT+8vtxTgkBZKox4Xy/2YnMlMWaX4+TUo6WzUeOxCERz7nv9 p/cg==
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=8+k6bbJzM+9STsQfFsAQFq+YAHL2C0AD85BYrMDeoHY=; b=QpcdSoSxtgHeCFTeCTGfxHnUXUNnfcFObeAi78NqNWqASsJwuN4DjK2AgeabVSBslQ 1QvthNbPIU1ly7wDPtFH0/iqmETF1AWtf/yrto4Po5odgqpgx7KNkQP4XcbJVRwmrwzU ggjB3FmsA4W6rw/qXBmnYqylOJPa3JZ5j7jFP6fDdAt2i8OihcL2R1sq63PIViCM/2jq LZDWraNpTDvHd6uq/ytr8w/kVhgY7ckJmd0Nivsprdj8lxn+GmzwhfdPxCtgEAB86N4L PcuZE33fSPbPN3AiPiP6ITHqx0gXZl+PUnkT5pZQ5Vq6/LxhXELGWfGf0cg+fSRYFJKU +n1A==
X-Gm-Message-State: APjAAAVAOq8mZMc0l/600ewNJBRx11HWtKAwUSPlHBa9ooKg4i2pn/KC 0ikgdk26bVkmiEk1OApHO08=
X-Google-Smtp-Source: APXvYqzy6r9CQAGJIS3FQVStPyzxeCN1FaRYLsIngHeFZrawaAQ9fEDpUz4IfDfIELE0Lafb3jQXtQ==
X-Received: by 2002:a37:dd4:: with SMTP id 203mr42418431qkn.326.1559877280299;  Thu, 06 Jun 2019 20:14:40 -0700 (PDT)
Received: from [10.0.0.15] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id y42sm623456qtc.66.2019.06.06.20.14.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jun 2019 20:14:39 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <35ECCB711814EE331938E6C7@PSB>
Date: Thu, 6 Jun 2019 23:14:38 -0400
Cc: S Moonesamy <sm+ietf@elandsys.com>, Warren Kumari <warren@kumari.net>, eligibility-discuss@ietf.org, Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Transfer-Encoding: quoted-printable
Message-Id: <06BAD820-C035-4822-B908-51992E24DE5A@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com> <35ECCB711814EE331938E6C7@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/InbDQ7a7Vz-TSE9Cq35J1ESm7Dk>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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, 07 Jun 2019 03:14:44 -0000

Hi John,

> On Jun 5, 2019, at 10:10 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> Suresh (and Alexey and Warren),
>=20
> It seems to me that there are two, quite different, possible BOF
> proposals and that the community could use a little guidance
> from the three of you about what the IESG is looking for.

Just speaking for myself here. I do have my preference (see below), but =
I will leave it up to the proponents to decide which way they want to =
go.

>=20
> One is the result of the direction in which Subramanian seems to
> be heading and that reflects the actual content of
> draft-moonesamy-recall-rev.  That is a very narrow set of
> changes to fine-tune the existing recall procedure to allow a
> set of people who do not meet the "Nomcom eligibility"
> requirement because they do not attend sufficient f2f meeting no
> matter how active they are in the IETF, to reduce the number of
> signatures required to initiate a recall because the current
> number is seen as burdensome (especially for people who can't
> collect them by, e.g., passing a sheet of paper around at a
> plenary), and by allowing people in the leadership to initiate
> recall efforts (not only for the bodies on which they sit but
> for other bodies).  The latter, which has almost nothing to do
> with remote participants, could easily be dropped if there was
> no support for it but I note that, draft-rescorla-istar-recall
> is largely orthogonal to the change proposed in the present
> draft: even if it were adopted, the proposed change would still
> be worth careful consideration for cases in which, e.g., the
> IESG felt there was a serious problem in the LLC Board.  The
> proposal doesn't "fix" the recall procedure, it merely tunes its
> first step a bit.
>=20
> My personal opinion is that, if the scope is as narrow as the
> "fine-tune the recall procedure in that way" implied above, a
> BOF, virtual or otherwise, would be a waste of time -- there has
> already been enough discussion to indicate community interest
> and we should move forward to discussing the draft (and not
> procedures for doing so).  If you are convinced that needs a
> short-lived WG to, e.g., avoid getting sidetracked, we should be
> working on a charter for that WG with the expectation that its
> approval will be expedited, not going through an elaborate set
> of rituals that are not required by IETF procedures.  On the
> other hand, if you are convinced that a quick virtual BOF would
> be helpful, let's get on with it.

This would be my preference. As I said in my earlier mail, if we can =
separate the three pieces of the draft and see how the community feels =
about each of them, I think we will be in a good spot to looking at =
writing a narrowly scoped charter for a WG.
=20
>=20
> At the other extreme, perhaps the posting of this draft has
> convinced the IESG that it is time to open up the entire
> candidate selection and removal process and review it.  That
> would (or at least might) include the nomcom eligibility
> criteria; questions about whether the nomcom model itself is
> appropriate in a contemporary IETF for which the implied
> assumption that most of the nomcom members would have personal
> knowledge of most of the candidates is no longer valid;
> questions of term lengths, limits (or preferences), and
> incumbent preferences; questions of whether, as the number of
> bodies and slots for which the nomcom is expected to make
> appointments has risen, having a single body do all of that work
> in a single cycle is still appropriate; examination of whether,
> in the environment of the IETF LLC having the ISOC President and
> CEO appoint the Nomcom (and Recall Committee) chairs is still
> appropriate both practically and from the standpoint of optics;
> whether we can devise a mechanism for mid-term removal of people
> who have misbehaved that is faster and more plausible than the
> present petition, chair appointment, and two consecutive
> committee model (or whether no such procedure is needed); and
> perhaps even some issues that overlap into the old NEWTRK
> effort.   That is obviously not a complete list: I'm confident
> that you could add some things to it and that, given a few
> hours, I probably could too.  =20

Just my personal opinion with no hats at all. I think this will be a =
=E2=80=9Cboil the ocean=E2=80=9D effort and I am not at all confident =
about its odds of success.

>=20
> If that is the BOF proposal/charter you and the rest of the IESG
> want, then it probably would benefit from a f2f discussion and
> some of us should see if we can get a proposal for a BOF in
> Montreal together within the next 48 hours.  However, any of us
> who have either tried writing I-Ds that propose adjustments in
> those areas or who have been through opening up some of the
> issues in WGs know that it will be a long, time and resource
> intensive, trek with many passionately-expressed opinions.
> Based on experience with POISSON, I think it would be
> unrealistic to expect a WG with that task list to converge and
> complete its work in less than two or three years. Even were
> that much time to be available, it would be nearly impossible to
> get to significant conclusions without enthusiastic IESG support
> for reviewing things and making changes as needed, support that
> would need to be independent of whatever changes the WG and
> community select.   Unless you can assure us that the conviction
> and enthusiasm exist, even holding a BOF, much less chartering a
> WG, would, IMO, be a waste of time that the IETF could better
> spend on technical work.

I whole-heartedly agree with you that this would probably be a waste of =
time.

>=20
> Even if a BOF proposal for this larger effort were wanted and if
> only because how long that effort would take, I think there is a
> very strong case for addressing the fine-tuning proposal now and
> getting it done with.  They really are separate efforts even
> though we might reasonably expect the larger one to make changes
> that would obsolete some or all of the smaller and faster one.
>=20
> So, what would you like to see and how are you and the IESG
> thinking about this?
>=20
> Just my opinion but, perhaps unfortunately, one that is informed
> by experience.

Much appreciated. I agree with you that a tightly scoped effort is more =
likely to succeed.=20

Thanks
Suresh


From nobody Fri Jun  7 10:54:49 2019
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 BE84A1200B4 for <eligibility-discuss@ietfa.amsl.com>; Fri,  7 Jun 2019 10:54:47 -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, 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=opendkim.org header.b=PSlTLP+x; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=iCoLrjD4
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 iq8TO2W1N7Yl for <eligibility-discuss@ietfa.amsl.com>; Fri,  7 Jun 2019 10:54:46 -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 EDD6212011F for <eligibility-discuss@ietf.org>; Fri,  7 Jun 2019 10:54:45 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.49.130]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x57HsLoB025853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jun 2019 10:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1559930080; x=1560016480; bh=AINR3i/UdZcbzoSQ8/wv0kCIe0lrsrCnLP6AL1R3nmM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PSlTLP+xAijwcVcxWmHpC2c3wlfUeMm/LeC9tVXMczydiFoOYxllHVZ+AfFAs0kvu yLDrzUwine2Ya9ERfoc2/hbtYzSGi3H05eldraowo6w3iqm39ocImIMrjee5hV28cx XIo0WfR6+2E23SOMHtM6oBgO9ryL3Y7MzZOxoQk4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1559930080; x=1560016480; i=@elandsys.com; bh=AINR3i/UdZcbzoSQ8/wv0kCIe0lrsrCnLP6AL1R3nmM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iCoLrjD41IxB2xZ260i7wegxi30QLnOO5+M9OiiP0xZ+pxUyQ0QzMur7S3IhtFtKV gynieo7z7CpaTM1lxZwoVpEQdWYC3VIMBsdF8CMBnmj1E2YcmcmQU9WcV0nBrEozDQ Kqtvl1s7RA2VOoNHkLCdw15YHZo2o2Y9CanF/E1Y=
Message-Id: <6.2.5.6.2.20190607104702.0cf93198@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Jun 2019 10:53:51 -0700
To: Suresh Krishnan <suresh.krishnan@gmail.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <942E0B4F-1A9D-4154-84E4-2CDCD8876BF4@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com> <942E0B4F-1A9D-4154-84E4-2CDCD8876BF4@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/HM3r95VmX7U_IwirQsc0p-DvQFY>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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, 07 Jun 2019 17:54:48 -0000

Hi Suresh,
At 07:28 PM 06-06-2019, Suresh Krishnan wrote:
>Just speaking for myself here. I think this depends on how you want 
>to scope the discussion. If you can go with a fairly narrow set of 
>goals with a defined scope and
>  deliverables, I think a WG forming BoF would be a good idea. If 
> you want to explore the problem space a bit, I think a non-WG 
> forming BoF might be a better fit.

Thank you for the feedback.

The time commitment to explore the problem space would likely be too 
high for me to fit that into my current schedule.

Regards,
S. Moonesamy 


From nobody Tue Jun 11 03:47:15 2019
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 687691200C7 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 03:47:14 -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, 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=opendkim.org header.b=CnVEwDPP; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=dn2zWGEz
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 wFN1qbZycopR for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 03:47:13 -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 CD9DD120140 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 03:47:13 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.213]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x5BAknlI019677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jun 2019 03:46:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1560250025; x=1560336425; bh=dWei1n9g7e0JJRBmaxdvzuDcQam7Ye8uxsrBP5dzEDs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CnVEwDPPlzMtIGBScee6192ibCWIsW7G58EEg+6DPNO5v91kSk2FYxms/49qUP8gY u2wUlsevO/JMJ8Kek/jVRu+n2M8u0jwoSHpjQ4xjE8jY+TIoaWPwd+S/qcrOCdPTbz QVzqSMia/oYPaP/8BysUlMhAnSERr2TVDRnBUFpY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1560250025; x=1560336425; i=@elandsys.com; bh=dWei1n9g7e0JJRBmaxdvzuDcQam7Ye8uxsrBP5dzEDs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dn2zWGEzf2ccCQd8sisfvAXFHamgK/OxAxAADmiE+vtuKEq+xR+c7W1zBhumUE1hJ tOsB48uvDdlAkhrOsDtbx3agte7H7hKJunx5B3CbVK+hxU38sM1GIPy+mBpM1vohm3 mR00zEjrzKd6FU6eV41oljTwt33/zO5IRfTZrfEE=
Message-Id: <6.2.5.6.2.20190611033500.0c619e48@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jun 2019 03:45:20 -0700
To: Suresh Krishnan <suresh.krishnan@gmail.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Warren Kumari <warren@kumari.net>, John C Klensin <john-ietf@jck.com>
In-Reply-To: <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@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/nvuFy42SRQEU-MCl-VbLBxtsDfg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 10:47:14 -0000

Hi Suresh,

Please see a revised version of the BOF proposal to address your comments:

Problem statement

      The current description of the process for initiating petitions 
for recalls
      for NomCom-appointed roles is described in RFC 7437 and is 
being updated in
      draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only three
      specific issues with the petition process; other parts of the 
recall model
      and other ways of removing Nomcom-appointees are explicitly out of scope.

      The three issues are:

      - Ineligibility of remote participants to seek redress through the
        recall process;

      - Reducing the number of signatories for a recall petition;

      - Ineligibility of IAB and IESG Members and other Nomcom
        Appointees to sign a recall petition.

The purpose of the BOF is to examine the above-mentioned issues and determine,
for each, whether it is sufficient interest and importance. 
draft-moonesamy-recall-rev
is a possible starting point for the effort.

Regards,
S. Moonesamy


From nobody Tue Jun 11 04:22:24 2019
Return-Path: <adrian@olddog.co.uk>
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 1A602120131 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 04:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 4s1-tdm9FShD for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 04:22:20 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 541F812000E for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 04:22:20 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5BBLBVq006974; Tue, 11 Jun 2019 12:21:35 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9CF1C2203A; Tue, 11 Jun 2019 12:21:34 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id 86C862203D; Tue, 11 Jun 2019 12:21:34 +0100 (BST)
Received: from LAPTOPK7AS653V (25.129.51.84.dyn.plus.net [84.51.129.25] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5BBLXpZ023286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 12:21:33 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'S Moonesamy'" <sm+ietf@elandsys.com>, "'Suresh Krishnan'" <suresh.krishnan@gmail.com>, <eligibility-discuss@ietf.org>
Cc: "'John C Klensin'" <john-ietf@jck.com>, "'Warren Kumari'" <warren@kumari.net>, "'Alexey Melnikov'" <aamelnikov@fastmail.fm>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com>
In-Reply-To: <6.2.5.6.2.20190611033500.0c619e48@elandnews.com>
Date: Tue, 11 Jun 2019 12:21:32 +0100
Organization: Old Dog Consulting
Message-ID: <065101d52047$d35ea620$7a1bf260$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFR42vyAucRjBtXO+m4xnaMV3ichgHs2gIPAxJf1rwBYZyWF6dpwPDA
Content-Language: en-gb
X-Originating-IP: 84.51.129.25
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24668.007
X-TM-AS-Result: No--9.997-10.0-31-10
X-imss-scan-details: No--9.997-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24668.007
X-TMASE-Result: 10--9.996900-10.000000
X-TMASE-MatchedRID: 9d2LtCNB3NLxIbpQ8BhdbMLRNemq17EiySf7HrQn3BptpkxrR+BG1lzT Kp++bzfF2hRWt8Blqlp1puXYN+PAvcEElERnDJHC0H8ihGEHNUdDdtobO2eZiWso23uKlCJjaXK zU8OFYui6D4zFLzK4rKDEBNi1lexNNmWNgiKcHndQ+S0N05fR+yIk3dpe5X+hLrb+wM+3z+KcvF BvqoNK+1FWRHF0dngvvqsaQIQa9Xs3ohqtjZUuxZSHVES5ghPh6TL3myIORk9SasGAkNQYrM79P lJmAmXDPgh6K149Lq2QiLJmDGsjCn9oXId4GW5yGJADAbBHGUxRvgR0hkbG4CBwR3y4lKPE0HCC 1wXiE/L7lStE1jOSEO2PEz9K9CO1vAJ338codddEIsnfsaOGrL1ZYuGtBm4a8CWGWvy/Nx2XmkT 7awT4edLHcrEX4rAUKh6jYUGL6hI2UEKHDN0wzMK1Ib9JAALxktBHfvLK/JqbKItl61J/ycnjLT A/UDoAMwyzN4BmnMl0HSe131POnjsAVzN+Ov/sw5uXquFvFWMgXn/hwq2+wsAaMFtXRPe12FGv8 nw0OlT3A7ZlyiMaQg==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/3YXzKQbmfk1bsDDD3wg1ce4p7Bg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 11:22:23 -0000

That's nice. I like the clarity.

I also like that the worms are kept firmly in their cans. It is without
doubt that a hundred other issues concerning the recall process could be
aired, and I am certain that many people have different hot issues. But I
firmly believe that addressing a few at a time is the best (only!) way to
make progress.

If it turns out that there is support for resolving any of these three
issues, they can be quickly picked off and we can move on to other issues if
there is interest. If there is no support for addressing these three
concerns, then they can be put to one side and work can start on other
issues if there is interest.

For my part, I think that all three issues should be addressed, and I think
that the approaches suggested in SM's draft are a good starting point for
discussion.

Thanks,
Adrian

-----Original Message-----
From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On Behalf
Of S Moonesamy
Sent: 11 June 2019 11:45
To: Suresh Krishnan <suresh.krishnan@gmail.com>;
eligibility-discuss@ietf.org
Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net>;
Alexey Melnikov <aamelnikov@fastmail.fm>
Subject: Re: [Eligibility-discuss] Virtual BoF for
draft-moonesamy-recall-rev

Hi Suresh,

Please see a revised version of the BOF proposal to address your comments:

Problem statement

      The current description of the process for initiating petitions 
for recalls
      for NomCom-appointed roles is described in RFC 7437 and is 
being updated in
      draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only
three
      specific issues with the petition process; other parts of the 
recall model
      and other ways of removing Nomcom-appointees are explicitly out of
scope.

      The three issues are:

      - Ineligibility of remote participants to seek redress through the
        recall process;

      - Reducing the number of signatories for a recall petition;

      - Ineligibility of IAB and IESG Members and other Nomcom
        Appointees to sign a recall petition.

The purpose of the BOF is to examine the above-mentioned issues and
determine,
for each, whether it is sufficient interest and importance. 
draft-moonesamy-recall-rev
is a possible starting point for the effort.

Regards,
S. Moonesamy

-- 
Eligibility-discuss mailing list
Eligibility-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/eligibility-discuss


From nobody Tue Jun 11 04:38:16 2019
Return-Path: <ekr@rtfm.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 14B5A120112 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 04:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 hRiQq_Ke7Jbi for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 04:38:12 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 3CEB512011F for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 04:38:12 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id o13so11265912lji.5 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 04:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q4N50os/pm/clZIqIIXFDs1nVEg4wHJBoPpYfo2Rm10=; b=eyLNtCLJa6/pNIvt+MuMeZtv1Cw/Qdkg1+qbl97SGMf6cYhPnXhjmKarEzU82cqOcW pUx0hsLII5D5Y86pvMMpP7kot4hypbeYl6uueBe4Xn3/WpASjnMchFEHwYbnM7aPyK9F Jm2ut1F0M/s+zhZg0Wr0kD/xO/M9rxC70gJsMMnzUAHLv5Cgly4zuivShjxHoFYLi7RM axnpVgSvl14MVrA4dZxQvssh7acaW9I6YINGAYrB5axeIhua0LziQzvFDYvljHtR3P6q 8mdW03Fru9o8LmyL43kal4naGA7iLwINYJuzt6Ij0ELJrijQKDe3J5r1V6Ws0l6QDa2G 6HQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q4N50os/pm/clZIqIIXFDs1nVEg4wHJBoPpYfo2Rm10=; b=dTyFVrx5WD0Ii+2BLAgy2XOCn/9gBITRhMfFvGfzmouhRS9SvvFCDfcd7LF1rpQmze W+Krx2SZ9BZEkwfa4rRc4fuKit2TCtcKc/vVl/NZUfWL4oIN09L/KkoPGe/9aaL6cnv8 OaoC76uCivNde/Ov6/tBt2Vd4cUDL3Js7+VE9kueljk5UYr+EyFh7nX+tMjZ6U878BAK 5DSUOkunnoewLXKbcXDpyuaHl6qWfRbZo7xtBpN/CYexB2RrG6oMYccqk2bH71KsV/p8 YO487JXofJTML9fjFAanY2XMjpf4ALR/PDAOG3RlEoX59b9DW512n7LoUB1tW+RNM2sP /cLg==
X-Gm-Message-State: APjAAAWS/ByYEjm17drTcPz+ETjmxI+ij2v8FeqJAaob2CIlzGQSzgb/ GyLWzz+Rx9JHTrNmA08g9b7uCyZMxqPJv82TjVsRFw==
X-Google-Smtp-Source: APXvYqwvYJAUVoQSlkZp0s6GL8mzoCahFF93EzHVDXftpLD+QGEySpMRaXI4HOuXU9lBd7xGBAT8U5Joo93/iBej7bg=
X-Received: by 2002:a2e:858b:: with SMTP id b11mr5017366lji.159.1560253090432;  Tue, 11 Jun 2019 04:38:10 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk>
In-Reply-To: <065101d52047$d35ea620$7a1bf260$@olddog.co.uk>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Jun 2019 04:37:33 -0700
Message-ID: <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: S Moonesamy <sm+ietf@elandsys.com>, Suresh Krishnan <suresh.krishnan@gmail.com>,  eligibility-discuss@ietf.org, John C Klensin <john-ietf@jck.com>,  Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Type: multipart/alternative; boundary="000000000000371cae058b0abb70"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/sCos13aMcqd_NzjuPRrX0sM06qw>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 11:38:15 -0000

--000000000000371cae058b0abb70
Content-Type: text/plain; charset="UTF-8"

H/mm..  These don't seem like "issues" so much as restatements of the
solution SM's draft proposes.

To take a specific one, what issue is addressed by reducing the number of
people required to sign the petition?

-Ekr


On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> That's nice. I like the clarity.
>
> I also like that the worms are kept firmly in their cans. It is without
> doubt that a hundred other issues concerning the recall process could be
> aired, and I am certain that many people have different hot issues. But I
> firmly believe that addressing a few at a time is the best (only!) way to
> make progress.
>
> If it turns out that there is support for resolving any of these three
> issues, they can be quickly picked off and we can move on to other issues
> if
> there is interest. If there is no support for addressing these three
> concerns, then they can be put to one side and work can start on other
> issues if there is interest.
>
> For my part, I think that all three issues should be addressed, and I think
> that the approaches suggested in SM's draft are a good starting point for
> discussion.
>
> Thanks,
> Adrian
>
> -----Original Message-----
> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On Behalf
> Of S Moonesamy
> Sent: 11 June 2019 11:45
> To: Suresh Krishnan <suresh.krishnan@gmail.com>;
> eligibility-discuss@ietf.org
> Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net>;
> Alexey Melnikov <aamelnikov@fastmail.fm>
> Subject: Re: [Eligibility-discuss] Virtual BoF for
> draft-moonesamy-recall-rev
>
> Hi Suresh,
>
> Please see a revised version of the BOF proposal to address your comments:
>
> Problem statement
>
>       The current description of the process for initiating petitions
> for recalls
>       for NomCom-appointed roles is described in RFC 7437 and is
> being updated in
>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only
> three
>       specific issues with the petition process; other parts of the
> recall model
>       and other ways of removing Nomcom-appointees are explicitly out of
> scope.
>
>       The three issues are:
>
>       - Ineligibility of remote participants to seek redress through the
>         recall process;
>
>       - Reducing the number of signatories for a recall petition;
>
>       - Ineligibility of IAB and IESG Members and other Nomcom
>         Appointees to sign a recall petition.
>
> The purpose of the BOF is to examine the above-mentioned issues and
> determine,
> for each, whether it is sufficient interest and importance.
> draft-moonesamy-recall-rev
> is a possible starting point for the effort.
>
> Regards,
> S. Moonesamy
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>

--000000000000371cae058b0abb70
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>H/mm..=C2=A0 These don&#39;t seem like &quot;issues&q=
uot; so much as restatements of the solution SM&#39;s draft proposes.</div>=
<div><br></div><div>To take a specific one, what issue is addressed by redu=
cing the number of people required to sign the petition?<br></div><div><br>=
</div><div>-Ekr</div><div><br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel=
 &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">That&#39;s n=
ice. I like the clarity.<br>
<br>
I also like that the worms are kept firmly in their cans. It is without<br>
doubt that a hundred other issues concerning the recall process could be<br=
>
aired, and I am certain that many people have different hot issues. But I<b=
r>
firmly believe that addressing a few at a time is the best (only!) way to<b=
r>
make progress.<br>
<br>
If it turns out that there is support for resolving any of these three<br>
issues, they can be quickly picked off and we can move on to other issues i=
f<br>
there is interest. If there is no support for addressing these three<br>
concerns, then they can be put to one side and work can start on other<br>
issues if there is interest.<br>
<br>
For my part, I think that all three issues should be addressed, and I think=
<br>
that the approaches suggested in SM&#39;s draft are a good starting point f=
or<br>
discussion.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
-----Original Message-----<br>
From: Eligibility-discuss &lt;<a href=3D"mailto:eligibility-discuss-bounces=
@ietf.org" target=3D"_blank">eligibility-discuss-bounces@ietf.org</a>&gt; O=
n Behalf<br>
Of S Moonesamy<br>
Sent: 11 June 2019 11:45<br>
To: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com" target=
=3D"_blank">suresh.krishnan@gmail.com</a>&gt;;<br>
<a href=3D"mailto:eligibility-discuss@ietf.org" target=3D"_blank">eligibili=
ty-discuss@ietf.org</a><br>
Cc: John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blan=
k">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=3D"mailto:warren@ku=
mari.net" target=3D"_blank">warren@kumari.net</a>&gt;;<br>
Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm" target=3D"_bl=
ank">aamelnikov@fastmail.fm</a>&gt;<br>
Subject: Re: [Eligibility-discuss] Virtual BoF for<br>
draft-moonesamy-recall-rev<br>
<br>
Hi Suresh,<br>
<br>
Please see a revised version of the BOF proposal to address your comments:<=
br>
<br>
Problem statement<br>
<br>
=C2=A0 =C2=A0 =C2=A0 The current description of the process for initiating =
petitions <br>
for recalls<br>
=C2=A0 =C2=A0 =C2=A0 for NomCom-appointed roles is described in RFC 7437 an=
d is <br>
being updated in<br>
=C2=A0 =C2=A0 =C2=A0 draft-ietf-iasa2-rfc7437bis.=C2=A0 The scope of this w=
ork addresses only<br>
three<br>
=C2=A0 =C2=A0 =C2=A0 specific issues with the petition process; other parts=
 of the <br>
recall model<br>
=C2=A0 =C2=A0 =C2=A0 and other ways of removing Nomcom-appointees are expli=
citly out of<br>
scope.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 The three issues are:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Ineligibility of remote participants to seek redress=
 through the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recall process;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Reducing the number of signatories for a recall peti=
tion;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Ineligibility of IAB and IESG Members and other Nomc=
om<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Appointees to sign a recall petition.<br>
<br>
The purpose of the BOF is to examine the above-mentioned issues and<br>
determine,<br>
for each, whether it is sufficient interest and importance. <br>
draft-moonesamy-recall-rev<br>
is a possible starting point for the effort.<br>
<br>
Regards,<br>
S. Moonesamy<br>
<br>
-- <br>
Eligibility-discuss mailing list<br>
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibili=
ty-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eli=
gibility-discuss</a><br>
<br>
-- <br>
Eligibility-discuss mailing list<br>
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibili=
ty-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eli=
gibility-discuss</a><br>
</blockquote></div></div>

--000000000000371cae058b0abb70--


From nobody Tue Jun 11 05:21:32 2019
Return-Path: <lear@cisco.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 A3152120115 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 n2r6bmxUwvy1 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:21:28 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF6C9120043 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12164; q=dns/txt; s=iport; t=1560255688; x=1561465288; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=07aFQrB9WLppRQacb7rFx8WeAF0OOfa08Aw2hpX5RNo=; b=FieCEMnJljizjLRKK2/s4LeBp9X9wLFAiufdWA4jzh3+vfImyDlxmPhm UGseDpn3vrJPYWS4Y4BulPGzTLlFEI2jDxaD6FFicMKYOQYYazvvCN1uV JiUFJldU/PU2uax+h7WqZ16hZ7S0t2Db53pKdDh87dBjFrR58fEQSoRn7 c=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAABpm/9c/xbLJq1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUgMBAQEBAQsBgWaBFFEBIBIojRCMBYlDiR2GAYF7Agc?= =?us-ascii?q?BAQEJAwEBGAEKDAEBg3pGAoMhNQgOAQMBAQQBAQIBBG0cDIVKAQEBAQIBAQF?= =?us-ascii?q?sCwUHBAsOAwQBAQEnByEGHwkIBhMbgwcBgWoDDg8PqgqFR4JCDYITCgaBNAG?= =?us-ascii?q?BT4okgX+BEScfgkw+ghpHAQGFHYImBJQOlGQ+CYISghuBBow5g2sbgiWGfYN?= =?us-ascii?q?gih6WDoo/gwcCBAYFAhWBUQI0gVgzGggbFTsqAYJBPoJ2AQmHVYVBPQMwkBA?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.63,579,1557187200";  d="asc'?scan'208,217";a="12975131"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 12:21:24 +0000
Received: from [10.61.194.73] ([10.61.194.73]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x5BCLNno006131 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 12:21:24 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DF307A8E-8F11-4D10-B635-8F2C730A04F2"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 14:21:21 +0200
In-Reply-To: <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
To: Eric Rescorla <ekr@rtfm.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.194.73, [10.61.194.73]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Ju7R5EwgJX9rhBF0vBH-pi6LwJM>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:21:31 -0000

--Apple-Mail=_DF307A8E-8F11-4D10-B635-8F2C730A04F2
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DDEFE664-33FA-4BA4-9A27-2F921385570B"


--Apple-Mail=_DDEFE664-33FA-4BA4-9A27-2F921385570B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
> H/mm..  These don't seem like "issues" so much as restatements of the =
solution SM's draft proposes.
>=20
> To take a specific one, what issue is addressed by reducing the number =
of people required to sign the petition?
>=20

Fewer people would have to set themselves up as targets for retribution; =
the pool of people able to serve on the recall committee is marginally =
increased.

Eliot

> -Ekr
>=20
>=20
> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk =
<mailto:adrian@olddog.co.uk>> wrote:
> That's nice. I like the clarity.
>=20
> I also like that the worms are kept firmly in their cans. It is =
without
> doubt that a hundred other issues concerning the recall process could =
be
> aired, and I am certain that many people have different hot issues. =
But I
> firmly believe that addressing a few at a time is the best (only!) way =
to
> make progress.
>=20
> If it turns out that there is support for resolving any of these three
> issues, they can be quickly picked off and we can move on to other =
issues if
> there is interest. If there is no support for addressing these three
> concerns, then they can be put to one side and work can start on other
> issues if there is interest.
>=20
> For my part, I think that all three issues should be addressed, and I =
think
> that the approaches suggested in SM's draft are a good starting point =
for
> discussion.
>=20
> Thanks,
> Adrian
>=20
> -----Original Message-----
> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org =
<mailto:eligibility-discuss-bounces@ietf.org>> On Behalf
> Of S Moonesamy
> Sent: 11 June 2019 11:45
> To: Suresh Krishnan <suresh.krishnan@gmail.com =
<mailto:suresh.krishnan@gmail.com>>;
> eligibility-discuss@ietf.org <mailto:eligibility-discuss@ietf.org>
> Cc: John C Klensin <john-ietf@jck.com <mailto:john-ietf@jck.com>>; =
Warren Kumari <warren@kumari.net <mailto:warren@kumari.net>>;
> Alexey Melnikov <aamelnikov@fastmail.fm =
<mailto:aamelnikov@fastmail.fm>>
> Subject: Re: [Eligibility-discuss] Virtual BoF for
> draft-moonesamy-recall-rev
>=20
> Hi Suresh,
>=20
> Please see a revised version of the BOF proposal to address your =
comments:
>=20
> Problem statement
>=20
>       The current description of the process for initiating petitions
> for recalls
>       for NomCom-appointed roles is described in RFC 7437 and is
> being updated in
>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses =
only
> three
>       specific issues with the petition process; other parts of the
> recall model
>       and other ways of removing Nomcom-appointees are explicitly out =
of
> scope.
>=20
>       The three issues are:
>=20
>       - Ineligibility of remote participants to seek redress through =
the
>         recall process;
>=20
>       - Reducing the number of signatories for a recall petition;
>=20
>       - Ineligibility of IAB and IESG Members and other Nomcom
>         Appointees to sign a recall petition.
>=20
> The purpose of the BOF is to examine the above-mentioned issues and
> determine,
> for each, whether it is sufficient interest and importance.
> draft-moonesamy-recall-rev
> is a possible starting point for the effort.
>=20
> Regards,
> S. Moonesamy
>=20
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
> https://www.ietf.org/mailman/listinfo/eligibility-discuss =
<https://www.ietf.org/mailman/listinfo/eligibility-discuss>
>=20
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
> https://www.ietf.org/mailman/listinfo/eligibility-discuss =
<https://www.ietf.org/mailman/listinfo/eligibility-discuss>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss


--Apple-Mail=_DDEFE664-33FA-4BA4-9A27-2F921385570B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 11 Jun 2019, at 13:37, Eric Rescorla &lt;<a =
href=3D"mailto:ekr@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">H/mm..&nbsp; =
These don't seem like "issues" so much as restatements of the solution =
SM's draft proposes.</div><div class=3D""><br class=3D""></div><div =
class=3D"">To take a specific one, what issue is addressed by reducing =
the number of people required to sign the petition?<br =
class=3D""></div><div class=3D""><br =
class=3D""></div></div></div></blockquote><div><br class=3D""></div>Fewer =
people would have to set themselves up as targets for retribution; the =
pool of people able to serve on the recall committee is marginally =
increased.</div><div><br class=3D""></div><div>Eliot</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"">-Ekr</div><div class=3D""><br =
class=3D""></div><br class=3D""><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 11, 2019 at 4:22 AM Adrian =
Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" =
class=3D"">adrian@olddog.co.uk</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">That's nice. I like the clarity.<br =
class=3D"">
<br class=3D"">
I also like that the worms are kept firmly in their cans. It is =
without<br class=3D"">
doubt that a hundred other issues concerning the recall process could =
be<br class=3D"">
aired, and I am certain that many people have different hot issues. But =
I<br class=3D"">
firmly believe that addressing a few at a time is the best (only!) way =
to<br class=3D"">
make progress.<br class=3D"">
<br class=3D"">
If it turns out that there is support for resolving any of these =
three<br class=3D"">
issues, they can be quickly picked off and we can move on to other =
issues if<br class=3D"">
there is interest. If there is no support for addressing these three<br =
class=3D"">
concerns, then they can be put to one side and work can start on =
other<br class=3D"">
issues if there is interest.<br class=3D"">
<br class=3D"">
For my part, I think that all three issues should be addressed, and I =
think<br class=3D"">
that the approaches suggested in SM's draft are a good starting point =
for<br class=3D"">
discussion.<br class=3D"">
<br class=3D"">
Thanks,<br class=3D"">
Adrian<br class=3D"">
<br class=3D"">
-----Original Message-----<br class=3D"">
From: Eligibility-discuss &lt;<a =
href=3D"mailto:eligibility-discuss-bounces@ietf.org" target=3D"_blank" =
class=3D"">eligibility-discuss-bounces@ietf.org</a>&gt; On Behalf<br =
class=3D"">
Of S Moonesamy<br class=3D"">
Sent: 11 June 2019 11:45<br class=3D"">
To: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com" =
target=3D"_blank" class=3D"">suresh.krishnan@gmail.com</a>&gt;;<br =
class=3D"">
<a href=3D"mailto:eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">eligibility-discuss@ietf.org</a><br class=3D"">
Cc: John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" =
target=3D"_blank" class=3D"">john-ietf@jck.com</a>&gt;; Warren Kumari =
&lt;<a href=3D"mailto:warren@kumari.net" target=3D"_blank" =
class=3D"">warren@kumari.net</a>&gt;;<br class=3D"">
Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm" =
target=3D"_blank" class=3D"">aamelnikov@fastmail.fm</a>&gt;<br class=3D"">=

Subject: Re: [Eligibility-discuss] Virtual BoF for<br class=3D"">
draft-moonesamy-recall-rev<br class=3D"">
<br class=3D"">
Hi Suresh,<br class=3D"">
<br class=3D"">
Please see a revised version of the BOF proposal to address your =
comments:<br class=3D"">
<br class=3D"">
Problem statement<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; The current description of the process for =
initiating petitions <br class=3D"">
for recalls<br class=3D"">
&nbsp; &nbsp; &nbsp; for NomCom-appointed roles is described in RFC 7437 =
and is <br class=3D"">
being updated in<br class=3D"">
&nbsp; &nbsp; &nbsp; draft-ietf-iasa2-rfc7437bis.&nbsp; The scope of =
this work addresses only<br class=3D"">
three<br class=3D"">
&nbsp; &nbsp; &nbsp; specific issues with the petition process; other =
parts of the <br class=3D"">
recall model<br class=3D"">
&nbsp; &nbsp; &nbsp; and other ways of removing Nomcom-appointees are =
explicitly out of<br class=3D"">
scope.<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; The three issues are:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; - Ineligibility of remote participants to seek =
redress through the<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; recall process;<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; - Reducing the number of signatories for a recall =
petition;<br class=3D"">
<br class=3D"">
&nbsp; &nbsp; &nbsp; - Ineligibility of IAB and IESG Members and other =
Nomcom<br class=3D"">
&nbsp; &nbsp; &nbsp; &nbsp; Appointees to sign a recall petition.<br =
class=3D"">
<br class=3D"">
The purpose of the BOF is to examine the above-mentioned issues and<br =
class=3D"">
determine,<br class=3D"">
for each, whether it is sufficient interest and importance. <br =
class=3D"">
draft-moonesamy-recall-rev<br class=3D"">
is a possible starting point for the effort.<br class=3D"">
<br class=3D"">
Regards,<br class=3D"">
S. Moonesamy<br class=3D"">
<br class=3D"">
-- <br class=3D"">
Eligibility-discuss mailing list<br class=3D"">
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">Eligibility-discuss@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><b=
r class=3D"">
<br class=3D"">
-- <br class=3D"">
Eligibility-discuss mailing list<br class=3D"">
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">Eligibility-discuss@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><b=
r class=3D"">
</blockquote></div></div>
-- <br class=3D"">Eligibility-discuss mailing list<br class=3D""><a =
href=3D"mailto:Eligibility-discuss@ietf.org" =
class=3D"">Eligibility-discuss@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_DDEFE664-33FA-4BA4-9A27-2F921385570B--

--Apple-Mail=_DF307A8E-8F11-4D10-B635-8F2C730A04F2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTgo4LlIIJ5lIBumWpugA9nE248uAUCXP+cwQAKCRBugA9nE248
uIC2AJ9LAplPVH+oREVmeGkWNc8z/Ch7TQCg2kodQbtG2FCUHhrcgMLHk3lp5hw=
=N56u
-----END PGP SIGNATURE-----

--Apple-Mail=_DF307A8E-8F11-4D10-B635-8F2C730A04F2--


From nobody Tue Jun 11 05:32:28 2019
Return-Path: <ekr@rtfm.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 CD7D9120154 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 JF0d-NEyWudz for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:32:24 -0700 (PDT)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) (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 E1A65120043 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:32:23 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id y17so9174895lfe.0 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zj0p/gTLZPWDb0lhf0XP+9gDlo/L9v3EbZnROuxNJwo=; b=XLNK8AimvB2lwzb5WsSvY9QTnpH/p/arhcP6ESi79fHSvg6fYDG2WuTBEJtvN7dFQy 7S7Y2gP6kTFfvGsAe/DDpfkuhFRBqf4fNQ4I2ksAt0PSYpLyf5uXqn7dMGH52bK+a8Mf WA9j3UCfskaq+PikgONUAjhHo1MQzNwaHuQRxEVZNBMnBc0ZSQc1SpGM4GFJMsK8zI+/ yUS8148xbELNSZW64Rx3K2kkjvxy2PSX2Qmam+tdCnsEZPIdZZ0iSEM+mFk3ivVRFcAp Cr9ZY/XS4RFBqGDYnl3nSx1QwS1NykR8bqWmZN6UFVMFLOok+OoR/reGLwXnWIvl5MW/ dF6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Zj0p/gTLZPWDb0lhf0XP+9gDlo/L9v3EbZnROuxNJwo=; b=HHzBHxqXXcWEr2GEQPteEClMXbkLlSEYW/PmYwwYHh00t5YLAjXjR+EaivpWAYsvmG YXy19TnXvIcyyzXkhKnQ8pTVNLB1wJHT9iReUx2IO5DcoQIlu3Oes85lFL5OcwtZhuGe L8uw7jcNbxrGMJIN9f7nBX81Iigftf8f2pFJyYWr+pTbYpv4Y074zFTTU/3+SyaO6ecG +ikmnBaIIpOp1rFxWZrc9084mY58lkrCVnbVmVHMjpw+rAQugU5s6Nuzja3Zx0XfQ26q F/zrz8XcD7khg8qKMSk58eU/AUDmli7Cm1fWQB3mgfhGQlGbNwtYgB7QfYBaLozwOuWh L6IA==
X-Gm-Message-State: APjAAAUK6avFj7N6YfzS8U7zYKohYLcOqMzi75xs+jchhRxcY9k+ZQcz 6xKX2ocbNpvn2E6IFA+Ji3RaDOea5QIPjcmf/QqsMA==
X-Google-Smtp-Source: APXvYqwoGfcPDdhfz/5AXE4rKywbM6CNRFM/GvN/7s5Am7PGh04aC+n+FQLXccqgIePhj20FKvn9N2tsCtZYPZ0MQB8=
X-Received: by 2002:ac2:5b0c:: with SMTP id v12mr24269831lfn.184.1560256342030;  Tue, 11 Jun 2019 05:32:22 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
In-Reply-To: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Jun 2019 05:31:45 -0700
Message-ID: <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Alexey Melnikov <aamelnikov@fastmail.fm>,  S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org,  Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="0000000000000696d8058b0b7dcd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/rXnwR0UTjeSxxU66ESrLOX9TDBM>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:32:27 -0000

--0000000000000696d8058b0b7dcd
Content-Type: text/plain; charset="UTF-8"

On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com> wrote:

>
>
> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>
> H/mm..  These don't seem like "issues" so much as restatements of the
> solution SM's draft proposes.
>
> To take a specific one, what issue is addressed by reducing the number of
> people required to sign the petition?
>
>
> Fewer people would have to set themselves up as targets for retribution;
> the pool of people able to serve on the recall committee is marginally
> increased.
>

That's helpful, but I think it also suggests that the problem statement
that SM has written is not really right: for instance, we could solve the
problem of people being targets of retribution by having the signers be
secret [0].. And we could address the pool issue by letting them serve on
the committee.

OTOH, it seems to me that the purpose of these requirements is to have a
certain level of accountability for the people requesting the recall and to
have a certain minimum level of support. So, is it clear that we actually
want to relax those objectives?

in any case, I think this exchange suggests that the first thing that's
needed is a problem statement that's decoupled from the solutions being
proposed.

-Ekr

[0] I'm aware that there are challenges here in verifying eligibility. I
believe there are solutions here, though they are too small to be contained
in this message.

Eliot
>
> -Ekr
>
>
> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>> That's nice. I like the clarity.
>>
>> I also like that the worms are kept firmly in their cans. It is without
>> doubt that a hundred other issues concerning the recall process could be
>> aired, and I am certain that many people have different hot issues. But I
>> firmly believe that addressing a few at a time is the best (only!) way to
>> make progress.
>>
>> If it turns out that there is support for resolving any of these three
>> issues, they can be quickly picked off and we can move on to other issues
>> if
>> there is interest. If there is no support for addressing these three
>> concerns, then they can be put to one side and work can start on other
>> issues if there is interest.
>>
>> For my part, I think that all three issues should be addressed, and I
>> think
>> that the approaches suggested in SM's draft are a good starting point for
>> discussion.
>>
>> Thanks,
>> Adrian
>>
>> -----Original Message-----
>> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On
>> Behalf
>> Of S Moonesamy
>> Sent: 11 June 2019 11:45
>> To: Suresh Krishnan <suresh.krishnan@gmail.com>;
>> eligibility-discuss@ietf.org
>> Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net
>> >;
>> Alexey Melnikov <aamelnikov@fastmail.fm>
>> Subject: Re: [Eligibility-discuss] Virtual BoF for
>> draft-moonesamy-recall-rev
>>
>> Hi Suresh,
>>
>> Please see a revised version of the BOF proposal to address your comments:
>>
>> Problem statement
>>
>>       The current description of the process for initiating petitions
>> for recalls
>>       for NomCom-appointed roles is described in RFC 7437 and is
>> being updated in
>>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only
>> three
>>       specific issues with the petition process; other parts of the
>> recall model
>>       and other ways of removing Nomcom-appointees are explicitly out of
>> scope.
>>
>>       The three issues are:
>>
>>       - Ineligibility of remote participants to seek redress through the
>>         recall process;
>>
>>       - Reducing the number of signatories for a recall petition;
>>
>>       - Ineligibility of IAB and IESG Members and other Nomcom
>>         Appointees to sign a recall petition.
>>
>> The purpose of the BOF is to examine the above-mentioned issues and
>> determine,
>> for each, whether it is sufficient interest and importance.
>> draft-moonesamy-recall-rev
>> is a possible starting point for the effort.
>>
>> Regards,
>> S. Moonesamy
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
>
>

--0000000000000696d8058b0b7dcd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 11, 2019 at 5:21 AM Eliot=
 Lear &lt;<a href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div><br><div><br><blockquote type=3D"cite"><div>On 11 Jun 2019, at 13:37,=
 Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rt=
fm.com</a>&gt; wrote:</div><br class=3D"m_-7006446583049777529m_38164753281=
36869560gmail-m_-1912520980219313799Apple-interchange-newline"><div><div di=
r=3D"ltr"><div>H/mm..=C2=A0 These don&#39;t seem like &quot;issues&quot; so=
 much as restatements of the solution SM&#39;s draft proposes.</div><div><b=
r></div><div>To take a specific one, what issue is addressed by reducing th=
e number of people required to sign the petition?<br></div><div><br></div><=
/div></div></blockquote><div><br></div>Fewer people would have to set thems=
elves up as targets for retribution; the pool of people able to serve on th=
e recall committee is marginally increased.</div></div></blockquote><div>=
=C2=A0</div><div>That&#39;s helpful, but I think it also suggests that the =
problem statement that SM has written is not really right: for instance, we=
 could solve the problem of people being targets of retribution by having t=
he signers be secret [0].. And we could address the pool issue by letting t=
hem serve on the committee.<br></div><div><br></div><div>OTOH, it seems to =
me that the purpose of these requirements is to have a certain level of acc=
ountability for the people requesting the recall and to have a certain mini=
mum level of support. So, is it clear that we actually want to relax those =
objectives?</div><div><br></div><div>in any case, I think this exchange sug=
gests that the first thing that&#39;s needed is a problem statement that&#3=
9;s decoupled from the solutions being proposed.<br></div><div><br></div><d=
iv>-Ekr</div><div><br></div><div>[0] I&#39;m aware that there are challenge=
s here in verifying eligibility. I believe there are solutions here, though=
 they are too small to be contained in this message.<br></div><div><br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>Eliot</div><d=
iv><br><blockquote type=3D"cite"><div><div dir=3D"ltr"><div>-Ekr</div><div>=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel &lt;<a href=3D"mailto:adr=
ian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">That&#39;s nice. I l=
ike the clarity.<br>
<br>
I also like that the worms are kept firmly in their cans. It is without<br>
doubt that a hundred other issues concerning the recall process could be<br=
>
aired, and I am certain that many people have different hot issues. But I<b=
r>
firmly believe that addressing a few at a time is the best (only!) way to<b=
r>
make progress.<br>
<br>
If it turns out that there is support for resolving any of these three<br>
issues, they can be quickly picked off and we can move on to other issues i=
f<br>
there is interest. If there is no support for addressing these three<br>
concerns, then they can be put to one side and work can start on other<br>
issues if there is interest.<br>
<br>
For my part, I think that all three issues should be addressed, and I think=
<br>
that the approaches suggested in SM&#39;s draft are a good starting point f=
or<br>
discussion.<br>
<br>
Thanks,<br>
Adrian<br>
<br>
-----Original Message-----<br>
From: Eligibility-discuss &lt;<a href=3D"mailto:eligibility-discuss-bounces=
@ietf.org" target=3D"_blank">eligibility-discuss-bounces@ietf.org</a>&gt; O=
n Behalf<br>
Of S Moonesamy<br>
Sent: 11 June 2019 11:45<br>
To: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com" target=
=3D"_blank">suresh.krishnan@gmail.com</a>&gt;;<br>
<a href=3D"mailto:eligibility-discuss@ietf.org" target=3D"_blank">eligibili=
ty-discuss@ietf.org</a><br>
Cc: John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blan=
k">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=3D"mailto:warren@ku=
mari.net" target=3D"_blank">warren@kumari.net</a>&gt;;<br>
Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm" target=3D"_bl=
ank">aamelnikov@fastmail.fm</a>&gt;<br>
Subject: Re: [Eligibility-discuss] Virtual BoF for<br>
draft-moonesamy-recall-rev<br>
<br>
Hi Suresh,<br>
<br>
Please see a revised version of the BOF proposal to address your comments:<=
br>
<br>
Problem statement<br>
<br>
=C2=A0 =C2=A0 =C2=A0 The current description of the process for initiating =
petitions <br>
for recalls<br>
=C2=A0 =C2=A0 =C2=A0 for NomCom-appointed roles is described in RFC 7437 an=
d is <br>
being updated in<br>
=C2=A0 =C2=A0 =C2=A0 draft-ietf-iasa2-rfc7437bis.=C2=A0 The scope of this w=
ork addresses only<br>
three<br>
=C2=A0 =C2=A0 =C2=A0 specific issues with the petition process; other parts=
 of the <br>
recall model<br>
=C2=A0 =C2=A0 =C2=A0 and other ways of removing Nomcom-appointees are expli=
citly out of<br>
scope.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 The three issues are:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Ineligibility of remote participants to seek redress=
 through the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recall process;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Reducing the number of signatories for a recall peti=
tion;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - Ineligibility of IAB and IESG Members and other Nomc=
om<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Appointees to sign a recall petition.<br>
<br>
The purpose of the BOF is to examine the above-mentioned issues and<br>
determine,<br>
for each, whether it is sufficient interest and importance. <br>
draft-moonesamy-recall-rev<br>
is a possible starting point for the effort.<br>
<br>
Regards,<br>
S. Moonesamy<br>
<br>
-- <br>
Eligibility-discuss mailing list<br>
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibili=
ty-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eli=
gibility-discuss</a><br>
<br>
-- <br>
Eligibility-discuss mailing list<br>
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibili=
ty-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eli=
gibility-discuss</a><br>
</blockquote></div></div>
-- <br>Eligibility-discuss mailing list<br><a href=3D"mailto:Eligibility-di=
scuss@ietf.org" target=3D"_blank">Eligibility-discuss@ietf.org</a><br><a hr=
ef=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><br></=
div></blockquote></div><br></div></blockquote></div></div>

--0000000000000696d8058b0b7dcd--


From nobody Tue Jun 11 05:39:03 2019
Return-Path: <lear@cisco.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 D042D120136 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 lftNq13O7umZ for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:38:59 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44CA612011E for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:38:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21504; q=dns/txt; s=iport; t=1560256738; x=1561466338; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=H7ovk4gDQKBjZStecKEanKwzuPhJFZe1A6o91GZ35IE=; b=eKRQNcQDU97glUTnbgYALj/OqMRqAygr/kdoHAoNdIeRCyQH/1zuDT0B s6sMXbJHr3H1vDBOTRI6dndpfJ3YqRydATrqdxJPQ6Jl1vaw/YOhoRqgX 608KbCDi/dGxGcJRjiJ89shuO2GH+lFlJAInqbDRNTGGw+kJ2S3rPl65O A=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAABtoP9c/xbLJq1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ5TBYEUUQEgEiiEFYgcX4wFiUOPHhS?= =?us-ascii?q?BZwIHAQEBCQMBARgBCgwBAYN6RgKDITQJDgEDAQEEAQECAQRtHAyFSgEBAQE?= =?us-ascii?q?CAQEBIUsLBQcECw4DBAEBAScDAgIhBh8JCAYTG4MHAYFqAw4PD6hpgTGFR4J?= =?us-ascii?q?CDYITCgaBNAGBT4okgX+BEScfgkw+ghpHAQGBSYMiMoImBJQOlGQ+CYISghu?= =?us-ascii?q?BBow5g2sbgiWGfYNgih6WDoo/gwcCBAYFAhWBTziBWDMaCBsVOyoBgkE+gnY?= =?us-ascii?q?BCYdVhUE9AzCQEAEB?=
X-IronPort-AV: E=Sophos;i="5.63,579,1557187200";  d="asc'?scan'208,217";a="13036367"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 12:38:55 +0000
Received: from [10.61.194.73] ([10.61.194.73]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x5BCcsAs008848 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 12:38:55 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <C30E8A9D-5D0A-456F-AC09-DB6787DEE4C6@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D8C6174D-B489-4E7B-91C6-46014289C319"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 14:38:52 +0200
In-Reply-To: <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Warren Kumari <warren@kumari.net>
To: Eric Rescorla <ekr@rtfm.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.194.73, [10.61.194.73]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/ed-Y4SpTIIrp6ku6AlnXFXZ8XXo>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:39:02 -0000

--Apple-Mail=_D8C6174D-B489-4E7B-91C6-46014289C319
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_711092E7-6B75-45E7-8194-BA7DC441E323"


--Apple-Mail=_711092E7-6B75-45E7-8194-BA7DC441E323
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 11 Jun 2019, at 14:31, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
> On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com =
<mailto:lear@cisco.com>> wrote:
>=20
>=20
>> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com =
<mailto:ekr@rtfm.com>> wrote:
>>=20
>> H/mm..  These don't seem like "issues" so much as restatements of the =
solution SM's draft proposes.
>>=20
>> To take a specific one, what issue is addressed by reducing the =
number of people required to sign the petition?
>>=20
>=20
> Fewer people would have to set themselves up as targets for =
retribution; the pool of people able to serve on the recall committee is =
marginally increased.
>=20
> That's helpful, but I think it also suggests that the problem =
statement that SM has written is not really right: for instance, we =
could solve the problem of people being targets of retribution by having =
the signers be secret [0].. And we could address the pool issue by =
letting them serve on the committee.

I agree with your 2nd sentence, but not your first, at least entirely.  =
It=E2=80=99s just just about eligibility, but also about the recall =
committee being able to understand the concerns of those seeking to have =
someone removed.  But I think your general point is well made: there =
needs to be one or more crisp problem statements to start with, and then =
various approaches can be considered to address the matter(s).

Eliot


>=20
> OTOH, it seems to me that the purpose of these requirements is to have =
a certain level of accountability for the people requesting the recall =
and to have a certain minimum level of support. So, is it clear that we =
actually want to relax those objectives?
>=20
> in any case, I think this exchange suggests that the first thing =
that's needed is a problem statement that's decoupled from the solutions =
being proposed.
>=20
> -Ekr
>=20
> [0] I'm aware that there are challenges here in verifying eligibility. =
I believe there are solutions here, though they are too small to be =
contained in this message.
>=20
> Eliot
>=20
>> -Ekr
>>=20
>>=20
>> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk =
<mailto:adrian@olddog.co.uk>> wrote:
>> That's nice. I like the clarity.
>>=20
>> I also like that the worms are kept firmly in their cans. It is =
without
>> doubt that a hundred other issues concerning the recall process could =
be
>> aired, and I am certain that many people have different hot issues. =
But I
>> firmly believe that addressing a few at a time is the best (only!) =
way to
>> make progress.
>>=20
>> If it turns out that there is support for resolving any of these =
three
>> issues, they can be quickly picked off and we can move on to other =
issues if
>> there is interest. If there is no support for addressing these three
>> concerns, then they can be put to one side and work can start on =
other
>> issues if there is interest.
>>=20
>> For my part, I think that all three issues should be addressed, and I =
think
>> that the approaches suggested in SM's draft are a good starting point =
for
>> discussion.
>>=20
>> Thanks,
>> Adrian
>>=20
>> -----Original Message-----
>> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org =
<mailto:eligibility-discuss-bounces@ietf.org>> On Behalf
>> Of S Moonesamy
>> Sent: 11 June 2019 11:45
>> To: Suresh Krishnan <suresh.krishnan@gmail.com =
<mailto:suresh.krishnan@gmail.com>>;
>> eligibility-discuss@ietf.org <mailto:eligibility-discuss@ietf.org>
>> Cc: John C Klensin <john-ietf@jck.com <mailto:john-ietf@jck.com>>; =
Warren Kumari <warren@kumari.net <mailto:warren@kumari.net>>;
>> Alexey Melnikov <aamelnikov@fastmail.fm =
<mailto:aamelnikov@fastmail.fm>>
>> Subject: Re: [Eligibility-discuss] Virtual BoF for
>> draft-moonesamy-recall-rev
>>=20
>> Hi Suresh,
>>=20
>> Please see a revised version of the BOF proposal to address your =
comments:
>>=20
>> Problem statement
>>=20
>>       The current description of the process for initiating petitions
>> for recalls
>>       for NomCom-appointed roles is described in RFC 7437 and is
>> being updated in
>>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses =
only
>> three
>>       specific issues with the petition process; other parts of the
>> recall model
>>       and other ways of removing Nomcom-appointees are explicitly out =
of
>> scope.
>>=20
>>       The three issues are:
>>=20
>>       - Ineligibility of remote participants to seek redress through =
the
>>         recall process;
>>=20
>>       - Reducing the number of signatories for a recall petition;
>>=20
>>       - Ineligibility of IAB and IESG Members and other Nomcom
>>         Appointees to sign a recall petition.
>>=20
>> The purpose of the BOF is to examine the above-mentioned issues and
>> determine,
>> for each, whether it is sufficient interest and importance.
>> draft-moonesamy-recall-rev
>> is a possible starting point for the effort.
>>=20
>> Regards,
>> S. Moonesamy
>>=20
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss =
<https://www.ietf.org/mailman/listinfo/eligibility-discuss>
>>=20
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss =
<https://www.ietf.org/mailman/listinfo/eligibility-discuss>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss =
<https://www.ietf.org/mailman/listinfo/eligibility-discuss>
>=20
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss


--Apple-Mail=_711092E7-6B75-45E7-8194-BA7DC441E323
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 11 Jun 2019, at 14:31, Eric Rescorla &lt;<a =
href=3D"mailto:ekr@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br class=3D"Apple-interchange-newline"><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear &lt;<a =
href=3D"mailto:lear@cisco.com" target=3D"_blank" =
class=3D"">lear@cisco.com</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;"><div class=3D""><br =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 11 Jun 2019, at 13:37, Eric Rescorla =
&lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank" =
class=3D"">ekr@rtfm.com</a>&gt; wrote:</div><br =
class=3D"m_-7006446583049777529m_3816475328136869560gmail-m_-1912520980219=
313799Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"">H/mm..&nbsp; These don't seem like "issues" =
so much as restatements of the solution SM's draft proposes.</div><div =
class=3D""><br class=3D""></div><div class=3D"">To take a specific one, =
what issue is addressed by reducing the number of people required to =
sign the petition?<br class=3D""></div><div class=3D""><br =
class=3D""></div></div></div></blockquote><div class=3D""><br =
class=3D""></div>Fewer people would have to set themselves up as targets =
for retribution; the pool of people able to serve on the recall =
committee is marginally increased.</div></div></blockquote><div =
class=3D"">&nbsp;</div><div class=3D"">That's helpful, but I think it =
also suggests that the problem statement that SM has written is not =
really right: for instance, we could solve the problem of people being =
targets of retribution by having the signers be secret [0].. And we =
could address the pool issue by letting them serve on the committee.<br =
class=3D""></div></div></div></div></blockquote><div><br =
class=3D""></div>I agree with your 2nd sentence, but not your first, at =
least entirely. &nbsp;It=E2=80=99s just just about eligibility, but also =
about the recall committee being able to understand the concerns of =
those seeking to have someone removed. &nbsp;But I think your general =
point is well made: there needs to be one or more crisp problem =
statements to start with, and then various approaches can be considered =
to address the matter(s).</div><div><br =
class=3D""></div><div>Eliot</div><div><br class=3D""></div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><div class=3D"gmail_quote"><div class=3D""><br =
class=3D""></div><div class=3D"">OTOH, it seems to me that the purpose =
of these requirements is to have a certain level of accountability for =
the people requesting the recall and to have a certain minimum level of =
support. So, is it clear that we actually want to relax those =
objectives?</div><div class=3D""><br class=3D""></div><div class=3D"">in =
any case, I think this exchange suggests that the first thing that's =
needed is a problem statement that's decoupled from the solutions being =
proposed.<br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">-Ekr</div><div class=3D""><br class=3D""></div><div =
class=3D"">[0] I'm aware that there are challenges here in verifying =
eligibility. I believe there are solutions here, though they are too =
small to be contained in this message.<br class=3D""></div><div =
class=3D""><br class=3D""></div><blockquote class=3D"gmail_quote" =
style=3D"margin: 0px 0px 0px 0.8ex; border-left-width: 1px; =
border-left-style: solid; border-left-color: rgb(204, 204, 204); =
padding-left: 1ex;"><div class=3D""><div class=3D"">Eliot</div><div =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">-Ekr</div><div =
class=3D""><br class=3D""></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun =
11, 2019 at 4:22 AM Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank" =
class=3D"">adrian@olddog.co.uk</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin: 0px =
0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; =
border-left-color: rgb(204, 204, 204); padding-left: 1ex;">That's nice. =
I like the clarity.<br class=3D""><br class=3D"">I also like that the =
worms are kept firmly in their cans. It is without<br class=3D"">doubt =
that a hundred other issues concerning the recall process could be<br =
class=3D"">aired, and I am certain that many people have different hot =
issues. But I<br class=3D"">firmly believe that addressing a few at a =
time is the best (only!) way to<br class=3D"">make progress.<br =
class=3D""><br class=3D"">If it turns out that there is support for =
resolving any of these three<br class=3D"">issues, they can be quickly =
picked off and we can move on to other issues if<br class=3D"">there is =
interest. If there is no support for addressing these three<br =
class=3D"">concerns, then they can be put to one side and work can start =
on other<br class=3D"">issues if there is interest.<br class=3D""><br =
class=3D"">For my part, I think that all three issues should be =
addressed, and I think<br class=3D"">that the approaches suggested in =
SM's draft are a good starting point for<br class=3D"">discussion.<br =
class=3D""><br class=3D"">Thanks,<br class=3D"">Adrian<br class=3D""><br =
class=3D"">-----Original Message-----<br class=3D"">From: =
Eligibility-discuss &lt;<a =
href=3D"mailto:eligibility-discuss-bounces@ietf.org" target=3D"_blank" =
class=3D"">eligibility-discuss-bounces@ietf.org</a>&gt; On Behalf<br =
class=3D"">Of S Moonesamy<br class=3D"">Sent: 11 June 2019 11:45<br =
class=3D"">To: Suresh Krishnan &lt;<a =
href=3D"mailto:suresh.krishnan@gmail.com" target=3D"_blank" =
class=3D"">suresh.krishnan@gmail.com</a>&gt;;<br class=3D""><a =
href=3D"mailto:eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">eligibility-discuss@ietf.org</a><br class=3D"">Cc: John C =
Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank" =
class=3D"">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a =
href=3D"mailto:warren@kumari.net" target=3D"_blank" =
class=3D"">warren@kumari.net</a>&gt;;<br class=3D"">Alexey Melnikov =
&lt;<a href=3D"mailto:aamelnikov@fastmail.fm" target=3D"_blank" =
class=3D"">aamelnikov@fastmail.fm</a>&gt;<br class=3D"">Subject: Re: =
[Eligibility-discuss] Virtual BoF for<br =
class=3D"">draft-moonesamy-recall-rev<br class=3D""><br class=3D"">Hi =
Suresh,<br class=3D""><br class=3D"">Please see a revised version of the =
BOF proposal to address your comments:<br class=3D""><br =
class=3D"">Problem statement<br class=3D""><br class=3D"">&nbsp; &nbsp; =
&nbsp; The current description of the process for initiating =
petitions<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">for recalls<br class=3D"">&nbsp; &nbsp; &nbsp; for =
NomCom-appointed roles is described in RFC 7437 and is<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">being =
updated in<br class=3D"">&nbsp; &nbsp; &nbsp; =
draft-ietf-iasa2-rfc7437bis.&nbsp; The scope of this work addresses =
only<br class=3D"">three<br class=3D"">&nbsp; &nbsp; &nbsp; specific =
issues with the petition process; other parts of the<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D"">recall =
model<br class=3D"">&nbsp; &nbsp; &nbsp; and other ways of removing =
Nomcom-appointees are explicitly out of<br class=3D"">scope.<br =
class=3D""><br class=3D"">&nbsp; &nbsp; &nbsp; The three issues are:<br =
class=3D""><br class=3D"">&nbsp; &nbsp; &nbsp; - Ineligibility of remote =
participants to seek redress through the<br class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; recall process;<br class=3D""><br class=3D"">&nbsp; &nbsp; =
&nbsp; - Reducing the number of signatories for a recall petition;<br =
class=3D""><br class=3D"">&nbsp; &nbsp; &nbsp; - Ineligibility of IAB =
and IESG Members and other Nomcom<br class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; Appointees to sign a recall petition.<br class=3D""><br =
class=3D"">The purpose of the BOF is to examine the above-mentioned =
issues and<br class=3D"">determine,<br class=3D"">for each, whether it =
is sufficient interest and importance.<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">draft-moonesamy-recall-rev<br class=3D"">is a possible =
starting point for the effort.<br class=3D""><br class=3D"">Regards,<br =
class=3D"">S. Moonesamy<br class=3D""><br class=3D"">--<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">Eligibility-discuss mailing list<br class=3D""><a =
href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">Eligibility-discuss@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><b=
r class=3D""><br class=3D"">--<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">Eligibility-discuss mailing list<br class=3D""><a =
href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">Eligibility-discuss@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><b=
r class=3D""></blockquote></div></div>--<span =
class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D"">Eligibility-discuss mailing list<br class=3D""><a =
href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank" =
class=3D"">Eligibility-discuss@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a><b=
r class=3D""></div></blockquote></div><br =
class=3D""></div></blockquote></div></div><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">--<span class=3D"Apple-converted-space">&nbsp;</span></span><br=
 style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Eligibility-discuss mailing =
list</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D""><a =
href=3D"mailto:Eligibility-discuss@ietf.org" =
class=3D"">Eligibility-discuss@ietf.org</a></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
class=3D"">https://www.ietf.org/mailman/listinfo/eligibility-discuss</a></=
span></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_711092E7-6B75-45E7-8194-BA7DC441E323--

--Apple-Mail=_D8C6174D-B489-4E7B-91C6-46014289C319
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTgo4LlIIJ5lIBumWpugA9nE248uAUCXP+g3AAKCRBugA9nE248
uELBAKDhXxFxYsb+hP52QOfZscisR3odAgCfYobp5v6zd7bsvR9EcDgdtAWrvP8=
=IZFN
-----END PGP SIGNATURE-----

--Apple-Mail=_D8C6174D-B489-4E7B-91C6-46014289C319--


From nobody Tue Jun 11 05:45:21 2019
Return-Path: <adrian@olddog.co.uk>
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 1DED0120099 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=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 oe5lH4ucIfMx for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:45:13 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 ADAF0120047 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:45:12 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5BCiNv7008072; Tue, 11 Jun 2019 13:44:24 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A759D22042; Tue, 11 Jun 2019 13:44:23 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id 8C79D2203D; Tue, 11 Jun 2019 13:44:23 +0100 (BST)
Received: from LAPTOPK7AS653V (25.129.51.84.dyn.plus.net [84.51.129.25] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5BCiMN5026642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 13:44:22 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Eric Rescorla'" <ekr@rtfm.com>, "'Eliot Lear'" <lear@cisco.com>
Cc: "'Alexey Melnikov'" <aamelnikov@fastmail.fm>, "'S Moonesamy'" <sm+ietf@elandsys.com>, <eligibility-discuss@ietf.org>, "'Suresh Krishnan'" <suresh.krishnan@gmail.com>, "'John C Klensin'" <john-ietf@jck.com>, "'Warren Kumari'" <warren@kumari.net>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
In-Reply-To: <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com>
Date: Tue, 11 Jun 2019 13:44:21 +0100
Organization: Old Dog Consulting
Message-ID: <066801d52053$650ea290$2f2be7b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0669_01D5205B.C6D52D70"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFR42vyAucRjBtXO+m4xnaMV3ichgHs2gIPAxJf1rwBYZyWFwJDqDEaAjXe+S0BtUW2PwFcTyHFpy1/XpA=
Content-Language: en-gb
X-Originating-IP: 84.51.129.25
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24668.007
X-TM-AS-Result: No--17.973-10.0-31-10
X-imss-scan-details: No--17.973-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24668.007
X-TMASE-Result: 10--17.972600-10.000000
X-TMASE-MatchedRID: CxmI61mtwh/xIbpQ8BhdbCqRJ4M9q7OvwZy9wGhpvaNFCDIidTKtYpFS DYziOe5w8vwsrbfwnUTrYt4Z4zzGgGqLs+uf/K4th6XwUno6mkn9aHlnkhmFFiS30GKAkBxWufB Ng+8/ksG2rLh8a1V1CtPKGHv3/PkFTdxlgyoTjkhkPwYFI6/mFOvWkvu/824/wj10jtt9j+9B9d 7E3eZ5kC5dI0Fz4J2fq6NOqQ9cAFcb35hYG2f1/cn9tWHiLD2GE7s3ncD36/1H7rX2ckGqtT53U iKoi7xOLvRFzGB1z1hIc7XcoyxALVEzcHURSIXRcaD+wPaBYtZCjhk4ByVfUgprCx5nrF2x3JWs hmL/k7/bPaIOzdngXluSVewUWUqGDZ4p7Io2WwzKE9oA9cXOzfiH64jt3FfEI0YrtQLsSUzCQH3 xHQZ0Sp2ywec1wywdHWyEHCDak5u4Gwz1apLtulWeeIqHthMLySf7HrQn3BptpkxrR+BG1lzTKp ++bzfFXUS+W6ogsA/eGUKKVq7jIEIw4Xa9LAtMqnhd3PneL8lzcxhUDJRJPug3wNKii1r5QPh/x C0EIZmuK2CoOfWQDl+b1eIMiHHUyTBgz6hl0dfF7d92CEJWO6ld1ZriBTRLj6Xh9k1IeO6IushU x+1X0I6hiC/HSAqLSaK6OQhDABTW77y3zZrIHboLyaVI8w2Xi84ZMJtUpThdzCApzeAWWaKkU0t 47vZIG2cmJvqAPualugrXm5IKcMNOo16VCf1yx/Stmah0FpbfVqwz+CynaalVRHRK9i1KzEVDGn c+EfKahG/i8Ja1Y7dYFVfIRaXS7zgtUFe2gc6eAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyI7KyMT1 v0KydCpCFLDTHZU4kYXbobxJbKl/MtrTwS4UL+QJhIfzUHNU5OIMDSrPFDqMouO24RAWXT9yLxI 0YMPZ2j2vJWDH8A=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Kf48j5Dr8vZiT2FMjxN77yiVfjg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:45:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0669_01D5205B.C6D52D70
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

How about phrasing the problem as =E2=80=9CYou need too many people to =
sign a recall petition, and that makes it too hard to achieve a =
recall=E2=80=9D?

=20

We can agree or disagree about whether this is a problem and whether we =
want to work on it. That=E2=80=99s why we have BoFs and mailing lists.

We can debate the correct solution for each problem, but (usually, when =
we have a BoF) the discussion of the solutions is sequenced after the =
discussion of the problems and agreement that we want to work on the =
problems.=20

=20

Adrian

=20

From: Eric Rescorla <ekr@rtfm.com>=20
Sent: 11 June 2019 13:32
To: Eliot Lear <lear@cisco.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>; Alexey Melnikov =
<aamelnikov@fastmail.fm>; S Moonesamy <sm+ietf@elandsys.com>; =
eligibility-discuss@ietf.org; Suresh Krishnan =
<suresh.krishnan@gmail.com>; John C Klensin <john-ietf@jck.com>; Warren =
Kumari <warren@kumari.net>
Subject: Re: [Eligibility-discuss] Virtual BoF for =
draft-moonesamy-recall-rev

=20

=20

=20

On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com =
<mailto:lear@cisco.com> > wrote:

=20





On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com =
<mailto:ekr@rtfm.com> > wrote:

=20

H/mm..  These don't seem like "issues" so much as restatements of the =
solution SM's draft proposes.

=20

To take a specific one, what issue is addressed by reducing the number =
of people required to sign the petition?

=20

=20

Fewer people would have to set themselves up as targets for retribution; =
the pool of people able to serve on the recall committee is marginally =
increased.

=20

That's helpful, but I think it also suggests that the problem statement =
that SM has written is not really right: for instance, we could solve =
the problem of people being targets of retribution by having the signers =
be secret [0].. And we could address the pool issue by letting them =
serve on the committee.

=20

OTOH, it seems to me that the purpose of these requirements is to have a =
certain level of accountability for the people requesting the recall and =
to have a certain minimum level of support. So, is it clear that we =
actually want to relax those objectives?

=20

in any case, I think this exchange suggests that the first thing that's =
needed is a problem statement that's decoupled from the solutions being =
proposed.

=20

-Ekr

=20

[0] I'm aware that there are challenges here in verifying eligibility. I =
believe there are solutions here, though they are too small to be =
contained in this message.

=20

Eliot





-Ekr

=20

=20

On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk =
<mailto:adrian@olddog.co.uk> > wrote:

That's nice. I like the clarity.

I also like that the worms are kept firmly in their cans. It is without
doubt that a hundred other issues concerning the recall process could be
aired, and I am certain that many people have different hot issues. But =
I
firmly believe that addressing a few at a time is the best (only!) way =
to
make progress.

If it turns out that there is support for resolving any of these three
issues, they can be quickly picked off and we can move on to other =
issues if
there is interest. If there is no support for addressing these three
concerns, then they can be put to one side and work can start on other
issues if there is interest.

For my part, I think that all three issues should be addressed, and I =
think
that the approaches suggested in SM's draft are a good starting point =
for
discussion.

Thanks,
Adrian

-----Original Message-----
From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org =
<mailto:eligibility-discuss-bounces@ietf.org> > On Behalf
Of S Moonesamy
Sent: 11 June 2019 11:45
To: Suresh Krishnan <suresh.krishnan@gmail.com =
<mailto:suresh.krishnan@gmail.com> >;
eligibility-discuss@ietf.org <mailto:eligibility-discuss@ietf.org>=20
Cc: John C Klensin <john-ietf@jck.com <mailto:john-ietf@jck.com> >; =
Warren Kumari <warren@kumari.net <mailto:warren@kumari.net> >;
Alexey Melnikov <aamelnikov@fastmail.fm <mailto:aamelnikov@fastmail.fm> =
>
Subject: Re: [Eligibility-discuss] Virtual BoF for
draft-moonesamy-recall-rev

Hi Suresh,

Please see a revised version of the BOF proposal to address your =
comments:

Problem statement

      The current description of the process for initiating petitions=20
for recalls
      for NomCom-appointed roles is described in RFC 7437 and is=20
being updated in
      draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses =
only
three
      specific issues with the petition process; other parts of the=20
recall model
      and other ways of removing Nomcom-appointees are explicitly out of
scope.

      The three issues are:

      - Ineligibility of remote participants to seek redress through the
        recall process;

      - Reducing the number of signatories for a recall petition;

      - Ineligibility of IAB and IESG Members and other Nomcom
        Appointees to sign a recall petition.

The purpose of the BOF is to examine the above-mentioned issues and
determine,
for each, whether it is sufficient interest and importance.=20
draft-moonesamy-recall-rev
is a possible starting point for the effort.

Regards,
S. Moonesamy

--=20
Eligibility-discuss mailing list
Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>=20
https://www.ietf.org/mailman/listinfo/eligibility-discuss

--=20
Eligibility-discuss mailing list
Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>=20
https://www.ietf.org/mailman/listinfo/eligibility-discuss

--=20
Eligibility-discuss mailing list
Eligibility-discuss@ietf.org <mailto:Eligibility-discuss@ietf.org>=20
https://www.ietf.org/mailman/listinfo/eligibility-discuss

=20


------=_NextPart_000_0669_01D5205B.C6D52D70
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>How about phrasing the problem as =
=E2=80=9CYou need too many people to sign a recall petition, and that =
makes it too hard to achieve a recall=E2=80=9D?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'>We can =
agree or disagree about whether this is a problem and whether we want to =
work on it. That=E2=80=99s why we have BoFs and mailing =
lists.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>We can debate the correct solution =
for each problem, but (usually, when we have a BoF) the discussion of =
the solutions is sequenced after the discussion of the problems and =
agreement that we want to work on the problems. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><b><span lang=3DEN-US>From:</span></b><span =
lang=3DEN-US> Eric Rescorla &lt;ekr@rtfm.com&gt; <br><b>Sent:</b> 11 =
June 2019 13:32<br><b>To:</b> Eliot Lear =
&lt;lear@cisco.com&gt;<br><b>Cc:</b> Adrian Farrel =
&lt;adrian@olddog.co.uk&gt;; Alexey Melnikov =
&lt;aamelnikov@fastmail.fm&gt;; S Moonesamy =
&lt;sm+ietf@elandsys.com&gt;; eligibility-discuss@ietf.org; Suresh =
Krishnan &lt;suresh.krishnan@gmail.com&gt;; John C Klensin =
&lt;john-ietf@jck.com&gt;; Warren Kumari =
&lt;warren@kumari.net&gt;<br><b>Subject:</b> Re: [Eligibility-discuss] =
Virtual BoF for draft-moonesamy-recall-rev<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Tue, Jun 11, 2019 at 5:21 AM Eliot Lear &lt;<a =
href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p =
class=3DMsoNormal>On 11 Jun 2019, at 13:37, Eric Rescorla &lt;<a =
href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal>H/mm..&nbsp; These don't seem like &quot;issues&quot; =
so much as restatements of the solution SM's draft =
proposes.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>To take a specific one, what issue is addressed by =
reducing the number of people required to sign the =
petition?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></blockquote><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal>Fewer people would have to set themselves up as =
targets for retribution; the pool of people able to serve on the recall =
committee is marginally =
increased.<o:p></o:p></p></div></div></blockquote><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>That's helpful, but I think it also suggests that the =
problem statement that SM has written is not really right: for instance, =
we could solve the problem of people being targets of retribution by =
having the signers be secret [0].. And we could address the pool issue =
by letting them serve on the committee.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OTOH, it seems to me that the purpose of these =
requirements is to have a certain level of accountability for the people =
requesting the recall and to have a certain minimum level of support. =
So, is it clear that we actually want to relax those =
objectives?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>in any case, I think this exchange suggests that the =
first thing that's needed is a problem statement that's decoupled from =
the solutions being proposed.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>-Ekr<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>[0] I'm aware that there are challenges here in =
verifying eligibility. I believe there are solutions here, though they =
are too small to be contained in this =
message.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p =
class=3DMsoNormal>Eliot<o:p></o:p></p></div><div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><p =
class=3DMsoNormal>-Ekr<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal>That's =
nice. I like the clarity.<br><br>I also like that the worms are kept =
firmly in their cans. It is without<br>doubt that a hundred other issues =
concerning the recall process could be<br>aired, and I am certain that =
many people have different hot issues. But I<br>firmly believe that =
addressing a few at a time is the best (only!) way to<br>make =
progress.<br><br>If it turns out that there is support for resolving any =
of these three<br>issues, they can be quickly picked off and we can move =
on to other issues if<br>there is interest. If there is no support for =
addressing these three<br>concerns, then they can be put to one side and =
work can start on other<br>issues if there is interest.<br><br>For my =
part, I think that all three issues should be addressed, and I =
think<br>that the approaches suggested in SM's draft are a good starting =
point for<br>discussion.<br><br>Thanks,<br>Adrian<br><br>-----Original =
Message-----<br>From: Eligibility-discuss &lt;<a =
href=3D"mailto:eligibility-discuss-bounces@ietf.org" =
target=3D"_blank">eligibility-discuss-bounces@ietf.org</a>&gt; On =
Behalf<br>Of S Moonesamy<br>Sent: 11 June 2019 11:45<br>To: Suresh =
Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com" =
target=3D"_blank">suresh.krishnan@gmail.com</a>&gt;;<br><a =
href=3D"mailto:eligibility-discuss@ietf.org" =
target=3D"_blank">eligibility-discuss@ietf.org</a><br>Cc: John C Klensin =
&lt;<a href=3D"mailto:john-ietf@jck.com" =
target=3D"_blank">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a =
href=3D"mailto:warren@kumari.net" =
target=3D"_blank">warren@kumari.net</a>&gt;;<br>Alexey Melnikov &lt;<a =
href=3D"mailto:aamelnikov@fastmail.fm" =
target=3D"_blank">aamelnikov@fastmail.fm</a>&gt;<br>Subject: Re: =
[Eligibility-discuss] Virtual BoF =
for<br>draft-moonesamy-recall-rev<br><br>Hi Suresh,<br><br>Please see a =
revised version of the BOF proposal to address your =
comments:<br><br>Problem statement<br><br>&nbsp; &nbsp; &nbsp; The =
current description of the process for initiating petitions <br>for =
recalls<br>&nbsp; &nbsp; &nbsp; for NomCom-appointed roles is described =
in RFC 7437 and is <br>being updated in<br>&nbsp; &nbsp; &nbsp; =
draft-ietf-iasa2-rfc7437bis.&nbsp; The scope of this work addresses =
only<br>three<br>&nbsp; &nbsp; &nbsp; specific issues with the petition =
process; other parts of the <br>recall model<br>&nbsp; &nbsp; &nbsp; and =
other ways of removing Nomcom-appointees are explicitly out =
of<br>scope.<br><br>&nbsp; &nbsp; &nbsp; The three issues =
are:<br><br>&nbsp; &nbsp; &nbsp; - Ineligibility of remote participants =
to seek redress through the<br>&nbsp; &nbsp; &nbsp; &nbsp; recall =
process;<br><br>&nbsp; &nbsp; &nbsp; - Reducing the number of =
signatories for a recall petition;<br><br>&nbsp; &nbsp; &nbsp; - =
Ineligibility of IAB and IESG Members and other Nomcom<br>&nbsp; &nbsp; =
&nbsp; &nbsp; Appointees to sign a recall petition.<br><br>The purpose =
of the BOF is to examine the above-mentioned issues =
and<br>determine,<br>for each, whether it is sufficient interest and =
importance. <br>draft-moonesamy-recall-rev<br>is a possible starting =
point for the effort.<br><br>Regards,<br>S. Moonesamy<br><br>-- =
<br>Eligibility-discuss mailing list<br><a =
href=3D"mailto:Eligibility-discuss@ietf.org" =
target=3D"_blank">Eligibility-discuss@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/eligibility-discu=
ss</a><br><br>-- <br>Eligibility-discuss mailing list<br><a =
href=3D"mailto:Eligibility-discuss@ietf.org" =
target=3D"_blank">Eligibility-discuss@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/eligibility-discu=
ss</a><o:p></o:p></p></blockquote></div></div><p class=3DMsoNormal>-- =
<br>Eligibility-discuss mailing list<br><a =
href=3D"mailto:Eligibility-discuss@ietf.org" =
target=3D"_blank">Eligibility-discuss@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/eligibility-discu=
ss</a><o:p></o:p></p></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></blockquote></div></div></d=
iv></body></html>
------=_NextPart_000_0669_01D5205B.C6D52D70--


From nobody Tue Jun 11 05:50:58 2019
Return-Path: <aamelnikov@fastmail.fm>
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 06BD7120099 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=aXUoiO49; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=zMc4N4gS
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 TtcoOJkVTAd3 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:50:55 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B06B120047 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:50:55 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 3E022220C9; Tue, 11 Jun 2019 08:50:54 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute7.internal (MEProxy); Tue, 11 Jun 2019 08:50:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type:content-transfer-encoding; s=fm3; bh=cp9eE rdgxSaSyHiXOxl7JL64Kd4eFe4asBYVDrMpxr8=; b=aXUoiO49IUeTQRpbakhDf SaFrRfJRgUyUn5w/StVmfAhnoSclJNWqnG9WWobOP0JRpD0ZiG2uHYE3GOU+Tgg+ ab8l/MVgxz1xS1e6ZavWGLu0GUhMmj/HY3V5m7pdXu+VOM43W477tLd7wCsr9ZpA qaaBpNUYTpXS0eZIYfL2ZNpRPEt14Mm8H0uCP70o+IXytqKqieQwqfTRqCqHLXnw JtE1uZjd6PFcnM8JrPMDxmeKml4MWrCD+SURY7Kq3L+fKnjtI4b+rr5OAsSUvUoy kKuoM2g+Ioj4gcovBu8UwRKeU90vZ9e5NKJ3CnCd/QuEklHKKn4c2RjQYR7Us3UM w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=cp9eErdgxSaSyHiXOxl7JL64Kd4eFe4asBYVDrMpx r8=; b=zMc4N4gSCXkPha8s3VeT3HW762yy44w/ILudmBEkaOngigOdLXJd+ubKi h/gDyWSFKUMv83Ia0NGKfdwnUEoAGVnFpqDmVb6rMQ2aL/51RFgx6qXn4oyJiZqq Yjv6RTQOLf+KMAl13dcMxUq24XBCnaMlf1wRtTdd3l2rwdLIbLjCoLZNsdn9AMlr 6ZzRnj/U6YJ336dDDKML115/zERmkeeuzjFzd9mSgQXLZJKOXlwxZ6fvcVqHB4ZK n3iuxumd1cAPvTDiSMFKS1MAbZi0olZG2EGMLz6xGK+4m6lOhyxKS51bWTz6J7WL INcifv/JGD5VNmkI1FHAep0bPbtlA==
X-ME-Sender: <xms:raP_XClpmOPRGPZviQrZwmbWIg6sui9RX3Hi7coJ06RgXpmg_etiRg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehhedggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedftehl vgigvgihucfovghlnhhikhhovhdfuceorggrmhgvlhhnihhkohhvsehfrghsthhmrghilh drfhhmqeenucfrrghrrghmpehmrghilhhfrhhomheprggrmhgvlhhnihhkohhvsehfrghs thhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:raP_XF2a4zbJiI9DzKJ77Ul5HGpgA5SZNklii9efj-OGiSOKTdiXmw> <xmx:raP_XC2YF1LvYCHb9xcCAfEz8zsuPSdCU9v1x2YuMr7r06wXOh2n-w> <xmx:raP_XHoZ9KjwMAItsAcf6nbT4vnmqsE1qr0D0yTqAimEh1XulzB3eA> <xmx:rqP_XD7n44atU9wBTSN3n-loUIrLwy8Au9y8qjIpqbEu0drM7IgNjg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 45122C200A3; Tue, 11 Jun 2019 08:50:53 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-663-gf46ad30-fmstable-20190607v1
Mime-Version: 1.0
Message-Id: <d64a1e12-f802-4ec4-bf72-d75f56f22684@www.fastmail.com>
In-Reply-To: <06BAD820-C035-4822-B908-51992E24DE5A@gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190604124032.0c2f0ca0@elandnews.com> <35ECCB711814EE331938E6C7@PSB> <06BAD820-C035-4822-B908-51992E24DE5A@gmail.com>
Date: Tue, 11 Jun 2019 13:50:41 +0100
From: "Alexey Melnikov" <aamelnikov@fastmail.fm>
To: "Suresh Krishnan" <suresh.krishnan@gmail.com>, "John C Klensin" <john-ietf@jck.com>
Cc: "S Moonesamy" <sm+ietf@elandsys.com>, "Warren Kumari" <warren@kumari.net>,  eligibility-discuss@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/l4WEYlEwDJVu84e1_4GldZ7-NBY>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:50:57 -0000

Hi John,

On Fri, Jun 7, 2019, at 4:14 AM, Suresh Krishnan wrote:
> Hi John,
>=20
> > On Jun 5, 2019, at 10:10 AM, John C Klensin <john-ietf@jck.com> wrot=
e:
> >=20
> > Suresh (and Alexey and Warren),
> >=20
> > It seems to me that there are two, quite different, possible BOF
> > proposals and that the community could use a little guidance
> > from the three of you about what the IESG is looking for.
>=20
> Just speaking for myself here. I do have my preference (see below), bu=
t=20
> I will leave it up to the proponents to decide which way they want to=20=

> go.
>=20
> >=20
> > One is the result of the direction in which Subramanian seems to
> > be heading and that reflects the actual content of
> > draft-moonesamy-recall-rev.  That is a very narrow set of
> > changes to fine-tune the existing recall procedure to allow a
> > set of people who do not meet the "Nomcom eligibility"
> > requirement because they do not attend sufficient f2f meeting no
> > matter how active they are in the IETF, to reduce the number of
> > signatures required to initiate a recall because the current
> > number is seen as burdensome (especially for people who can't
> > collect them by, e.g., passing a sheet of paper around at a
> > plenary), and by allowing people in the leadership to initiate
> > recall efforts (not only for the bodies on which they sit but
> > for other bodies).  The latter, which has almost nothing to do
> > with remote participants, could easily be dropped if there was
> > no support for it but I note that, draft-rescorla-istar-recall
> > is largely orthogonal to the change proposed in the present
> > draft: even if it were adopted, the proposed change would still
> > be worth careful consideration for cases in which, e.g., the
> > IESG felt there was a serious problem in the LLC Board.  The
> > proposal doesn't "fix" the recall procedure, it merely tunes its
> > first step a bit.
> >=20
> > My personal opinion is that, if the scope is as narrow as the
> > "fine-tune the recall procedure in that way" implied above, a
> > BOF, virtual or otherwise, would be a waste of time -- there has
> > already been enough discussion to indicate community interest
> > and we should move forward to discussing the draft (and not
> > procedures for doing so).  If you are convinced that needs a
> > short-lived WG to, e.g., avoid getting sidetracked, we should be
> > working on a charter for that WG with the expectation that its
> > approval will be expedited, not going through an elaborate set
> > of rituals that are not required by IETF procedures.  On the
> > other hand, if you are convinced that a quick virtual BOF would
> > be helpful, let's get on with it.
>=20
> This would be my preference. As I said in my earlier mail, if we can=20=

> separate the three pieces of the draft and see how the community feels=
=20
> about each of them, I think we will be in a good spot to looking at=20=

> writing a narrowly scoped charter for a WG.

I agree. When I read the draft I couldn't quite figure out why it includ=
ed certain changes and not others. Instead of arguing about the whole co=
llection of changes IETF community should decide which ones should be wo=
rked on. (If all of them ended up having rough consensus, that would be =
fine with me.).

> >=20
> > At the other extreme, perhaps the posting of this draft has
> > convinced the IESG that it is time to open up the entire
> > candidate selection and removal process and review it.  That
> > would (or at least might) include the nomcom eligibility
> > criteria; questions about whether the nomcom model itself is
> > appropriate in a contemporary IETF for which the implied
> > assumption that most of the nomcom members would have personal
> > knowledge of most of the candidates is no longer valid;
> > questions of term lengths, limits (or preferences), and
> > incumbent preferences; questions of whether, as the number of
> > bodies and slots for which the nomcom is expected to make
> > appointments has risen, having a single body do all of that work
> > in a single cycle is still appropriate; examination of whether,
> > in the environment of the IETF LLC having the ISOC President and
> > CEO appoint the Nomcom (and Recall Committee) chairs is still
> > appropriate both practically and from the standpoint of optics;
> > whether we can devise a mechanism for mid-term removal of people
> > who have misbehaved that is faster and more plausible than the
> > present petition, chair appointment, and two consecutive
> > committee model (or whether no such procedure is needed); and
> > perhaps even some issues that overlap into the old NEWTRK
> > effort.   That is obviously not a complete list: I'm confident
> > that you could add some things to it and that, given a few
> > hours, I probably could too.  =20
>=20
> Just my personal opinion with no hats at all. I think this will be a=20=

> =E2=80=9Cboil the ocean=E2=80=9D effort and I am not at all confident =
about its odds of=20
> success.

Agreed. I am very happy to work on a small problem (or a small collectio=
n of related problems) once there is agreement to work on it.

> > If that is the BOF proposal/charter you and the rest of the IESG
> > want, then it probably would benefit from a f2f discussion and
> > some of us should see if we can get a proposal for a BOF in
> > Montreal together within the next 48 hours.  However, any of us
> > who have either tried writing I-Ds that propose adjustments in
> > those areas or who have been through opening up some of the
> > issues in WGs know that it will be a long, time and resource
> > intensive, trek with many passionately-expressed opinions.
> > Based on experience with POISSON, I think it would be
> > unrealistic to expect a WG with that task list to converge and
> > complete its work in less than two or three years. Even were
> > that much time to be available, it would be nearly impossible to
> > get to significant conclusions without enthusiastic IESG support
> > for reviewing things and making changes as needed, support that
> > would need to be independent of whatever changes the WG and
> > community select.   Unless you can assure us that the conviction
> > and enthusiasm exist, even holding a BOF, much less chartering a
> > WG, would, IMO, be a waste of time that the IETF could better
> > spend on technical work.
>=20
> I whole-heartedly agree with you that this would probably be a waste o=
f time.

+1.

> > Even if a BOF proposal for this larger effort were wanted and if
> > only because how long that effort would take, I think there is a
> > very strong case for addressing the fine-tuning proposal now and
> > getting it done with.  They really are separate efforts even
> > though we might reasonably expect the larger one to make changes
> > that would obsolete some or all of the smaller and faster one.
> >=20
> > So, what would you like to see and how are you and the IESG
> > thinking about this?
> >=20
> > Just my opinion but, perhaps unfortunately, one that is informed
> > by experience.
>=20
> Much appreciated. I agree with you that a tightly scoped effort is mor=
e=20
> likely to succeed.=20

+1.

Best Regards,
Alexey


From nobody Tue Jun 11 05:59:24 2019
Return-Path: <ekr@rtfm.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 DBE32120158 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 ZMU37q_Z_3DU for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 05:59:19 -0700 (PDT)
Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (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 3B71A120025 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:59:19 -0700 (PDT)
Received: by mail-lj1-x244.google.com with SMTP id 16so11500829ljv.10 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 05:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fHjj72mfB2b8ntVk6R8Hhp7J6ExILfwPnaNpkPOdleA=; b=E32b0/riT0aZJgXJoQnoie6VzyNeQ4AJOMC5e/QaTN3kvnwpuYJhCsP6cHwFvfoabc U7dUu3CvthzfINoln5biG0ue7QxU4uIGu/6uggWtR4J+34gcgPy6tFth1Cnrqs/7RjHK dWwCkh9Ntk7+U/9fkrn6TgMrRPB8bgyMAQf4FZ0qT4kYsYXmw4NpeuG0TaxQ3dHXNgod lafwrlKcX1jBWPgF1OdZRHF0/FmtSGSyLtEuyMZ31FSOtYSbb+EpgSvVHX6nZ2UQ8OMb MJWx07XSC0TP5Lo81dhqRvUHqPC0cao38BjsMSh8EQwOOSzPf+9OcRKaB5I0SPJJgATU /++Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fHjj72mfB2b8ntVk6R8Hhp7J6ExILfwPnaNpkPOdleA=; b=WJDEG/rrMnzWYKIpS0Kl8k2rg4Duz+nPSYJM0v0vwmStL/GZbKFgQL77lxmaJ2HjyK 7ya6zT20tf03IZzuOcoOCwOymiWgNn+xC2FL33A3aJKdxSZUslYp7Zq8VTuP6C5ELJBJ fQViWxyusvQKkg0hfKm3Ff7W5PoUsVBll0mR8OmGsy1M/txE87yQnfjbPbmbQLTSQv4l CyMyxZyCu81zmauN9VTMXHyl58ZIdhqiEU41Y+O4Mjq5ry8PCTe7rQKMCTXs3UFMfd2a 8ax++vHaAHxRLwmyKYJZXbkz4PGKEkHXdfH6EvITXRGNlvPCY6l9q2uEH4Infqgosr0K ibGA==
X-Gm-Message-State: APjAAAUPwgLRQLv5cXnETd18KWX1Ayoqrcii6a6RCm1bvS08/mshNjiJ z4BnO66jWPcNiRNEAkD7OduVMqLtAvb74ObdXHv/xQ==
X-Google-Smtp-Source: APXvYqzLNi830gaYa8Jwg9kJQ+iZSh4xUNZvErJ7z0p7ODByNu96aDQCEuFd1YOveZ7J9oMqGPa6TiBIocfA6miSZ9Y=
X-Received: by 2002:a2e:9152:: with SMTP id q18mr21126704ljg.77.1560257957490;  Tue, 11 Jun 2019 05:59:17 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk>
In-Reply-To: <066801d52053$650ea290$2f2be7b0$@olddog.co.uk>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Jun 2019 05:58:40 -0700
Message-ID: <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: Eliot Lear <lear@cisco.com>, Alexey Melnikov <aamelnikov@fastmail.fm>,  S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org,  Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="000000000000508578058b0bddc5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/ITC4-0E2oGivcUd7Xl1KHcXoFBo>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 12:59:23 -0000

--000000000000508578058b0bddc5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 11, 2019 at 5:45 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> How about phrasing the problem as =E2=80=9CYou need too many people to si=
gn a
> recall petition, and that makes it too hard to achieve a recall=E2=80=9D?
>

Without taking a position on the merits, that seems more like a problem
statement. An even crisper statement, perhaps, would be "It's too hard to
achieve a recall"


We can agree or disagree about whether this is a problem and whether we
> want to work on it. That=E2=80=99s why we have BoFs and mailing lists.
>

Yes.

We can debate the correct solution for each problem, but (usually, when we
> have a BoF) the discussion of the solutions is sequenced after the
> discussion of the problems and agreement that we want to work on the
> problems.
>

Agreed. That's what I'm hoping for here.

-Ekr

Adrian
>
>
>
> *From:* Eric Rescorla <ekr@rtfm.com>
> *Sent:* 11 June 2019 13:32
> *To:* Eliot Lear <lear@cisco.com>
> *Cc:* Adrian Farrel <adrian@olddog.co.uk>; Alexey Melnikov <
> aamelnikov@fastmail.fm>; S Moonesamy <sm+ietf@elandsys.com>;
> eligibility-discuss@ietf.org; Suresh Krishnan <suresh.krishnan@gmail.com>=
;
> John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net>
> *Subject:* Re: [Eligibility-discuss] Virtual BoF for
> draft-moonesamy-recall-rev
>
>
>
>
>
>
>
> On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com> wrote:
>
>
>
>
>
> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>
>
>
> H/mm..  These don't seem like "issues" so much as restatements of the
> solution SM's draft proposes.
>
>
>
> To take a specific one, what issue is addressed by reducing the number of
> people required to sign the petition?
>
>
>
>
>
> Fewer people would have to set themselves up as targets for retribution;
> the pool of people able to serve on the recall committee is marginally
> increased.
>
>
>
> That's helpful, but I think it also suggests that the problem statement
> that SM has written is not really right: for instance, we could solve the
> problem of people being targets of retribution by having the signers be
> secret [0].. And we could address the pool issue by letting them serve on
> the committee.
>
>
>
> OTOH, it seems to me that the purpose of these requirements is to have a
> certain level of accountability for the people requesting the recall and =
to
> have a certain minimum level of support. So, is it clear that we actually
> want to relax those objectives?
>
>
>
> in any case, I think this exchange suggests that the first thing that's
> needed is a problem statement that's decoupled from the solutions being
> proposed.
>
>
>
> -Ekr
>
>
>
> [0] I'm aware that there are challenges here in verifying eligibility. I
> believe there are solutions here, though they are too small to be contain=
ed
> in this message.
>
>
>
> Eliot
>
>
>
> -Ekr
>
>
>
>
>
> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk> wrote=
:
>
> That's nice. I like the clarity.
>
> I also like that the worms are kept firmly in their cans. It is without
> doubt that a hundred other issues concerning the recall process could be
> aired, and I am certain that many people have different hot issues. But I
> firmly believe that addressing a few at a time is the best (only!) way to
> make progress.
>
> If it turns out that there is support for resolving any of these three
> issues, they can be quickly picked off and we can move on to other issues
> if
> there is interest. If there is no support for addressing these three
> concerns, then they can be put to one side and work can start on other
> issues if there is interest.
>
> For my part, I think that all three issues should be addressed, and I thi=
nk
> that the approaches suggested in SM's draft are a good starting point for
> discussion.
>
> Thanks,
> Adrian
>
> -----Original Message-----
> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On Behal=
f
> Of S Moonesamy
> Sent: 11 June 2019 11:45
> To: Suresh Krishnan <suresh.krishnan@gmail.com>;
> eligibility-discuss@ietf.org
> Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net>=
;
> Alexey Melnikov <aamelnikov@fastmail.fm>
> Subject: Re: [Eligibility-discuss] Virtual BoF for
> draft-moonesamy-recall-rev
>
> Hi Suresh,
>
> Please see a revised version of the BOF proposal to address your comments=
:
>
> Problem statement
>
>       The current description of the process for initiating petitions
> for recalls
>       for NomCom-appointed roles is described in RFC 7437 and is
> being updated in
>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses only
> three
>       specific issues with the petition process; other parts of the
> recall model
>       and other ways of removing Nomcom-appointees are explicitly out of
> scope.
>
>       The three issues are:
>
>       - Ineligibility of remote participants to seek redress through the
>         recall process;
>
>       - Reducing the number of signatories for a recall petition;
>
>       - Ineligibility of IAB and IESG Members and other Nomcom
>         Appointees to sign a recall petition.
>
> The purpose of the BOF is to examine the above-mentioned issues and
> determine,
> for each, whether it is sufficient interest and importance.
> draft-moonesamy-recall-rev
> is a possible starting point for the effort.
>
> Regards,
> S. Moonesamy
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>
>
>
>

--000000000000508578058b0bddc5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Tue, Jun 11, 2019 at 5:45 AM Adrian Farrel &lt;<a href=3D"mai=
lto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div class=
=3D"gmail-m_5496890430798475711WordSection1"><p class=3D"MsoNormal"><span>H=
ow about phrasing the problem as =E2=80=9CYou need too many people to sign =
a recall petition, and that makes it too hard to achieve a recall=E2=80=9D?=
</span></p></div></div></blockquote><div><br></div><div>Without taking a po=
sition on the merits, that seems more like a problem statement. An even cri=
sper statement, perhaps, would be &quot;It&#39;s too hard to achieve a reca=
ll&quot;<br></div><div><span><br></span></div><div><span> <br></span></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div =
class=3D"gmail-m_5496890430798475711WordSection1"><p class=3D"MsoNormal"><s=
pan>We can agree or disagree about whether this is a problem and whether we=
 want to work on it. That=E2=80=99s why we have BoFs and mailing lists.</sp=
an></p></div></div></blockquote><div><br></div><div>Yes.</div><div> <br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><d=
iv class=3D"gmail-m_5496890430798475711WordSection1"><p class=3D"MsoNormal"=
><span><u></u><u></u></span></p><p class=3D"MsoNormal"><span>We can debate =
the correct solution for each problem, but (usually, when we have a BoF) th=
e discussion of the solutions is sequenced after the discussion of the prob=
lems and agreement that we want to work on the problems. </span></p></div><=
/div></blockquote><div><br></div><div>Agreed. That&#39;s what I&#39;m hopin=
g for here.</div><div><br></div><div>-Ekr</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div class=3D"gmai=
l-m_5496890430798475711WordSection1"><p class=3D"MsoNormal"><span><u></u></=
span></p><p class=3D"MsoNormal"><span>Adrian<u></u><u></u></span></p><p cla=
ss=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal=
"><b><span lang=3D"EN-US">From:</span></b><span lang=3D"EN-US"> Eric Rescor=
la &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&g=
t; <br><b>Sent:</b> 11 June 2019 13:32<br><b>To:</b> Eliot Lear &lt;<a href=
=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt;<br><b>C=
c:</b> Adrian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_=
blank">adrian@olddog.co.uk</a>&gt;; Alexey Melnikov &lt;<a href=3D"mailto:a=
amelnikov@fastmail.fm" target=3D"_blank">aamelnikov@fastmail.fm</a>&gt;; S =
Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com" target=3D"_blank">s=
m+ietf@elandsys.com</a>&gt;; <a href=3D"mailto:eligibility-discuss@ietf.org=
" target=3D"_blank">eligibility-discuss@ietf.org</a>; Suresh Krishnan &lt;<=
a href=3D"mailto:suresh.krishnan@gmail.com" target=3D"_blank">suresh.krishn=
an@gmail.com</a>&gt;; John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.co=
m" target=3D"_blank">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=
=3D"mailto:warren@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;<b=
r><b>Subject:</b> Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy=
-recall-rev<u></u><u></u></span></p><p class=3D"MsoNormal"><u></u>=C2=A0<u>=
</u></p><div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><p c=
lass=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal"=
>On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear &lt;<a href=3D"mailto:lear@cisc=
o.com" target=3D"_blank">lear@cisco.com</a>&gt; wrote:<u></u><u></u></p></d=
iv><blockquote style=3D"border-color:currentcolor currentcolor currentcolor=
 rgb(204,204,204);border-style:none none none solid;border-width:medium med=
ium medium 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">=
<div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNor=
mal"><br><br><u></u><u></u></p><blockquote style=3D"margin-top:5pt;margin-b=
ottom:5pt"><div><p class=3D"MsoNormal">On 11 Jun 2019, at 13:37, Eric Resco=
rla &lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&=
gt; wrote:<u></u><u></u></p></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></=
u></p><div><div><div><p class=3D"MsoNormal">H/mm..=C2=A0 These don&#39;t se=
em like &quot;issues&quot; so much as restatements of the solution SM&#39;s=
 draft proposes.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=
=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">To take a specific one, =
what issue is addressed by reducing the number of people required to sign t=
he petition?<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=
=A0<u></u></p></div></div></div></blockquote><div><p class=3D"MsoNormal"><u=
></u>=C2=A0<u></u></p></div><p class=3D"MsoNormal">Fewer people would have =
to set themselves up as targets for retribution; the pool of people able to=
 serve on the recall committee is marginally increased.<u></u><u></u></p></=
div></div></blockquote><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>=
</div><div><p class=3D"MsoNormal">That&#39;s helpful, but I think it also s=
uggests that the problem statement that SM has written is not really right:=
 for instance, we could solve the problem of people being targets of retrib=
ution by having the signers be secret [0].. And we could address the pool i=
ssue by letting them serve on the committee.<u></u><u></u></p></div><div><p=
 class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNorm=
al">OTOH, it seems to me that the purpose of these requirements is to have =
a certain level of accountability for the people requesting the recall and =
to have a certain minimum level of support. So, is it clear that we actuall=
y want to relax those objectives?<u></u><u></u></p></div><div><p class=3D"M=
soNormal"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">in any =
case, I think this exchange suggests that the first thing that&#39;s needed=
 is a problem statement that&#39;s decoupled from the solutions being propo=
sed.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u=
></p></div><div><p class=3D"MsoNormal">-Ekr<u></u><u></u></p></div><div><p =
class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNorma=
l">[0] I&#39;m aware that there are challenges here in verifying eligibilit=
y. I believe there are solutions here, though they are too small to be cont=
ained in this message.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><=
u></u>=C2=A0<u></u></p></div><blockquote style=3D"border-color:currentcolor=
 currentcolor currentcolor rgb(204,204,204);border-style:none none none sol=
id;border-width:medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin-lef=
t:4.8pt;margin-right:0cm"><div><div><p class=3D"MsoNormal">Eliot<u></u><u><=
/u></p></div><div><p class=3D"MsoNormal"><br><br><u></u><u></u></p><blockqu=
ote style=3D"margin-top:5pt;margin-bottom:5pt"><div><div><div><p class=3D"M=
soNormal">-Ekr<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=
=C2=A0<u></u></p></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div>=
<div><p class=3D"MsoNormal">On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel &=
lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.c=
o.uk</a>&gt; wrote:<u></u><u></u></p></div><blockquote style=3D"border-colo=
r:currentcolor currentcolor currentcolor rgb(204,204,204);border-style:none=
 none none solid;border-width:medium medium medium 1pt;padding:0cm 0cm 0cm =
6pt;margin-left:4.8pt;margin-right:0cm"><p class=3D"MsoNormal">That&#39;s n=
ice. I like the clarity.<br><br>I also like that the worms are kept firmly =
in their cans. It is without<br>doubt that a hundred other issues concernin=
g the recall process could be<br>aired, and I am certain that many people h=
ave different hot issues. But I<br>firmly believe that addressing a few at =
a time is the best (only!) way to<br>make progress.<br><br>If it turns out =
that there is support for resolving any of these three<br>issues, they can =
be quickly picked off and we can move on to other issues if<br>there is int=
erest. If there is no support for addressing these three<br>concerns, then =
they can be put to one side and work can start on other<br>issues if there =
is interest.<br><br>For my part, I think that all three issues should be ad=
dressed, and I think<br>that the approaches suggested in SM&#39;s draft are=
 a good starting point for<br>discussion.<br><br>Thanks,<br>Adrian<br><br>-=
----Original Message-----<br>From: Eligibility-discuss &lt;<a href=3D"mailt=
o:eligibility-discuss-bounces@ietf.org" target=3D"_blank">eligibility-discu=
ss-bounces@ietf.org</a>&gt; On Behalf<br>Of S Moonesamy<br>Sent: 11 June 20=
19 11:45<br>To: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail=
.com" target=3D"_blank">suresh.krishnan@gmail.com</a>&gt;;<br><a href=3D"ma=
ilto:eligibility-discuss@ietf.org" target=3D"_blank">eligibility-discuss@ie=
tf.org</a><br>Cc: John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" t=
arget=3D"_blank">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=3D"ma=
ilto:warren@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;;<br>Ale=
xey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm" target=3D"_blank=
">aamelnikov@fastmail.fm</a>&gt;<br>Subject: Re: [Eligibility-discuss] Virt=
ual BoF for<br>draft-moonesamy-recall-rev<br><br>Hi Suresh,<br><br>Please s=
ee a revised version of the BOF proposal to address your comments:<br><br>P=
roblem statement<br><br>=C2=A0 =C2=A0 =C2=A0 The current description of the=
 process for initiating petitions <br>for recalls<br>=C2=A0 =C2=A0 =C2=A0 f=
or NomCom-appointed roles is described in RFC 7437 and is <br>being updated=
 in<br>=C2=A0 =C2=A0 =C2=A0 draft-ietf-iasa2-rfc7437bis.=C2=A0 The scope of=
 this work addresses only<br>three<br>=C2=A0 =C2=A0 =C2=A0 specific issues =
with the petition process; other parts of the <br>recall model<br>=C2=A0 =
=C2=A0 =C2=A0 and other ways of removing Nomcom-appointees are explicitly o=
ut of<br>scope.<br><br>=C2=A0 =C2=A0 =C2=A0 The three issues are:<br><br>=
=C2=A0 =C2=A0 =C2=A0 - Ineligibility of remote participants to seek redress=
 through the<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 recall process;<br><br>=C2=A0 =
=C2=A0 =C2=A0 - Reducing the number of signatories for a recall petition;<b=
r><br>=C2=A0 =C2=A0 =C2=A0 - Ineligibility of IAB and IESG Members and othe=
r Nomcom<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Appointees to sign a recall petitio=
n.<br><br>The purpose of the BOF is to examine the above-mentioned issues a=
nd<br>determine,<br>for each, whether it is sufficient interest and importa=
nce. <br>draft-moonesamy-recall-rev<br>is a possible starting point for the=
 effort.<br><br>Regards,<br>S. Moonesamy<br><br>-- <br>Eligibility-discuss =
mailing list<br><a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_=
blank">Eligibility-discuss@ietf.org</a><br><a href=3D"https://www.ietf.org/=
mailman/listinfo/eligibility-discuss" target=3D"_blank">https://www.ietf.or=
g/mailman/listinfo/eligibility-discuss</a><br><br>-- <br>Eligibility-discus=
s mailing list<br><a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D=
"_blank">Eligibility-discuss@ietf.org</a><br><a href=3D"https://www.ietf.or=
g/mailman/listinfo/eligibility-discuss" target=3D"_blank">https://www.ietf.=
org/mailman/listinfo/eligibility-discuss</a><u></u><u></u></p></blockquote>=
</div></div><p class=3D"MsoNormal">-- <br>Eligibility-discuss mailing list<=
br><a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligib=
ility-discuss@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listi=
nfo/eligibility-discuss" target=3D"_blank">https://www.ietf.org/mailman/lis=
tinfo/eligibility-discuss</a><u></u><u></u></p></div></blockquote></div><p =
class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></blockquote></div></div>=
</div></div></blockquote></div></div>

--000000000000508578058b0bddc5--


From nobody Tue Jun 11 08:29:35 2019
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 8A5FF1201C9 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:29:32 -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, 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=opendkim.org header.b=dZMfAcI3; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=QrlQ5Ml+
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 jWGGSys26lha for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:29:31 -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 9042C120043 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 08:29:31 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.213]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x5BFTAcL004072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jun 2019 08:29:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1560266964; x=1560353364; bh=7K3QEoQqtD4JY+h2q2BtJpftI3ctRYwzKV88dDN8cWk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dZMfAcI3BiVNgEyqRLEXw8mUkXKvL6r35jS3WgzwdLk5wR7ags8hECyG5UlG5SmVt KKce4TF0360pkDEnBP4GyJyEKPl/VI14jsLgin5EIbIY/vcEAMUL+r/Dx8eHc1cX7s a4zGs9yl86ytOa5ZBIbTLXaknx4/mqz6ygtUQVA8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1560266964; x=1560353364; i=@elandsys.com; bh=7K3QEoQqtD4JY+h2q2BtJpftI3ctRYwzKV88dDN8cWk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QrlQ5Ml+Mkn2+wDjfESi1cP4vBqrPurFg7ipA3gdotPXPaX2aR6lnDPLMlAOKsilx AO86/x5PqjdkNA34b1yiUANnyMXiaroBAun00Y899XsqtBxGKO2lD0hGQYzZ1jXYC6 rBAkxCCi0nx0/wbnfO/BBl4fkn+dXkxVLGLbr3I0=
Message-Id: <6.2.5.6.2.20190611065212.0d37b868@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jun 2019 08:28:57 -0700
To: Eric Rescorla <ekr@rtfm.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>, Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.g mail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.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/U5-Trlatv4Rj9xIZ6XTj8Lrv7Oo>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 15:29:33 -0000

Dear Mr Rescorla,
At 04:37 AM 11-06-2019, Eric Rescorla wrote:
>H/mm..  These don't seem like "issues" so much as restatements of 
>the solution SM's draft proposes.
>
>To take a specific one, what issue is addressed by reducing the 
>number of people required to sign the petition?

The above is a good question.  I'll propose the following changes to 
the second and third issues:

    - The required number of signatories sets a very high barrier to initiate
      a recall petition

    - The ineligibility of a member of appointing bodies from being a signatory
      restricts the initiation of a recall petition in a timely manner.

Regards,
S. Moonesamy 


From nobody Tue Jun 11 08:41:18 2019
Return-Path: <john-ietf@jck.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 0017012018B for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 cLCU89F6PfHW for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:41:14 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E146F120157 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 08:41:13 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1haitZ-000DKm-4P; Tue, 11 Jun 2019 11:41:09 -0400
Date: Tue, 11 Jun 2019 11:41:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Eric Rescorla <ekr@rtfm.com>
cc: S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org
Message-ID: <987121D4908D32C98579FEE8@PSB>
In-Reply-To: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/EKfou1ygw6a25tTrCBZ5vPeGQmc>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 15:41:16 -0000

--On Tuesday, June 11, 2019 14:21 +0200 Eliot Lear
<lear@cisco.com> wrote:

> 
> 
>> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>> 
>> H/mm..  These don't seem like "issues" so much as
>> restatements of the solution SM's draft proposes.
>> 
>> To take a specific one, what issue is addressed by reducing
>> the number of people required to sign the petition?
> 
> Fewer people would have to set themselves up as targets for
> retribution; the pool of people able to serve on the recall
> committee is marginally increased.

And, like the remote participants measure, if makes recall
initiation marginally more plausible, especially for remote
participants.

Thanks for mentioning the fear of retribution issue.  I've seen
it several times when people have felt unable to post negative
Last Call comments about documents in which one or more ADs are
involved as authors or by having significant skin in the game.
I had not considered it in the case of recall initiation, but it
is obviously going to be a concern.

It seems to me that, if a high level statement is needed, it
would be something like:

	"During the years since the Recall petitioning procedure
	was changed, with RFC 3777 in June 2004, to require
	Nomcom eligibility and 20 signatures it has become
	fairly clear that it is unusable in practice for any
	case that is not so completely obvious that a complex,
	time-consuming, multi-step, procedure should not be
	required.   It has also become progressively more unfair
	as the requirements exclude potential petitioners who
	are likely to be more knowledgeable than typical IETF
	f2f participants about particular types of abuses,
	whether because of the position those people hold or
	because as significant fraction of their participation
	is not f2f at IETF meetings.  It is also more burdensome
	for the latter group of participants than for those who
	are Nomcom-eligible under the normal rules, which is
	another source of unfairness.  The BoF is expected to
	address three specific aspects of those issues: the
	Nomcom eligibility requirement of physical meeting
	attendance, the number of signatures required on a
	petition, and the ineligibility of Nomcom-appointed
	members of leadership bodies to initiate petitions."

I remain concerned about broad statements opening up discussions
of the entire recall model (more about that in a note I have
written but hope I don't have to send), but perhaps something
like the above would respond to the need that others seem to be
feeling without significantly opening that door.

 best,
   john




From nobody Tue Jun 11 08:48:55 2019
Return-Path: <mcmanus@ducksong.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 F29871201A8 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:48:52 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=kly435ub; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=VFs1rIBX
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 Ks36ZkCsWiWv for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 08:48:49 -0700 (PDT)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 BAB6512024D for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 08:48:47 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560268126; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=kGc/fDDMCNidlzuCc+4oJ53OuqaSp93AbjdbAsqpwB/vWt0TbgIBXyT7GJsde/yunEdDRxc4a2KH6 w6pTM4DfLF80qdJUeHpPJOSFNhgey/XPMhz6ERR/TzyVO5a2HvND1sXZ2rcSz4thMHFYgTNNdIezVC adHOG8OFvVt4JOldZruQ5cNsosfbx1UqmnSTHSljX0jmpw4lhmEl9vSGgbtscKXwlG3gegQ8r9imO8 9GRJxOsfSkY/mFbYft0EKYSx9LJy9K9dfw56CesHfYSrUVdWiNw7D4ARBnSLxpX40B4g4trIiPfZKW OvtvMyK8/WwloZh+soBGQxe5uIPYecg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=DvOslJIslTnPHAnBMwSINnirgYSM5uSoByobHeLPAMc=; b=b8BVXIrq4aof/i9+086V764bEo/Z7g1/DegQASbXOVoTsv7523PDcAlzwixizP6wQUVuDfVMwscrK dkZrg7g9OcnKx1xFo0eKMvajJKR3S1ntZLHZ0RivnCH3mk1QVyGEC8d7/YGVF9S8pp4oDEwPrflc8T 4EQ1tHWJFbiHpCI7vTlrdjqgId1/tIZVGPNuRxKiPV1RUZOeQ8wAX1yuU7Os4BE0OJdkair9/zx+4q nVOZKJ1lPfnosjXtRq0Fm8QIMoPgjkLyvhXHbg9dGZNp5eNgsGVe2V6QGmO9fwObR2BeuSa/7Uig2a yZ37lhRZMmhm+R0t2XMZfcHsxcmoyOQ==
ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.167.179; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=DvOslJIslTnPHAnBMwSINnirgYSM5uSoByobHeLPAMc=; b=kly435ubYwTfGKo8zQTrXGNxGiwAOLJdP+DO3qhMqz9sbfM9JvG3VzgmvhyTOilom1um6tbluDW4J g2vi7lKtc/iIE1fd9TAqkosD5BuoY5xLgWfMbbMeMBL8RNlWaetVcinbm9JyYgvwtVTYgiLJb2JAzj SELgrLyILuMGrvWg=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=DvOslJIslTnPHAnBMwSINnirgYSM5uSoByobHeLPAMc=; b=VFs1rIBXCjznDHyI54MIznXWkufXDN/3mO2km7HuK76zu2nCJ0QWI/uKc51ay2FvxfgTal/AMVds+ X6p1MMNzigzGOUjxJ9ChUzUpO8cn9Bkv6dsmE+2spYOOTX4C3Ae2v17xZwCMpvS61LwVY1bUDm8FMN LQCbWUaaZ4HOR1fllLeJ1+b7LyvDe5d+WdJ0+ROCMbWsP23zuJD6+IshBjHZbGPXpJOyw/h5H2KtXl vRrA1MIhwaYRPVvDqNETD+bHv3LN2cVenykmWdIUiBXj7+tiWEcqOYZGLCTKJ/GX2Ovv8xm0DkhZVp eZAmc6G091UlAQb/xKdLtJL93CUvzuQ==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: 644c838a-8c60-11e9-ba65-db796b3fb7af
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.167.179
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-oi1-f179.google.com (unknown [209.85.167.179]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 644c838a-8c60-11e9-ba65-db796b3fb7af; Tue, 11 Jun 2019 15:48:44 +0000 (UTC)
Received: by mail-oi1-f179.google.com with SMTP id m206so9295871oib.12 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 08:48:44 -0700 (PDT)
X-Gm-Message-State: APjAAAXZ9CL0PhZJmZGZM64VoftQHgo/8ZEisWh3vsEpIkrRJ9gNPf2H Ut642VCwHieou4KUWkTVq4BmIJ7Jdi+9s6pXCI8=
X-Google-Smtp-Source: APXvYqzHWxTOP/Rqt++rsvhCFatIjPKzs0nEs3W/6BW78bRV+pfzoY98EK0SruwRc4LkzpWcOyYFoHCrKfyEBJHikjA=
X-Received: by 2002:aca:80f:: with SMTP id 15mr9602009oii.118.1560268123615; Tue, 11 Jun 2019 08:48:43 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com>
In-Reply-To: <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Tue, 11 Jun 2019 11:48:31 -0400
X-Gmail-Original-Message-ID: <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.gmail.com>
Message-ID: <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Eliot Lear <lear@cisco.com>,  Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>,  eligibility-discuss@ietf.org, Suresh Krishnan <suresh.krishnan@gmail.com>,  John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="0000000000004339e6058b0e3b27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/dZlllDHkmzu3E3iAapT1ho-bzYQ>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 15:48:53 -0000

--0000000000004339e6058b0e3b27
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

At least for the audience on this list,  I'm probably going to be in the
wilderness on this one.. I don't think a BoF here is the best use of IETF
energy..

There are really two questions. One is about the sweet spot of recall
difficulty - number of signers, etc... I believe that's an unimportant
question - leadership have short 2 year terms and its not like they possess
nuclear codes. Failsafes of some level of effectiveness exist already, and
the art of working around ineffective appointees is a common part of most
committee work that we should not expect to go away through rule tweaking.
Let's focus on tech, tech policy, and organizational outreach rather than
tuning the bureaucracy and the question proposed for the BoF is really just
what the right tuning is. Its not worth asking the plenary.

The larger question is about enfranchisement. but its not really about
recalls in any special way. This is an important question and, while the
various tradeoffs are apparent, the right answer is not obvious. More to
the point this is an important question in many contexts far more
significant than the recall process: nomcomm of course but perhaps the
entire question of leadership selection, hallway-track viability, interim
processes, funding, willingness to serve in leadership. etc. The definition
for recall is currently linked to the definition for nomcomm and that makes
a lot of sense. Let's discuss enfranchisement in a context where it will
actually have a meaningful impact and then apply the findings consistently
if changes are deemed appropriate.

-Patrick


On Tue, Jun 11, 2019 at 8:59 AM Eric Rescorla <ekr@rtfm.com> wrote:

>
> On Tue, Jun 11, 2019 at 5:45 AM Adrian Farrel <adrian@olddog.co.uk> wrote=
:
>
>> How about phrasing the problem as =E2=80=9CYou need too many people to s=
ign a
>> recall petition, and that makes it too hard to achieve a recall=E2=80=9D=
?
>>
>
> Without taking a position on the merits, that seems more like a problem
> statement. An even crisper statement, perhaps, would be "It's too hard to
> achieve a recall"
>
>
> We can agree or disagree about whether this is a problem and whether we
>> want to work on it. That=E2=80=99s why we have BoFs and mailing lists.
>>
>
> Yes.
>
> We can debate the correct solution for each problem, but (usually, when w=
e
>> have a BoF) the discussion of the solutions is sequenced after the
>> discussion of the problems and agreement that we want to work on the
>> problems.
>>
>
> Agreed. That's what I'm hoping for here.
>
> -Ekr
>
> Adrian
>>
>>
>>
>> *From:* Eric Rescorla <ekr@rtfm.com>
>> *Sent:* 11 June 2019 13:32
>> *To:* Eliot Lear <lear@cisco.com>
>> *Cc:* Adrian Farrel <adrian@olddog.co.uk>; Alexey Melnikov <
>> aamelnikov@fastmail.fm>; S Moonesamy <sm+ietf@elandsys.com>;
>> eligibility-discuss@ietf.org; Suresh Krishnan <suresh.krishnan@gmail.com=
>;
>> John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net>
>> *Subject:* Re: [Eligibility-discuss] Virtual BoF for
>> draft-moonesamy-recall-rev
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Jun 11, 2019 at 5:21 AM Eliot Lear <lear@cisco.com> wrote:
>>
>>
>>
>>
>>
>> On 11 Jun 2019, at 13:37, Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>
>>
>> H/mm..  These don't seem like "issues" so much as restatements of the
>> solution SM's draft proposes.
>>
>>
>>
>> To take a specific one, what issue is addressed by reducing the number o=
f
>> people required to sign the petition?
>>
>>
>>
>>
>>
>> Fewer people would have to set themselves up as targets for retribution;
>> the pool of people able to serve on the recall committee is marginally
>> increased.
>>
>>
>>
>> That's helpful, but I think it also suggests that the problem statement
>> that SM has written is not really right: for instance, we could solve th=
e
>> problem of people being targets of retribution by having the signers be
>> secret [0].. And we could address the pool issue by letting them serve o=
n
>> the committee.
>>
>>
>>
>> OTOH, it seems to me that the purpose of these requirements is to have a
>> certain level of accountability for the people requesting the recall and=
 to
>> have a certain minimum level of support. So, is it clear that we actuall=
y
>> want to relax those objectives?
>>
>>
>>
>> in any case, I think this exchange suggests that the first thing that's
>> needed is a problem statement that's decoupled from the solutions being
>> proposed.
>>
>>
>>
>> -Ekr
>>
>>
>>
>> [0] I'm aware that there are challenges here in verifying eligibility. I
>> believe there are solutions here, though they are too small to be contai=
ned
>> in this message.
>>
>>
>>
>> Eliot
>>
>>
>>
>> -Ekr
>>
>>
>>
>>
>>
>> On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel <adrian@olddog.co.uk>
>> wrote:
>>
>> That's nice. I like the clarity.
>>
>> I also like that the worms are kept firmly in their cans. It is without
>> doubt that a hundred other issues concerning the recall process could be
>> aired, and I am certain that many people have different hot issues. But =
I
>> firmly believe that addressing a few at a time is the best (only!) way t=
o
>> make progress.
>>
>> If it turns out that there is support for resolving any of these three
>> issues, they can be quickly picked off and we can move on to other issue=
s
>> if
>> there is interest. If there is no support for addressing these three
>> concerns, then they can be put to one side and work can start on other
>> issues if there is interest.
>>
>> For my part, I think that all three issues should be addressed, and I
>> think
>> that the approaches suggested in SM's draft are a good starting point fo=
r
>> discussion.
>>
>> Thanks,
>> Adrian
>>
>> -----Original Message-----
>> From: Eligibility-discuss <eligibility-discuss-bounces@ietf.org> On
>> Behalf
>> Of S Moonesamy
>> Sent: 11 June 2019 11:45
>> To: Suresh Krishnan <suresh.krishnan@gmail.com
>> <suresh.krishnan@gmail..com>>;
>> eligibility-discuss@ietf.org
>> Cc: John C Klensin <john-ietf@jck.com>; Warren Kumari <warren@kumari.net
>> >;
>> Alexey Melnikov <aamelnikov@fastmail.fm>
>> Subject: Re: [Eligibility-discuss] Virtual BoF for
>> draft-moonesamy-recall-rev
>>
>> Hi Suresh,
>>
>> Please see a revised version of the BOF proposal to address your comment=
s:
>>
>> Problem statement
>>
>>       The current description of the process for initiating petitions
>> for recalls
>>       for NomCom-appointed roles is described in RFC 7437 and is
>> being updated in
>>       draft-ietf-iasa2-rfc7437bis.  The scope of this work addresses onl=
y
>> three
>>       specific issues with the petition process; other parts of the
>> recall model
>>       and other ways of removing Nomcom-appointees are explicitly out of
>> scope.
>>
>>       The three issues are:
>>
>>       - Ineligibility of remote participants to seek redress through the
>>         recall process;
>>
>>       - Reducing the number of signatories for a recall petition;
>>
>>       - Ineligibility of IAB and IESG Members and other Nomcom
>>         Appointees to sign a recall petition.
>>
>> The purpose of the BOF is to examine the above-mentioned issues and
>> determine,
>> for each, whether it is sufficient interest and importance.
>> draft-moonesamy-recall-rev
>> is a possible starting point for the effort.
>>
>> Regards,
>> S. Moonesamy
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>> --
>> Eligibility-discuss mailing list
>> Eligibility-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>>
>>
>>
>> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>

--0000000000004339e6058b0e3b27
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">At least for the audience on this list,=C2=A0 I&#39;m prob=
ably going to be in the wilderness on this one.. I don&#39;t think a BoF he=
re is the best use of IETF energy..<div><br></div><div>There are really two=
 questions. One is about the sweet spot of recall difficulty - number of si=
gners, etc... I believe that&#39;s an unimportant question - leadership hav=
e short 2 year terms and its not like they possess nuclear codes. Failsafes=
 of some level of effectiveness exist already, and the art of working aroun=
d ineffective appointees is a common part of most committee work that we sh=
ould not expect to go away through rule tweaking. Let&#39;s focus on tech, =
tech policy, and organizational outreach rather than tuning the bureaucracy=
 and the question proposed for the BoF is really just what the right tuning=
 is. Its not worth asking the plenary.</div><div><br></div><div>The larger =
question is about enfranchisement. but its not really about recalls in any =
special way. This is an important question and, while the various tradeoffs=
 are apparent, the right answer is not obvious. More to the point this is a=
n important question in many contexts far more significant than the recall =
process: nomcomm of course but perhaps the entire question of leadership se=
lection, hallway-track viability, interim processes, funding, willingness t=
o serve in leadership. etc. The definition for recall is currently linked t=
o the definition for nomcomm and that makes a lot of sense. Let&#39;s discu=
ss enfranchisement in a context where it will actually have a meaningful im=
pact and then apply the findings consistently if changes are deemed appropr=
iate.</div><div><br></div><div>-Patrick</div><div><br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 11,=
 2019 at 8:59 AM Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"ltr"><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Jun 11, 2019 at 5:45 AM Adrian Farrel &lt;<a href=
=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div l=
ang=3D"EN-GB"><div class=3D"gmail-m_7570265644765763704gmail-m_549689043079=
8475711WordSection1"><p class=3D"MsoNormal"><span>How about phrasing the pr=
oblem as =E2=80=9CYou need too many people to sign a recall petition, and t=
hat makes it too hard to achieve a recall=E2=80=9D?</span></p></div></div><=
/blockquote><div><br></div><div>Without taking a position on the merits, th=
at seems more like a problem statement. An even crisper statement, perhaps,=
 would be &quot;It&#39;s too hard to achieve a recall&quot;<br></div><div><=
span><br></span></div><div><span> <br></span></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><div lang=3D"EN-GB"><div class=3D"gmail-m_7570265=
644765763704gmail-m_5496890430798475711WordSection1"><p class=3D"MsoNormal"=
><span>We can agree or disagree about whether this is a problem and whether=
 we want to work on it. That=E2=80=99s why we have BoFs and mailing lists.<=
/span></p></div></div></blockquote><div><br></div><div>Yes.</div><div> <br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"=
><div class=3D"gmail-m_7570265644765763704gmail-m_5496890430798475711WordSe=
ction1"><p class=3D"MsoNormal"><span><u></u><u></u></span></p><p class=3D"M=
soNormal"><span>We can debate the correct solution for each problem, but (u=
sually, when we have a BoF) the discussion of the solutions is sequenced af=
ter the discussion of the problems and agreement that we want to work on th=
e problems. </span></p></div></div></blockquote><div><br></div><div>Agreed.=
 That&#39;s what I&#39;m hoping for here.</div><div><br></div><div>-Ekr</di=
v><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lan=
g=3D"EN-GB"><div class=3D"gmail-m_7570265644765763704gmail-m_54968904307984=
75711WordSection1"><p class=3D"MsoNormal"><span><u></u></span></p><p class=
=3D"MsoNormal"><span>Adrian<u></u><u></u></span></p><p class=3D"MsoNormal">=
<span><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><b><span lang=
=3D"EN-US">From:</span></b><span lang=3D"EN-US"> Eric Rescorla &lt;<a href=
=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; <br><b>Sent=
:</b> 11 June 2019 13:32<br><b>To:</b> Eliot Lear &lt;<a href=3D"mailto:lea=
r@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt;<br><b>Cc:</b> Adrian =
Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@=
olddog.co.uk</a>&gt;; Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fast=
mail.fm" target=3D"_blank">aamelnikov@fastmail.fm</a>&gt;; S Moonesamy &lt;=
<a href=3D"mailto:sm%2Bietf@elandsys.com" target=3D"_blank">sm+ietf@elandsy=
s.com</a>&gt;; <a href=3D"mailto:eligibility-discuss@ietf.org" target=3D"_b=
lank">eligibility-discuss@ietf.org</a>; Suresh Krishnan &lt;<a href=3D"mail=
to:suresh.krishnan@gmail.com" target=3D"_blank">suresh.krishnan@gmail.com</=
a>&gt;; John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_=
blank">john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=3D"mailto:warre=
n@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;<br><b>Subject:</b=
> Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev<u></=
u><u></u></span></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><di=
v><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><p class=3D"MsoNorma=
l"><u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal">On Tue, Jun 11,=
 2019 at 5:21 AM Eliot Lear &lt;<a href=3D"mailto:lear@cisco.com" target=3D=
"_blank">lear@cisco.com</a>&gt; wrote:<u></u><u></u></p></div><blockquote s=
tyle=3D"border-color:currentcolor currentcolor currentcolor rgb(204,204,204=
);border-style:none none none solid;border-width:medium medium medium 1pt;p=
adding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm"><div><p class=3D=
"MsoNormal"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal"><br><br><u>=
</u><u></u></p><blockquote style=3D"margin-top:5pt;margin-bottom:5pt"><div>=
<p class=3D"MsoNormal">On 11 Jun 2019, at 13:37, Eric Rescorla &lt;<a href=
=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<u></=
u><u></u></p></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div=
><div><p class=3D"MsoNormal">H/mm..=C2=A0 These don&#39;t seem like &quot;i=
ssues&quot; so much as restatements of the solution SM&#39;s draft proposes=
.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></=
p></div><div><p class=3D"MsoNormal">To take a specific one, what issue is a=
ddressed by reducing the number of people required to sign the petition?<u>=
</u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></=
div></div></div></blockquote><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></=
u></p></div><p class=3D"MsoNormal">Fewer people would have to set themselve=
s up as targets for retribution; the pool of people able to serve on the re=
call committee is marginally increased.<u></u><u></u></p></div></div></bloc=
kquote><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p></div><div><p cl=
ass=3D"MsoNormal">That&#39;s helpful, but I think it also suggests that the=
 problem statement that SM has written is not really right: for instance, w=
e could solve the problem of people being targets of retribution by having =
the signers be secret [0].. And we could address the pool issue by letting =
them serve on the committee.<u></u><u></u></p></div><div><p class=3D"MsoNor=
mal"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">OTOH, it see=
ms to me that the purpose of these requirements is to have a certain level =
of accountability for the people requesting the recall and to have a certai=
n minimum level of support. So, is it clear that we actually want to relax =
those objectives?<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u=
>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">in any case, I think th=
is exchange suggests that the first thing that&#39;s needed is a problem st=
atement that&#39;s decoupled from the solutions being proposed.<u></u><u></=
u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div>=
<p class=3D"MsoNormal">-Ekr<u></u><u></u></p></div><div><p class=3D"MsoNorm=
al"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">[0] I&#39;m a=
ware that there are challenges here in verifying eligibility. I believe the=
re are solutions here, though they are too small to be contained in this me=
ssage.<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u><=
/u></p></div><blockquote style=3D"border-color:currentcolor currentcolor cu=
rrentcolor rgb(204,204,204);border-style:none none none solid;border-width:=
medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-r=
ight:0cm"><div><div><p class=3D"MsoNormal">Eliot<u></u><u></u></p></div><di=
v><p class=3D"MsoNormal"><br><br><u></u><u></u></p><blockquote style=3D"mar=
gin-top:5pt;margin-bottom:5pt"><div><div><div><p class=3D"MsoNormal">-Ekr<u=
></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><=
/div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div><p class=3D"M=
soNormal">On Tue, Jun 11, 2019 at 4:22 AM Adrian Farrel &lt;<a href=3D"mail=
to:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt; wrote=
:<u></u><u></u></p></div><blockquote style=3D"border-color:currentcolor cur=
rentcolor currentcolor rgb(204,204,204);border-style:none none none solid;b=
order-width:medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.=
8pt;margin-right:0cm"><p class=3D"MsoNormal">That&#39;s nice. I like the cl=
arity.<br><br>I also like that the worms are kept firmly in their cans. It =
is without<br>doubt that a hundred other issues concerning the recall proce=
ss could be<br>aired, and I am certain that many people have different hot =
issues. But I<br>firmly believe that addressing a few at a time is the best=
 (only!) way to<br>make progress.<br><br>If it turns out that there is supp=
ort for resolving any of these three<br>issues, they can be quickly picked =
off and we can move on to other issues if<br>there is interest. If there is=
 no support for addressing these three<br>concerns, then they can be put to=
 one side and work can start on other<br>issues if there is interest.<br><b=
r>For my part, I think that all three issues should be addressed, and I thi=
nk<br>that the approaches suggested in SM&#39;s draft are a good starting p=
oint for<br>discussion.<br><br>Thanks,<br>Adrian<br><br>-----Original Messa=
ge-----<br>From: Eligibility-discuss &lt;<a href=3D"mailto:eligibility-disc=
uss-bounces@ietf.org" target=3D"_blank">eligibility-discuss-bounces@ietf.or=
g</a>&gt; On Behalf<br>Of S Moonesamy<br>Sent: 11 June 2019 11:45<br>To: Su=
resh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail..com" target=3D"_=
blank">suresh.krishnan@gmail.com</a>&gt;;<br><a href=3D"mailto:eligibility-=
discuss@ietf.org" target=3D"_blank">eligibility-discuss@ietf.org</a><br>Cc:=
 John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">=
john-ietf@jck.com</a>&gt;; Warren Kumari &lt;<a href=3D"mailto:warren@kumar=
i.net" target=3D"_blank">warren@kumari.net</a>&gt;;<br>Alexey Melnikov &lt;=
<a href=3D"mailto:aamelnikov@fastmail.fm" target=3D"_blank">aamelnikov@fast=
mail.fm</a>&gt;<br>Subject: Re: [Eligibility-discuss] Virtual BoF for<br>dr=
aft-moonesamy-recall-rev<br><br>Hi Suresh,<br><br>Please see a revised vers=
ion of the BOF proposal to address your comments:<br><br>Problem statement<=
br><br>=C2=A0 =C2=A0 =C2=A0 The current description of the process for init=
iating petitions <br>for recalls<br>=C2=A0 =C2=A0 =C2=A0 for NomCom-appoint=
ed roles is described in RFC 7437 and is <br>being updated in<br>=C2=A0 =C2=
=A0 =C2=A0 draft-ietf-iasa2-rfc7437bis.=C2=A0 The scope of this work addres=
ses only<br>three<br>=C2=A0 =C2=A0 =C2=A0 specific issues with the petition=
 process; other parts of the <br>recall model<br>=C2=A0 =C2=A0 =C2=A0 and o=
ther ways of removing Nomcom-appointees are explicitly out of<br>scope.<br>=
<br>=C2=A0 =C2=A0 =C2=A0 The three issues are:<br><br>=C2=A0 =C2=A0 =C2=A0 =
- Ineligibility of remote participants to seek redress through the<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 recall process;<br><br>=C2=A0 =C2=A0 =C2=A0 - Redu=
cing the number of signatories for a recall petition;<br><br>=C2=A0 =C2=A0 =
=C2=A0 - Ineligibility of IAB and IESG Members and other Nomcom<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Appointees to sign a recall petition.<br><br>The purpo=
se of the BOF is to examine the above-mentioned issues and<br>determine,<br=
>for each, whether it is sufficient interest and importance. <br>draft-moon=
esamy-recall-rev<br>is a possible starting point for the effort.<br><br>Reg=
ards,<br>S. Moonesamy<br><br>-- <br>Eligibility-discuss mailing list<br><a =
href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibility-=
discuss@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/el=
igibility-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
eligibility-discuss</a><br><br>-- <br>Eligibility-discuss mailing list<br><=
a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibilit=
y-discuss@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/=
eligibility-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinf=
o/eligibility-discuss</a><u></u><u></u></p></blockquote></div></div><p clas=
s=3D"MsoNormal">-- <br>Eligibility-discuss mailing list<br><a href=3D"mailt=
o:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibility-discuss@ietf.=
org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-dis=
cuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eligibility-d=
iscuss</a><u></u><u></u></p></div></blockquote></div><p class=3D"MsoNormal"=
><u></u>=C2=A0<u></u></p></div></blockquote></div></div></div></div></block=
quote></div></div>
-- <br>
Eligibility-discuss mailing list<br>
<a href=3D"mailto:Eligibility-discuss@ietf.org" target=3D"_blank">Eligibili=
ty-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eligibility-discuss" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/eli=
gibility-discuss</a><br>
</blockquote></div>

--0000000000004339e6058b0e3b27--


From nobody Tue Jun 11 09:12:42 2019
Return-Path: <msj@nthpermutation.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 73EBD1202F5 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.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 NXiKRMIxHumf for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:12:38 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 9571A12006A for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 09:12:38 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id j19so15174142qtr.12 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 09:12:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ZbKBB605PV5ol4t1qQB+9Q1wUBLlotozRDymP6OAv6c=; b=kMsKA21ig2DTSYDfqcnXAqqYw6di12QmIk0otIOBONVmE56uQJXjCH2oTMookr8Pv6 7RAMuCrZLDH+cW/WOTRK8su89Bz0aE3v/HXiXNl3g3fsVo8CXBOoN5Ca6zxRvUYccEHb K5qWCN8WL5ye5NTPkpLrx+zs7V/T+zNJUz5rRnJ8ndwh2qCf8QYadVlFZpeTqG+rzsnv cG0GtTm/dBYLY5JqZ3EMhjMfxXMxI2do6UrvuXFho5nKhSHrW9yM3vBztM8iz/BQU/P/ mBOUO8OxKDLvc9GfW8q7G11+fVBw2SHuMkagZSTWeiflHYg+5UZ6m+9XT2QopiTktXSO //rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ZbKBB605PV5ol4t1qQB+9Q1wUBLlotozRDymP6OAv6c=; b=ApRI4sUlTM+vrCNDf/3px+tWUrf/LgeLWL/rraG522wzg7J8fCogIKU3MefYsooPFC vHkNrMaL5Qy+A8+h3DYhkPOIxmY/wW1KLCzafjmHHNp78O+9crUnhMT3HJ4vQ2jlBBum MQ1DvleCSjJf0aoKWvVYWaQ+Z0SMxboL0CCkh4Rqb29FIhN4NmTQSZSXnXtdDAkyAL4L aV6ITNbL0t0Qv3dYZXA9qtPbewpqGHYO/3BG7IbEer6gdFExIDv2C3mO8UIcF3YQlBg6 3ACrN9l8OXOGuiT8swoj5EyKkonznSuoqZ3beGATr1nVnBckP7aQ4QaN50cKfnnsygmx nMig==
X-Gm-Message-State: APjAAAWO5yS0LvSgJk+5mHPuJTIO5gmIv7tADAp3puvi5ctZ5pkPSIV1 lwe7qoU2OCfRCpY7y5S6w1YJ5V2iYd4=
X-Google-Smtp-Source: APXvYqxOFG4FB/2s57zV0HRc4QzdYvCZzrvyHbgttq6qynKRcpm/ihH8CMA2Bsdrn/EIXB99OozB9Q==
X-Received: by 2002:a0c:88f5:: with SMTP id 50mr47023993qvo.134.1560269557194;  Tue, 11 Jun 2019 09:12:37 -0700 (PDT)
Received: from ?IPv6:2601:152:4400:437c:c131:8095:616:e621? ([2601:152:4400:437c:c131:8095:616:e621]) by smtp.gmail.com with ESMTPSA id s23sm9568653qtj.56.2019.06.11.09.12.35 for <eligibility-discuss@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jun 2019 09:12:36 -0700 (PDT)
To: eligibility-discuss@ietf.org
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <987121D4908D32C98579FEE8@PSB>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <2aec60bf-5d1d-0f4b-b3bb-7b6558813dc0@nthpermutation.com>
Date: Tue, 11 Jun 2019 12:12:32 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <987121D4908D32C98579FEE8@PSB>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/oOgrywvQkFAXtmPHCacGDX9F04c>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 16:12:41 -0000

On 6/11/2019 11:41 AM, John C Klensin wrote:
> I remain concerned about broad statements opening up discussions
> of the entire recall model (more about that in a note I have
> written but hope I don't have to send), but perhaps something
> like the above would respond to the need that others seem to be
> feeling without significantly opening that door.

And I'd suggest that if we're going to expend any energy on this, we 
deal with the actual problems with the recall process rather than the 
deck chair counting.

Specifically, as currently described it's going to be something like a 
2-3 month process to start the recall, select the chair, form the 
committee, get them up to speed on the requirements for the position and 
reasonable reasons for recall, investigate the problem and finally have 
a vote.   That's a lot of time to leave a potential recallee in limbo 
and is probably not good for the IETF collaborative model.

And unlike the formation of the Nomcom and selection of the Nomcom 
chair, having the ISOC chair select the recall chair has a number of 
downsides including the possibility of the perception of selecting a 
chair for a desired result.


So instead of restating SM's conclusion as the goal of the BOF maybe use 
something like:

__________________________________

a) Evaluate the current recall model for changes;  whether other 
processes may be more appropriate for perceived needs; and whether the 
recall process should remain part of the management process for IETF 
leadership.

b) In light of (a) evaluate and possibly revise the initiation model for 
the recall process including the possibility of revising or supplanting 
the current petition based model; evaluate and possibly revise the model 
for selection of the recall committee and chair; evaluate and possibly 
revise the deliberation model for the recall committee and the rights of 
the proposed recallee during the process.

c) In light of the addition of the Ombudsman process, evaluate how the 
Ombudsman process should interact if at all with the recall process; for 
example should the Obudsteam be used to investigate charged wrong-doing 
asserted by a recall petition?

The BOF will report out one [or more] of the following:

a) Consensus is that no changes are necessary at this time.

b) We've come to consensus on the following changes:   {}  and we've 
been unable to come to consensus on the following topics {}.  These 
represent all of the topics considered by the group.  A draft covering 
the consensus items shall be forthcoming.

c) We've been unable to come to consensus, however the group has 
determined - through consensus - that there's enough interest to form a 
WG to address these topics.  We have X people who have agreed to 
participate actively. The charter is attached.

d) We've been unable to come to consensus and there is no consensus that 
further deliberation at this time will result in progress.

_____________________________________________

Or something like this.   As I asked earlier - do we actually have 10 or 
20 people who think they want to spend some time working this process or 
are we being DOS'd on a process question that few if any really care about?

We as the IETF have a hard problem of saying "no" at times - for WG 
creation, for the publication of limited impact documents, etc.  It may 
be time as a group to thank SM for his efforts and decline to proceed.

Later, Mike




From nobody Tue Jun 11 09:44:29 2019
Return-Path: <lear@cisco.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 F3CE1120350 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 U-Z6_qMZ1aGO for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:44:26 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEADD12016A for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 09:44:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3916; q=dns/txt; s=iport; t=1560271466; x=1561481066; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=L/DXS1tf9cZ8sAZtFBNrdXr5nomm+WEYq/Y3AYMrJUg=; b=AuNOljVfUvqruVXcLAwXjJjQ/nX79Kbe8gxHlJwxsdCdKup9WZLC+7Pv qAzqzbHNKfVfNGZOGkLea22oya35xHQKQvrmzjK8NdKaF054d2iAab9AA BUZD44lnhGpah8XxnT26RIY09rWK5Gs7CywrV6oHpeeysWx/QcwDAPwRo 8=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAADL2f9c/xbLJq1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAIBAQEBCwGBDoI+MiiEFYh7jAWSYId8AgcBAQEJAwEBLwE?= =?us-ascii?q?BhEACgyE3Bg4BAwEBBAEBAgEEbSiFSgEBAQMBI1YFCwsEFCoCAlcGE4MiAYF?= =?us-ascii?q?7D6lzgTGFR4RfEIE0AYFPiiSBf4ERJx+CTD6HTjKCJgSUDpUjCYISghuBBpA?= =?us-ascii?q?kG40CiiCgToMHAgQGBQIVgWUigVgzGggbFWUBgkE+kBY9AzCQZAEB?=
X-IronPort-AV: E=Sophos;i="5.63,362,1557187200";  d="asc'?scan'208,217";a="12981768"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 16:44:23 +0000
Received: from [10.61.194.73] ([10.61.194.73]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x5BGiMNI012086 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 16:44:23 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E3D1BDBB-A71D-4BC4-9770-DAA1445A8169"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 18:44:22 +0200
In-Reply-To: <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Adrian Farrel <adrian@olddog.co.uk>, Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>
To: Patrick McManus <mcmanus@ducksong.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.194.73, [10.61.194.73]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/C7Un6icHfrmeuRYlCbyn9qqVglQ>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 16:44:28 -0000

--Apple-Mail=_E3D1BDBB-A71D-4BC4-9770-DAA1445A8169
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_4BEEDB19-A787-450E-BEDD-C51DE3FB2D85"


--Apple-Mail=_4BEEDB19-A787-450E-BEDD-C51DE3FB2D85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 11 Jun 2019, at 17:48, Patrick McManus <mcmanus@ducksong.com> =
wrote:
>=20
> . One is about the sweet spot of recall difficulty - number of =
signers, etc... I believe that's an unimportant question - leadership =
have short 2 year terms and its not like they possess nuclear codes.


I think this very much depends on your business.  Knowing that the =
standard can be dinked right up until the IESG, if someone disappears =
from that process, your feature scheduling goes out the window.  =
Possibly your release planning as well.  Now some variability has to be =
allowed for in this process.  Weeks, maybe even small number of months.  =
Large #s of months or even years is not an acceptable #.

And that would encourage people to do work elsewhere.  And so it=E2=80=99s=
 harmful to this organization when someone fails to show up for an =
extended period of time.

Eliot

--Apple-Mail=_4BEEDB19-A787-450E-BEDD-C51DE3FB2D85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 11 Jun 2019, at 17:48, Patrick McManus &lt;<a =
href=3D"mailto:mcmanus@ducksong.com" =
class=3D"">mcmanus@ducksong.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">. One is about the sweet spot of =
recall difficulty - number of signers, etc... I believe that's an =
unimportant question - leadership have short 2 year terms and its not =
like they possess nuclear codes.</span></div></blockquote></div><br =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">I think =
this very much depends on your business. &nbsp;Knowing that the standard =
can be dinked right up until the IESG, if someone disappears from that =
process, your feature scheduling goes out the window. &nbsp;Possibly =
your release planning as well. &nbsp;Now some variability has to be =
allowed for in this process. &nbsp;Weeks, maybe even small number of =
months. &nbsp;Large #s of months or even years is not an acceptable =
#.</div><div class=3D""><br class=3D""></div><div class=3D"">And that =
would encourage people to do work elsewhere. &nbsp;And so it=E2=80=99s =
harmful to this organization when someone fails to show up for an =
extended period of time.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Eliot</div></body></html>=

--Apple-Mail=_4BEEDB19-A787-450E-BEDD-C51DE3FB2D85--

--Apple-Mail=_E3D1BDBB-A71D-4BC4-9770-DAA1445A8169
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTgo4LlIIJ5lIBumWpugA9nE248uAUCXP/aZgAKCRBugA9nE248
uH32AKCT/tfehVi3TNITB/ybMQs1wh3muQCeJTlVHTbT9gSNg1kBTRGu/DtEAwM=
=9ULd
-----END PGP SIGNATURE-----

--Apple-Mail=_E3D1BDBB-A71D-4BC4-9770-DAA1445A8169--


From nobody Tue Jun 11 10:18:36 2019
Return-Path: <john-ietf@jck.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 3854012010C for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 10:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 wai1AdDEZF02 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 10:18:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891D0120025 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 10:18:33 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hakPm-000DWf-F6; Tue, 11 Jun 2019 13:18:30 -0400
Date: Tue, 11 Jun 2019 13:18:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Patrick McManus <mcmanus@ducksong.com>
cc: eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>
Message-ID: <9C18B7DC9C307B3DBD8E76BA@PSB>
In-Reply-To: <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.gmail.c om> <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/PgpbBMVFnj69twtgq2dXWQugoGw>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 17:18:35 -0000

--On Tuesday, June 11, 2019 18:44 +0200 Eliot Lear
<lear@cisco.com> wrote:

> 
> 
>> On 11 Jun 2019, at 17:48, Patrick McManus
>> <mcmanus@ducksong.com> wrote:
>> 
>> . One is about the sweet spot of recall difficulty - number
>> of signers, etc... I believe that's an unimportant question -
>> leadership have short 2 year terms and its not like they
>> possess nuclear codes.
> 
> 
> I think this very much depends on your business.  Knowing that
> the standard can be dinked right up until the IESG, if someone
> disappears from that process, your feature scheduling goes out
> the window.  Possibly your release planning as well.  Now some
> variability has to be allowed for in this process.  Weeks,
> maybe even small number of months.  Large #s of months or even
> years is not an acceptable #.

It seem to me that this would apply even more strongly if
someone on, say, the IESG decided to adopt an obstructionist
position relative to your ideas, your company, or, noting your
earlier comment about retaliation, you as an individual.  In
such situations, the IESG has tools to move ahead in spite of
that AD, but they have proven in the past to be time-consuming
and to impede overall progress when the offender is obstinate,
so trade-offs get made, maybe trade-offs that would be less
necessary with a more effective recall mechanism.

Personally, I believe that the IETF is in need of a faster and
lighter-weight mechanism for getting rid of someone who has
disappeared then relying on the present recall process.
However, because I've seen little or no evidence that the
community is ready to deal with a redesign of the recall model,
or the nomination and selection models more generally, I
continue to hope that this discussion can be kept focused on the
particular issues in the petitioning process identified in
draft-moonesamy-recall-rev

best,
   john

> 
> And that would encourage people to do work elsewhere.  And so
> it's harmful to this organization when someone fails to show
> up for an extended period of time.
> 
> Eliot





From nobody Tue Jun 11 10:34:06 2019
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 A03D8120321 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:24:10 -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, 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=opendkim.org header.b=dWp0PFgR; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=4pWgM7X5
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 V8YcJEDNlbjI for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 09:24:09 -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 8265D12032B for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 09:24:09 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.213]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x5BGNbQH000431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jun 2019 09:23:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1560270234; x=1560356634; bh=CK3eagbJ4euK799r43CxhL9avFHKlqXY9mc+Bb8jIvU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dWp0PFgRhZp5Jynhvk1qurL7K/zSBC8cOBkYxhY3E892LS7oxUjPY02tBRabILYnv uK10jIWj5rAgQB0QOEn58T4CaRXd9aRs3rHd1tnIm9+UjyHRF6R8MGCwq4cgN+gGpT E3dRsQmf66Z+icypDaO/Uz49Zk8abcZMkNQzToFc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1560270234; x=1560356634; i=@elandsys.com; bh=CK3eagbJ4euK799r43CxhL9avFHKlqXY9mc+Bb8jIvU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4pWgM7X57hfy6Zz/IvpNuvwHLstiEWQiB+QLe0tQb4qDui7qq0Kl/TirThJoL3+8j 7l6dmm54TsgwtX4HKsg375ZXaNEdlcQylxXHboocpZD0fWP3cvn+WtUGZg1t4Dx6D8 6r3LQW0DIGyJe1It4rb2nzg4599RRHhsMwS2O02c=
Message-Id: <6.2.5.6.2.20190611090352.08372f80@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jun 2019 09:15:34 -0700
To: Patrick McManus <mcmanus@ducksong.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Eliot Lear <lear@cisco.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, S Moonesamy <sm+ietf@elandsys.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, Warren Kumari <warren@kumari.net>, Eric Rescorla <ekr@rtfm.com>
In-Reply-To: <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.g mail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <CAOdDvNpCbkXU69X6PCfJ9q8cG-RA+mPHzWu=ga-Yq_0nMV_-+w@mail.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/7JLX1A2l3rH2nC3QpWxDDB2Zibk>
X-Mailman-Approved-At: Tue, 11 Jun 2019 10:34:05 -0700
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 16:24:11 -0000

Hi Patrick,
At 08:48 AM 11-06-2019, Patrick McManus wrote:
>The larger question is about enfranchisement. but its not really 
>about recalls in any special way. This is an important question and, 
>while the various tradeoffs are

The intent was to put in an effort which is sustainable instead of 
tackling larger questions without any proposal in sight and which 
would require a huge effort.

Regards,
S. Moonesamy 


From nobody Tue Jun 11 10:53:59 2019
Return-Path: <jmh@joelhalpern.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 82A5B120136 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 10:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 K4IFApvWspVC for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 10:53:55 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 6AD3F120044 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 10:53:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 45Nd0g15YSzjXj9; Tue, 11 Jun 2019 10:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1560275635; bh=xBkC/frS2STRfql3D0mWJPIjNSwV5HiKWU+johTEjX8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=XcVR65xon0SRnCsfyAwsnDQphqaH6PAxlZglVuz4wmqbUrrBYcOvRT1q/vUfjHU7e zWc2mBWGnfUW624GBO2LXur60SadGUTuKrGuNCO30qCKEzUrdFIkHLbgnqd1Sszwl2 CP1VOXnjrwg1fyKZJMJ/qsjJ6V0C+0mYhn4itFEI=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [147.178.4.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 45Nd0f2ztXzjXDM; Tue, 11 Jun 2019 10:53:54 -0700 (PDT)
To: Michael StJohns <msj@nthpermutation.com>, eligibility-discuss@ietf.org
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <987121D4908D32C98579FEE8@PSB> <2aec60bf-5d1d-0f4b-b3bb-7b6558813dc0@nthpermutation.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <43a6082f-2c6d-8f2e-e75c-bd354bd41914@joelhalpern.com>
Date: Tue, 11 Jun 2019 13:53:52 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <2aec60bf-5d1d-0f4b-b3bb-7b6558813dc0@nthpermutation.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/MaB_0oRDh_kfCM9IT_pblDawUJ0>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 17:53:59 -0000

Given the IETF history (at least as seen through my narrow keyhole) on 
handling process changes, there is a BIG advantage to doing small things.

If we undertake the discussion proposed below, it will take a very long 
time, and likely end up in the typical distribution of a modest number 
of people strongly in favor (of something) a lot of people wondering 
what the fuss is about, and a roughly similar modest number of people 
strongly opposed (to whatever).

In contrast, the focused items SM has proposed strike me as something 
that can be discussed in a reasonable time, and if folks stop trying to 
generalize the issue, actually get resolved (one way or the other).

I don't care whether the mechanism is a BoF, email list sponsored by the 
IETF chair, or a rotting band of singers (all singing badly).

Yours,
Joel

On 6/11/19 12:12 PM, Michael StJohns wrote:
> On 6/11/2019 11:41 AM, John C Klensin wrote:
>> I remain concerned about broad statements opening up discussions
>> of the entire recall model (more about that in a note I have
>> written but hope I don't have to send), but perhaps something
>> like the above would respond to the need that others seem to be
>> feeling without significantly opening that door.
> 
> And I'd suggest that if we're going to expend any energy on this, we 
> deal with the actual problems with the recall process rather than the 
> deck chair counting.
> 
> Specifically, as currently described it's going to be something like a 
> 2-3 month process to start the recall, select the chair, form the 
> committee, get them up to speed on the requirements for the position and 
> reasonable reasons for recall, investigate the problem and finally have 
> a vote.   That's a lot of time to leave a potential recallee in limbo 
> and is probably not good for the IETF collaborative model.
> 
> And unlike the formation of the Nomcom and selection of the Nomcom 
> chair, having the ISOC chair select the recall chair has a number of 
> downsides including the possibility of the perception of selecting a 
> chair for a desired result.
> 
> 
> So instead of restating SM's conclusion as the goal of the BOF maybe use 
> something like:
> 
> __________________________________
> 
> a) Evaluate the current recall model for changes;  whether other 
> processes may be more appropriate for perceived needs; and whether the 
> recall process should remain part of the management process for IETF 
> leadership.
> 
> b) In light of (a) evaluate and possibly revise the initiation model for 
> the recall process including the possibility of revising or supplanting 
> the current petition based model; evaluate and possibly revise the model 
> for selection of the recall committee and chair; evaluate and possibly 
> revise the deliberation model for the recall committee and the rights of 
> the proposed recallee during the process.
> 
> c) In light of the addition of the Ombudsman process, evaluate how the 
> Ombudsman process should interact if at all with the recall process; for 
> example should the Obudsteam be used to investigate charged wrong-doing 
> asserted by a recall petition?
> 
> The BOF will report out one [or more] of the following:
> 
> a) Consensus is that no changes are necessary at this time.
> 
> b) We've come to consensus on the following changes:   {}  and we've 
> been unable to come to consensus on the following topics {}.  These 
> represent all of the topics considered by the group.  A draft covering 
> the consensus items shall be forthcoming.
> 
> c) We've been unable to come to consensus, however the group has 
> determined - through consensus - that there's enough interest to form a 
> WG to address these topics.  We have X people who have agreed to 
> participate actively. The charter is attached.
> 
> d) We've been unable to come to consensus and there is no consensus that 
> further deliberation at this time will result in progress.
> 
> _____________________________________________
> 
> Or something like this.   As I asked earlier - do we actually have 10 or 
> 20 people who think they want to spend some time working this process or 
> are we being DOS'd on a process question that few if any really care about?
> 
> We as the IETF have a hard problem of saying "no" at times - for WG 
> creation, for the publication of limited impact documents, etc.  It may 
> be time as a group to thank SM for his efforts and decline to proceed.
> 
> Later, Mike
> 
> 
> 


From nobody Tue Jun 11 11:13:26 2019
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 AB6661201D1 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 11:13:25 -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, 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=opendkim.org header.b=ucJjPshB; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=Fzm+BgKq
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 d51_zh_qQ-YS for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 11:13:24 -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 652A51201CF for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 11:13:21 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.213]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x5BID6eB006192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jun 2019 11:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1560276800; x=1560363200; bh=+ED/TMWiDOUveFMniIl1LerMbOlhXpoBxq5ktNqlxqY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ucJjPshBZMF6yYFCKnkMHtd6f0v7XcxNgs6j25Hpxf1aL7hS+Jv89o5qiPisy8Bj1 xohFK+MU1kZAKrPNuZdwPfc+co5cLX+5OSqEI8UaaAArQRUaJ94aTCSyDO2OB78q/O 5yexqsZgHfPq3jkO18VK8Kbgy+3tkaulYGsA70PY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1560276800; x=1560363200; i=@elandsys.com; bh=+ED/TMWiDOUveFMniIl1LerMbOlhXpoBxq5ktNqlxqY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Fzm+BgKqVvDOgfFhHkNkqOqLCGkmtc1dbHJCWFjN+JrQdkrsVTdc515ZD/n6xPDWh l/XTy9egjKSzUBH8X86SZpE6Xdqmg3EbyqIkDZcdwXxU+jt0kbe0vw+BBZA3SEOEiX N0Gb4f7VPUxQipHZ1V4n1KjDhel3I4wbELyXsWWU=
Message-Id: <6.2.5.6.2.20190611102407.0d353e30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jun 2019 11:12:51 -0700
To: Eliot Lear <lear@cisco.com>, eligibility-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Alexey Melnikov <aamelnikov@fastmail.fm>, Suresh Krishnan <suresh.krishnan@gmail.com>, Warren Kumari <warren@kumari.net>
In-Reply-To: <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/LJq9CIpAMTbn9-D2B6_0v5GpzMM>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 18:13:25 -0000

Hi Eliot,
At 05:21 AM 11-06-2019, Eliot Lear wrote:
>Fewer people would have to set themselves up as targets for 
>retribution; the pool of people able to serve on the recall 
>committee is marginally increased.

Thank you for mentioning the above.

It is not easy to argue against a proposal which is authored by the 
"leadership".  There is a perception that there could be retribution 
against the persons listed as signatories.  How many IETF 
participants are willing to face that?

Regards,
S. Moonesamy 


From nobody Tue Jun 11 12:16:21 2019
Return-Path: <lear@cisco.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 BED0E120099 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 12:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 uyUXN7ohwOOD for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 12:16:17 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E729D120045 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 12:16:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4833; q=dns/txt; s=iport; t=1560280577; x=1561490177; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=miVCoDwf3HEt5vnwYe2OXPhwBWTDDejfP4jZgmBrwDs=; b=eOkrYGduwknOYyPr9F/WBoA2j2FBPjnISxgVZpBF69fxb7cCGS0tZi7F mtMxCxARyXY/oynObf0lzRY5JOb+BK6r8484fhg9Q2zeobuJwnes9STYn gIVw+HLvzfqIyDRgJz5Twxw/9EqmpZpY/J4sTgtNXM2ErSTxxjQqf90el o=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0APAACT/f9c/xbLJq1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBVAEBAQEBAQsBgWGBGVIyKIQViHuMBH6ZXgIHAQEBCQM?= =?us-ascii?q?BARgLDAEBg3pGAoMhNwYOAQMBAQQBAQIBBG0cDIVKAQEBAwEBASFLCwULCxg?= =?us-ascii?q?qAgInMAYTgyIBgXsPD6lLgTGFR4RcCgaBNAGBT4okgX+BEScfghc1PoJhAQG?= =?us-ascii?q?BOoMxMoImBJQOlDlqCYISghuBBpAkG40CiiCgToMHAgQGBQIVgWUigVgzGgg?= =?us-ascii?q?bFTsqAYJBPopVhUE9AzCOEoJSAQE?=
X-IronPort-AV: E=Sophos;i="5.63,362,1557187200";  d="asc'?scan'208";a="13043187"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2019 19:16:14 +0000
Received: from [10.61.163.185] ([10.61.163.185]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x5BJGDeX025940 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Jun 2019 19:16:14 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <D844882E-53A5-4F2F-915C-DDFC6ED54E80@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_0A666A35-3D0A-4176-8514-389C9FAD9612"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 21:16:13 +0200
In-Reply-To: <2aec60bf-5d1d-0f4b-b3bb-7b6558813dc0@nthpermutation.com>
Cc: eligibility-discuss@ietf.org
To: Michael StJohns <msj@nthpermutation.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <987121D4908D32C98579FEE8@PSB> <2aec60bf-5d1d-0f4b-b3bb-7b6558813dc0@nthpermutation.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.163.185, [10.61.163.185]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/gPuTZMFzYF4AIO8fR8KYPBahcIg>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 19:16:20 -0000

--Apple-Mail=_0A666A35-3D0A-4176-8514-389C9FAD9612
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Mike,

With regard to your BoF proposal below, I think it=E2=80=99s fine, but =
it looks more like a WG charter.  I propose we use it as a starting =
point as such.  I would add some scoping so that this doesn=E2=80=99t =
stretch beyond recalls.

Eliot

> On 11 Jun 2019, at 18:12, Michael StJohns <msj@nthpermutation.com> =
wrote:
>=20
> On 6/11/2019 11:41 AM, John C Klensin wrote:
>> I remain concerned about broad statements opening up discussions
>> of the entire recall model (more about that in a note I have
>> written but hope I don't have to send), but perhaps something
>> like the above would respond to the need that others seem to be
>> feeling without significantly opening that door.
>=20
> And I'd suggest that if we're going to expend any energy on this, we =
deal with the actual problems with the recall process rather than the =
deck chair counting.
>=20
> Specifically, as currently described it's going to be something like a =
2-3 month process to start the recall, select the chair, form the =
committee, get them up to speed on the requirements for the position and =
reasonable reasons for recall, investigate the problem and finally have =
a vote.   That's a lot of time to leave a potential recallee in limbo =
and is probably not good for the IETF collaborative model.
>=20
> And unlike the formation of the Nomcom and selection of the Nomcom =
chair, having the ISOC chair select the recall chair has a number of =
downsides including the possibility of the perception of selecting a =
chair for a desired result.
>=20
>=20
> So instead of restating SM's conclusion as the goal of the BOF maybe =
use something like:
>=20
> __________________________________
>=20
> a) Evaluate the current recall model for changes;  whether other =
processes may be more appropriate for perceived needs; and whether the =
recall process should remain part of the management process for IETF =
leadership.
>=20
> b) In light of (a) evaluate and possibly revise the initiation model =
for the recall process including the possibility of revising or =
supplanting the current petition based model; evaluate and possibly =
revise the model for selection of the recall committee and chair; =
evaluate and possibly revise the deliberation model for the recall =
committee and the rights of the proposed recallee during the process.
>=20
> c) In light of the addition of the Ombudsman process, evaluate how the =
Ombudsman process should interact if at all with the recall process; for =
example should the Obudsteam be used to investigate charged wrong-doing =
asserted by a recall petition?
>=20
> The BOF will report out one [or more] of the following:
>=20
> a) Consensus is that no changes are necessary at this time.
>=20
> b) We've come to consensus on the following changes:   {}  and we've =
been unable to come to consensus on the following topics {}.  These =
represent all of the topics considered by the group.  A draft covering =
the consensus items shall be forthcoming.
>=20
> c) We've been unable to come to consensus, however the group has =
determined - through consensus - that there's enough interest to form a =
WG to address these topics.  We have X people who have agreed to =
participate actively. The charter is attached.
>=20
> d) We've been unable to come to consensus and there is no consensus =
that further deliberation at this time will result in progress.
>=20
> _____________________________________________
>=20
> Or something like this.   As I asked earlier - do we actually have 10 =
or 20 people who think they want to spend some time working this process =
or are we being DOS'd on a process question that few if any really care =
about?
>=20
> We as the IETF have a hard problem of saying "no" at times - for WG =
creation, for the publication of limited impact documents, etc.  It may =
be time as a group to thank SM for his efforts and decline to proceed.
>=20
> Later, Mike
>=20
>=20
>=20
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss


--Apple-Mail=_0A666A35-3D0A-4176-8514-389C9FAD9612
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTgo4LlIIJ5lIBumWpugA9nE248uAUCXP/9/QAKCRBugA9nE248
uOJeAKC7/7c5Ji7XVrJ51U6ldW11yom2+ACgn+VJeesBchSmxJgsc6g+uKs4Fow=
=WYpp
-----END PGP SIGNATURE-----

--Apple-Mail=_0A666A35-3D0A-4176-8514-389C9FAD9612--


From nobody Tue Jun 11 15:42:23 2019
Return-Path: <mcmanus@ducksong.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 0FDF5120074 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 15:42:21 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=gDMmzwA9; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=qyVIDjoc
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 l932N06989E0 for <eligibility-discuss@ietfa.amsl.com>; Tue, 11 Jun 2019 15:42:18 -0700 (PDT)
Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (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 B9E4812000F for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 15:42:17 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1560292936; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=QbsYNaEl5hJB3Mcm57BgIga7E5uhOcrznUR5JysFhpDf4IIdx2/lzbClVoLzLKuRSXJBEtb98VKOA 8JPxFaag1MlL5Z083eX/GRVh/YdrTsK7S/v5205ZJKq7k9gfQxYVVdJuJv+RZGvhdZAJ1LMJ1qkXFA vVpBkO6yQuH9b3c+Ka20qcMR2qISUcqlLxSe9ZVwJfEnDQS1UL87z1dcZG5RlPuctfpIRoaqPiCRj2 HYMPsmTFKVJiboebs2PS7yuPTLAyahIRWAT7yU2wuEJ3rumgQEX1uGXGbESpA2rN38OsVRq/Rc4O/u HVczwJjB9LG3JUcsu6dgol/V9xurHgg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=RCM/IbFSlFzoTN8ouzH8/6RHsVxgAwYzKcKbYUsqOv4=; b=NXJPtDEvG92ORT2q5KhOvYbbf0OaGmN6Zo/6U4iCszak2m7JukG24hQgtVcT1Jv+c/CssD8JSx3Yn s9SHYDux5+riWYxC54qhlPLmma8L94gU0zXf8K8U2QnDi4+QmWIw+sm6ktnhi9GDn104pZN7ji+FD8 cGK9IoIZpodfLmiNLbMZtzo+/eqjFtIUsWzH+9FCxTFK20EaNKTuP4qi1cvFlWre1LGkms4mK8Lwtv 5+nspF1+xu8S8p2oEUbTmvbJKAEcKSKGg85uWeHPHo2dBDmnsV4TIsQcoooqHfvdUWTrUbPx1Jdd8t XfXBwBh7rUNCWFQYM60KB2BSVmDCEwg==
ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.167.174; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=RCM/IbFSlFzoTN8ouzH8/6RHsVxgAwYzKcKbYUsqOv4=; b=gDMmzwA9adSZv3Ro/3GQKc+YBo7W9OOq6ZpX4n5HDqi5m+n7a3FJHjt3wTFp8ENlkE+DHX2jEvpup s6yfzAqrGTrzXQLvBZ2niJLDk3Kr/uLj3rexxtPP3oypJsH/AP56LODdnm5Wj2ElaDEpm5odYIqnRB 9ewapV3bTDrOSW8U=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=RCM/IbFSlFzoTN8ouzH8/6RHsVxgAwYzKcKbYUsqOv4=; b=qyVIDjoc3swSkiHtYJBvbCu9uK6pLTqqoJ86M2HETeXI55BZeBW6urkRns9j95eRF4ORy4t+6tY7D +lClgwPlaCHeaCWmowKV85BzZZQiNTcRZw7ULAOGf4adDuUmYSlp5fQ0ysPTW3fBxdREwEfKzdW+yL OWjHncQktbKCHIAhBT7tsRhbuvNJgQgttOFCZu1P9bwVN9EIj2xXmdGdXZE3A8X/kZUpAmgeafPplI GhPW8ZEXWYvjEqlhPS4o5nydshL1f9yShSngw34rIwZnyBOFSyD536DO8mhNqmbI7YuFsQ1bE2X/ie mR311+fG5FcDJAsVnLyRadEjfak3iwg==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: 279cdcca-8c9a-11e9-85c6-c97e5c048ed3
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.167.174
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-oi1-f174.google.com (unknown [209.85.167.174]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id 279cdcca-8c9a-11e9-85c6-c97e5c048ed3; Tue, 11 Jun 2019 22:42:13 +0000 (UTC)
Received: by mail-oi1-f174.google.com with SMTP id w7so10240915oic.3 for <eligibility-discuss@ietf.org>; Tue, 11 Jun 2019 15:42:13 -0700 (PDT)
X-Gm-Message-State: APjAAAW+yEke4paYU6rF+Rf0uk8q+Hjotw0DVk3ont4ufyHaPbMlwSvb eVP+4LZ9xXqWH7uvxJ7U76rd/I3Ig33/ZyL8g+M=
X-Google-Smtp-Source: APXvYqxLpv3Y06E8A9YdTmSznOXUhfqe1EMuIzChHo630e6HJz9+/0HZ4G7EFr27XXrZMmPJBBqfLic52bbVFEwEBSU=
X-Received: by 2002:aca:c3d7:: with SMTP id t206mr16670421oif.138.1560292932596;  Tue, 11 Jun 2019 15:42:12 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com> <9C18B7DC9C307B3DBD8E76BA@PSB>
In-Reply-To: <9C18B7DC9C307B3DBD8E76BA@PSB>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Tue, 11 Jun 2019 18:42:00 -0400
X-Gmail-Original-Message-ID: <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
Message-ID: <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Eliot Lear <lear@cisco.com>, Patrick McManus <mcmanus@ducksong.com>, eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="000000000000fe3901058b1401f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/ldlKD4AGIa0a-dr0_TMRXnVbHkI>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Tue, 11 Jun 2019 22:42:21 -0000

--000000000000fe3901058b1401f0
Content-Type: text/plain; charset="UTF-8"

Hi Eliot,

The reason I made a comment on this topic is because the amount of
discussion related to recall struck me as embarrassing.

I am reminded of kids in a clubhouse, no doubt bearing a keep out sign,
discussing whether the secretary or treasurer would take over in the wake
of the simultaneous death of the co-presidents (who couldn't agree on who
would be president in the first place). In short - its a process discussion
obsessed with trappings and machinery and meta-talk. It exists only to
serve itself. At least the kids in the clubhouse have nothing better to do.
A BoF is just endorsement that its important, when it is not.

WRT clear and non-controversial cases such as AWOL - there already is a
process that has been prepared in contingency in the past and not needed
yet. That seems fine.

WRT less obvious cases - referring them to a committee is not how one
effectively resolves complicated questions. In the case of a multi
stakeholder organization like ours those questions will inevitably be
tinged with market and political forces - its the nature of the beast.
Keeping terms short creates an accountability loop while also allowing the
office holder space to fulfill their duties day to day. A totally
reasonable situation - half the leadership stands for appointment every
year already.

-P



On Tue, Jun 11, 2019 at 1:18 PM John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, June 11, 2019 18:44 +0200 Eliot Lear
> <lear@cisco.com> wrote:
>
> >
> >
> >> On 11 Jun 2019, at 17:48, Patrick McManus
> >> <mcmanus@ducksong.com> wrote:
> >>
> >> . One is about the sweet spot of recall difficulty - number
> >> of signers, etc... I believe that's an unimportant question -
> >> leadership have short 2 year terms and its not like they
> >> possess nuclear codes.
> >
> >
> > I think this very much depends on your business.  Knowing that
> > the standard can be dinked right up until the IESG, if someone
> > disappears from that process, your feature scheduling goes out
> > the window.  Possibly your release planning as well.  Now some
> > variability has to be allowed for in this process.  Weeks,
> > maybe even small number of months.  Large #s of months or even
> > years is not an acceptable #.
>
> It seem to me that this would apply even more strongly if
> someone on, say, the IESG decided to adopt an obstructionist
> position relative to your ideas, your company, or, noting your
> earlier comment about retaliation, you as an individual.  In
> such situations, the IESG has tools to move ahead in spite of
> that AD, but they have proven in the past to be time-consuming
> and to impede overall progress when the offender is obstinate,
> so trade-offs get made, maybe trade-offs that would be less
> necessary with a more effective recall mechanism.
>
> Personally, I believe that the IETF is in need of a faster and
> lighter-weight mechanism for getting rid of someone who has
> disappeared then relying on the present recall process.
> However, because I've seen little or no evidence that the
> community is ready to deal with a redesign of the recall model,
> or the nomination and selection models more generally, I
> continue to hope that this discussion can be kept focused on the
> particular issues in the petitioning process identified in
> draft-moonesamy-recall-rev
>
> best,
>    john
>
> >
> > And that would encourage people to do work elsewhere.  And so
> > it's harmful to this organization when someone fails to show
> > up for an extended period of time.
> >
> > Eliot
>
>
>
>
>

--000000000000fe3901058b1401f0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Eliot,<div><br></div><div>The reason I made a comment o=
n this topic is because the amount of discussion related to recall struck m=
e as embarrassing.=C2=A0</div><div><br></div><div>I am reminded of kids in =
a clubhouse, no doubt bearing a keep out sign, discussing whether the secre=
tary or treasurer would take over in the wake of the simultaneous death of =
the co-presidents (who couldn&#39;t agree on who would be president in the =
first place). In short - its a process discussion obsessed with trappings a=
nd machinery and meta-talk. It exists only to serve itself. At least the ki=
ds in the clubhouse have nothing better to do. A BoF is just endorsement th=
at its important, when it is not.</div><div><br></div><div>WRT clear and no=
n-controversial cases such as AWOL - there already is a process that has be=
en prepared in contingency in the past and not needed yet. That seems fine.=
</div><div><br></div><div>WRT less obvious cases - referring them to a comm=
ittee is not how one effectively resolves complicated questions. In the cas=
e of a multi stakeholder organization like ours those questions will inevit=
ably be tinged with market and political forces - its the nature of the bea=
st. Keeping terms short creates an accountability loop while also allowing =
the office holder space to fulfill their duties day to day. A totally reaso=
nable situation - half the leadership stands for appointment every year alr=
eady.</div><div><br></div><div>-P</div><div><br></div><div><div><div><div><=
div><div><div><br></div></div></div></div></div></div></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 11,=
 2019 at 1:18 PM John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com" ta=
rget=3D"_blank">john-ietf@jck.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><br>
<br>
--On Tuesday, June 11, 2019 18:44 +0200 Eliot Lear<br>
&lt;<a href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&=
gt; wrote:<br>
<br>
&gt; <br>
&gt; <br>
&gt;&gt; On 11 Jun 2019, at 17:48, Patrick McManus<br>
&gt;&gt; &lt;<a href=3D"mailto:mcmanus@ducksong.com" target=3D"_blank">mcma=
nus@ducksong.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; . One is about the sweet spot of recall difficulty - number<br>
&gt;&gt; of signers, etc... I believe that&#39;s an unimportant question -<=
br>
&gt;&gt; leadership have short 2 year terms and its not like they<br>
&gt;&gt; possess nuclear codes.<br>
&gt; <br>
&gt; <br>
&gt; I think this very much depends on your business.=C2=A0 Knowing that<br=
>
&gt; the standard can be dinked right up until the IESG, if someone<br>
&gt; disappears from that process, your feature scheduling goes out<br>
&gt; the window.=C2=A0 Possibly your release planning as well.=C2=A0 Now so=
me<br>
&gt; variability has to be allowed for in this process.=C2=A0 Weeks,<br>
&gt; maybe even small number of months.=C2=A0 Large #s of months or even<br=
>
&gt; years is not an acceptable #.<br>
<br>
It seem to me that this would apply even more strongly if<br>
someone on, say, the IESG decided to adopt an obstructionist<br>
position relative to your ideas, your company, or, noting your<br>
earlier comment about retaliation, you as an individual.=C2=A0 In<br>
such situations, the IESG has tools to move ahead in spite of<br>
that AD, but they have proven in the past to be time-consuming<br>
and to impede overall progress when the offender is obstinate,<br>
so trade-offs get made, maybe trade-offs that would be less<br>
necessary with a more effective recall mechanism.<br>
<br>
Personally, I believe that the IETF is in need of a faster and<br>
lighter-weight mechanism for getting rid of someone who has<br>
disappeared then relying on the present recall process.<br>
However, because I&#39;ve seen little or no evidence that the<br>
community is ready to deal with a redesign of the recall model,<br>
or the nomination and selection models more generally, I<br>
continue to hope that this discussion can be kept focused on the<br>
particular issues in the petitioning process identified in<br>
draft-moonesamy-recall-rev<br>
<br>
best,<br>
=C2=A0 =C2=A0john<br>
<br>
&gt; <br>
&gt; And that would encourage people to do work elsewhere.=C2=A0 And so<br>
&gt; it&#39;s harmful to this organization when someone fails to show<br>
&gt; up for an extended period of time.<br>
&gt; <br>
&gt; Eliot<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--000000000000fe3901058b1401f0--


From nobody Wed Jun 12 00:39:54 2019
Return-Path: <lear@cisco.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 1DB721200FA for <eligibility-discuss@ietfa.amsl.com>; Wed, 12 Jun 2019 00:39:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 tdBILKKcTfY4 for <eligibility-discuss@ietfa.amsl.com>; Wed, 12 Jun 2019 00:39:50 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EA071200F9 for <eligibility-discuss@ietf.org>; Wed, 12 Jun 2019 00:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13108; q=dns/txt; s=iport; t=1560325189; x=1561534789; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=vQ+Oyr4gkoLEd+1Rj/OX/02WIBGUALVGF6zXaC8XBtU=; b=ZtsN3QWruob4bu9IILKS6v0K7ChyvFv43IgcfU/dLPv9nMXFJZAlpNiS h0osfmvw3IZ0KnRoYMgX0gU3QbnxvJYJsBy/FHOQOKn1t73XeTFeT8JK2 jlirNw3wBVuYmp2IPYH1ywj6Zj4ya3wPuXTcA9wQp1gsnUbDA+bcD8m2n I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BAAABwqwBd/xbLJq1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBZYN/KIQViHuLYiV+kWKHfAIHAQEBCQMBAS8BAYRAAoM?= =?us-ascii?q?kOBMBAwEBBAEBAgEEbSiFSgEBAQECASNWBQsLGCcDAgJGEQYTFIMOAYF7D6h?= =?us-ascii?q?JgTGFR4ReEIE0gVCJfiaBf4ERJwwTgU5JNT6HTjKCJgSLRYhRlSoJghKCG4E?= =?us-ascii?q?GhzyGPIIxFAeCJYcBjgCgVoMIAgQGBQIVgWYhgVgzGggbFWUBgkE+gV0XjiI?= =?us-ascii?q?9AzCQEwEB?=
X-IronPort-AV: E=Sophos;i="5.63,363,1557187200";  d="asc'?scan'208,217";a="13068280"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Jun 2019 07:39:47 +0000
Received: from ams3-vpn-dhcp2414.cisco.com (ams3-vpn-dhcp2414.cisco.com [10.61.73.110]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x5C7dkUY017601 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 12 Jun 2019 07:39:46 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <E33325A0-2961-4C46-B387-10F17F927E78@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_CF4C6296-602B-4772-B6D4-C2C564E1D2D9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 12 Jun 2019 09:39:45 +0200
In-Reply-To: <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
Cc: John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>
To: Patrick McManus <mcmanus@ducksong.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com> <9C18B7DC9C307B3DBD8E76BA@PSB> <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.73.110, ams3-vpn-dhcp2414.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/uGYFENICh1lWEvOUYaUB8GR9RxI>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Wed, 12 Jun 2019 07:39:52 -0000

--Apple-Mail=_CF4C6296-602B-4772-B6D4-C2C564E1D2D9
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FD18C4DE-3333-4102-B84C-4D22C255EACF"


--Apple-Mail=_FD18C4DE-3333-4102-B84C-4D22C255EACF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Patrick,

I=E2=80=99ll respond since you addressed this to me, but you replied to =
John=E2=80=99s message.  I cannot tell if you are saying that there =
isn=E2=80=99t a problem to be solved or whether you are arguing over its =
scope.  If you are saying that we have a process that deals with AWOL =
people, it clearly hasn=E2=80=99t functioned properly in the past.  If =
you are saying that you are okay dealing with the AWOL problem, but =
would prefer not expanding to address the more general case, ok.  But =
your analogy is not appropriate.  Please allow for the possibility that =
there are those of us have been materially impacted, and who have seen =
the impact on this organization.  Perhaps you don=E2=80=99t see it =
because it hasn=E2=80=99t hit the area in which you work.

Eliot


> On 12 Jun 2019, at 00:42, Patrick McManus <mcmanus@ducksong.com> =
wrote:
>=20
> Hi Eliot,
>=20
> The reason I made a comment on this topic is because the amount of =
discussion related to recall struck me as embarrassing.
>=20
> I am reminded of kids in a clubhouse, no doubt bearing a keep out =
sign, discussing whether the secretary or treasurer would take over in =
the wake of the simultaneous death of the co-presidents (who couldn't =
agree on who would be president in the first place). In short - its a =
process discussion obsessed with trappings and machinery and meta-talk. =
It exists only to serve itself. At least the kids in the clubhouse have =
nothing better to do. A BoF is just endorsement that its important, when =
it is not.
>=20
> WRT clear and non-controversial cases such as AWOL - there already is =
a process that has been prepared in contingency in the past and not =
needed yet. That seems fine.
>=20
> WRT less obvious cases - referring them to a committee is not how one =
effectively resolves complicated questions. In the case of a multi =
stakeholder organization like ours those questions will inevitably be =
tinged with market and political forces - its the nature of the beast. =
Keeping terms short creates an accountability loop while also allowing =
the office holder space to fulfill their duties day to day. A totally =
reasonable situation - half the leadership stands for appointment every =
year already.
>=20
> -P
>=20
>=20
>=20
> On Tue, Jun 11, 2019 at 1:18 PM John C Klensin <john-ietf@jck.com =
<mailto:john-ietf@jck.com>> wrote:
>=20
>=20
> --On Tuesday, June 11, 2019 18:44 +0200 Eliot Lear
> <lear@cisco.com <mailto:lear@cisco.com>> wrote:
>=20
> >
> >
> >> On 11 Jun 2019, at 17:48, Patrick McManus
> >> <mcmanus@ducksong.com <mailto:mcmanus@ducksong.com>> wrote:
> >>
> >> . One is about the sweet spot of recall difficulty - number
> >> of signers, etc... I believe that's an unimportant question -
> >> leadership have short 2 year terms and its not like they
> >> possess nuclear codes.
> >
> >
> > I think this very much depends on your business.  Knowing that
> > the standard can be dinked right up until the IESG, if someone
> > disappears from that process, your feature scheduling goes out
> > the window.  Possibly your release planning as well.  Now some
> > variability has to be allowed for in this process.  Weeks,
> > maybe even small number of months.  Large #s of months or even
> > years is not an acceptable #.
>=20
> It seem to me that this would apply even more strongly if
> someone on, say, the IESG decided to adopt an obstructionist
> position relative to your ideas, your company, or, noting your
> earlier comment about retaliation, you as an individual.  In
> such situations, the IESG has tools to move ahead in spite of
> that AD, but they have proven in the past to be time-consuming
> and to impede overall progress when the offender is obstinate,
> so trade-offs get made, maybe trade-offs that would be less
> necessary with a more effective recall mechanism.
>=20
> Personally, I believe that the IETF is in need of a faster and
> lighter-weight mechanism for getting rid of someone who has
> disappeared then relying on the present recall process.
> However, because I've seen little or no evidence that the
> community is ready to deal with a redesign of the recall model,
> or the nomination and selection models more generally, I
> continue to hope that this discussion can be kept focused on the
> particular issues in the petitioning process identified in
> draft-moonesamy-recall-rev
>=20
> best,
>    john
>=20
> >
> > And that would encourage people to do work elsewhere.  And so
> > it's harmful to this organization when someone fails to show
> > up for an extended period of time.
> >
> > Eliot
>=20
>=20
>=20
>=20


--Apple-Mail=_FD18C4DE-3333-4102-B84C-4D22C255EACF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Patrick,<div class=3D""><br class=3D""></div><div =
class=3D"">I=E2=80=99ll respond since you addressed this to me, but you =
replied to John=E2=80=99s message. &nbsp;I cannot tell if you are saying =
that there isn=E2=80=99t a problem to be solved or whether you are =
arguing over its scope. &nbsp;If you are saying that we have a process =
that deals with AWOL people, it clearly hasn=E2=80=99t functioned =
properly in the past. &nbsp;If you are saying that you are okay dealing =
with the AWOL problem, but would prefer not expanding to address the =
more general case, ok. &nbsp;But your analogy is not appropriate. =
&nbsp;Please allow for the possibility that there are those of us have =
been materially impacted, and who have seen the impact on this =
organization. &nbsp;Perhaps you don=E2=80=99t see it because it hasn=E2=80=
=99t hit the area in which you work. &nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Eliot</div><div class=3D""><br =
class=3D""><div class=3D""><br class=3D""></div><div =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
12 Jun 2019, at 00:42, Patrick McManus &lt;<a =
href=3D"mailto:mcmanus@ducksong.com" =
class=3D"">mcmanus@ducksong.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"ltr" class=3D"">Hi Eliot,<div class=3D""><br =
class=3D""></div><div class=3D"">The reason I made a comment on this =
topic is because the amount of discussion related to recall struck me as =
embarrassing.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">I am reminded of kids in a clubhouse, no doubt bearing a keep =
out sign, discussing whether the secretary or treasurer would take over =
in the wake of the simultaneous death of the co-presidents (who couldn't =
agree on who would be president in the first place). In short - its a =
process discussion obsessed with trappings and machinery and meta-talk. =
It exists only to serve itself. At least the kids in the clubhouse have =
nothing better to do. A BoF is just endorsement that its important, when =
it is not.</div><div class=3D""><br class=3D""></div><div class=3D"">WRT =
clear and non-controversial cases such as AWOL - there already is a =
process that has been prepared in contingency in the past and not needed =
yet. That seems fine.</div><div class=3D""><br class=3D""></div><div =
class=3D"">WRT less obvious cases - referring them to a committee is not =
how one effectively resolves complicated questions. In the case of a =
multi stakeholder organization like ours those questions will inevitably =
be tinged with market and political forces - its the nature of the =
beast. Keeping terms short creates an accountability loop while also =
allowing the office holder space to fulfill their duties day to day. A =
totally reasonable situation - half the leadership stands for =
appointment every year already.</div><div class=3D""><br =
class=3D""></div><div class=3D"">-P</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D""><div class=3D""><div class=3D""><br =
class=3D""></div></div></div></div></div></div></div></div><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Tue, Jun 11, 2019 at 1:18 PM John C Klensin =
&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank" =
class=3D"">john-ietf@jck.com</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><br class=3D"">
<br class=3D"">
--On Tuesday, June 11, 2019 18:44 +0200 Eliot Lear<br class=3D"">
&lt;<a href=3D"mailto:lear@cisco.com" target=3D"_blank" =
class=3D"">lear@cisco.com</a>&gt; wrote:<br class=3D"">
<br class=3D"">
&gt; <br class=3D"">
&gt; <br class=3D"">
&gt;&gt; On 11 Jun 2019, at 17:48, Patrick McManus<br class=3D"">
&gt;&gt; &lt;<a href=3D"mailto:mcmanus@ducksong.com" target=3D"_blank" =
class=3D"">mcmanus@ducksong.com</a>&gt; wrote:<br class=3D"">
&gt;&gt; <br class=3D"">
&gt;&gt; . One is about the sweet spot of recall difficulty - number<br =
class=3D"">
&gt;&gt; of signers, etc... I believe that's an unimportant question =
-<br class=3D"">
&gt;&gt; leadership have short 2 year terms and its not like they<br =
class=3D"">
&gt;&gt; possess nuclear codes.<br class=3D"">
&gt; <br class=3D"">
&gt; <br class=3D"">
&gt; I think this very much depends on your business.&nbsp; Knowing =
that<br class=3D"">
&gt; the standard can be dinked right up until the IESG, if someone<br =
class=3D"">
&gt; disappears from that process, your feature scheduling goes out<br =
class=3D"">
&gt; the window.&nbsp; Possibly your release planning as well.&nbsp; Now =
some<br class=3D"">
&gt; variability has to be allowed for in this process.&nbsp; Weeks,<br =
class=3D"">
&gt; maybe even small number of months.&nbsp; Large #s of months or =
even<br class=3D"">
&gt; years is not an acceptable #.<br class=3D"">
<br class=3D"">
It seem to me that this would apply even more strongly if<br class=3D"">
someone on, say, the IESG decided to adopt an obstructionist<br =
class=3D"">
position relative to your ideas, your company, or, noting your<br =
class=3D"">
earlier comment about retaliation, you as an individual.&nbsp; In<br =
class=3D"">
such situations, the IESG has tools to move ahead in spite of<br =
class=3D"">
that AD, but they have proven in the past to be time-consuming<br =
class=3D"">
and to impede overall progress when the offender is obstinate,<br =
class=3D"">
so trade-offs get made, maybe trade-offs that would be less<br class=3D"">=

necessary with a more effective recall mechanism.<br class=3D"">
<br class=3D"">
Personally, I believe that the IETF is in need of a faster and<br =
class=3D"">
lighter-weight mechanism for getting rid of someone who has<br class=3D"">=

disappeared then relying on the present recall process.<br class=3D"">
However, because I've seen little or no evidence that the<br class=3D"">
community is ready to deal with a redesign of the recall model,<br =
class=3D"">
or the nomination and selection models more generally, I<br class=3D"">
continue to hope that this discussion can be kept focused on the<br =
class=3D"">
particular issues in the petitioning process identified in<br class=3D"">
draft-moonesamy-recall-rev<br class=3D"">
<br class=3D"">
best,<br class=3D"">
&nbsp; &nbsp;john<br class=3D"">
<br class=3D"">
&gt; <br class=3D"">
&gt; And that would encourage people to do work elsewhere.&nbsp; And =
so<br class=3D"">
&gt; it's harmful to this organization when someone fails to show<br =
class=3D"">
&gt; up for an extended period of time.<br class=3D"">
&gt; <br class=3D"">
&gt; Eliot<br class=3D"">
<br class=3D"">
<br class=3D"">
<br class=3D"">
<br class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></div></div></body></html>=

--Apple-Mail=_FD18C4DE-3333-4102-B84C-4D22C255EACF--

--Apple-Mail=_CF4C6296-602B-4772-B6D4-C2C564E1D2D9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTgo4LlIIJ5lIBumWpugA9nE248uAUCXQCsQQAKCRBugA9nE248
uL8hAJ0f30wKBh8Z7PTK1XSWasB4KvGgwACeNP0rEpblcaxMnluo2/eEv85MSF0=
=ZF3H
-----END PGP SIGNATURE-----

--Apple-Mail=_CF4C6296-602B-4772-B6D4-C2C564E1D2D9--


From nobody Wed Jun 12 01:28:04 2019
Return-Path: <john-ietf@jck.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 09022120074 for <eligibility-discuss@ietfa.amsl.com>; Wed, 12 Jun 2019 01:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 dtsEsAem00Z3 for <eligibility-discuss@ietfa.amsl.com>; Wed, 12 Jun 2019 01:28:01 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 242C812003F for <eligibility-discuss@ietf.org>; Wed, 12 Jun 2019 01:28:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1haybt-000H6O-TD; Wed, 12 Jun 2019 04:27:57 -0400
Date: Wed, 12 Jun 2019 04:27:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Patrick McManus <mcmanus@ducksong.com>
cc: Eliot Lear <lear@cisco.com>, eligibility-discuss@ietf.org, Warren Kumari <warren@kumari.net>
Message-ID: <6EFD05B270A85EFE83B3AD5E@PSB>
In-Reply-To: <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
References: <6.2.5.6.2.20190525144314.0e72bb68@elandnews.com> <6.2.5.6.2.20190601204707.0bf89070@elandnews.com> <D58B591C-9140-4273-AA11-59E2EBD101FE@gmail.com> <6.2.5.6.2.20190611033500.0c619e48@elandnews.com> <065101d52047$d35ea620$7a1bf260$@olddog.co.uk> <CABcZeBOX3PURx57jE1poyBt-VxdbVbcFp-E+eocPMH6fsBq6qw@mail.gmail.com> <1AE7F6A0-F278-42A5-9E55-4DA94A38CB01@cisco.com> <CABcZeBMbGOA09rRVuq2WK6SJ-pK8hAjxgMz5EaBm5-h9RGLk3g@mail.gmail.com> <066801d52053$650ea290$2f2be7b0$@olddog.co.uk> <CABcZeBMzca2JGBMtuURnHp4UomSbkwmLUmaW2OEeMTZF-Wfw3w@mail.gmail.com> <4FF5A2A6-FC52-4C90-9E25-A4A5FDEA4CFA@cisco.com> <9C18B7DC9C307B3DBD8E76BA@PSB> <CAOdDvNrRxibAr4CoidUhSXKuMAOLT+qFQDC81g+nqjnPxeyMZg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/0o8UUWXLdUIjDVmyUmNjG5oy2N0>
Subject: Re: [Eligibility-discuss] Virtual BoF for 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: Wed, 12 Jun 2019 08:28:03 -0000

--On Tuesday, June 11, 2019 18:42 -0400 Patrick McManus
<mcmanus@ducksong.com> wrote:

> Hi Eliot,
> 
> The reason I made a comment on this topic is because the
> amount of discussion related to recall struck me as
> embarrassing.

It strikes me as embarrassing too, but for a rather different
reason.

> I am reminded of kids in a clubhouse, no doubt bearing a keep
> out sign, discussing whether the secretary or treasurer would
> take over in the wake of the simultaneous death of the
> co-presidents (who couldn't agree on who would be president in
> the first place). In short - its a process discussion obsessed
> with trappings and machinery and meta-talk. It exists only to
> serve itself. At least the kids in the clubhouse have nothing
> better to do. A BoF is just endorsement that its important,
> when it is not.

Please remember that draft-moonesamy-recall-rev was proposed as
a very small set of patches to address perceived process
unfairness to a collection of IETF participants who, as the IETF
evolves, is growing more numerous and perhaps even more
important.  I was responsible for adding a decade-old loose end
to the patch list because it would be convenient.  That was
probably a mistake.   The authors thought that these patches
were sufficiently minor and focused that they could easily be
handled by going directly to IETF Last Call or, at worst, to a
very focused and short-lived WG.  Far more significant process
changes in this particular area were handled that way.  For
better or worse, had that occurred, we wouldn't be trying to
negotiate the terms of a BOF, we would not be intertwining
discussions of those patches with discussions of the
appropriateness of recalls and alternate models, etc.: exactly
the type of process discussion you are complaining about.  But
the IESG decided it wanted to open the door to broader
discussions and iterations on problem statements, so here we
are.  The usual refrain at this point is "if you don't like it,
tell it to the Nomcom".

> WRT clear and non-controversial cases such as AWOL - there
> already is a process that has been prepared in contingency in
> the past and not needed yet. That seems fine.

Actually, I'm not sure I know what you are talking about.  I was
active in POISED and even chaired one of its successor WGs.  I
don't even remember a discussion of recall as a mechanism for
dealing with what I think you are referring to as "AWOL".   If
it had been discussed, I'd like to believe we would have done
much better because the recall procedure is far too expensive
and time-consuming to deal with a person who has left but not
formally resigned.  For that situation, we shouldn't need much
more than a formal way of confirming the disappearance and
resigning for them, i.e., a way to define and fill a vacancy
without a formal resignation from the person.  Collecting
signatures, appointing a recall committee chair, going through
the process of getting volunteers for and selecting a recall
committee, and then having that committee say "yep, he or she
has disappeared" is almost certainly a far larger waste of time
than what you are complaining about in this discussion.  So to
claim that there is a process prepared for that case and
suggesting it is fine is, umm, strange to me.

That said, it seems to me that you are doing what you are
complaining about by introducing an issue that was not on the
table and expanding the scope of the discussion well beyond the
narrow focus of  the I-D and the discussion around it.  To me,
"trappings and machinery and meta-talk" pretty well cover that
situation.  YMMD, but, if so, I'd like to understand how and why.

> WRT less obvious cases - referring them to a committee is not
> how one effectively resolves complicated questions. In the
> case of a multi stakeholder organization like ours those
> questions will inevitably be tinged with market and political
> forces - its the nature of the beast. Keeping terms short
> creates an accountability loop while also allowing the office
> holder space to fulfill their duties day to day. A totally
> reasonable situation - half the leadership stands for
> appointment every year already.

And, again, those of us who want to keep the discussion narrowly
focused don't consider the less obvious cases or complicated
questions to be in scope.  From that point of view, the above is
either a distraction or a no-op.  On the other hand, I agree
with Eliot: your assumption that there is no leadership
performance or non-performance problem so severe that it cannot
wait a year or two without causing harm is inconsistent with my
experience as well.  It is also incorrect unless we have
concluded that things have changed and that old notions of
"Internet time" as moving very quickly are no longer applicable.

best,
    john





