Re: New proposal/New SOW comment period (off-topic)

S Moonesamy <sm+ietf@elandsys.com> Sat, 28 September 2019 18:51 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 B2B34120025 for <ietf@ietfa.amsl.com>; Sat, 28 Sep 2019 11:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 T87k40SFZLcB for <ietf@ietfa.amsl.com>; Sat, 28 Sep 2019 11:51:35 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFE5120019 for <ietf@ietf.org>; Sat, 28 Sep 2019 11:51:35 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.155.140]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8SIpMxr004520 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Sep 2019 11:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1569696694; x=1569783094; i=@elandsys.com; bh=a4l6j/R83lEdTqCfjbjEfB5NmPN+bVeghPT+B++M/tg=; h=Date:To:From:Subject:In-Reply-To:References; b=CdZKHtewEueXMQI+Fm5/ClsbjG4t2KXO8rsAW+IhF4Xo/WmrULJzGIweZ32zG0tLE ZKKTc09rqJRP0xY4k6X7sVhxZ5fGXWArpYuoM4jm+1ejOU/XWkNeO5tI9bOg4fk70Y 1+hHAfsciC04OKCIqeh5EfMlXb/e+FYFPu6nn78I=
Message-Id: <6.2.5.6.2.20190928091638.11d8e8e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 28 Sep 2019 11:50:52 -0700
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: New proposal/New SOW comment period (off-topic)
In-Reply-To: <5364B34FDA8C34FA6A7E2570@PSB>
References: <394203C8F4EF044AA616736F@PSB> <E0AA9720-A0BF-486C-AFD6-0675FDF1D0A3@encrypted.net> <5364B34FDA8C34FA6A7E2570@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c3sHdOWWJpxo8gfmTI2UjP2Th5Q>
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: Sat, 28 Sep 2019 18:51:37 -0000

Hi John,
At 03:21 PM 27-09-2019, John C Klensin wrote:
>Others have commented about part of this.   Your line of
>reasoning above essentially makes a call for community comments
>useless because someone (or a committee, board, or other group)
>can always say "we made a proposal, there wasn't very clear and
>obvious support for something else, and therefore we are going
>with our proposal".  A few years ago I would have argued this
>was unnecessary, but it may be time that the IETF considers a
>rule that, if a proposal originates with a given body, that body
>is not allowed to be the determiner of consensus on that
>proposal or alternatives to it.

I am not commenting about the line of reasoning as I switched to 
other stuff instead of paying attention to the thread.  I'll comment 
on the call for comments aspect instead.  It could be classified as a 
public consultation.  There is usually low engagement from the public 
if the consultation is not viewed as useful or if there is a 
perception that the consultation is being used to gain automatic 
approval.  The consequences is that it becomes very difficult to 
identify problems which the committee or board did not think about or 
devise solutions which will have some positive impact.  At some 
point, it can create a disconnect between the committee or board, and 
the public.

It is not pleasant to receive (negative) criticism.  However, it is 
better for an entity not to prohibit that, whether it is directly or 
indirectly, if it wishes to be open to public scrutiny.

It is rather unfortunate that the IESG has been unable to steer the 
various discussions over the years.  I'll take that into 
consideration in saying that I would not blame a Security Area 
Director for an action which he/she took.  My guess is that there is 
some backend messaging which lead to that.

On a somewhat unrelated note, it is likely that there is a a rift in 
the community since around 2017.  It is not possible to tackle that 
as long as there are entrenched views on either side.

Regards,
S. Moonesamy