Re: [Iasa20] Benjamin Kaduk's No Objection on draft-ietf-iasa2-rfc4071bis-09: (with COMMENT)
Joseph Lorenzo Hall <joe@cdt.org> Thu, 11 April 2019 15:06 UTC
Return-Path: <jhall@cdt.org>
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 ECE1612038D
for <iasa20@ietfa.amsl.com>; Thu, 11 Apr 2019 08:06:02 -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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=cdt.org
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 5UW18Nr55KLi for <iasa20@ietfa.amsl.com>;
Thu, 11 Apr 2019 08:06:00 -0700 (PDT)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com
[IPv6:2607:f8b0:4864:20::333])
(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 EA31812037E
for <iasa20@ietf.org>; Thu, 11 Apr 2019 08:05:59 -0700 (PDT)
Received: by mail-ot1-x333.google.com with SMTP id f10so5507136otb.6
for <iasa20@ietf.org>; Thu, 11 Apr 2019 08:05:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=T7P5vmij9r5h0MF1npfIQdI0iVkTqb1zygZgmieOxaI=;
b=lkhOEox2vbI7DZiW7ew9M+M8HpWepWsAUu1aTr3ZP3zZusMUYDBkAiIHhYNIZAb+xm
IU8y73NHKoz9FJ3KER9Ea8IeNf8P3KEpfwcoDAY2FREHZYnsvbvDk3xBD9o0pwA9evcg
5IJ1fRWrD72WXRQ0ni6tLVR8liLgnq39MId4w=
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=T7P5vmij9r5h0MF1npfIQdI0iVkTqb1zygZgmieOxaI=;
b=PYevWfo4rhLKcHj/3m4saBcWWEMrlipt7ep4rhI47mtahc4RZh4wY4ZrsVTnkX3T1p
RUEvUGKbGAKfJoHTa7rc5Jfw80dY3qDpHmh991Qz6LfRnbgT6kPmPLwayy5i7pcuHdxb
yLAuTD8sA4MoohdGCOb4whf0bxjnu/Vfp+j3CPiKk6jfSW0g/FRMOVZshrQjkY64kMu1
keGTAW8QAydNXtlTpw9ZmjugOUh98KQRGA3lZ8Oo0pFLO4JF4/ErHQdDitRZFQLTTw/1
XYd7r3cKfb+gQaxyjPUVrQRSVsy3qo+QEFD0Y+1ppLNVeNd6fwlZ12WKmj/Kmk1HPU3x
41xQ==
X-Gm-Message-State: APjAAAXZMnwziIoBDPYJVH3a3FTF0lsmrAyDIhXI6BykyGYN3RcejhGB
X4PIysu88UqGIpH2STLafwIdr+EcrD5Mn8ApuZQc7FQ+5ws=
X-Google-Smtp-Source: APXvYqwyjpr/tOBxUOW/oLBZa4mVPHappvw2ZsNvz/+VwyEVhCM8jhzgSOyUqv3zkLXSA5D/vKWCh9cBS2Trg7MWk7w=
X-Received: by 2002:a9d:63d5:: with SMTP id e21mr30885075otl.288.1554995158858;
Thu, 11 Apr 2019 08:05:58 -0700 (PDT)
MIME-Version: 1.0
References: <155498907076.25231.13801022071773065752.idtracker@ietfa.amsl.com>
In-Reply-To: <155498907076.25231.13801022071773065752.idtracker@ietfa.amsl.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 11 Apr 2019 11:05:48 -0400
Message-ID: <CABtrr-XbQkVvGykEMDnb9jyFxZaei39R=4KgbnBXsB5nsoermQ@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000125adb0586428636"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/77H7z8s50cgsCH_KubEHkg6FjBI>
Subject: Re: [Iasa20] Benjamin Kaduk's No Objection on
draft-ietf-iasa2-rfc4071bis-09: (with COMMENT)
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: Thu, 11 Apr 2019 15:06:03 -0000
Thanks, Ben! Responses inline, pointing to opened github issues that we'll bang out shortly... On Thu, Apr 11, 2019 at 9:24 AM Benjamin Kaduk via Datatracker < noreply@ietf.org> wrote: > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Four paragraphs is fairly long for an Abstract. > > This is a pretty foundational document, so I think it's a rarity. > Section 1 > > Under this > structure, the Internet Administrative Oversight Committee (IAOC) is > eliminated, and its oversight and advising functions transferred to > the IETF LLC Board. > > (I note that the Abstract uses the past tense "was eliminated", and also > differs about whether the 'I' is "Internet" or "IETF".) > Are we comfortable tossing out the concept of the IAOC with no lead-up > or reference? > > We'll fix both the tense confusion (will try to prefer present tense, if possible): https://github.com/IASA2/draft-ietf-iasa2-struct/issues/99 Should we point to the definitions to fix the last problem? We can easily say "See Section 4.1" for the definitions or we could insert something like: OLD Under this structure, the Internet Administrative Oversight Committee (IAOC) is eliminated, and its oversight and advising functions transferred to the IETF LLC Board. NEW Under this structure, the IETF Administrative Oversight Committee (IAOC) -- the previous administrative oversight body for the IETF -- is eliminated, and its oversight and advising functions transferred to the IETF LLC Board. Holler if that works. Section 2 > > It's great to say that no changes are made, but that doesn't help > someone looking for the current procedures if we don't provide a > reference to what the current procedures are. > > Here, are you saying that we should enrich that paragraph with citations? So, something like: OLD The document does not propose any changes related to the standards process as currently conducted by the Internet Engineering Steering Group (IESG) and Internet Architecture Board (IAB). In addition, no changes are made to the appeals chain, the process for making and confirming IETF and IAB appointments, the technical work of the Internet Research Task Force (IRTF), or to ISOC's membership in or support of other organizations. NEW (added three BCP refs): The document does not propose any changes related to the standards process as currently conducted by the Internet Engineering Steering Group (IESG) and Internet Architecture Board (IAB) [BCP 9]. In addition, no changes are made to the appeals chain, the process for making and confirming IETF and IAB appointments [BCP 10], the technical work of the Internet Research Task Force (IRTF) [BCP 8], or to ISOC's membership in or support of other organizations. Section 4.2 > > o The Board of Directors of the IETF LLC - formally a multi-member > "manager" of the IETF LLC on behalf of ISOC - assumes the > oversight responsibilities of the IAOC. > > I'm not sure whether there's any ambiguity about whether "of" means > "over" or "from", to a reader who doesn't already know that it means > "from". > > Is this just saying you think it reads better if s/of the IAOC/from the IAOC/ ? > Section 6.2 > > As noted above, a maximum of two Directors may be appointed by the > IETF LLC Board. They can obviously choose to appoint none, one, or > two. These appointments need not be on an exceptional basis, but > rather be routine, and may occur at any time of the year since it is > on an as-needed basis. > > nit: I think there's a word missing here, maybe in "can rather be routine". > There also seems to be a singular/plural mismatch between "these" and > "it". > How about: s/rather be routine/can be routine/ ? > > The appointment of a Board-appointed Director requires a two-thirds > majority vote of the Directors then in office, and the appointee > shall take office immediately upon appointment. [...] > > Upon appointment, or upon appointment *and confirmation*? > > Good catch, will fix by making that addition: https://github.com/IASA2/draft-ietf-iasa2-struct/issues/100 > > The Board may decide on a case-by-case basis how long each term shall > be, factoring in the restriction for consecutive terms in > Section 6.4. > > Section 6.5 also seems relevant. > > This is a typo; it should point to 6.5, will change. https://github.com/IASA2/draft-ietf-iasa2-struct/issues/101 > Section 6.10 > > If a quorum is not present at any > meeting of the Board, the Directors present may adjourn the meeting > from time to time, without notice other than announcement at the > meeting, until a quorum is present. [...] > > I'm not sure I understand the purpose of "from time to time" in this > sentence. (Barry seems to have covered this already, though.) > Yes, Barry proposed a fix that would deal with this, will update in the next version: https://github.com/IASA2/draft-ietf-iasa2-struct/issues/102 > Section 7.7 > > The IETF LLC exists to support the IETF, IAB, and IRTF. Therefore, > the IETF LLC's funding and all revenues, in-kind contributions, and > other income that comprise that funding shall be used solely to > support activities related to the IETF, IAB, IRTF, and RFC Editor, > and for no other purposes. > > Why are the lists in the first and second sentences different? > Because the RFC Editor is contracted through the IAB, but that somewhere in the WG discussion it felt important to call out in the second list. I don't think we can just add the RFC Editor to the first list... but we could do something like this: "The IETF LLC exists to support the IETF, IRTF, and IAB (through which the RFC Editor receives support)." best, Joe -- Joseph Lorenzo Hall Chief Technologist, Center for Democracy & Technology [https://www.cdt.org] 1401 K ST NW STE 200, Washington DC 20005-3497 e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 1607 5F86 6987 40A9 A871
- [Iasa20] Benjamin Kaduk's No Objection on draft-i… Benjamin Kaduk via Datatracker
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Ted Hardie
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Benjamin Kaduk
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Alissa Cooper
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Eliot Lear
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Eliot Lear
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Benjamin Kaduk
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Salz, Rich
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Barry Leiba
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Russ Housley
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Michael Richardson
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Joseph Lorenzo Hall
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Brian E Carpenter
- Re: [Iasa20] Benjamin Kaduk's No Objection on dra… Brian E Carpenter