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

John C Klensin <john-ietf@jck.com> Tue, 09 April 2019 16:14 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 677AA1203BF for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 09:14:36 -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 jtB3zn1J10Vy for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 09:14:34 -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 564C5120899 for <iasa20@ietf.org>; Tue, 9 Apr 2019 09:14:25 -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 1hDtOA-0003d2-UJ; Tue, 09 Apr 2019 12:14:22 -0400
Date: Tue, 09 Apr 2019 12:14:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Joseph Lorenzo Hall <joe@cdt.org>
cc: IASA 2 WG <iasa20@ietf.org>
Message-ID: <971E5ACD6A0048FDD0438D45@PSB>
In-Reply-To: <CALaySJK9LDW7_YbBKp4kBFJoViKOFbx2rAwQ9-p9feL3rrFi+Q@mail.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> <CABtrr-U9uk4FVR08ai7roBRReJBNHjj+AgQpVB09o73MBSSDMA@mail.gmail.c om> <CALaySJK9LDW7_YbBKp4kBFJoViKOFbx2rAwQ9-p9feL3rrFi+Q@mail.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/nIwcTRbfHE5g0M6I1c2tCI4W264>
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: Tue, 09 Apr 2019 16:14:37 -0000


--On Tuesday, April 9, 2019 11:06 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>...
> My concern is that the IESG is limited in whom it can choose,
> and it's not clear to me that that was intentional and that
> the working group actually considered these issues.

Like you, I don't believe the WG got nearly as far down into
those issues, certainly not in the form of a discussion with
wide participation.

> As I said in the message you quoted, I don't agree that the
> current text allows the IESG to pick an AD, have that AD leave
> the IESG in a year, and simply have that AD continue as the
> IESG-appointed Director. As I read the text, the IESG would
> have to run a selection process, which might or might not
> result in the same person being selected to continue.
> Further, should that happen then the IESG-appointed position
> would become out of sync with the IETF Chair cycle, and that
> could cause unexpected and undesirable results down the line.
> 
> OK, so let me try to lay out what I think we need to do to
> clear up this situation.  The point is that I want the
> document to be clear about what the choices really are --
> because I don't think it is -- and to be sure the working
> group has consensus on the result -- because I think this is
> too significant a change to be simply editorial.

Agreed.  It also needs to be absolutely clear as to whether the
IESG can pick someone who is not a sitting AD at the time the
choice is made.  I think it does and probably don't care, but it
should be clear one way or the other.  That clarification is
probably not an editorial chance either.

> I suggest the following alternatives (one could come up with
> others, I'm sure):
> 
> 1. Change the term for the IESG-appointed Director to 1 year,
> with language strongly recommending multiple terms for that
> member (likely using the word "exceptional" to describe a
> single one-year term). This would also mean changing the term
> limit for that role to be specified in number of years, rather
> than number of terms.
 
> 2. Make it clear that once the IESG appoints an AD as
> Director, that person will serve her full term (modulo
> resignation, and see below), regardless of whether she remains
> an AD.  It sounds like this is the best way to make everyone
> on this discussion thread happy, but I think we still need to
> go to the working group for consensus on it.
> 
> 3. Move the word "exceptionally" earlier in the sentence, to
> make the selection of anyone other than the IETF Chair
> exceptional.  It would be helpful, should the working group
> choose this, to also add text making it explicitly clear that
> this is meant to be an IETF Chair ex officio position.  I
> gather this is what some on this thread want; it's my personal
> last choice... but in any case, I'd want to see working group
> consensus for the choice.

My personal preference is for 1, then 2, and could happily live
with either.  Because a decision by the IESG about what was
unusual or special enough to be considered an exceptional
circumstance would potentially be subject to an appeal and we
don't need to invite that sort of aggravation, I'd suggest that
we not put any more stress or focus on "exceptionally" than
necessary.
 
> I'll also note that, as we've mentioned, it's possible for a
> Director to resign mid-term, and if we simply appoint another
> AD for a two-year term we might get that position out of sync
> with the IETF Chair cycle. So I think it's important to also
> add text specifying that a mid-term replacement will serve:
> * if the remainder of the term is more than a year, through
> the end of that term, or
> * if the remainder of the term is a year or less, through the
> end of that term plus another term.
> 
> Does this make sense to everyone?

Yes.  However, as I tried to suggest in an earlier note and
somewhat following up on one of Mirja's concerns, if there is
any circumstance in which we could end up with an LLC Board
member who is not a sitting AD, there needs to be a mechanism
for removing that person from the LLC Board, presumably for
malfeasance or non-feasance.  If we have a situation in which
someone resigns, retires, or is retired from the IESG but can
continue to serve out their term on the LLC Board, it is not
clear that even a recall from the AD position would change their
status vis-a-vis the LLC.

So I see that as another issue the document needs to address
that does not now seem to be covered.

   john