%% You should probably cite rfc8039 instead of this I-D.
@techreport{ietf-tictoc-multi-path-synchronization-06,
    number =    {draft-ietf-tictoc-multi-path-synchronization-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-tictoc-multi-path-synchronization/06/},
    author =    {Alex Shpiner and Richard Tse and Craig Schelp and Tal Mizrahi},
    title =     {{Multi-Path Time Synchronization}},
    pagetotal = 17,
    year =      2016,
    month =     oct,
    day =       6,
    abstract =  {Clock synchronization protocols are very widely used in IP-based networks. The Network Time Protocol (NTP) has been commonly deployed for many years, and the last few years have seen an increasingly rapid deployment of the Precision Time Protocol (PTP). As time- sensitive applications evolve, clock accuracy requirements are becoming increasingly stringent, requiring the time synchronization protocols to provide high accuracy. This memo describes a multi-path approach to PTP and NTP over IP networks, allowing the protocols to run concurrently over multiple communication paths between the master and slave clocks, without modifying these protocols. The multi-path approach can significantly contribute to clock accuracy, security and fault tolerance. The multi-path approach that is presented in this document enables backward compatibility with nodes that do not support the multi-path functionality.},
}