1 / 7

PTP Enterprise Profile

This document from the TICTOC Working Group of IETF discusses the Enterprise Profile for PTP in Enterprise IT Networks, focusing on timestamping event data, measuring latencies, and multi-domain configurations. It outlines master and slave clock operations across different domains.

rrandolph
Download Presentation

PTP 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. Doug Arnold & Heiko Gerstung Meinberg Radio Clocks TICTOC Working Group IETF 91 Honolulu, Nov 2014 Enterprise Profile TICTOC, IETF 91 PTP Enterprise Profile

  2. Enterprise Profile TICTOC, IETF 91 Purpose • PTP Profile for Enterprise IT Networks • Driven by Financial Industry for HFT • Register time of events • Timestamp event data for playback in algorithm development • Measure network and algorithm latencies • Existing PTP Profiles and those under development are tailored toward specialized applications distinct from enterprise networks

  3. Enterprise Profile TICTOC, IETF 91 Current Status • draft-ietf-tictoc-ptp-enterprise-profile-04 • Changes since version 03 • A number of editorial issues identified by Laurent Montini, addresses. Posted to tictoc reflector. • More have been submitted. • Expanded description of the use of multiple domains to support multiple simultaneous masters has been added. • Note: Domains to support multi-master operation has also been proposed in the IEEE 1588 Working Group

  4. Enterprise Profile TICTOC, IETF 91 Multiple Domains • Preferred Master clocks SHOULD move to another domain if they are not the best master • BCs and syntonizing TCs SHOULD support multiple domains • Maintain separate servo loops and spanning trees for each • Slave clocks SHOULD operate multiple independent OCs • Each in a different domain • Time ensembling, voting, etc. outside of PTP

  5. Enterprise Profile TICTOC, IETF 91 Master Domain Selection • For each configured domain • If I am the best clock • While still the best clock • Stay in this domain • End while • End if • End for

  6. Enterprise Profile TICTOC, IETF 91 Multi-Domain Slave Clock Slave clock timing subsystem (outside of PTP) Integrity checking, voting, ensembling independent OC instantiations OC (slave state) Domain 0 OC (slave state) Domain 2 OC (slave state) Domain 1 Arrows indicate Direction of flow Of timing information Network port Network port Network

  7. Enterprise Profile TICTOC, IETF 91 Thank you for your attention • Please review document and post comments on the reflector • Authors • Doug Arnold: doug.Arnold@meinberg-usa.com • Heiko Gerstung: heiko.gerstung@meinberg.de

More Related