1 / 4

Precision Time Protocol Version 2 (PTPv2) Management Information Base

Precision Time Protocol Version 2 (PTPv2) Management Information Base. draft-ietf-tictoc-ptp-mib-05.txt IETF 86, Orlando , March 2013 Vinay Shankarkumar, Laurent Montini – Cisco Systems Tim Frost, Greg Dowd – Symmetricom. Overview of Draft. Presents a MIB for a PTP Clock

kolya
Download Presentation

Precision Time Protocol Version 2 (PTPv2) Management Information Base

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 Version 2 (PTPv2) Management Information Base draft-ietf-tictoc-ptp-mib-05.txt IETF 86, Orlando, March 2013 Vinay Shankarkumar, Laurent Montini – Cisco Systems Tim Frost, Greg Dowd – Symmetricom

  2. Overview of Draft • Presents a MIB for a PTP Clock • Concentrates on standard PTP data elements • Associated information such as performance data metrics are to be covered in a separate MIB • PTP protocol-specific standard data sets: • Default, Current, Parent, Time Properties,Port,TC Default and TC Port Data Sets • Covers all types of PTP clocks • ordinary, boundary and transparent clocks • Aims to create a standard method for monitoring PTP clocks

  3. Current Status • Currently at version -05, released 25 Feb 2013 • Draft has received reviews from various people • -01 reviewed by Bert Wijnen • -02 reviewed by Andy Bierman • -03 reviewed by AlunLuchuk and Kevin Gross • Changes from version -03 (presented at last meeting): • Use of 'AutonomousType' import • Use of ptpbasewellKnownTransportTypesand ptpbasewellKnownEncapsulationTypes • Changed some types from Integer32 to use defined textual conventions • Various minor changes to descriptive text

  4. Future Work • Decided to keep MIB read-only • Suggested at ISPCS and IETF85 to make it read-write • Design team consensus is to release this as read-only • A read-write version could follow if sufficient demand • IEEE is proposing a new PAR for IEEE1588 • MIB could become part of the work plan • Important for IETF to propose a finished work. • Design team consensus that the MIB is now stable, and no further changes planned* • Alan Luchuk(SNMP Research) has created an SNMP agent for the MIB, to help people evaluate it • Last call requested on the current version of the draft *apart from a couple of known typos

More Related