IETF Logo Mail Archive

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

Harlan Stenn <stenn@nwtime.org> Fri, 12 August 2022 09:24 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 D9814C159483 for <ntp@ietfa.amsl.com>; Fri, 12 Aug 2022 02:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.104
X-Spam-Level:
X-Spam-Status: No, score=-1.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 PSna0zFgBrS8 for <ntp@ietfa.amsl.com>; Fri, 12 Aug 2022 02:24:06 -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 40335C15C50A for <ntp@ietf.org>; Fri, 12 Aug 2022 02:23:57 -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 4M3ysn25SLzMP3M; Fri, 12 Aug 2022 09:23:57 +0000 (UTC)
Message-ID: <b0157386-8569-881c-170b-a73f42bafe15@nwtime.org>
Date: Fri, 12 Aug 2022 02:23:56 -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: Leif Johansson <leifj@mnt.se>
Cc: "Salz, Rich" <rsalz@akamai.com>, Miroslav Lichvar <mlichvar@redhat.com>, ntp@ietf.org
References: <67545c9a-3291-bbe6-c876-4c762c80c710@nwtime.org> <3F87A35A-A072-4ECC-94DA-BE9BA32B5CFD@mnt.se>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <3F87A35A-A072-4ECC-94DA-BE9BA32B5CFD@mnt.se>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/migyuyjxrwJRGauW_I_gDGoeksk>
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: Fri, 12 Aug 2022 09:24:16 -0000

On 8/12/2022 2:01 AM, Leif Johansson wrote:
>>
>> Most disturbing.
>>
>> Does anybody really think rough consensus will produce a high-quality result?
> 
> Since rough consensus and running code is THE central tenet of the IETF I’d say you are not only in the rough here but not even in the same zip-code as the fairway
The NTP Project has been delivering very well-running code for decades.

What's being discussed now may be rough consensus, but there is no 
running code for what's going on with the current proposals.

My comments are based on my experience with actual running code.

> Cheers Leif

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

v2.23.0 | Report a Bug | By Email