draft-ietf-tictoc-ptp-mib-01.txt   draft-ietf-tictoc-ptp-mib-02.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 Greg Dowd
Symmetricom Symmetricom
Expires: August 6, 2012 February 6, 2012 Expires: January 16, 2013 July 16, 2012
Precision Time Protocol Version 2 (PTPv2) Precision Time Protocol Version 2 (PTPv2)
Management Information Base Management Information Base
draft-ietf-tictoc-ptp-mib-01.txt draft-ietf-tictoc-ptp-mib-02.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 August 6, 2012. This Internet-Draft will expire on January 16, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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..................................3 2. The SNMP Management Framework..................................4
3. Overview.......................................................4 3. Overview.......................................................5
4. IETF PTP MIB Definition........................................5 4. IETF PTP MIB Definition........................................5
5. Security Considerations.......................................63 5. Security Considerations.......................................72
6. IANA Considerations...........................................64 6. IANA Considerations...........................................72
7. References....................................................64 7. References....................................................73
7.1. Normative References.....................................64 7.1. Normative References.....................................73
7.2. Informative References...................................64 7.2. Informative References...................................73
8. Acknowledgements..............................................66 8. Acknowledgements..............................................75
9. Author's Addresses............................................66 9. Author's Addresses............................................75
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 3, line 27 skipping to change at page 3, line 27
defined to monitor, measure the performance of the PTP devices and defined to monitor, measure the performance of the PTP devices and
telecom clocks. telecom clocks.
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. This section tracks changes made to the
visions of the Internet Drafts of this document. It will be revisions of the Internet Drafts of this document. It will be
*deleted* when the document is published as an RFC. *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:
- changed "ptpbaseClockPortRunningIPversion" to the more
generic "ptpbaseClockPortRunningTransport", covering
all transport types defined in [IEEE 1588-2008]
(i.e. IPv4, IPv6, Ethernet, DeviceNet and ControlNet).
- changed addresses associated with transports from
"InetAddress" (for the IP transport) to a string,
to allow for the different transport types.
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
skipping to change at page 5, line 26 skipping to change at page 5, line 31
Counter64 Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
OBJECT-GROUP, OBJECT-GROUP,
MODULE-COMPLIANCE MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TEXTUAL-CONVENTION,
TruthValue, TruthValue,
DisplayString DisplayString
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB;
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB;
ptpbaseMIB MODULE-IDENTITY ptpbaseMIB MODULE-IDENTITY
LAST-UPDATED "201201230000Z" LAST-UPDATED "201201230000Z"
ORGANIZATION "TICTOC Working Group" ORGANIZATION "TICTOC Working Group"
CONTACT-INFO CONTACT-INFO
"WG Email: tictoc@ietf.org "WG Email: tictoc@ietf.org
Vinay Shankarkumar Vinay Shankarkumar
Cisco Systems, Cisco Systems,
Email: vinays@cisco.com Email: vinays@cisco.com
skipping to change at page 7, line 51 skipping to change at page 8, line 24
output is complete. output is complete.
Boundary clock: Boundary clock:
A clock that has multiple Precision Time Protocol (PTP) ports in A clock that has multiple Precision Time Protocol (PTP) ports in
a domain and maintains the timescale used in the domain. It a domain and maintains the timescale used in the domain. It
may serve as the source of time, i.e., be a master clock, and may serve as the source of time, i.e., be a master clock, and
may synchronize to another clock, i.e., be a slave clock. may synchronize to another clock, i.e., be a slave clock.
Boundary node clock: Boundary node clock:
A clock that has multiple Precision Time Protocol(PTP) ports in A clock that has multiple Precision Time Protocol(PTP) ports in
a domain and maintains the timescale used in the domain. It a domain and maintains the timescale used in the domain. It
differs from a boundary clock in that the clock roles can differs from a boundary clock in that the clock roles can
change. change.
Clock: Clock:
A node participating in the Precision Time Protocol (PTP) that A node participating in the Precision Time Protocol (PTP) that
is capable of providing a measurement of the passage of time is capable of providing a measurement of the passage of time
since a defined epoch. since a defined epoch.
Domain: Domain:
A logical grouping of clocks that synchronize to each other A logical grouping of clocks that synchronize to each other
skipping to change at page 11, line 48 skipping to change at page 12, line 44
Transparent clock: Transparent clock:
A device that measures the time taken for a Precision Time A device that measures the time taken for a Precision Time
Protocol event message to transit the device and provides this Protocol event message to transit the device and provides this
information to clocks receiving this PTP event message. information to clocks receiving this PTP event message.
Two-step clock: Two-step clock:
A clock that provides time information using the combination of A clock that provides time information using the combination of
an event message and a subsequent general message. an event message and a subsequent general message.
The below table specifies the object formats of the various The table below specifies the object formats of the various
textual conventions used. textual conventions used.
Data type mapping Textual Convention SYNTAX Data type mapping Textual Convention SYNTAX
------------------- ------------------ --------------------- ------------------- ------------------ ---------------------
5.3.2 TimeInterval ClockTimeInterval OCTET STRING(SIZE(1..255)) 5.3.2 TimeInterval ClockTimeInterval OCTET STRING(SIZE(1..255))
5.3.3 Timestamp ClockTimestamp OCTET STRING(SIZE(6)) 5.3.3 Timestamp ClockTimestamp OCTET STRING(SIZE(6))
5.3.4 ClockIdentity ClockIdentity OCTET STRING(SIZE(1..255)) 5.3.4 ClockIdentity ClockIdentity OCTET STRING(SIZE(1..255))
5.3.5 PortIdentity ClockPortNumber INTEGER(1..65535) 5.3.5 PortIdentity ClockPortNumber INTEGER(1..65535)
5.3.7 ClockQuality ClockQualityClassType 5.3.7 ClockQuality ClockQualityClassType
skipping to change at page 21, line 33 skipping to change at page 24, line 5
REFERENCE "Section 5.3.7, 7.6.2.6 and Table 7 of REFERENCE "Section 5.3.7, 7.6.2.6 and Table 7 of
[IEEE 1588-2008]." [IEEE 1588-2008]."
SYNTAX INTEGER { SYNTAX INTEGER {
atomicClock(16), -- 0x10 atomicClock(16), -- 0x10
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
internalOsillator(160) -- 0xA0 internalOscillator(160) -- 0xA0
} }
ClockTimeInterval ::= TEXTUAL-CONVENTION ClockTimeInterval ::= TEXTUAL-CONVENTION
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.
skipping to change at page 22, line 45 skipping to change at page 25, line 23
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
DESCRIPTION
"The Clock port transport type. The transport protocol used for
the communication between the clock nodes. This includes
IP version 4, IP version 6, Ethernet, DeviceNet, ControlNet and
IEC61158."
REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet),
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
STATUS current
DESCRIPTION
"The Clock port transport protocol address used for the
communication between the clock nodes. This is a string
corresponding to the address type as specified by the
ClockPortTransportType.
This can be an address of types IP version 4, IP version 6,
Ethernet, DeviceNet, ControlNet and IEC61158."
REFERENCE "Annex D (IPv4), Annex E (IPv6), Annex F (Ethernet),
Annex G (DeviceNet), Annex H (ControlNet) and
Annex I (IEC61158) of [IEEE 1588-2008]"
SYNTAX OCTET STRING (SIZE (1..255))
ptpbaseMIBNotifs OBJECT IDENTIFIER ptpbaseMIBNotifs OBJECT IDENTIFIER
::= { ptpbaseMIB 0 } ::= { ptpbaseMIB 0 }
ptpbaseMIBObjects OBJECT IDENTIFIER ptpbaseMIBObjects OBJECT IDENTIFIER
::= { ptpbaseMIB 1 } ::= { ptpbaseMIB 1 }
ptpbaseMIBConformance OBJECT IDENTIFIER ptpbaseMIBConformance OBJECT IDENTIFIER
::= { ptpbaseMIB 2 } ::= { ptpbaseMIB 2 }
ptpbaseMIBSystemInfo OBJECT IDENTIFIER ptpbaseMIBSystemInfo OBJECT IDENTIFIER
skipping to change at page 27, line 34 skipping to change at page 31, line 34
"Group which aggregates objects describing PTP Port Dataset "Group which aggregates objects describing PTP Port Dataset
information" information"
::= { ptpbaseMIBGroups 9 } ::= { ptpbaseMIBGroups 9 }
ptpbaseMIBClockPortRunningGroup OBJECT-GROUP ptpbaseMIBClockPortRunningGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ptpbaseClockPortRunningName, ptpbaseClockPortRunningName,
ptpbaseClockPortRunningState, ptpbaseClockPortRunningState,
ptpbaseClockPortRunningRole, ptpbaseClockPortRunningRole,
ptpbaseClockPortRunningInterfaceIndex, ptpbaseClockPortRunningInterfaceIndex,
ptpbaseClockPortRunningIPversion, ptpbaseClockPortRunningTransport,
ptpbaseClockPortRunningEncapsulationType, ptpbaseClockPortRunningEncapsulationType,
ptpbaseClockPortRunningTxMode, ptpbaseClockPortRunningTxMode,
ptpbaseClockPortRunningRxMode, ptpbaseClockPortRunningRxMode,
ptpbaseClockPortRunningPacketsReceived, ptpbaseClockPortRunningPacketsReceived,
ptpbaseClockPortRunningPacketsSent ptpbaseClockPortRunningPacketsSent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group which aggregates objects describing PTP running interface "Group which aggregates objects describing PTP running interface
information" information"
skipping to change at page 48, line 10 skipping to change at page 55, line 7
::= { 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 InetAddressType, ptpbaseClockPortCurrentPeerAddressType ClockPortTransportType,
ptpbaseClockPortCurrentPeerAddress InetAddress, 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 49, line 29 skipping to change at page 56, line 33
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 InetAddressType SYNTAX ClockPortTransportType
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. Based on the scenario and the setup for PTP communication."
involved, the values might look like these -
Scenario Value
------------------- ----------------
Single Master master port
Multiple Masters selected master port
Single Slave slave port
Multiple Slaves <empty>
(In relevant setups, information on available
slaves and available masters will be available through
ptpClockPortAssociateTable)"
::= { ptpbaseClockPortEntry 8 } ::= { ptpbaseClockPortEntry 8 }
ptpbaseClockPortCurrentPeerAddress OBJECT-TYPE ptpbaseClockPortCurrentPeerAddress OBJECT-TYPE
SYNTAX InetAddress 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. Based on the scenario and the setup for PTP communication."
involved, the values might look like these -
Scenario Value
------------------- ----------------
Single Master master port
Multiple Masters selected master port
Single Slave slave port
Multiple Slaves <empty>
(In relevant setups, information on available
slaves and available masters will be available through
ptpClockPortAssociateTable)"
::= { ptpbaseClockPortEntry 9 } ::= { ptpbaseClockPortEntry 9 }
ptpbaseClockPortNumOfAssociatedPorts OBJECT-TYPE ptpbaseClockPortNumOfAssociatedPorts OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies - "This object specifies -
For a master port - the number of PTP slave sessions (peers) For a master port - the number of PTP slave sessions (peers)
associated with this PTP port. associated with this PTP port.
skipping to change at page 54, line 43 skipping to change at page 62, line 14
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,
ptpbaseClockPortRunningIPversion Integer32, ptpbaseClockPortRunningTransport
ClockPortTransportType,
ptpbaseClockPortRunningEncapsulationType Integer32, ptpbaseClockPortRunningEncapsulationType Integer32,
ptpbaseClockPortRunningTxMode ClockTxModeType, ptpbaseClockPortRunningTxMode ClockTxModeType,
ptpbaseClockPortRunningRxMode ClockTxModeType, ptpbaseClockPortRunningRxMode ClockTxModeType,
ptpbaseClockPortRunningPacketsReceived Counter64, ptpbaseClockPortRunningPacketsReceived Counter64,
ptpbaseClockPortRunningPacketsSent Counter64 ptpbaseClockPortRunningPacketsSent Counter64
} }
ptpbaseClockPortRunningDomainIndex OBJECT-TYPE ptpbaseClockPortRunningDomainIndex OBJECT-TYPE
SYNTAX ClockDomainType SYNTAX ClockDomainType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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."
::= { ptpbaseClockPortRunningEntry 1 } ::= { ptpbaseClockPortRunningEntry 1 }
ptpbaseClockPortRunningClockTypeIndex OBJECT-TYPE ptpbaseClockPortRunningClockTypeIndex OBJECT-TYPE
skipping to change at page 57, line 5 skipping to change at page 64, line 36
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 }
ptpbaseClockPortRunningIPversion OBJECT-TYPE ptpbaseClockPortRunningTransport OBJECT-TYPE
SYNTAX Integer32 SYNTAX ClockPortTransportType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the IP version 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the type of encapsulation if the "This object specifies the type of encapsulation if the
interface is adding extra layers (eg. VLAN, Pseudowire interface is adding extra layers (eg. VLAN, Pseudowire
skipping to change at page 61, line 20 skipping to change at page 69, line 32
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 InetAddressType, ptpbaseClockPortAssociateAddressType ClockPortTransportType,
ptpbaseClockPortAssociateAddress InetAddress, 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 62, line 23 skipping to change at page 70, line 42
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 InetAddressType SYNTAX ClockPortTransportType
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 InetAddress SYNTAX ClockPortTransportTypeAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the peer port's network address used for "This object specifies the peer port's network address used for
PTP communication." PTP communication."
::= { ptpbaseClockPortAssociateEntry 7 } ::= { ptpbaseClockPortAssociateEntry 7 }
ptpbaseClockPortAssociatePacketsSent OBJECT-TYPE ptpbaseClockPortAssociatePacketsSent OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "packets" UNITS "packets"
 End of changes. 26 change blocks. 
58 lines changed or deleted 81 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/