1. Definitions of Managed Objects for PTPv2 Slave Clocks draft-frost-tictoc-ptp-slave-mib-00.txt IETF 78, Maastricht, July 2010 Tim Frost, Greg Dowd – Symmetricom

2. Purpose of Draft Present an outline of a MIB for a PTP Slave Clock Aligned with the PTP Telecom Profile for Frequency Distribution (draft recommendation G.8265.1) Proposes the potential contents of such a MIB Addresses clauses 2.1 and 2.2 of draft-frost- tictoc-management-00

3. Contents of MIB PTP protocol-specific standard data sets – Default, Current, Parent, Time Properties and Port Data Sets Proposes four new data sets: – Slave Status Data Set (contains current status information on the clock servo loop) – Slave Performance Data Set (contains performance information on the clock servo loop) – Alarm Status Data Set (contains the alarm status of the device) – Network Statistics Data Set (contains performance information on the network itself)

4. Issues to be resolved Should this be a general PTPv2 slave MIB, or tailored to a specific application (e.g. G.8265.1 Telecom Profile)? What about a family of MIBs? – PTPv2 “default” slave MIB – Telecom profile MIB – Other profile MIB Should the MIB be restricted to protocol-specified elements (e.g. the standard PTP data sets), or expanded to include other useful information (e.g. performance and status information)?