Precision Time Protocol Version 2 (PTPv2) Management Information Base
RFC 8173
| Document | Type | RFC - Proposed Standard (June 2017; No errata) | |
|---|---|---|---|
| Authors | Vinay Shankarkumar , Laurent Montini , Tim Frost , Greg Dowd | ||
| Last updated | 2018-12-20 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Karen O'Donoghue | ||
| Shepherd write-up | Show (last changed 2015-08-13) | ||
| IESG | IESG state | RFC 8173 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Suresh Krishnan | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) V. Shankarkumar
Request for Comments: 8173 L. Montini
Category: Standards Track Cisco Systems
ISSN: 2070-1721 T. Frost
Calnex Solutions Ltd.
G. Dowd
Microsemi
June 2017
Precision Time Protocol Version 2 (PTPv2)
Management Information Base
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in internets based on TCP
or IP. In particular, it defines objects for managing networks using
the Precision Time Protocol (PTP), specified in IEEE Std. 1588-2008.
This memo specifies a MIB module in a manner that is both compliant
to the Structure of Management Information version 2 (SMIv2) and
semantically identical to the peer SMIv1 definitions.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8173.
Shankarkumar, et al. Standards Track [Page 1]
RFC 8173 PTPv2 MIB June 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
1.1. Relationship to Other Profiles and MIBs ....................3
2. The SNMP Management Framework ...................................4
3. Overview ........................................................4
4. PTP MIB Definition ..............................................5
5. Security Considerations ........................................59
6. IANA Considerations ............................................61
7. References .....................................................62
7.1. Normative References ......................................62
7.2. Informative References ....................................63
Acknowledgements ..................................................63
Author's Addresses ................................................64
Shankarkumar, et al. Standards Track [Page 2]
RFC 8173 PTPv2 MIB June 2017
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
module for use with network management protocols in the Internet
community. In particular, it describes managed objects used for
managing PTP devices including ordinary clocks, transparent clocks,
and boundary clocks.
This MIB module is restricted to reading standard PTP data elements,
as described in [IEEE-1588-2008]. This enables it to monitor the
operation of PTP clocks within the network. It is envisioned that
this MIB module will complement other managed objects to be defined
that will provide more detailed information on the performance of PTP
clocks supporting the Telecom Profile defined in [G.8265.1] and any
future profiles that may be defined. Those objects are considered
out of scope for the current document.
Similarly, this MIB module is read-only and not intended to provide
the ability to configure PTP clocks. Since PTP clocks are often
embedded in other network elements such as routers, switches, and
gateways, this ability is generally provided via the configuration
interface for the network element.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text