Re: Terminology discussion threads

Benjamin Kaduk <kaduk@mit.edu> Fri, 14 August 2020 21:07 UTC

Return-Path: <kaduk@mit.edu>
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 57E293A09B4 for <ietf@ietfa.amsl.com>; Fri, 14 Aug 2020 14:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5Aj0TRfViTHk for <ietf@ietfa.amsl.com>; Fri, 14 Aug 2020 14:07:46 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 97CFC3A09A9 for <ietf@ietf.org>; Fri, 14 Aug 2020 14:07:46 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07EL7eX8024869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 14 Aug 2020 17:07:42 -0400
Date: Fri, 14 Aug 2020 14:07:40 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Nico Williams <nico@cryptonector.com>
Cc: ietf@ietf.org
Subject: Re: Terminology discussion threads
Message-ID: <20200814210740.GN92412@kduck.mit.edu>
References: <6AA0BCBB-D95B-4036-B94D-5E79E7B94D75@ietf.org> <F15E387D-9FDC-4A76-8002-78B85F6D16BE@nohats.ca> <CABcZeBNitWbdPO4Y2WfCzjy10Z+s27px6cGT1uRHmtGHa5iX+Q@mail.gmail.com> <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net> <7ec6f897-fd3e-8a22-cf6e-ea457d745982@lounge.org> <20200814191721.GK92412@kduck.mit.edu> <20200814204125.GL3100@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20200814204125.GL3100@localhost>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1-ppZXNkw-SpTnfqqgsGIHEBsPQ>
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: Fri, 14 Aug 2020 21:07:48 -0000

On Fri, Aug 14, 2020 at 03:41:26PM -0500, Nico Williams wrote:
> On Fri, Aug 14, 2020 at 12:17:21PM -0700, Benjamin Kaduk wrote:
> >                                     [...].  Rather, the departure of many
> > prominent IETF contributors from the membership list of ietf@ietf.org has
> > placed us in a (or, perhaps, excacerbated an existing) situation where the
> > membership of what is nominally the "general IETF discussion list" is not
> > representative of the IETF community.  As someone who is, at times, charged
> > with assessing IETF consensus, I feel that this calls into question the
> > utility of the ietf@ietf.org list for determining consensus.  Personally, I
> > now have significant doubts that the results of discussion on ietf@ietf.org
> > will reflect IETF consensus.  [...]
> 
> That's a problem then, because the RFC publication process for the IETF
> requires IETF-wide Last Calls.  Rather than abandon the list,
> subscribers who are unhappy with certain debates should ignore them.
> 
> Damaging or destroying the IETF's ability to publish RFCs is truly
> extreme, whether intentional or otherwise.  I'm not saying that taking
> destructive steps could never be justified, but I am saying it's
> extreme, and in this case not justified or not yet.

Note that, at present, IETF Last Call discussion on documents occurs on the
last-call@ietf.org list, not the ietf@ietf.org general list.  Perhaps that
reduced some peoples' sense of obligation to remain on ietf@ietf.org,
though that is speculation.

-Ben