Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 / Extension fields

Miroslav Lichvar <mlichvar@redhat.com> Mon, 06 December 2021 09:15 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 235A43A094D for <ntp@ietfa.amsl.com>; Mon, 6 Dec 2021 01:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.701, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 (1024-bit key) header.d=redhat.com
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 NOMF10woCVOB for <ntp@ietfa.amsl.com>; Mon, 6 Dec 2021 01:15:31 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EEF13A094B for <ntp@ietf.org>; Mon, 6 Dec 2021 01:15:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638782130; 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=Vq7AJA1qLMldsq2JW46reGgJk7TPRer/E2yY81uAfqU=; b=RufnlHkQp6JW0UjkvhkkjbTcrXdyQSvuhyWr2x7/Ib4n+ZNQazjo07C74P6hfSGyOBkAqh 5XCi0EZZPVG/E2fNTPOlMKuXz0g/KfQodtmpBadde100OFzCYlLkRSP/rvjYs08GTm8TH7 I0mVKh8geDOzQzNgEgKG7IB/pdHZ+x4=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-363-A3a5WzUhNW-cdElcgoZ_lQ-1; Mon, 06 Dec 2021 04:15:29 -0500
X-MC-Unique: A3a5WzUhNW-cdElcgoZ_lQ-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 03E7B100C661; Mon, 6 Dec 2021 09:15:28 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4662C694D7; Mon, 6 Dec 2021 09:15:26 +0000 (UTC)
Date: Mon, 06 Dec 2021 10:15:15 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Doug Arnold <doug.arnold@meinberg-usa.com>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <Ya3UozKl4s5mNfAJ@localhost>
References: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org> <20211125214748.Horde.K2Fa5qir5iPLYRvfQJBMx8m@mail.drown.org> <YadcBggcGB2plRcB@localhost> <20211201222611.Horde.cHBebdjnI893O9eYyGQ_AE7@mail.drown.org> <YaiK7LT+BHaJMkyv@localhost> <AM7PR02MB57650A1696E0708E322247E7CF699@AM7PR02MB5765.eurprd02.prod.outlook.com>
MIME-Version: 1.0
In-Reply-To: <AM7PR02MB57650A1696E0708E322247E7CF699@AM7PR02MB5765.eurprd02.prod.outlook.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/zcfxiR0PEtjyZR7qOOxt0tJSCy0>
Subject: Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 / Extension fields
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: Mon, 06 Dec 2021 09:15:34 -0000

On Thu, Dec 02, 2021 at 05:20:16PM +0000, Doug Arnold wrote:
> Just to be clear: PTP does not require that all switches are PTP capable.  The ITU-T G.8265.1 and G.8275.2 profiles explicitly assume that there is no or only partial timing support in the network path.  Financial data centers often do not need on-path support since their networks are designed for minimum latency.

I guess I should say "required to perform well".

Yes, technically speaking, PTP will work in a network without full PTP
support, but it was not designed for that (it breaks the assumption
about delay being mostly constant) and generally will not work as well
as protocols that were designed for real computer networks like NTP.

Also, the PTP support in switches is not just about being present or
not. It must be reasonably well implemented. I know that in some cases
it had to be disabled as it actually made things worse.

> Practically speaking, in long network paths, it would take only one busy router with no timing capability to render the correction field irrelevant. The Correction proposed for ntpv5 would probably be most useful for site local use cases, at least at first.  But if it became common for switch and router vendors to implement this feature, then WAN timing would gradually become more precise.

Right.

-- 
Miroslav Lichvar