< draft-ietf-tictoc-ptp-mib-02.txt   draft-ietf-tictoc-ptp-mib-03.txt >
TICTOC Working Group Vinay Shankarkumar TICTOC Working Group Vinay Shankarkumar
INTERNET DRAFT Laurent Montini INTERNET DRAFT Laurent Montini
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: January 30, 2013
Tim Frost Tim Frost
Greg Dowd Greg Dowd
Symmetricom Symmetricom
Expires: January 16, 2013 July 16, 2012 July 30, 2012
Precision Time Protocol Version 2 (PTPv2) Precision Time Protocol Version 2 (PTPv2)
Management Information Base Management Information Base
draft-ietf-tictoc-ptp-mib-02.txt draft-ietf-tictoc-ptp-mib-03.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 16, 2013. This Internet-Draft will expire on January 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
definitions. definitions.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
1.1. Relationship to other Profiles and MIBs...................3 1.1. Relationship to other Profiles and MIBs...................3
1.2. Change Log................................................3 1.2. Change Log................................................3
2. The SNMP Management Framework..................................4 2. The SNMP Management Framework..................................4
3. Overview.......................................................5 3. Overview.......................................................5
4. IETF PTP MIB Definition........................................5 4. IETF PTP MIB Definition........................................5
5. Security Considerations.......................................72 5. Security Considerations.......................................61
6. IANA Considerations...........................................72 6. IANA Considerations...........................................61
7. References....................................................73 7. References....................................................61
7.1. Normative References.....................................73 7.1. Normative References.....................................61
7.2. Informative References...................................73 7.2. Informative References...................................61
8. Acknowledgements..............................................75 8. Acknowledgements..............................................63
9. Author's Addresses............................................75 9. Author's Addresses............................................64
10. ANNEX A: Extended Fields Addendum............................65
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet Community. for use with network management protocols in the Internet Community.
In particular, it describes managed objects used for managing PTP In particular, it describes managed objects used for managing PTP
devices including the ordinary clock, transparent clock, boundary devices including the ordinary clock, transparent clock, boundary
clocks. clocks.
This MIB is restricted to reading standard PTP data elements, as This MIB is restricted to reading standard PTP data elements, as
skipping to change at page 4, line 4 skipping to change at page 3, line 52
- corrected some data types - corrected some data types
- corrected references and typos - corrected references and typos
-02 Jul 12 Revised following comment at IETF83: -02 Jul 12 Revised following comment at IETF83:
- changed "ptpbaseClockPortRunningIPversion" to the more - changed "ptpbaseClockPortRunningIPversion" to the more
generic "ptpbaseClockPortRunningTransport", covering generic "ptpbaseClockPortRunningTransport", covering
all transport types defined in [IEEE 1588-2008] all transport types defined in [IEEE 1588-2008]
(i.e. IPv4, IPv6, Ethernet, DeviceNet and ControlNet). (i.e. IPv4, IPv6, Ethernet, DeviceNet and ControlNet).
- changed addresses associated with transports from - changed addresses associated with transports from
"InetAddress" (for the IP transport) to a string, "InetAddress" (for the IP transport) to a string,
to allow for the different transport types. to allow for the different transport types.
-03 Jul 31 Revised following comments at IETF83 and from Andy
Bierman:
- corrected minor compiling errors and typos from -01
- corrected breaking compiling error from -02
- moved the OBJECT-GROUPS and MODULE-COMPLIANCES to the
end
- edited description clauses of MIBCompliances 1,2,3 & 4
- renamed ptpbaseMIBCompliances1 to 4:
ptpbaseMIBCompliancesSystemInfo
ptpbaseMIBCompliancesClockInfo
ptpbaseMIBCompliancesClockPortInfo
ptpbaseMIBCompliancesTransparentClockInfo
- added Annex with the extended structures introduced in
-01
- edited minor corrections from -02
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in STD62, [RFC 3411]. 1. An overall architecture, described in STD62, [RFC 3411].
o Mechanisms for describing and naming objects and events for the 2. Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16: [RFC 1155], [RFC 1212] and [RFC 1215]. STD 16: [RFC 1155], [RFC 1212] and [RFC 1215].
The second version, called SMIv2, is described in STD 58: The second version, called SMIv2, is described in STD 58:
[RFC 2578], [RFC 2579] and [RFC 2580]. [RFC 2578], [RFC 2579] and [RFC 2580].
o Message protocols for transferring management information. The 3. Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15 [RFC 1157]. A second version of the SNMP described in STD 15 [RFC 1157]. A second version of the SNMP
message protocol, which is not an Internet standards track message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in [RFC 1901] and protocol, is called SNMPv2c and described in [RFC 1901] and
[RFC 1906]. The third version of the message protocol is called [RFC 1906]. The third version of the message protocol is called
SNMPv3 and described in STD62: [RFC 3417], [RFC 3412] and [RFC SNMPv3 and described in STD62: [RFC 3417], [RFC 3412] and [RFC
3414]. 3414].
o Protocol operations for accessing management information. The 4. Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15 [RFC 1157]. A second set of protocol described in STD 15 [RFC 1157]. A second set of protocol
operations and associated PDU formats is described in STD 62 operations and associated PDU formats is described in STD 62
[RFC 3416]. [RFC 3416].
o A set of fundamental applications described in STD 62 [RFC 3413] 5. A set of fundamental applications described in STD 62 [RFC 3413]
and the view-based access control mechanism described in STD 62 and the view-based access control mechanism described in STD 62
[RFC 3415]. [RFC 3415].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
skipping to change at page 5, line 21 skipping to change at page 5, line 35
PTPBASE-MIB DEFINITIONS ::= BEGIN PTPBASE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Integer32, Integer32,
Gauge32, Gauge32,
Unsigned32, Unsigned32,
Counter32, Counter32,
Counter64 Counter64,
mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
OBJECT-GROUP, OBJECT-GROUP,
MODULE-COMPLIANCE MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
TruthValue, TruthValue,
DisplayString DisplayString
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB; FROM IF-MIB;
ptpbaseMIB MODULE-IDENTITY ptpbaseMIB MODULE-IDENTITY
LAST-UPDATED "201201230000Z" LAST-UPDATED "201207230000Z"
ORGANIZATION "TICTOC Working Group" ORGANIZATION "TICTOC Working Group"
CONTACT-INFO CONTACT-INFO
"WG Email: tictoc@ietf.org "WG Email: tictoc@ietf.org
Vinay Shankarkumar Vinay Shankarkumar
Cisco Systems, Cisco Systems,
Email: vinays@cisco.com Email: vinays@cisco.com
Laurent Montini, Laurent Montini,
Cisco Systems, Cisco Systems,
skipping to change at page 12, line 44 skipping to change at page 11, line 45
Transparent clock: Transparent clock:
A device that measures the time taken for a Precision Time A device that measures the time taken for a Precision Time
Protocol event message to transit the device and provides this Protocol event message to transit the device and provides this
information to clocks receiving this PTP event message. information to clocks receiving this PTP event message.
Two-step clock: Two-step clock:
A clock that provides time information using the combination of A clock that provides time information using the combination of
an event message and a subsequent general message. an event message and a subsequent general message.
The table below specifies the object formats of the various The below table specifies the object formats of the various
textual conventions used. textual conventions used.
Data type mapping Textual Convention SYNTAX Data type mapping Textual Convention SYNTAX
------------------- ------------------ --------------------- ------------------- ------------------ ---------------------
5.3.2 TimeInterval ClockTimeInterval OCTET STRING(SIZE(1..255)) 5.3.2 TimeInterval ClockTimeInterval OCTET STRING(SIZE(1..255))
5.3.3 Timestamp ClockTimestamp OCTET STRING(SIZE(6)) 5.3.3 Timestamp ClockTimestamp OCTET STRING(SIZE(6))
5.3.4 ClockIdentity ClockIdentity OCTET STRING(SIZE(1..255)) 5.3.4 ClockIdentity ClockIdentity OCTET STRING(SIZE(1..255))
5.3.5 PortIdentity ClockPortNumber INTEGER(1..65535) 5.3.5 PortIdentity ClockPortNumber INTEGER(1..65535)
5.3.7 ClockQuality ClockQualityClassType 5.3.7 ClockQuality ClockQualityClassType
Simple master-slave hierarchy, section 6.6.2.4 [IEEE 1588-2008]: Simple master-slave hierarchy, section 6.6.2.4 [IEEE 1588-2008]:
+---------------+ +---------------+
| Ordinary | | Ordinary |
| Clock -1 | | Clock -1 |
| (GrandMaster) | | (GrandMaster) |
+-------M-------+ +-------M-------+
| |
1 1
| |
skipping to change at page 14, line 41 skipping to change at page 13, line 35
+----------------------+ +----------------------+
+----------------------+ | End-to-end | +----------------------+ | End-to-end |
| Ordinary clock 1-2 |----------| transparent clock- | | Ordinary clock 1-2 |----------| transparent clock- |
+----------------------+ | 1 - 2 | +----------------------+ | 1 - 2 |
+----------------------+ +----------------------+
The MIB refers to the sections of [IEEE 1588-2008]." The MIB refers to the sections of [IEEE 1588-2008]."
-- revision log -- revision log
::= { mib-2 XXX }_-- XXX to be assigned by IANA ::= { mib-2 XXX } -- XXX to be assigned by IANA
ClockDomainType ::= TEXTUAL-CONVENTION ClockDomainType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Domain is identified by an integer, the domainNumber, in "The Domain is identified by an integer, the domainNumber, in
the range of 0 to 255. An integer value that is used to assign the range of 0 to 255. An integer value that is used to assign
each PTP device to a particular domain. The following values each PTP device to a particular domain. The following values
define the valid domains. define the valid domains.
skipping to change at page 25, line 27 skipping to change at page 22, line 23
SYNTAX INTEGER { SYNTAX INTEGER {
ordinaryClock(1), ordinaryClock(1),
boundaryClock(2), boundaryClock(2),
transparentClock(3), transparentClock(3),
boundaryNode(4) boundaryNode(4)
} }
ClockPortTransportType ::= TEXTUAL-CONVENTION ClockPortTransportType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
DESCRIPTION "The Clock port transport type."
"The Clock port transport type. The transport protocol used for
the communication between the clock nodes. This includes
IP version 4, IP version 6, Ethernet, DeviceNet, ControlNet and
IEC61158."
REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet), REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet),
Annex G (DeviceNet), Annex H (ControlNet) and Annex G (DeviceNET), Annex H (ControlNET) and
Annex I (IEC61158) of [IEEE 1588-2008]" Annex I (IEC61158) of [IEEE 1588-2008]"
SYNTAX INTEGER { SYNTAX INTEGER {
ipversion4(1), ipversion4(1),
ipversion6(2), ipversion6(2),
ethernet(3), ethernet(3),
DeviceNet(4), deviceNET(4),
ControlNet(5), controlNET(5),
IEC61158(6) iec61158(6)
} }
ClockPortTransportTypeAddress ::= TEXTUAL-CONVENTION ClockPortTransportTypeAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Clock port transport protocol address used for the "The Clock port transport protocol address used for this
communication between the clock nodes. This is a string communication between the clock nodes. This is a string
corresponding to the address type as specified by the corresponding to the address type as specified by the
ClockPortTransportType. ClockPortTransportType.
This can be an address of types IP version 4, IP version 6, This can be address of type IP version 4, IP version 6,
Ethernet, DeviceNet, ControlNet and IEC61158." Ethernet, DeviceNET, ControlNET and IEC61158."
REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet), REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet),
Annex G (DeviceNet), Annex H (ControlNet) and Annex G (DeviceNET), Annex H (ControlNET) and
Annex I (IEC61158) of [IEEE 1588-2008]" Annex I (IEC61158) of [IEEE 1588-2008]"
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
ptpbaseMIBNotifs OBJECT IDENTIFIER
::= { ptpbaseMIB 0 }
ptpbaseMIBObjects OBJECT IDENTIFIER
::= { ptpbaseMIB 1 }
ptpbaseMIBConformance OBJECT IDENTIFIER
::= { ptpbaseMIB 2 }
ptpbaseMIBSystemInfo OBJECT IDENTIFIER
::= { ptpbaseMIBObjects 1 }
ptpbaseMIBCompliances OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 1 }
ptpbaseMIBGroups OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 2 }
ptpbaseMIBCompliances1 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide read-only support
for PTPBASE-MIB. 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 }
ptpbaseMIBCompliances2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide read-only support
for PTPBASE-MIB. 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 {
ptpbaseMIBClockCurrentDSGroup,
ptpbaseMIBClockParentDSGroup,
ptpbaseMIBClockDefaultDSGroup,
ptpbaseMIBClockRunningGroup,
ptpbaseMIBClockTimepropertiesGroup
}
::= { ptpbaseMIBCompliances 2 }
ptpbaseMIBCompliances3 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide read-only support
for PTPBASE-MIB. 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 {
ptpbaseMIBClockPortGroup,
ptpbaseMIBClockPortDSGroup,
ptpbaseMIBClockPortRunningGroup,
ptpbaseMIBClockPortAssociateGroup
}
::= { ptpbaseMIBCompliances 3 }
ptpbaseMIBCompliances4 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide read-only support
for PTPBASE-MIB. 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 {
ptpbaseMIBClockTranparentDSGroup,
ptpbaseMIBClockPortTransDSGroup
}
::= { ptpbaseMIBCompliances 4 }
ptpbaseMIBSystemInfoGroup OBJECT-GROUP
OBJECTS {
ptpbaseSystemDomainTotals,
ptpDomainClockPortsTotal,
ptpbaseSystemProfile
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing system-wide
information"
::= { ptpbaseMIBGroups 1 }
ptpbaseMIBClockCurrentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockCurrentDSStepsRemoved,
ptpbaseClockCurrentDSOffsetFromMaster,
ptpbaseClockCurrentDSMeanPathDelay
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Current Dataset
information"
::= { ptpbaseMIBGroups 2 }
ptpbaseMIBClockParentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockParentDSParentPortIdentity,
ptpbaseClockParentDSParentStats,
ptpbaseClockParentDSOffset,
ptpbaseClockParentDSClockPhChRate,
ptpbaseClockParentDSGMClockIdentity,
ptpbaseClockParentDSGMClockPriority1,
ptpbaseClockParentDSGMClockPriority2,
ptpbaseClockParentDSGMClockQualityClass,
ptpbaseClockParentDSGMClockQualityAccuracy,
ptpbaseClockParentDSGMClockQualityOffset
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Parent Dataset
information"
::= { ptpbaseMIBGroups 3 }
ptpbaseMIBClockDefaultDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockDefaultDSTwoStepFlag,
ptpbaseClockDefaultDSClockIdentity,
ptpbaseClockDefaultDSPriority1,
ptpbaseClockDefaultDSPriority2,
ptpbaseClockDefaultDSSlaveOnly,
ptpbaseClockDefaultDSQualityClass,
ptpbaseClockDefaultDSQualityAccuracy,
ptpbaseClockDefaultDSQualityOffset
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Default Dataset
information"
::= { ptpbaseMIBGroups 4 }
ptpbaseMIBClockRunningGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockRunningState,
ptpbaseClockRunningPacketsSent,
ptpbaseClockRunningPacketsReceived
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP running state
information"
::= { ptpbaseMIBGroups 5 }
ptpbaseMIBClockTimepropertiesGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid,
ptpbaseClockTimePropertiesDSCurrentUTCOffset,
ptpbaseClockTimePropertiesDSLeap59,
ptpbaseClockTimePropertiesDSLeap61,
ptpbaseClockTimePropertiesDSTimeTraceable,
ptpbaseClockTimePropertiesDSFreqTraceable,
ptpbaseClockTimePropertiesDSPTPTimescale,
ptpbaseClockTimePropertiesDSSource
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Time Properties
information"
::= { ptpbaseMIBGroups 6 }
ptpbaseMIBClockTranparentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockTransDefaultDSClockIdentity,
ptpbaseClockTransDefaultDSNumOfPorts,
ptpbaseClockTransDefaultDSDelay,
ptpbaseClockTransDefaultDSPrimaryDomain
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Transparent
Dataset
information"
::= { ptpbaseMIBGroups 7 }
ptpbaseMIBClockPortGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortName,
ptpbaseClockPortSyncOneStep,
ptpbaseClockPortCurrentPeerAddress,
ptpbaseClockPortNumOfAssociatedPorts,
ptpbaseClockPortCurrentPeerAddressType,
ptpbaseClockPortRole
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing information for a
given PTP Port."
::= { ptpbaseMIBGroups 8 }
ptpbaseMIBClockPortDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortDSName,
ptpbaseClockPortDSPortIdentity,
ptpbaseClockPortDSAnnouncementInterval,
ptpbaseClockPortDSAnnounceRctTimeout,
ptpbaseClockPortDSSyncInterval,
ptpbaseClockPortDSMinDelayReqInterval,
ptpbaseClockPortDSPeerDelayReqInterval,
ptpbaseClockPortDSDelayMech,
ptpbaseClockPortDSPeerMeanPathDelay,
ptpbaseClockPortDSGrantDuration,
ptpbaseClockPortDSPTPVersion
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Port Dataset
information"
::= { ptpbaseMIBGroups 9 }
ptpbaseMIBClockPortRunningGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortRunningName,
ptpbaseClockPortRunningState,
ptpbaseClockPortRunningRole,
ptpbaseClockPortRunningInterfaceIndex,
ptpbaseClockPortRunningTransport,
ptpbaseClockPortRunningEncapsulationType,
ptpbaseClockPortRunningTxMode,
ptpbaseClockPortRunningRxMode,
ptpbaseClockPortRunningPacketsReceived,
ptpbaseClockPortRunningPacketsSent
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP running interface
information"
::= { ptpbaseMIBGroups 10 }
ptpbaseMIBClockPortTransDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortTransDSPortIdentity,
ptpbaseClockPortTransDSlogMinPdelayReqInt,
ptpbaseClockPortTransDSFaultyFlag,
ptpbaseClockPortTransDSPeerMeanPathDelay
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP TransparentDS
Dataset
information"
::= { ptpbaseMIBGroups 11 }
ptpbaseMIBClockPortAssociateGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortAssociatePacketsSent,
ptpbaseClockPortAssociatePacketsReceived,
ptpbaseClockPortAssociateAddress,
ptpbaseClockPortAssociateAddressType,
ptpbaseClockPortAssociateInErrors,
ptpbaseClockPortAssociateOutErrors
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing information on peer
PTP ports for a given PTP clock-port."
::= { ptpbaseMIBGroups 12 }
ptpbaseMIBClockInfo OBJECT IDENTIFIER ptpbaseMIBClockInfo OBJECT IDENTIFIER
::= { ptpbaseMIBObjects 2 } ::= { ptpbaseMIBObjects 2 }
ptpbaseSystemTable OBJECT-TYPE ptpbaseSystemTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseSystemEntry SYNTAX SEQUENCE OF PtpbaseSystemEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of count information about the PTP system for all "Table of count information about the PTP system for all
domains." domains."
skipping to change at page 55, line 8 skipping to change at page 41, line 29
PtpbaseClockPortEntry ::= SEQUENCE { PtpbaseClockPortEntry ::= SEQUENCE {
ptpbaseClockPortDomainIndex ClockDomainType, ptpbaseClockPortDomainIndex ClockDomainType,
ptpbaseClockPortClockTypeIndex ClockType, ptpbaseClockPortClockTypeIndex ClockType,
ptpbaseClockPortClockInstanceIndex ClockInstanceType, ptpbaseClockPortClockInstanceIndex ClockInstanceType,
ptpbaseClockPortTablePortNumberIndex ClockPortNumber, ptpbaseClockPortTablePortNumberIndex ClockPortNumber,
ptpbaseClockPortName DisplayString, ptpbaseClockPortName DisplayString,
ptpbaseClockPortRole ClockRoleType, ptpbaseClockPortRole ClockRoleType,
ptpbaseClockPortSyncOneStep TruthValue, ptpbaseClockPortSyncOneStep TruthValue,
ptpbaseClockPortCurrentPeerAddressType ClockPortTransportType, ptpbaseClockPortCurrentPeerAddressType ClockPortTransportType,
ptpbaseClockPortCurrentPeerAddress ptpbaseClockPortCurrentPeerAddress ClockPortTransportTypeAddress,
ClockPortTransportTypeAddress,
ptpbaseClockPortNumOfAssociatedPorts Gauge32 ptpbaseClockPortNumOfAssociatedPorts Gauge32
} }
ptpbaseClockPortDomainIndex OBJECT-TYPE ptpbaseClockPortDomainIndex OBJECT-TYPE
SYNTAX ClockDomainType SYNTAX ClockDomainType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the domain number used to create logical "This object specifies the domain number used to create logical
group of PTP devices." group of PTP devices."
skipping to change at page 62, line 14 skipping to change at page 47, line 23
PtpbaseClockPortRunningEntry ::= SEQUENCE { PtpbaseClockPortRunningEntry ::= SEQUENCE {
ptpbaseClockPortRunningDomainIndex ClockDomainType, ptpbaseClockPortRunningDomainIndex ClockDomainType,
ptpbaseClockPortRunningClockTypeIndex ClockType, ptpbaseClockPortRunningClockTypeIndex ClockType,
ptpbaseClockPortRunningClockInstanceIndex ClockInstanceType, ptpbaseClockPortRunningClockInstanceIndex ClockInstanceType,
ptpbaseClockPortRunningPortNumberIndex ClockPortNumber, ptpbaseClockPortRunningPortNumberIndex ClockPortNumber,
ptpbaseClockPortRunningName DisplayString, ptpbaseClockPortRunningName DisplayString,
ptpbaseClockPortRunningState ClockPortState, ptpbaseClockPortRunningState ClockPortState,
ptpbaseClockPortRunningRole ClockRoleType, ptpbaseClockPortRunningRole ClockRoleType,
ptpbaseClockPortRunningInterfaceIndex InterfaceIndexOrZero, ptpbaseClockPortRunningInterfaceIndex InterfaceIndexOrZero,
ptpbaseClockPortRunningTransport ptpbaseClockPortRunningTransport ClockPortTransportType,
ClockPortTransportType,
ptpbaseClockPortRunningEncapsulationType Integer32, ptpbaseClockPortRunningEncapsulationType Integer32,
ptpbaseClockPortRunningTxMode ClockTxModeType, ptpbaseClockPortRunningTxMode ClockTxModeType,
ptpbaseClockPortRunningRxMode ClockTxModeType, ptpbaseClockPortRunningRxMode ClockTxModeType,
ptpbaseClockPortRunningPacketsReceived Counter64, ptpbaseClockPortRunningPacketsReceived Counter64,
ptpbaseClockPortRunningPacketsSent Counter64 ptpbaseClockPortRunningPacketsSent Counter64
} }
ptpbaseClockPortRunningDomainIndex OBJECT-TYPE ptpbaseClockPortRunningDomainIndex OBJECT-TYPE
SYNTAX ClockDomainType SYNTAX ClockDomainType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 69, line 33 skipping to change at page 53, line 30
} }
::= { ptpbaseClockPortAssociateTable 1 } ::= { ptpbaseClockPortAssociateTable 1 }
PtpbaseClockPortAssociateEntry ::= SEQUENCE { PtpbaseClockPortAssociateEntry ::= SEQUENCE {
ptpClockPortCurrentDomainIndex ClockDomainType, ptpClockPortCurrentDomainIndex ClockDomainType,
ptpClockPortCurrentClockTypeIndex ClockType, ptpClockPortCurrentClockTypeIndex ClockType,
ptpClockPortCurrentClockInstanceIndex ClockInstanceType, ptpClockPortCurrentClockInstanceIndex ClockInstanceType,
ptpClockPortCurrentPortNumberIndex ClockPortNumber, ptpClockPortCurrentPortNumberIndex ClockPortNumber,
ptpbaseClockPortAssociatePortIndex Unsigned32, ptpbaseClockPortAssociatePortIndex Unsigned32,
ptpbaseClockPortAssociateAddressType ClockPortTransportType, ptpbaseClockPortAssociateAddressType ClockPortTransportType,
ptpbaseClockPortAssociateAddress ptpbaseClockPortAssociateAddress ClockPortTransportTypeAddress,
ClockPortTransportTypeAddress,
ptpbaseClockPortAssociatePacketsSent Counter64, ptpbaseClockPortAssociatePacketsSent Counter64,
ptpbaseClockPortAssociatePacketsReceived Counter64, ptpbaseClockPortAssociatePacketsReceived Counter64,
ptpbaseClockPortAssociateInErrors Counter64, ptpbaseClockPortAssociateInErrors Counter64,
ptpbaseClockPortAssociateOutErrors Counter64 ptpbaseClockPortAssociateOutErrors Counter64
} }
ptpClockPortCurrentDomainIndex OBJECT-TYPE ptpClockPortCurrentDomainIndex OBJECT-TYPE
SYNTAX ClockDomainType SYNTAX ClockDomainType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 72, line 12 skipping to change at page 55, line 33
ptpbaseClockPortAssociateOutErrors OBJECT-TYPE ptpbaseClockPortAssociateOutErrors OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the output errors associated with the "This object specifies the output errors associated with the
peer port." peer port."
::= { ptpbaseClockPortAssociateEntry 11 } ::= { ptpbaseClockPortAssociateEntry 11 }
END ptpbaseMIBNotifs OBJECT IDENTIFIER
::= { ptpbaseMIB 0 }
ptpbaseMIBObjects OBJECT IDENTIFIER
::= { ptpbaseMIB 1 }
ptpbaseMIBConformance OBJECT IDENTIFIER
::= { ptpbaseMIB 2 }
ptpbaseMIBSystemInfo OBJECT IDENTIFIER
::= { ptpbaseMIBObjects 1 }
-- Conformance Information Definition
ptpbaseMIBCompliances OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 1 }
ptpbaseMIBGroups OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 2 }
ptpbaseMIBCompliancesSystemInfo MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"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 {
ptpbaseMIBClockCurrentDSGroup,
ptpbaseMIBClockParentDSGroup,
ptpbaseMIBClockDefaultDSGroup,
ptpbaseMIBClockRunningGroup,
ptpbaseMIBClockTimepropertiesGroup
}
::= { ptpbaseMIBCompliances 2 }
ptpbaseMIBCompliancesClockPortInfo MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"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 {
ptpbaseMIBClockPortGroup,
ptpbaseMIBClockPortDSGroup,
ptpbaseMIBClockPortRunningGroup,
ptpbaseMIBClockPortAssociateGroup
}
::= { ptpbaseMIBCompliances 3 }
ptpbaseMIBCompliancesTransparentClockInfo MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"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 {
ptpbaseMIBClockTranparentDSGroup,
ptpbaseMIBClockPortTransDSGroup
}
::= { ptpbaseMIBCompliances 4 }
ptpbaseMIBSystemInfoGroup OBJECT-GROUP
OBJECTS {
ptpbaseSystemDomainTotals,
ptpDomainClockPortsTotal,
ptpbaseSystemProfile
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing system-wide
information"
::= { ptpbaseMIBGroups 1 }
ptpbaseMIBClockCurrentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockCurrentDSStepsRemoved,
ptpbaseClockCurrentDSOffsetFromMaster,
ptpbaseClockCurrentDSMeanPathDelay
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Current Dataset
information"
::= { ptpbaseMIBGroups 2 }
ptpbaseMIBClockParentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockParentDSParentPortIdentity,
ptpbaseClockParentDSParentStats,
ptpbaseClockParentDSOffset,
ptpbaseClockParentDSClockPhChRate,
ptpbaseClockParentDSGMClockIdentity,
ptpbaseClockParentDSGMClockPriority1,
ptpbaseClockParentDSGMClockPriority2,
ptpbaseClockParentDSGMClockQualityClass,
ptpbaseClockParentDSGMClockQualityAccuracy,
ptpbaseClockParentDSGMClockQualityOffset
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Parent Dataset
information"
::= { ptpbaseMIBGroups 3 }
ptpbaseMIBClockDefaultDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockDefaultDSTwoStepFlag,
ptpbaseClockDefaultDSClockIdentity,
ptpbaseClockDefaultDSPriority1,
ptpbaseClockDefaultDSPriority2,
ptpbaseClockDefaultDSSlaveOnly,
ptpbaseClockDefaultDSQualityClass,
ptpbaseClockDefaultDSQualityAccuracy,
ptpbaseClockDefaultDSQualityOffset
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Default Dataset
information"
::= { ptpbaseMIBGroups 4 }
ptpbaseMIBClockRunningGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockRunningState,
ptpbaseClockRunningPacketsSent,
ptpbaseClockRunningPacketsReceived
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP running state
information"
::= { ptpbaseMIBGroups 5 }
ptpbaseMIBClockTimepropertiesGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid,
ptpbaseClockTimePropertiesDSCurrentUTCOffset,
ptpbaseClockTimePropertiesDSLeap59,
ptpbaseClockTimePropertiesDSLeap61,
ptpbaseClockTimePropertiesDSTimeTraceable,
ptpbaseClockTimePropertiesDSFreqTraceable,
ptpbaseClockTimePropertiesDSPTPTimescale,
ptpbaseClockTimePropertiesDSSource
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Time Properties
information"
::= { ptpbaseMIBGroups 6 }
ptpbaseMIBClockTranparentDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockTransDefaultDSClockIdentity,
ptpbaseClockTransDefaultDSNumOfPorts,
ptpbaseClockTransDefaultDSDelay,
ptpbaseClockTransDefaultDSPrimaryDomain
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Transparent
Dataset
information"
::= { ptpbaseMIBGroups 7 }
ptpbaseMIBClockPortGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortName,
ptpbaseClockPortSyncOneStep,
ptpbaseClockPortCurrentPeerAddress,
ptpbaseClockPortNumOfAssociatedPorts,
ptpbaseClockPortCurrentPeerAddressType,
ptpbaseClockPortRole
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing information for a
given PTP Port."
::= { ptpbaseMIBGroups 8 }
ptpbaseMIBClockPortDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortDSName,
ptpbaseClockPortDSPortIdentity,
ptpbaseClockPortDSAnnouncementInterval,
ptpbaseClockPortDSAnnounceRctTimeout,
ptpbaseClockPortDSSyncInterval,
ptpbaseClockPortDSMinDelayReqInterval,
ptpbaseClockPortDSPeerDelayReqInterval,
ptpbaseClockPortDSDelayMech,
ptpbaseClockPortDSPeerMeanPathDelay,
ptpbaseClockPortDSGrantDuration,
ptpbaseClockPortDSPTPVersion
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP Port Dataset
information"
::= { ptpbaseMIBGroups 9 }
ptpbaseMIBClockPortRunningGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortRunningName,
ptpbaseClockPortRunningState,
ptpbaseClockPortRunningRole,
ptpbaseClockPortRunningInterfaceIndex,
ptpbaseClockPortRunningTransport,
ptpbaseClockPortRunningEncapsulationType,
ptpbaseClockPortRunningTxMode,
ptpbaseClockPortRunningRxMode,
ptpbaseClockPortRunningPacketsReceived,
ptpbaseClockPortRunningPacketsSent
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP running interface
information"
::= { ptpbaseMIBGroups 10 }
ptpbaseMIBClockPortTransDSGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortTransDSPortIdentity,
ptpbaseClockPortTransDSlogMinPdelayReqInt,
ptpbaseClockPortTransDSFaultyFlag,
ptpbaseClockPortTransDSPeerMeanPathDelay
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing PTP TransparentDS
Dataset
information"
::= { ptpbaseMIBGroups 11 }
ptpbaseMIBClockPortAssociateGroup OBJECT-GROUP
OBJECTS {
ptpbaseClockPortAssociatePacketsSent,
ptpbaseClockPortAssociatePacketsReceived,
ptpbaseClockPortAssociateAddress,
ptpbaseClockPortAssociateAddressType,
ptpbaseClockPortAssociateInErrors,
ptpbaseClockPortAssociateOutErrors
}
STATUS current
DESCRIPTION
"Group which aggregates objects describing information on peer
PTP ports for a given PTP clock-port."
::= { ptpbaseMIBGroups 12 }
END
5. Security Considerations 5. Security Considerations
This MIB contains readable objects whose values provide information This MIB contains readable objects whose values provide information
related to PTP objects. While unauthorized access to the readable related to PTP objects. While unauthorized access to the readable
objects is relatively innocuous, unauthorized access to the write- objects is relatively innocuous, unauthorized access to the write-
able objects could cause a denial of service, or could cause able objects could cause a denial of service, or could cause
unauthorized creation and/or manipulation of tunnels. Hence, the unauthorized creation and/or manipulation of tunnels. Hence, the
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
skipping to change at line 3206 skipping to change at page 65, line 4
USA. USA.
Email: tfrost@symmetricom.com Email: tfrost@symmetricom.com
Greg Dowd, Greg Dowd,
Symmetricom Inc., Symmetricom Inc.,
2300 Orchard Parkway, 2300 Orchard Parkway,
San Jose, San Jose,
CA 95131, CA 95131,
USA. USA.
Email: gdowd@symmetricom.com Email: gdowd@symmetricom.com
10. ANNEX A: Extended Fields Addendum
Some structures in the MIB have been extended. The MIB is thus able
to cover the structures defined in the IEEE standards and is
extensible as well.
o ClockIdentity is defined in the standard as 8-octet array. The MIB
defines it as OCTET string of length (1..255).
o ClockPortNumber is defined in the standard as ranging from 1, 2,
... till FFFF (16 bits); FFFF is used as the 'all-ports' indicator
in Management messages and in signalling messages. The MIB defines
it as Unsigned32 ranging in value (0..65535).
o ClockTimeInterval is defined in the standard as of length 64 bits
(Integer64). The MIB defines it as OCTET string of length
(1..255).
o ptpbaseClockParentDSClockPhChRate
(parentDS.observedParentClockPaseChangeRate) is defined in the
standard as 16 bits. The MIB defines it as Integer32.
 End of changes. 30 change blocks. 
318 lines changed or deleted 332 lines changed or added

This html diff was produced by rfcdiff 1.39p1. The latest version is available from http://tools.ietf.org/tools/rfcdiff/