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

Barry Leiba <barryleiba@computer.org> Mon, 08 April 2019 19:18 UTC

Return-Path: <barryleiba@gmail.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 E320E1203E0; Mon, 8 Apr 2019 12:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no 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 oBcU6n5EYnlL; Mon, 8 Apr 2019 12:18:25 -0700 (PDT)
Received: from mail-it1-f180.google.com (mail-it1-f180.google.com [209.85.166.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DB8012032F; Mon, 8 Apr 2019 12:18:25 -0700 (PDT)
Received: by mail-it1-f180.google.com with SMTP id a190so962691ite.4; Mon, 08 Apr 2019 12:18:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ODWgv57XN5BalEiaHgZN0s5Oyo4NXrDuNYbJhsdiXxQ=; b=rkG6XwadqvM71MwUzCHXl9SlrxrAsLAJGrG8+LyvheVOtF3qaxlulqJ/TNNviAcRyW GGD2k6HNhUHJNIQee93658yb7wno3Qdfs/KZ0tMGZbIg7qyTsCe4oIaiZ17QM2NggH48 HV0XZ3EDxlOktQMYIgTsgUTPCdscLxlDQgYf1nEogqtx79mQNtijn0iDROFukm7kCdDh PTiU7zmZ2uc1HEDncO06h+OkLofSfbKIqRK5hAH7gGC+/WhunbfGhMOGzs9Myk3FqUa2 5nlLoeX8v5VVmYMxkDLVW4jDOkwDiRtAF7KtvAe2uoEIhhR1IJF3GDkPXQyrZu8btbY1 9S+A==
X-Gm-Message-State: APjAAAUEJjPPMn3MzROw3GXFy/1dL0z/+HCeIB6lwhMmL7T4Dc++/cnX PD2YMxNSVxVpHt1lY8CLYJ9cDYt4P6hx0IfVauA=
X-Google-Smtp-Source: APXvYqyqzgps19YC/D/dwL45itiwOfcPKzuTxwOsrzoT+enb+hrnsXc/pTNfdqhj2aRUPmgnTqrrASRoc/oQOGdPld0=
X-Received: by 2002:a24:3d94:: with SMTP id n142mr20404830itn.147.1554751103951; Mon, 08 Apr 2019 12:18:23 -0700 (PDT)
MIME-Version: 1.0
References: <155470226964.18209.2289908384768506570.idtracker@ietfa.amsl.com> <CA+9kkMB40Op1igA4emnkB=XWdj7ZzuUrK_5nTWBnW928FVW9pg@mail.gmail.com> <0B892B67-6402-4898-A041-C232CA4A2E35@vigilsec.com> <CA+9kkMBNVEFZQWO8c8g2AARZ7xidZLYGF1BhJnXvULkzrPBkSA@mail.gmail.com>
In-Reply-To: <CA+9kkMBNVEFZQWO8c8g2AARZ7xidZLYGF1BhJnXvULkzrPBkSA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 8 Apr 2019 15:18:12 -0400
Message-ID: <CALaySJKtQbFRQfv4ZfypeJe9hS++iVQNCvdMOgA08eBVE+=ehg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Russ Housley <housley@vigilsec.com>, Jon Peterson <jon.peterson@neustar.biz>, IASA 2 WG <iasa20@ietf.org>, iasa2-chairs@ietf.org, IESG <iesg@ietf.org>, draft-ietf-iasa2-rfc4071bis@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/7Xq8Q2snLQ5KBtAFafIjC8y5cf0>
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: Mon, 08 Apr 2019 19:18:27 -0000

Lots of other discussion, but let's focus on the meat of it:

> I believe Barry's DISCUSS was "was this choice made deliberately?" and the answer to
> that is clear: yes.  We could take this as a signal to re-litigate it, but that is not the point
> of the IESG review and would not be an appropriate reaction to this DISCUSS.

Quite.  Yes, what makes this a DISCUSS is that I want to have a
discussion about whether the working group considered the issues.
You're quite correct that simply relitigating it would be
inappropriate.

What you're missing, perhaps, is that I'm not asking if the working
group really discussed the desired term; I'm quite sure they did.  I'm
asking if they properly considered the consequences of that decision
on the IESG's ability to practically select someone other than the
IETF Chair.

First, while it's been mentioned in the discussion that we could have
a non-AD in that position, I'll remind everyone that the document
explicitly says "exceptionally".  We don't know exactly what that
means, but I interpret it as an admonishment not to make it a routine
thing.

In practical terms, that means that half the ADs are at best
questionably eligible and, depending upon interpretation, not
practically eligible at all.  And they never will be, because they'll
always be "off cycle".  This really pushed the IESG to appoint someone
who has the same AD cycle as the IETF Chair, and to rule out the other
seven.  Was this considered?

But suppose we should choose to appoint a first-term AD in the middle
of her term, figuring that she'll likely get a second term and that we
can invoke "exceptionally" if she doesn't.  Might that affect NomCom's
decision next year?  Did anyone think about that effect?

Suppose someone wanted to stand for an AD position and specifically
hoped to get the IESG's LLC appointment.  Perhaps she would choose NOT
to stand next year because it will be off cycle and she'd be unlikely
to get the appointment.  That has an effect on who puts their names in
for AD positions.  Did the working group discuss that?

It doesn't take too long to come up with a number of situations that
the two-year term for the IESG appointment raises, if the IESG decides
to appoint someone other than the chair... and, again, I think it's
*very* important that we have the ability to assign tasks such as this
to other than the IETF Chair, so I think that part of the working
group's decision was well founded.

As to Alissa's point about running a selection process, I'll note that
the IESG itself can control that by explicitly appointing someone for
two years -- essentially giving two one-year terms in the appointment.
But that lets us control it.

I appreciate that changing board members too often is bad.  I do not
think that having one board member *potentially* change every year is
not that bad -- and language can be there encouraging continuity and
discouraging frequent replacement for no good reason.  And I think the
benefits to opening up the IESG's choice outweighs the down side.

But what I'm aiming at in the discussion is whether the working group
considered that explicitly: were the issues that this raises for the
IESG's decision process and practical ability to fill the position
adequately considered and discussed.  I'm not sure they were.

Barry

On Mon, Apr 8, 2019 at 1:02 PM Ted Hardie <ted.ietf@gmail.com> wrote:
>
> On Mon, Apr 8, 2019 at 9:51 AM Russ Housley <housley@vigilsec.com> wrote:
>>
>>
>>
>> Speaking personally, I believe consideration to this point was given.  See the threads leading up to Jason's message with the title "Consensus on Director Sources and Number"  August 1, 2018.
>>
>>
>> I agree that this was discussed, but I can see that a one-year term for the IESG appointment would work better with the way that the IESG assigns various people to jobs.  That gets revisited every March.  So, if we really want the IESG to be able to pick someone other than the IETF Chair, the one-year term does seem to be a better fit.
>>
> But shifting that often would be terrible for the Board.  As it stands, there's a lot of context in all of this and that amount of transition is just bad for forward progress.  Since this appointee has to act on behalf of the whole organization (as all board members do), having them have less context than the other members is already bad; shifting to one year would make it potentially much worse.  I think that would make this much closer to a liaison role, with all the issues that entails.
>
> I believe Barry's DISCUSS was "was this choice made deliberately?" and the answer to that is clear: yes.  We could take this as a signal to re-litigate it, but that is not the point of the IESG review and would not be an appropriate reaction to this DISCUSS.  That would, in fact, shift it over the line in the DISCUSS criteria document to DISCUSS non-criteria:
>
> Disagreement with informed WG decisions that do not exhibit problems outlined in Section 3.1 (DISCUSS Criteria). In other words, disagreement in preferences among technically sound approaches.
>
> regards,
>
> Ted
>
>