[Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01

Alissa Cooper <alissa@cooperw.in> Sat, 09 February 2019 01:11 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 D7D95130EE9; Fri, 8 Feb 2019 17:11:12 -0800 (PST)
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=IqmwuuBp; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HRKx2wzL
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 Kk3MQ9pxdbpr; Fri, 8 Feb 2019 17:11:10 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90273127133; Fri, 8 Feb 2019 17:11:07 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 93B2220FE0; Fri, 8 Feb 2019 20:11:06 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 08 Feb 2019 20:11:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:content-type:mime-version:subject:message-id:date:cc:to; s= fm2; bh=mhWdkHv1fkSzitWor6jcnOncmw4RxzTyJ2EC1RLuwGM=; b=IqmwuuBp sFJv4gaIX31lnX7smKcUPlfRCbSgqlVsqh32KIDUKfuvBHDuule1WHJ8eWY/VNv7 SGdLelK3O/yaV13eDSvFEjg/1CB7iBxCZXEGIFDmBfB+zMWgIE+bqqatBEssUdn9 cB652FfjVRXYutR/fV1zmsdBHlqti21Rb13OKUJNFFwSeKXr2hCgC+SL3SsOfb4V xeXoIHiJk7D//RGUFeV3g10BaGOGkJNtPcrgY9PjiU8HEh5q1MLrlzWh3AIdSxJx y5ksgJZc8UBFPl7yn8aBcVqu0Fy1/TroocnkJe4tKXoR/7wzlEdBjizTO+KU9P3M j5QAe9eXKA+6Og==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=mhWdkHv1fkSzitWor6jcnOncmw4Rx zTyJ2EC1RLuwGM=; b=HRKx2wzLgb9zAWfIumdEzPx751PMj7/ntNCTeT6I4JWki bHV9u59pc2td9izbBHVdKx3zGbwSykore0y8LSNrA2fbuAhQlOgxxhRsXELxx4zQ jdHORW7Eqru2U65JZD4Q74JDj74Al/jD2k2nIS7MEGYUXZIipNXxWFNoIh2KGkUf LTPLCjiPFslqReNdWisVolrT1CkV7ZieLjzjwF3KX4xL6Fge+Xhr7di8Wuh17A2i IJYt4BrA19bxQQHET/0alOsDPEnnLc04LfXTFfgD6d5GZVQtOONKw8nWPuZfX6Z8 W8M3ObqtyVqQvXj59J3DWz9UPiWmKqkbr7VkcyKEw==
X-ME-Sender: <xms:qiheXCF9b_P3tsyyKyHb85wtP3O6coyXGzGawH-3ER7HPmpsNz5faQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrleefgddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephfgtggfukfffvf fosegrtdhmrehhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhs shgrsegtohhophgvrhifrdhinheqnecukfhppedujeefrdefkedruddujedrkeejnecurf grrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:qiheXOP2IjcjYWB2ke8U2qVxuQABZnXhO6Cy9edmQgVhuO7PJ-6flA> <xmx:qiheXD_RJbrCrGCUxKc9j6bKxaVws_HBCrXoyPm9TwpTOXeG6u2buw> <xmx:qiheXKS_FjK9I9ZkIYBJop6ehRzMlz5qiINSXXEtuPgAaa2gpq5cGA> <xmx:qiheXCe90u5ekaJpAa8dpB9l-vjS2qxMDu3o19oLOZFwmGpGQ0E8nw>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id 99D04E44A1; Fri, 8 Feb 2019 20:11:05 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_36175B5C-938F-4599-B16E-8F9BB13FA375"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in>
Date: Fri, 8 Feb 2019 20:11:04 -0500
Cc: draft-ietf-iasa2-rfc4844-bis@ietf.org
To: IASA 2 WG <iasa20@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/izvnwsqC2v1YSSncCoU4ClRZ_qI>
Subject: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
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: Sat, 09 Feb 2019 01:11:13 -0000

Earlier this week the IAB discussed whether to put draft-ietf-iasa2-rfc4844-bis-01 out for community review. In reviewing it I felt there were some clarifications needed before it would be ready and the IAB thought the most appropriate path would be to bring those to the WG for resolution first.

I haven’t started my AD review of 4071bis yet (hope to next week), but I think 4071bis has a problem in that the definition of “IASA” in that document is broken (it refers to the definition in 4071, which it itself is obsoleting). And until it is clear how we are defining “IASA,” I have trouble with statements such as the following from Section 3.3 in 4844bis:

"The IASA is tasked with providing the funding for and operational oversight of the RFC Editor.”

Is the RSOC part of IASA? It’s pretty hard to tell without a good definition of IASA, which we do not currently have IMO. (I think there is a further problem with the sentence above, which is that the funding comes from the LLC, and it would be better to be that specific.)

While looking at Section 3.3, I don’t think this text belongs there since this document is about the RFC series and editor, not IASA generally:

"The IETF LLC Board provides oversight of the IASA, and the IETF Executive Director is the chief actor for the IASA.”

I also find lack of clarity between 4844bis Section 3 and 6635bis Section 3. For example, 4844bis says:

"The IETF Executive Director works with the IAB to identify suitable persons or entities to fulfill the mandate of the RFC Editor.”

While 6635bis says:

"For all decisions that affect the RSE individually (e.g., hiring and firing), the RSOC prepares recommendations for the IAB, but the final decision is the responsibility of the IAB.”

But under the current model (which I presume we plan to keep), the ED is a member of the RSOC. So does the ED work directly with the IAB? Or indirectly with the IAB through the RSOC? Or both?

4844bis also says:

"The IETF Executive Director may define additional operational requirements and policies for management purposes to meet the requirements defined by the various communities.”

I wonder if this is really consistent with what is envisioned in 6635bis.

I also find it odd that the budget for an RSE search is discussed in 6635bis, while the budget for the RFC Editor function overall is discussed in 4844bis — is the separation meaningful? Since the LLC Board approves the whole IETF budget, presumably what 4844bis says about the RFC Editor budget applies to the search budget mentioned in 6635bis as well, but since it’s not explicit it isn’t totally clear.

Thanks,
Alissa