[Ntp] Antw: Re: I-D Action: draft-roughtime-aanchal-02.txt

["Ulrich Windl" <[e-mail]>]

>>> Thomas Peterson <[e-mail]> schrieb am 28.05.2019 um 17:01
in
Nachricht <[e-mail]>:
> 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‑[e-mail] 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
>> [e-mail] 
>> https://www.ietf.org/mailman/listinfo/ntp 
>> 
> 
> _______________________________________________
> ntp mailing list
> [e-mail] 
> https://www.ietf.org/mailman/listinfo/ntp