[{"author": "Lou Berger", "text": "https://notes.ietf.org/notes-ietf-113-detnet?edit
", "time": "2022-03-22T13:33:07Z"}, {"author": "J\u00e1nos Farkas", "text": "yes, it is status
", "time": "2022-03-22T13:34:52Z"}, {"author": "Pascal Thubert", "text": "had the same garbaging of the automated pdf conversion AT LPWAN
", "time": "2022-03-22T13:35:04Z"}, {"author": "Toerless Eckert", "text": "Lou: Video from you would be nice
", "time": "2022-03-22T13:35:10Z"}, {"author": "J\u00e1nos Farkas", "text": "https://datatracker.ietf.org/doc/slides-113-detnet-01-intro-wg-status-charter-draft-status/
", "time": "2022-03-22T13:36:51Z"}, {"author": "Andy Malis", "text": "The garbled \"WG Status\" slide is fine on the Datatracker meeting materials page
", "time": "2022-03-22T13:37:02Z"}, {"author": "Scott Mansfield", "text": "https://www.itu.int/en/ITU-T/studygroups/2017-2020/13/Pages/q6.aspx
ITU-T Y.3000-series \u2013 Network 2030 services: Capabilities, performance and
design of new communication services for the Network 2030 applications
https://www.itu.int/rec/T-REC-Y.Sup66-202007-I/en
Liaison receiver: https://datatracker.ietf.org/liaison/1753/
Liaison sent: https://datatracker.ietf.org/liaison/1765/
02 - ITU-T Q6/13 recommendation progress
", "time": "2022-03-22T13:50:19Z"}, {"author": "J\u00e1nos Farkas", "text": "I agree, contributions are welcome.
", "time": "2022-03-22T14:10:18Z"}, {"author": "Xuesong Geng", "text": "For the comments from Toerless: I have checked the trakcer and find that IEEE 802.1 Qcc is one of the references in the original versions, but missed somehow in the latest versions
", "time": "2022-03-22T14:28:38Z"}, {"author": "Xuesong Geng", "text": "Thank for raising this, and we will add it in the next version
", "time": "2022-03-22T14:29:14Z"}, {"author": "Yizhou Li", "text": "that works
", "time": "2022-03-22T14:52:38Z"}, {"author": "Toerless Eckert", "text": "Ah.. now we can rerad the slides
", "time": "2022-03-22T14:52:41Z"}, {"author": "Lou Berger", "text": "@meetecho -- had a couple of instances of corrupted slides. I reloaded the slides and it's okay. See #8 and #1
", "time": "2022-03-22T14:53:50Z"}, {"author": "Meetecho", "text": "Lou: yes, we've seen a couple of instances, it looks like it's happening only on the first slide (at least before)
", "time": "2022-03-22T14:54:23Z"}, {"author": "Meetecho", "text": "It sounds like a conversion error, possibly due to some charset or font problem, we'll check later what the issue may be
", "time": "2022-03-22T14:54:41Z"}, {"author": "Lou Berger", "text": "2nd slide for presentation #8 and towards the end on pres #1
", "time": "2022-03-22T14:54:57Z"}, {"author": "Lou Berger", "text": "for us
", "time": "2022-03-22T14:55:06Z"}, {"author": "Meetecho", "text": "Thanks, we'll have a look at those slides to see what's happening!
", "time": "2022-03-22T14:55:25Z"}, {"author": "Lou Berger", "text": "otherwise the upload and presenter control is very nice!
", "time": "2022-03-22T14:55:41Z"}, {"author": "Shaofu Peng", "text": "can i check mic ?
", "time": "2022-03-22T15:13:47Z"}, {"author": "Dean Bogdanovi\u0107", "text": "per the slide, there is requirement to provide time stamping by the origination and destination point. As Greg correctly pointed out, we can't rely to have those two end points will be in time sync and don't know what is the drift on each end. With that the one way delay measurement becomes unreliable.
", "time": "2022-03-22T15:22:10Z"}, {"author": "Kehan Yao", "text": "Hi @Greg, regarding your questions on clock synchronization deployment, sometimes the deployment is not that easy especially places underground. People might need multiple-stratum NTP for time sync. But the precision can not be guaranteed, and the cost might be very high.
", "time": "2022-03-22T15:23:27Z"}, {"author": "Kehan Yao", "text": "My proposal assumes a ref pkt been sent in deterministic path where its latency bound is within us level, every time you want to measure a target pkt, you use the ref pkt for calculation. The sending time interval between both the pkts is very small, so that we could think the offset between both ends is static. And we can just get the OWD based on the mechanism above.
", "time": "2022-03-22T15:28:05Z"}]