IETF Logo Mail Archive

Re: [Ntp] [EXT] Re: I-D Action: draft-ietf-ntp-over-ptp-02.txt

Miroslav Lichvar <mlichvar@redhat.com> Tue, 20 February 2024 08:26 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 99AC6C151997 for <ntp@ietfa.amsl.com>; Tue, 20 Feb 2024 00:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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_H2=-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 PbZFPsjFnXrG for <ntp@ietfa.amsl.com>; Tue, 20 Feb 2024 00:26:33 -0800 (PST)
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 06FA2C151996 for <ntp@ietf.org>; Tue, 20 Feb 2024 00:26:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1708417591; 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=mBqLkSi8NwBHPhCMi2o8EihKTLKyd5v455nWgkzOgTU=; b=Sjcm8wR41wvHrJgEMuYgQ2No056/xGSzB+1qhYctKVB3FtJ3lElz59iKrxQHp6X5+22q+r uW6dIjBOsHEtZdhg/okh72p1DWgGnr5Rcl+pF/lumCJfIIAnudbVJegd9zjDwPEFsJ7t1s 94U1anIs24UNqxE/8rQg7E7JtWxBJrk=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-401-Z1totAkMNxCir2RdQrFh6Q-1; Tue, 20 Feb 2024 03:26:29 -0500
X-MC-Unique: Z1totAkMNxCir2RdQrFh6Q-1
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (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 C79CB84AF90; Tue, 20 Feb 2024 08:26:28 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 50B20492BE2; Tue, 20 Feb 2024 08:26:28 +0000 (UTC)
Date: Tue, 20 Feb 2024 09:26:26 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Windl, Ulrich" <u.windl@ukr.de>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <ZdRiMoQ2lgzGGdSN@localhost>
References: <170559083139.51727.7055735529782201998@ietfa.amsl.com> <0b00f60b1df14fe49666b0be67813ff6@ukr.de> <ZbDkl8pOAuvTdS9b@localhost> <1a5437e79aeb476fa24d1b38984aad0d@ukr.de>
MIME-Version: 1.0
In-Reply-To: <1a5437e79aeb476fa24d1b38984aad0d@ukr.de>
X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10
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/765XYJeoGdPC8_elDrm93QBxGE4>
Subject: Re: [Ntp] [EXT] Re: I-D Action: draft-ietf-ntp-over-ptp-02.txt
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: Tue, 20 Feb 2024 08:26:33 -0000

On Wed, Jan 24, 2024 at 10:29:11AM +0000, Windl, Ulrich wrote:
> Miroslav,
> 
> thanks for explaining; my second issue was whether the abstract should emphasize that "NTP _packets_" are encapsulated(?) in "PTP _packets_". That's what I meant with "transport". I think saying "protocol" instead is more confusing.

The draft in the git repository now has:

This document specifies a transport for the client-server and
symmetric modes of the Network Time Protocol (NTP) which encapsulates
NTP messages in messages of the Precision Time Protocol (PTP). This
transport enables hardware timestamping in network interface
controllers which can timestamp only PTP messages and enables delay
corrections in PTP transparent clocks.

Please let me know if you think this is still not clear enough.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email