IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 29 October 2019 02:37 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 B5BCC120047 for <eligibility-discuss@ietfa.amsl.com>; Mon, 28 Oct 2019 19:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 6R5DnirxolRo for <eligibility-discuss@ietfa.amsl.com>; Mon, 28 Oct 2019 19:37:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B67EC120033 for <eligibility-discuss@ietf.org>; Mon, 28 Oct 2019 19:37:37 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 141563897A; Mon, 28 Oct 2019 22:34:53 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 748DD3BF0; Mon, 28 Oct 2019 22:37:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: S Moonesamy <sm+ietf@elandsys.com>
cc: eligibility-discuss@ietf.org, adrian@olddog.co.uk
In-Reply-To: <6.2.5.6.2.20191028080914.0c04a118@elandnews.com>
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> <01ef01d58b44$18700850$495018f0$@olddog.co.uk> <19846.1572202173@localhost> <6.2.5.6.2.20191027153050.13e594b0@elandnews.com> <28974.1572275232@localhost> <6.2.5.6.2.20191028080914.0c04a118@elandnews.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 28 Oct 2019 22:37:35 -0400
Message-ID: <23771.1572316655@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/QJmXu_D1GLTjCM6OeQJXCXILgLk>
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: Tue, 29 Oct 2019 02:37:40 -0000

S Moonesamy <sm+ietf@elandsys.com> wrote:
    > Hi Michael,
    > At 08:07 AM 28-10-2019, Michael Richardson wrote:
    >> 1) You can participate on Meetecho without registered.
    >> (I guess we agree that they don't count)

    > Please see https://www.ietf.org/how/meetings/104/remote/  Meetecho requires
    > registration.

I can observe without registration.
I can ask questions on jabber without registration.
(I can do this by mistake, and wind up on not the list, or claim that I did)

    >> I would think that the official list would be the one from the secretariat.

    > Yes.

    >> If we are going to do all this work, then let's do it for the selection
    >> commitee too.

    > Someone will have to submit a proposal if he/she would like to identify and
    > address the wider issue(s).

I would be happy to do that, but up until last week I didn't know what the
problem statement was, so I thought we were going to discuss if there was a
path forward.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email