Re: [Eligibility-discuss] Virtual BoF for draft-moonesamy-recall-rev

Suresh Krishnan <Suresh@kaloom.com> Tue, 04 June 2019 03:27 UTC

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, 04 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:
> 
> I probably can't speak to the cases you describe.
> 
> 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 cosignatories was slow, but for good reasons. People generally said "Yes, bad stuff is happening, but recall is pretty serious. Can we think about other ways of handling this?". And, indeed, once the seriousness got discussed a bit, the AD concerned modified their behaviour (coincidence is not causation).
> 
> The process did not seem unwieldy to me, but making it more wieldy (for example by reducing the number of signatures needed) does not seem to be a bad idea to me. In fact, it is part of SM's draft, IIRC. 

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

> 
> However, adding a new process that allows removal of a community appointment by other than the community looks like a way of just increasing the chances 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 independent of SM's proposals.

Agree.

Thanks
Suresh