Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 / Message Format
Dan Drown <dan-ntp@drown.org> Thu, 25 November 2021 04:38 UTC
Return-Path: <dan-ntp@drown.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 74FE73A0E94 for <ntp@ietfa.amsl.com>; Wed, 24 Nov 2021 20:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sz3IZKbYYbsj for <ntp@ietfa.amsl.com>; Wed, 24 Nov 2021 20:38:10 -0800 (PST)
Received: from vps3.drown.org (vps3.drown.org [96.126.122.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEC2F3A0E92 for <ntp@ietf.org>; Wed, 24 Nov 2021 20:38:10 -0800 (PST)
Received: by vps3.drown.org (Postfix, from userid 48) id 2A1192FCAC6; Wed, 24 Nov 2021 22:38:10 -0600 (CST)
Received: from 2603-8080-2709-c400-e945-1441-73fa-e502.res6.spectrum.com (2603-8080-2709-c400-e945-1441-73fa-e502.res6.spectrum.com [2603:8080:2709:c400:e945:1441:73fa:e502]) by mail.drown.org (Horde Framework) with HTTPS; Wed, 24 Nov 2021 22:38:10 -0600
Date: Wed, 24 Nov 2021 22:38:10 -0600
Message-ID: <20211124223810.Horde.KKjrsykVQUMJgW4WVO5ZZmt@mail.drown.org>
From: Dan Drown <dan-ntp@drown.org>
To: ntp@ietf.org
In-Reply-To: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/7VR_nOp7XQO6v7b4UC9Sr6bckII>
Subject: Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 / Message Format
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Nov 2021 04:38:14 -0000
This email will be on the "4. Message Format" section. Right now the flags/era/timescale fields come before root dispersion and root distance. This puts them at a different offset in the packet compared to their location in NTPv4. Was there a reason not to keep these at the same offset? It's not an implementation problem, just a cosmetic difference. For timescale offset, there is an overlap with the unknown value (0x8000/-1.0 seconds) during a negative leap second smear. Is this worth mentioning in the rfc? Transmit Timestamp currently has: "In responses it is the time when a response to the client was transmitted. The specific response depends on the selected mode (basic or interleaved). The timestamp corresponds to the beginning of the transmission" I'm suggesting this rewording: "In responses it is the beginning of the transmission of a response to the client. Which response it refers to depends on the selected mode (basic or interleaved). See Measurement Modes section below for detail."
- [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 Dan Drown
- [Ntp] Antw: [EXT] comments on draft‑mlichvar‑ntp‑… Ulrich Windl
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 Miroslav Lichvar
- Re: [Ntp] Antw: [EXT] comments on draft‑mlichvar‑… Miroslav Lichvar
- [Ntp] Antw: Re: Antw: [EXT] comments on draft‑mli… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] comments on draft… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: [EXT] comments on draft… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] comments on draft… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft‑mlichvar‑ntp‑ntpv5‑03 Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Harlan Stenn
- Re: [Ntp] comments on draft‑mlichvar‑ntp‑ntpv5‑03 Steven Sommars
- Re: [Ntp] comments on draft‑mlichvar‑ntp‑ntpv5‑03 Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- [Ntp] Antw: [EXT] Re: comments on draft‑mlichvar‑… Ulrich Windl
- [Ntp] Antw: [EXT] Re: comments on draft‑mlichvar‑… Ulrich Windl
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Danny Mayer
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Dan Drown
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Danny Mayer
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Doug Arnold
- Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03… Miroslav Lichvar