Re: Terminology discussion threads (off-topic)

S Moonesamy <sm+ietf@elandsys.com> Sun, 16 August 2020 00:34 UTC

Return-Path: <sm@elandsys.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 68B143A0B4F for <ietf@ietfa.amsl.com>; Sat, 15 Aug 2020 17:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 Axos9D14CWSx for <ietf@ietfa.amsl.com>; Sat, 15 Aug 2020 17:34:47 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8583A0B4D for <ietf@ietf.org>; Sat, 15 Aug 2020 17:34:43 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.189.14]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 07G0YT1L004069 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Aug 2020 17:34:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1597538082; x=1597624482; i=@elandsys.com; bh=+GfZ0L/AuFvL3BnSBtVRvrdSUp85H0Eh2/LSL/mu+kA=; h=Date:To:From:Subject:In-Reply-To:References; b=d4C6UvI67FRwQdr7DoswvXPmCqMN39WeaKCxNAykTOY20g3zUB6yf2R4bkeqQL075 cLgWLLXJMBw1ypKcXF8UgccCG1HUMduuEm/Rq3sCqNVEGYEmVJOWBqwQdnIJNI6oxu 696AN0frMV6PrFIRw1LF4q9WPxrPTKvqwE2gXikE=
Message-Id: <6.2.5.6.2.20200815135529.0af0c950@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 15 Aug 2020 17:33:18 -0700
To: Benjamin Kaduk <kaduk@mit.edu>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Terminology discussion threads (off-topic)
In-Reply-To: <20200815172255.GR92412@kduck.mit.edu>
References: <6AA0BCBB-D95B-4036-B94D-5E79E7B94D75@ietf.org> <F15E387D-9FDC-4A76-8002-78B85F6D16BE@nohats.ca> <CABcZeBNitWbdPO4Y2WfCzjy10Z+s27px6cGT1uRHmtGHa5iX+Q@mail.gmail.com> <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net> <20200814174247.GH92412@kduck.mit.edu> <6.2.5.6.2.20200814133128.07dfe1f8@elandnews.com> <20200815172255.GR92412@kduck.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sEa3qmUdM6iRxFD7LLhB23SYQho>
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, 16 Aug 2020 00:34:49 -0000

Hi Ben,
At 10:22 AM 15-08-2020, Benjamin Kaduk wrote:
>When you say "it was never implemented", is that RFC 6729 itself, or
>specifically the "written for this mailing list" part?

There was a message which did not make it to this mailing list.  The 
matter was discussed on this mailing list and the authors wrote the 
RFC to capture the proposed solution as a specification (RFC).  I 
meant that the specification was never implemented by the IETF.

>I'm not entirely sure what value eliding the word in question is supposed
>to provide?  I assume that it is "thick-skinned" but I am only guessing.

Your guess is correct.  There are words which I prefer not to use.  I 
would not prevent you or anyone else from using them.

>I also don't understand the reference to RFC 7154 being a rewrite to address
>the "unpleasantness" part, as "unpleasant" does not appear in the diff from
>RFC 3184 to RFC 7154
>(https://tools.ietf.org/rfcdiff?url2=rfc7154&url1=rfc3184), nor does the
>string "pleasant".

It was well-known that there was a "conduct" issue in the IETF.  One 
of the objectives of the rewrite was to provide an opportunity to 
anyone who disagrees with the document to ask for changes to it.  As 
an example, if you (used in general terms) were of the opinion that 
the guidelines should allow unpleasantness, you could have proposed 
that.  If that was the consensus, it would have been added into the document.

You won't find any of the two words as the thoughts are expressed 
through the sentences and informational references in that RFC.  The 
IESG can determine, as part of an IESG review, whether your messages 
constitute a breach of RFC 7154 if that the matter gets to that stage.

>Could you also clarify what you mean by "the new role option was tested
>previously"?  The referened message indicates that there had been a
>proposal for a new "facilitator" role, but I did not see or recall any
>attempt to actually try out someone in that role.  Perhaps you mean that it
>has been discussed previously but not attempted due to the results of that
>discussion?

Sorry, I must have chosen the wrong message.  The message in 2016 
announcing the experiment is at 
https://mailarchive.ietf.org/arch/msg/ietf-announce/nQ-7XIKdLHvYlntNn7RB5gtnT3Q/ 
The experiment was concluded about a year after that; the results 
were viewed as a failure.

>The formatting suggests that these are intended to be "your idea here"

Yes.

>proposals for what the IETF might do, but they mostly seem to be statements
>relevant for general background as opposed to proposed actions; am I
>missing something?

Some of the ideas could be formalized after discussion.  Going 
directly to actions [1] could cause "process" violations.

Regards,
S. Moonesamy

1. Within the context of this exchange, I do not consider publishing 
a document as an action.