0% found this document useful (0 votes)
65 views

NTPandPTP A Brief Comparison

NTP and PTP (IEEE 1588) are time transfer protocols that operate 'in band' (with traffic) over Ethernet networks >Both encapsulate time in NTP or PTP packets >Both operate in Master / slave (or server-client) mode. PTP is a time-stamping error log file used for 'application level' synchronization.

Uploaded by

Ashok Dwivedi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
65 views

NTPandPTP A Brief Comparison

NTP and PTP (IEEE 1588) are time transfer protocols that operate 'in band' (with traffic) over Ethernet networks >Both encapsulate time in NTP or PTP packets >Both operate in Master / slave (or server-client) mode. PTP is a time-stamping error log file used for 'application level' synchronization.

Uploaded by

Ashok Dwivedi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

NTP and PTP (IEEE 1588)

A Brief Comparison

NTP vs PTP

In general:
PTP = IEEE 1588 (various flavors & profiles exist)
NTP

Coarse level granularity


Requirement for synchronization guarantee does not exist
Example: time-stamping error log files

PTP

used for application level synchronization

used for precision synchronization

Mission critical applications


Dedicated hardware to minimize on-path issues
High end algorithms and secret sauce to eliminate network & equipment jitter

COPYRIGHT SYMMETRICOM (2010)

PAGE 2

Similarities between PTP & NTP


Both

are time transfer protocols that operate in band (with


traffic) over Ethernet networks
Both encapsulate time in NTP or PTP packets
Both operate in Master / slave (or server-client) mode

COPYRIGHT SYMMETRICOM (2010)

PAGE 3

NTP & PTP compared


Criteria

NTP

PTP (IEEE 1588)

Peak time transfer error

> 1ms (10-3s)

> 100 ns (10-7s)

Primary error source

Routers

Routers, switches, port contention,


o/s stack delay, network etc.

Implementation

Hardware or software
servers; software clients

Hardware masters; hardware or


software clients (slaves)

Mode of operation

Clients pull time from server

Masters push time to slaves


(clients)

On path support

Non existent and not


possible

Not required, but possible through


transparent clocks and boundary
clocks (enhances performance)

Relative cost of solution

Inexpensive

More expensive (higher precision


solutions cost more)

Metrics, monitoring &


management

Exists, but minimal

Extensive in band metrics for


monitoring and management

COPYRIGHT SYMMETRICOM (2010)

PAGE 4

You might also like