Sensing what is Right (was Re: BCP 83 PR actions and new media

Abdussalam Baryun <abdussalambaryun@gmail.com> Wed, 16 November 2022 10:51 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 9BB51C15791D for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2022 02:51:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RRqDPDHM5UBs for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2022 02:51:29 -0800 (PST)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 A881DC15791C for <ietf@ietf.org>; Wed, 16 Nov 2022 02:51:29 -0800 (PST)
Received: by mail-lj1-x234.google.com with SMTP id h12so21310126ljg.9 for <ietf@ietf.org>; Wed, 16 Nov 2022 02:51:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=TH+w1RAs91IHeFzxszdHULt3+OyFkPN3VWWSNTXahCA=; b=EmZ1VRf/GXGYyv7WUKEA+lNLJJdKI/sY3Da5abNX8LsHKRhsppD5N3Nzv8M+x/zf1+ q+9oP6caES27AqUitWf4Zffng/y6YtG/G/4EnehnPMRwtlSJv0Zs1xuLnaEDsAX8pNYG SENW0618abvOSvhT7OKrnVwLt7caOnt2dcT5hsaxMX9WO6FDcreuF/UNu1e22/wZgCib nnF+4o2z2mlhkH8L2g/o+cc20RpAJJEax5zmXF5g6Ja2Tmts8R2HgUxnF6+JJ7gYi9mq okCYyZRULpFOzQbSltHrSfDDwZ8hbjhCY48OraPNccXIORgOPOPsbg/ELk7KP4xwie9C kxjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=TH+w1RAs91IHeFzxszdHULt3+OyFkPN3VWWSNTXahCA=; b=o7fCmurVxlTWVFh67yBQTQ8kmHL5R4/u3ir8qtjI3G7C7/bslK4jPh2IYOPBVpCq2o 1xojJ5DyibnpOEvu96kn3+z9xxZShWbpyf9NrAU9NFH96k3SEKcSbPsIo8nrUKdO3q5r gVU27mnxaD4uSaWuyBnWDXgCPFbkbPUrwofGFFemBRIAXAlkfdJmXmKeY2+xQW0qJPN4 pUQkSZptD1FuCJyeyCcKXvZriOiCN5kVl3Mm/M/g49R3ccgKNqu4ftwyfdYHmUrSQDVy x4+pbY1jA/724PpCsS+vfSqoui0WNbW3zPahW9sGIh1mtD+iTl7lrbL5y/IRG+30tVWr deXw==
X-Gm-Message-State: ANoB5pk633AF02HuBUYdcOPr6eRCaqeSN/3NEt2p4cJQQHuU6+Pipdir c9a2YNTP4CYu9zqt+gtcYP0EwJcJaS/0/eac/L9UTDQiZgdeFA==
X-Google-Smtp-Source: AA0mqf6nc17RljlduR6c26NtFZnUusFp5THjjpEgaYUjKZg+DKbAWV6uBc9jzJkycc7fEQlB6AImUD1eAmn12HJHq40=
X-Received: by 2002:a05:651c:1197:b0:277:4150:b560 with SMTP id w23-20020a05651c119700b002774150b560mr8143725ljo.299.1668595887186; Wed, 16 Nov 2022 02:51:27 -0800 (PST)
MIME-Version: 1.0
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Wed, 16 Nov 2022 12:54:07 +0200
Message-ID: <CADnDZ88sQ3bTc7A1CpsdQg0ykGzHYj+_M1Hww8-265uGr9GT_w@mail.gmail.com>
Subject: Sensing what is Right (was Re: BCP 83 PR actions and new media
To: Keith Moore <moore@network-heretics.com>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000021275d05ed944156"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qWebHWwK7hlmvoAUsmbjq3FXn2A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Wed, 16 Nov 2022 10:51:33 -0000

Hi Keith,

(sorry if this message was long but I think it covers my position on the
subject)

Firstly, I thank you very much for your discussions related to BCP 83 and I
really enjoy discussing with you and hope you have same feelings. So I am
discussing from Africa Region and I think you are discussing from America
Region, we may have different traditions but I believe we have the same
common sense and both we want a progress in the subject under discussion. I
believe it is a communication_principle that ietf_participants involved in
one work_subject SHOULD have similar/common objectives to progress in work.

Secondly, there is no doubt that Organisation_Experts have strong sense of
what is Right and strong sensing what is Wrong, also experience sensing
what is Good, Bad and Ugly within IETF Communications and
Computing/Analysing of Informations. Sensing is very important in making
humans and things more intelligent in actions, reactions and interactions.
Furthermore, having common abilities make communications more cooperative.
Therefore, IMHO if all participants within any IETF WG have
common_sense_ability_and_objective then they can be more working progress
and more cooperative. As Jack Ma said once about AI and Quality of life: "I
always tell myself that we are born here not to work, but to enjoy life. We
are here to make things better for one another."

Also our IETF RFC technologies, always depends on that both
communication/computing ends need to be having the same protocol in common,
so IMHO, it is very principle engineering to have common sensing protocol,
and common communication protocol so we can have cooperative results. In
one important work [1] it looks into IETF decision makings of
IETF_business_work and I think concluded that we need
cooperative discussions within IETF decision_makings. So I am one that
believes that All IETF discussions needs cooperative parties in
IETF_directors, IETF_participants, IETF_rfc_authors and among all. More
comments below,

On Sat, Nov 12, 2022 at 3:52 PM Keith Moore <moore@network-heretics.com>
wrote:

> On 11/12/22 02:50, Abdussalam Baryun wrote:
>
> > I agree, however, there may no need to be clear on common things about
> > good/ugly communications, because it is depending on either common
> > sense (human_group sense) or what is usually done in family/social
> > organisations.
>
> As far as I can tell, "common sense" is one of those phrases that people
> use to argue for some position that they do not know how to support.


My meaning of *common sense*  is human_management_common_sense to make
Right Decision_Makings to such continuous behavior (i.e. as human have same
sensing of voices, image, etc.). This BCP or this RFC_use_case is related
to management to use, and not society_individuals to use, so I think our
discussion can be scoped more on the IETF managerial common sense of
Managing Human_Organisation's inter_communications and not participants'
common sense.


> It reflects a presumption that everyone else thinks, or should think,
> like the speaker thinks.
>

This BCP was produced by the society and not produced by the management of
IETF, so the policy_speaker is the human_society of this IETF organisation.
Furthermore, the IETF_society is choosing their managers not the other
way around as some organisations do, so our management's common sense will
consider that as well. There is no doubt that the IETF_society is selecting
their IETF_Best_Experts and Best_Available. Therefore, I think if I
understood you the words *the Speaker_thinks* can be pointed at the IESG,
so my reply is that they SHOULD be the best_ietf_experts otherwise we MUST
blame the IETF_Society of no courage of talking/speaking.

My argument's important phrase_objectives are  *Social_Organisation* and
*Managerial_Cooperation*, then within that organisation we already get to
know/sense what is normal/good and what is not normal. All
Human_Organisation_Managers build a common sense of what is right and what
is wrong from experience within their organisations (they may also build
common traditions). There are many business books analysed the organisation
behavior and show important of Human_Management decisions for business and
progress (I think our Research Groups have been doing some work in that
direction). IETF is doing important internet_business as we know and maybe
lagging in following up the world's technology evolution.

Reality is that different people are exposed to widely different
> conditions and experiences in life, and different people
>

Yes, that is why we need management/group_directors/IESG to have time to
look into that reality which is very complicated when we deal with humans
and interactions among_humans. Also *Reality* is the IT market/business
that needs new standards to follow the developments and there are
work_management process issues and research done for IETF organisation
which needs to be understood/considered by all IETF society participants
[1].


> Reality is that different people are exposed to widely different
> conditions and experiences in life, and different people are born with
> different personalities and values, so each person develops their own
> sense of the bounds of propriety.   To some extent these things are
> reinforced by other people, but not entirely so.   And such
> reinforcement is often harmful, for example, in that it can serve to
> protect abusive practices or individuals.
>

IETF already produced this Best Current Practice, so are you against it,
because my discussion/argument is not about amending or changing this BCP,
but my discussion is about how to use it now, and I think you are doing the
same. My discussion is not against having IESG deciding to use this BCP or
not, but maybe I think you are doing that. So my reply is a question: Do
you want this IETF organisation without rules/group_management that
controls posting of special_attacks? Do you want society_individuals free
to disrupt the IETF_process with no sense of control or with no
management_interference?

>
> No abusive practice that's tolerated by society, and no mistaken notion
> of how the world works, ever gets changed without some individuals
> having the courage to violate "common sense" ideas of propriety.
>

IMHO, to make our ietf_organisation simple, there are two courage_planes in
the IETF_human_Organisation, one is Working_Plane and the other is
Control_plane, so I am interested to first discuss Control_plane then
Working_plane, and don't want to mix them. Some discussion mix and some
separate, but this IETF_BCP is about separation so it is better to separate
so we get into discussion_progress results. However, we have other level of
controls within IETF_work_process but IMHO this BCP_action is not about
those.

In addition, The IESG will always give chance to societies
courage/new_ideas to discuss and find consensus within society so the
societies common sense is heard before IESG decision, on the other hand the
manager's common sense is important to make the possible_initiation of this
BCP_action and asking for the societies_consensus, then the IESG's common
sense decision making come into discussion among ietf_society_directors.

Finally, the ietf_society can be more clear for the working_plane, if they
think they need more clear definitions of what is good/ugly
human_communication/behavior on the IETF_environments, then it is better to
have another RFC that is related to Working_Plane and not Control_Plane,
within the IETF_Organisation, so we can be simple, sensitive and clear.

Best Wishes,
AB

[1] https://mailarchive.ietf.org/arch/msg/ietf/7iccMwdInLz1WQTr8xQzqExZWdU/