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

Harlan Stenn <stenn@nwtime.org> Tue, 09 August 2022 02:03 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 37E5FC14F72D for <ntp@ietfa.amsl.com>; Mon, 8 Aug 2022 19:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 VwQ2rZVrM0A3 for <ntp@ietfa.amsl.com>; Mon, 8 Aug 2022 19:03:32 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.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 0B620C14F727 for <ntp@ietf.org>; Mon, 8 Aug 2022 19:03:32 -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) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4M1xDz5JWlzMP5L; Tue, 9 Aug 2022 02:03:31 +0000 (UTC)
Message-ID: <434fa060-bf66-5faf-837f-c50a6f3073f7@nwtime.org>
Date: Mon, 08 Aug 2022 19:03:30 -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: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ntp@ietf.org" <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> <62F0EE62020000A10004C2F7@gwsmtp.uni-regensburg.de> <c3820711-4a3e-564a-5d51-5b5683de1e2f@nwtime.org> <DE69E944-6150-4861-B066-00EEDC1932DC@akamai.com>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <DE69E944-6150-4861-B066-00EEDC1932DC@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/DVO7yzGq-batnELYnaS1HBsjbW4>
Subject: Re: [Ntp] Antw: [EXT] Re: 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: Tue, 09 Aug 2022 02:03:36 -0000


On 8/8/2022 8:04 AM, Salz, Rich wrote:
>>     Please tell me if your experimental playground is private or on the
>>     public internet.
> 
> People can put things on the Internet without asking permission.  That's one of its fundamental tenets. A large company may wish to experiment with an NTP extension (e.g., QUIC checksum complement?) and only has to be concerned that their experiment will not conflict with other people's experiments, or standard extensions. Perhaps you don’t know that this happens very often with HTTP and email, often via "X-" headers (as Ulrich said). It also happens with DNS (new RR types), and TLS (new crypto algorithms among others). It is common practice for protocol registries to have a "playground" area.

Sure, and that makes sense where it's appropriate.

I believe I already said this.

>>     I disagree.  The new numbers may still be assigned, but there's still
>>     the potential/likely mess with the old numbers.
> 
> In the larger IETF we have a great deal of experience in experiments concluding, being taken down, and official standard numbers being used. It doesn't happen overnight, but it doesn't take decades either.

Really?  What % of the traffic that you see is still NTPv3?

How long do you think it will be before updated NTPv4 servers are 
"generally" deployed?

What are the cleanup/pollution costs of doing what I have suggested, 
compared to what you are suggesting?

> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp

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