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 20:57 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 DBBA8120485 for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 13:57:35 -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=unavailable 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 iUYAZcyW4OMU for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 13:57:34 -0700 (PDT)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (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 B74D012063D for <iasa20@ietf.org>; Tue, 9 Apr 2019 13:57:30 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id y84so14774371oia.12 for <iasa20@ietf.org>; Tue, 09 Apr 2019 13:57:30 -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=40U4Z/oshDA0EM+5t8iiQlW3awxZQ9svDVlVnr/UE0U=; b=hd6SGK6m94sn2z+cq7wFjqvYSOZASeygwaiYQF1Yas9+AExE42zv3dGBKWXPtSYDSB v4FV6SLCiBmwQaMoTLmckJaa1F+b4F6Vt+mtL9If+H+FIy5KUEuT7VEg9Ub+o1Igo05h sIJan+WS53TwbveaKXPdUVJVWapQYoGd7B1sY=
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=40U4Z/oshDA0EM+5t8iiQlW3awxZQ9svDVlVnr/UE0U=; b=uOJwesjmDdbbL+GHAiXJIQAleufMNLIsFIgUty1HkPUcoQ4s9Im9MkpcNEPh9jMvKk RdmY6IPtAK481XAzq5RPtom00qvyvgvEAi7Ko8v4mp3C7tWk1Cv++Rdc8gqTULOJuCAF 8bMkR6rKn5loLITWb5+Ie5nesRz1RVFTautdxwJJ7MhTpH7O2cBviCDsNOBBPN7SMfjh mHIn9L7gpkPp7duRvO58ZF900eMX3o4SwwJa62Us/E71JGLSob5aneNFqwCX2Q/q6Xa8 cDGTpC1FY8R8H+VpjOpJ0KkbmJTm/5MwxkCgPvKtsWCh4smdSq5hWDe2Oj2OB1zXA5px A/Mw==
X-Gm-Message-State: APjAAAUoz8cy9aigxmJ/EczVdnOKA5TZd9UGzlqdizkoAYbmmDUTnmC8 tKx6iLM8QD+lMI5HNu3UyB3oMjAbloyAyVvqe2Owmg==
X-Google-Smtp-Source: APXvYqzWVqGkqtY6WTMF4jUloVqfwnzJJM635J7Y8fVlsbuAqSXk//BJ4Fm35bHFQvV1CZzqWc5eAiSTakr+DZq3Jbc=
X-Received: by 2002:aca:378a:: with SMTP id e132mr201516oia.171.1554843449802; Tue, 09 Apr 2019 13:57:29 -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> <eec3a909-9e41-243b-1331-cacb1852fac4@gmail.com>
In-Reply-To: <eec3a909-9e41-243b-1331-cacb1852fac4@gmail.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Tue, 9 Apr 2019 16:57:18 -0400
Message-ID: <CABtrr-XcuGLMtUqe0HbECBHbdUWkFgywSDZnEFvQc2dRbmVBpg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, Ted Hardie <ted.ietf@gmail.com>, Russ Housley <housley@vigilsec.com>, draft-ietf-iasa2-rfc4071bis@ietf.org, Jon Peterson <jon.peterson@neustar.biz>, IASA 2 WG <iasa20@ietf.org>, iasa2-chairs@ietf.org, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081db0705861f33d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/oOahSEc14KLwj8tJuN4k1zyd8xo>
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 20:57:41 -0000

On Tue, Apr 9, 2019 at 4:52 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 10-Apr-19 01:43, Barry Leiba wrote:
> >>> As Joe noted, they do not have to be members of the IESG at all.  If
> they were appointed
> >>> while on the IESG and then rotated off by NomCom action, they could
> still serve the
> >>> remaining year.  Presumably, the IESG would have to take that into
> account when
> >>> deciding who to select, but it is pretty clearly permitted by the
> document now.
> >>
> >> Agreed. And as somebody else pointed out, the incumbent can always
> resign
> >> if they happen to leave the IESG mid-term; or not, if they are happy to
> >> continue for another year
> >
> > Several comments have said this, but I don't see that it's consistent
> > with the document:
> >
> >    At the IESG's discretion, another
> >    area director may serve instead, or exceptionally the IESG may run a
> >    selection process to appoint a director.
> >
> > First, what this says to me is that in order for the board member to
> > be someone other than an AD, we have to run a selection process.  Just
> > letting someone fall out does not meet that requirement.
> >
> > Second, the selection process is put forth as an exceptional
> > situation.  I don't think that routine appointees not returning to the
> > IESG constitutes an exceptional situation.
> >
> > As I understand that text, it would block the IESG from appointing an
> > AD who is not on the same cycle as the chair, because the IESG would
> > intentionally be stepping into an exceptional condition.
> >
> >> Did the WG analyze every possible ramification? No. But as far as I'm
> >> concerned this was a conscious choice that obtained WG consensus.
> >
> > Of course the WG didn't and couldn't analyze *every* possibility;
> > please don't try to pull my concern into appearing ridiculous.
>
> Sorry, that implication was an unintended side-effect.
>
> What I'm getting at is that we have a method of removing any IESG
> member from the IESG (i.e. a recall) and two methods of removing
> NomCom-appointed LLC Directors (section 6.7 of the draft). But
> I now see that we've failed to define a method of removing the
> IESG-appointed LLC Director if that became appropriate. That does
> seem to need fixing. As long as Directors can be removed, we
> don't need to analyze all possible contingencies.
>
> So how about changing the language to make it clear that the
> IESG can remove as well as appoint their Director?
>
>
Well, the IESG-appointed Director could be removed by the IETF recall
process, no? So we should add another explicit mechanism? Is it as easy as
adding the following to 6.1: "The IESG may remove an IESG-appointed
director at their discretion."


> Skipping to later in the thread, I prefer your suggestion #2:
>
> >> 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 agree with your suggestion that there needs to be
> some language to cover mid-term replacement.
>

Barry or someone had some language that was of the gist: "may appoint
someone to fill the remainder of the vacant term" which seems very simple.

(I'm trying to boil this down to edits.)

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