draft-ietf-tictoc-ptp-mib-05.txt   draft-ietf-tictoc-ptp-mib-06.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
Tim Frost Tim Frost
Greg Dowd Calnex Solutions Ltd.
Symmetricom
Expires: August 25, 2013 February 25, 2013 Greg Dowd
Microsemi
Expires: September 12, 2014 March 12, 2014
Precision Time Protocol Version 2 (PTPv2) Precision Time Protocol Version 2 (PTPv2)
Management Information Base Management Information Base
draft-ietf-tictoc-ptp-mib-05.txt draft-ietf-tictoc-ptp-mib-06.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 39
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 August 25, 2013. This Internet-Draft will expire on September 12, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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, specified in [IEEE 1588-2008]. Precision Time Protocol, specified in IEEE Std. 1588(TM)-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 ....................................... 6
5. Security Considerations.......................................74 5. Security Considerations ...................................... 75
6. IANA Considerations...........................................75 6. IANA Considerations .......................................... 75
7. References....................................................75 7. References ................................................... 76
7.1. Normative References.....................................75 7.1. Normative References .................................... 76
7.2. Informative References...................................75 7.2. Informative References .................................. 76
8. Acknowledgements..............................................77 8. Acknowledgements ............................................. 78
9. Author's Addresses............................................77 9. Author's Addresses ........................................... 78
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 5 skipping to change at page 4, line 7
-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 12 Minor changes following comments from Andy Bierman: -03 Jul 12 Minor changes following comments from Andy Bierman:
- corrected some compilation errors - corrected some compilation errors
- moved OBJECT-GROUP and MODULE-COMPLIANCE macros to the - moved OBJECT-GROUP and MODULE-COMPLIANCE macros to the
end end
-04 Jan 13 Changes: -04 Jan 13 Changes:
- Use of 'AutonomousType' import - Use of 'AutonomousType' import
- Display hint being specified for ClockIdentity, - Display hint being specified for ClockIdentity,
ClockInterval, ClockPortTransportTypeAddress ClockInterval, ClockPortTransportTypeAddress
Textual Conventions Textual Conventions
- Removal of the Textual convention - Removal of the Textual convention
ClockPortTransportType, replaced with the ClockPortTransportType, replaced with the
wellKnownTransportTypes wellKnownTransportTypes
- Modified ptpbaseClockPortCurrentPeerAddressType, - Modified ptpbaseClockPortCurrentPeerAddressType,
ptpbaseClockPortRunningTransport, ptpbaseClockPortRunningTransport,
ptpbaseClockPortAssociateAddressType, to use ptpbaseClockPortAssociateAddressType, to use
AutonomousType. AutonomousType.
- various textual changes to descriptive text in - various textual changes to descriptive text in
response to comments response to comments
-05 Feb 13 Several changes in response to comments from Alun Luchuk -05 Feb 13 Several changes in response to comments from Alun Luchuk
and Kevin Gross: and Kevin Gross:
- Modified the use of wellKnownTransportTypes and - Modified the use of wellKnownTransportTypes and
wellKnownEncapsulationTypes wellKnownEncapsulationTypes
- changed ptpbaseClockPortSyncOneStep to - changed ptpbaseClockPortSyncOneStep to
ptpbaseClockPortSyncTwoStep to match IEEE1588 ptpbaseClockPortSyncTwoStep to match IEEE1588
semantics semantics
- Re-ordered textual conventions to be alphabetic - Re-ordered textual conventions to be alphabetic
- Changed some types from Integer32 to use defined - Changed some types from Integer32 to use defined
textual conventions textual conventions
- various minor descriptive text changes - various minor descriptive text changes
-06 Mar 14 Updated author information, and fixed typos
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]. o An overall architecture, described in STD62, [RFC 3411].
o 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].
o 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].
o 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].
o 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 6, line 39 skipping to change at page 6, line 46
Vinay Shankarkumar Vinay Shankarkumar
Cisco Systems, Cisco Systems,
Email: vinays@cisco.com Email: vinays@cisco.com
Laurent Montini, Laurent Montini,
Cisco Systems, Cisco Systems,
Email: lmontini@cisco.com Email: lmontini@cisco.com
Tim Frost, Tim Frost,
Symmetricom Inc., Calnex Solutions Ltd.,
Email: tfrost@symmetricom.com Email: tim.frost@calnexsol.com
Greg Dowd, Greg Dowd,
Symmetricom Inc., Microsemi Inc.,
Email: gdowd@symmetricom.com" Email: greg.dowd@microsemi.com"
DESCRIPTION DESCRIPTION
"The MIB module for PTP version 2 (IEEE Std. 1588(TM)-2008) "The MIB module for PTP version 2 (IEEE Std. 1588(TM)-2008)
Overview of PTP version 2 (IEEE Std. 1588(TM)-2008) Overview of PTP version 2 (IEEE Std. 1588(TM)-2008)
[IEEE 1588-2008] defines a protocol enabling precise [IEEE 1588-2008] defines a protocol enabling precise
synchronization of clocks in measurement and control systems synchronization of clocks in measurement and control systems
implemented with packet-based networks, the Precision Time implemented with packet-based networks, the Precision Time
Protocol Version 2 (PTPv2). This MIB does not address the Protocol Version 2 (PTPv2). This MIB does not address the
skipping to change at page 50, line 45 skipping to change at page 51, line 10
DESCRIPTION DESCRIPTION
"This object specifies that two-step clock operation between "This object specifies that two-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 AutonomousType 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 type
for PTP communication." used 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
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 9 } ::= { ptpbaseClockPortEntry 9 }
skipping to change at page 53, line 25 skipping to change at page 53, line 34
DESCRIPTION DESCRIPTION
"This object specifies the PTP portnumber associated with this "This object specifies the PTP portnumber associated with this
PTP port." PTP port."
::= { ptpbaseClockPortDSEntry 4 } ::= { ptpbaseClockPortDSEntry 4 }
ptpbaseClockPortDSName OBJECT-TYPE ptpbaseClockPortDSName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..64)) SYNTAX DisplayString (SIZE (1..64))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the PTP clock port name." "This object specifies the PTP clock port dataset name."
::= { ptpbaseClockPortDSEntry 5 } ::= { ptpbaseClockPortDSEntry 5 }
ptpbaseClockPortDSPortIdentity OBJECT-TYPE ptpbaseClockPortDSPortIdentity OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(1..256)) SYNTAX OCTET STRING(SIZE(1..256))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the PTP clock port Identity." "This object specifies the PTP clock port Identity."
::= { ptpbaseClockPortDSEntry 6 } ::= { ptpbaseClockPortDSEntry 6 }
skipping to change at page 78, line 16 skipping to change at page 78, line 31
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., Calnex Solutions Ltd.,
2300 Orchard Parkway, Herkimer House,
San Jose, Linlithgow,
CA 95131, EH49 7SF,
USA. UK.
Email: tfrost@symmetricom.com Email: tim.frost@calnexsol.com
Greg Dowd, Greg Dowd,
Symmetricom Inc., Microsemi Inc.,
2300 Orchard Parkway, 2300 Orchard Parkway,
San Jose, San Jose,
CA 95131, CA 95131,
USA. USA.
Email: gdowd@symmetricom.com Email: greg.dowd@microsemi.com
 End of changes. 25 change blocks. 
46 lines changed or deleted 50 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/