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

Russ Housley <housley@vigilsec.com> Sat, 09 February 2019 18:44 UTC

Return-Path: <housley@vigilsec.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 5C53C126D00 for <iasa20@ietfa.amsl.com>; Sat, 9 Feb 2019 10:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 6UDL_VzCWFB2 for <iasa20@ietfa.amsl.com>; Sat, 9 Feb 2019 10:44:25 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 622621312FE for <iasa20@ietf.org>; Sat, 9 Feb 2019 10:44:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 22D39300AAB for <iasa20@ietf.org>; Sat, 9 Feb 2019 13:25:48 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EHT9YzLGLVzu for <iasa20@ietf.org>; Sat, 9 Feb 2019 13:25:45 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-108-45-137-105.washdc.fios.verizon.net [108.45.137.105]) by mail.smeinc.net (Postfix) with ESMTPSA id 84007300474; Sat, 9 Feb 2019 13:25:45 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <23C614C4-5C79-4355-9D74-2ED7D0DE63B2@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2164FF43-35C4-47D3-AE46-F38E9049BE0A"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Sat, 9 Feb 2019 13:44:01 -0500
In-Reply-To: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in>
Cc: IASA 2 WG <iasa20@ietf.org>, draft-ietf-iasa2-rfc4844-bis@ietf.org
To: Alissa Cooper <alissa@cooperw.in>
References: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/tLzY-A1DjKoW7WoiaeBo4ucfbNE>
Subject: Re: [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 18:44:29 -0000

Alissa:

I think we want the hiring/firing of the RFC Series Editor to stay with the IAB, but the funding to stay with IASA.  The decision whether the ED serves on the ROC should not be determined by this document.  If the IAB wants the ED to be part of RSOC, they can make that appointment.

Perhaps it would be best to make this change:

OLD:

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

NEW:

   The IASA is tasked with providing the funding for the RFC Editor.
   The IETF Executive Director is tasked with overnight of contracts
   and operational agreements related to the RFC Editor.

Russ

> On Feb 8, 2019, at 8:11 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> 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
> 
>