Re: [TICTOC] I-D Action: draft-ietf-tictoc-multi-path-synchronization-01.txt

Tal Mizrahi <> Thu, 23 October 2014 05:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D38991A88CB for <>; Wed, 22 Oct 2014 22:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FjUcw1c_hc6B for <>; Wed, 22 Oct 2014 22:24:03 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 45A161A88CA for <>; Wed, 22 Oct 2014 22:24:03 -0700 (PDT)
Received: from pps.filterd ( []) by (8.14.5/8.14.5) with SMTP id s9N5O3O2021599 for <>; Wed, 22 Oct 2014 22:24:03 -0700
Received: from ([]) by with ESMTP id 1q5y9jbmy9-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <>; Wed, 22 Oct 2014 22:24:02 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 22 Oct 2014 22:24:02 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.913.22; Thu, 23 Oct 2014 08:23:16 +0300
Received: from ([fe80::5d63:81cd:31e2:fc36]) by ([fe80::5d63:81cd:31e2:fc36%20]) with mapi id 15.00.0913.011; Thu, 23 Oct 2014 08:23:16 +0300
From: Tal Mizrahi <>
To: "" <>
Thread-Topic: [TICTOC] I-D Action: draft-ietf-tictoc-multi-path-synchronization-01.txt
Thread-Index: AQHP7f/pbat69rnUG0SNY634bnHOw5w9Jh/w
Date: Thu, 23 Oct 2014 05:23:16 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-10-23_03:2014-10-22,2014-10-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1410230046
Subject: Re: [TICTOC] I-D Action: draft-ietf-tictoc-multi-path-synchronization-01.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Oct 2014 05:24:05 -0000


We have posted an updated draft with minor updates compared to the previous draft.
The most notable update is that section 6 (combining algorithms) is somewhat shorter, as we do not want the draft to mandate a specific combining method(s).


-----Original Message-----
From: TICTOC [] On Behalf Of
Sent: Wednesday, October 22, 2014 4:55 PM
Subject: [TICTOC] I-D Action: draft-ietf-tictoc-multi-path-synchronization-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Timing over IP Connection and Transfer of Clock Working Group of the IETF.

        Title           : Multi-Path Time Synchronization
        Authors         : Alex Shpiner
                          Richard Tse
                          Craig Schelp
                          Tal Mizrahi
	Filename        : draft-ietf-tictoc-multi-path-synchronization-01.txt
	Pages           : 16
	Date            : 2014-10-22

   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

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

TICTOC mailing list