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

Ted Hardie <ted.ietf@gmail.com> Tue, 15 October 2019 17:57 UTC

Return-Path: <ted.ietf@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 44C301201C6 for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 10:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 (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 EIuDSnj4sTfL for <architecture-discuss@ietfa.amsl.com>; Tue, 15 Oct 2019 10:57:41 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 9FC28120808 for <architecture-discuss@ietf.org>; Tue, 15 Oct 2019 10:57:41 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id w12so47958967iol.11 for <architecture-discuss@ietf.org>; Tue, 15 Oct 2019 10:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ASlOPtele9g4BZgyVjhC/J0RIuu2wSgICSGHVjcm2Vw=; b=AhUG6xUCTesF6RUoMFkRE+qf5V8zbqoXL+1HJWsJPZExfE59wn4u3wwt5d1QTADO7C Dc05egzRTKyp1r7D17sfCcJqGlXqS9yx1Br2sB5Y8IhyD94+PUrk8NMgamAIMzxn4dUE 8eZDWmppzoUBiV0LmqXKcEtP9EJw0g7IimPHea5GQyIZilAiIVDwBlM4u04YMT6G1jCn BlKRHKBsFn5e5k/xAY1eHgdtvfqrooEe6fWSlEAGpL3uV1m3VzXxdWeVNcMcezw+RTYI 5fZprBjCOAe2n0NWZVgWluT60Zb+vF35IrKX6B3V2lDkINLp9cBKM0uucM1iJqWZXmye GR5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ASlOPtele9g4BZgyVjhC/J0RIuu2wSgICSGHVjcm2Vw=; b=j7ZvYftQTRFYFVoxHpXAzidjvzDmLTw0sbvFe8HtKkWlGey/um6+WEV7WlQWkG2n9b tbwKN9cpqxiChCTSfpHiQMkBTcWU8AGGfDbdfQ1+RvVbC5Lld4auVqZMhfq2hmWcciOs CKWO91YSWbkSdOF7vnQ1czFM3jJBMChdCdtPW7gd2k5Hg98SvdsHIlhki2uguCVsL9HO vBS8uUZwmg/GUVe1e1iTUY6DP/vt89FNPdfDE4wjfxSagLedNz5+qIho86dRKflLxAiF 0MkZPgC3wgVz4YTtkdehqT5+45iM0B9B8ZGa3+h2C9eEYHa407U6En5tgxoN/iCmL2To 7fcA==
X-Gm-Message-State: APjAAAUh28/hYSJyboLFYvWnpiw0tEqoLKQ4Zanlv6ujIdhnpUBQiK1y mfYfWew90QwQ6s6BfWKPnAQbUz310JFjYoJMA28=
X-Google-Smtp-Source: APXvYqzxV3Ze2Wx7PNz2HA4W7Usrw/liyamr5TpObgLe/WdRJok1lumSoMZKAEQvTMcU7awotThWhOjAtrHVHd7CZ5k=
X-Received: by 2002:a6b:ce03:: with SMTP id p3mr6505958iob.290.1571162260722; Tue, 15 Oct 2019 10:57:40 -0700 (PDT)
MIME-Version: 1.0
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> <9B58D313-3DF5-485E-92AD-9DDA1B9BACE5@cooperw.in>
In-Reply-To: <9B58D313-3DF5-485E-92AD-9DDA1B9BACE5@cooperw.in>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 15 Oct 2019 10:57:13 -0700
Message-ID: <CA+9kkMBFUrsoxL1XfrSLEtOcVVAqxjdaDgA9RCofzNg_ScK=tg@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Russ Housley <housley@vigilsec.com>, Leslie Daigle <ldaigle@thinkingcat.com>, IAB <iab@iab.org>, architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006f5a840594f6b860"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/iT_XN2XAdHOy5ELT4w7-iqqPjvU>
Subject: Re: [arch-d] [IAB] 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:57:45 -0000

Hi Russ,

If everyone is okay with this text, can you update the draft?  I'll bring
it to an IAB meeting (probably week after next, but possible the one after
that, depending on the other agenda items).

thanks,

Ted

On Tue, Oct 15, 2019 at 10:25 AM Alissa Cooper <alissa@cooperw.in> wrote:

> 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>
> 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
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>
> --
> ------------------------------
>
> Leslie Daigle
> Principal, ThinkingCat Enterprises
> ldaigle@thinkingcat.com
>
>
>
>