[Ntp] Antw: Re: I-D Action: draft-roughtime-aanchal-02.txt
"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> Wed, 29 May 2019 08:23 UTC
Return-Path: <Ulrich.Windl@rz.uni-regensburg.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 B911B120075 for <ntp@ietfa.amsl.com>; Wed, 29 May 2019 01:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 DFvXS7CztVYq for <ntp@ietfa.amsl.com>; Wed, 29 May 2019 01:23:56 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (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 5EC8612002E for <ntp@ietf.org>; Wed, 29 May 2019 01:23:56 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6F8906000051 for <ntp@ietf.org>; Wed, 29 May 2019 10:23:53 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 43E6F600004D for <ntp@ietf.org>; Wed, 29 May 2019 10:23:52 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 29 May 2019 10:23:52 +0200
Message-Id: <5CEE4196020000A1000317DC@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.1.1
Date: Wed, 29 May 2019 10:23:50 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Thomas Peterson <nosretep.samoht@gmail.com>, "ntp@ietf.org" <ntp@ietf.org>
References: <155897662160.809.5527655773398720605@ietfa.amsl.com> <2351e209-4ab5-c336-cd48-5d792901574f@gmail.com>
In-Reply-To: <2351e209-4ab5-c336-cd48-5d792901574f@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/kcu0oitRht6b7ZL90_NuVSpxq6I>
Subject: [Ntp] Antw: Re: I-D Action: draft-roughtime-aanchal-02.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, 29 May 2019 08:24:00 -0000
>>> Thomas Peterson <nosretep.samoht@gmail.com> schrieb am 28.05.2019 um 17:01 in Nachricht <2351e209-4ab5-c336-cd48-5d792901574f@gmail.com>: > Thank you for publishing a new version of the draft. > > Some feedback based on your new changes, the existing concerns raised > prior not withstanding: > > * Nit: "... violations are greater then a second the loss..." should be > "greater than a second" > * You have not provided sufficient information for implementations on > how to actually calculate time, only citing a single, out‑of‑publication > reference. Besides Wikipedia and a humor page[0] stored on the Internet > Archive, I have been unable to find a definitive source that describes > MJD. Could you please in a future version describe in detail how an RFC 1305 refers to it, too: "The Modified Julian Date (MJD), which is sometimes used to represent dates near our own era in conventional time and with fewer digits, is defined as MJD = JD – 2,400,000.5. Following the convention that our century began at 0h on 1 January 1900, at which time the tropical year was already 12h old, that eclectic instant corresponds to MJD 15,020.0. Thus, the Julian timescale ticks in standard (atomic) 365.25-day centuries and was set to a given value at the approximate epoch of a cosmic event which apparently synchronized the entire human community, the origin of the Common Era." Later: "The UTC timescale thus ticks in standard (atomic) seconds and was set to the value 0h MJD 41,317.0 at the epoch determined by astronomical observation to be 0h on 1 January 1972 according to the Gregorian calendar; that is, the inaugural tick of the UTC Era." "The NTP timescale is based on the UTC timescale, but not necessarily always coincident with it. At 0h on 1 January 1972 (MJD 41,317.0), the first tick of the UTC Era, the NTP clock was set to 2,272,060,800, representing the number of standard seconds since 0h on 1 January 1900 (MJD 15,020.0)." Finally in RFC 6055 ;-) [MJD] Duerst, M., "The Properties and Promizes of UTF-8", Regards, Ulrich Windl > implementation take the time received and perform the necessary > computation to something that could be applied to a system clock. > * Would it not be more appropriate to break up the MIDP value so the MJD > day and time offset from midnight be pout into separate keys? > * Is there a specific reason why the document has now a mixture of "bit" > and "byte"? For example, MIDP is 8 _bytes_, but RADI is 32 _bits_. It's > reasonable to assume that a reader can distinguish, but having a mixture > such as this could lead to errors in implementations due to reader error. > > Regards > > 0: > https://web.archive.org/web/20070606064704/http://vms.tuwien.ac.at/info/humo > ur/vms‑base‑time‑origin.txt > > On 27/05/2019 17:03, 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 : Roughtime >> Authors : Aanchal Malhotra >> Adam Langley >> Watson Ladd >> Filename : draft‑roughtime‑aanchal‑02.txt >> Pages : 11 >> Date : 2019‑05‑27 >> >> Abstract: >> This document specifies Roughtime ‑ a protocol that aims to achieve >> rough time synchronization while detecting servers that provide >> inaccurate time and providing cryptographic proof of their >> malfeasance. >> >> 1 >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft‑roughtime‑aanchal/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft‑roughtime‑aanchal‑02 >> https://datatracker.ietf.org/doc/html/draft‑roughtime‑aanchal‑02 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft‑roughtime‑aanchal‑02 >> >> >> 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 mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp
- [Ntp] I-D Action: draft-roughtime-aanchal-02.txt internet-drafts
- Re: [Ntp] I-D Action: draft-roughtime-aanchal-02.… Thomas Peterson
- [Ntp] Antw: Re: I-D Action: draft-roughtime-aanch… Ulrich Windl
- Re: [Ntp] I-D Action: draft-roughtime-aanchal-02.… Tal Mizrahi
- Re: [Ntp] I-D Action: draft-roughtime-aanchal-02.… Watson Ladd
- Re: [Ntp] Antw: Re: I-D Action: draft-roughtime-a… Thomas Peterson