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

David Venhoek <david@venhoek.nl> Thu, 14 December 2023 12:26 UTC

Return-Path: <david@venhoek.nl>
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 F2B2BC14F618 for <ntp@ietfa.amsl.com>; Thu, 14 Dec 2023 04:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=venhoek-nl.20230601.gappssmtp.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 qbIjjbKlVebs for <ntp@ietfa.amsl.com>; Thu, 14 Dec 2023 04:26:52 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4D1D3C14F5E4 for <ntp@ietf.org>; Thu, 14 Dec 2023 04:26:51 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-54cb4fa667bso11155029a12.3 for <ntp@ietf.org>; Thu, 14 Dec 2023 04:26:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venhoek-nl.20230601.gappssmtp.com; s=20230601; t=1702556809; x=1703161609; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xWcb94tQhshPfpUQ4C4Eby7YNhJjCXyjeQz9QLQ5F1Y=; b=kVkyh+72L7hloVtucTMlZwUUjH5iIjLMiYmYUZmngW8KhexsHPDX0NyRrsidi79JTH dOTEu9xDt494+1r8skdn4KGOk42Euyzd7o7lQt2p4vxiLUJ3Mhxud3vSKrLkiPaU1Wo5 3BA3cg5dmJw2rTBV63qeUwkJo6A5RXtPte1m0Br3yfU7AtCgF48x/e8PX7UFKTiiJ0+A i4gsHxmPq/efor6b7xRvCALSo31265Od9rWOuvn8z1fylTLLarigHu2XRdPkFTPFvuVc LtTmsZdkgXLUoQKpABhoasSNtZkOrspOO9NqzWp9rjL6LchfOAqfc5IKkdNIYe/Xx0QQ FKtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702556809; x=1703161609; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xWcb94tQhshPfpUQ4C4Eby7YNhJjCXyjeQz9QLQ5F1Y=; b=RTqL77+XEoDUmoAKvWnv2Krwfow2sKXBHTkc6zrWeWnqnc584AJg16+4EHqEbxzy+N ygIBdMicO5hyvycb2qOLrySlSgvlkzL3+LEES8vvSl7l+Sk3S8Wv9z0WU/em+k/AuOR0 8rHlnvBk4Tx2z+xTJJg+365LUTNxI5w2WNKD0vkNcdNt+y8Aj09BQsHRwm90B7nVgHbD 0Eho5rQv4EfVcgGyhflxVVD+0AbOAlxR8JqVxVpTSgCLGFq7HA93zxuBg0h6dsUZIU+y lPqy01QfALlCpS9/is1lPhlIc4y9mhttCrWxd3Rg0VPqkpWPfRrjDQsMSdLFUlWjsdOS zkmw==
X-Gm-Message-State: AOJu0YyDDQvDxNDNYW9rDYOYtS+BbR9DWDYNBkVcVXXXRoM2PX0D4IhJ krlA6OXkyTvmFsNPPCmCD4lMDpkAgFFyhGWgHyolbn4kR+yLJlyd
X-Google-Smtp-Source: AGHT+IGY4tqqczlkakokhqA4+4OI++7ibx+42b7R1w3ugbDFRkhlvk2Rh94c+4EzD767XtKsZ/8wkNbZmVH9JLOMnk0=
X-Received: by 2002:a17:906:100d:b0:a1f:8b0a:f09f with SMTP id 13-20020a170906100d00b00a1f8b0af09fmr4561501ejm.93.1702556809052; Thu, 14 Dec 2023 04:26:49 -0800 (PST)
MIME-Version: 1.0
References: <CA+mgmiPAoS3-VFrBB3PUhOOWp7iU1exLrYJTj8GdA5gcTTa+yw@mail.gmail.com> <DM8PR04MB7799D8AEBCA0EC789FA6F03EA18AA@DM8PR04MB7799.namprd04.prod.outlook.com> <OF658EB84F.7400FD62-ONC1258A85.003FC225-C1258A85.00403180@ptb.de>
In-Reply-To: <OF658EB84F.7400FD62-ONC1258A85.003FC225-C1258A85.00403180@ptb.de>
From: David Venhoek <david@venhoek.nl>
Date: Thu, 14 Dec 2023 13:26:37 +0100
Message-ID: <CAPz_-SUVs2u8+7b-05sm7eqGdDVEJa3kYgYYU6gExxw2_mzbsw@mail.gmail.com>
To: martin.langer=40ptb.de@dmarc.ietf.org
Cc: mlichvar@redhat.com, ntp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/toDS96jNc5FJwsLHnu5Ajmy-KMg>
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 12:26:54 -0000

I have read the draft and although I do consider it sufficiently ready
in its current state, I agree with Martin and consider all his
suggestions improvements that would be worth making.

Kind regards,
David

On Thu, Dec 14, 2023 at 12:41 PM <martin.langer=40ptb.de@dmarc.ietf.org> wrote:
>
> 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.
>
> https://datatracker.ietf.org/doc/draft-ietf-ntp-over-ptp/01/
>
>
>
> 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
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp