Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS and COMMENT)

John C Klensin <john-ietf@jck.com> Wed, 10 April 2019 02:04 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 A83C51201AB; Tue, 9 Apr 2019 19:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 y_oy_oyIPo_h; Tue, 9 Apr 2019 19:04:01 -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 D69581201A9; Tue, 9 Apr 2019 19:04:00 -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 1hE2ai-000638-Sa; Tue, 09 Apr 2019 22:03:56 -0400
Date: Tue, 09 Apr 2019 22:03:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>
cc: draft-ietf-iasa2-rfc4071bis@ietf.org, IASA 2 WG <iasa20@ietf.org>, iasa2-chairs@ietf.org, IESG <iesg@ietf.org>
Message-ID: <E7F2442A29F9A627523ED13E@PSB>
In-Reply-To: <92271d10-1b07-69ce-977e-3c13ba8ebcc9@gmail.com>
References: <155470226964.18209.2289908384768506570.idtracker@ietfa.amsl.com> <CA+9kkMB40Op1igA4emnkB=XWdj7ZzuUrK_5nTWBnW928FVW9pg@mail.gmail.c om> <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>
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/CLLLZE_k6YHK4gs_QBiIArumJos>
Subject: Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS and COMMENT)
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 02:04:03 -0000


--On Wednesday, April 10, 2019 10:23 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> This is not correct. As Joe pointed out, any director can be
>> removed via the IETF recall process.
> 
> I don't think so. Agreed, the draft says:
> 
>>    Directors may also be removed via the
>>    IETF recall process defined in [I-D.ietf-iasa2-rfc7437bis],
>>    Section 7.
> 
> But that Section 7 says:
> 
>>    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 the NomCom appointed IETF LLC
>>    Directors.
> 
> That *does not* include the IESG-appointed LLC Director, even
> if they are an IESG member.
>...

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?

Even if one accepts the "edge case of an edge case" argument in
principle, the observation that we've had an example in which
someone has disappeared and we almost needed to use the recall
procedure to create a vacancy that could then be filled is
probably argument enough for clarifying the answer to that
question.

     john