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

"Andrew G. Malis" <agmalis@gmail.com> Fri, 25 October 2019 14:51 UTC

Return-Path: <agmalis@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 7BF6C120105 for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 07:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, 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 pb-xmY0c7chw for <eligibility-discuss@ietfa.amsl.com>; Fri, 25 Oct 2019 07:51:02 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 19F1B120122 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 07:51:02 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id o25so3620030qtr.5 for <eligibility-discuss@ietf.org>; Fri, 25 Oct 2019 07:51:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TwPsIzKfeN5XQCn1ieYGtTrJgRFJDe+Qyf9gJA6SdNg=; b=gkYkUaorJaITgaz9LKzVknoM6dAbe1/fjbm43NnuIbPi6243ZpP9SdL0q0IB0XpIOl QeIsGFv7nscqJ4qpe/cL+DLJS4QiZx1ylOe/HLvrZOxPDdC/6OBEkGqENb4tUniiPNhH 71KR0jyBDuCbn93PGEhoSpF0TlOXV7rCkJ/8OqTHGyCwRF5nWzBkMgSCUVwvhcNnQlHA 0PDT8jZPJ8kH5cpk0NA3Qvq/WFRBC04D1h10Zc8qpK7/5lgt+/E0DmJD1sMmYIP7nafx 2iF6qIsh0oaUi7FQwWMHy3QbLPz13Rz0+aJ4fIHC13bS0HMOTcMDlCOQ7UKyaUQ3jF9h Xlzg==
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=TwPsIzKfeN5XQCn1ieYGtTrJgRFJDe+Qyf9gJA6SdNg=; b=T2YNNEIO/IoBRfmJLt05gJbUsalUwgvtrQINS8dBe1QnSgYOzkCxQDPdaoMyh8fyqd WJfsftX/SfPnxsX8z5V0s0KVBhPWoM8LICIPnDI34R7+/s3hVHWUo/pjh0hKC1of5QZb 9hVV0zVkHAIQv6f8XvUS3SZHDPEDEyWSleE4iwGGank1HOqCZtoqmBvAIcNQE39lbvxn kpMGY0Jdv1CZO5ac78cDXwferFduqYBUUV9Bpmf4nrlqugiKvdfZoojmUQyF7rCwKtAw BqtGGRdZsCrBu23SOvlF04PXi3/x9zUPjJPLAu01GWRcZX9dQHhrJjU+edNyzLkJnftM ZvXg==
X-Gm-Message-State: APjAAAV1hRRJJo4qjTUEXHKPkL0y107Scyi2GEveo/uQL7SnkxNR+qR4 WT/jNIUdak5Vk/tvg/gZRg5IVA0eyTycZjytknk=
X-Google-Smtp-Source: APXvYqwtPAlj4wHVQ6Gp2nl/1y2vhRjBhMAMdE96fkqbY/BT9ME/On/RKZgyTaRyDCu4o0+7bl8I332UJtlucdKpypQ=
X-Received: by 2002:a0c:ff44:: with SMTP id y4mr3408041qvt.99.1572015061028; Fri, 25 Oct 2019 07:51:01 -0700 (PDT)
MIME-Version: 1.0
References: <00c801d58a9a$53693c60$fa3bb520$@olddog.co.uk> <CB806045-0E5E-4445-A377-7CD547B9DD90@cisco.com> <010a01d58ac1$c0ab2320$42016960$@olddog.co.uk> <dc3bf13f-0178-8e4c-6680-ae3258ac1a9b@gmail.com> <587B859DB99BCB30198AF5AE@PSB> <17311.1572013829@localhost>
In-Reply-To: <17311.1572013829@localhost>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 25 Oct 2019 10:50:50 -0400
Message-ID: <CAA=duU2L-qA2_y9x5MveJN93U+XRML5YpLMeq6RZ5nMW7vzA_A@mail.gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Eliot Lear <lear@cisco.com>, eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004b589d0595bd47a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/kqS9uSY7-2dcTHKcXTqLLPIpZXk>
Subject: Re: [Eligibility-discuss] Handling the fear of "bogus" recall petitions
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 14:51:05 -0000

I fully agree with Michael that fully enfranchising all active IETF
participants, whether or not they're able to physically attend IETF
meetings, is the right goal, and SM's draft is a good step in this
direction.

Perhaps having registered for the past n of x IETF meetings, for your
favorite values of n and x, is a reasonable way to discern an active IETF
participant. An additional requirement could be, for remote registrations,
actually having logged into Meetecho at least once during a meeting as
proof of participation.

That would require anyone planning a "DOS attack" on the system via bogus
registrations needing to do quite a bit of advance work.

Cheers,
Andy


On Fri, Oct 25, 2019 at 10:30 AM Michael Richardson <mcr@sandelman.ca>
wrote:

>
> John C Klensin <john-ietf@jck.com> wrote:
>     > Brian, keep in mind that we are talking about petitioners here,
>     > not the recall committee.
>
> Tweaking the list for petitions for a process that effectively never gets
> used is boring.  It's not worth the RFC.
>
> If we are going to do something, let's find a way to enfrachise (fully)
> people in category (b).
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT
> architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
> --
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>