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

Bob Hinden <bob.hinden@gmail.com> Mon, 30 September 2019 15:35 UTC

Return-Path: <bob.hinden@gmail.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 4A5851200EC for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 08:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aXB168x_8G9a for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2127912081B for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id r5so11841478wrm.12 for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ujyA2DWDaHtVTdVISbAO8GVIKP2ZTrDDEkKtmZ0qQ38=; b=pZZYj+zFtZGDwU/PSveQ7s9YacmS5LrmyiVcCK2k0hqhK9LKGje2yMdhzQ9rEeInlg hR5DthMfaRAfqJwKZCUr2a4t2gpmaIebHRRRI5wXtFriZ8KZFzTo/MDXOwJgs4xw5hwj KkStTogw2jA6b0NePwEH4nbAsoDc0YdaV95bWosC61zv3YLsQp556/Jf6bDYtcnDUD1c bQ/VtMvwjTIP6yh6PnSJl2PqXvcoEZdR89WoDmvqm/vzYP4mWTP6ecGHVLJuTHRfmnbt k5ybsIBHB9aD4NGrp7bcS9xng9om76KQ0pSeId+u56UpgQ6UoqlZb5ksGbndkyOrCF/e KRQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ujyA2DWDaHtVTdVISbAO8GVIKP2ZTrDDEkKtmZ0qQ38=; b=p03H+24QnbhQBJW75pi4+zDSkOUQCjneSZ6JSZbP0p5ojKITqJDgSJ+Y2da3eib2LE 0BACshakQ3o4qjHrTJS3xkW0Yyl2mLpBgYXCY8JsxKHKE8rWmw++gNo+8hCCEIBXyjMT UHkC51+bQms1Hv2g8mBR+KISEnfXmM4kCL0O0FiSvsopNaZeS/VwVc/W4O05gKldRcWp Ja8Bj3OAWG7D2zaj9bZDicZ5UwdQDTozsevyODD8onvPNKHo3xUKwmPSEouEEx2weQA8 Ni+xMcfCvJe9FuQAup+SH6ftQxe6plb1XjlfKyBUW/HDlYMTNiPQvW/cZs75XNbGBU7Z 7UeQ==
X-Gm-Message-State: APjAAAWDOrePfhHPk4IF9orrJV7xf+DwxQIv/xc+MabVp87rtOwqH/MZ slH4PCcmqejfVYqeakf9KtoJI84T
X-Google-Smtp-Source: APXvYqyibEUXRzQoi0aKraoFXsMf7K8RoNgCuyUYPnq0IyY5c1CLJr/2QgDor3iVyHxGeyHhLF1Vkw==
X-Received: by 2002:adf:e292:: with SMTP id v18mr529292wri.232.1569857745466; Mon, 30 Sep 2019 08:35:45 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:944d:9d98:6dcb:5730? ([2601:647:5a00:ef0b:944d:9d98:6dcb:5730]) by smtp.gmail.com with ESMTPSA id w125sm41138929wmg.32.2019.09.30.08.35.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Sep 2019 08:35:44 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <71DF4217-A53A-4D0A-ABDF-B75E59B4168F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2357E333-2888-41F0-91F4-8F025B1377C9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 30 Sep 2019 08:35:41 -0700
In-Reply-To: <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org, The IAB <iab@iab.org>
To: Alissa Cooper <alissa@cooperw.in>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in> <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com> <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/qJnMxDfYFKpTdwurlLSE1cxZaNE>
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 15:35:50 -0000

Thanks, I will plan a new version with these changes after the last call ends on 2019-10-02.

Bob


> On Sep 30, 2019, at 6:01 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> 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
>> 
>