IETF Logo Mail Archive

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

Hal Murray <halmurray@sonic.net> Wed, 06 December 2023 07:02 UTC

Return-Path: <halmurray@sonic.net>
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 608BFC14F5F9 for <ntp@ietfa.amsl.com>; Tue, 5 Dec 2023 23:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sonic.net
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 MODvNuEPRwS3 for <ntp@ietfa.amsl.com>; Tue, 5 Dec 2023 23:02:37 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4D5C14F5F5 for <ntp@ietf.org>; Tue, 5 Dec 2023 23:02:37 -0800 (PST)
Received: from 107-137-68-211.lightspeed.sntcca.sbcglobal.net (104-182-38-69.lightspeed.sntcca.sbcglobal.net [104.182.38.69]) (authenticated bits=0) by c.mail.sonic.net (8.16.1/8.16.1) with ESMTPSA id 3B672Xl4014916 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 5 Dec 2023 23:02:33 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sonic.net; s=net23; t=1701846155; bh=gVn48Ex5JVbos4q3f0PZflrhdzFAZH/Uj9xe7WM9Hvo=; h=To:From:Subject:Mime-Version:Date:Message-Id:From:Subject; b=C5b/8LPYbRgZPSAuz3qxwG6TtUjxdx1Vu8Qy5xc7/jDe3BAqeHEO5V0BLuCNB+e5h PESwa/ItQMGXgWuKzQoAZ1Ods6/vudRbfhJyU59B+z1341JBu5bW52N+VSf/PU7+Tx PfXkKwG8qpwolkb2LRZoab2N1DIvTK1ygPqSWo5E+4Nv5+ICDEkyV959XGIa7C+h5x tbi/F460vNXWfkl5758CltISFcwc3tPmb47Gaoi+2FBru/hcMko/Goy/0zn6FqPG7q 6hAeuoMl5S9LIAZE4PGrHsnWyhjx94VD1eDdJ7SLgJU4DX2BVVWZ7nQ1Fih67clgVO cH/XBgQ5r+b2Q==
Received: from hgm (localhost [IPv6:::1]) by 107-137-68-211.lightspeed.sntcca.sbcglobal.net (Postfix) with ESMTP id 8BEE328C1C3; Tue, 5 Dec 2023 23:02:33 -0800 (PST)
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8
To: "Salz, Rich" <rsalz@akamai.com>
cc: Hal Murray <halmurray@sonic.net>, "ntp@ietf.org" <ntp@ietf.org>
From: Hal Murray <halmurray@sonic.net>
In-Reply-To: Message from "Salz, Rich" <rsalz@akamai.com> of "Tue, 05 Dec 2023 15:44:21 +0000." <450EAC4D-E24E-4E04-9239-EB0356784822@akamai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 05 Dec 2023 23:02:33 -0800
Message-Id: <20231206070233.8BEE328C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Sonic-CAuth: UmFuZG9tSVao4e9S2MzIDSNTawFLSn3sB3xwUE9eDln6d4m6mhBl8fegbX25LI8XOJuRLmtEQULh7gSeZBEPHBTzdcmTbHK3gzEu1KfFHlc=
X-Sonic-ID: C;RHsMbgWU7hGOoS5nR+6Zsg== M;Xm8hbgWU7hGOoS5nR+6Zsg==
X-Sonic-Spam-Details: -1.5/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gSnjYA8htPjy28Cgp480EF-RkBk>
Subject: Re: [Ntp] 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, 06 Dec 2023 07:02:41 -0000

rsalz@akamai.com said:
> Is there a typo in that 7882 number?  Maybe 7821? I would also really
> appreciate it if you could propose (very rough draft is fine) text as I still
> don't understand you. 

Yes on typo.  No on 7821.  I was trying for 7822
  Network Time Protocol Version 4 (NTPv4) Extension Fields

> I would also really appreciate it if you could propose (very rough draft is
> fine) text as I still don't understand you.

NTPv4 packets may contain a MAC (Message Authentication Code) that appears 
where you would expect an extension but it does NOT have the type/length 
header of an extension.  RFC 7822 has the details of how MACs can coexist with 
extensions.
    Network Time Protocol Version 4 (NTPv4) Extension Fields


-- 
These are my opinions.  I hate spam.

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