[Ntp] Re: Grease in Roughtime
Marcus Dansarie <marcus@dansarie.se> Thu, 26 September 2024 12:03 UTC
Return-Path: <marcus@dansarie.se>
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 E24AAC180B5F for <ntp@ietfa.amsl.com>; Thu, 26 Sep 2024 05:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dansarie.se
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 x8kFnTm3RDmP for <ntp@ietfa.amsl.com>; Thu, 26 Sep 2024 05:03:49 -0700 (PDT)
Received: from mail.dansarie.se (mail.dansarie.se [IPv6:2a02:7aa0:5000::14a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C00FC15153F for <ntp@ietf.org>; Thu, 26 Sep 2024 05:03:48 -0700 (PDT)
Received: by mail.dansarie.se (Postfix, from userid 117) id F1D1C7E117; Thu, 26 Sep 2024 12:03:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dansarie.se; s=mail; t=1727352220; bh=qXswWNOAhIt8lxTqzcP/pm8UdpURITMUbXcxwalgOko=; h=Date:Subject:To:References:From:In-Reply-To:From; b=PcLUYh3L7YUbO2f92McJKhTzCJeDk4ZxpvcR84bu2bqcnAqWaJWFYytaJx4338Rbr MaMp2biiif9sCR36avgFnreWZZYolzBE7I3xxuKwpAKf2SJ+NT2O9hxkFl3UUDePVo TAwNd9cCWya9ydThQV703lEEij3Ib3OjATWF8OVZf3k2f1PIQCX83mzmkksQWSzuZT WaCI9jsvAoiEED3OcQambU1rLeaukrCYtF0zRs/PaGc+h98fWHfWk632pt/MSDwCOD SvE68gRa95bGe95Rw9idTh05F6k6SyECUWWRQZMcDyoQyEEd8Ef45YDSql8Qftr99d wqRIG9GPeQeZg==
Message-ID: <f535f5d6-d176-4ae8-8447-53d6846d0267@dansarie.se>
Date: Thu, 26 Sep 2024 14:03:39 +0200
MIME-Version: 1.0
To: ntp@ietf.org
References: <CAPz_-SUY9egByeG+cSHXFqbc6XzRmkpCF7Y4QS2ud0LmOjccAA@mail.gmail.com> <55dedf3b-04f7-4efe-bb8a-6aee9554e011@dansarie.se> <CAPz_-SU7qf3dkvgQvG44knH6ZostdXY=_z-viBrCk-7gF1K4SQ@mail.gmail.com>
Content-Language: en-US, sv-SE
From: Marcus Dansarie <marcus@dansarie.se>
In-Reply-To: <CAPz_-SU7qf3dkvgQvG44knH6ZostdXY=_z-viBrCk-7gF1K4SQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: RTROXKKR377OUMCWHDVZUUBXP3EKTF2E
X-Message-ID-Hash: RTROXKKR377OUMCWHDVZUUBXP3EKTF2E
X-MailFrom: marcus@dansarie.se
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: Grease in Roughtime
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/KM4RjSovQmN1b5t3sjl4hdVGOag>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>
Thanks! Would adding "Servers SHOULD ignore any unknown version numbers in the list supplied by the client. If the list contains no version numbers supported by the server, it MAY respond with another version or ignore the request entirely, see Section 6.2.2." to Section 6.1.1. (in draft 11) be a suitable fix for this? Kind regards, Marcus On 2024-09-26 08:22, David Venhoek wrote: > Hi Marcus, > > Apologies for taking some time on this. My concern here is that > suppose we go to a version 2 of roughtime in the future, clients may > for a while send out requests that are both valid as version 1 and > version 2 requests, accepting either response. If the server balks at > seeing version number 2 (because it doesn't exist according to it) and > thus would not, or not respond correctly to such packets, this would > make version negotiation really painfull. So servers in my view should > ignore version numbers they don't recognize in the VER tag, as long as > there is at least one they do know about. > > I hope that clarifies. > > Kind regards, > David Venhoek
- [Ntp] Grease in Roughtime David Venhoek
- [Ntp] Re: Grease in Roughtime Marcus Dansarie
- [Ntp] Re: Grease in Roughtime kristof.teichel
- [Ntp] Re: Grease in Roughtime Marcus Dansarie
- [Ntp] Re: Grease in Roughtime kristof.teichel
- [Ntp] Re: Grease in Roughtime David Venhoek
- [Ntp] Re: Grease in Roughtime Marcus Dansarie
- [Ntp] Re: Grease in Roughtime Marcus Dansarie