Re: AD Sponsorship of draft-moonesamy-recall-rev

S Moonesamy <sm+ietf@elandsys.com> Sat, 27 April 2019 19:30 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF044120182 for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2019 12:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1] 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=4HjqD4Y5; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=yztghtcQ
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 pbXZoVCBbSsa for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2019 12:30: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 687C2120174 for <ietf@ietf.org>; Sat, 27 Apr 2019 12:30:40 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.55.228]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x3RJUFqU004887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Apr 2019 12:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1556393429; x=1556479829; bh=FI4i+trD3RmeQN4JDhOOKWRbVcHTIWRh8hSlTyv/bEg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4HjqD4Y5AJ+GC+lBiyeKshl6UhBzSnkXRbwiGhCF+PTh6JI7bWSDi5Ry0jzDmxlWB Zv+15vLHk85C8GR9kkCUrRbcbjXSm6Z4tvY7/SOuoe4OlJkR7xfgJ9N1u+CrMTTBLK xM882jnZF6aL1TU6eX3memBzeFfF2WOJ89+vPLgQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1556393429; x=1556479829; i=@elandsys.com; bh=FI4i+trD3RmeQN4JDhOOKWRbVcHTIWRh8hSlTyv/bEg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yztghtcQyXMg3kYzo4SNaebL3KX7WctB4OlrBB7dQXWV73LbD5qbVRlJu7maOoIIy FNwUl+sXQs0SYtyHeP4TkzVwg5KqQ62ONj7qHZKgVUUgyx8PkLOV1Rs5rfHrQ+ziZc VxTBDPD6nfH8Q6XBDVeMQRea/I2Y3vXhq/eLBiy0=
Message-Id: <6.2.5.6.2.20190427094440.12099d10@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 27 Apr 2019 12:16:45 -0700
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
Cc: Adrian Farrel <adrian@olddog.co.uk>, John C Klensin <john-ietf@jck.com>
In-Reply-To: <20190427155921.i32pftxdbkvv7ist@isoc.org>
References: <6.2.5.6.2.20190424095017.13cdadc8@elandnews.com> <51068F13-E90F-42A2-8AE2-627D5E18B145@akamai.com> <20190424201939.GM3137@localhost> <6.2.5.6.2.20190424134823.0c9faf68@elandnews.com> <20190424211123.GO3137@localhost> <6.2.5.6.2.20190424144539.0cabcde0@elandnews.com> <20190424234334.GQ3137@localhost> <11F97591808485C30AD98A22@PSB> <20190426150436.v4svwa67xja6267r@mx4.yitter.info> <0a1e01d4fc6c$10b93df0$322bb9d0$@olddog.co.uk> <20190427155921.i32pftxdbkvv7ist@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d-CB4ckrshCDijp8ehzbThmRaNw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2019 19:30:42 -0000

Hi Andrew,
At 09:00 AM 27-04-2019, 'Andrew Sullivan' wrote:
>Only sort of.  It allows registered remote participants to count
>(good) but then sets up a rule in which people "have participated
>physically or remotely" without defining that term.  If ever there
>were an opportunity for confusion and arguments over what constitutes
>"participation", I'd like to hope that its first official duty would
>not be in determining how we pick everyone else to manage the
>organization.  The existing arrangement is quite clear: you register
>for and attend the meetings.  The new proposal adds a notion of
>participation that is at least in serious need of unpacking.

The draft does not make any change to the section about the Internet 
Society President.

There is the following sentence in the Note Well: "By participating 
in the IETF, you agree to follow IETF processes and 
policies".  Signatories are "expected to be familiar with the IETF 
processes and procedures, which are readily learned by active 
participation ..."  It is the up to a signatory to show that he or 
she participated in those IETF meetings.

>You might do anything at all, of course, and another person might do
>something else yet again.  The point is that good organizational
>procedures intended to be triggered frequently ought to be well
>understood.  The current draft proposes that 10 random people who sign
>up for free remote participation 3 times and "participate" in some
>unspecified way can hold the entire IETF so-called "leadership" to
>ransom, and we have no idea how those demands would be processed.  It
>seems like the sort of decision that requires careful community
>deliberation.  I don't see that this document has reached that
>threshold.

Please see draft-sullivan-mtgvenue-decisions-00 as it discusses about 
different types of attendees.

 From what I recall, it only took one appointee to negatively impact 
the work of the administrative support activity.  Russ explained why 
it was not possible for the body to exercise the recall process option.

There are 10 random persons who choose the so-called "leadership" 
each year.  The persons  do not have to have to participate on this 
mailing list even though this is usually the place where IETF 
policies are discussed.  What is the difference between them and 10 
random persons who participate remotely?

Is an accountability mechanism a way to hold the so-called 
"leadership" to ransom?

Regards,
S. Moonesamy