IETF Logo Mail Archive

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

Mirja Kuehlewind <ietf@kuehlewind.net> Tue, 09 April 2019 11:39 UTC

Return-Path: <ietf@kuehlewind.net>
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 264881202E2; Tue, 9 Apr 2019 04:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham 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 VyhwGym2kA6M; Tue, 9 Apr 2019 04:39:46 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 A74EC120058; Tue, 9 Apr 2019 04:39:46 -0700 (PDT)
Received: from sessfw99-sesbfw99-93.ericsson.net ([192.176.1.93] helo=[10.148.125.253]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1hDp62-00069t-Do; Tue, 09 Apr 2019 13:39:22 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <85d31d43-d98d-ad8a-01f5-a9ada3cf0110@gmail.com>
Date: Tue, 9 Apr 2019 13:39:21 +0200
Cc: 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-Transfer-Encoding: quoted-printable
Message-Id: <4C7DE24D-A2E5-42AC-9855-8CCF2C3C1B05@kuehlewind.net>
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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.104.8)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1554809986;57e2181e;
X-HE-SMSGID: 1hDp62-00069t-Do
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/PlAxWaR-XKPY8pZB4Sa0iOt_y8E>
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 11:39:49 -0000

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.

Mirja


> 
> Did the WG analyze every possible ramification? No. But as far as I'm
> concerned this was a conscious choice that obtained WG consensus.
> 
>    Brian
> 
>

v2.8.7 | Report a Bug | By Email