Re: [Iasa20] Recall details in rfc7437bis

John C Klensin <john-ietf@jck.com> Wed, 10 April 2019 15:59 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58CC1200E9 for <iasa20@ietfa.amsl.com>; Wed, 10 Apr 2019 08:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 KnC3FJYgUyFE for <iasa20@ietfa.amsl.com>; Wed, 10 Apr 2019 08:58:58 -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 812971203B7 for <iasa20@ietf.org>; Wed, 10 Apr 2019 08:58:58 -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 1hEFcn-0008j0-3G; Wed, 10 Apr 2019 11:58:57 -0400
Date: Wed, 10 Apr 2019 11:58:49 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alissa Cooper <alissa@cooperw.in>
cc: IASA 2 WG <iasa20@ietf.org>
Message-ID: <B107C216A568095BF0E68292@PSB>
In-Reply-To: <83057AC4-F085-4825-9756-8F7CF5E5131B@cooperw.in>
References: <155470226964.18209.2289908384768506570.idtracker@ietfa.amsl.com> <0B892B67-6402-4898-A041-C232CA4A2E35@vigilsec.com> <CA+9kkMBNVEFZQWO8c8g2AARZ7xidZLYGF1BhJnXvULkzrPBkSA@mail.gmail.com> <803F101C-F519-446D-A660-73B9EDE4CB56@vigilsec.com> <CA+9kkMB0Q=n_GSbtZF43iU310tZG3T=y0sXAowD6jYQdRdBd=g@mail.gmail.com> <85d31d43-d98d-ad8a-01f5-a9ada3cf0110@gmail.com> <CALaySJKQPNWYF52HAJar53DoZ_RgyN1oFW3JpABbW9KXrjbyWA@mail.gmail.com> <eec3a909-9e41-243b-1331-cacb1852fac4@gmail.com> <51F9114D-3845-40A5-AC2F-25A3F7B7A428@cooperw.in> <92271d10-1b07-69ce-977e-3c13ba8ebcc9@gmail.com> <E7F2442A29F9A627523ED13E@PSB> <CALaySJJ6eAQhXwOF6edOiHGKgFWfx-uzdVLXZpHFkr-5HeabNQ@mail.gmail.com> <34CDE12B4CE7FD7E7C2D788B@PSB> <83057AC4-F085-4825-9756-8F7CF5E5131B@cooperw.in>
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/iasa20/9xAQTcu5iWJb3r1X6ucqowTli-s>
Subject: Re: [Iasa20] Recall details in rfc7437bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 15:59:05 -0000

Alissa,

Works for me. 
thanks
   john


--On Wednesday, April 10, 2019 11:45 -0400 Alissa Cooper
<alissa@cooperw.in> wrote:

> Changed the subject line and dropped the IESG and others from
> the recipients list since this is about a different WG
> document.
> 
> I commented on the issue in light of this email thread:
> https://github.com/IASA2/RFC-7437-bis/issues/9
> <https://github.com/IASA2/RFC-7437-bis/issues/9>
> 
> Also posting the text here for discussion:
> 
> I thought the WG discussion was clear that recall should not
> apply to the ISOC-appointed director, but should apply to the
> board-appointed directors. This is also reflected in the LLC
> agreement. I haven't re-reviewed the threads though.
> 
> There is actually an additional change that would need to be
> made in 7.1 that I missed before, to make all of this align.
> And text is needed to address John Klensin's point about two
> recall petitions versus one. So something like this could
> capture all of that:
> 
> Member, Trustee, and Director Recall
> The following rules apply to the recall process. If necessary,
> a paragraph discussing the interpretation of each rule is
> included.
> 
> It applies to IESG and IAB Members, the NomCom appointed IETF
> Trust Trustees, and all IETF LLC Directors except the
> ISOC-appointed LLC Director.
> 
> 7.1. Petition
> 
> At any time, a signed petition (email is acceptable) may be
> submitted to the Internet Society President to request the
> recall of any sitting IESG or IAB member, or NomCom appointed
> IETF Trust Trustee, or any IETF LLC Director except the
> ISOC-appointed Director. There are two different types of
> petitions: a petition by participants of the IETF community,
> and a petition by the Ombudsteam as described in [RFC7776].
> 
> A petition to recall an individual who is simultaneously
> serving as both an IETF LLC Director and in another role that
> is eligible for recall may request that the individual be
> recalled from one role or both roles.
> 
> Alissa
> 
>> On Apr 10, 2019, at 9:40 AM, John C Klensin
>> <john-ietf@jck.com> wrote:
>> 
>> Barry,
>> 
>> Agree completely.  While a personally prefer to treat the two
>> positions as separate (and requiring separate removal actions)
>> for the reason you describe, my main concern is only that we
>> reach some agreement and be clear about it.  This is not the
>> sort of thing we can, as John Levine and Bob Hinden suggested
>> for what I assume are other issues, wait until there is a
>> problem and then sort things out ex post facto.
>> 
>> thanks,
>>   john
>> 
>> 
>> --On Wednesday, April 10, 2019 08:50 -0400 Barry Leiba
>> <barryleiba@computer.org> wrote:
>> 
>>>> It also raises the question I've tried to ask before: if an
>>>> IESG member (Chair or otherwise) who is serving as a
>>>> Director resigns or is recalled from the IESG, does that
>>>> action remove that person from the LLC Board position, or
>>>> are the two positions essentially separate?
>>> 
>>> Alissa's proposed text addresses that by making it clear that
>>> regardless of how the IESG appointee is appointed, the person
>>> serves a full term as LLC Director.
>>> 
>>> That does mean that, with a recall situation, there need to
>>> be two recalls done.  Perhaps they could be bundled into one
>>> recall (in the case, for instance, of someone who
>>> disappears). But I think it's good to be able to separate
>>> them, in a case, say, of an AD who is egregiously bad, but
>>> who is doing fine on the LLC Board.
>>> 
>>> Barry
>> 
>> 
>> 
>> 
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
>