RFC 8039: Multipath Time Synchronization
In plain English — editorial summary, not part of the RFC
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 multipath 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 multipath approach can significantly contribute to clock accuracy, security, and fault tolerance. The multipath approach that is presented in this document enables backward compatibility with nodes that do not support the multipath functionality.
Document record
- Document ID
- RFC8039
- Published
- December 2016
- Authors
- A. Shpiner; R. Tse; C. Schelp; T. Mizrahi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7384Security Requirements of Time Protocols in Packet Switched NetworksCurrent
October 2014
- RFC 9581Concise Binary Object Representation (CBOR) Tags for Time, Duration, and PeriodCurrent
August 2024
- RFC 7822Network Time Protocol Version 4 (NTPv4) Extension FieldsUpdated
March 2016
- RFC 7821UDP Checksum Complement in the Network Time Protocol (NTP)Updated
March 2016
- RFC 8573Message Authentication Code for the Network Time ProtocolUpdated
June 2019
- RFC 8633Network Time Protocol Best Current PracticesCurrent
July 2019
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 9249A YANG Data Model for NTPCurrent
July 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?