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

Joseph Lorenzo Hall <joe@cdt.org> Tue, 09 April 2019 15:14 UTC

Return-Path: <jhall@cdt.org>
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 32F51120837 for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 08:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 N1oEKAQCoC8u for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 08:14:55 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 6BE3A120773 for <iasa20@ietf.org>; Tue, 9 Apr 2019 08:14:55 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id c16so15898996otn.4 for <iasa20@ietf.org>; Tue, 09 Apr 2019 08:14:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=psBq6HNH7WJIAzkdb72MBO243Nfi7HZS9xjngMzN93E=; b=DdijXokaqTOYU9DbnYZ2dASdhvq0cz6w2vtdZ7I4wuBsREs3opBxTDBOuSiRPvWRH9 Nl9sv3LdNQQHXr34TgbJkA/Hx/1CuH5xgf5sOKbzgT40FkOtCsjUw3Is/d8/2LdC9sW1 bkRrk3j8fI4gAmmezSb7gS98xCrh2fFckgDC0=
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=psBq6HNH7WJIAzkdb72MBO243Nfi7HZS9xjngMzN93E=; b=tYUr20RxhYiUjaFVyXjo3X3tGLiKrRu2bdW5BCYjY61TTo9QPQNl49loihfmZsYx8D K/0Jem5K/YQts1gEortpy/qQNkrftz4Ix+OeDwF2m7aDU/T/WAYnCu444v1kRii/Zgoi YIqKiYK+NutBTDAwp+zY4/BExGl1s4YiZM0apv4n3M/DBkCMXuAUlRbKHYzUjNZWsDjH DV7UaswGa6cKo/KXla1GEsxIZygixxVl12kT5onk2BgLejJXh3sqODwS0YtstPet1JbP xjyTjocPKw5+7tPs/pQlP8dqsi4OUUgjmpEGL1ezmF80NAJqVnZVeFb7V34JPk29JBTq ghtA==
X-Gm-Message-State: APjAAAVaCYup/mQCPkama8R2JgdbEk6BOaQL/s7RTMjBZzyfxtPXo9YE aWNLC2otR4HNtLlEhvanok7KtNOJudMy+E3JwJwelERj
X-Google-Smtp-Source: APXvYqwRodKjlQMGR5QGPpp0lSN8T93t5ZKdSGvs6TdSVLa7ktFF9Rn4riiBIOTgcU2tDBHQyd2mk7b0s+uPRUt2FEs=
X-Received: by 2002:a9d:da9:: with SMTP id 38mr22367911ots.183.1554822894439; Tue, 09 Apr 2019 08:14:54 -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> <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.com> <CALaySJK9LDW7_YbBKp4kBFJoViKOFbx2rAwQ9-p9feL3rrFi+Q@mail.gmail.com>
In-Reply-To: <CALaySJK9LDW7_YbBKp4kBFJoViKOFbx2rAwQ9-p9feL3rrFi+Q@mail.gmail.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Tue, 9 Apr 2019 11:14:43 -0400
Message-ID: <CABtrr-VvCcQ2XxbUj5hQ_g5vdsTMLmdX-SJ+ZbHZ4uUaUhBxJw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, Russ Housley <housley@vigilsec.com>, Jon Peterson <jon.peterson@neustar.biz>, IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ff1c605861a6a50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/aC18YUyud8ymSB0oNCSqh-i2WWs>
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 15:14:59 -0000

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.
>
>
Minor point: I don't think the text says that if an IESG-appointed AD
Director ceases being an AD that anything special is supposed to happen
(like running a selection process). It's about what they are at the time of
appointment, not what they become later in their term.


> 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.
>
>
I definitely prefer 2 here. Curious to see what others think. best, Joe


> 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
>


-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871

Don't miss out! CDT's Tech Prom is April 10, 2019, at The
Anthem. Please join us: https://cdt.org/annual-dinner/