Re: RFC Series Editor Resignation

Hector Santos <hsantos@isdg.net> Sun, 07 July 2019 17:46 UTC

Return-Path: <hsantos@isdg.net>
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 BCCC91200B3 for <ietf@ietfa.amsl.com>; Sun, 7 Jul 2019 10:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=IZIyM0Wm; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=ekUHyLT0
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 jY9XrHl_TV0n for <ietf@ietfa.amsl.com>; Sun, 7 Jul 2019 10:46:24 -0700 (PDT)
Received: from mail.winserver.com (ntbbs.santronics.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id 979CF120043 for <ietf@ietf.org>; Sun, 7 Jul 2019 10:46:24 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4620; t=1562521577; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=S2pDXqJXA0fUGogdTDn6LXGvA+c=; b=IZIyM0WmdaT5d1SpRDNjjeIVZCc3SgNT5XiJT3rUmAz0kAlYLDWxOvtyX/oILN T0qBdn1AEnCDhkVICPEGSTnXcQs7pC17/p1s35FyKbQfsqHvfko7wOI/U3dcBlkL 4ePJ45Hxstbo1x3GNKXyNzgPfNOnqtlkDfv+J0ewpQMbU=
Received: by winserver.com (Wildcat! SMTP Router v8.0.454.8) for ietf@ietf.org; Sun, 07 Jul 2019 13:46:17 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v8.0.454.8) with ESMTP id 3313990954.1.2816; Sun, 07 Jul 2019 13:46:16 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4620; t=1562521327; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=tEYFCkG d6nm7G1AMWkd+A3Dx0wlzc5d0JkQPFpgMfGQ=; b=ekUHyLT0HIjRTq/LV8DcpJZ btinDv53RfnTdnQrXVVi/a76DYr+8fK3WHq0tx0RAetUWVn9hpNUFopQnzMsL4HL FXXZht537GTrXFpa+pEh5FjhemwY+56LchFXQgQpXu9ZCAxHlRAG2XKXWWpVB1pc hjQTR958o2XdEDlkKDX4=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.8) for ietf@ietf.org; Sun, 07 Jul 2019 13:42:07 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.8) with ESMTP id 591215380.9.315480; Sun, 07 Jul 2019 13:42:06 -0400
Message-ID: <5D222FE3.1030008@isdg.net>
Date: Sun, 07 Jul 2019 13:46:11 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, "Scott O. Bradner" <sob@sobco.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: RFC Series Editor Resignation
References: <34F6E9B8-2BC2-46AC-8AF8-EFDA552D659D@tzi.org> <EA13A490-2636-459F-919B-8A72F4F45174@cable.comcast.com> <df5a6b6c-d444-7e72-dd6c-e2fa844195fa@comcast.net> <20190628214503.GC30882@kduck.mit.edu> <7e5167bf-8167-bf81-981f-662d6da6f1ab@comcast.net> <20190628232206.GC10013@kduck.mit.edu> <e7bf71c3-7842-8699-1f56-36ffa823da99@comcast.net> <20190701223914.GK13810@kduck.mit.edu> <bad99f11-0d66-4aba-72ef-b4b648470753@comcast.net> <34A581FE-BCFA-4FDD-A626-372E036BD79A@cooperw.in> <20190703125524.GB98598@verdi> <B926E8F3-AC7C-4EF0-B433-82513723194A@sobco.com> <3EACBC3B-B559-45DF-B976-6F770096C9B5@cooperw.in> <882E56B9-636B-4E59-A497-DEE0A7F776A4@sobco.com> <m2lfxfun6j.wl-randy@psg.com>
In-Reply-To: <m2lfxfun6j.wl-randy@psg.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1ML6PvKX40T1lNNc5TTdPEVlTTE>
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: Sun, 07 Jul 2019 17:46:28 -0000

On 7/3/2019 11:56 AM, Randy Bush wrote:> [ just hitting reply to be in 
thread, not pointing at you, sob ]
>
> tom jennings (still a friend), the creator of fidonet[0],

Amazingly, Randy, I still have many die-hards using Fidonet frontends, 
mail and file gateways, virtualized over TCP. My Platinum Xpress (PX) 
and Wildcat! BBS are among the "Last of the Mohicans" with Fidonet 
capabilities.  http://www.santronics.com/products/pxpress


> was repeatedly
> pressured to make rules.  he eventually gave in and made two rules.  of
> course, they immediately became expanded by the embellishers, resulting
> in https://www.fidonet.org/policy4.txt, from which i quote
>
>    The FidoNet judicial philosophy can be summed up in two rules:
>
>       1) Thou shalt not excessively annoy others.
>
>       2) Thou shalt not be too easily annoyed.


Yes, as you remember, there was a weapon -- membership into the 
Fidonet nodelist.  Excommunications was possible.  There is also the 
technical compliance requirement. FTS-1 was a basic requirement for 
all the software during Zone Mail Hour.  I recall how this became an 
early contention and conflict with the FTSC and the then-modern 
internet developers who wanted to use the advanced internet-ready 
WAZOO protocol and not waste time with a dated protocol that did not 
work well under the packet switching network.  A sysop could be 
excommunicated for not using compliant software.

> mike asked solid and critical questions.  when not answered, he became a
> bit more strident.  as one to whisper twice and then nuke from orbit, i
> find it hard to fault him.  when the response is an attack on his tone,
> with no response to his question(s), and coming from two members of the
> iesg, i am alarmed and deeply saddened by an abuse (due to imbalance) of
> power in what is easily construed as an attempt to silence.

Unfortunately, this remains to be and don't see is changing.  The 
basic idea among the many IETF cogs is to allow "noise" (thread 
activity levels) decide what is relevant or when a "cog" will join the 
discussion.  There is also the "messenger" problem.  Depending on who 
delivers it, it can activate or kill mail I/O.   This remains to be a 
behavior with a number of well-respected, long time IETF "do-all" cogs 
who will ignore smaller participant postings until someone deemed more 
important replies, and to a large extent, almost always to "shut" it 
down.   There is also now the big elephant in the room, the "who you 
work for" guy - big vs small.  If you are from the bigger firm, 
increasingly with stronger, sponsorship ties to the IETF,  in my 
technical opinion, this has hurts what I long called "Cooperative 
Competition" where we design protocols common to all implementations 
at all scales and doesn't include technology that hurt or raise the 
barriers of entry for the smaller scales and implementations.  Today, 
cooperative competition is harder to achieve.  The IETF still helps 
keep the spirit, but in the end, the little guy is losing within the 
IETF.  I understand it is a battle. People will suggest the IETF 
monies spent needs to be allocated in a way that gets thing done. I 
read that a number of times stated when it comes to creating WG. 
Unfortunately, in my view, even if you are incline to follow a market 
leader, the quality of proposals are down and while the "Trickle Down" 
theories are nice, the realities are they don't quite work when the 
implementation cost are now much higher to even explore new ideas and 
methods used by the bigger firms.

> this is severely damaging the ietf and the internet.  please stop.  just
> stop.

In my opinion, the IETF does not benefit by the, for lack of a better 
term, "IETF Do-all" folks. They are certainly highly experienced, 
provide input, help complete, push, and to a growing extent  help 
"rammed down" lower quality documents as "proposed standards," but in 
my opinion, it comes with no major long term gain or benefits to the 
entire IETF community as a whole -- from hobbyist, small, mid to 
enterprises.  Newer participants quickly learn "who's who" and learn 
to pick their battles often leaving out concerns that may appear like 
you are rocking the boat.   Like now.

Today, many in the IETF are less tolerant are are quick to promote or 
seed the ideas of moderation and controls to shut down any form of 
contention or boat rocking.


> 0 - "FidoNet: technology, tools, and history," Communications of the ACM
>      Volume 36 Issue 8, August 1993.
>      https://archive.psg.com/930000.fidonet-acm.pdf

Never knew this document existed. :)

-- 
HLS