Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Jouni
Hi. If the timestamp is used only for the playout time and the granularity is 1nS, how will the sending system know the value of time at the receiving system with 1nS granularity for playout planning? How will the sending system know the transit time of that specific packet to plan for the playout with 1nS of accuracy? Pat > From: jouni.korhonen@xxxxxxxxxxxx > To: STDS-1904-3-TF@xxxxxxxxxxxxxxxxx > Subject: continuing the discussion on timestamps > Date: Wed, 18 Mar 2015 22:40:43 +0000 > > Folks, > > Let's continue where we left off in call.. two things I would like to get a better sense of the room is the timestamp granularity/accuracy. I had a proposal for 1ns and not sending timestamp in every packet. Assuming that the timestamp actually serves as a marker when the packet(s) need to be played out from the encapsulation function (e.g. to RE, REC or in some use cases to CPRI mapper - exact location _where_ in encaps/mapper is up to the implementation) I would take 1ns is enough. Between timestamps I proposed using sequence numbers. > > Comments? Thoughts? > > - Jouni |