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

Alissa Cooper <alissa@cooperw.in> Wed, 10 April 2019 12:27 UTC

Return-Path: <alissa@cooperw.in>
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 CDC821202E4; Wed, 10 Apr 2019 05:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=LlUV+y4o; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XaIpJ+vY
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 PGycc05urUAk; Wed, 10 Apr 2019 05:27:18 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B70A1202E2; Wed, 10 Apr 2019 05:27:18 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 3967F21DB7; Wed, 10 Apr 2019 08:27:17 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 10 Apr 2019 08:27:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=tFkcHfvRkEniuSAGCu6p6Kp t3mIXgxw0O+HwHEOXBL0=; b=LlUV+y4oIaW444AYiBAA5V3Y3yJLu+fqHjP+Zb8 Ai0dyV0bKstnNxB+BvbjGnwxH49aRAlzALeHisBT+kuw/BYNdYrz0g561UaYiaNz N0oahgAo0rcYk1qUzEN7m9mVbmDqCdBqh/bJ/P+yf41CEcWfrdA57QJ1X57gnrh+ TDcsWZ/5FyKkoIKFgdjPVrR//ogrplF9tSW8oAY6X8Cqp6Y9D2ONfSL0xrZAIIt3 BeN487bB195cH0lR+SJSb6ODAnJMfpAJUybil14ez+BHDk0+OeyjJleuMGbSrZdJ Skdg56dXSBj7nsBrHTjC0ETI/Oe+SFIZDlubZTRxyBOdltQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=tFkcHf vRkEniuSAGCu6p6Kpt3mIXgxw0O+HwHEOXBL0=; b=XaIpJ+vYqT+IOXan7SqLwl hE2nCVx0IXzcvxloNoUk2bqHXCihzPZoGGhLt1JbJ8/SD8BmZJHUECmca9p/Ycys vh5l/XfzIac8ZWfTpCy/ciVgy2eE4F2nyg+Vai+G0/ubjZtmKPSzvvans72WDbvq 90rDRZ5OAU504X3Cisc5EmiCp1pG7l78rKFZbZ3ZBbE7TPAwlw9sm+tOvvrLYwxc JKjG4IqaWKNpjj2O2sNJ0+qjbkuV9H1T0SdzMVwicHtLcX80+JTGXqUTXbcuS1EF xXOrpa1Npcvt0mzqhc175a5x2ZY3FrsJxU2W3dF4ccCHzhfyfa44HewWqMEUWYTw ==
X-ME-Sender: <xms:JOGtXGHT5c8tiSkg3nBtO1tP6Q85toSTbl8aS0ODworNl7QyE_LhVg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudejgdehvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhkfgtggfuffgjvfhfofesrgdtmherhhdtvdenucfhrhhomheptehlihhsshgr ucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrghinh epghhithhhuhgsrdgtohhmnecukfhppedujeefrdefkedruddujedrkeejnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:JOGtXPf3LidWjKonfGDPuUtPmS2ZPZX9j-8prJhBlAlnKsU2wqfEOw> <xmx:JOGtXPqLFHWan70bHhH0yB4ORgq_4KujP1VIEqvr1T2YI_ogXgRYrA> <xmx:JOGtXAC0ZHjmgkmZPC-EUyrLcwYeWVYUEwzo-W_DS0JYrjeRH0QquQ> <xmx:JeGtXPF24hZDFkq7pEo9nEYzM7ZiH8ai6mkcbxT4VTcWKC5z3Gv3pA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id A0D91E4332; Wed, 10 Apr 2019 08:27:15 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <4F81EF92-CF7D-4448-9360-89F4E28477D6@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AB19D16F-FC04-4A19-BD38-1CC02781DE34"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 10 Apr 2019 08:27:13 -0400
In-Reply-To: <92271d10-1b07-69ce-977e-3c13ba8ebcc9@gmail.com>
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>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
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> <92271d10-1b07-69ce-977e-3c13ba8ebcc9@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/N4JGLnlPDHtDw9jl_C1mG1fNIbo>
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: Wed, 10 Apr 2019 12:27:21 -0000

> On Apr 9, 2019, at 6:23 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> 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.

Good catch. I filed an issue to address this: https://github.com/IASA2/RFC-7437-bis/issues/9 <https://github.com/IASA2/RFC-7437-bis/issues/9>

Alissa

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