IEEE 1588 Working Group

Subcommittees 2013-2019

The P1588 Working Group worked on the 2019 edition of the IEEE1588 standard (2013-2019) in subcommittees dedicated to specific aspects of the 2019 revision. Each P1588 Subcommittee consisted of a subset of P1588 WG members that were interested in the specific aspect. The P1588 Subcommittees prepared and recommended proposals for consideration by the P1588 WG.

Maintenance

  • Scope: Incorporate official IEEE interpretations and other known errors or needed clarifications into 1588-2008 in order to provide a clean version as a basis for modifications of the current P1588 working group. Once this is done serve as a ‘quality control’ function for any modifications proposed by other committees to ensure freedom from inconsistencies and backward compatibility issues.
  • Chair: John Eidson and Pat Diamond

Architecture

  • Scope: Organize the content of the standard toward the goal of clarifying the interfaces between IEEE 1588 and technology defined by other organizations. This includes organizations with jurisdiction over profiles as well as transport protocols. The interfaces will also work toward the goal of improving co-existence of different profiles and transport protocols in a synchronized network.
  • Chairs: Douglas Arnold and Rodney Cummings

Management

  • Scope: Define a unified extensible configuration and monitoring of PTP clocks.The managed objects can be accessed by an appropriate management protocol. A goal of the standard revision is “improved co-existence of different profiles and transport protocols in asynchronized network.
  • Chair: Hans Weibel

High Accuracy

  • Scope: Evaluate different and independently useful mechanisms which enable enhancing accuracy of synchronization. The mechanisms may include but are not limited to: 1) performing measurements, calibrations and exchange of parameters needed for enabling higher accuracy; 2) supporting physical layer syntonization.
  • Chairs: John Mackay and Maciej Lipinski

Security

  • Scope: Specify an optional security functionality, the solution may provide multiple mechanisms and will utilize existing mechanisms where possible.
  • Chair: Karen O’Donoghue and Silvana Rodrigues