> On 25 Jul 2018, at 21:52, Benjamin Kaduk <[email protected]> wrote: > > On Fri, Jul 20, 2018 at 02:48:16PM -0400, Melinda Shore wrote: >> Hi, all: >> >> Thanks for an excellent meeting yesterday. There are a few >> questions coming out of it that we'll be bringing to the mailing >> list next week, once most people are home. >> >> The draft minutes have been posted at >> https://datatracker.ietf.org/meeting/102/materials/minutes-102-trans-00. >> Please send comments, corrections, etc. to the mailing list. > > % 4) Fotis Loukos requested that we clarify what we mean by > % "current NTP time." There is no proposed text. Given > % how late this is in the process, if someone doesn't give > % us text there's nothing to talk about, so if someone > % feels strongly about this they should contribute text. > % Nobody expressed concern. Fotis should produce text, or > % we'll drop it. > > ("NTP Time" appears twice in the document.) > > It seems like the concern here is that NTP is a protocol for conveying time > information from one location/system to another, but there is not > necessarily a single universal/global consensus "NTP Time". That is, I can > run a clock over here with free-running quartz and use NTP to synchronize a > different machine with it, but it will be quite disjoint from "reality". > So it seems like we need to indicate what pool(s) of servers are > authoritative for the time that we want to be using, or just say it's UTC > or GPS or whatever.
Isn’t there a case, here, for asking the tictoc WG for advice about a canonical reference or chunk of text that could be used? Yrs., Robin
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
