Re: [rfc-i] IAB Seeks Feedback on Independent Submissions Editor

Nico Williams <nico@cryptonector.com> Sat, 14 September 2019 08:04 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0190B1200BA for <ietf@ietfa.amsl.com>; Sat, 14 Sep 2019 01:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=cryptonector.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 3g7M-pgBlmft for <ietf@ietfa.amsl.com>; Sat, 14 Sep 2019 01:04:25 -0700 (PDT)
Received: from crocodile.birch.relay.mailchannels.net (crocodile.birch.relay.mailchannels.net [23.83.209.45]) (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 3D0FD120024 for <ietf@ietf.org>; Sat, 14 Sep 2019 01:04:25 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 6B56B5E218A; Sat, 14 Sep 2019 08:04:24 +0000 (UTC)
Received: from pdx1-sub0-mail-a11.g.dreamhost.com (100-96-86-165.trex.outbound.svc.cluster.local [100.96.86.165]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id D7D495E24C2; Sat, 14 Sep 2019 08:04:23 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a11.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.17.5); Sat, 14 Sep 2019 08:04:24 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Little-Ruddy: 2989d78859654773_1568448264149_3266492746
X-MC-Loop-Signature: 1568448264149:2475848979
X-MC-Ingress-Time: 1568448264148
Received: from pdx1-sub0-mail-a11.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a11.g.dreamhost.com (Postfix) with ESMTP id 2A8A78353A; Sat, 14 Sep 2019 01:04:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=a3xMWwx6lwqVNr zqnesXsgttH9o=; b=dI1e5FntLKsFDa2AL7UqVejL+kdy0uvDqb5fgTCmSoBmZn XYEsWRDROBOl/5wFekPdAP1a5/B5Cl3cFExPR/ou95JCoM40XkUd6Q3ZGVA5xurU U23RtKjlRNWnZi/Qwp84EoeD4Q5Yt+BkR+MAC+AYhk+TDUL3Fjv3MzKDMWtw4=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a11.g.dreamhost.com (Postfix) with ESMTPSA id F24708352C; Sat, 14 Sep 2019 01:04:18 -0700 (PDT)
Date: Sat, 14 Sep 2019 03:04:16 -0500
X-DH-BACKEND: pdx1-sub0-mail-a11
From: Nico Williams <nico@cryptonector.com>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: Randy Bush <randy@psg.com>, Eric Rescorla <ekr@rtfm.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [rfc-i] IAB Seeks Feedback on Independent Submissions Editor
Message-ID: <20190914080415.GA5002@localhost>
References: <156814308493.22374.12964350262219210658.idtracker@ietfa.amsl.com> <e9a47208-c847-85a3-ba1b-2135da1e1b1b@nthpermutation.com> <CA+9kkMAeuokjeraHuL2KJt8REqhxnR2Gow90bZgeazV6GEN78A@mail.gmail.com> <c182bdf6-f592-b512-32ba-6a439f03c16f@nthpermutation.com> <CA+9kkMAFGe5pFMWJnbLP1gKT1KGm50faQqWc1_bViDPnib9oSQ@mail.gmail.com> <320B79B1F7F7631266F4C8D5@PSB> <CA+9kkMAGW=RhCmoF=-MgsrNn_cmmYJoZ22-kNRJwwQX6ZEJujg@mail.gmail.com> <CABcZeBO5m+obV85qmasmvkzOUPKHVQRo=mVLsJx7yAK8J+E3pg@mail.gmail.com> <m2h85fzmq2.wl-randy@psg.com> <b72c09b0-ec67-1e33-a8ee-a5d2f0c1a148@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b72c09b0-ec67-1e33-a8ee-a5d2f0c1a148@gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrtdekgdduvddvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucfkphepvdegrddvkedruddtkedrudekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhenucevlhhushhtvghrufhiiigvpedt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1JoJhqXIr6ok2wplsuMJB1J26QQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2019 08:04:27 -0000

On Fri, Sep 13, 2019 at 06:15:08PM -0800, Melinda Shore wrote:
> On 9/13/19 5:32 PM, Randy Bush wrote:
> >> [0] To the extent to which one believes -- mistakenly, IMO -- that
> >> traffic on the ietf@ list ought to be taken as a proxy for the views
> >> of the community.
> > ok.  i'll bite.  you have another suggestion that is not a closed space
> > with important people breathing each others' smoke?

We could limit the general list to announcements and IETF Last Calls.

Discussion of the sort that might not be possible to settle due to the
fact that no consensus call is involved, plus strong opinions from
forceful personalities, should be OK to start here provided it then
moves elsewhere.

> This is something we're going to need to deal with at some point -
> some number of community participants have indicated that they do
> not subscribe to ietf@ because of the volume/tone/low signal-to-
> noise ratio.  Those are people who are part of the community and
> not participating here.  We have never made an explicit decision
> to discount the views of people who can't/won't tolerate this
> mailing list but it's effectively what we're doing, I think.

Well, if they don't subscribe and participate because of volume and
noise-to-signal ratio, then arguably they're helping :/  OTOH, this list
is very important process-wise, yet here we are making it a DDoS on its
subscribers by filling it with noise.  If all IETF participants started
participating on this list, the resulting cacophony would make the past
few months' worth of archives feel like a peaceful walk in the park.

As for tone, it certainly doesn't keep me away, for whatever that's
worth, but the volume and the noise?  Oh yeah, that does.  Yet here I
am...  not helping :(  Others might be kept out by tone, but whatever
the causes for any one person, we almost certainly can't scale this list
to all IETF participants being active on it.

This was a thread about ISE, and once more we have (potentially, unless
everyone else can just not bite) a thread about about tone.  Every
thread (every thread!) seems likely to devolve into being a continuation
of the acrimonious debates we've been having lately that aren't
consensus calls, so there's no way to settle them.

> I don't know if that's the problem that EKR has in mind but I do
> think that it's one reason that the while the views expressed here
> are basically definitive, in terms of IETF process, they don't
> necessarily reflect the actual views of the community.  (Maybe
> someone is willing to argue that that the people who remove themselves
> are randomly distributed with respect to the community but I
> seriously hope not).

I've no idea about that distribution.  I won't suppose it's uniform, or
that that matters.  There are probably many IETF LCs where we need only
miss one particular voice to possibly cause serious problems.

However, I suspect that most IETF participants who do not subscribe here
are WG participants who contribute to the development of WG work items
and aren't too interested in how the IETF process, and the IETF itself,
evolve.  For a long time that was a fair description of me, and the
noise from this list did not keep me so much as just not needing it at
all in my life.  It takes more than passing interest in such things to
participate here -- there's legal and business knowledge, experience,
and skills that one must have in order to really move the needle and not
merely add to the noise.  It's almost like a WG -- I don't participate
in most WGs...

Nico
--