Re: [Gendispatch] IETF transparency and diversity

Tony Rutkowski <rutkowski.tony@gmail.com> Fri, 09 April 2021 19:56 UTC

Return-Path: <rutkowski.tony@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19233A09DF for <gendispatch@ietfa.amsl.com>; Fri, 9 Apr 2021 12:56:41 -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, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, MONEY_NOHTML=0.001, NICE_REPLY_A=-0.001, 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 (2048-bit key) header.d=gmail.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 GFmyphISt-Sp for <gendispatch@ietfa.amsl.com>; Fri, 9 Apr 2021 12:56:40 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 5B5E33A09D8 for <gendispatch@ietf.org>; Fri, 9 Apr 2021 12:56:40 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id c123so2245899qke.1 for <gendispatch@ietf.org>; Fri, 09 Apr 2021 12:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=x0F6TrdLz5QCIgNAi3u4JgzsCBH+9EUosG2ldvcoe4M=; b=ckF2IQ7UXS4iCsrPy/xns9GMHGFrud+kUdhRSTvpYIlXm2zQ/mzeauH9c3/TGX1BEX eOaGUyLDol2kLDFNq5yx8VeX9+E1krPBxzKe2GBJO/o09UVJoseHGrvEQUkVQ5cMF/IZ XRxqilOJqLeV9Vxiiqs28zc52VsJV7xnBlpJLXOug2pOdZe2GnsNhNB+pcQCgWRmf0s6 RsHPgnclPWT8+T3KRaPlTmuWBUcAXouYc8YY0w0xkz9K8hq+vzYTITDu06hCIcT6yR+a 8GBs3izOrKq89GKH4HKnGxKgE34qx2UkMciBSCqZAzyLUlQkusEJquRHO0qnhlVZoL9X 6VCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=x0F6TrdLz5QCIgNAi3u4JgzsCBH+9EUosG2ldvcoe4M=; b=Gz/N3YT7lgnNFSV0LOLiwH6RRsRCi+PwpxTc3Y7Wcf8z2INbpbzGUPBb4cVYYGKz7g 59ywG7rkxBUmRG6WT+qC2avT6lrzirtwwNzxYBx5wsYqGrmsFxg2Q7uNzf32GXBOjSSa Sy8P6gxqye6vpJz3DoxiSnGRCA9rtLk1rWhRuU3hSCJ6z4YWFz9Qj707bi/LViaANBP8 U6FGkGHxeKQsEIuuETYE6OZL1WUoztkuFRsMgMO/QKhEvpb1rv57Jeu8L1V4m3+JybAZ EiCwX6xWjV5nS6+en05KoyPLx+qT+Hkn9iKYMVrUmlh4LuWKfAu863td2LBM8xKJ8clm LETg==
X-Gm-Message-State: AOAM532d13/8K7/QQL533JGg4onqA0cmelKLzPMIPDfX7npp/gcOCL/x IZ3vtZT+/CFP1oHkF0wgyERAReTvFCc+RQ==
X-Google-Smtp-Source: ABdhPJwprODBJu3eiG2AOpr8K8LkNPrgCgon4VyedTPyAx6Gqhz4QnFupJJKUUGMDb9lTnJOr4oRRw==
X-Received: by 2002:a05:620a:152f:: with SMTP id n15mr8177217qkk.129.1617998198805; Fri, 09 Apr 2021 12:56:38 -0700 (PDT)
Received: from [192.168.1.249] (pool-70-106-222-98.clppva.fios.verizon.net. [70.106.222.98]) by smtp.gmail.com with ESMTPSA id v11sm2457133qtx.79.2021.04.09.12.56.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Apr 2021 12:56:38 -0700 (PDT)
To: Mark Nottingham <mnot@mnot.net>
Cc: "gendispatch@ietf.org" <gendispatch@ietf.org>
References: <CAChr6Sxa6uY+nOzWW=MSXP_ekLaBSCTfjC2YcURi+kX0h2X+Rg@mail.gmail.com> <MN2PR11MB43668B598495DFDD060D33E2B5769@MN2PR11MB4366.namprd11.prod.outlook.com> <CAChr6SxZY6j+n1ps5C7R3ySePNpRt_9rdE5sB37FRmp6DBBVJA@mail.gmail.com> <3D340A9D-1A39-4ADA-BA27-E4E912CA6D03@akamai.com> <8d9a6f04-4d6d-288a-e901-aa17c42a5886@gmail.com> <CABcZeBM4e3vrNHA1+==n=KamRLwPUSWMgvQsTtVhA_uBaHaBug@mail.gmail.com> <65aec12d-715d-9447-65ae-70b14bbab717@cs.tcd.ie> <CAChr6SxYWW5CpY5t=ZD+xg+wH=YH5_nu+L_8dpP7_p+dED-ggA@mail.gmail.com> <2dfc430a-be5c-507d-1f63-9df7f71c9588@cs.tcd.ie> <eedbc43b-82ea-2f95-d3db-69f601093a8d@gmail.com> <E0D59DE7-0858-4A9D-A17C-C6D4050BFF92@mnot.net>
From: Tony Rutkowski <rutkowski.tony@gmail.com>
Message-ID: <32ab9a0e-d105-6861-7b46-c438bb5547bc@gmail.com>
Date: Fri, 09 Apr 2021 15:56:37 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <E0D59DE7-0858-4A9D-A17C-C6D4050BFF92@mnot.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/Qvb3gqRH_nvgu9EnsxPRD35_RZI>
Subject: Re: [Gendispatch] IETF transparency and diversity
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 19:56:42 -0000

Hi Mark,

It was good to see a recognition that the IETF has a potentially 
significant antitrust exposure and willingness to increase the 
transparency mechanisms as a first step.  The exposure here is not new.  
The first major independent analysis of the topic occurred in 1994 by an 
external lawfirm.  I know, because I signed the check, and then signed 
for the liability insurance.  Over the years and especially during the 
past decade, almost all significant standards bodies individually and 
collectively have engaged in activities to diminish the exposure and 
develop related sets of organisational practices.  The IETF has been 
largely a non-participant outlier, ignoring the problems; although the 
relatively recent formation of the LLC and work of legal counsel have 
made some improvements.

The IETF has long been "easy pickings" for antitrust behaviors because 
of the lack of transparency and other organisational practices which 
enable the adoption of a IETF standards that enable a company to acquire 
significant market share for a product or service.  I believe there was 
testimony in recent litigation that an IETF specification was worth 
about $4 million.  Continuing participation in the IETF is very costly 
and the number of participants attributed to a few specific companies or 
(as noted by Phil H-B, unattributed operatives) at meetings is a 
testament to beneficiaries.

The observation that the IETF's problems today extend well beyond 
anticompetitive behavior seems spot on.  The participant and work item 
metrics show that major contemporary specification development and 
engagement today have shifted rather massively to venues like 3GPP.  The 
IETF remains stagnant.  Large numbers of academics flow in and out to 
mine ideas and advance their academic studies.  Few companies want to 
pursue anything there anymore except for a comparative handful trying to 
leverage a few more years and dollars out of legacy technologies.

The tendencies in the IETF to be abusive and intolerant - especially to 
people who are apostates - has unfortunately been standard practice in 
the IETF in the past few decades.  If you reject the religious mandates 
of the IETF, you are declared "off topic," or fail to get a group 
started, or told to go elsewhere - often in abusive ways.  The 
intolerant behavior is especially difficult for those in many 
non-Western cultures.  These are the bigger problems of the IETF.

All organisations are largely incapable of analysing themselves and 
understanding their strengths and weakness in the larger ecosystem.  The 
tendency is to reject criticism - even when it is essential.  It seems 
worth not only maintaining a generic discourse list, but to encourage 
dissident and critical participation without dismissing commentarity as 
rhetorical and pile-on behavior.  Occasional good humour would also help.

best,
tony r (working as an agnostic analyst who admittedly preferred the IETF 
circa 1970-1992)


On 08-Apr-21 1:02 AM, Mark Nottingham wrote:
> So all of the above suggest that maintaining a generic IETF discourse list is probably a good thing.  --tony r
> That is a *huge* leap  -- can you show us your workings?
>