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

Alissa Cooper <alissa@cooperw.in> Mon, 08 April 2019 18:49 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 9732A12031D; Mon, 8 Apr 2019 11:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=bBvF5QY5; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=z4PUPxo6
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 VD622MhSNTeQ; Mon, 8 Apr 2019 11:49:30 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC2741200F9; Mon, 8 Apr 2019 11:49:29 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id D294F7FD; Mon, 8 Apr 2019 14:49:28 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 08 Apr 2019 14:49:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=K fJk13VWMpBBdt7Bqf59Omk0CWzl+kdBONysG7hnMpQ=; b=bBvF5QY5z2q/m/o7q 5sqqLzaMz6Kx5ibt7601FAMolU8GT/dPe/rx2zgu+PzdAP4Ifx+aZcv1t8fhIo++ LRf3l5UhJnGIilJ1ZCYRPjIHYsCUIY5xgNaGkGpq3VCnFF03x84ZD77yZu0/RlkA tJb5pU/EytozT96p/sNDOLxY20FYG/ktf8dubIFvv4RVEmOXUq4o8fw0xA+nf+l2 yr6jRwJ6cb2kbd6crMa9d2Z+lYe6bJOzBi/V3/27IqtXicVjjurMvxYGbU6rYbux KV3M4ur1i8jZ76oi9oDdBPCnleYgQfGMws74D2vxltOscX4VXzYPepoozih/5V34 jmGlQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=KfJk13VWMpBBdt7Bqf59Omk0CWzl+kdBONysG7hnM pQ=; b=z4PUPxo69SLLlDIW3EwZVYYBu/cFyeBCyWeLEBVYd11H10ycz1qUzlCaG 4ZqpSIdzWFH4s1pAzG+RaszqkwuepozjiFn5msENk6qLGz97eZm4x3Cz8/J6B+fD cw9nwS0xhYoLfw0JrjajYUr1wy6Fylwegt0otfeEiobPqTn2cgRbNKxwL8P1c05g L2sSA89p+J4LnI57m9ZR2CEnABsXUpCmTMx83OMr6k9dtIdFv/VEXfETnah/upyA x25GekAT1GsXaqZUY0Vg8eChChrk32mQ69Qm1WXDVAgnGGRapSE4dquMLwbjcMi8 F+pdqGsKx+rMn8ExudRcd3e7U0YEw==
X-ME-Sender: <xms:t5erXAZ1tw3dlYTfCApk2uUa6tn7kFbmmO7UcWncyUo5KHuI__sHKQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudefgddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrleefnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:t5erXApBx87scQdV-1-c238ueCQVC_7uPug0djy-LGMUf5GZULbOew> <xmx:t5erXMpMEYnziDHjgEDRq1aH5DuEwaqi1enmnBZ8GflEdqNH2FmZbQ> <xmx:t5erXC0k3BG_HZxRJz5D8Znv507PI2mEsVR-yCGfxdQSrJBfCMiIyQ> <xmx:uJerXOmbeFha6gAkyPvsv-ncsZchiXfD8bIJGOC1JY5piZbvQhThig>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 30E941031A; Mon, 8 Apr 2019 14:49:27 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <155470226964.18209.2289908384768506570.idtracker@ietfa.amsl.com>
Date: Mon, 8 Apr 2019 14:49:25 -0400
Cc: The IESG <iesg@ietf.org>, IASA 2 WG <iasa20@ietf.org>, draft-ietf-iasa2-rfc4071bis@ietf.org, iasa2-chairs@ietf.org, Jon Peterson <jon.peterson@neustar.biz>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DEB9E21-996C-4E08-9B84-45E2CBEA3359@cooperw.in>
References: <155470226964.18209.2289908384768506570.idtracker@ietfa.amsl.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/W_tHWTYxBOj_90BdV9BQpHTytyk>
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: Mon, 08 Apr 2019 18:49:33 -0000

Hi Barry,

> On Apr 8, 2019, at 1:44 AM, Barry Leiba via Datatracker <noreply@ietf.org> wrote:
> 
> Barry Leiba has entered the following ballot position for
> draft-ietf-iasa2-rfc4071bis-08: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4071bis/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> — Section 6.4 —
> Adding to what Mirja notes about a two-year term for the IESG appointee: the
> text here clearly assumes it will be the IETF Chair, allows it not to be, but
> makes that situation awkward.  

Can you explain how it makes it awkward?

> Each IESG should be able to change the
> appointment if it thinks it appropriate.  In particular, we chose the IETF
> chair this time to maintain continuity with the transition, but we might
> prefer, once the startup tasks are done, to move to someone else in order to
> lighten the load on the IETF Chair position.  I think such delegation is
> important.
> 
> So for a number of reasons, a one-year term makes more sense, perhaps with text
> encouraging reappointment for two or three years, would be better (along with
> appropriate changes to term limits in 6.5 to specify years rather than terms). 

Another drawback to a one-year term in addition to the ones already mentioned in the thread is that if the IESG does want to run a selection process to fill this slot, they would have to begin that process after appointing a person to this role only 8 or 9 months earlier (to allow time for a call for candidates, feedback, announcing the appointment in advance of the new person being seated, etc.), and possibly before seeing the outcome of one of the board’s major deliberations — whether to approve the following year’s budget. 

Alissa

> Did the working group specifically discuss and reject this?  Or was it just
> aligned to the IETF Chair’s term without giving consideration to these points?
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> — Section 4.1 —
> Is there a difference, now, between the meanings of “IASA” and “IASA 2.0”?
> 
> — Section 6.9 —
> I’ll point out that two thirds of 5 is not 3, so both a quorum and a vote on an
> “act of the Board” require a supermajority of 4 out of 5 Directors.  That seems
> like it could end up being problematic.
> 
> — Section 6.10 —
> What does “from time to time” mean here?  I can’t figure out how to fit the
> normal English meaning of the idiom in here.
> 
>