Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01

Richard Barnes <rlb@ipv.sx> Sat, 09 February 2019 23:49 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C28A130FD4 for <iasa20@ietfa.amsl.com>; Sat, 9 Feb 2019 15:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 dCY5EdayRxXJ for <iasa20@ietfa.amsl.com>; Sat, 9 Feb 2019 15:49:10 -0800 (PST)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 488A5130FCF for <iasa20@ietf.org>; Sat, 9 Feb 2019 15:49:10 -0800 (PST)
Received: by mail-ot1-x332.google.com with SMTP id 32so11880163ota.12 for <iasa20@ietf.org>; Sat, 09 Feb 2019 15:49:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=10QRkUgAcY5MbbTAT+5/puyaylZFHM+B4yFzw1bnYs4=; b=hMDflvW8ql9ScwbO0LYAoe6hytjxBalNAqaMs8ZrvJnhppdFGHphzbgzAtlgF/FaJt 3bmSvf+6yWexn1PV8Jdej5le2/xdDpCDD2ppBbjMkxAXnSbkL0+h4TNufo0kjMgak7jB 84fbTnbnZvOuQA0CccqUBDFoSt4EltvTzqwQasYiKwPIMebjKUP+J+6lZMGXUVQaZeDx z1k1jDD914dgypL5YBd7PTbDqYEtyZ+BXPbFy8kil8gGPQarcLwp4+jZSZpWOk54zQVg mgRp4X3WcpFnLYCnX+BWbF4aGG3oIzAvxfTzzG6NsOs8FGrPFsIQgwWkVKKMfAYyQpoR Q2vw==
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=10QRkUgAcY5MbbTAT+5/puyaylZFHM+B4yFzw1bnYs4=; b=UIoEUF4hC5WaZh6M+4bFfCocjldm01e5nk25DxLRH6BGYX0KQe1OqMwqF2nOhFdpTp jteUnPJ3Lw6SLbgKjKrWJvLgARoIcQmBUL4S174GCqsPJQ+Fb4ClE+HqJtrCjwapnOGi jpPOzoxIxnQEksw/G/uVciZy3f1BWLXx4dzYFWeuWjcqXitcwbUCN8N+BtI2YfaXOgPk O2pzpzWlLBZbwN1pNfbJh9z9mSd8W9lUYCIWtaAZstmWjMeJb0qMRgCkKvtBfa2kgnkd /ciRCMN3UOeUgHpG78p+4RFmmRlHD7dYjNU8awKZveMreGwmxN9A4j8wkF8uHMOkg+Ks ncYQ==
X-Gm-Message-State: AHQUAuZcbOsFFNV4xkjA2z3+vw1TbBcd50nMTps+Ygn+aBcIMIoZJ8eL XX6ugJq5MRBgPwMUqaRKp3anaGE+Xe1TcZiZL0eWjw==
X-Google-Smtp-Source: AHgI3Ib8Kkbj1r6L7/wxfQLa39gXY2jJ+phiQ4yaOhvWymeiwtMj6EMEiti4Y9vdYT8pJkjiwLciLAXJbohuu7c0qqg=
X-Received: by 2002:a9d:6347:: with SMTP id y7mr12425231otk.331.1549756149263; Sat, 09 Feb 2019 15:49:09 -0800 (PST)
MIME-Version: 1.0
References: <32C06675-C60B-4D6A-979A-FC3653E56D42@cooperw.in> <23C614C4-5C79-4355-9D74-2ED7D0DE63B2@vigilsec.com>
In-Reply-To: <23C614C4-5C79-4355-9D74-2ED7D0DE63B2@vigilsec.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Sat, 9 Feb 2019 18:48:57 -0500
Message-ID: <CAL02cgTzEQPTXyPL-ermABDne2G8F8UjbPpYADkyxxWHnVVf4g@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: Alissa Cooper <alissa@cooperw.in>, draft-ietf-iasa2-rfc4844-bis@ietf.org, IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c403f905817eb8ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/8e3yy_6SyvzocpvyhMttajewSWs>
Subject: Re: [Iasa20] Comments on draft-ietf-iasa2-rfc4844-bis-01
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2019 23:49:14 -0000

On Sat, Feb 9, 2019 at 1:44 PM Russ Housley <housley@vigilsec.com> wrote:

> Alissa:
>
> I think we want the hiring/firing of the RFC Series Editor to stay with
> the IAB, but the funding to stay with IASA.
>

This is not a reasonable thing to ask.  One of the key driving factors for
this whole endeavor it makes no legal sense for an organization to delegate
its hiring / firing / contracting decisions to people external to that
organization.

By all means, the IASA should work with the IAB on the RSE, but since the
IASA is ultimately the responsible party, it can't totally cede
responsibility.  The "operational oversight" text that's in there now seems
like it captures this accurately.



> The decision whether the ED serves on the ROC should not be determined by
> this document.  If the IAB wants the ED to be part of RSOC, they can make
> that appointment.
>
> Perhaps it would be best to make this change:
>
> OLD:
>
>    The IASA is tasked with providing the funding for and operational
>    oversight of the RFC Editor.
>
> NEW:
>
>    The IASA is tasked with providing the funding for the RFC Editor.
>    The IETF Executive Director is tasked with overnight of contracts
>    and operational agreements related to the RFC Editor.
>

I don't see how this accomplishes what you claim above.  The IETF ED is
part of the IASA.  And especially given that, the second sentence here is
really just micromanagement of the LLC.

--Richard



>
> Russ
>
> On Feb 8, 2019, at 8:11 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>
> Earlier this week the IAB discussed whether to
> put draft-ietf-iasa2-rfc4844-bis-01 out for community review. In reviewing
> it I felt there were some clarifications needed before it would be ready
> and the IAB thought the most appropriate path would be to bring those to
> the WG for resolution first.
>
> I haven’t started my AD review of 4071bis yet (hope to next week), but I
> think 4071bis has a problem in that the definition of “IASA” in that
> document is broken (it refers to the definition in 4071, which it itself is
> obsoleting). And until it is clear how we are defining “IASA,” I have
> trouble with statements such as the following from Section 3.3 in 4844bis:
>
> "The IASA is tasked with providing the funding for and operational oversight
> of the RFC Editor.”
>
> Is the RSOC part of IASA? It’s pretty hard to tell without a good
> definition of IASA, which we do not currently have IMO. (I think there is a
> further problem with the sentence above, which is that the funding comes
> from the LLC, and it would be better to be that specific.)
>
> While looking at Section 3.3, I don’t think this text belongs there since
> this document is about the RFC series and editor, not IASA generally:
>
> "The IETF LLC Board provides oversight of the IASA, and the IETF Executive
> Director is the chief actor for the IASA.”
>
> I also find lack of clarity between 4844bis Section 3 and 6635bis Section
> 3. For example, 4844bis says:
>
> "The IETF Executive Director works with the IAB to identify suitable persons
> or entities to fulfill the mandate of the RFC Editor.”
>
> While 6635bis says:
>
> "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.”
>
> But under the current model (which I presume we plan to keep), the ED is a
> member of the RSOC. So does the ED work directly with the IAB? Or
> indirectly with the IAB through the RSOC? Or both?
>
> 4844bis also says:
>
> "The IETF Executive Director may define additional operational
> requirements and policies for management purposes to meet the
> requirements defined by the various communities.”
>
> I wonder if this is really consistent with what is envisioned in 6635bis.
>
> I also find it odd that the budget for an RSE search is discussed in
> 6635bis, while the budget for the RFC Editor function overall is discussed
> in 4844bis — is the separation meaningful? Since the LLC Board approves the
> whole IETF budget, presumably what 4844bis says about the RFC Editor budget
> applies to the search budget mentioned in 6635bis as well, but since it’s
> not explicit it isn’t totally clear.
>
> Thanks,
> Alissa
>
>
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>