draft-ietf-tictoc-ptp-mib-09.txt   draft-ietf-tictoc-ptp-mib-10.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
Calnex Solutions Ltd. Calnex Solutions Ltd.
Greg Dowd Greg Dowd
Microsemi Microsemi
Expires: October 21, 2016 April 21, 2016 Expires: February 22, 2017 August 22, 2016
Precision Time Protocol Version 2 (PTPv2) Precision Time Protocol Version 2 (PTPv2)
Management Information Base Management Information Base
draft-ietf-tictoc-ptp-mib-09.txt draft-ietf-tictoc-ptp-mib-10.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 39 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 October 21, 2016. This Internet-Draft will expire on February 22, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 32 skipping to change at page 2, line 32
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 ................................ 5 2. The SNMP Management Framework ................................ 5
3. Overview ..................................................... 6 3. Overview ..................................................... 6
4. IETF PTP MIB Definition ...................................... 6 4. IETF PTP MIB Definition ...................................... 6
5. Security Considerations ..................................... 6 5. Security Considerations ..................................... 6
6. IANA Considerations ......................................... 77 6. IANA Considerations ......................................... 79
7. References .................................................. 77 7. References .................................................. 79
7.1. Normative References ................................... 77 7.1. Normative References ................................... 79
7.2. Informative References ................................. 77 7.2. Informative References ................................. 79
8. Acknowledgements ............................................ 79 8. Acknowledgements ............................................ 81
9. Author's Addresses .......................................... 79 9. Author's Addresses .......................................... 82
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)
module for use with network management protocols in the Internet module for use with network management protocols in the Internet
Community. In particular, it describes managed objects used for Community. In particular, it describes managed objects used for
managing PTP devices including the ordinary clock, transparent clock, managing PTP devices including the ordinary clock, transparent clock,
boundary clocks. boundary clocks.
This MIB module is restricted to reading standard PTP data elements, This MIB module is restricted to reading standard PTP data elements,
skipping to change at page 5, line 7 skipping to change at page 5, line 7
-07 Mar 15 Updated author information, and fixed typo/enum -07 Mar 15 Updated author information, and fixed typo/enum
-08 Feb 16 Updated MIB in response to Brian Haberman's comments: -08 Feb 16 Updated MIB in response to Brian Haberman's comments:
- Fixed MIB date - Fixed MIB date
- Fixed references to IEEE1588-2008 - Fixed references to IEEE1588-2008
- Changed "router" for "node" - Changed "router" for "node"
-09 Apr 16 Updated following Dan Romascanu's MIB Doctor comments -09 Apr 16 Updated following Dan Romascanu's MIB Doctor comments
-10 Aug 16 Update following further feedback from Dan Romascanu.
Also updated security section to list out all objects
with MAX-ACCESS other than non-accessible, in response
to comments from Deborah Brungard and Alissa Cooper.
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
skipping to change at page 76, line 26 skipping to change at page 76, line 31
intruder can alter or create any management objects of this MIB intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations. module via direct SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. the network via SNMP.
The following objects all have a MAX-ACCESS of read-only:
ptpDomainClockPortsTotal,
ptpbaseSystemDomainTotals,
ptpbaseSystemProfile expose general information about the clock
system.
ptpbaseClockRunningState,
ptpbaseClockRunningPacketsSent,
ptpbaseClockRunningPacketsReceived expose a clock's current running
status.
ptpbaseClockCurrentDSStepsRemoved,
ptpbaseClockCurrentDSOffsetFromMaster,
ptpbaseClockCurrentDSMeanPathDelay expose the values of a clock's
current dataset (currentDS).
ptpbaseClockParentDSParentPortIdentity,
ptpbaseClockParentDSParentStats,
ptpbaseClockParentDSOffset,
ptpbaseClockParentDSClockPhChRate,
ptpbaseClockParentDSGMClockIdentity,
ptpbaseClockParentDSGMClockPriority1,
ptpbaseClockParentDSGMClockPriority2,
ptpbaseClockParentDSGMClockQualityClass,
ptpbaseClockParentDSGMClockQualityAccuracy,
ptpbaseClockParentDSGMClockQualityOffset expose the values of a
clock's parent dataset (parentDS).
ptpbaseClockDefaultDSTwoStepFlag,
ptpbaseClockDefaultDSClockIdentity,
ptpbaseClockDefaultDSPriority1,
ptpbaseClockDefaultDSPriority2,
ptpbaseClockDefaultDSSlaveOnly,
ptpbaseClockDefaultDSQualityClass,
ptpbaseClockDefaultDSQualityAccuracy,
ptpbaseClockDefaultDSQualityOffset expose the values of a clock's
default dataset (defaultDS).
ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid,
ptpbaseClockTimePropertiesDSCurrentUTCOffset,
ptpbaseClockTimePropertiesDSLeap59,
ptpbaseClockTimePropertiesDSLeap61,
ptpbaseClockTimePropertiesDSTimeTraceable,
ptpbaseClockTimePropertiesDSFreqTraceable,
ptpbaseClockTimePropertiesDSPTPTimescale,
ptpbaseClockTimePropertiesDSSource expose the values of a clock's
time properties dataset (timePropertiesDS).
ptpbaseClockTransDefaultDSClockIdentity,
ptpbaseClockTransDefaultDSNumOfPorts,
ptpbaseClockTransDefaultDSDelay,
ptpbaseClockTransDefaultDSPrimaryDomain expose the values of a
transparent clock's default dataset (transparentClockDefaultDS).
ptpbaseClockPortName,
ptpbaseClockPortRole,
ptpbaseClockPortSyncTwoStep,
ptpbaseClockPortCurrentPeerAddressType,
ptpbaseClockPortCurrentPeerAddress,
ptpbaseClockPortNumOfAssociatedPorts expose general information
about a clock port.
ptpbaseClockPortRunningName,
ptpbaseClockPortRunningState,
ptpbaseClockPortRunningRole,
ptpbaseClockPortRunningInterfaceIndex,
ptpbaseClockPortRunningTransport,
ptpbaseClockPortRunningEncapsulationType,
ptpbaseClockPortRunningTxMode,
ptpbaseClockPortRunningRxMode,
ptpbaseClockPortRunningPacketsReceived,
ptpbaseClockPortRunningPacketsSent expose a clock port's current
running status.
ptpbaseClockPortDSName,
ptpbaseClockPortDSPortIdentity,
ptpbaseClockPortDSlogAnnouncementInterval,
ptpbaseClockPortDSAnnounceRctTimeout,
ptpbaseClockPortDSlogSyncInterval,
ptpbaseClockPortDSMinDelayReqInterval,
ptpbaseClockPortDSPeerDelayReqInterval,
ptpbaseClockPortDSDelayMech,
ptpbaseClockPortDSPeerMeanPathDelay,
ptpbaseClockPortDSGrantDuration,
ptpbaseClockPortDSPTPVersion expose the values of a clock port's
port dataset (portDS).
ptpbaseClockPortTransDSPortIdentity,
ptpbaseClockPortTransDSlogMinPdelayReqInt,
ptpbaseClockPortTransDSFaultyFlag,
ptpbaseClockPortTransDSPeerMeanPathDelay expose the values of a
transparent clock port's port dataset (transparentClockPortDS).
ptpbaseClockPortAssociateAddressType,
ptpbaseClockPortAssociateAddress,
ptpbaseClockPortAssociatePacketsSent,
ptpbaseClockPortAssociatePacketsReceived,
ptpbaseClockPortAssociateInErrors,
ptpbaseClockPortAssociateOutErrors expose information about a clock
port's peer node.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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. allowed to access and GET (read) the objects in this MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC 3410]), and implementations claiming SNMPv3 framework (see [RFC 3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC 3414] with the AES cipher algorithm [RFC 3826]. Implementations [RFC 3414] with the AES cipher algorithm [RFC 3826]. Implementations
 End of changes. 6 change blocks. 
9 lines changed or deleted 116 lines changed or added

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