Re: [Ntp] ntp-over-ptp concerns
Miroslav Lichvar <mlichvar@redhat.com> Thu, 21 March 2024 14:04 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 B2562C15154E for <ntp@ietfa.amsl.com>; Thu, 21 Mar 2024 07:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=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=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DCizAWxn2OhR for <ntp@ietfa.amsl.com>; Thu, 21 Mar 2024 07:04:06 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23B3EC1519B7 for <ntp@ietf.org>; Thu, 21 Mar 2024 07:04:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1711029844; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=s0Sq+adRFKDP48Bfq/1fAo57VgyJggm1qKkuMYJ2PeE=; b=UZGiaqYq3WHR82omycfEbxKToIGXuzjyr/uz/RDa//5QCY63VlCKRtIlLfpeny28+rTbzq 1OxZEqIBCtZZOcEYv5okhbp+cPLXlj4NNGkZyKHBxsis51Ir4hB4NKMx2gchT/F9KuyKJm OO5WrkyHvtal/0Tij/CTKYmZdYFU6kw=
Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-319-KvIv8BBeMNKfMfz399XHtQ-1; Thu, 21 Mar 2024 10:04:03 -0400
X-MC-Unique: KvIv8BBeMNKfMfz399XHtQ-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id A165D3C02754; Thu, 21 Mar 2024 14:04:02 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AA4A21121337; Thu, 21 Mar 2024 14:04:01 +0000 (UTC)
Date: Thu, 21 Mar 2024 15:04:00 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Rodney Cummings <rodney.cummings@keysight.com>
Cc: Rodney Cummings <rodney.cummings=40keysight.com@dmarc.ietf.org>, NTP WG <ntp@ietf.org>, Doug Arnold <doug.arnold@meinberg-usa.com>
Message-ID: <Zfw-UJOw3-la9aEv@localhost>
References: <DM6PR17MB3484BA12E5E0214094779270832B2@DM6PR17MB3484.namprd17.prod.outlook.com> <ZfG46DseQnstP42z@localhost> <DM6PR17MB3484BAD48E399E34F9099D53832A2@DM6PR17MB3484.namprd17.prod.outlook.com> <Zfha5e_qPafzuhYz@localhost> <DM6PR17MB3484D04B648BBCB46E48F387832D2@DM6PR17MB3484.namprd17.prod.outlook.com> <Zflgai93DduRfWyX@localhost> <DM6PR17MB3484F334535FD5985EEF28AA832C2@DM6PR17MB3484.namprd17.prod.outlook.com>
MIME-Version: 1.0
In-Reply-To: <DM6PR17MB3484F334535FD5985EEF28AA832C2@DM6PR17MB3484.namprd17.prod.outlook.com>
X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/PvmxBJJnbycACKAM5ypmML9G7TY>
Subject: Re: [Ntp] ntp-over-ptp concerns
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: Thu, 21 Mar 2024 14:04:06 -0000
On Tue, Mar 19, 2024 at 04:14:44PM +0000, Rodney Cummings wrote: > There’s a very basic statement in 6.6.2 of 1588-2019: > “MASTER: The PTP Port is the source of time on the PTP Communication Path served by the PTP Port.” > > What is the source of time in NTP-over-PTP? There is no working PTP source of time in NTP over PTP. It's like a network where all PTP clocks are slaveOnly clocks, waiting for a master to appear, but that never happens. The PTP clocks are just sending unicast delay requests transporting NTP messages according to their configuration. Nothing interesting is happening from the PTP point of view. > You seem to be saying “It doesn’t comply with any state in 1588”. If so, that proves my point. No, I'm not saying that. The UNCALIBRATED state seems perfectly fine for NTP over PTP. It allows delay requests to be sent by the port. It doesn't require any messages to be received before that. The unicast option doesn't require the delay response grant for sending delay requests. 9.5.11.2 has requirements for timing of delay requests. It starts with "Unless the unicast option of 16.1 is in use", but 16.1 refers back to 9.5.11.2 with "In addition to these transmission requirements, Delay_Req messages are also required to comply with the transmission requirements defined in 9.5.11.2.", i.e. there is a loop in the specification. Assuming the intention for timing of unicast delay requests was to also follow the general requirements specified for multicast delay requests, we need a different state to stop sending delay requests when not needed. The PASSIVE state seems like a good option. It ignores all received messages and doesn't transmit anything. Alternatively, we can immediately destroy the PTP instance after sending the delay request and create it again when needed. The port can reach the UNCALIBRATED and PASSIVE states the usual way from INITIALIZING through LISTENING using an alternate BMCA, or directly using the "17.6 Mechanism for external configuration of a PTP Instance’s PTP Port state" option. Please let me know if you see any errors in this. -- Miroslav Lichvar
- [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns Doug Arnold
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar
- Re: [Ntp] ntp-over-ptp concerns heiko.gerstung@meinberg.de
- Re: [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns David Venhoek
- Re: [Ntp] ntp-over-ptp concerns Doug Arnold
- Re: [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar
- Re: [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar
- Re: [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar
- Re: [Ntp] ntp-over-ptp concerns Rodney Cummings
- Re: [Ntp] ntp-over-ptp concerns Miroslav Lichvar