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 13:54 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 A14621202F1 for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 06:54:15 -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 m3Q1lck4ldBN for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 06:54:12 -0700 (PDT)
Received: from mail-oi1-x242.google.com (mail-oi1-x242.google.com [IPv6:2607:f8b0:4864:20::242]) (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 9568D1202EB for <iasa20@ietf.org>; Tue, 9 Apr 2019 06:54:12 -0700 (PDT)
Received: by mail-oi1-x242.google.com with SMTP id v7so13596476oie.8 for <iasa20@ietf.org>; Tue, 09 Apr 2019 06:54:12 -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=qfmpu4P/GrO0W1YCkdxuYGtD0Is8Nji0LtbTmzC4VEw=; b=rim8fq/mjeb1O5eXkYHTwkrUhQBcU3QH+OKITxAPpgG4jhfw1KMPI0tsGecFRPpuee v1NJ/iBjruLug+j7nTW1N9Dw77g4Be38eIvmZtZ0oAkMkhxrkmveOtpiB9a6oLOgQjYg eAZ7B0u588naHBNvYjFGYjSUB9SLzuEGNevxc=
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=qfmpu4P/GrO0W1YCkdxuYGtD0Is8Nji0LtbTmzC4VEw=; b=J7uczZ23kPHkFL7aLt82+fdcEouRiAEdZlVsjLdr3+E1DtInFSlMvw23SQdLLS8fs6 fq+hkShhjk2s0Sg82Baz0wiJRFu0H711ZDVELx05jQxsgmHlGxNJQc2FLjBi879RfsIG mzgfwGNqfTJAFlI3jQpTliPXyNspt1IesCG9NvgZRjfGziJIoM18Lqfnv4aR1eylOCIb qYLBIvXu6kiPfdhb0lg3qe4OWl17N0MmkKLIUIe2zZrARjsM4pRexQ1DXeMFa7GroUjY kJt3VfeoCGbNqNzD/sSIRmri9m8wxVk1JRXvw9CYj9qR4T94YgjSRmX7wxb9woe/wNNc HtYw==
X-Gm-Message-State: APjAAAUcASLFi21ZChKYs8isalQtOSUj4/1vLfo5yarWQ0NBBgm8ZWgy m51V1Y6wMkJWkEDEc66KlcGYBKkfJSkBoQmwtKboGA==
X-Google-Smtp-Source: APXvYqzMt5d9KZFMDqMU5gDRpn1Lw9UjDFh8A+vDkdieVogEJHUkBX/nzy4bRgq3olXkeXGKpkZZxl7yAxwWVL82Wp8=
X-Received: by 2002:aca:da07:: with SMTP id r7mr21023021oig.5.1554818051159; Tue, 09 Apr 2019 06:54:11 -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> <4C7DE24D-A2E5-42AC-9855-8CCF2C3C1B05@kuehlewind.net>
In-Reply-To: <4C7DE24D-A2E5-42AC-9855-8CCF2C3C1B05@kuehlewind.net>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Tue, 9 Apr 2019 09:54:00 -0400
Message-ID: <CABtrr-UC+UeWNPG0i+O-tYrThou5L3UNowqOmFazXvFFF6KZ3A@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 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>, Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="000000000000a1459605861949f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/wa8tuQo1DNwLYB7QiqDODd4m_k4>
X-Mailman-Approved-At: Mon, 15 Apr 2019 05:55:45 -0700
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 13:54:16 -0000

On Tue, Apr 9, 2019 at 7:39 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote:

> Hi Brian, hi Ted, hi all,
>
> Please see one more comment below.
>
> > On 8. Apr 2019, at 22:57, Brian E Carpenter <brian.e.carpenter@gmail.com>
> wrote:
> >
> > On 09-Apr-19 06:15, Ted Hardie wrote:
> >> On Mon, Apr 8, 2019 at 11:01 AM Russ Housley <housley@vigilsec.com
> <mailto:housley@vigilsec.com>> wrote:
> >>
> >>
> >>    Yes, I agree that the length of the term was discussed.  I do no
> recall this aspect being discussed.
> >>
> >>    At least one board seat will change every year.  If the two-year
> term stands, then only half of the IESG can be considered for the seat, and
> that would be the people that have the same IESG term as the IETF Chair.
> The other half cannot be sure that they will still be on the IESG for a
> full two years.
> >>
> >>
> >> 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, including of course communicating with the
> > IESG as needed. If they were a worthy Board member in the first place,
> > where's the problem?
>
> That actually brings me to another question of my comment. Yes, the
> appointee can reign but as far as I understand there is no way for the IESG
> to remove someone. Was that considered. Is that intended. I mean if the
> chair takes the director position, it would be very unlikely or uncommon to
> for the IESG to move that person. However, if someone else is hold this
> position, I can imagine situations that could occur.
>

I think the only way to remove a non-NomCom appointed LLC Board member is
through the IETF recall process noted in Section 6.7. If I recall
correctly, this was because it didn't really make sense for the board to be
able to remove the ISOC-appointed director (as presumably ISOC would just
re-appoint that person). So for the IESG-appointed slot recall would need
to be the mechanism used here. best, Joe

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