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

"Leslie Daigle" <ldaigle@thinkingcat.com> Tue, 15 October 2019 14:09 UTC

Return-Path: <ldaigle@thinkingcat.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 391F8120119 for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 07:09:52 -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, HTML_MESSAGE=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 (1024-bit key) header.d=thinkingcat.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 bahymH72JA6O for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 07:09:50 -0700 (PDT)
Received: from anteater.oak.relay.mailchannels.net (anteater.oak.relay.mailchannels.net [23.83.215.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 906EB120043 for <architecture-discuss@ietf.org>; Tue, 15 Oct 2019 07:09:49 -0700 (PDT)
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 0202120A95; Tue, 15 Oct 2019 14:09:47 +0000 (UTC)
Received: from pdx1-sub0-mail-a97.g.dreamhost.com (100-96-6-135.trex.outbound.svc.cluster.local [100.96.6.135]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 7DE75229FA; Tue, 15 Oct 2019 14:09:31 +0000 (UTC)
Received: from pdx1-sub0-mail-a97.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Tue, 15 Oct 2019 14:09:46 +0000
Received: from pdx1-sub0-mail-a97.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a97.g.dreamhost.com (Postfix) with ESMTP id F385E7F7ED; Tue, 15 Oct 2019 07:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :cc:subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=thinkingcat.com; bh=a v2B97rDgXUhch9iEXQFIq30Vgo=; b=oL659Zga+jygb+/L6l1cTaDDkoumiT1DN jURC0Zjy4BwGGn5iFz1iSo4vUUbAPruf1Z35VrzoSdKl1WhaC0fKSIAhwBBkt1v1 iyvsDiigTUpOcGWu1XTT14iZVPJFFWcBs5c15XjVIuOxfGcQXuh0a5dgGiVgLXFh AH5QFE83+0=
Received: from [192.168.62.222] (unknown [94.142.114.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ldaigle@thinkingcat.com) by pdx1-sub0-mail-a97.g.dreamhost.com (Postfix) with ESMTPSA id 3C5FB7F7EC; Tue, 15 Oct 2019 07:09:22 -0700 (PDT)
X-DH-BACKEND: pdx1-sub0-mail-a97
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Russ Housley" <housley@vigilsec.com>
Cc: "Alissa Cooper" <alissa@cooperw.in>, IAB <iab@iab.org>, architecture-discuss@ietf.org
Date: Tue, 15 Oct 2019 10:09:15 -0400
X-Mailer: MailMate (1.13r5655)
Message-ID: <8B086B3F-5630-43BF-91E2-6747EE75EC03@thinkingcat.com>
In-Reply-To: <33B6BD0C-260B-4061-A188-58CD1CA44535@vigilsec.com>
References: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com> <281D3BF8-CE5E-46D3-B4F4-F0289606C308@cooperw.in> <33B6BD0C-260B-4061-A188-58CD1CA44535@vigilsec.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C9294CF6-24EB-416D-8630-92141E330D24_="
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/BwLdHzhu2Fek_TCo_Ekxg0NMUyw>
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 14:09:53 -0000

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
> https://www.ietf.org/mailman/listinfo/architecture-discuss

-- 

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises
ldaigle@thinkingcat.com
-------------------------------------------------------------------