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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 09 April 2019 22:23 UTC

Return-Path: <brian.e.carpenter@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 DB43612003F; Tue, 9 Apr 2019 15:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KKfTjlAWY1rx; Tue, 9 Apr 2019 15:23:31 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 11A65120013; Tue, 9 Apr 2019 15:23:31 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id 8so115264pfr.4; Tue, 09 Apr 2019 15:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=XN4wbApm2g3FicFvQ4Fs6oVdDpF8HT0pm7Qio2YXZgI=; b=e5CYkq5QyAOgmXiATsa+tPUU8dH1svnLllTuUvfU+gCe82Ck3PU8fy2+q50gmskPE7 /aPN+GBcUPYJfLcyRVVSqpNsYJJ7R7nChI7C++xfgsdc4PjG+PK8mJf5XY72qRQy7cqc wmXPd30HPbY0eQ81E8ABltUelYKG6RioVqJz7Dap0q6X3P1Kqx6oJOFNVVvOjfvj9MuP pp3ohZwDfMLhbv8E80OKDGVjInDZZ2GfmQXKsEFF/2fe+FufcKQ2XHksH4Mmt89l2S4e rNNlDswHSBn5dcbQvNPRbBFeeOhZWOTI/wsCJHvHO3/W1/a1S50rGwRRjDG+NVNSfrx4 9+ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XN4wbApm2g3FicFvQ4Fs6oVdDpF8HT0pm7Qio2YXZgI=; b=bzavqR04FwAC1z23gY/jlx7cbR2cjAW6yOOfEQuUnljGzLR9f2tzWuIf/A75VChWTs FRdMQb2ZwcyTwPhGhy9GMwMjSe8KiMYaH3+wEHroEcwsyXyPPMilyTm4tU9GneWhQcYf mX3U/rzRD5R5YXrF9jEqojUiL+yxzAtH54E5JAsvu6LRetiSnSOMMhg79CFbDTLtezSV wlLzo/gHhsM0YsgnXtvQrX235ylnvGfy4YJ+YAzAiABpZr1uyQAvw1HoHrLS+7/aqSJT xHyn7alwh7txJlZl4zc9tG9kV64rm2dWnGVHeHD0WKsEzPD+vLboFfcNimtSxe6hl/0q /bzQ==
X-Gm-Message-State: APjAAAWRaicvgxA36D5fbUFgS+TGklXCsjn/LKXQ3qlpifUighirS9Ps 2BH6orQUat2hhjCj9hrj+7lTDlDm
X-Google-Smtp-Source: APXvYqwIxYy2MfqrcQDOn/CPfg1CgGEU3qGrIJFBzQ8SqvJkJlkwmPvJqp7ZUKPbr7YnHkrDgrv/+g==
X-Received: by 2002:aa7:9389:: with SMTP id t9mr40049114pfe.60.1554848609922; Tue, 09 Apr 2019 15:23:29 -0700 (PDT)
Received: from [130.216.36.25] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.25]) by smtp.gmail.com with ESMTPSA id l10sm24549662pfc.46.2019.04.09.15.23.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Apr 2019 15:23:29 -0700 (PDT)
To: Alissa Cooper <alissa@cooperw.in>
Cc: Barry Leiba <barryleiba@computer.org>, Ted Hardie <ted.ietf@gmail.com>, draft-ietf-iasa2-rfc4071bis@ietf.org, Jon Peterson <jon.peterson@neustar.biz>, IASA 2 WG <iasa20@ietf.org>, Russ Housley <housley@vigilsec.com>, iasa2-chairs@ietf.org, IESG <iesg@ietf.org>
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> <51F9114D-3845-40A5-AC2F-25A3F7B7A428@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <92271d10-1b07-69ce-977e-3c13ba8ebcc9@gmail.com>
Date: Wed, 10 Apr 2019 10:23:25 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <51F9114D-3845-40A5-AC2F-25A3F7B7A428@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/JlhtZerIVE_OI5nuwHtIhUXW0yA>
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 22:23:33 -0000

> This is not correct. As Joe pointed out, any director can be removed via the IETF recall process.

I don't think so. Agreed, the draft says:

>    Directors may also be removed via the
>    IETF recall process defined in [I-D.ietf-iasa2-rfc7437bis],
>    Section 7.

But that Section 7 says:

>    The following rules apply to the recall process.  If necessary, a
>    paragraph discussing the interpretation of each rule is included.
> 
>    It applies to IESG and IAB Members, the NomCom appointed IETF Trust
>    Trustees, and the NomCom appointed IETF LLC Directors.

That *does not* include the IESG-appointed LLC Director, even
if they are an IESG member.

If that's a drafting error in 7437bis, my point would be
satisfied by fixing it.

Regards
   Brian

On 10-Apr-19 08:59, Alissa Cooper wrote:
> Hi Brian,
> 
>> On Apr 9, 2019, at 4:52 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>
>>>> 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.
> 
> This is not correct. As Joe pointed out, any director can be removed via the IETF recall process.
> 
> Alissa
> 
>> 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?
>>
>> 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.
>>
>>     Brian
>>
> 
>