Re: [Ntp] Please move draft-ietf-ntp-update-registries forward
Harlan Stenn <stenn@nwtime.org> Wed, 17 August 2022 23:30 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 9D163C15949B; Wed, 17 Aug 2022 16:30:57 -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 rmTHXMQQhiJh; Wed, 17 Aug 2022 16:30:53 -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 9C50CC159498; Wed, 17 Aug 2022 16:30:53 -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 4M7PQj0kWCzMP64; Wed, 17 Aug 2022 23:30:53 +0000 (UTC)
Message-ID: <aaf49a9b-0c48-6a15-250b-fe293fac8fa2@nwtime.org>
Date: Wed, 17 Aug 2022 16:30:52 -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-chairs@ietf.org" <ntp-chairs@ietf.org>
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <173FE6CC-D76F-4B44-9E1B-13B5C5F196BB@akamai.com>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <173FE6CC-D76F-4B44-9E1B-13B5C5F196BB@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/_9vLmnNpQCw42lo55S7Z3Aw2_1w>
Subject: Re: [Ntp] Please move draft-ietf-ntp-update-registries forward
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: Wed, 17 Aug 2022 23:30:57 -0000
I remain opposed to the advancement of this document. I gather it makes no difference that the NTP Project is opposed to the advancement of this document. On 8/17/2022 1:47 PM, Salz, Rich wrote: > Chairs, > > This version has the changes that I posted about at [1]. I changed the subject line (it was "Quick review of WGLC for status change for draft-ietf-ntp-update-registries") to avoid getting buried in the mega-thread. > > Thanks. > /r$ > > [1] https://mailarchive.ietf.org/arch/msg/ntp/swcTFo8r2tw9swke_ZB5vx7RElE/ > > > On 8/17/22, 4:31 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Network Time Protocols WG of the IETF. > > Title : Updating the NTP Registries > Author : Rich Salz > Filename : draft-ietf-ntp-update-registries-06.txt > Pages : 10 > Date : 2022-08-17 > > Abstract: > The Network Time Protocol (NTP) and Network Time Security (NTS) > documents define a number of assigned number registries, collectively > called the NTP registries. Some registries have wrong values, some > registries do not follow current common practice, and some are just > right. For the sake of completeness, this document reviews all NTP > and NTS registries. > > This document updates RFC 5905, RFC 5906, RFC 8573, RFC 7822, and RFC > 7821. > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-ntp-update-registries > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ietf-ntp-update-registries-06.html > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-ntp-update-registries-06 > > _______________________________________________ > ntp mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp -- Harlan Stenn <stenn@nwtime.org> http://networktimefoundation.org - be a member!
- [Ntp] Please move draft-ietf-ntp-update-registrie… Salz, Rich
- Re: [Ntp] Please move draft-ietf-ntp-update-regis… Harlan Stenn
- Re: [Ntp] Please move draft-ietf-ntp-update-regis… Sanjeev Gupta
- Re: [Ntp] Please move draft-ietf-ntp-update-regis… Salz, Rich