Tweet This is a modified version of the Internet RFC suitable for machine-translating. Original version is available here: RFC8173
Ad
PROPOSED STANDARD
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.
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.
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 "OPTIONAL" in this document are to be interpreted as described in BCP14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.
This MIB module is intended to be used with the default PTP profile described in [IEEE-1588-2008] when running over the IP network layer. As stated above, it is envisioned that this MIB module will complement other managed objects to be defined to monitor and measure the performance of PTP clocks supporting specific PTP profiles, e.g., the Telecom Profile defined in [G.8265.1].
Some other PTP profiles have their own MIB modules defined as part of the profile, and this MIB module is not intended to replace those MIB modules.
Shankarkumar, et al. Standards Track [Page 3]
RFC 8173 PTPv2 MIB June 20172. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410[RFC3410].
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 2579[RFC2579] and STD 58, RFC 2580[RFC2580].
Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
Overview of PTP version 2 (IEEE Std. 1588-2008)
[IEEE-1588-2008] defines a protocol enabling precise synchronization of clocks in measurement and control systems implemented with packet-based networks, the Precision Time Protocol version 2 (PTPv2). This MIB module does not address PTPv1, the earlier version defined in IEEE Std. 1588-2002. The protocol is applicable to network elements communicating using IP. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock.
The protocol supports system-wide synchronization accuracy in the sub-microsecond range with minimal network and local clock computing resources. [IEEE-1588-2008] uses UDP/IP or Ethernet and can be adapted to other mappings. It includes formal mechanisms for message extensions, higher sampling rates, correction for asymmetry, a clock type to reduce error accumulation in large topologies, and specifications on how to incorporate the resulting additional data into the synchronization protocol. [IEEE-1588-2008] also defines conformance and management capability.
MIB description
This MIB module supports the Precision Time Protocol version 2 (PTPv2, hereafter designated as PTP) features of network element system devices, when using the default PTP profile described in [IEEE-1588-2008] when running over the IP network layer.
It is envisioned that this MIB module will complement other managed objects to be defined to monitor and measure the performance of the PTP devices and telecom clocks supporting specific PTP profiles. Some other PTP profiles have their own MIB modules defined as part of the profile, and this MIB module is not intended to replace those MIB modules.
Abbreviations: E2E End-to-End EUI Extended Unique Identifier GPS Global Positioning System IANA Internet Assigned Numbers Authority IP Internet Protocol NTP Network Time Protocol (see [RFC5905]) P2P Peer-to-Peer PTP Precision Time Protocol TAI International Atomic Time UDP User Datagram Protocol UTC Coordinated Universal Time
References:
[IEEE-1588-2008] IEEE Standard for A Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE Std. 1588-2008, July 2008.
The below table specifies the object formats of the various textual conventions used.
Data type mapping Textual Convention SYNTAX
------------------- --------------------- ------------------
5.3.2 TimeInterval PtpClockTimeInterval OCTET
"The Domain is identified by an integer, the domainNumber, in the range of 0 to 255. An integer value that is used to assign each PTP device to a particular domain."
REFERENCE "Section 7.1 ('Domains') and Table 2 ('domainNumber')
of [IEEE-1588-2008]"
SYNTAX Unsigned32 (0..255)
PtpClockIdentity ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"The clock identity is an 8-octet array and will be presented in the form of a character array. Network byte order is assumed.
The value of the PtpClockIdentity should be taken from the IEEE EUI-64 individual assigned numbers as indicated in Section 7.5.2.2.2 of [IEEE-1588-2008]. It can also be a non-EUI-64 address as defined in Section 7.5.2.2.3 of [IEEE-1588-2008].
The clock identifier can be constructed from existing EUI-48 assignments."
"The clock type based on whether end-to-end or peer-to-peer mechanisms are used. The mechanism used to calculate the Mean Path Delay as indicated in Table 9 of [IEEE-1588-2008]."
REFERENCE
"Sections 8.2.5.4.4 ('portDS.delayMechanism'), 6.6.4 ('Measuring link propagation delay in clocks supporting peer-to-peer path correction'), and 7.4.2 ('communication Path asymmetry') of [IEEE-1588-2008]."
SYNTAX INTEGER {
e2e(1), p2p(2), disabled(254) }
PtpClockPortNumber ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An index identifying a specific PTP port on a PTP node."
REFERENCE
"Sections 7.5.2.3 ('portNumber') and 5.3.5 ('PortIdentity') of [IEEE-1588-2008]"
SYNTAX Unsigned32 (0..65535)
PtpClockPortState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This is the value of the current state of the protocol engine associated with this port."
REFERENCE
"Sections 8.2.5.3.1 ('portState') and 9.2.5 ('State machines')
"The clock port transport protocol address used for this
communication between the clock nodes. This is a string corresponding to the address type as specified by the transport type used. The transport types can be defined elsewhere, in addition to the ones defined in this document. This can be an address of type IP version 4, IP version 6, Ethernet, DeviceNET, ControlNET, or IEC61158. The OCTET STRING representation of the OID of ptpbaseWellKnownTransportTypes will be used in the values contained in the OCTET STRING."
REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet),
Annex G (DeviceNET), Annex H (ControlNET), and
Annex I (IEC61158) of [IEEE-1588-2008]"
SYNTAX OCTET STRING (SIZE (1..255))
PtpClockProfileType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Clock Profile used. A profile is the set of allowed PTP features applicable to a device."
REFERENCE "Sections 3.1.30 ('profile') and 19.3 ('PTP
profiles') of [IEEE-1588-2008]"
SYNTAX INTEGER {
default(1),
"This textual convention corresponds to the TimeInterval structure indicated in Section 5.3.2 of [IEEE-1588-2008]. It will be presented in the form of a character array. Network byte order is assumed."
REFERENCE
"Sections 5.3.2 ('TimeInterval') and 7.7.2.1 ('Timer interval
specification') of [IEEE-1588-2008]"
SYNTAX OCTET STRING (SIZE (1..255))
SYNTAX SEQUENCE OF PtpbaseSystemEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of count information about the PTP system for all domains."
::= { ptpbaseMIBSystemInfo 1 }
ptpbaseSystemEntry OBJECT-TYPE
SYNTAX PtpbaseSystemEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains count information about a single domain. New row entries are added when the PTP clock for this domain is configured, while the unconfiguration of the PTP clock removes them."
INDEX {
ptpDomainIndex, ptpInstanceIndex
}
::= { ptpbaseSystemTable 1 }
SYNTAX PtpClockDomainType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the domain number used to create a logical group of PTP devices. The Clock Domain is a logical group of clocks and devices that synchronize with each other using the PTP protocol.
SYNTAX PtpClockInstanceType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the instance of the clock for this domain."
::= { ptpbaseSystemEntry 2 }
ptpDomainClockPortsTotal OBJECT-TYPE
SYNTAX Gauge32
UNITS "ptp ports"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the total number of clock ports configured within a domain in the system."
::= { ptpbaseSystemEntry 3 }
ptpbaseSystemDomainTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseSystemDomainEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP system for all clock modes -- ordinary, boundary, or transparent."
::= { ptpbaseMIBSystemInfo 2 }
ptpbaseSystemDomainEntry OBJECT-TYPE
SYNTAX PtpbaseSystemDomainEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single clock mode for the PTP system. A row entry gets added when PTP clocks are configured on the node." INDEX { ptpbaseSystemDomainClockTypeIndex } ::= { ptpbaseSystemDomainTable 1 }
RFC 8173 PTPv2 MIB June 2017
SYNTAX PtpClockType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the clock type as defined in the textual convention description."
::= { ptpbaseSystemDomainEntry 1 }
ptpbaseSystemDomainTotals OBJECT-TYPE
SYNTAX Unsigned32
UNITS "domains"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the total number of PTP domains for this particular clock type configured in this node."
::= { ptpbaseSystemDomainEntry 2 }
ptpbaseSystemProfile OBJECT-TYPE
SYNTAX PtpClockProfileType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the PTP profile implemented on the system."
REFERENCE "Section 19.3 ('PTP profiles')
of [IEEE-1588-2008]"
::= { ptpbaseMIBSystemInfo 3 }
ptpbaseClockCurrentDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockCurrentDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP clock currentDS for all domains."
::= { ptpbaseMIBClockInfo 1 }
ptpbaseClockCurrentDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockCurrentDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP clock currentDS for a domain."
REFERENCE
"Section 8.2.2 ('currentDS data set member specifications') of [IEEE-1588-2008]"
SYNTAX Unsigned32
UNITS "Steps"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current clock dataset stepsRemoved value.
This object specifies the distance measured by the number of boundary clocks between the local clock and the foreign master as indicated in the stepsRemoved field of Announce messages."
REFERENCE
"Section 8.2.2.2 ('stepsRemoved') of [IEEE-1588-2008]"
::= { ptpbaseClockCurrentDSEntry 4 }
ptpbaseClockCurrentDSOffsetFromMaster OBJECT-TYPE
SYNTAX PtpClockTimeInterval
UNITS "Time Interval"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the current clock dataset ClockOffset value. The value of the computation of the offset in time between a slave and a master clock."
REFERENCE
"Section 8.2.2.3 ('currentDS.offsetFromMaster') of [IEEE-1588-2008]"
::= { ptpbaseClockCurrentDSEntry 5 }
ptpbaseClockCurrentDSMeanPathDelay OBJECT-TYPE
SYNTAX PtpClockTimeInterval
UNITS "Time Interval"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the current clock dataset MeanPathDelay value.
The mean path delay between a pair of ports as measured by the delay request-response mechanism."
REFERENCE
"Section 8.2.2.4 ('currentDS.meanPathDelay') of [IEEE-1588-2008]"
::= { ptpbaseClockCurrentDSEntry 6 }
SYNTAX SEQUENCE OF PtpbaseClockParentDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP clock parentDS for all domains."
::= { ptpbaseMIBClockInfo 2 }
ptpbaseClockParentDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockParentDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP clock parentDS for a domain."
REFERENCE
"Section 8.2.3 ('parentDS data set member specifications') of [IEEE-1588-2008]"
INDEX {
ptpbaseClockParentDSDomainIndex, ptpbaseClockParentDSClockTypeIndex, ptpbaseClockParentDSInstanceIndex
}
::= { ptpbaseClockParentDSTable 1 }
SYNTAX OCTET STRING(SIZE(1..256))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the value of portIdentity of the port on the master that issues the Sync messages used in synchronizing this clock."
REFERENCE
"Section 8.2.3.2 ('parentDS.parentPortIdentity') of
[IEEE-1588-2008]"
::= { ptpbaseClockParentDSEntry 4 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the parentDS ParentStats value.
This value indicates whether the values of ParentDSOffset and ParentDSClockPhChRate have been measured and are valid. A TRUE value shall indicate valid data."
REFERENCE
"Section 8.2.3.3 ('parentDS.parentStats') of [IEEE-1588-2008]"
::= { ptpbaseClockParentDSEntry 5 }
ptpbaseClockParentDSOffset OBJECT-TYPE
SYNTAX PtpClockIntervalBase2 (-128..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the parentDS ParentOffsetScaledLogVariance value.
This value is the variance of the parent clock's phase as measured by the local clock."
REFERENCE
"Section 8.2.3.4 ('parentDS.observedParentOffsetScaledLogVariance') of [IEEE-1588-2008]"
::= { ptpbaseClockParentDSEntry 6 }
ptpbaseClockParentDSClockPhChRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the clock's parentDS ParentClockPhaseChangeRate value.
This value is an estimate of the parent clock's phase change rate as measured by the slave clock."
REFERENCE
"Section 8.2.3.5 ('parentDS.observedParentClockPhaseChangeRate') of [IEEE-1588-2008]"
::= { ptpbaseClockParentDSEntry 7 }
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the parentDS grandmaster clock quality offset."
REFERENCE
"Section 8.2.3.7 ('parentDS.grandmasterClockQuality') of
[IEEE-1588-2008]"
::= { ptpbaseClockParentDSEntry 13 }
ptpbaseClockDefaultDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockDefaultDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP clock defaultDS for all domains."
::= { ptpbaseMIBClockInfo 3 }
ptpbaseClockDefaultDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockDefaultDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP clock defaultDS for a domain."
INDEX {
ptpbaseClockDefaultDSDomainIndex, ptpbaseClockDefaultDSClockTypeIndex, ptpbaseClockDefaultDSInstanceIndex
}
::= { ptpbaseClockDefaultDSTable 1 }
SYNTAX SEQUENCE OF PtpbaseClockRunningEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP clock running datasets for all domains."
::= { ptpbaseMIBClockInfo 4 }
ptpbaseClockRunningEntry OBJECT-TYPE
SYNTAX PtpbaseClockRunningEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP clock running dataset for a domain."
INDEX {
ptpbaseClockRunningDomainIndex, ptpbaseClockRunningClockTypeIndex, ptpbaseClockRunningInstanceIndex
}
::= { ptpbaseClockRunningTable 1 }
RFC 8173 PTPv2 MIB June 2017
SYNTAX PtpClockDomainType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the domain number used to create a logical group of PTP devices."
::= { ptpbaseClockRunningEntry 1 }
ptpbaseClockRunningClockTypeIndex OBJECT-TYPE
SYNTAX PtpClockType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the clock type as defined in the textual convention description."
::= { ptpbaseClockRunningEntry 2 }
ptpbaseClockRunningInstanceIndex OBJECT-TYPE
SYNTAX PtpClockInstanceType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the instance of the clock for this clock type in the given domain."
::= { ptpbaseClockRunningEntry 3 }
ptpbaseClockRunningState OBJECT-TYPE
SYNTAX PtpClockStateType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the clock state returned by a PTP engine."
::= { ptpbaseClockRunningEntry 4 }
ptpbaseClockRunningPacketsSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the total number of all unicast and multicast packets that have been sent out for this clock in this domain for this type. These counters are discontinuous."
::= { ptpbaseClockRunningEntry 5 }
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the total number of all unicast and multicast packets that have been received for this clock in this domain for this type. These counters are discontinuous."
::= { ptpbaseClockRunningEntry 6 }
ptpbaseClockTimePropertiesDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockTimePropertiesDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP clock timePropertiesDS for all domains."
::= { ptpbaseMIBClockInfo 5 }
ptpbaseClockTimePropertiesDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockTimePropertiesDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP clock timePropertiesDS for a domain."
REFERENCE
"Section 8.2.4 ('timePropertiesDS data set member specifications') of [IEEE-1588-2008]"
INDEX {
ptpbaseClockTimePropertiesDSDomainIndex, ptpbaseClockTimePropertiesDSClockTypeIndex, ptpbaseClockTimePropertiesDSInstanceIndex
}
::= { ptpbaseClockTimePropertiesDSTable 1 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the timePropertiesDS value of whether the current UTC offset is valid."
REFERENCE
"Section 8.2.4.2 ('timePropertiesDS.currentUtcOffset') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 4 }
DESCRIPTION
"This object specifies the timePropertiesDS value of the current UTC offset.
In PTP systems whose epoch is the PTP epoch, the value of timePropertiesDS.currentUtcOffset is the offset between TAI and UTC; otherwise, the value has no meaning. The value shall be in units of seconds."
REFERENCE
"Section 8.2.4.3 ('timePropertiesDS.currentUtcOffsetValid') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 5 }
ptpbaseClockTimePropertiesDSLeap59 OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the Leap59 value in the clock currentDS."
REFERENCE
"Section 8.2.4.4 ('timePropertiesDS.leap59') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 6 }
ptpbaseClockTimePropertiesDSLeap61 OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the Leap61 value in the clock currentDS."
REFERENCE
"Section 8.2.4.5 ('timePropertiesDS.leap61') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 7 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the Time Traceable value in the clock currentDS."
REFERENCE
"Section 8.2.4.6 ('timePropertiesDS.timeTraceable') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 8 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the Frequency Traceable value in the clock currentDS."
REFERENCE
"Section 8.2.4.7 ('timePropertiesDS.frequencyTraceable') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 9 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the PTP Timescale value in the clock currentDS."
REFERENCE
"Section 8.2.4.8 ('timePropertiesDS.ptpTimescale') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 10 }
ptpbaseClockTimePropertiesDSSource OBJECT-TYPE
SYNTAX PtpClockTimeSourceType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the Timesource value in the clock currentDS."
REFERENCE
"Section 8.2.4.9 ('timePropertiesDS.timeSource') of [IEEE-1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 11 }
ptpbaseClockTransDefaultDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockTransDefaultDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the PTP transparentClockDefaultDS for all domains."
::= { ptpbaseMIBClockInfo 6 }
SYNTAX PtpbaseClockTransDefaultDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single PTP transparent clock defaultDS for a domain."
REFERENCE
"Section 8.3.2 ('transparentClockDefaultDS data set member specifications') of [IEEE-1588-2008]"
INDEX {
ptpbaseClockTransDefaultDSDomainIndex, ptpbaseClockTransDefaultDSInstanceIndex
}
::= { ptpbaseClockTransDefaultDSTable 1 }
DESCRIPTION
"This object specifies the value of the clockIdentity attribute of the local clock."
REFERENCE
"Section 8.3.2.2.1 ('transparentClockDefaultDS.clockIdentity') of [IEEE-1588-2008]"
::= { ptpbaseClockTransDefaultDSEntry 3 }
ptpbaseClockTransDefaultDSNumOfPorts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the number of PTP ports of the device.
These counters are discontinuous."
REFERENCE
"Section 8.3.2.2.2 ('transparentClockDefaultDS.numberPorts') of [IEEE-1588-2008]"
::= { ptpbaseClockTransDefaultDSEntry 4 }
ptpbaseClockTransDefaultDSDelay OBJECT-TYPE
SYNTAX PtpClockMechanismType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object, if the transparent clock is an end-to-end transparent clock, has the value of e2e; if the transparent clock is a peer-to-peer transparent clock, the value is p2p."
REFERENCE
"Section 8.3.2.3.1 ('transparentClockDefaultDS.delayMechanism') of [IEEE-1588-2008]"
::= { ptpbaseClockTransDefaultDSEntry 5 }
SYNTAX PtpClockDomainType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the value of the primary syntonization domain. The initialization value is 0."
REFERENCE
"Section 8.3.2.3.2 ('transparentClockDefaultDS.primaryDomain') of [IEEE-1588-2008]"
::= { ptpbaseClockTransDefaultDSEntry 6 }
SYNTAX SEQUENCE OF PtpbaseClockPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the clock ports for a particular domain."
::= { ptpbaseMIBClockInfo 7 }
ptpbaseClockPortEntry OBJECT-TYPE
SYNTAX PtpbaseClockPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single clock port."
INDEX {
ptpbaseClockPortDomainIndex, ptpbaseClockPortClockTypeIndex, ptpbaseClockPortClockInstanceIndex, ptpbaseClockPortTablePortNumberIndex
}
::= { ptpbaseClockPortTable 1 }
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the current peer's network address type
used for PTP communication."
::= { ptpbaseClockPortEntry 8 }
ptpbaseClockPortCurrentPeerAddress OBJECT-TYPE
SYNTAX PtpClockPortTransportTypeAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the current peer's network address used for PTP communication."
::= { ptpbaseClockPortEntry 9 }
ptpbaseClockPortNumOfAssociatedPorts OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the following: For a master port - the number of PTP slave sessions (peers) associated with this PTP port. For a slave port - the number of masters available to this slave port (might or might not be peered)."
::= { ptpbaseClockPortEntry 10 }
ptpbaseClockPortDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockPortDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the clock's portDS for a particular domain."
::= { ptpbaseMIBClockInfo 8 }
SYNTAX PtpbaseClockPortDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains portDS information for a single clock port."
INDEX {
ptpbaseClockPortDSDomainIndex, ptpbaseClockPortDSClockTypeIndex, ptpbaseClockPortDSClockInstanceIndex, ptpbaseClockPortDSPortNumberIndex
}
::= { ptpbaseClockPortDSTable 1 }
SYNTAX PtpClockMechanismType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the delay mechanism used. If the clock is an end-to-end clock, the value is e2e; if the clock is a peer to-peer clock, the value is p2p."
::= { ptpbaseClockPortDSEntry 12 }
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the type of encapsulation if the interface is adding extra layers (e.g., VLAN or Pseudowire encapsulation) for the PTP messages."
::= { ptpbaseClockPortRunningEntry 10 }
ptpbaseClockPortRunningTxMode OBJECT-TYPE
SYNTAX PtpClockTxModeType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the clock transmission mode as: unicast: Using unicast communication channel multicast: Using multicast communication channel multicast-mix: Using multicast-unicast communication channel"
::= { ptpbaseClockPortRunningEntry 11 }
ptpbaseClockPortRunningRxMode OBJECT-TYPE
SYNTAX PtpClockTxModeType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the clock receive mode as: unicast: Using unicast communication channel multicast: Using multicast communication channel multicast-mix: Using multicast-unicast communication channel"
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the packets received on the clock port (cumulative). These counters are discontinuous."
::= { ptpbaseClockPortRunningEntry 13 }
ptpbaseClockPortRunningPacketsSent OBJECT-TYPE
SYNTAX Counter64
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the packets sent on the clock port (cumulative). These counters are discontinuous."
::= { ptpbaseClockPortRunningEntry 14 }
ptpbaseClockPortTransDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockPortTransDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about the transparentClockPortDS for a particular domain."
::= { ptpbaseMIBClockInfo 10 }
ptpbaseClockPortTransDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockPortTransDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains clock port transparent dataset information about a single clock port."
INDEX {
ptpbaseClockPortTransDSDomainIndex, ptpbaseClockPortTransDSInstanceIndex, ptpbaseClockPortTransDSPortNumberIndex
}
::= { ptpbaseClockPortTransDSTable 1 }
DESCRIPTION
"This object specifies the value of the PortIdentity attribute of the local port."
REFERENCE
"Section 8.3.3.2.1 ('transparentClockPortDS.portIdentity') of [IEEE-1588-2008]"
::= { ptpbaseClockPortTransDSEntry 4 }
SYNTAX PtpClockIntervalBase2
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the value of the logarithm to the base 2 of the minPdelayReqInterval."
REFERENCE
"Section 8.3.3.3.1 ('transparentClockPortDS.logMinPdelayReqInterval') of [IEEE-1588-2008]"
::= { ptpbaseClockPortTransDSEntry 5 }
ptpbaseClockPortTransDSFaultyFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the value TRUE if the port is faulty and FALSE if the port is operating normally."
REFERENCE
"Section 8.3.3.3.2 ('transparentClockPortDS.faultyFlag') of [IEEE-1588-2008]"
::= { ptpbaseClockPortTransDSEntry 6 }
SYNTAX PtpClockTimeInterval
UNITS "Time Interval"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies, if the delayMechanism used is p2p, the value of the estimate of the current one-way propagation delay, i.e., <meanPathDelay> on the link attached to this port, computed using the peer delay mechanism. If the value of the delayMechanism used is e2e, then the value will be zero."
REFERENCE
"Section 8.3.3.3.3 ('transparentClockPortDS.peerMeanPathDelay') of [IEEE-1588-2008]"
::= { ptpbaseClockPortTransDSEntry 7 }
SYNTAX SEQUENCE OF PtpbaseClockPortAssociateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about a given port's associated ports.
For a master port: multiple slave ports that have established
sessions with the current master port.
For a slave port: the list of masters available for a given
slave port.
Session information (packets, errors) to be displayed based on availability and scenario."
::= { ptpbaseMIBClockInfo 11 }
-- -- Well Known transport types for PTP communication. -- ptpbaseWellKnownTransportTypes OBJECT IDENTIFIER ::= { ptpbaseMIBClockInfo 12 }
ptpbaseTransportTypeIPversion4 OBJECT-IDENTITY STATUS current DESCRIPTION
"IP version 4"
::= { ptpbaseWellKnownTransportTypes 1 }
ptpbaseTransportTypeIPversion6 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"IP version 6"
::= { ptpbaseWellKnownTransportTypes 2 }
ptpbaseTransportTypeEthernet OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Ethernet"
::= { ptpbaseWellKnownTransportTypes 3 }
ptpbaseTransportTypeDeviceNET OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Device NET"
::= { ptpbaseWellKnownTransportTypes 4 }
ptpbaseTransportTypeControlNET OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Control NET"
::= { ptpbaseWellKnownTransportTypes 5 }
ptpbaseTransportTypeIEC61158 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"IEC61158"
::= { ptpbaseWellKnownTransportTypes 6 }
-- -- Well Known encapsulation types for PTP communication. -- ptpbaseWellKnownEncapsulationTypes OBJECT IDENTIFIER ::= { ptpbaseMIBClockInfo 13 }
ptpbaseEncapsulationTypeEthernet OBJECT-IDENTITY STATUS current DESCRIPTION
"Ethernet Encapsulation type."
::= { ptpbaseWellKnownEncapsulationTypes 1 }
ptpbaseEncapsulationTypeVLAN OBJECT-IDENTITY
STATUS current DESCRIPTION
"VLAN Encapsulation type."
::= { ptpbaseWellKnownEncapsulationTypes 2 }
ptpbaseEncapsulationTypeUDPIPLSP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"UDP/IP over MPLS Encapsulation type."
::= { ptpbaseWellKnownEncapsulationTypes 3 }
ptpbaseEncapsulationTypePWUDPIPLSP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"UDP/IP Pseudowire over MPLS Encapsulation type."
::= { ptpbaseWellKnownEncapsulationTypes 4 }
ptpbaseEncapsulationTypePWEthernetLSP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Ethernet Pseudowire over MPLS Encapsulation type."
::= { ptpbaseWellKnownEncapsulationTypes 5 }
ptpbaseClockPortAssociateEntry OBJECT-TYPE
SYNTAX PtpbaseClockPortAssociateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table entry that contains information about a single associated port for the given clock port."
INDEX {
ptpClockPortCurrentDomainIndex, ptpClockPortCurrentClockTypeIndex, ptpClockPortCurrentClockInstanceIndex, ptpClockPortCurrentPortNumberIndex, ptpbaseClockPortAssociatePortIndex
}
::= { ptpbaseClockPortAssociateTable 1 }
SYNTAX PtpClockType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the given port's clock type."
::= { ptpbaseClockPortAssociateEntry 2 }
ptpClockPortCurrentClockInstanceIndex OBJECT-TYPE
SYNTAX PtpClockInstanceType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the instance of the clock for this clock type in the given domain."
::= { ptpbaseClockPortAssociateEntry 3 }
ptpClockPortCurrentPortNumberIndex OBJECT-TYPE
SYNTAX PtpClockPortNumber
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the PTP portNumber for the given port."
::= { ptpbaseClockPortAssociateEntry 4 }
ptpbaseClockPortAssociatePortIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the associated port's serial number in the current port's context."
::= { ptpbaseClockPortAssociateEntry 5 }
ptpbaseClockPortAssociateAddressType OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the peer port's network address type used for PTP communication. The OCTET STRING representation of the OID of ptpbaseWellKnownTransportTypes will be used in the values contained in the OCTET STRING."
::= { ptpbaseClockPortAssociateEntry 6 }
"Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide system-level information of clock devices. Such devices can only be monitored using this MIB module.
The module is implemented with support for read-only. In other words, only monitoring is available by implementing this
MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS { ptpbaseMIBSystemInfoGroup }
::= { ptpbaseMIBCompliances 1 }
ptpbaseMIBCompliancesClockInfo MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide clock-related information. Such devices can only be monitored using this MIB module.
The module is implemented with support for read-only. In other words, only monitoring is available by implementing this
MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
"Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide clock-port-related information. Such devices can only be monitored using this MIB module.
The module is implemented with support for read-only. In other words, only monitoring is available by implementing this
MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
"Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide transparent-clock-related information. Such devices can only be monitored using this MIB module.
The module is implemented with support for read-only. In other words, only monitoring is available by implementing this
MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS {
"Group that aggregates objects describing information on peer PTP ports for a given PTP clock port"
::= { ptpbaseMIBGroups 12 }
END
Shankarkumar, et al. Standards Track [Page 58]
RFC 8173 PTPv2 MIB June 20175. Security Considerations
There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP.
These are the tables and objects and their sensitivity/vulnerability:
ptpDomainClockPortsTotal, ptpbaseSystemDomainTotals, and ptpbaseSystemProfile expose general information about the clock system.
ptpbaseClockRunningState, ptpbaseClockRunningPacketsSent, and ptpbaseClockRunningPacketsReceived expose a clock's current running status.
ptpbaseClockCurrentDSStepsRemoved, ptpbaseClockCurrentDSOffsetFromMaster, and ptpbaseClockCurrentDSMeanPathDelay expose the values of a clock's current dataset (currentDS).
ptpbaseClockParentDSParentPortIdentity, ptpbaseClockParentDSParentStats, ptpbaseClockParentDSOffset, ptpbaseClockParentDSClockPhChRate, ptpbaseClockParentDSGMClockIdentity, ptpbaseClockParentDSGMClockPriority1, ptpbaseClockParentDSGMClockPriority2, ptpbaseClockParentDSGMClockQualityClass, ptpbaseClockParentDSGMClockQualityAccuracy, and ptpbaseClockParentDSGMClockQualityOffset expose the values of a clock's parent dataset (parentDS).
ptpbaseClockDefaultDSTwoStepFlag, ptpbaseClockDefaultDSClockIdentity, ptpbaseClockDefaultDSPriority1, ptpbaseClockDefaultDSPriority2, ptpbaseClockDefaultDSSlaveOnly, ptpbaseClockDefaultDSQualityClass, ptpbaseClockDefaultDSQualityAccuracy, and ptpbaseClockDefaultDSQualityOffset expose the values of a clock's default dataset (defaultDS). ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid, ptpbaseClockTimePropertiesDSCurrentUTCOffset, ptpbaseClockTimePropertiesDSLeap59, ptpbaseClockTimePropertiesDSLeap61, ptpbaseClockTimePropertiesDSTimeTraceable, ptpbaseClockTimePropertiesDSFreqTraceable, ptpbaseClockTimePropertiesDSPTPTimescale, and ptpbaseClockTimePropertiesDSSource expose the values of a clock's time properties dataset (timePropertiesDS).
ptpbaseClockTransDefaultDSClockIdentity, ptpbaseClockTransDefaultDSNumOfPorts, ptpbaseClockTransDefaultDSDelay, and ptpbaseClockTransDefaultDSPrimaryDomain expose the values of a transparent clock's default dataset (transparentClockDefaultDS).
ptpbaseClockPortName, ptpbaseClockPortRole, ptpbaseClockPortSyncTwoStep, ptpbaseClockPortCurrentPeerAddressType, ptpbaseClockPortCurrentPeerAddress, and ptpbaseClockPortNumOfAssociatedPorts expose general information about a clock port.
ptpbaseClockPortRunningName, ptpbaseClockPortRunningState, ptpbaseClockPortRunningRole, ptpbaseClockPortRunningInterfaceIndex, ptpbaseClockPortRunningTransport, ptpbaseClockPortRunningEncapsulationType, ptpbaseClockPortRunningTxMode, ptpbaseClockPortRunningRxMode, ptpbaseClockPortRunningPacketsReceived, and ptpbaseClockPortRunningPacketsSent expose a clock port's current running status.
ptpbaseClockPortDSName, ptpbaseClockPortDSPortIdentity, ptpbaseClockPortDSlogAnnouncementInterval, ptpbaseClockPortDSAnnounceRctTimeout, ptpbaseClockPortDSlogSyncInterval, ptpbaseClockPortDSMinDelayReqInterval, ptpbaseClockPortDSPeerDelayReqInterval, ptpbaseClockPortDSDelayMech, ptpbaseClockPortDSPeerMeanPathDelay, ptpbaseClockPortDSGrantDuration, and ptpbaseClockPortDSPTPVersion expose the values of a clock port's port dataset (portDS).
ptpbaseClockPortTransDSPortIdentity, ptpbaseClockPortTransDSlogMinPdelayReqInt, ptpbaseClockPortTransDSFaultyFlag, and ptpbaseClockPortTransDSPeerMeanPathDelay expose the values of a transparent clock port's port dataset (transparentClockPortDS). ptpbaseClockPortAssociateAddressType, ptpbaseClockPortAssociateAddress, ptpbaseClockPortAssociatePacketsSent, ptpbaseClockPortAssociatePacketsReceived, ptpbaseClockPortAssociateInErrors, and ptpbaseClockPortAssociateOutErrors expose information about a clock port's peer node.
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example, by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET (read) the objects in this MIB module.
Implementations SHOULD provide the security features described by the SNMPv3 framework (see [RFC3410]), and implementations claiming compliance to the SNMPv3 standard MUST include full support for authentication and privacy via the User-based Security Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations MAY also provide support for the Transport Security Model (TSM) [RFC5591] in combination with a secure transport such as SSH [RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT recommended. Instead, it is recommended to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them.
The MIB module defined in this document uses the following IANA- assigned OBJECT IDENTIFIER value recorded in the "Structure of Management Information (SMI) Numbers (MIB Module Registrations)" registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
ptpbaseMIB { mib-2 241 }
Shankarkumar, et al. Standards Track [Page 61]
RFC 8173 PTPv2 MIB June 20177. References7.1. Normative References
[IEEE-1588-2008]
IEEE, "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE Std. 1588-2008, DOI 10.1109/IEEESTD.2008.4579760.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/RFC2578, April 1999, <http://www.rfc-editor.org/info/rfc2578>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/RFC3414, December 2002, <http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, DOI 10.17487/RFC3826, June 2004, <http://www.rfc-editor.org/info/rfc3826>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, <http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, <http://www.rfc-editor.org/info/rfc6353>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, DOI 10.17487/RFC3410, December 2002, <http://www.rfc-editor.org/info/rfc3410>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, <http://www.rfc-editor.org/info/rfc5905>.
[G.8265.1] ITU-T, "Precision time protocol telecom profile for
frequency synchronization", ITU-T Recommendation G.8265.1, July 2014.
Acknowledgements
Thanks to John Linton and Danny Lee for their valuable comments and to Bert Wijnen, Kevin Gross, Alan Luchuk, Chris Elliot, Brian Haberman, and Dan Romascanu for their reviews of this MIB module.
Vinay Shankarkumar Cisco Systems 7100-9 Kit Creek Road Research Triangle Park, NC 27709 United States of America
Email: vinays@cisco.com
Laurent Montini Cisco Systems 11, rue Camille Desmoulins 92782 Issy-les-Moulineaux France
Email: lmontini@cisco.com
Tim Frost Calnex Solutions Ltd. Oracle Campus Linlithgow EH49 7LR United Kingdom
Email: tim.frost@calnexsol.com
Greg Dowd Microsemi Inc. 3870 North First Street San Jose, CA 95134 United States of America
Email: greg.dowd@microsemi.com
Shankarkumar, et al. Standards Track [Page 64]
Ad
Translate documents to 日本語, svenska, Nederlands, Deutsch, français, русский, italiano, español, Tiếng Việt, polski, português, 中文, українська, català, norsk, فارسی, suomi, Bahasa Indonesia, العربية, čeština, 한국어, Bahasa Melayu, magyar, română, српски and other languages.
