[TICTOC] RFC 8039 on Multipath Time Synchronization

rfc-editor@rfc-editor.org Thu, 08 December 2016 16:45 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E156129FD5; Thu, 8 Dec 2016 08:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdea27fCuX2C; Thu, 8 Dec 2016 08:45:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2BAB129FAA; Thu, 8 Dec 2016 08:45:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EFD9FB80252; Thu, 8 Dec 2016 08:45:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161208164509.EFD9FB80252@rfc-editor.org>
Date: Thu, 8 Dec 2016 08:45:09 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/F5RJlMdL2mi551RY69mMYIMcjZA>
Cc: drafts-update-ref@iana.org, tictoc@ietf.org, rfc-editor@rfc-editor.org
Subject: [TICTOC] RFC 8039 on Multipath Time Synchronization
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2016 16:45:15 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8039

        Title:      Multipath Time Synchronization 
        Author:     A. Shpiner, R. Tse,
                    C. Schelp, T. Mizrahi
        Status:     Experimental
        Stream:     IETF
        Date:       December 2016
        Mailbox:    alexshp@mellanox.com, 
                    Richard.Tse@microsemi.com, 
                    craig.schelp@oracle.com,
                    talmi@marvell.com
        Pages:      17
        Characters: 39763
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tictoc-multi-path-synchronization-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8039

        DOI:        10.17487/RFC8039

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.

This document is a product of the Timing over IP Connection and Transfer of Clock Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC