Re: [Ntp] Quick review of WGLC for status change for draft-ietf-ntp-update-registries

Harlan Stenn <stenn@nwtime.org> Thu, 11 August 2022 02:58 UTC

Return-Path: <stenn@nwtime.org>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5268C14F736 for <ntp@ietfa.amsl.com>; Wed, 10 Aug 2022 19:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.105
X-Spam-Level:
X-Spam-Status: No, score=-6.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 6QZha7jF6C0W for <ntp@ietfa.amsl.com>; Wed, 10 Aug 2022 19:58:25 -0700 (PDT)
Received: from chessie.everett.org (unknown [IPv6:2001:470:1:205::234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 DE8A3C14F692 for <ntp@ietf.org>; Wed, 10 Aug 2022 19:58:24 -0700 (PDT)
Received: from [10.208.75.149] (071-084-168-128.res.spectrum.com [71.84.168.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4M3BMM4JQhzMP4C; Thu, 11 Aug 2022 02:58:23 +0000 (UTC)
Message-ID: <4fdc026f-c44a-cea7-d284-ad97eb5baa3a@nwtime.org>
Date: Wed, 10 Aug 2022 19:58:23 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: Karen ODonoghue <kodonog@pobox.com>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, ntp@ietf.org
References: <PH0PR06MB7061FA7A5B338D262B3A2963C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <6a187a2f-9883-2fb5-1f51-1593591ddebb@nwtime.org> <PH0PR06MB706126984E4442EF32F8242AC2999@PH0PR06MB7061.namprd06.prod.outlook.com> <da155c84-2c70-2e3b-59eb-03e380806cf2@nwtime.org> <PH0PR06MB70611F2331D8255F7E2B6604C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <0b4c7efa-3977-b588-0974-33b6a9437e52@nwtime.org> <YvDWC27qKnODlD52@localhost> <0b57b7db-772e-f5e6-e6a0-a433673f3d77@nwtime.org> <YvED7T5R0UsRWbv3@localhost> <b64c6a0a-ea2e-0a19-4bb9-38bfaa2e5032@nwtime.org> <CA+mgmiO9YimJ=+huw59F+1BtOE5dor5fxWdcWgSS4FsNLTKO1g@mail.gmail.com>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <CA+mgmiO9YimJ=+huw59F+1BtOE5dor5fxWdcWgSS4FsNLTKO1g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/bBu4cTj0KH-TRZ_8kZ5x00rF888>
Subject: Re: [Ntp] Quick review of WGLC for status change for draft-ietf-ntp-update-registries
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2022 02:58:29 -0000

Karen,

On 8/10/2022 3:10 PM, Karen ODonoghue wrote:
> Harlan,
> 
> Your statement quoted below is completely false. I have always and 
> continue to welcome comments and contributions from you. I think the 
> working group and the NTP community would benefit from your constructive 
> engagement. We had this same conversation in a private conversation in 
> 2020, and I responded in a private email to you to correct your 
> misconceptions. I have quoted part of that email to you below.

You and I remember the conversation you had with me when you told me all 
my proposals had been dropped differently.

I also said this to you in our conversation in 2020.

I will take you at your word that y'all are interested in constructive 
engagement from me.

H
--
> On Mon, Aug 8, 2022 at 9:46 PM Harlan Stenn <stenn@nwtime.org 
> <mailto:stenn@nwtime.org>> wrote:
> 
>     On 8/8/2022 5:39 AM, Miroslav Lichvar wrote:
>      > On Mon, Aug 08, 2022 at 03:35:40AM -0700, Harlan Stenn wrote:
> 
>     Karen told me the WG consensus was to drop all my proposals, and
>     further
>     informed me that future submissions from me would not be considered.
> 
>     I have no plans to pursue my proposals via the Standards track of the
>     WG, or perhaps thru the WG at all.
> 
> 
> ********* below is quoted directly from a private email exchange with 
> Harlan on 26 August 2020 **********
> 
> Having said that, you are clearly misrepresenting what I said on that 
> phone call. This is the same thing that I have said to you many many 
> times over the course of several years as I tried to help you progress 
> documents in the IETF.
> 
> Specifically what I said was that there was no working group consensus 
> to adopt your extension field draft. In fact, the working group was all 
> opposed except for you. 
> (https://tools.ietf.org/html/draft-stenn-ntp-extension-fields-09 
> <https://tools.ietf.org/html/draft-stenn-ntp-extension-fields-09>)
> Several of us including myself and Sam Weiler tried to work with you to 
> help you gather support for this document, but we were not successful. 
> In this (unadopted) document you wanted to make changes to RFC 7822 
> (https://tools.ietf.org/html/rfc7822 
> <https://tools.ietf.org/html/rfc7822>) because you didn't agree with the 
> clarifications made by that RFC (changes which you agreed to at the time 
> of publication). My point to you was that the document was dead in the 
> working group unless you got other members of the working group to 
> support it. I also said that any of your extension field drafts that 
> relied on your extension field update would not be able to progress. Any 
> extension field draft that accepted the RFC 8722 extension field 
> clarification could progress provided there was working group support.
> 
> So, in summary, I NEVER told you that I "would not advance *any* future 
> Standards track proposals" or  "*any* future Informational track 
> proposals" from you. This is absolutely FALSE.
> 
> What I told is that you need to work collaboratively with the working 
> group and get working group consensus to progress working group 
> documents. As working group co-chair, all I am doing is trying to 
> determine consensus. You are very much welcome to contribute, and I am 
> happy to help shepherd documents authored by you. However, I don't make 
> decisions. I measure the consensus of the working group.

-- 
Harlan Stenn <stenn@nwtime.org>
http://networktimefoundation.org - be a member!