Re: [Ntp] I-D Action: draft-aanchal-time-implementation-guidance-01.txt
"Dieter Sibold" <dsibold.ietf@gmail.com> Wed, 31 October 2018 19:09 UTC
Return-Path: <dsibold.ietf@gmail.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 44388130DFA; Wed, 31 Oct 2018 12:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 CBJoEszpgi_l; Wed, 31 Oct 2018 12:09:11 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FE01130E61; Wed, 31 Oct 2018 12:09:11 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id b203-v6so15581826wme.5; Wed, 31 Oct 2018 12:09:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=svaAf5NJLWFa7ni+NDamc5cuCo8lnh+hytUt22V/JTw=; b=GQRDv47v8l/+IZZ1n5ee/6755XtRq8aU6fwQrs+jqlwp4H21ncdV3WFgCZ5fIyNInd hEHpQ5mrkexR5Va4LkZTLx3pKFaFGA1cwAxoFtnvQjYVPHEjWSolbxyiWZSiIKPcOmpu /RQsUUctlN5paudR4q9/DdK+2Er3F2CEnuwVKePYeE9uU2MmLwVSFvNjf4LdePLtHjD8 72iNbXvEB3zvWb43jYH5nxyNmN6nR0U3IoCs/BrfRgSBiAVAyIKw0/N1H3C3+FwJb0Xt 7uEUtR3zZE+eK99PzGt5DZKdUQ+XfnUEa9Yvq/surMuJy6FpwrJB+SH2D72MQLRJWOio 306A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=svaAf5NJLWFa7ni+NDamc5cuCo8lnh+hytUt22V/JTw=; b=aUtfzbjncypgHrBS+4UFlawUPQtrcn4FA7DJG9DLLQ7yx6T4tvJ7kXLXdW2Nt4Y97G 4meCCfPj4Ys+y0GUwhHhD1u3tAxnUYV04F4p5cp1ypjvrT4YbshBItr1qE+S6D5n81Fv asIwNizZMncBCa6q3qs4VYvCuwVaOOP6NiXrUdBKil5E1r+vJlNGQ5W84CfC3SFetQXH CGzGR05+Z/N5ofUdYNXQJEq2BGJt8rsEPWR7xtwSQrn7igOLF4il+3HOONDGRWwJeDC5 aaNF/8CEWUzirvuMMdr7MMozW8KrUV3Q83suCIxfTrSP+MwsanjavmZGh97FGP9tjf6k dKgw==
X-Gm-Message-State: AGRZ1gJBOWIBRLCFtNUnQ0L8TNowbrsCkKIqAhAmkvAPrTdp7vhWo2uY v2W+l2XG8HxHFXXhjtUSD9ZLce/k
X-Google-Smtp-Source: AJdET5f1UrxHrlcRsuFux0tL19ddkceAyB7Fl+F70FdBVqeHAz6PK4dE1pu+nzBwz9pzA6tiD08QUQ==
X-Received: by 2002:a1c:d0c6:: with SMTP id h189-v6mr2477303wmg.43.1541012949560; Wed, 31 Oct 2018 12:09:09 -0700 (PDT)
Received: from [192.168.178.23] (p200300D17F19E100352137C8526F46A4.dip0.t-ipconnect.de. [2003:d1:7f19:e100:3521:37c8:526f:46a4]) by smtp.gmail.com with ESMTPSA id k73-v6sm5192901wmd.33.2018.10.31.12.09.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Oct 2018 12:09:09 -0700 (PDT)
From: Dieter Sibold <dsibold.ietf@gmail.com>
To: ntp@ietf.org
Cc: i-d-announce@ietf.org
Date: Wed, 31 Oct 2018 20:09:07 +0100
X-Mailer: MailMate Trial (1.12r5523)
Message-ID: <5E11364F-629C-4400-8141-4111E00EE2CB@gmail.com>
In-Reply-To: <154023544942.13497.15596133854387518696@ietfa.amsl.com>
References: <154023544942.13497.15596133854387518696@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Vw8CTwKmqJhEzFaaTJOEhVzHyjw>
Subject: Re: [Ntp] I-D Action: draft-aanchal-time-implementation-guidance-01.txt
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: Wed, 31 Oct 2018 19:09:15 -0000
I appreciate the intention of this document and I think this can be a very valuable document. But from my point of view Sec. 5 and 6 currently are somewhat short for a real helpful guidance for implementors. The approach using relative time is interesting; but it misses to indicate the possibility to syntonize clocks. Especially, I missed a discussion for the situation for using relative time in time synchronized systems. The reason is that it is nearly unimaginable to operate computer systems unsynchronized. Usually, regulations such as ISO/IEC 27002 enforce the need to synchronize your systems to an external time reference. Other comments: - Sec. 2, last paragraph. I would claim that e.g. ITU-R TF.686-3 define most of the terms used in this document. - Sec. 3.2, second paragraph: I would suggest to replace „rate of passage …“ with frequency or even better with the term „clock rate“ - Sec. 4. I don’t get the meaning of the first sentence. Is it possible to rephrase in order to make it easier to understand? - Sec. 4.2, 5th paragraph, last sentence. Chrony, OpenNTP are all more or less complete implementations of NTP and not different time protocols as implied by this sentense. - Sec. 4.2, 7th paragraph. I would think, that adjusting time zone offsets is not to be compared to the manuell adjustment to what is called the world clock. - Sec. 5, last paragraph: an application may rely on timing over short and long time periods depending on the specific situation. So this is not only application but also depending upon the specific situation. - Sec. 6.1 introduce the term „raw time“ without definition Dieter On 22 Oct 2018, at 21:10, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Network Time Protocol WG of the IETF. > > Title : On Implementing Time > Authors : Aanchal Malhotra > Kristof Teichel > Martin Hoffmann > Willem Toorop > Filename : draft-aanchal-time-implementation-guidance-01.txt > Pages : 9 > Date : 2018-10-22 > > Abstract: > This document describes the properties of different types of clocks > available on digital systems. It provides implementors of > applications with guidance on choices they have to make when > working > with time to provide basic functionality and security guarantees. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-aanchal-time-implementation-guidance/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-aanchal-time-implementation-guidance-01 > https://datatracker.ietf.org/doc/html/draft-aanchal-time-implementation-guidance-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-aanchal-time-implementation-guidance-01 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > ntp mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp
- [Ntp] I-D Action: draft-aanchal-time-implementati… internet-drafts
- Re: [Ntp] I-D Action: draft-aanchal-time-implemen… Dieter Sibold
- Re: [Ntp] I-D Action: draft-aanchal-time-implemen… Aanchal Malhotra