Re: Notification to list from IETF Moderators team

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 17 October 2022 03: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 8E4E7C14F74C for <ietf@ietfa.amsl.com>; Sun, 16 Oct 2022 20:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 qMPrfT1lvqI4 for <ietf@ietfa.amsl.com>; Sun, 16 Oct 2022 20:51:27 -0700 (PDT)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 6676CC14F749 for <ietf@ietf.org>; Sun, 16 Oct 2022 20:51:27 -0700 (PDT)
Received: by mail-wm1-x331.google.com with SMTP id y10so7878384wma.0 for <ietf@ietf.org>; Sun, 16 Oct 2022 20:51:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=J/bE9tiukhwQy8cXKwgK7QFan4Wf1KJ7hM//Rn9eCLc=; b=eG0g3vMIKcdKlAq+WZoDIsiOWjeZboi+RlQCYYCOQyNnJ/2757HZuv9iTKARX8rnXC Bk4KnoYe4wGg6Y+Da1xXLKVQI0gf8fmJXOI0KxJtMl9ftWNYg6CkLBm51ut6AHsHAqQD EsQ9mr0A7eDvuhwkhW/y9X95itzhSiNqEruf9n09smwy8yVW+cxZomgOXe+ofJupbZaE C50TlU0iDx6jWVpTjpUH9fI4RgdOTi1EB6mMfgJGlQaYuLxsMfkjj+MrraVNFaa0yE56 vdDZBo5SSEqLNf4v1PkuZhRjz+/cXAtcxnHDmRC75Xt0swoa1Wpj5KcgMNCXqwgXD2ac 4ChA==
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:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=J/bE9tiukhwQy8cXKwgK7QFan4Wf1KJ7hM//Rn9eCLc=; b=YzgCkyN8hYIwSURuhTzxh+PG0uB+BiGyup88FXgvw5Kp3OyAVSqMvNELiGznPaQL64 eN1KLN5+WtPH16aElGgR1WOe0cNC4xWuMB3lt/jJRHgTKFpY8pjkp1imQxD6pZYrvXUZ z1zmVk3NCts+DDRNwhR2RFpX4EMq6IY0io8Kz8lereXZowNjRpjW0OliMoUnFTKkoDHy 4Xkj0K6fg9Q+Yzf56pGswraM+TZ0FzJ1WXkEHkwNJTImT1LAPZFHkYBH2sv636og7ECv QEkOWIqaXfHfYQg6jWq7GBo7mckU/vSQOR9hro4OBax4YcctaIc2ADmo+co+hEpLI5Xh gKQQ==
X-Gm-Message-State: ACrzQf3mmfyIpGCGfv/vGjgDBZKDh48XCntz1BXyBwbBLj/Cg0rG2jyJ 7Ojn+nU6o8OXkBKSmArq7Gfy+RL/aOTd0J+ISJs=
X-Google-Smtp-Source: AMsMyM5xK2yNJRN/lKLqRszid0lYjiNpNuQBoroUBKCk9dSdyMJaQT7KbPhTeOddnIRxRnGHHqkRfJeR3u7WWtaKEBU=
X-Received: by 2002:a1c:2507:0:b0:3b3:3681:f774 with SMTP id l7-20020a1c2507000000b003b33681f774mr18107588wml.134.1665978684863; Sun, 16 Oct 2022 20:51:24 -0700 (PDT)
MIME-Version: 1.0
References: <4545ee83-1c56-4633-05f0-0576ac297884@ietf.org> <108e89fb-a9b9-e4ae-c217-d51ee1be598f@network-heretics.com> <43e94411-441e-93a1-8496-2f1d0a5af67c@gmail.com> <YwVjnrcbO7uUbXHg@husky> <0683a17d-a8c3-1819-d5ad-0eb8fee2421b@network-heretics.com> <29e213c2-5526-44c5-8e1d-74b24d946f7e@necom830.hpcl.titech.ac.jp> <Y0by/yiCnVxGbkU6@faui48e.informatik.uni-erlangen.de> <c6f11c6e-6f3a-76e9-bdfa-d84d15f3284a@necom830.hpcl.titech.ac.jp> <389D2392-E653-443A-A180-D2FA782237B2@staff.ietf.org> <0dac0694-73c1-edfb-47bd-0e41d25f0847@necom830.hpcl.titech.ac.jp> <18F8D177-C74A-44C9-991E-1EC05FC7771E@ietf.org> <588c7344-1ba4-5a76-3845-454cdf0a4c79@necom830.hpcl.titech.ac.jp> <CADnDZ8_-2oy3z_7TC+pQvOKFsjV24w+voKUK2gWv7KF7SrNs=Q@mail.gmail.com> <ECB1A65C-BFC1-4999-9240-BD3F66F3AD84@cisco.com>
In-Reply-To: <ECB1A65C-BFC1-4999-9240-BD3F66F3AD84@cisco.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 17 Oct 2022 05:55:20 +0200
Message-ID: <CADnDZ89YQ=SJYyFzjTdfp5f4LUJ9gr-C_9Z63CHjZVuszdnTCQ@mail.gmail.com>
Subject: Re: Notification to list from IETF Moderators team
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
Cc: IETF Community <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b6fb6805eb32e37f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/huwJE6Bf21VPBXniSAvcW6GHFOE>
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: Mon, 17 Oct 2022 03:51:29 -0000

On Sun, Oct 16, 2022 at 10:57 PM Eric Vyncke (evyncke) <evyncke=
40cisco.com@dmarc.ietf.org> wrote:

> > I don't agree to respect the funny RFCs which are issued in April a
> waste of time and effort, I will not call
> > it any word that makes me out of the list but it is very strange that
> some participants say it is IETF culture,
> > which I don't seem to know if IETF have defined what is its culture or
> defining motives for such funny-RFCs.
> > So I don't respect those RFCs because it does not title that it is a
> joke or drama,
> >
> > The reader needs to be respected, so the technology-producer, or
> document-producer needs to
> > respect/understand the Reader's interests, without making him feel bad.
> I discussed about this before, but maybe time will help,
>
> I would not call April 1st RFC as "culture", but it is indeed quite deep
> in the "folklore" and traditions of the IETF. It may be linked to the fact
> that April 1st jokes are told in my own country even on mainstream
> newspapers and TV channels, therefore I can understand that other IETF'ers
> do not find this funny. In this case, there are usually easy to spot (they
> are the only ones having a day in the publication date) to allow either a
> careful reading with a smile or to skip the reading.
>

Thanks for your input :-) and I enjoyed reading your documents because I
understood the Objectives before reading the documents' body.

Newspapers or TV channels are *Communication-Channels* with
Clear-Objectives (with clear Track, as some RFCs clarify
Informational/Standard)  to the country-community or the world but their
Output is *titled* as making knowledge or jokes or or test or other, they
usually make *Objectives* Clear as All respected English Writers/Speakers,
however, when we come for speaking (communicating with voice within low
noise) as Output it is maybe allowable to make separate jokes while
discussing serious objectives because the speaker will have signals by
voice without noise. In writing there should be a clear signal to reader
that a section of document is a joke and maybe best to clarify the
objective of joke if it was not easy to be clarified by a human.  In best
English writing they tell us to give the reader information of what will
you say before you say it then tell them what you just said as summary.

My objective of disagreement with IETF was in the IETF-Output which is
sending a RFC to the World using one communicating-channel to the World
Without clarifying the *Aim or Objectives* of such Output but only using a
*Date* to make such signal it was Joking ot Testing.

>
> The whole intent is to bring smile on several faces, not to waste time of
> course.
>

Yes all good people want that but by using principles of communication, and
there are differences between human-communication and machine-communication
which some people may be mistaken specially when they use technology within
their communication environment.


> -éric (author of RFC 5514 published on this very special date)
>

IMHO this RFC5514 is misleading the reader because it has not clarified the
real *Aim* of such document. We need to look into English *Writing
Principles* and into *Communication Principles* between writer and reader.
Those output from IETF are not doing a *good job* on that date and through
their life of communication as long some readers have low SNR within a
noisless-channel (the IETF is making the Noise).

>
> PS: I had more fun writing this useless RFC than for any of my other RFCs
> ;-)
>
> Yes it can be fun writing/reading any document only when all the readers
are within a defined environment and they are all known to the Writer, but
in future some other-environment-reader may not be having fun reading if
the written-document was not telling them in abstarct/title that it was a
joke or test.

Best Wishes,
AB