Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc4844-bis-02> (The RFC Series and RFC Editor)

Russ Housley <housley@vigilsec.com> Mon, 14 October 2019 19:45 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27188120932 for <architecture-discuss@ietfa.amsl.com>; Mon, 14 Oct 2019 12:45:30 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 SK3lDR5XkKEt for <architecture-discuss@ietfa.amsl.com>; Mon, 14 Oct 2019 12:45:28 -0700 (PDT)
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 6980D12091A for <architecture-discuss@ietf.org>; Mon, 14 Oct 2019 12:45:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E7F54300AAB for <architecture-discuss@ietf.org>; Mon, 14 Oct 2019 15:45:26 -0400 (EDT)
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 CyeuqkW1O9-w for <architecture-discuss@ietf.org>; Mon, 14 Oct 2019 15:45:25 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id DFB45300460; Mon, 14 Oct 2019 15:45:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <281D3BF8-CE5E-46D3-B4F4-F0289606C308@cooperw.in>
Date: Mon, 14 Oct 2019 15:45:25 -0400
Cc: architecture-discuss@ietf.org, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <33B6BD0C-260B-4061-A188-58CD1CA44535@vigilsec.com>
References: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com> <281D3BF8-CE5E-46D3-B4F4-F0289606C308@cooperw.in>
To: Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/DwOgQpzlP7Dqs6JnoN6Hz-H6Pto>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc4844-bis-02> (The RFC Series and RFC Editor)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2019 19:45:30 -0000

Alissa:

> Section 3.3:
> 
> The first paragraph of this section fails to mention the IAB and RSOC, which according to RFC 6635 have oversight roles. It seems incorrect to claim that operational oversight is solely the responsibility of IASA.
> 
> The second paragraph is superfluous since the roles of the LLC Board and ED are defined in rfc4071bis, so I think for clarity it should be removed.
> 
> The resulting changes could appear as follows:
> 
> OLD 
> The IETF Administration Limited Liability Company (IETF LLC), as part of the IETF Administrative Support Activity (IASA), is responsible for administrative and financial matters for the IETF, the IAB, and the Internet Research Task Force (IRTF) [I-D.ietf-iasa2-rfc4071bis]. The IASA is tasked with providing the funding for and operational oversight of the RFC Editor.
> 
> The IETF LLC Board provides oversight of the IASA, and the IETF Executive Director is the chief actor for the IASA.
> 
> The IETF Executive Director works with the IAB to identify suitable persons or entities to fulfill the mandate of the RFC Editor.
> 
> NEW 
> The IETF Administration Limited Liability Company (IETF LLC), as part of the IETF Administrative Support Activity (IASA), is responsible for administrative and financial matters for the IETF, the IAB, and the Internet Research Task Force (IRTF) [I-D.ietf-iasa2-rfc4071bis].The IASA is tasked with providing the funding for the RFC Editor. The IASA, the IAB, and the RFC Series Oversight Committee (RSOC) provide operational oversight of the RFC Editor.
> 
> The IETF Executive Director works with the IAB to identify suitable persons or entities to fulfill the mandate of the RFC Editor.

The RSOC is not otherwise mentioned in this document, so to bring the RSOC into this discussion, I think a bit more context is needed.  I suggest:

   The IETF Administration Limited Liability Company (IETF LLC), as part
   of the IETF Administrative Support Activity (IASA), is responsible
   for administrative and financial matters for the IETF, the IAB, and
   the Internet Research Task Force (IRTF) [I-D.ietf-iasa2-rfc4071bis].
   The IASA is tasked with providing the funding for the RFC Editor.
   The IASA and the IAB provide operational oversight of the RFC Editor;
   however, as described in Section 3.1 of [I-D.ietf-iasa2-rfc6635bis],
   RFC Series Oversight Committee (RSOC), acting with authority
   delegated from the IAB, is responsible for ensuring that the RFC
   Series is run in a transparent and accountable manner, including
   design and execution of the RFC Series Editor selection process.

   The IETF Executive Director works with the IAB to identify suitable
   persons or entities to fulfill the mandate of the RFC Production
   Center and the RFC Publisher roles as defined in
   [I-D.ietf-iasa2-rfc6635bis].


> Section 7:
> 
> I would suggest the following to make the text consistent with rfc4071bis Sec. 4.2:
> 
> OLD
>   Under the new structure, the IETF LLC performs the tasks that were
>   previously assigned to the IETF Administrative Oversight Committee
>   (IAOC) under the old structure.
> 
> NEW
>   Under the new structure, the IETF LLC performs the tasks related to IASA that were
>   previously assigned to the IETF Administrative Director and to the Internet Society.

Sure.  That is an improvement.

Russ