1 / 5

Precision Time Protocol Enterprise Profile

This document outlines the draft for the Enterprise Profile of the Precision Time Protocol (PTP), designed specifically for IT networks. It highlights the increasing adoption by high-frequency trading firms and the support of various PTP equipment vendors. Key features include Layer 3 implementation, support for both IPv4 and IPv6, and methods for end-to-end delay requests. The draft addresses the unique needs of enterprise environments and aims to balance interoperability with a broad range of use cases. Feedback from industry experts has informed this draft, which seeks to align with the goals of precision time synchronization.

yvonne
Télécharger la présentation

Precision Time Protocol Enterprise Profile

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Precision Time Protocol Enterprise Profile draft-ietf-tictoc-ptp-enterprise-profile-02.txt IETF 86, Orlando, March 2013 Doug Arnold, Symmetricom Heiko Gerstung, Meinberg

  2. Overview of Draft • Designed for Enterprise IT networks • Early adopters of PTP in enterprise are High Frequency Trading Firms • At least two PTP equipment vendors currently support most of proposed profile as proprietary solutions • Originally proposed by Network Architect from IMF • Major PTP properties • Layer 3 • IPv4 or IPv6 • End to end delay request mechanism • Multicast sync and announce messages • Delay requests/responses can be multicast or unicast • Unicastrecommended • No unicastnegociation

  3. Current Status • First draft submitted to IETF TICTOC for comments • 74 comments posted (though some are repeats) • Thanks to Laurent Montini, Tal Mizrahi, John Fletcher, John Eidson, Silvana Rodrigues, Stefano Ruffini, Samer Darras for reviewing draft • Expect to submit updated draft before next IETF meeting, addressing all comments

  4. General Comments Q: What is specific to enterprise networks to require a profile? A: PTP has a large number of options • not all compatible • does not work well without making choices • Many enterprise system designers requesting a similar configuration Q: Does the proposed profile contain too many options and modes? A: We want to cover as many use cases as possible, as long as Enterprise profile compliant clocks will interoperate.

  5. General Comments (cont) Q: Where does ±1 µs requirement come from? A: Commonly sited as a desirable and achievable goal for PTP systems. • For example ISPCS 2011 Keynote Address: “Time Synchronization and Financial Trading,” Peter Lankford, Securities Technologies Analysis Center Q: Without unicast negotiation, how will message rates be determined? A: Message rates will be determined by configuring each ports. Master ports will answer delay requests to the best of their ability. • Less robust than telecom profile • Less configuration required than telecom profile

More Related