[Ntp] Re: Murray Kucherawy's No Objection on draft-ietf-ntp-interleaved-modes-07: (with COMMENT)

Miroslav Lichvar <mlichvar@redhat.com> Thu, 22 August 2024 14:24 UTC

Return-Path: <mlichvar@redhat.com>
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 31CE6C1D5300 for <ntp@ietfa.amsl.com>; Thu, 22 Aug 2024 07:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level:
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 2bayAvqVrxy8 for <ntp@ietfa.amsl.com>; Thu, 22 Aug 2024 07:24:57 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B063BC1D52FA for <ntp@ietf.org>; Thu, 22 Aug 2024 07:24:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1724336696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ttLvcOcu33QIxf/S4eOwi8AqhAsmpicUYUPSOSiOp2Q=; b=csMdaMsnaWtWMvltFiouyN35R/ZrPfH1GLtmr5NKwJJc7OPyatbHrJ3xy++muHjbPpkz7G 0TxxikTVSJc8U8gS44AVkB6GJCGB9derNcHi6qPROUMZnQVbQAcv0rijbes1EXQnvMva6R hG3sR8FP1+HOMQUCOAWAmzEjz+Zd0uQ=
Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-283-IIxIVUDfOC2ZTyBXbPN0rQ-1; Thu, 22 Aug 2024 10:24:52 -0400
X-MC-Unique: IIxIVUDfOC2ZTyBXbPN0rQ-1
Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 550441955D48; Thu, 22 Aug 2024 14:24:51 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7AE3319560A3; Thu, 22 Aug 2024 14:24:49 +0000 (UTC)
Date: Thu, 22 Aug 2024 16:24:47 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <ZsdKL65bWceeLr6R@localhost>
References: <172430714178.2516744.14943185824171903015@dt-datatracker-6df4c9dcf5-t2x2k>
MIME-Version: 1.0
In-Reply-To: <172430714178.2516744.14943185824171903015@dt-datatracker-6df4c9dcf5-t2x2k>
X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: 25DAYHB6FLM5IZXYYBAM3XZDTQ2JZJYG
X-Message-ID-Hash: 25DAYHB6FLM5IZXYYBAM3XZDTQ2JZJYG
X-MailFrom: mlichvar@redhat.com
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
CC: The IESG <iesg@ietf.org>, draft-ietf-ntp-interleaved-modes@ietf.org, ntp-chairs@ietf.org, ntp@ietf.org, odonoghue@isoc.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: Murray Kucherawy's No Objection on draft-ietf-ntp-interleaved-modes-07: (with COMMENT)
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/WGoVp5swV2ihAqZCGyaXlEYWGIA>
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>

On Wed, Aug 21, 2024 at 11:12:21PM -0700, Murray Kucherawy via Datatracker wrote:
> A SHOULD presents an implementer with a choice.  A specification using it
> provides better service to implementers when they are fully informed of that
> choice, why one or the other option is preferred, what interoperability impact
> there is when deviating from the advice, etc.
> 
> In my case, the one I'm most interested in is this one in Section 2:
> 
> > When the server receives a request from a client, it SHOULD respond in the
> interleaved mode if the following conditions are met:
> 
> Why would an implementer opt not to comply with this SHOULD?  What are the
> implications of not doing so?

This was meant to avoid forcing servers to respond in interleaved
mode, for example to improve the timekeeping performance or server
performance. The server might be able to respond, but it prefers to
not to do that, e.g. it still has the old timestamps but it now knows
their accuracy was worse than the current non-interleaved timestamps.

-- 
Miroslav Lichvar