[Ntp] Alternative for interleave mode

David Venhoek <david@venhoek.nl> Fri, 13 January 2023 14:34 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 93EB5C1782D1 for <ntp@ietfa.amsl.com>; Fri, 13 Jan 2023 06:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 pJQJHdp6N5My for <ntp@ietfa.amsl.com>; Fri, 13 Jan 2023 06:34:26 -0800 (PST)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 C3BADC1782CD for <ntp@ietf.org>; Fri, 13 Jan 2023 06:34:25 -0800 (PST)
Received: by mail-pj1-x1033.google.com with SMTP id o13so19112914pjg.2 for <ntp@ietf.org>; Fri, 13 Jan 2023 06:34:25 -0800 (PST)
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=B2tdHDL2Xse0ke/iBXl54WqB5Ou2LamdhZ5VbkBj9ig=; b=vJSYR1vvs3ijKgoYbIAD7zV+9Tuub3LyQXCAcrhwr1hvvvWzZiyw27bWL6vaoW1RGh QuPzsHopoJmtLnM8gJAtcvER5aAl6elDPJAHfrFXwv9NxS6rVtmyWLfxAauF3iFqpCeq AppnbJ+tHQuG/iJK+egq1zo0dwtBiU8kjTQWSH3DUA8gyENMt0HOc8dYK4hsTM4gjvpW qGxhn9xFJMsCPVOwt3p0JHob/iIjIhIBqyEqASAZN1efDVTd9FassUrUCQP/F9MrZj4u 3EWJVzFGNaD3ccdx9cioHNH/QdnDppsveTrpsRL32joit4tQ6UHytmNeqD0X67izTkSj K9Sg==
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=B2tdHDL2Xse0ke/iBXl54WqB5Ou2LamdhZ5VbkBj9ig=; b=lG7LyAxk/X92MGkU3eainBowW7ngasPkA3CxasP7Y2h4ashXUbki+yfV8j+E+C5dwa Nlb3Uoig0wSuirLnN+9GHWqn0yvQf3hRcskhMSMn05Iabav2CX0vIeXRAyMU0hXVSmix za7oJYpH9Kc4YmopQRjd5LLOMeVuTyJw4A0uKF1irAb8/c7aa8phB0crObErBEFlQnDv GKOURcgvpqoWexpk3z8V+YW0bHZ7rxVVHdNuucyCNLOcd1f6Q+Awj7vJtHSEst7bF4cJ +RbMxtQn1/fUzb2rYzTx78IJEvRO5nokOJbEKv6GLLFtkFZiAD/JtVm/0W0KYXFeQICc bG8A==
X-Gm-Message-State: AFqh2kpShUDQIYwur27g5mELDLy3BOVkySENTyHmMuwxQg0oTknHtPue /GIoKgqy3UaNdnCm4E9UD+CgpNuH2BpKB8WYZ8toilFJw1bZZQ==
X-Google-Smtp-Source: AMrXdXtBakTe6i3600fwx28/WaAkgpuaQM5JudMHxjDZR1DibL3+3Sh4QXcV9B670sAIrKc3j1su6KwdphzWWjFl/Ao=
X-Received: by 2002:a17:902:f252:b0:194:6b4c:125f with SMTP id j18-20020a170902f25200b001946b4c125fmr314971plc.63.1673620465160; Fri, 13 Jan 2023 06:34:25 -0800 (PST)
MIME-Version: 1.0
From: David Venhoek <david@venhoek.nl>
Date: Fri, 13 Jan 2023 15:34:14 +0100
Message-ID: <CAPz_-SWfJgxtaTYjEyck106oCezMV6P+psV=Ldes4MRJ5uNjFQ@mail.gmail.com>
To: ntp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/zoFxfWrrdwHHEA-gsbaSgEiLRhU>
Subject: [Ntp] Alternative for interleave mode
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, 13 Jan 2023 14:34:28 -0000

Dear All,

The current proposal for NTPv5 includes an interleaved mode. It's
current design is quite involved, with the server keeping state across
multiple exchanges, and a client potentially having to wait a further
polling interval before getting the final timestamp. As such, it makes
implementation a bit tricky.

I would like to at least have discussed the following alternative:
When a server receives an "high-precision" request, it first sends to
the client the actual response, and then immediately on getting the
transmission timestamp for that response, it sends a second response
with the higher-precision transmission timestamp (similar to PTP's 2
step mode). This would have the advantage that a client gets its high
precision timestamp immediately, without having to do multiple NTP
requests in short succession, and that the server would not have to
keep any long-term state.

I know this probably immediately triggers a gut reaction of: "But then
the NTP server can be used to amplify traffic in reflection denial of
service attacks". Yes, technically we indeed now get a greater than
unity amplification factor. However, the amplification factor is still
only 2, both in bytes and number of packets, which is well below other
widely deployed UDP-based protocols such as quic (and from what i can
tell, quite well accepted, the quic working group is working by the
guideline that one should never send more than 3x the packets/bytes
received before validating origin). Given the simplicity of the above
scheme compared to interleave mode, I am of the opinion this is a
tradeoff worth making, but I was wondering what other peoples view is?

Kind regards,
David Venhoek