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

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 18 June 2022 10:03 UTC

Return-Path: <abdussalambaryun@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 6591AC14F74A for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2022 03:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPsOdD2udEJl for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2022 03:03:25 -0700 (PDT)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 BA905C14F693 for <ietf@ietf.org>; Sat, 18 Jun 2022 03:03:25 -0700 (PDT)
Received: by mail-wr1-x433.google.com with SMTP id n1so8270007wrg.12 for <ietf@ietf.org>; Sat, 18 Jun 2022 03:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qJSM4NsAC+6aR9dA5sHvoNTYzteLy1OSNHqQhZ2Gpnc=; b=Rrj380ZN7eizVIFpMcumEc7hbcBDe+1UgLrv1BT9toSCClnte5oSQnRvVuxo5FQdyG weH31UzH8yW5jTUDWpkm59cYKuRJeTnaKEEM4+DX2P5Ldl24jKXrm7AzMZwL2tvBjIPg CMm2szzgeU5abIbb2RObRAcL0siX35g9OXLjl65DuZGSovxzOw9aAoaqQJXBs/Gu6X4e jzvXX2vBv5zPzjaofru1t5BZdiWrZHc802LRohicEH001OSLNKoLmuQnrHpglWss8Exw hbObaES/iuTW99QsaP3L3a5BqoYbNS7eJYL3cJk04el/PpESuXvu03isPDA5AKeYUdQq sgdQ==
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=qJSM4NsAC+6aR9dA5sHvoNTYzteLy1OSNHqQhZ2Gpnc=; b=1wgHN3DEtt40zn8zlBoVaCcz5GkuKaECkBC8oiDzVeVMfbArv7egyAt6bPdhAtnjSi l0/bfjZw1zxwI9tTO9bsVV2kRvaGHLjKEWzC9YIrIxr9xhBBiFWcAbZmSLGfvF7rj1M+ k0y9dPx21xCtPwda7Ammwl/OCDMpcQff6Vv4rlZGlgIDB4/VmQ5V1pnYcvvU8hqVNpGr qS0L9DaMq4Ao6CHt5b6NfYIFXjcVwhupgygv859p2n1GG7xJTpRdYNVwl4YzAYpd0zrd eMhKyZED7AJd2mRw0F+Na3PRhwuOYDr7VLfJ8SGrCROzMiYbNXsA/XwhofpZX6JHl3Sh qNkA==
X-Gm-Message-State: AJIora9qplhjQgrjqDmFqm5BIzrQJ4H6jV9Rq1eKf819lfeIh5n59vUU KuY6TvQ4sU1/nZOK8oCV/bOan2AGZ3EjtdZTPiY=
X-Google-Smtp-Source: AGRyM1siitZB4mCObPbg/uOHCVQ2NhPdy7+BTbJyHOQS9G3G0YwQt9Jbh+bKk+uy9/LE0aC2lTFBKhb7eQwey6N4fhg=
X-Received: by 2002:a5d:4a49:0:b0:21a:3740:454e with SMTP id v9-20020a5d4a49000000b0021a3740454emr11341489wrs.322.1655546604154; Sat, 18 Jun 2022 03:03:24 -0700 (PDT)
MIME-Version: 1.0
References: <20220614144751.97882437791D@ary.local> <cf6d63e8-aebc-9c2a-1137-96c3d1c86570@gmail.com> <CAMm+LwgkL2hB4ssSHZQcMzRpkJMukNjpxys1b3o0s31CuJzp6A@mail.gmail.com>
In-Reply-To: <CAMm+LwgkL2hB4ssSHZQcMzRpkJMukNjpxys1b3o0s31CuJzp6A@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Sat, 18 Jun 2022 11:53:03 +0200
Message-ID: <CADnDZ8_=8-+vSRU1ENH70gr6XEbo=vNsuZPo74UCpzXaCsoYOQ@mail.gmail.com>
Subject: Re: Bad/Good ideas and damage control by experienced participants
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003ff44d05e1b5fb79"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-Xa1-2_yeTY4PgnWF1pvrwY3hKk>
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: Sat, 18 Jun 2022 10:03:26 -0000

On Fri, Jun 17, 2022 at 11:26 PM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

>
>
> 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.
>

IMHO the biggest problem of IETF's WGs is that adopted works are not
discussed Good/Well within the WG, discussed Well should mean involving all
(i.e. old or new community-comer) and responding to all questions and
should be proving valid ideas/usecase/references to the community with
good-reasons/good-language. The WG chair must work to get all questions
answered to adopted work, because IETF is adopting the uncomplete work, to
make adopted work complete its evaluate process (should be done involving
new comers with their fresh ideas and fresh arguments).

IETF should make it clear to long term workers that they need to complete
work within the world community that USE internet, that is why internet is
important because it is Used by ALL, so then the principle of IETF is to
involve ALL without ignoring new people/questions/comments.

As some say in IETF is does not hurt to be nice (especially when someone is
the author/chair/editor of an adopted work and wants it to be completing
the ietf-process in Good behavior/feeling for all)

AB