Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))

Alissa Cooper <alissa@cooperw.in> Mon, 30 September 2019 13:01 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 2DA7C120236 for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 06:01:24 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ik9W7c3u; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=A5iV/jQN
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 dQTbkXuF2hpv for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 06:01:21 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53F09120289 for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 06:01:21 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 82FF3206FC; Mon, 30 Sep 2019 09:01:20 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 30 Sep 2019 09:01:20 -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=fm1; bh=I Alq/vXyWIE6Q6Jw+6o+NZ3kZQklNsOjCae2kNjsXSY=; b=ik9W7c3up/751Spwf fwHmyHtmykgROoJEl5TwTwLXdcPyztfJLueJnlZNnFfzm9IQ1yyV7fgSfHrBSgWG fZQ1Y5gPD9Bt7M/wn9YT1irVwpDSCzsKn/qJcl8RNmcghuxLTZ78M24ebiJFTe+H YCm8C8SWSzXsGdxFR/eP870wHILT+GcQrSUEBPXRzsZDdH1rHah0/hPR9Y3LRMGY Lco9cBxMIRBKr8zkLiuvlvufJ6HKz08K+ltXMBLK+gks21PHl+plgpi0yshUrzK7 /fl+XgSvb6TD+oy1OKJ+nlYr0Za+KICkd4op/VlX1nAq0732XZ1fUyn6ZTERgVDp oaBMg==
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=fm3; bh=IAlq/vXyWIE6Q6Jw+6o+NZ3kZQklNsOjCae2kNjsX SY=; b=A5iV/jQNUyT97qdnN8EKxqMhldFHrKnPfX2rYJOHnt44PiZ6V8Wtv6R++ PAuM1vZ0SddsZ8ELRVbW4YNPdJSkesA/sDHvvf2cx8OhIbp8E7BUl2cy6sht66nB aQ18j0YchNhQXwA/wCBbjYwVko+cY7PgpUrtC8gdJJL/5FScNum1FM0rHunMW5WU KWzZ6afaSEieduZEXtkZcje4OABy2N5bNfkLkENikyw51LY54wLnlUXTlgN0dOWN /A1i+3lIJPa/PXRoxGmoRBo9+M/Z34Xg1iKrDx/c+KaLm6EmjE6OVMD7+fiwEw/+ T24WRJxFgI5NULtWT79NLTCwNDZqw==
X-ME-Sender: <xms:n_yRXfmZamYJ9R0dq3UKhjq9xW5p2n6OSfNX5_VhqNn4bstEBqGPJg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgedvgdehhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddu jedrkedunecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfi drihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:n_yRXerMllUfGjU-4vGH59rD9pdKZABh4T5HM7_0_O_j9WZCgPaB6A> <xmx:n_yRXbK5jaDAOX4uYZ7YsEoTpFflt0eNAV2NHwQjFCqaLXlk6GsjNA> <xmx:n_yRXaAYQrO33OumyaXl-4FvXVsqjLhsaWXeggW6H7m5Um7ZSd7qkw> <xmx:oPyRXTLFrAlBhGx3Lv1pkzRwVR-UPEvIeMzesLUzohd9sKJYutKSjw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 3ED3A80063; Mon, 30 Sep 2019 09:01:19 -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: <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com>
Date: Mon, 30 Sep 2019 09:01:17 -0400
Cc: architecture-discuss@ietf.org, The IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in> <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/SExTDAVvLKflg9WzzZdxnrJhzaE>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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, 30 Sep 2019 13:01:24 -0000

Hi Bob,

All sounds good to me.

Thanks,
Alissa


> On Sep 27, 2019, at 7:45 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
> 
> Alissa,
> 
>> On Sep 27, 2019, at 6:33 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>> 
>> Hi,
>> 
>> I have some comments on this document.
> 
> Thanks for reviewing the document.
> 
>> 
>> 
>> Section 1:
>> 
>> s/The IAB maintains it's/The IAB maintains its/
>> 
>> s/Internet Administrative Oversight Committee (IAOC)/IETF Administrative Oversight Committee (IAOC)/
> 
> Good
> 
>> 
>> 
>> Section 2.1:
>> 
>> "The RSE is expected to cooperate closely with the LLC Board and the
>>  stream managers."
>> 
>> Given that the LLC Board is an oversight body operating at a strategic level, I think this would make more sense if it said "LLC" (which includes LLC staff and contractors, including tools people) rather than "LLC Board.”
>> 
> 
> That is fixed in -03.
> 
> 
>> Section 2.1.7:
>> 
>> The LLC is in the process of adopting a conflict of interest policy that will apply to all staff, contractors, and board directors <https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of-Interest-00.md>. Since the RSE will be bound by that policy, I think Section 2.1.7 should be removed to avoid confusion about which policy applies.
>> 
> 
> As Brian Carpenter said, I think it would be a mistake to not say anything.  His proposed text seems reasonable to me, it is:
> 
>  The RSE is expected to avoid even the appearance of conflict of
>  interest or judgment in performing these roles.  To ensure this,
>  the RSE will be subject to a conflict of interest policy
>  established by the LLC.
> 
> 
>> 
>> Section 3.1:
>> 
>> "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."
>> 
>> Since the LLC is the contract holder, it needs to have final decisional authority about hiring and firing, e.g. if it is unable to negotiate suitable contract terms with a candidate. I would suggest the following edit:
>> 
>> "For all decisions that affect the RSE individually (e.g., hiring and firing), the RSOC prepares recommendations for the IAB, but approval of these recommendations is the responsibility of the IAB.”
> 
> I think that is an improvement on the text.
> 
> 
>> Section 4.2:
>> 
>> "The RFC Series portion of the LLC budget shall include entries for
>>  the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The LLC
>>  budget shall also include entries for the streams, including the
>>  independent stream."
>> 
>> Since RFC 6635 was published I can't recall seeing a budget that had a line item for RSOC or for "the streams," so this text has seemingly not matched actual practice for some time. More generally, allowing the LLC some flexibility about how the line items appear seems warranted given that the LLC has this flexibility for the rest of the budget. I would suggest the following edit:
>> 
>> "The LLC budget shall include funding to support the RSOC, RSE, RFC Production Center, the RFC Publisher, and the Independent Submissions Editor.”
> 
> I don’t read this as requiring line items in a published budget, for example, like the one at:
> 
> https://www.ietf.org/media/documents/IETF_2019_Budget_Public_2018-12-19.pdf
> 
> I think it was saying the LLC should be budgeting and tracking these activities, how it reports this to the community is a different matter.  That said, I think your text is clearer, but I think it’s a mistake to call out the RSOC here, as that is clearly part of the IAB.  So I suggest:
> 
> OLD:
> 
>   The RFC Series portion of the LLC budget shall include entries for
>   the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The LLC
>   budget shall also include entries for the streams, including the
>   independent stream.
> 
> NEW:
> 
>   The RFC Series portion of the LLC budget shall include funding to support
>   the RSE, RFC Production Center, RFC Publisher, and the Independent Stream.
> 
> 
>> 
>> 
>> Section 4.4:
>> 
>>  "If a disagreement or decision has immediate or future contractual
>>  consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
>>  RSE must identify the issue and provide his or her advice to the LLC;
>>  additionally, if the RSOC has provided advice, forward that advice as
>>  well."
>> 
>> This sentence is not grammatically correct. I'm not sure what to suggest as it seems to be stating something obvious, but perhaps I'm not able to understand the point being made.
> 
> That is quite a sentence, too many editors here :-)
> 
> How about:
> 
>   If a disagreement or decision has immediate or future contractual
>   consequences, it falls under [I-D.ietf-iasa2-rfc4071bis].  If this happens
>   the RSE must identify the issue and provide advice to the LLC.
>   Additionally, if the RSOC has also developed advice, it should forward that
>   advice to the LLC.
> 
>   The LLC must notify the RSOC and IAB regarding the action it
>   concludes is required to resolve the issue based on its applicable
>   procedures and provisions in the relevant contracts.
> 
> Thanks,
> Bob
> 
> 
>> 
>> 
>> Thanks,
>> Alissa
>> 
>> 
>> 
>> 
>>> On Sep 4, 2019, at 9:59 PM, IAB Executive Administrative Manager <execd@iab.org> wrote:
>>> 
>>> This is an announcement of an IETF-wide Call for Comment on
>>> draft-ietf-iasa2-rfc6635bis-03.
>>> 
>>> The document is being considered for publication as an Informational RFC
>>> within the IAB stream, and is available for inspection at:
>>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>>> 
>>> The Call for Comment will last until 2019-10-02. Please send comments to
>>> architecture-discuss@ietf.org and iab@iab.org.
>>> 
>>> Abstract
>>> 
>>> The RFC Editor model described in this document divides the
>>> responsibilities for the RFC Series into three functions: the RFC
>>> Series Editor, the RFC Production Center, and the RFC Publisher.
>>> Internet Architecture Board (IAB) oversight via the RFC Series
>>> Oversight Committee (RSOC) is described, as is the relationship
>>> between the IETF Administration Limited Liability Company and the
>>> RSOC.  This document reflects the experience gained with "RFC Editor
>>> Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to
>>> replace all references to the IASA and related structures with those
>>> defined by the IASA 2.0 Model.
>>> 
>>> [RFC Editor: Please remove the following paragraph prior to
>>> publication.]
>>> 
>>> The IASA2 WG requests that the IAB publish this replacement for RFC
>>> 6635.
>>> 
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> 
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
>