[Ntp] NTPv5 draft move timescale into flags
David Venhoek <david@venhoek.nl> Fri, 04 November 2022 11:20 UTC
Return-Path: <david@venhoek.nl>
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 588DDC15271B for <ntp@ietfa.amsl.com>; Fri, 4 Nov 2022 04:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venhoek-nl.20210112.gappssmtp.com
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 Csf2MADjXKaK for <ntp@ietfa.amsl.com>; Fri, 4 Nov 2022 04:20:12 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 CE2CFC152719 for <ntp@ietf.org>; Fri, 4 Nov 2022 04:20:12 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id v27so7149054eda.1 for <ntp@ietf.org>; Fri, 04 Nov 2022 04:20:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venhoek-nl.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ZWqHLU+ByemwkNHmx258I33yvWQFDzVTROdtUzWwBx8=; b=uO544sY/Ovuu5mRBxe7S69bT9AlJVxSsbXtJqKpkclbLYUnM0Q349RQADuhtOzUvQx B+uyvaM8hUilX8QOY3w7UVjsJIvtCPAWbjTHdmEpGL/zr7Xqbjdoo7GRK8azO5EBvDvP 3ycsYbOWXJg+CjaoXlXIAMWMqxVGpKR7MFgf4gXlUhcaVrcKS9Zi6z49XjVZdeWSQMWK oJaiOdvyxLHxfDJ+M6wNslG45O7Lv+uHvoeUZtx9sH009/fQsosT9W5Qjs/79h2a5eDj w79UF/YbYYO5SM+EStnYoK5N8mCEdfQ7dR+WKwsL43m+vp5UTDEAh186dGMhMKwJ5i/u WL4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZWqHLU+ByemwkNHmx258I33yvWQFDzVTROdtUzWwBx8=; b=lvPWsNB7uCxqbLMw5cG4+nGcCOFTaOHYnabYY3YWNIKmx387aLOOhaI9pu9sYRuOKN jR2U1C32nOzD8HxxdLf5ZWuDE3arlMwrD5OWtwYpBNvgIjBT3/e+hcZJGvSXwVYjTQE/ aFzFtBTa7OkFXXrFg92+8tuEgi1DMtJXUBx5LFV4it4xpNNUl5/2GS/lXMvibgqkTnZ3 CKwWtACYWHPFHYC31+uk/AbSZ5sVmcahnYsnLOtfX4pq6K9t7GGnGOYUdp8t5mOSzf8e 4YARZ5lAezcS6QjE5N6HPOil6F1JY+vGf9eVSmAQ8p65u7FCYfVVZ3t6B+0V7WkY925e vGmw==
X-Gm-Message-State: ACrzQf0FLpkf2w160rFWmf4MJOjuUhVgz39Q5dcQ7A/vEKOzeFP/+6oo zhLulBn5cbT5tbnWoHqybxOdLLpJlndpTSZsM5GhWGqkeFxOiQ==
X-Google-Smtp-Source: AMsMyM63IUH1QxrRBvfe0vqgzV8Hel66ZWzEAd6ZcWcNz+OyUyrYmrTYOnQ6aqWd4IlIqaJieQ+VWnhZhP6aOJmvT3I=
X-Received: by 2002:aa7:c1d9:0:b0:463:aeaf:3383 with SMTP id d25-20020aa7c1d9000000b00463aeaf3383mr20044091edp.253.1667560810677; Fri, 04 Nov 2022 04:20:10 -0700 (PDT)
MIME-Version: 1.0
From: David Venhoek <david@venhoek.nl>
Date: Fri, 04 Nov 2022 12:19:59 +0100
Message-ID: <CAPz_-SU-J46nT__7-AtxFmPBYn_5x_HwgMhjSLEzBsX3R93Rbg@mail.gmail.com>
To: ntp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/GhbQSE3Vrs5kxOPGBlFWcSrkuG4>
Subject: [Ntp] NTPv5 draft move timescale into flags
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: Fri, 04 Nov 2022 11:20:17 -0000
Dear All, I would like to propose moving the timescale identifying field into what in the current draft is the flags field. In my view, doing so would have several advantages: - We keep the full 8 bits available for stratum, thus allowing parties that want to work with higher stratum ranges to still do so. - Because the flag field is relatively under-used, a full 6 (or even 7, depending on what we do with interleaved modes and the server cookie) can be used for timescale identification, leaving more room for future expansion and/or a private/experimental-use range. I have opened a pull request to this effect on Miroslav's draft git repository, the diff is included below for those not comfortable with git. Kind regards, David Venhoek --- a/ntp-ntpv5.xml +++ b/ntp-ntpv5.xml @@ -199,9 +199,9 @@ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -|LI | VN |Mode | Scale |Stratum| Poll | Precision | +|LI | VN |Mode | Stratum | Poll | Precision | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -| Flags | Era | Timescale Offset | +|FL | Timescale | Era | Timescale Offset | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Root Delay | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -258,8 +258,8 @@ <t hangText="Mode"><vspace/> A 3-bit field containing the value 3 (request) or 4 (response).</t> - <t hangText="Scale"><vspace/> - A 4-bit identifier of the timescale. In requests it is the + <t hangText="Timescale"><vspace/> + A 6-bit identifier of the timescale. In requests it is the requested timescale. In responses it is the timescale of the receive and transmit timestamps. Defined values are: @@ -288,8 +288,8 @@ included in the message as a rounded log2 value in seconds. In requests, which don't contain any timestamps, it is always 0.</t> - <t hangText="Flags"><vspace/> - An 8-bit integer that can contain the following flags: + <t hangText="FL"><vspace/> + A 2-bit integer flag field that can contain the following flags: <list style="hanging"> <t hangText="0x1: Unknown leap"><vspace/>
- [Ntp] NTPv5 draft move timescale into flags David Venhoek
- Re: [Ntp] NTPv5 draft move timescale into flags Miroslav Lichvar
- Re: [Ntp] NTPv5 draft move timescale into flags David Venhoek