Re: Bad/Good ideas and damage control by experienced participants

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 17 June 2022 21:25 UTC

Return-Path: <hallam@gmail.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 DAE77C14CF0A for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2022 14:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.408
X-Spam-Level:
X-Spam-Status: No, score=-1.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dh3AKBIg8h7V for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2022 14:25:45 -0700 (PDT)
Received: from mail-yw1-f169.google.com (mail-yw1-f169.google.com [209.85.128.169]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4F1EC14F72D for <ietf@ietf.org>; Fri, 17 Jun 2022 14:25:45 -0700 (PDT)
Received: by mail-yw1-f169.google.com with SMTP id 00721157ae682-3176b6ed923so53587777b3.11 for <ietf@ietf.org>; Fri, 17 Jun 2022 14:25:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8OlJMbNIU9Q6iZflI5YkSg7yFDuub81EqyD0B83Mjvw=; b=sUyGNw9XBsK1IQBchnQ2qHigRnY/fYqOPLhWDXNcBsaAF51kgR29A1KVRwxNBl0LpP pAVJKWH/TVjdUtFvef6rQBVXjz/JUvlrucqSXdStXWCGObTrIWiXgcKO+AcH5/v0szUI GQuSKBLSaAVCEupBlsGy94fixJz2dGAYRbtbWcQ9erORVk7YdipAm5wAvv0WtOSkeEZa Z/eQ+udXf0j4K6ajH1j8/XQE56PFOKcDLNTOsSM8mk/Jq7LzXIgtAxt1NI/8SVLAgjl/ qt28Pe1dbxdKrP4OpV785IFYuh/bmSrzzzLgM7j1r4qFxi8Vi/eudbUhaxdPFVJ0UUjm Km2Q==
X-Gm-Message-State: AJIora+Ju797vvnjYS1A0bxoagVG2AYFHzzlZpJ7giZba1U8qsnA7bjM L/iQx2VBhZ6lQoDiqlgV85im89/nzgjUMqGH2LkdtIKSEn4=
X-Google-Smtp-Source: AGRyM1vUlOBp7plobW1SUmzEdFlJmq07CrW1oOEtKIKrA9FoB0u41EKVMekNqn9EUf9KgDnWgQYt2fADU+ON70rVsKU=
X-Received: by 2002:a81:48cc:0:b0:317:4d57:8732 with SMTP id v195-20020a8148cc000000b003174d578732mr14154346ywa.217.1655501144693; Fri, 17 Jun 2022 14:25:44 -0700 (PDT)
MIME-Version: 1.0
References: <20220614144751.97882437791D@ary.local> <cf6d63e8-aebc-9c2a-1137-96c3d1c86570@gmail.com>
In-Reply-To: <cf6d63e8-aebc-9c2a-1137-96c3d1c86570@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 17 Jun 2022 17:25:33 -0400
Message-ID: <CAMm+LwgkL2hB4ssSHZQcMzRpkJMukNjpxys1b3o0s31CuJzp6A@mail.gmail.com>
Subject: Re: Bad/Good ideas and damage control by experienced participants
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a79e2205e1ab65b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ggjJzoEDFIgUzcZd6MhksT3bxHk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Jun 2022 21:25:47 -0000

On Tue, Jun 14, 2022 at 4:38 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 15-Jun-22 02:47, John Levine wrote:
> > It appears that Miles Fidelman  <mfidelman@meetinghouse.net> said:
> >> On the other hand, is it really a negative when someone is snarky with a
> >> snot-nosed kid who doesn't appreciate being told that their "great new
> >> idea" is a retread of something folks learned not to do decades ago?
> >
> > Depends.  If your goal is to make sure nobody new ever comes to the
> IETF, sure, do that.
> >
> > On the other hand, if someone new goes to the effort to write up an I-D
> and ask us
> > to look at it, there are a lot better ways to see if you can redirect
> their interest
> > to something that might be useful.  Sometimes they may go off in a sulk,
> but sometimes
> > a little politeness and specific references to prior work they should
> read about can
> > go a long way.
>
> I think it is also a very effective sieve. Newcomers who respond positively
> to this are much more likely to become genuine contributors than people
> who won't listen and learn. The ones who don't listen are unlikely to
> succeed anyway.


That is completely wrong. I could not disagree more emphatically.

Miles' premise is utterly wrong.

Most ideas are relevant to a very specific time and not always the one in
which they were proposed. Sometimes the solution to a problem came up long
before the problem was recognized. And that makes it very difficult to get
attention for that particular approach in academic circles because careers
are built finding new bright shiny objects, the realization that the
solution to the critical problem of today was discovered 20 years ago does
not usually bring offers of tenure.

Most systems are the result of a set of compromises. The fact that X was
considered and rejected 20 years ago because Y isn't a major concern is a
poor argument for rejecting X now that Y has become a major problem.

I don't think that anyone is doing anyone else a service by driving away
anyone who dares question the sacred principles of IETF protocols. The
IETF's biggest problem has been group think for a very long time.