Re: What's the alternative to "snarling"?

Richard Shockey <richard@shockey.us> Mon, 19 April 2021 22:57 UTC

Return-Path: <richard@shockey.us>
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 2BF103A47FB for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 15:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.655
X-Spam-Level:
X-Spam-Status: No, score=0.655 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 Vcrzqt28qFE0 for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 15:57:06 -0700 (PDT)
Received: from gateway30.websitewelcome.com (gateway30.websitewelcome.com [50.116.126.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219B23A47F5 for <ietf@ietf.org>; Mon, 19 Apr 2021 15:57:06 -0700 (PDT)
Received: from cm16.websitewelcome.com (cm16.websitewelcome.com [100.42.49.19]) by gateway30.websitewelcome.com (Postfix) with ESMTP id 837121FA94 for <ietf@ietf.org>; Mon, 19 Apr 2021 17:57:04 -0500 (CDT)
Received: from box5527.bluehost.com ([162.241.218.19]) by cmsmtp with SMTP id YcpElKyzQb8LyYcpElONvn; Mon, 19 Apr 2021 17:57:04 -0500
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To :References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=IMTuXWVV990+WeGZTC9JanC69QLdT+lFnFRyfce4JXE=; b=gmVew4z0XG7+AxO2epGDXbdahg c4hvlHSsCW6lPw0Zvk4+Q91A/KN0E4Eq3qMzRfzuYLKZnpiVnKtjXJ7ua25aIFOEPtmkLVdzBrWUo XMmZRARIC1ktVl83/wLC8NVpy;
Received: from pool-100-36-18-145.washdc.fios.verizon.net ([100.36.18.145]:58744 helo=[192.168.1.156]) by box5527.bluehost.com with esmtpa (Exim 4.94) (envelope-from <richard@shockey.us>) id 1lYcpE-0026Xm-6m; Mon, 19 Apr 2021 16:57:04 -0600
User-Agent: Microsoft-MacOutlook/16.48.21041102
Date: Mon, 19 Apr 2021 18:57:02 -0400
Subject: Re: What's the alternative to "snarling"?
From: Richard Shockey <richard@shockey.us>
To: Keith Moore <moore@network-heretics.com>, Leif Johansson <leifj@mnt.se>
CC: <ietf@ietf.org>
Message-ID: <FE678189-A87E-4BEB-9767-3A6C00D0F948@shockey.us>
Thread-Topic: What's the alternative to "snarling"?
References: <0b63d094-8c95-409f-282e-86231128f7b5@network-heretics.com> <1C5B7B67-27E5-41F5-89D4-765A407C1FC6@mnt.se> <1d7995d4-f193-2316-9052-d22c2961ac14@network-heretics.com> <8a1b6b42-d085-0b79-19e3-589b4e921b95@mnt.se> <8e17dcbe-c4d1-eb94-856e-45026c2f1c43@network-heretics.com>
In-Reply-To: <8e17dcbe-c4d1-eb94-856e-45026c2f1c43@network-heretics.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box5527.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 100.36.18.145
X-Source-L: No
X-Exim-ID: 1lYcpE-0026Xm-6m
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-18-145.washdc.fios.verizon.net ([192.168.1.156]) [100.36.18.145]:58744
X-Source-Auth: richard+shockey.us
X-Email-Count: 1
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NTUyNy5ibHVlaG9zdC5jb20=
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rh02870wh9dIKwkhNnbSbGvia6s>
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: Mon, 19 Apr 2021 22:57:10 -0000

In Line..


On 4/19/21, 5:00 PM, "ietf on behalf of Keith Moore" <ietf-bounces@ietf.org on behalf of moore@network-heretics.com> wrote:

    On 4/19/21 4:09 PM, Leif Johansson wrote:

    > On 2021-04-19 21:46, Keith Moore wrote:
    >> On 4/19/21 11:51 AM, Leif Johansson wrote:
    >>
    >>>> In other words, they can spend all of their time politely explaining in detail why proposals are Bad Ideas, instead of getting useful work done.
    >>> Point to where the useful work will be done if we don’t stop this.
    >> I don't want to either dismiss your concern (which I share) or sound flippant, but I also wonder where the useful work will be done if we DO stop this.
    > I appreciate your attempt to keep sticking to your point and trying to be serious
    > about it but... I just don't buy the IETF as the group of brilliant but tortured
    > souls who have "snarl" at each other to make themselves heard over the din of "Bad
    > Ideas".

    Well, again, I'm not even sure we're all talking about the same thing 
    when we use the word "snarling".   And while I'm pretty sure that we 
    need a way to push back on Bad Ideas, I'm not sure that what people are 
    calling "snarling" is only or even mostly about discouraging Bad 
    Ideas.   Maybe, for example, some of it is about "baggage" - old 
    resentments for hard-fought battles lost, perceived insults, or even 
    genuinely bad behavior.

    > Where is this apocalyptic horde of Bad Ideas that is sucking up all of our precious
    > resources?
    One doesn't have to look very far to find some, just follow ietf@ or any 
    of several mailing lists.   In theory at least, the situation would be 
    worse if we didn't try to discourage them.

RS> IMHO its already gone too far.  This whole thread is case in point. 

    > The IETF meetings are growing smaller. Clearly we have figured out how
    > to turn people away at the door.

RS> That’s easy ... the process has become way too complicated. The IETF has become what it always despised the ITU-T.   I would never take new work into the IETF and I was a WG chair for almost 10 years (RFC 6116 ENUM) .   Work on improving or fixing problems in Real Time Communications protocols in ART has stalled. Look at the DISPATCH list for instance. Other than WEBRTC the last useful thing ART did was STIR and even with that we had to re-form as a SDO outside the IETF with the ATIS/SIP Forum NNI TF to get the operational standards ready.  Snarling is definitely allowed there and encouraged in our TF.  

We backtracked Rich Call Data only after we had the documentation ready if for no other reasons to make sure it had enough eyeballs on it.  The savings in time and effort was enormous.  Our TF meets every single month.  

    With respect, it doesn't follow from just that information.  I'm sure we 
    have surveys which have shown that some people have stopped attending 
    because of what they perceived as rudeness, but there may be many more 
    reasons than that.

RS> Its not rudeness and IMHO rudeness has its place.  There is a whole lot of stupid out there. I've seen serious proposals about using Hyperledger for TN to URI translation. 

I cannot empathize enough the issues with  STIR/SHAKEN protocols is regulatory.  I spend a unique amount of time explaining S/S to an alphabet soup of national regulators. I could go on and on about that.  BTW based on my conversations most of us are well served by our national regulators and if ever offered to serve on a National or State Technical Advisory Committee do so. For those of you in the US write your Governor.  BTW the FCC has openings for CSRIC. You can self-nominate.  

https://www.fcc.gov/document/fcc-intends-re-establish-csric-and-solicits-membership-nominations

 It’s a very pleasant a rewarding experience.  I'm currently on the FCC NANC. 

BTW the surest way to get a protocol adopted is have it mandated by the relevant legislature which is what we did with S/S and the US TRACED Act.  You want BGP security ...mandate it.  

https://www.congress.gov/bill/116th-congress/senate-bill/151


    What is IETF doing these days that's exciting, that helps make the 
    Internet generally better in a way that's obvious to most participants, 
    that gives participants a sense of purpose and makes them proud to work 
    with IETF?   I don't think it's the null set, but it's certainly not 
    like it was 30 years ago when there was a general sense of excitement 
    about making this wonderful resource available to the world.

RS>  +1 Keith 

    In conversations with IETFers I often get a sense of futility, as in 
    "sure we could theoretically improve X, but we'd have to deal with these 
    technical constraints and/or these people and/or these Big Companies". 

RS> Well there are certainly constraints and "those people" namely the <fill in the blank> Mafia around certain protocols and certainly companies if you have to deal with routing protocols.  The largest single problem the IETF has now is what I refer to as the 'Persistence of Protocol'  Once something get imbedded in the network it is nearly impossible to extract or modify.  Professionally I've spent 30 years trying to kill off Time Division Multiplexing and Signaling System 7 in the Phone networks and it's still there.  I literally have to argue with regulators. "If you want real Calling Line Authentication S/S" Tell THEM to shut it F* off. Pick a date.  In the US we did that with Digital Television and made the US Treasury 40B richer when the spectrum was sold off. 
  
    There's a lot more inertia around many kinds of Internet development 
    than there used to be.   

RS> Keith its not  lack of inertia. Its Entropy.

https://en.wikipedia.org/wiki/Second_law_of_thermodynamics


It's probably not IETF's fault, so much as a 
    symptom of success.   But it has changed the landscape and how we feel 
    about our work.

    And yet, conditions have changed enough that the constraints around 
    deployment of new features in some applications protocols and some 
    layers of the stack may be less than they once were. Understanding where 
    we can make a positive difference may be as important as understanding 
    what limitations there are.

    Keith

RS> There are issues ISOC might be helpful in working with the general IETF community on some of these issues but I know they are extremely careful treading on areas that look like lobbying.  Realistically the IETF is not unlike any major SDO dealing with "essential" networks. The electric power people certainly are well organized. IEEE etc. EPRI.  IMHO we are being way way to idealistic about what we do. 

— 
Richard Shockey
Shockey Consulting LLC
Chairman of the Board SIP Forum
www.shockey.us
www.sipforum.org
richard<at>shockey.us
Skype-Linkedin-Facebook –Twitter  rshockey101