IETF Logo Mail Archive

Re: [Ntp] [EXT] I-D Action: draft-ietf-ntp-update-registries-09.txt

"Windl, Ulrich" <u.windl@ukr.de> Wed, 22 November 2023 09:48 UTC

Return-Path: <u.windl@ukr.de>
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 664A1C151061; Wed, 22 Nov 2023 01:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 CN4Wu4puY6UG; Wed, 22 Nov 2023 01:48:48 -0800 (PST)
Received: from mail01.ukr.de (mail01.ukr.de [193.175.194.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34A49C14CE2F; Wed, 22 Nov 2023 01:48:43 -0800 (PST)
X-CSE-ConnectionGUID: My21lN3GSOW00ky+KddDIg==
X-CSE-MsgGUID: ipsJyTjtReaqTOPOrtEL4A==
X-ThreatScanner-Verdict: Negative
X-IronPort-AV: E=McAfee;i="6600,9927,10901"; a="486702"
X-IronPort-AV: E=Sophos;i="6.04,218,1695679200"; d="scan'208,217";a="486702"
Received: from unknown (HELO ukr-excmb04.ukr.local) ([172.24.6.64]) by dmz-infcsg01.ukr.dmz with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Nov 2023 10:48:40 +0100
Received: from ukr-excmb03.ukr.local (172.24.6.63) by ukr-excmb04.ukr.local (172.24.6.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.34; Wed, 22 Nov 2023 10:48:40 +0100
Received: from ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0]) by ukr-excmb03.ukr.local ([fe80::1cb4:6e0c:6da4:a8a0%4]) with mapi id 15.01.2507.034; Wed, 22 Nov 2023 10:48:40 +0100
From: "Windl, Ulrich" <u.windl@ukr.de>
To: "ntp@ietf.org" <ntp@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [EXT] [Ntp] I-D Action: draft-ietf-ntp-update-registries-09.txt
Thread-Index: AQHaHODBiGVUTJv2O0aLZenGV2JYxLCGFs/g
Date: Wed, 22 Nov 2023 09:48:40 +0000
Message-ID: <3248dbced66b4210b5e660848416ef29@ukr.de>
References: <170061542965.24075.12652860551660946944@ietfa.amsl.com>
In-Reply-To: <170061542965.24075.12652860551660946944@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.3.1]
Content-Type: multipart/alternative; boundary="_000_3248dbced66b4210b5e660848416ef29ukrde_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/EBZiZZq7dv9GEUe40aQLAIrNv-c>
Subject: Re: [Ntp] [EXT] I-D Action: draft-ietf-ntp-update-registries-09.txt
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, 22 Nov 2023 09:48:52 -0000

Hi all!



It seems " an ASCII uppercase letter or minus sign" still lacks "digit" (in 4.1. NTP Reference Identifier Codes).

I'm unsure about " 4.2. NTP Kiss-o'-Death Codes" that claims the same.



I'm also surprised a bit by the ordering of the entries at the end of the table:
0xC302

Reserved for historic reasons

This RFC

0xC402

Reserved for historic reasons

This RFC

0xC502

Reserved for historic reasons

This RFC

0xC602

Reserved for historic reasons

This RFC

0xC702

Reserved for historic reasons

This RFC

0xC802

Reserved for historic reasons

This RFC

0x0902

Reserved for historic reasons

This RFC

0x8902

Reserved for historic reasons

This RFC

0xC902

Reserved for historic reasons

This RFC




Kind regards,

Ulrich



-----Original Message-----
From: ntp <ntp-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: Wednesday, November 22, 2023 2:10 AM
To: i-d-announce@ietf.org
Cc: ntp@ietf.org
Subject: [EXT] [Ntp] I-D Action: draft-ietf-ntp-update-registries-09.txt



Internet-Draft draft-ietf-ntp-update-registries-09.txt is now available. It is

a work item of the Network Time Protocols (NTP) WG of the IETF.



   Title:   Updating the NTP Registries

   Author:  Rich Salz

   Name:    draft-ietf-ntp-update-registries-09.txt

   Pages:   11

   Dates:   2023-11-21



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, and makes updates where necessary.



   This document updates RFC 5905, RFC 5906, RFC 8573, RFC 7822, and RFC

   7821.



The IETF datatracker status page for this Internet-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-09.html



A diff from the previous version is available at:

https://author-tools.ietf.org/iddiff?url2=draft-ietf-ntp-update-registries-09



Internet-Drafts are also available by rsync at:

rsync.ietf.org::internet-drafts





_______________________________________________

ntp mailing list

ntp@ietf.org

https://www.ietf.org/mailman/listinfo/ntp

v2.28.0 | Report a Bug | By Email | System Status