draft-ietf-tictoc-ptp-mib-03.txt   draft-ietf-tictoc-ptp-mib-04.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
July 30, 2012 Expires: July 31, 2013 January 31, 2013
Precision Time Protocol Version 2 (PTPv2) Precision Time Protocol Version 2 (PTPv2)
Management Information Base Management Information Base
draft-ietf-tictoc-ptp-mib-03.txt draft-ietf-tictoc-ptp-mib-04.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 30, 2013. This Internet-Draft will expire on July 31, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Abstract Abstract
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 TCP/IP-based internets. for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing networks using In particular, it defines objects for managing networks using
Precision Time Protocol. Precision Time Protocol, specified in [IEEE 1588-2008].
This memo specifies a MIB module in a manner that is both compliant This memo specifies a MIB module in a manner that is both compliant
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
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.......................................61 5. Security Considerations.......................................72
6. IANA Considerations...........................................61 6. IANA Considerations...........................................73
7. References....................................................61 7. References....................................................73
7.1. Normative References.....................................61 7.1. Normative References.....................................73
7.2. Informative References...................................61 7.2. Informative References...................................73
8. Acknowledgements..............................................63 8. Acknowledgements..............................................75
9. Author's Addresses............................................64 9. Author's Addresses............................................75
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
described in [IEEE 1588-2008]. It is envisioned this MIB will described in [IEEE 1588-2008]. This enables it to monitor the
complement other managed objects to be defined to monitor, measure operation of PTP clocks within the network. It is envisioned this
the performance of the PTP devices and telecom clocks. Those objects MIB will complement other managed objects to be defined that will
are considered out of scope for the current draft. 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 draft.
Similarly, this MIB is read-only and not intended to provide the Similarly, this MIB is read-only and not intended to provide the
ability to configure PTP clocks. Since PTP clocks are often embedded ability to configure PTP clocks. Since PTP clocks are often embedded
in other network elements such as routers, switches and gateways, in other network elements such as routers, switches and gateways,
this ability is generally provided via the configuration interface this ability is generally provided via the configuration interface
for the network element. for the network element.
1.1. Relationship to other Profiles and MIBs 1.1. Relationship to other Profiles and MIBs
This MIB is intended to be used with the default PTP profile This MIB is intended to be used with the default PTP profile
described in [IEEE 1588-2008], and the Telecom Profile described in described in [IEEE 1588-2008] when running over the IP network layer.
[G.8265.1], when running over the IP network layer. As stated above, As stated above, it is envisioned this MIB will complement other
it is envisioned this MIB will complement other managed objects to be managed objects to be defined to monitor and measure the performance
defined to monitor, measure the performance of the PTP devices and of PTP clocks supporting specific PTP profiles, e.g. the Telecom
telecom clocks. Profile defined in [G.8265.1].
Some other PTP profiles have their own MIBs defined as part of the Some other PTP profiles have their own MIBs defined as part of the
profile, and this MIB is not intended to replace those MIBs. profile, and this MIB is not intended to replace those MIBs.
1.2. Change Log 1.2. Change Log
This section tracks changes made to the revisions of the Internet This section tracks changes made to the revisions of the Internet
Drafts of this document. It will be *deleted* when the document is Drafts of this document. It will be *deleted* when the document is
published as an RFC. This section tracks changes made to the published as an RFC.
revisions of the Internet Drafts of this document. It will be
*deleted* when the document is published as an RFC.
draft-vinay-tictoc-ptp-mib draft-vinay-tictoc-ptp-mib
-00 Mar 11 Initial version; showed structure of MIB -00 Mar 11 Initial version; showed structure of MIB
draft-ietf-tictoc-ptp-mib draft-ietf-tictoc-ptp-mib
-00 Jul 11 First full, syntactically correct and compileable MIB -00 Jul 11 First full, syntactically correct and compileable MIB
-01 Jan 12 Revised following comments from Bert Wijnen: -01 Jan 12 Revised following comments from Bert Wijnen:
- revised introduction to clarify the scope, and the - revised introduction to clarify the scope, and the
relationship to other MIBs and profiles relationship to other MIBs and profiles
- changed name to "ptpbase" - changed name to "ptpbase"
- 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 -03 Jul 12 Minor changes following comments from Andy Bierman:
- corrected breaking compiling error from -02 - corrected some compilation errors
- moved the OBJECT-GROUPS and MODULE-COMPLIANCES to the - moved OBJECT-GROUP and MODULE-COMPLIANCE macros to the
end end
- edited description clauses of MIBCompliances 1,2,3 & 4
- renamed ptpbaseMIBCompliances1 to 4: -04 Jan 13 Changes:
ptpbaseMIBCompliancesSystemInfo - Use of 'AutonomousType' import
ptpbaseMIBCompliancesClockInfo - Display hint being specified for ClockIdentity,
ptpbaseMIBCompliancesClockPortInfo ClockInterval, ClockPortTransportTypeAddress
ptpbaseMIBCompliancesTransparentClockInfo Textual Conventions
- added Annex with the extended structures introduced in - Removal of the Textual convention
-01 ClockPortTransportType, replaced with the
- edited minor corrections from -02 wellKnownTransportTypes
- Modified ptpbaseClockPortCurrentPeerAddressType,
ptpbaseClockPortRunningTransport,
ptpbaseClockPortAssociateAddressType, to use
AutonomousType.
- various textual changes to descriptive text in
response to comments
There are still some small changes to be addressed following two
recent MIB reviews. These will be addressed in the next version.
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:
1. An overall architecture, described in STD62, [RFC 3411]. o An overall architecture, described in STD62, [RFC 3411].
2. Mechanisms for describing and naming objects and events for the o 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].
3. Message protocols for transferring management information. The o 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].
4. Protocol operations for accessing management information. The o 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].
5. A set of fundamental applications described in STD 62 [RFC 3413] o 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 31 skipping to change at page 5, line 39
The objects defined in this MIB are to be used when describing the The objects defined in this MIB are to be used when describing the
Precision Time Protocol (PTPv2). Precision Time Protocol (PTPv2).
4. IETF PTP MIB Definition 4. IETF PTP MIB Definition
PTPBASE-MIB DEFINITIONS ::= BEGIN PTPBASE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Integer32,
Gauge32, Gauge32,
Unsigned32, Unsigned32,
Counter32, Counter32,
Counter64, Counter64,
mib-2 mib-2,
Integer32
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,
AutonomousType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB; FROM IF-MIB;
ptpbaseMIB MODULE-IDENTITY ptpbaseMIB MODULE-IDENTITY
LAST-UPDATED "201207230000Z" 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
skipping to change at page 6, line 50 skipping to change at page 7, line 25
accumulation in large topologies, and specifications on how to accumulation in large topologies, and specifications on how to
incorporate the resulting additional data into the incorporate the resulting additional data into the
synchronization protocol. The [IEEE 1588-2008] defines synchronization protocol. The [IEEE 1588-2008] defines
conformance and management capability also. conformance and management capability also.
MIB description MIB description
This MIB is to support the Precision Time Protocol version 2 This MIB is to support the Precision Time Protocol version 2
(PTPv2, hereafter designated as PTP) features of network element (PTPv2, hereafter designated as PTP) features of network element
system devices, when using the default PTP profile described in system devices, when using the default PTP profile described in
[IEEE 1588-2008], or the Telecom Profile described in [IEEE 1588-2008] when running over the IP network layer.
[G.8265.1], when running over the IP network layer.
It is envisioned this MIB will complement other managed objects It is envisioned this MIB will complement other managed objects
to be defined to monitor, measure the performance of the PTP to be defined to monitor and measure the performance of the PTP
devices and telecom clocks. devices and telecom clocks supporting specific PTP profiles.
Some other PTP profiles have their own MIBs defined as part of Some other PTP profiles have their own MIBs defined as part of
the profile, and this MIB is not intended to replace those MIBs. the profile, and this MIB is not intended to replace those MIBs.
Acronyms: Acronyms:
ARB Arbitrary Timescale ARB Arbitrary Timescale
E2E End-to-End E2E End-to-End
EUI Extended Unique Identifier. EUI Extended Unique Identifier.
GPS Global Positioning System GPS Global Positioning System
IANA Internet Assigned Numbers Authority IANA Internet Assigned Numbers Authority
skipping to change at page 7, line 33 skipping to change at page 8, line 17
TAI International Atomic Time TAI International Atomic Time
TC Transparent Clock TC Transparent Clock
UDP User Datagram Protocol UDP User Datagram Protocol
UTC Coordinated Universal Time UTC Coordinated Universal Time
References: References:
[IEEE 1588-2008] IEEE Standard for A Precision Clock [IEEE 1588-2008] IEEE Standard for A Precision Clock
Synchronization Protocol for Networked Measurement and Synchronization Protocol for Networked Measurement and
Control Systems, IEEE Std. 1588(TM)-2008, 24 July 2008. Control Systems, IEEE Std. 1588(TM)-2008, 24 July 2008.
[G.8265.1] Precision Time Protocol Telecom Profile for
Frequency Synchronization, ITU-T Recommendation G.8265.1,
October 2010.
As defined in [IEEE 1588-2008]: As defined in [IEEE 1588-2008]:
Accuracy: Accuracy:
The mean of the time or frequency error between the clock under The mean of the time or frequency error between the clock under
test and a perfect reference clock, over an ensemble of test and a perfect reference clock, over an ensemble of
measurements. Stability is a measure of how the mean varies measurements. Stability is a measure of how the mean varies
with respect to variables such as time, temperature, and so on, with respect to variables such as time, temperature, and so on,
while the precision is a measure of the deviation of the error while the precision is a measure of the deviation of the error
from the mean. from the mean.
skipping to change at page 13, line 37 skipping to change at page 15, line 17
| 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
-- Textual Conventions
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.
Value Definition Value Definition
skipping to change at page 14, line 9 skipping to change at page 15, line 41
1 Alternate domain 1 1 Alternate domain 1
2 Alternate domain 2 2 Alternate domain 2
3 Alternate domain 3 3 Alternate domain 3
4 - 127 User-defined domains 4 - 127 User-defined domains
128 - 255 Reserved" 128 - 255 Reserved"
REFERENCE "Section 7.1 Domains, Table 2 of [IEEE 1588-2008]" REFERENCE "Section 7.1 Domains, Table 2 of [IEEE 1588-2008]"
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
ClockIdentity ::= TEXTUAL-CONVENTION ClockIdentity ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The clock Identity is an 8-octet array and will be presented in "The clock Identity is an 8-octet array and will be presented in
the form of a character array. The value of the the form of a character array. The value of the
ClockIdentity should be taken from the IEEE EUI-64 individual ClockIdentity should be taken from the IEEE EUI-64 individual
assigned numbers as indicated in Section 7.5.2.2.2 of assigned numbers as indicated in Section 7.5.2.2.2 of
[IEEE 1588-2008]. The EUI-64 address is divided into the [IEEE 1588-2008]. The EUI-64 address is divided into the
following fields: following fields:
OUI bytes (0-2) OUI bytes (0-2)
skipping to change at page 20, line 6 skipping to change at page 23, line 9
Clock State Value Description Clock State Value Description
-------------------------------------------------------------- --------------------------------------------------------------
Freerun state 1 Applies to a slave device that is not Freerun state 1 Applies to a slave device that is not
locked to a master. This is the initial locked to a master. This is the initial
state a slave starts out with when it state a slave starts out with when it
is not getting any PTP packets from the is not getting any PTP packets from the
master or because of some other input master or because of some other input
error (erroneous packets, etc). error (erroneous packets, etc).
Holdover state 2 In this state the slave device is Holdover state 2 In this state the slave device is
locked to a master but communication locked to a master but communication
with the master is lost or the with the master has been lost or the
timestamps in the ptp packets are timestamps in the ptp packets are
incorrect. But since the slave was incorrect. Since the slave was
locked to the master, it can run with locked to the master, it can run in this
the same accuracy for sometime. The state with the similar accuracy for some
slave can continue to operate in this time. If communication with the master
state for some time. If communication is not restored for an extended period
with the master is not restored for a (dependent on the clock implementation),
while, the device is moved to the the device is moved to the FREERUN
FREERUN state. state.
Acquiring state 3 The slave device is receiving packets Acquiring state 3 The slave device is receiving packets
from a master and is trying to acquire from a master and is trying to acquire
a lock. a lock.
Freq_locked state 4 Slave device is locked to the Master Freq_locked state 4 Slave device is locked to the Master
with respect to frequency, but not phase with respect to frequency, but not phase
aligned aligned
Phase_aligned state 5 Locked to the master with respect to Phase_aligned state 5 Locked to the master with respect to
skipping to change at page 21, line 15 skipping to change at page 24, line 27
gps(32), -- 0x20 gps(32), -- 0x20
terrestrialRadio(48), -- 0x22 terrestrialRadio(48), -- 0x22
ptp(64), -- 0x40 ptp(64), -- 0x40
ntp(80), -- 0x50 ntp(80), -- 0x50
handSet(96), -- 0x60 handSet(96), -- 0x60
other(144), -- 0x90 other(144), -- 0x90
internalOscillator(160) -- 0xA0 internalOscillator(160) -- 0xA0
} }
ClockTimeInterval ::= TEXTUAL-CONVENTION ClockTimeInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention corresponds to the TimeInterval "This textual convention corresponds to the TimeInterval
structure indicated in section 5.3.2 of [IEEE 1588-2008]. structure indicated in section 5.3.2 of [IEEE 1588-2008].
It will be presented in the form of a character array. It will be presented in the form of a character array.
The TimeInterval type represents time intervals. The TimeInterval type represents time intervals.
struct TimeInterval struct TimeInterval
{ {
skipping to change at page 21, line 48 skipping to change at page 25, line 18
REFERENCE REFERENCE
"Section 5.3.2 and setion 7.7.2.1 Timer interval "Section 5.3.2 and setion 7.7.2.1 Timer interval
specification of [IEEE 1588-2008]" specification of [IEEE 1588-2008]"
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
ClockTxModeType ::= TEXTUAL-CONVENTION ClockTxModeType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Transmission mode. "Transmission mode.
unicast. Using unicast communication channel. Unicast: Using unicast communication channel.
Multicast: Using Multicast communication channel.
multicast. Using Multicast communication channel. multicast-mix: Using multicast-unicast communication channel"
multicast-mix. Using multicast-unicast communication channel"
SYNTAX INTEGER { SYNTAX INTEGER {
unicast(1), unicast(1),
multicast(2), multicast(2),
multicastmix(3) multicastmix(3)
} }
ClockType ::= TEXTUAL-CONVENTION ClockType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The clock types as defined in the MIB module description." "The clock types as defined in the MIB module description."
REFERENCE "Section 6.5.1 of [IEEE 1588-2008]." REFERENCE "Section 6.5.1 of [IEEE 1588-2008]."
SYNTAX INTEGER { SYNTAX INTEGER {
ordinaryClock(1), ordinaryClock(1),
boundaryClock(2), boundaryClock(2),
transparentClock(3), transparentClock(3),
boundaryNode(4) boundaryNode(4)
} }
ClockPortTransportType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Clock port transport type."
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 INTEGER {
ipversion4(1),
ipversion6(2),
ethernet(3),
deviceNET(4),
controlNET(5),
iec61158(6)
}
ClockPortTransportTypeAddress ::= TEXTUAL-CONVENTION ClockPortTransportTypeAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Clock port transport protocol address used for this "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. Transport type used. The transport types can be defined
elsewhere, in addition to the ones defined in this document.
This can be address of type 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))
wellKnownTransportTypes OBJECT IDENTIFIER ::= { char }
transportTypeIPversion4 OBJECT IDENTIFIER ::= { wellKnownTransportTypes
1}
transportTypeIPversion6 OBJECT IDENTIFIER ::= { wellKnownTransportTypes
2}
transportTypeEthernet OBJECT IDENTIFIER ::= { wellKnownTransportTypes 3}
transportTypeDeviceNET OBJECT IDENTIFIER ::= { wellKnownTransportTypes
4}
transportTypeControlNET OBJECT IDENTIFIER ::= { wellKnownTransportTypes
5}
transportTypeIEC61158 OBJECT IDENTIFIER ::= { wellKnownTransportTypes 6}
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 33, line 32 skipping to change at page 39, line 21
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default dataset Quality Class." "This object specifies the default dataset Quality Class."
::= { ptpbaseClockDefaultDSEntry 9 } ::= { ptpbaseClockDefaultDSEntry 9 }
ptpbaseClockDefaultDSQualityAccuracy OBJECT-TYPE ptpbaseClockDefaultDSQualityAccuracy OBJECT-TYPE
SYNTAX ClockQualityAccuracyType SYNTAX ClockQualityAccuracyType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default dataset Quality Accurarcy." "This object specifies the default dataset Quality Accuracy."
::= { ptpbaseClockDefaultDSEntry 10 } ::= { ptpbaseClockDefaultDSEntry 10 }
ptpbaseClockDefaultDSQualityOffset OBJECT-TYPE ptpbaseClockDefaultDSQualityOffset OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default dataset Quality offset." "This object specifies the default dataset Quality offset."
::= { ptpbaseClockDefaultDSEntry 11 } ::= { ptpbaseClockDefaultDSEntry 11 }
skipping to change at page 35, line 8 skipping to change at page 41, line 15
::= { ptpbaseClockRunningEntry 3 } ::= { ptpbaseClockRunningEntry 3 }
ptpbaseClockRunningState OBJECT-TYPE ptpbaseClockRunningState OBJECT-TYPE
SYNTAX ClockStateType SYNTAX ClockStateType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the Clock state returned by PTP engine "This object specifies the Clock state returned by PTP engine
which was described earlier. which was described earlier.
Freerun state. Applies to a slave device that is not locked to Freerun state. Applies to a slave device that is not locked to
a master. This is the initial state a slave starts out with a master. This is the initial state a slave starts out with
when when it is not getting any PTP packets from the master, or
it is not getting any PTP packets from the master or because of because of some other input error (erroneous packets, etc).
some other input error (erroneous packets, etc).
Holdover state. In this state the slave device is locked to a Holdover state. In this state the slave device is locked to a
master but communication with the master is lost or the master but communication with the master has been lost or the
timestamps in the ptp packets are incorrect. But since the timestamps in the ptp packets are incorrect. Since the
slave was locked to the master, it can run with the same slave was previously locked to the master, it can run in this
accuracy for state with the similar accuracy for some time. If communication
sometime. The slave can continue to operate in this state for with the master is not restored for an extended period
some time. If communication with the master is not restored for (dependent on the clock implementation), the device is moved to
a while, the device is moved to the FREERUN state. the FREERUN state.
Acquiring state. The slave device is receiving packets from a Acquiring state. The slave device is receiving packets from a
master and is trying to acquire a lock. master and is trying to acquire a lock.
Freq_locked state. Slave device is locked to the Master with Freq_locked state. Slave device is locked to the Master with
respect to frequency, but not phase aligned respect to frequency, but not phase aligned
Phase_aligned state. Locked to the master with respect to Phase_aligned state. Locked to the master with respect to
frequency and phase." frequency and phase."
::= { ptpbaseClockRunningEntry 4 } ::= { ptpbaseClockRunningEntry 4 }
skipping to change at page 36, line 8 skipping to change at page 42, line 22
"This object specifies the total number of all packet Unicast "This object specifies the total number of all packet Unicast
and multicast that have been received for this clock in this and multicast that have been received for this clock in this
domain for this type." domain for this type."
::= { ptpbaseClockRunningEntry 6 } ::= { ptpbaseClockRunningEntry 6 }
ptpbaseClockTimePropertiesDSTable OBJECT-TYPE ptpbaseClockTimePropertiesDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockTimePropertiesDSEntry SYNTAX SEQUENCE OF PtpbaseClockTimePropertiesDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of information about the PTP clock Timeproperties "Table of information about the PTP clock TimeProperties
Datasets for all domains." Datasets for all domains."
::= { ptpbaseMIBClockInfo 5 } ::= { ptpbaseMIBClockInfo 5 }
ptpbaseClockTimePropertiesDSEntry OBJECT-TYPE ptpbaseClockTimePropertiesDSEntry OBJECT-TYPE
SYNTAX PtpbaseClockTimePropertiesDSEntry SYNTAX PtpbaseClockTimePropertiesDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information about a single "An entry in the table, containing information about a single
PTP clock timeproperties Datasets for a domain." PTP clock timeproperties Datasets for a domain."
skipping to change at page 37, line 42 skipping to change at page 44, line 24
current UTC offset. current UTC offset.
In PTP systems whose epoch is the PTP epoch, the value of In PTP systems whose epoch is the PTP epoch, the value of
timePropertiesDS.currentUtcOffset is the offset timePropertiesDS.currentUtcOffset is the offset
between TAI and UTC; otherwise the value has no meaning. The between TAI and UTC; otherwise the value has no meaning. The
value shall be in units of seconds. value shall be in units of seconds.
The initialization value shall be selected as follows: The initialization value shall be selected as follows:
a) If the timePropertiesDS.ptpTimescale (see 8.2.4.8) is TRUE, a) If the timePropertiesDS.ptpTimescale (see 8.2.4.8) is TRUE,
the value is the value obtained from a the value is the value obtained from a
primary reference if the value is known at the time of primary reference if the value is known at the time of
initialization, else. initialization, else,
b) The value shall be the current number of leap seconds (7.2.3) b) The value shall be the current number of leap seconds (7.2.3)
when the node is designed." when the node is designed."
REFERENCE "Section 8.2.4.3 of [IEEE 1588-2008]" REFERENCE "Section 8.2.4.3 of [IEEE 1588-2008]"
::= { ptpbaseClockTimePropertiesDSEntry 5 } ::= { ptpbaseClockTimePropertiesDSEntry 5 }
ptpbaseClockTimePropertiesDSLeap59 OBJECT-TYPE ptpbaseClockTimePropertiesDSLeap59 OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 41, line 28 skipping to change at page 48, line 43
::= { ptpbaseClockPortTable 1 } ::= { ptpbaseClockPortTable 1 }
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 AutonomousType,
ptpbaseClockPortCurrentPeerAddress ClockPortTransportTypeAddress, ptpbaseClockPortCurrentPeerAddress
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 42, line 44 skipping to change at page 50, line 29
ptpbaseClockPortSyncOneStep OBJECT-TYPE ptpbaseClockPortSyncOneStep OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies that one-step clock operation between "This object specifies that one-step clock operation between
the PTP master and slave device is enabled." the PTP master and slave device is enabled."
::= { ptpbaseClockPortEntry 7 } ::= { ptpbaseClockPortEntry 7 }
ptpbaseClockPortCurrentPeerAddressType OBJECT-TYPE ptpbaseClockPortCurrentPeerAddressType OBJECT-TYPE
SYNTAX ClockPortTransportType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the current peer's network address used "This object specifies the current peer's network address used
for PTP communication." for PTP communication."
::= { ptpbaseClockPortEntry 8 } ::= { ptpbaseClockPortEntry 8 }
ptpbaseClockPortCurrentPeerAddress OBJECT-TYPE ptpbaseClockPortCurrentPeerAddress OBJECT-TYPE
SYNTAX ClockPortTransportTypeAddress SYNTAX ClockPortTransportTypeAddress
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 47, line 23 skipping to change at page 56, line 10
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 ClockPortTransportType, ptpbaseClockPortRunningTransport AutonomousType,
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 49, line 27 skipping to change at page 58, line 32
ptpbaseClockPortRunningInterfaceIndex OBJECT-TYPE ptpbaseClockPortRunningInterfaceIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the interface on the router being used by "This object specifies the interface on the router being used by
the PTP Clock for PTP communication." the PTP Clock for PTP communication."
::= { ptpbaseClockPortRunningEntry 8 } ::= { ptpbaseClockPortRunningEntry 8 }
ptpbaseClockPortRunningTransport OBJECT-TYPE ptpbaseClockPortRunningTransport OBJECT-TYPE
SYNTAX ClockPortTransportType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the transport protocol being used for PTP "This object specifies the transport protocol being used for PTP
communication (the mapping used)." communication (the mapping used)."
::= { ptpbaseClockPortRunningEntry 9 } ::= { ptpbaseClockPortRunningEntry 9 }
ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE ptpbaseClockPortRunningEncapsulationType OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 52, line 33 skipping to change at page 62, line 22
REFERENCE "Section 8.3.3.3.2 of [IEEE 1588-2008]" REFERENCE "Section 8.3.3.3.2 of [IEEE 1588-2008]"
::= { ptpbaseClockPortTransDSEntry 6 } ::= { ptpbaseClockPortTransDSEntry 6 }
ptpbaseClockPortTransDSPeerMeanPathDelay OBJECT-TYPE ptpbaseClockPortTransDSPeerMeanPathDelay OBJECT-TYPE
SYNTAX ClockTimeInterval SYNTAX ClockTimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies, (if the delayMechanism used is P2P) the "This object specifies, (if the delayMechanism used is P2P) the
value is the estimate of the current one-way propagation delay, value is the estimate of the current one-way propagation delay,
i.e., <meanPathDelay> on the link attached to this port i.e., <meanPathDelay> on the link attached to this port,
computed computed using the peer delay mechanism. If the value of the
using the peer delay mechanism. If the value of the delayMechanism used is E2E, then the value will be zero."
delayMechanism
used is E2E, then the value will be zero."
REFERENCE "Section 8.3.3.3.3 of [IEEE 1588-2008]" REFERENCE "Section 8.3.3.3.3 of [IEEE 1588-2008]"
::= { ptpbaseClockPortTransDSEntry 7 } ::= { ptpbaseClockPortTransDSEntry 7 }
ptpbaseClockPortAssociateTable OBJECT-TYPE ptpbaseClockPortAssociateTable OBJECT-TYPE
SYNTAX SEQUENCE OF PtpbaseClockPortAssociateEntry SYNTAX SEQUENCE OF PtpbaseClockPortAssociateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of information about a given port's associated ports. "Table of information about a given port's associated ports.
For a master port - multiple slave ports which have established For a master port: multiple slave ports which have established
sessions with the current master port. sessions with the current master port.
For a slave port - the list of masters available for a given For a slave port: the list of masters available for a given
slave port. slave port.
Session information (pkts, errors) to be displayed based on Session information (packets, errors) to be displayed based on
availability and scenario." availability and scenario."
::= { ptpbaseMIBClockInfo 11 } ::= { ptpbaseMIBClockInfo 11 }
ptpbaseClockPortAssociateEntry OBJECT-TYPE ptpbaseClockPortAssociateEntry OBJECT-TYPE
SYNTAX PtpbaseClockPortAssociateEntry SYNTAX PtpbaseClockPortAssociateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information about a single "An entry in the table, containing information about a single
associated port for the given clockport." associated port for the given clockport."
skipping to change at page 53, line 29 skipping to change at page 63, line 25
ptpbaseClockPortAssociatePortIndex ptpbaseClockPortAssociatePortIndex
} }
::= { 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 AutonomousType,
ptpbaseClockPortAssociateAddress ClockPortTransportTypeAddress, ptpbaseClockPortAssociateAddress
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 54, line 28 skipping to change at page 64, line 34
ptpbaseClockPortAssociatePortIndex OBJECT-TYPE ptpbaseClockPortAssociatePortIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the associated port's serial number in "This object specifies the associated port's serial number in
the current port's context." the current port's context."
::= { ptpbaseClockPortAssociateEntry 5 } ::= { ptpbaseClockPortAssociateEntry 5 }
ptpbaseClockPortAssociateAddressType OBJECT-TYPE ptpbaseClockPortAssociateAddressType OBJECT-TYPE
SYNTAX ClockPortTransportType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the peer port's network address type used "This object specifies the peer port's network address type used
for PTP communication." for PTP communication."
::= { ptpbaseClockPortAssociateEntry 6 } ::= { ptpbaseClockPortAssociateEntry 6 }
ptpbaseClockPortAssociateAddress OBJECT-TYPE ptpbaseClockPortAssociateAddress OBJECT-TYPE
SYNTAX ClockPortTransportTypeAddress SYNTAX ClockPortTransportTypeAddress
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 56, line 7 skipping to change at page 66, line 29
ptpbaseMIBCompliances OBJECT IDENTIFIER ptpbaseMIBCompliances OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 1 } ::= { ptpbaseMIBConformance 1 }
ptpbaseMIBGroups OBJECT IDENTIFIER ptpbaseMIBGroups OBJECT IDENTIFIER
::= { ptpbaseMIBConformance 2 } ::= { ptpbaseMIBConformance 2 }
ptpbaseMIBCompliancesSystemInfo MODULE-COMPLIANCE ptpbaseMIBCompliancesSystemInfo MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide read-only support "Compliance statement for agents that provide read-only support
for PTPBASE-MIB to provide system level information of clock devices. for PTPBASE-MIB to provide system level information of clock
devices.
Such devices can only be monitored using this MIB module. Such devices can only be monitored using this MIB module.
The Module is implemented with support for read-only. In other The Module is implemented with support for read-only. In other
words, only monitoring is available by implementing this words, only monitoring is available by implementing this
MODULE-COMPLIANCE." MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { ptpbaseMIBSystemInfoGroup } MANDATORY-GROUPS { ptpbaseMIBSystemInfoGroup }
::= { ptpbaseMIBCompliances 1 } ::= { ptpbaseMIBCompliances 1 }
ptpbaseMIBCompliancesClockInfo MODULE-COMPLIANCE ptpbaseMIBCompliancesClockInfo MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide read-only support "Compliance statement for agents that provide read-only support
for PTPBASE-MIB to provide clock related information. Such devices can for PTPBASE-MIB to provide clock related information.
only be monitored using this MIB module.
Such devices can only be monitored using this MIB module.
The Module is implemented with support for read-only. In other The Module is implemented with support for read-only. In other
words, only monitoring is available by implementing this words, only monitoring is available by implementing this
MODULE-COMPLIANCE." MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ptpbaseMIBClockCurrentDSGroup, ptpbaseMIBClockCurrentDSGroup,
ptpbaseMIBClockParentDSGroup, ptpbaseMIBClockParentDSGroup,
ptpbaseMIBClockDefaultDSGroup, ptpbaseMIBClockDefaultDSGroup,
ptpbaseMIBClockRunningGroup, ptpbaseMIBClockRunningGroup,
ptpbaseMIBClockTimepropertiesGroup ptpbaseMIBClockTimepropertiesGroup
} }
::= { ptpbaseMIBCompliances 2 } ::= { ptpbaseMIBCompliances 2 }
ptpbaseMIBCompliancesClockPortInfo MODULE-COMPLIANCE ptpbaseMIBCompliancesClockPortInfo MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide read-only support "Compliance statement for agents that provide read-only support
for PTPBASE-MIB to provide clock port related information. Such devices for PTPBASE-MIB to provide clock port related information.
can only be monitored using this MIB module. Such devices can only be monitored using this MIB module.
The Module is implemented with support for read-only. In other The Module is implemented with support for read-only. In other
words, only monitoring is available by implementing this words, only monitoring is available by implementing this
MODULE-COMPLIANCE." MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ptpbaseMIBClockPortGroup, ptpbaseMIBClockPortGroup,
ptpbaseMIBClockPortDSGroup, ptpbaseMIBClockPortDSGroup,
ptpbaseMIBClockPortRunningGroup, ptpbaseMIBClockPortRunningGroup,
ptpbaseMIBClockPortAssociateGroup ptpbaseMIBClockPortAssociateGroup
} }
::= { ptpbaseMIBCompliances 3 } ::= { ptpbaseMIBCompliances 3 }
ptpbaseMIBCompliancesTransparentClockInfo MODULE-COMPLIANCE ptpbaseMIBCompliancesTransparentClockInfo MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide read-only support "Compliance statement for agents that provide read-only support
for PTPBASE-MIB to provide Transparent clock related information. Such for PTPBASE-MIB to provide Transparent clock related
devices can only be monitored using this MIB module. information.
Such devices can only be monitored using this MIB module.
The Module is implemented with support for read-only. In other The Module is implemented with support for read-only. In other
words, only monitoring is available by implementing this words, only monitoring is available by implementing this
MODULE-COMPLIANCE." MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ptpbaseMIBClockTranparentDSGroup, ptpbaseMIBClockTranparentDSGroup,
ptpbaseMIBClockPortTransDSGroup ptpbaseMIBClockPortTransDSGroup
} }
::= { ptpbaseMIBCompliances 4 } ::= { ptpbaseMIBCompliances 4 }
skipping to change at page 61, line 4 skipping to change at page 72, line 29
ptpbaseClockPortAssociateInErrors, ptpbaseClockPortAssociateInErrors,
ptpbaseClockPortAssociateOutErrors ptpbaseClockPortAssociateOutErrors
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group which aggregates objects describing information on peer "Group which aggregates objects describing information on peer
PTP ports for a given PTP clock-port." PTP ports for a given PTP clock-port."
::= { ptpbaseMIBGroups 12 } ::= { ptpbaseMIBGroups 12 }
END 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. It does not contain writable objects.
objects is relatively innocuous, unauthorized access to the write-
able objects could cause a denial of service, or could cause
unauthorized creation and/or manipulation of tunnels. Hence, the
support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations.
SNMPv1 by itself is such an insecure environment. Even if the Some of the readable objects in this MIB module (i.e., objects with a
network itself is secure (for example by using IPSec), even then, MAX-ACCESS other than not-accessible) may be considered sensitive or
there is no control as to who on the secure network is allowed to vulnerable in some network environments. It is thus important to
access and SET (change/create/delete) the objects in this MIB. 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.
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.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework (see [RFC 3410], section
of the User-based Security Model [RFC 3414] and the View-based Access 8). Specifically, the use of the User-based Security Model
Control Model [RFC 3415] is recommended. [RFC 3414] and the View-based Access Control Model [RFC 3415] is
recommended.
It is then a customer/user responsibility to ensure that the SNMP Further, deployment of SNMP versions prior to SNMPv3 is NOT
entity giving access to this MIB, is properly configured to give recommended. Instead, it is recommended to deploy SNMPv3 and to
access to those objects only to those principals (users) that have enable cryptographic security. It is then a customer/operator
legitimate rights to access them. responsibility to ensure that the SNMP entity giving access to an
instance of this MIB is properly configured to give access to those
objects only to those principals (users) that have legitimate rights
to access them.
6. IANA Considerations 6. IANA Considerations
To be added. The MIB module defined in this document uses the following IANA-
assigned OBJECT IDENTIFIER value recorded in the SMI Numbers
registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
ptpbaseMIB { mib-2 xxx }
[NOTE for IANA: Please allocate an object identifier at
http://www.iana.org/assignments/smi-numbers for object ptpbaseMIB.]
7. References 7. References
7.1. Normative References 7.1. Normative References
[IEEE 1588-2008] "IEEE Standard for A Precision Clock Synchronization [IEEE 1588-2008] "IEEE Standard for A Precision Clock Synchronization
Protocol for Networked Measurement and Control Systems", IEEE Std. Protocol for Networked Measurement and Control Systems", IEEE Std.
1588(TM)-2008, 24 July 2008 1588(TM)-2008, 24 July 2008
7.2. Informative References 7.2. Informative References
skipping to change at page 62, line 33 skipping to change at page 74, line 30
[RFC 2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC 2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", STD 58, RFC "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC 2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC 2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC 2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC 2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC 3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet Standard
Management Framework", RFC 3410 SNMP Research, Inc., Network
Associates Laboratories, Ericsson, December 2002.
[RFC 3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC 3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Protocol (SNMP) Architecture for Describing Simple Network Management Protocol (SNMP)
Management Frameworks", STD 62, RFC 3411, Enterasys Networks, BMC Management Frameworks", STD 62, RFC 3411, Enterasys Networks, BMC
Software, Inc., Lucent Technologies, December 2002 Software, Inc., Lucent Technologies, December 2002
[RFC 3412] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC 3412] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple Network Management "Message Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", STD 62, RFC 3412, SNMP Research, Inc., Enterasys Protocol (SNMP)", STD 62, RFC 3412, SNMP Research, Inc., Enterasys
Networks, BMC Software, Inc., Lucent Technologies, December 2002. Networks, BMC Software, Inc., Lucent Technologies, December 2002.
skipping to change at page 63, line 31 skipping to change at page 75, line 34
and Metropolitan area networks - Specific requirements Part 3: and Metropolitan area networks - Specific requirements Part 3:
Carrier sense multiple access with Collision Detection (CSMA/CD) Carrier sense multiple access with Collision Detection (CSMA/CD)
Access Method and Physical Layer Specifications", IEEE Std. 802.3 - Access Method and Physical Layer Specifications", IEEE Std. 802.3 -
2008, 26 December 2008 2008, 26 December 2008
[G.8265.1] "Precision time protocol telecom profile for frequency [G.8265.1] "Precision time protocol telecom profile for frequency
synchronization", ITU-T Recommendation G.8265.1, October 2010. synchronization", ITU-T Recommendation G.8265.1, October 2010.
8. Acknowledgements 8. Acknowledgements
Thanks to John Linton and Danny Lee for valuable comments. Thanks to John Linton and Danny Lee for valuable comments, and to
Bert Wijnen, Kevin Gross and Alan Luchuk for their reviews of this
MIB.
9. Author's Addresses 9. Author's Addresses
Vinay Shankarkumar Vinay Shankarkumar
Cisco Systems, Cisco Systems,
7025-4 Kit Creek Road, 7025-4 Kit Creek Road,
Research Triangle Park, Research Triangle Park,
NC 27560, NC 27560,
USA. USA.
Email: vinays@cisco.com
Email: vinays@cisco.com
Laurent Montini, Laurent Montini,
Cisco Systems, Cisco Systems,
11, rue Camille Desmoulins, 11, rue Camille Desmoulins,
92782 Issy-les-Moulineaux, 92782 Issy-les-Moulineaux,
France. France.
Email: lmontini@cisco.com Email: lmontini@cisco.com
Tim Frost, Tim Frost,
Symmetricom Inc., Symmetricom Inc.,
2300 Orchard Parkway, 2300 Orchard Parkway,
San Jose, San Jose,
CA 95131, CA 95131,
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
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, Email: gdowd@symmetricom.com
... 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. 70 change blocks. 
163 lines changed or deleted 185 lines changed or added

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