Re: [Ntp] NTS4UPTP draft

Miroslav Lichvar <mlichvar@redhat.com> Thu, 03 June 2021 08:02 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 4B4EE3A2EFD for <ntp@ietfa.amsl.com>; Thu, 3 Jun 2021 01:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.496
X-Spam-Level:
X-Spam-Status: No, score=-3.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=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 qpNRqYno-3Ea for <ntp@ietfa.amsl.com>; Thu, 3 Jun 2021 01:02:54 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.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 4939F3A2EFB for <ntp@ietf.org>; Thu, 3 Jun 2021 01:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1622707372; 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=z1KTgIC+fCvAhjPAeuK+1Cvd9cDN88tb0C9LyGP6EN4=; b=IURhP3zuXI9GfL7m2Qj+khkHlGow9AZhlKbiqW5ZQ0DeSwr2vXEcqsAbl9Kp0uiOB65xHK 2P7Srd95uD0XWFHwfBWiH8aEJ5z/HXqf27qiNZlEUN3gHbsvDGVphwFyJ+0hurRj56FGTN n1mtkyA5bgoF7TZpOAi1LFQN1wC24x0=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-152-6x-02mjTP96qL7jOJns4eA-1; Thu, 03 Jun 2021 04:02:51 -0400
X-MC-Unique: 6x-02mjTP96qL7jOJns4eA-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 25832107ACCA; Thu, 3 Jun 2021 08:02:50 +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 3E094610B0; Thu, 3 Jun 2021 08:02:49 +0000 (UTC)
Date: Thu, 3 Jun 2021 10:02:47 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Dieter Sibold <dsibold.ietf@gmail.com>
Cc: Heiko Gerstung <heiko.gerstung=40meinberg.de@dmarc.ietf.org>, NTP WG <ntp@ietf.org>
Message-ID: <YLiMp17LeGVOTp+r@localhost>
References: <C3693A60-E1A0-4570-91C3-876EB584B468@meinberg.de> <A2CB8908-86BE-4FB0-959C-7FF1DED9B421@gmail.com>
MIME-Version: 1.0
In-Reply-To: <A2CB8908-86BE-4FB0-959C-7FF1DED9B421@gmail.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
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/z1U9-wk_6ZAQ-rvHQNuIJv8VwzU>
Subject: Re: [Ntp] NTS4UPTP draft
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 03 Jun 2021 08:02:57 -0000

On Wed, Jun 02, 2021 at 11:40:49PM +0200, Dieter Sibold wrote:
> In the past PTP is applied mainly in local networks but today it is going to
> be applied across Internet connection also.

Just to clarify, do you mean that people are now using PTP to
synchronize clocks over Internet, or that the servers are
accessible from Internet and that's why they need to be secured?

The former wouldn't make sense to me as PTP relies on hardware support
in routers/switches, which is generally missing on Internet.

-- 
Miroslav Lichvar