Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS and COMMENT)
Barry Leiba <barryleiba@computer.org> Tue, 09 April 2019 17:41 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 296C11207F7;
Tue, 9 Apr 2019 10:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 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,
URIBL_BLOCKED=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 mvIaYzp25jbq; Tue, 9 Apr 2019 10:41:16 -0700 (PDT)
Received: from mail-it1-f177.google.com (mail-it1-f177.google.com
[209.85.166.177])
(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 08570120331;
Tue, 9 Apr 2019 10:41:16 -0700 (PDT)
Received: by mail-it1-f177.google.com with SMTP id f22so6351134ita.3;
Tue, 09 Apr 2019 10:41:15 -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;
bh=NpqZmnKIhAf07K5O4zAGrC4fmWCtT4wEYFcQ+TLgLNM=;
b=feonA5tMJV9U8TkWmO7FMDIeigdyKMdUw3RaCpXkvUE0H2UfoE2mfYMqpyrQ9WQ2+j
7eCisCX/BAV87kO9ELeddTN9SLHhXPwhHWhvrfekdEpV59gAWf6i0azRWBtoAxxQMHwg
gntFn/uo6wqKVzJUYetpRaNksPbEszmkZJIFODBMhRzXC4rpuUfPL8UNK2VUxchxTMmc
L59w+Qv1+JRlrrbmY37fV/BSQxDxdYH7U7eZU0NbTaspY8YzVsGzhNdXPz75Y67hE25Y
Bg8CDPNbzBjGHkapvvTirLLCzn7SBj+NzfbC9wMWjE+W8czTfuA0yv30/BwCKLs0ylod
L6XQ==
X-Gm-Message-State: APjAAAXBjpn5N2kVgcSFdPgI7EI4v5RXFYjKReR1T5c3/YyNMVRNK693
RzAZDBUr/w2jRlQAyZMA1nXwW/6nFGx/zSWEDh4=
X-Google-Smtp-Source: APXvYqzaaq+3QKnIccp66DH2DDBpUNz6zC3cNDDCPv1Zq3xeqchUL8Z3lIgS+AkKDSBnzY51j3pwhjJWKsLBki+LPKM=
X-Received: by 2002:a24:4d12:: with SMTP id l18mr23340834itb.66.1554831674890;
Tue, 09 Apr 2019 10:41:14 -0700 (PDT)
MIME-Version: 1.0
References: <20190409160911.4BF602011C7A02@ary.qy>
<65A3927E-EB56-452C-A91D-EB018F93715A@gmail.com>
In-Reply-To: <65A3927E-EB56-452C-A91D-EB018F93715A@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 9 Apr 2019 13:41:03 -0400
Message-ID: <CALaySJKMrr2Oc4ty9ikhJYE9oOS3xM81RvTVrqTD2esgrmSYLw@mail.gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: IASA 2 WG <iasa20@ietf.org>, IESG <iesg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/SOvV3EiELJx6L_Are5VnljuRtqI>
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 17:41:17 -0000
(I'm not sure when nor why the IESG was removed from the distribution list (Bob didn't do it), but I've added it back on; please leave it there.) > Another alternative not discussed is to change so it has to be the IETF Chair. No exceptions. It's correct that we haven't discussed it here, because THAT was certainly discussed and decided in the working group, and relitigating that would be inappropriate. It sounds to me from the discussion here that my option (2) is a fairly minor change and something we can live with and easily confirm working group consensus on. I'm happy to propose text, as I'm the one who started this up; I'm also happy if the editors go off and do it. Barry On Tue, Apr 9, 2019 at 11:06 AM Barry Leiba <barryleiba@computer.org> wrote: > > Hi, Joe. > > >> What I see -- and, so far, no comments have shown otherwise -- is that > >> the term period was well considered, but, in general, the effect that > >> that period has on the ability of the IESG to actually have a > >> meaningful choice in whom we select... was not. It *appears* to me > >> that the alternatives for the IESG were included grudgingly, where at > >> least a few people just wanted it to be the IETF Chair ex officio, and > >> that's it. My issue here is that if we're given a choice it has to be > >> a real choice, not a Hobson's choice. > > > > I still don't get the concern here, Barry, apologies. Is the sole > > concern that if an AD is not on the same cycle as the Chair then the > > IESG may be constrained in picking that person? I don't think that's > > the case; even if that person cycles out of the AD role they can still > > serve as the IESG-appointed member. It would be less of an effective > > liaison with IESG since that person would not be deep in the mix for > > that last year. Do we need to specify that this IESG-appointed LLC > > director must be in cycle with the chair (since the text says this is a > > two-year appointment and having someone not on IESG for their last year > > doesn't seem ideal). > > 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. > > 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. > > 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. > > 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? > > Barry
- [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa… Barry Leiba via Datatracker
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Ted Hardie
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Russ Housley
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Ted Hardie
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Bob Hinden
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Mirja Kuehlewind
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Russ Housley
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Ted Hardie
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John C Klensin
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Alissa Cooper
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John Levine
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Ted Hardie
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Brian E Carpenter
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Mirja Kuehlewind
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Ted Hardie
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John Levine
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John C Klensin
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Bob Hinden
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Alissa Cooper
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Brian E Carpenter
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Alissa Cooper
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Brian E Carpenter
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John C Klensin
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Alissa Cooper
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John C Klensin
- [Iasa20] Recall details in rfc7437bis Alissa Cooper
- Re: [Iasa20] Recall details in rfc7437bis John C Klensin
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Barry Leiba
- Re: [Iasa20] Recall details in rfc7437bis Brian E Carpenter
- Re: [Iasa20] Recall details in rfc7437bis Adrian Farrel
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… John C Klensin
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall
- Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-… Joseph Lorenzo Hall