Re: [Terminology] Update to TERM charter text

Mallory Knodel <mknodel@cdt.org> Tue, 13 April 2021 23:09 UTC

Return-Path: <mknodel@cdt.org>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96883A1504 for <terminology@ietfa.amsl.com>; Tue, 13 Apr 2021 16:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Kve-jG2S-JAd for <terminology@ietfa.amsl.com>; Tue, 13 Apr 2021 16:09:44 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 56D533A15F1 for <terminology@ietf.org>; Tue, 13 Apr 2021 16:09:32 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id b28so1015263pft.8 for <terminology@ietf.org>; Tue, 13 Apr 2021 16:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aKhACsiHCc5ifkTOfNPIqVnYzDcBhHPBnxAu/0u56y4=; b=n/QliVMaNuDws8+ml77IuazLSQm0t7HsuyzKCFsyGQRxV9UqzLrRnZ00z7V3HbNL0a EtY0yr2W/xaNZC6y2vCIUphXh0Qy9tlPR9SpzJd426cXu5YUtDp5Zt+mHSdQKmICh4nv C655DLk9FmuCBOYMEio18ThFnz7tlp16P/BQI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aKhACsiHCc5ifkTOfNPIqVnYzDcBhHPBnxAu/0u56y4=; b=t+2adkFLIDwoFEQRu0/NV6UX7bx8cbe9JzHfMbNnrLyPQZTysRXvsz41P/BOMixX/r YFJlrGULcoHF1w3MhQs8fa1uMrMm9smUatcPPIWrpKz7B+Jv9HmO8UlYWaFQQVuBQa73 VEzpO7HPayfwFSMfb5Mkwmn99hXHkqfkcX17kV6BY0K5wtmDfjqVOoyOVOJTOLSLWQAp bm2u3arvoZ6tB//L1gfp4xaH7KsD63W1wXDJrgFEMM/hGWZTAgi3sKG76sBKq9WSteIn BeBs9BsrwNcEpFYDTAcQnoPS7MPXc2+kLtrg+0YhVyP93fOhRgwxkTTxObwkrlyqTYzj iM0A==
X-Gm-Message-State: AOAM530ymkElKZBkZnityHHJawENXZZASIje8PUHOUsMNfeYAFSPRl6f X+7J+e3ztN2T8UXaWAOaO8FuZuUK17DM8rg8d1U+vQ==
X-Google-Smtp-Source: ABdhPJwjf78V0Vhrg+1RZCF1sX6n5T7uq5IrNVjTt6imRun2LBIFRGdzlnJRQlQa1/czqKT9vevb3SQYUAYLQVDKKlI=
X-Received: by 2002:a63:4944:: with SMTP id y4mr35267709pgk.9.1618355369876; Tue, 13 Apr 2021 16:09:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a05:6a10:a48d:0:0:0:0 with HTTP; Tue, 13 Apr 2021 16:09:29 -0700 (PDT)
In-Reply-To: <cd599df3-aea0-c529-44a1-5da96e3eb12d@gmail.com>
References: <8143F715-9D83-4C15-B441-D0D8CA302C50@eggert.org> <D5FEBE8C-14D4-48BD-AAE7-9436E296CB7E@eggert.org> <ed88e91a-1224-4918-710e-dfe6e5c89df4@digitaldissidents.org> <9191f3bd-d52a-4fa4-b117-79b3bb517cdf@www.fastmail.com> <6a54335a-b033-60a1-a431-ba92954527cc@digitaldissidents.org> <CANMZLAb4wHudyNCr+m7VosqfMz=nzKtt54thb8pCQS8kKoisMw@mail.gmail.com> <50b0ee01-f587-b132-4305-5241b01cbaca@cdt.org> <cd599df3-aea0-c529-44a1-5da96e3eb12d@gmail.com>
From: Mallory Knodel <mknodel@cdt.org>
Date: Tue, 13 Apr 2021 19:09:29 -0400
Message-ID: <CAGVFjMLJjWE=N_cH=ESrDLV8C09QeTXC=Ojkqdm9WX7O72hUOg@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Niels ten Oever <lists@digitaldissidents.org>, "terminology@ietf.org" <terminology@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f1328005bfe2b844"
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/Per3TVAf5-SA9GFbzpkRc7oZ6AU>
Subject: Re: [Terminology] Update to TERM charter text
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2021 23:09:50 -0000

Hi,

On Tuesday, April 13, 2021, Brian E Carpenter <brian.e.carpenter@gmail.com>
wrote:

> Mallory,
>
> Nobody is creating a new layer. We're just running the IETF process as
> we've run it for three decades.
>
>
>
I am not questioning process or the process fairness or whether or not
anyone else is following process. I do, however, appreciate being corrected.

I am offering my view that there appears to be a choice in processes and we
may have chosen badly if I do a quick calculation:

Current process: IESG+community approval of a WG charter + production of a
document + WG+AD+IESG+Community approval.

That’s three milestones and several rounds of approvals (6?).

IS: production of a document + GA/AD sponsorship + IESG+Community approval.

That’s three milestones and 3? approvals.

IS just seems more lightweight, and ideally the AD and willing members of
the IESG could work on production, cutting down more hurdles.

Now I think IS isn’t ideal if it wouldn’t represent community consensus.
(I’ve heard others say this but surviving last call would mean consensus,
would it not?)  But since the IESG approves it, this is rather more
satisfying ime due to DEI initiatives needing some healthy degree of
leadership in order to break reactionary impasses, sometimes, as a peril of
majority rules communities.

Please be patient if I’ve gotten something wrong. I’m merely trying to
explain my prior messages and my intention more clearly.

-M



>
> On 14-Apr-21 01:40, Mallory Knodel wrote:
> > Hi all,
> >
> > Remembering that once this WG is chartered it's supposed to draft a
> document. So, aren't we making it much harder for ourselves by creating
> this abstraction layer that first needs IESG+community approval of a
> charter, and then also production of a document that will need
> WG+AD+IESG+Community approval? A document just needs GA/AD+Community
> approval once.
> >
> > -Mallory
> >
> > On 4/13/21 6:48 AM, Brian Carpenter wrote:
> >> Niels,
> >>
> >> I don't understand your concern. The IETF process doesn't treat
> charters the same as drafts. It's the IESG's job to approve charters,
> because until there is a charter, there is no WG and no WG Chair. And it's
> the whole IETF's input that counts, not just the people who happened to
> propose the charter.
> >>
> >> Regards
> >>   Brian
> >>
> >> On Tue, 13 Apr 2021, 22:39 Niels ten Oever, <
> lists@digitaldissidents.org <mailto:lists@digitaldissidents.org>> wrote:
> >>
> >>
> >>     On 13-04-2021 12:22, Bron Gondwana wrote:
> >>     > Unfortunately, this "problem" is not restricted to GENDISPATCH.
> I haven't even been in the IETF that long but I've seen multiple documents
> - drafts, charters, etc, be exposed to larger review and have the carefully
> crafted work of a working group be re-considered when it's exposed to a
> wider review.
> >>     >
> >>     > Indeed, this is precisely the function of an IETF last-call -
> otherwise why do we bother sending work to the IESG for review?  We could
> just deliver every piece of careful "working group last call"ed document
> directly to the RFC editor with no cross-sectional review.
> >>     >
> >>     > Of course, the flip side is that as a participant in the process,
> you can ask for the work to be brought back to GENDISPATCH to see whether
> there's consensus for the new document or not.  Or you could just object to
> charter in its current form I guess, I'm not sure how that works at IETF
> last-call stage.  One thing is for sure, the IETF processes aren't good at
> enforcing that the IETF goes ahead with the exact consensus product of a
> single working group, unchanged by wider review.
> >>
> >>     In my experience, IESG review brings up comments that are for the
> authors to fix, instead of IESG fixing them for you.
> >>
> >>     Best,
> >>
> >>     Niels
> >>
> >>     >
> >>     > Regards,
> >>     >
> >>     > Bron.
> >>     >
> >>     > On Tue, Apr 13, 2021, at 19:41, Niels ten Oever wrote:
> >>     >> Dear IESG,
> >>     >>
> >>     >> I am dismayed by the discussion in the IESG on the charter and
> the revisions that are proposed. The charter that was proposed was the
> product of long and complex discussions in GENDISPATCH. The review in the
> IESG is now rehashing those debates but changing the outcome. The changes
> in the charter are thus subvert the consensus that was carefully built. The
> proposed changes therefore undermine and jeopardize the work that the
> proposed WG could produce.
> >>     >>
> >>     >> Best,
> >>     >>
> >>     >> Niels
> >>     >>
> >>     >>
> >>     >> On 13-04-2021 08:46, Lars Eggert wrote:
> >>     >> > Hi,
> >>     >> >
> >>     >> > there is now an -05 version that rolls in some additional
> feedback received yesterday: https://datatracker.ietf.org/doc/
> charter-ietf-term/00-05/ <https://datatracker.ietf.org/
> doc/charter-ietf-term/00-05/>
> >>     >> >
> >>     >> > Diff at https://www.ietf.org/rfcdiff?url1=https%3A%2F%
> 2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-term%
> 2Fwithmilestones-00-04.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%
> 2Fcharter-ietf-term%2Fwithmilestones-00-05.txt <
> https://www.ietf.org/rfcdiff?url1=https%3A%2F%
> 2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-term%
> 2Fwithmilestones-00-04.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%
> 2Fcharter-ietf-term%2Fwithmilestones-00-05.txt>
> >>     >> >
> >>     >> > Thanks,
> >>     >> > Lars
> >>     >> >
> >>     >> >
> >>     >> >
> >>     >>
> >>     >> --
> >>     >> Niels ten Oever, PhD
> >>     >> Postdoctoral Researcher - Media Studies Department - University
> of Amsterdam
> >>     >> Research Fellow - Centre for Internet and Human Rights -
> European University Viadrina
> >>     >> Associated Scholar - Centro de Tecnologia e Sociedade - Fundação
> Getúlio Vargas
> >>     >>
> >>     >> https://nielstenoever.net <https://nielstenoever.net> -
> mail@nielstenoever.net <mailto:mail@nielstenoever.net> <mailto:
> mail%40nielstenoever.net <mailto:mail%2540nielstenoever.net>> -
> @nielstenoever - +31629051853
> >>     >> PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
> >>     >>
> >>     >> Read my latest article on Internet infrastructure governance in
> New Media & Society here: https://journals.sagepub.com/doi/full/10.1177/
> 1461444820929320 <https://journals.sagepub.com/doi/full/10.1177/
> 1461444820929320>
> >>     >>
> >>     >> --
> >>     >> Terminology mailing list
> >>     >> Terminology@ietf.org <mailto:Terminology@ietf.org> <mailto:
> Terminology%40ietf.org <mailto:Terminology%2540ietf.org>>
> >>     >> https://www.ietf.org/mailman/listinfo/terminology <
> https://www.ietf.org/mailman/listinfo/terminology>
> >>     >>
> >>     >
> >>     > --
> >>     >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >>     >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> >>     >
> >>     >
> >>     >
> >>
> >>     --
> >>     Niels ten Oever, PhD
> >>     Postdoctoral Researcher - Media Studies Department - University of
> Amsterdam
> >>     Research Fellow - Centre for Internet and Human Rights - European
> University Viadrina
> >>     Associated Scholar - Centro de Tecnologia e Sociedade - Fundação
> Getúlio Vargas
> >>
> >>     https://nielstenoever.net - mail@nielstenoever.net <mailto:
> mail@nielstenoever.net> - @nielstenoever - +31629051853
> >>     PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3
> >>
> >>     Read my latest article on Internet infrastructure governance in New
> Media & Society here: https://journals.sagepub.com/doi/full/10.1177/
> 1461444820929320
> >>
> >>     --
> >>     Terminology mailing list
> >>     Terminology@ietf.org <mailto:Terminology@ietf.org>
> >>     https://www.ietf.org/mailman/listinfo/terminology
> >>
> >>
> > --
> > Mallory Knodel
> > CTO, Center for Democracy and Technology
> > gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780
> >
>
>

-- 
Mallory Knodel
CTO, Center for Democracy and Technology
gpg fingerprint :: E3EB 63E0 65A3 B240 BCD9 B071 0C32 A271 BD3C C780