Last Call: <draft-ietf-tictoc-multi-path-synchronization-05.txt> (Multi-Path Time Synchronization) to Experimental RFC

The IESG <iesg-secretary@ietf.org> Wed, 14 September 2016 13:23 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-tictoc-multi-path-synchronization-05.txt> (Multi-Path Time Synchronization) to Experimental RFC
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <147385938838.1983.6256743823052514880.idtracker@ietfa.amsl.com>
Date: Wed, 14 Sep 2016 06:23:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/m14CHJY53YtrUbhapvKwF7NSunI>
Cc: draft-ietf-tictoc-multi-path-synchronization@ietf.org, tictoc-chairs@ietf.org, tictoc@ietf.org
Reply-To: ietf@ietf.org

The IESG has received a request from the Timing over IP Connection and
Transfer of Clock WG (tictoc) to consider the following document:
- 'Multi-Path Time Synchronization'
  <draft-ietf-tictoc-multi-path-synchronization-05.txt> as Experimental
RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-09-28. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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. Slave Diversity is a recently
   introduced approach, where the master and slave clocks (also known as
   server and client) are connected through multiple network paths, and
   the slave combines the information received through all paths to
   obtain a higher clock accuracy compared to the conventional one-path
   approach.  This document 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. The
   multi-path approach can significantly contribute to clock accuracy,
   security and fault tolerance. The Multi-Path Precision Time Protocol
   (MPPTP) and Multi-Path Network Time Protocol (MPNTP) define an
   additional layer that extends the existing PTP and NTP without the
   need to modify these protocols. MPPTP and MPNTP also allow backward
   compatibility with nodes that do not support the multi-path
   extension.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tictoc-multi-path-synchronization/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-tictoc-multi-path-synchronization/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2152/
   https://datatracker.ietf.org/ipr/2151/

Last Call: <draft-ietf-tictoc-multi-path-synchron… The IESG