Re: [Ntp] [EXTERNAL] WGLC - draft-ietf-ntp-over-ptp

martin.langer@ptb.de Thu, 14 December 2023 11:41 UTC

Return-Path: <martin.langer@ptb.de>
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 C380CC14F5FB for <ntp@ietfa.amsl.com>; Thu, 14 Dec 2023 03:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.529
X-Spam-Level:
X-Spam-Status: No, score=-6.529 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, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, HTTPS_HTTP_MISMATCH=0.1, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=ptb.de
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 MpwHwKy1oLgW for <ntp@ietfa.amsl.com>; Thu, 14 Dec 2023 03:41:14 -0800 (PST)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (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 E45D8C14F5EC for <ntp@ietf.org>; Thu, 14 Dec 2023 03:41:13 -0800 (PST)
Received: from s23397.bs.ptb.de ([172.21.101.132]) by mx1.bs.ptb.de with ESMTP id 3BEBfBvm017048-3BEBfBvo017048 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 14 Dec 2023 12:41:11 +0100
Sensitivity:
MIME-Version: 1.0
In-Reply-To: <DM8PR04MB7799D8AEBCA0EC789FA6F03EA18AA@DM8PR04MB7799.namprd04.prod.outlook.com>
References: <DM8PR04MB7799D8AEBCA0EC789FA6F03EA18AA@DM8PR04MB7799.namprd04.prod.outlook.com>, <CA+mgmiPAoS3-VFrBB3PUhOOWp7iU1exLrYJTj8GdA5gcTTa+yw@mail.gmail.com>
From: martin.langer@ptb.de
To: mlichvar@redhat.com
Cc: ntp@ietf.org
Message-ID: <OF658EB84F.7400FD62-ONC1258A85.003FC225-C1258A85.00403180@ptb.de>
X-Priority: 3 (Normal)
Importance: Normal
Date: Thu, 14 Dec 2023 12:41:09 +0100
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-FEAS-Client-IP: 172.21.101.132
X-FE-Policy-ID: 5:5:5:SYSTEM
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=ptb.de; s=s1-ptbde; c=relaxed/relaxed; h=mime-version:subject:references:from:to:cc:message-id:date:content-type; bh=nZfpK+jk9MqAy0kyvyhynU2IsSoDpZbgp1tlnD9nHV4=; b=WrqGRW+HoIvdQkw2BkyzGQUFbtoAYUSmk8Gg54OQi7V3QlVNfXkzRDFD9CfLqgHABhPb9TlEVXgA epLOQNmsBcDQDodei6VmpDxcNto/QqjeoDXdpGyubYtX6mvIvEFfI+jcKYYvzztl2Ho73VYoxkKw 1xJz+Nx5h7qyIZsV0bRPtlwntv9xXzBw2m9M/WtFoZMHe7+UacCa4ys4XvZfAx6olLX6LUYaSLE4 NT0H920aFo+696hKmv+GYvnkhk/edcmSf27xZY777HZxBWwykhGCG1BIev7uVs2eaVJjm0uwvQWe e8WdpTw6WoeQ4Uh34a8hTViVQ2lQmiAqCLnzkA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/QXC7FIbKM5P6v4hp8KfWBOdZl1M>
Subject: Re: [Ntp] [EXTERNAL] WGLC - draft-ietf-ntp-over-ptp
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, 14 Dec 2023 11:41:18 -0000

Dear Miroslav, dear all,
 
I have reviewed your draft and have a few final comments.
Otherwise, I think this document is ready to be submitted to the IESG for publication.
 
 
#1: On the first page you wrote: "specific PTP transport (e.g. UDPv4, UDPv6, 802.3)". I would suggest the following: "specific PTP transport (e.g. UDP over IPv4, UDP over IPv6, 802.3)". 
--> I consider this change optional.
 
 

#2: On page two it says: "It adds a new extension field (TLV) for PTP". My suggestion: "It adds a new type-length-value (TLV) extension field for PTP". 
--> I see this change as optional, but I would prefer it.
 
 

#3: Section1 has only one subsection. From a structural point of view, there should always be at least two subsection. My suggestion: Simply insert another subsection before the text "The client-server mode of NTP, even if using the PTP transport, has several advantages to PTP using multicast or unicast messaging:". E.g. with the title: "1.1. Main Features and Advantages". The current subsection "1.1. Requirements Lanuage" will therefore become 1.2. 
--> I see this change as a recommendation, but I would much prefer it.
 
 

#4: On page 3 it says: "NTP is more secure. It can use existing security mechanisms ". I am not sure if this is true. The PTP header/PTP timestamp are not protected. For example, NTS would only secure the NTP packet embedded in PTP (also mentioned in section 2), right? Could you clarify this again? Maybe I just didn't understand it correctly.
--> A brief clarification (possibly an additional sentence) of what is protected and what is not would be highly recommended.
 

#5: In chapter 2 it says: "The originTimestamp field and all fields of the header SHOULD be zero, except:". My recommendations:
  - 1: instead of "the header" better "the PTP header"
  - 2: should "minorVersionPTP" also be included in the following list? Then you will support PTPv2.0 and PTPv2.1.
--> However, I see this change as optional.
 
 

#6: Chapter 3 describes an NTP extension field. I recommend 1-2 more sentences about the fact that:
  - Type and Length are each a 16-bit unsigned integer in network byte order.
  - Length represents the size of the complete extension field (including the Ext Field Header).
-->I see this change as a recommendation, but I would prefer it.
 
 
 
kind regards,
Martin

__________________________________________
Dr.-Ing. Martin Langer
Physikalisch-Technische Bundesanstalt (PTB)
Working Group 4.42 "Dissemination of Time"
Bundesallee 100,
38116 Braunschweig (Germany)
Tel.: +49 531 592-4470
E-Mail: martin.langer@ptb.de
__________________________________________
 
 
----- Ursprüngliche Nachricht -----
Von: "Denis Reilly" <dreilly=40equinix.com@dmarc.ietf.org>
Gesendet von: "ntp" <ntp-bounces@ietf.org>
An: "Karen ODonoghue" <kodonog@pobox.com>, "ntp@ietf.org" <ntp@ietf.org>
CC:
Betreff: Re: [Ntp] [EXTERNAL] WGLC - draft-ietf-ntp-over-ptp
Datum: Fr, 8. Dez 2023 21:04
 

Hello,

 

I have reviewed this document (NTP over PTP) and have no further comments.

I believe this document is ready to be submitted to the IESG for publication.

 

Best Regards,

 

--

Denis Reilly

Principal Timing Architect, Equinix Precision Time

Equinix | dreilly@equinix.com  |  +1-585-282-7899

 

 

 

From: ntp <ntp-bounces@ietf.org> on behalf of Karen ODonoghue <kodonog@pobox.com>
Date: Thursday, November 30, 2023 at 4:35 PM
To: ntp@ietf.org <ntp@ietf.org>
Subject: [EXTERNAL] [Ntp] WGLC - draft-ietf-ntp-over-ptp

NTP WG members,

 

This email initiates the NTP working group last call for the NTP over PTP document. 

 

Please review this document and respond with an email on the following two questions: 

1) Please review the document closely and provide comments. It is also only eleven pages in total so it is a quick read. 

2) Please state whether or not you think this document is ready to be submitted to the IESG for publication (pending resolution of any comments you have made). 

 

Given the brevity of the document, this WGLC will conclude on Wednesday 13 November. 

 

Regards,

Karen and Dieter

_______________________________________________
ntp mailing list
ntp@ietf.org
https://www.ietf.org/mailman/listinfo/ntp" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/ntp