3 ms·
This article from today is somewhat obsolete. MiFID II regulations require absolute accuracy of either 100 microseconds or 1 millisecond depending on certain co
by jeffbee 6y ago
This article from today is somewhat obsolete. MiFID II regulations require absolute accuracy of either 100 microseconds or 1 millisecond depending on certain conditions, and reporting in microseconds. I don't know why they went with microseconds when nanoseconds would have been technically just as practical and far more future-proof.
https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex_en.pdf https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/1...
- lucaspauker 6y agoEurope regulations are different than US regulations and are more stringent, as pointed out in the article you linked. I focused on US rules for the article on my site.
- RyanHamilton 6y ago>>technically just as practical What makes you think that? My experience has been that getting closer to perfection requires increasingly more effort as you approach it. In this case, having a larger limit would allow monitoring and correction in case of an error without any kind of "trip" being triggered.
- lucaspauker 6y agoYou're right. The more fine-tuned it becomes, the more you have to consider low-level protocols. This paper https://nvlpubs.nist.gov/nistpubs/jres/121/jres.121.023.pdf https://nvlpubs.nist.gov/nistpubs/jres/121/jres.121.023.pdf suggests with current systems, time uncertainty can be decreased to about 1-10 us from NIST.
- jeffbee 6y agoIt doesn't really matter if the last three digits are just noise for the time being. It's just as practical, from the programmer's standpoint. 64 bits worth of nanoseconds gives abundant range (±292 years from the origin) and microsecond times already necessitate a 64-bit representation (2^31 microseconds only gets you half an hour). So you can build all your protocols around signed 64-bit nanos from a defined origin and never need to change it again.
- andylynch 6y agoThis has already happens. OUCH and other binary protocols have carried nanoseconds for years. FIX now specifies microseconds be supported in all time stamps but also lets you use nanos or even picos if you and your counterparty really want to.
- guenthert 6y agoThe protocols might had ns resolution, but that doesn't say anything about the accuracy of the time information in there. The PPS output of GPS receivers typically has a jitter of a few ns. And how well is the position of the antenna known?
- dmurray 6y agoNanosecond precision, for future proofing, but millisecond accuracy.
- andylynch 6y agoNanoseconds were mentioned in the draft technical standards for MiFID II but industry and scientific feedback was that mandating nanosecond-level sync to UTC is not feasible to mandate given the current state of the art ( and will be for some time). Common trading protocols like FIX and OUCH do support nanoseconds for time stamps, but the MiFID requirement is in terms of deviation from UTC, so you need to budget and have traceability for the total error between your system, clock, and back to the reference standards - ie UTC(NPL), UTC(NIST) etc. If you’re doing this properly this can well involve visits to your data centre with portable atomic clocks. There’s a really good paper on implementing this from the UK NPL; see https://www.ion.org/publications/abstract.cfm?articleID=13160 https://www.ion.org/publications/abstract.cfm?articleID=1316...