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

Alissa Cooper <alissa@cooperw.in> Tue, 15 October 2019 17:25 UTC

Return-Path: <alissa@cooperw.in>
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 76FB012083A for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 10:25:13 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=l4h3/arS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=croJftjt
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 b3FKI80HJLUr for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 10:25:10 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8494120808 for <architecture-discuss@ietf.org>; Tue, 15 Oct 2019 10:25:09 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id F1BE372D; Tue, 15 Oct 2019 13:25:07 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Tue, 15 Oct 2019 13:25:08 -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=fm1; bh=8Tnr5t3j/0LXRLS421gQkLb dtBjHp70h+CJHX0EPT+o=; b=l4h3/arSZ7oHAVHPsJg05frKIJQ5foTlmZ7Fgmi D3+V1+N3sZd+4xyp9J9STKbLbfpLziMFt8kilZsAx7tz6cVnxAta0jyg4OsCtDyt on+74/tSLcs4mNIVbQ/c5V0pu3rNdxvE0KLj1k6uFVH9LgWqOuts6NwKqnE3a4ER 3vTlaJ+DQeZ/9c/JzvbctYPfsOHR/WlRwhpC7K3imuzNOr2+4uQb71gerys42evt LOj3CKN1f/MUIgEGx1Gh/gvOujKdlcY9S1xH1dIw85rChzCHQNu9mheMROKF/+lv +lDjTO425dnWcNpx2ndFzUTkNAs+qK5vkLTzuAiIrjjqmSw==
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=fm1; bh=8Tnr5t 3j/0LXRLS421gQkLbdtBjHp70h+CJHX0EPT+o=; b=croJftjtvCD1byyYgx/9ZS JrWyD3Uw7/lRnnKhbppsz3VItgtEZec7w3mIhkyyljC8MWldkNEU+/GhPpqHSrz+ DSyJZ8E/UiW07A1f7NSkoFrlu+47EKa6rF+pfu+p+MxzC5N0nCRyce4E4cZ4tHAp YSvdjwQxNf5sguqleWTkDWDlSqJtCigF3iqATpGzcRpeaCZdCl7GsTb/+THIDZAA 7plqlryu4fvLhjA0hOMX88HQqpHKpN41ehq/LRr2tSGkIyk7NVRNIQkIhaycn8d5 qyaVGz/lFUvgciPwtCeutaZNKIny2mlE+OB7v++65/qZqOkZ651PwOEDXaIan5tA ==
X-ME-Sender: <xms:8wCmXbdZgHMIE60IP5_MFom4GTofvcNxn3P9NuZeWzo33Ts3d0P4Wg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrjeefgdduudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffktgggufffjgfvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdekfeenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:8wCmXYqUxpY-xEPV2YKKedRNPiBygvRpL13AAnd5oN1n1GxYLuKTug> <xmx:8wCmXR5Dt2vyL3_XscmKUvpP0VHlksPR67pVhIMawdxvBgxuxZm40w> <xmx:8wCmXWoLx09tWgFJ3XcG1JXPDF1PzqYP84qPsvjxHlNHtW3S6VavCA> <xmx:8wCmXUEa_hmsuA8ssv0UqDv_6PIOzL5FtwOd6We2lN4YjL0Gdj7O_g>
Received: from rtp-alcoop-nitro3.cisco.com (unknown [173.38.117.83]) by mail.messagingengine.com (Postfix) with ESMTPA id CC36BD60066; Tue, 15 Oct 2019 13:25:06 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <9B58D313-3DF5-485E-92AD-9DDA1B9BACE5@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_461DBE85-464B-4AD0-85EB-3470200B15DC"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 15 Oct 2019 13:25:05 -0400
In-Reply-To: <5614790E-8498-4546-8585-3171EB3C722B@vigilsec.com>
Cc: Leslie Daigle <ldaigle@thinkingcat.com>, IAB <iab@iab.org>, architecture-discuss@ietf.org
To: Russ Housley <housley@vigilsec.com>
References: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com> <281D3BF8-CE5E-46D3-B4F4-F0289606C308@cooperw.in> <33B6BD0C-260B-4061-A188-58CD1CA44535@vigilsec.com> <8B086B3F-5630-43BF-91E2-6747EE75EC03@thinkingcat.com> <5614790E-8498-4546-8585-3171EB3C722B@vigilsec.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/k3Mk80voyOk5-BP3Tj8AQXDUOiU>
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: Tue, 15 Oct 2019 17:25:24 -0000

WFM
Alissa

> On Oct 15, 2019, at 12:22 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> Leslie:
> 
> Works for me.  
> 
> Russ
> 
> 
>> On Oct 15, 2019, at 10:09 AM, Leslie Daigle <ldaigle@thinkingcat.com <mailto:ldaigle@thinkingcat.com>> wrote:
>> 
>> I agree that the second point is improved wording.
>> 
>> However on the first point, while I agree a rewrite is in order, I think Alissa’s suggested text, and your refinements, are taking us a bit off track.
>> 
>> In-line:
>> 
>> On 14 Oct 2019, at 15:45, Russ Housley wrote:
>> 
>> 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.
>> 
>> Oh, boy, operational oversite from 3 independent bodies! Sounds like serving 3 masters, and two is already discouraged in most literature.
>> 
>> The original intent was to make the distinction between oversight of substantive matters (which fell to the IAB, and now its delegate, the RSOC) and contractual, day-to-day matters, which falls to the admin side of the house.
>> 
>> I think we need to continue to make some version of that distinction (and, evidently clearer than it was originally written).
>> 
>> I also note that the original text, convoluted as it had become, made the IAD/IETF Executive Director, in charge of those contracts. If we simply say “the IASA”, we introduce an infelicitous fourth potential oversight body, in the shape of the IASA LLC Board. There is nothing in this setup that rises to the level of the involvement of the IASA LLC Board, except in its normal oversight of the exec dir.
>> 
>> Straw text:
>> 
>> 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 (through the IETF Executive Director) provides contractual and financial oversight of the RFC Editor. Additionally, 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].
>> 
>> Leslie.
>> 
>> 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
>> 
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org <mailto:Architecture-discuss@ietf.org>
>> https://www.ietf.org/mailman/listinfo/architecture-discuss <https://www.ietf.org/mailman/listinfo/architecture-discuss>
>> --
>> 
>> Leslie Daigle
>> Principal, ThinkingCat Enterprises
>> 
>> ldaigle@thinkingcat.com <mailto:ldaigle@thinkingcat.com>