![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> The GPS itself usually expresses time as some integer number of whole > weeks from the epoch (the week of January 6, 1980 being week #0) plus > seconds within the week (there being 604800 seconds in a week). But > nothing says we can't reduce things further to a simple integer count > of seconds from the same epoch. It simplifies calculations, and uses > bits more efficiently too. Make the count 64 bits long, and we won't > have to worry about rollover for some time. I'd like to suggest that there be sub-second resolution. That would make the same time representation useful for those who need to synchronize media sources (like when lip-synching voice and video). This could add another 16 to 24 bits to the length. --karl--
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.