Browse Prior Art Database

Multipath Time Synchronization (RFC8039)

IP.com Disclosure Number: IPCOM000248497D
Original Publication Date: 2016-Dec-01
Included in the Prior Art Database: 2016-Dec-09
Document File: 34 page(s) / 40K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Shpiner: AUTHOR [+4]

Abstract

The two most common time synchronization protocols in IP networks are (1) the Network Time Protocol [NTP] and (2) the Precision Time Protocol (PTP) as defined in the IEEE 1588 standard [IEEE1588].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                        A. Shpiner Request for Comments: 8039                                      Mellanox Category: Experimental                                            R. Tse ISSN: 2070-1721                                                Microsemi                                                                C. Schelp                                                                   Oracle                                                               T. Mizrahi                                                                  Marvell                                                            December 2016

                      Multipath Time Synchronization

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 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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for examination, experimental implementation, and    evaluation.

   This document defines an Experimental Protocol for the Internet    community.  This document is a product of the Internet Engineering    Task Force (IETF).  It represents the consensus of the IETF    community.  It has received public review and has been approved for    publication by the Internet Engineering Steering Group (IESG).  Not    all documents approved by the IESG are a candidate for any level of    Internet Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained a...