draft-ietf-hubmib-wis-mib-02.txt   draft-ietf-hubmib-wis-mib-03.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
INTERNET DRAFT BMC Software, Inc. INTERNET DRAFT BMC Software, Inc.
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
C. M. Heard C. M. Heard
Consultant Consultant
Kam Lam Kam Lam
Lucent Technologies Lucent Technologies
Kerry McDonald Kerry McDonald
CSU San Bernardino CSU San Bernardino
K. C. Norseth K. C. Norseth
Enterasys Networks Consultant
Kaj Tesink Kaj Tesink
Telcordia Technologies Telcordia Technologies
February 18, 2002 April 14, 2002
Definitions of Managed Objects Definitions of Managed Objects
for the Ethernet WAN Interface Sublayer for the Ethernet WAN Interface Sublayer
<draft-ietf-hubmib-wis-mib-02.txt> <draft-ietf-hubmib-wis-mib-03.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 5 skipping to change at page 2, line 5
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
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
1. Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based (MIB) for use with network management protocols in TCP/IP based
internets. In particular, it defines objects for managing the internets. In particular, it defines objects for managing the
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae]. Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).
The MIB module defined in this memo is implemented in conjunction The MIB module defined in this memo is an extension of the SONET/SDH
with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium Interface MIB and is implemented in conjunction with it and with the
Attachment Unit MIB [MAU-MIB], the Interfaces Group MIB [RFC2863], Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB,
and the Inverted Stack Table MIB [RFC2864]. It also extends the the Interfaces Group MIB, and the Inverted Stack Table MIB.
SONET MIB [SONETng] and is implemented in conjunction with that MIB
module. 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL", when they appear in this document, are to be interpreted
as described in RFC 2119 [RFC2119].
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 RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
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 3, line 29 skipping to change at page 3, line 29
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3. Overview 3. Overview
The objects defined in this memo are used in conjunction with objects The objects defined in this memo are used in conjunction with objects
defined in the Interfaces Group MIB [RFC2863], the SONET MIB defined in the Interfaces Group MIB [RFC2863], the SONET/SDH
[SONETng], and the MAU MIB [MAU-MIB] to manage the WAN Interface Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage
Sublayer (WIS) defined in [P802.3ae]. The WIS contains functions to the WAN Interface Sublayer (WIS) defined in [P802.3ae]. The WIS
perform OC-192c/VC-4-64c framing and scrambling. It resides between contains functions to perform OC-192c/VC-4-64c framing and
the PCS and PMA sublayers within a 10GBASE-W 10 Gb/s WAN-compatible scrambling. It resides between the PCS and PMA sublayers within a
PHY and may be used in conjunction with any of the PCS, PMA, and PMD 10GBASE-W 10 Gb/s WAN-compatible PHY and may be used in conjunction
sublayers that are defined in [P802.3ae] for 10GBASE-W PHYs. Three with any of the PCS, PMA, and PMD sublayers that are defined in
types of 10GBASE-W PHYs are defined, distinguished by the type of [P802.3ae] for 10GBASE-W PHYs. Three types of 10GBASE-W PHYs are
optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. The defined, distinguished by the type of optics employed: 10GBASE-SW,
objects defined in this memo may be used to manage an Ethernet 10GBASE-LW, and 10GBASE-EW. The objects defined in this memo may be
interface employing any type of 10GBASE-W PHY. They do not apply to used to manage an Ethernet interface employing any type of 10GBASE-W
any other kind of interface. In particular, they do not apply to PHY. They do not apply to any other kind of interface. In
so-called Ethernet Line Terminating Equipment (ELTE) residing within particular, they do not apply to so-called Ethernet Line Terminating
a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but Equipment (ELTE) residing within a SONET network element that uses
otherwise acts as SONET Line Terminating Equipment (LTE). the 10GBASE-W PMA/PMD sublayers but otherwise acts as SONET Line
Terminating Equipment (LTE).
The objects presented here -- along with those incorporated by The objects presented here -- along with those incorporated by
reference from the Interfaces Group MIB, the SONET MIB, and the MAU reference from the Interfaces Group MIB, the SONET/SDH Interface MIB,
MIB -- are intended to provide exact representations of the mandatory and the 802.3 MAU MIB -- are intended to provide exact
attributes in the oWIS managed object class (i.e., the members of the representations of the mandatory attributes in the oWIS managed
pWISBasic package) defined in Clause 30 and Annex 30A of [P802.3ae]. object class (i.e., the members of the pWISBasic package) defined in
They are also intended to provide approximate representations of the Clause 30 and Annex 30A of [P802.3ae]. They are also intended to
optional attributes (i.e., the members of the pWISOptional package). provide approximate representations of the optional attributes (i.e.,
Some objects with no analogues in oWIS are defined to support WIS the members of the pWISOptional package). Some objects with no
testing features required by Clause 50 of [P802.3ae]. analogues in oWIS are defined to support WIS testing features
required by Clause 50 of [P802.3ae].
3.1. Relationship to the SONET MIB 3.1. Relationship to the SONET/SDH Interface MIB
Since the Ethernet WAN Interface Sublayer was designed to be SONET- Since the Ethernet WAN Interface Sublayer was designed to be SONET-
compatible, information similar to that provided by most of the compatible, information similar to that provided by most of the
members of the oWIS managed object class is available from objects members of the oWIS managed object class is available from objects
defined in the SONET MIB [SONETng]. Thus, the MIB module defined in defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in
this memo is a sparse augmentation of the SONET MIB -- in other this memo is a sparse augmentation of the SONET-MIB -- in other
words, every table defined here is an extension of some table in the words, every table defined here is an extension of some table in the
SONET MIB -- and its compliance statement REQUIRES that an agent SONET-MIB -- and its compliance statement REQUIRES that an agent
implementing the objects defined in this memo also implement the implementing the objects defined in this memo also implement the
relevant SONET MIB objects. That includes all objects required by relevant SONET-MIB objects. That includes all objects required by
sonetCompliance2 as well as some that it leaves optional. sonetCompliance2 as well as some that it leaves optional.
It should be noted that some of the objects incorporated by reference It should be noted that some of the objects incorporated by reference
from the SONET MIB -- specifically, the threshold objects and from the SONET-MIB -- specifically, the threshold objects and
interval counter objects -- provide only approximate representations interval counter objects -- provide only approximate representations
of the corresponding oWIS attributes, as detailed in Section 3.6. An of the corresponding oWIS attributes, as detailed in Section 3.6. An
alternative approach would have been to define new objects to exactly alternative approach would have been to define new objects to exactly
match the oWIS definitions. That approach was rejected because the match the oWIS definitions. That approach was rejected because the
SONET MIB objects are already used in deployed systems to manage the SONET-MIB objects are already used in deployed systems to manage the
SONET sublayers of ATM over SONET and PPP over SONET interfaces, and SONET sublayers of ATM over SONET and PPP over SONET interfaces, and
it was deemed undesirable to use a different scheme to manage the it was deemed undesirable to use a different scheme to manage the
SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note
that the approach adopted by this memo requires no hardware support that the approach adopted by this memo requires no hardware support
beyond that mandated by [P802.3ae] subclause 50.3.10. beyond that mandated by [P802.3ae] subclause 50.3.11.
3.2. Relationship to the Ethernet-like Interfaces MIB 3.2. Relationship to the Ethernet-like Interface MIB
An interface which includes the Ethernet WIS is, by definition, an An interface which includes the Ethernet WIS is, by definition, an
Ethernet-like interface, and an agent implementing the objects Ethernet-like interface, and an agent implementing the objects
defined in this memo MUST implement the objects required by the defined in this memo MUST implement the objects required by the
dot3Compliance2 compliance statement in the EtherLike-MIB. dot3Compliance2 compliance statement in the EtherLike-MIB.
3.3. Relationship to the 802.3 MAU MIB 3.3. Relationship to the 802.3 MAU MIB
Support for the mauModIfCompl2 compliance statement of the MAU-MIB Support for the mauModIfCompl3 compliance statement of the MAU-MIB
[MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB
is needed in order to allow applications to control and/or determine is needed in order to allow applications to control and/or determine
the media type in use. That is important for devices than can the media type in use. That is important for devices than can
support both the 10GBASE-R 10 Gb/s LAN format (which does not include support both the 10GBASE-R 10 Gb/s LAN format (which does not include
the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the
WIS). The MAU-MIB also provides the means to put a device in standby WIS). The MAU-MIB also provides the means to put a device in standby
mode or to reset it; the latter may be used to re-initialize the mode or to reset it; the latter may be used to re-initialize the
WIS. WIS.
3.4. Use of the ifTable 3.4. Use of the ifTable
skipping to change at page 8, line 18 skipping to change at page 8, line 27
sonetFarEndPathIntervalESs sonetFarEndPathIntervalESs
aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs +
sonetFarEndPathIntervalCVs sonetFarEndPathIntervalCVs
It should be noted that the threshold and counter objects imported It should be noted that the threshold and counter objects imported
from the SONET-MIB are not completely equivalent to the corresponding from the SONET-MIB are not completely equivalent to the corresponding
IEEE 802.3 objects. The specific differences are as follows: IEEE 802.3 objects. The specific differences are as follows:
IEEE 802.3 Managed Object How Corresponding SNMP Object Differs IEEE 802.3 Managed Object How Corresponding SNMP Object Differs
oWIS - pWISOptional package
aSectionSESThreshold This object is defined in [P802.3ae] aSectionSESThreshold This object is defined in [P802.3ae]
as an integer with one instance per as an integer with one instance per
interface. sonetSESthresholdSet interface. sonetSESthresholdSet
is an enumerated value that has one is an enumerated value that has one
instance per network element; it instance per network element; it
controls the thresholds for all layers controls the thresholds for all layers
simultaneously and allows only certain simultaneously and allows only certain
discrete values to be selected. discrete values to be selected.
aSectionSESs This object is defined in [P802.3ae] as aSectionSESs This object is defined in [P802.3ae] as
a generalized nonresetable counter. a generalized nonresetable counter.
skipping to change at page 11, line 50 skipping to change at page 12, line 13
nonresetable counter in [P802.3ae], and nonresetable counter in [P802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndPathCurrentCVs and objects sonetFarEndPathCurrentCVs and
sonetFarEndPathIntervalCVs are 15-minute sonetFarEndPathIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify one-second intervals that qualify
either as severely errored seconds either as severely errored seconds
or as unavailable seconds. or as unavailable seconds.
Please note that despite the differences in semantics between the Note: despite the semantic differences between the threshold objects
threshold objects and counter objects imported from the SONET-MIB and and counter objects imported from the SONET-MIB and the corresponding
the corresponding IEEE 802.3 objects, the hardware support mandated IEEE 802.3 objects, the hardware support mandated by [P802.3ae]
by [P802.3ae] subclause 50.3.10 suffices for both. See Appendix A subclause 50.3.11 suffices for both. See Appendix A for details.
for details.
3.7. Mapping of SNMP Objects to WIS Station Management Registers 3.7. Mapping of SNMP Objects to WIS Station Management Registers
Some of the objects defined in this memo or incorporated by reference Some of the objects defined in this memo or incorporated by reference
from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS-
specific hardware support. [P802.3ae] subclause 50.3.10 specifies specific hardware support. [P802.3ae] subclause 50.3.11 specifies
WIS management interface requirements, including a required subset of WIS management interface requirements, including a required subset of
the WIS MDIO (Management Data Input/Output) registers defined in the WIS MDIO (Management Data Input/Output) registers defined in
[P802.3ae] subclause 45.2.2. The table below provides a cross- [P802.3ae] subclause 45.2.2. The table below provides a cross-
reference between those managed objects and the WIS MDIO registers reference between those managed objects and the WIS MDIO registers
from the subset in [P802.3ae] subclause 50.3.10 required to support from the subset in [P802.3ae] subclause 50.3.11 required to support
them. Note that the MDIO interface is optional; however, if it is them. Note that the MDIO interface is optional; however, if it is
not implemented, then the capabilities of the required register not implemented, then the capabilities of the required register
subset must be provided by other means. subset must be provided by other means.
SNMP Object WIS MDIO Register(s) SNMP Object WIS MDIO Register(s)
ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS Control 2 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2
ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS Control 2 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2
ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS Test Pattern ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern
Error Counter error counter
SONET-MIB - sonetMediumType none required SONET-MIB - sonetMediumType none required
SONET-MIB - sonetMediumTimeElapsed none required SONET-MIB - sonetMediumTimeElapsed none required
SONET-MIB - sonetMediumValidIntervals none required SONET-MIB - sonetMediumValidIntervals none required
SONET-MIB - sonetMediumLineCoding none required SONET-MIB - sonetMediumLineCoding none required
SONET-MIB - sonetMediumLineType none required SONET-MIB - sonetMediumLineType none required
SONET-MIB - sonetMediumCircuitIdentifier none required SONET-MIB - sonetMediumCircuitIdentifier none required
SONET-MIB - sonetMediumInvalidIntervals none required SONET-MIB - sonetMediumInvalidIntervals none required
SONET-MIB - sonetMediumLoopbackConfig none required SONET-MIB - sonetMediumLoopbackConfig none required
SONET-MIB - sonetSESthresholdSet none required SONET-MIB - sonetSESthresholdSet none required
ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 Tx ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 tx
ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 Rx ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 rx
SONET-MIB - sonetSectionCurrentStatus 10G WIS status 3
SONET-MIB - sonetSectionCurrentStatus 10G WIS Status 3
SONET-MIB - sonetSectionCurrentESs \ SONET-MIB - sonetSectionCurrentESs \
SONET-MIB - sonetSectionCurrentSESs \ SONET-MIB - sonetSectionCurrentSESs \
SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS Status 3 SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS status 3
SONET-MIB - sonetSectionCurrentCVs | + SONET-MIB - sonetSectionCurrentCVs | +
SONET-MIB - sonetSectionIntervalESs | 10G WIS Section SONET-MIB - sonetSectionIntervalESs | 10G WIS section
SONET-MIB - sonetSectionIntervalSESs | BIP Error Count SONET-MIB - sonetSectionIntervalSESs | BIP error count
SONET-MIB - sonetSectionIntervalSEFSs / SONET-MIB - sonetSectionIntervalSEFSs /
SONET-MIB - sonetSectionIntervalCVs / SONET-MIB - sonetSectionIntervalCVs /
SONET-MIB - sonetSectionIntervalValidData none required SONET-MIB - sonetSectionIntervalValidData none required
SONET-MIB - sonetLineCurrentStatus 10G WIS Status 3
SONET-MIB - sonetLineCurrentStatus 10G WIS status 3
SONET-MIB - sonetLineCurrentESs \ SONET-MIB - sonetLineCurrentESs \
SONET-MIB - sonetLineCurrentSESs \ SONET-MIB - sonetLineCurrentSESs \
SONET-MIB - sonetLineCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetLineCurrentCVs | 10G WIS status 3
SONET-MIB - sonetLineCurrentUASs | + SONET-MIB - sonetLineCurrentUASs | +
SONET-MIB - sonetLineIntervalESs | 10G WIS Line SONET-MIB - sonetLineIntervalESs | 10G WIS line
SONET-MIB - sonetLineIntervalSESs | BIP Errors SONET-MIB - sonetLineIntervalSESs | BIP errors
SONET-MIB - sonetLineIntervalCVs / SONET-MIB - sonetLineIntervalCVs /
SONET-MIB - sonetLineIntervalUASs / SONET-MIB - sonetLineIntervalUASs /
SONET-MIB - sonetLineIntervalValidData none required SONET-MIB - sonetLineIntervalValidData none required
SONET-MIB - sonetFarEndLineCurrentESs \ SONET-MIB - sonetFarEndLineCurrentESs \
SONET-MIB - sonetFarEndLineCurrentSESs \ SONET-MIB - sonetFarEndLineCurrentSESs \
SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS status 3
SONET-MIB - sonetFarEndLineCurrentUASs | + SONET-MIB - sonetFarEndLineCurrentUASs | +
SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS Far End SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS far end
SONET-MIB - sonetFarEndLineIntervalSESs | Line BIP Errors SONET-MIB - sonetFarEndLineIntervalSESs | line BIP errors
SONET-MIB - sonetFarEndLineIntervalCVs / SONET-MIB - sonetFarEndLineIntervalCVs /
SONET-MIB - sonetFarEndLineIntervalUASs / SONET-MIB - sonetFarEndLineIntervalUASs /
SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS Status 3 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS status 3
ETHER-WIS - etherWisPathCurrentStatus 10G WIS Status 3 ETHER-WIS - etherWisPathCurrentStatus 10G WIS status 3
ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 Tx ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 tx
ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 Rx ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 rx
SONET-MIB - sonetPathCurrentWidth none required SONET-MIB - sonetPathCurrentWidth none required
SONET-MIB - sonetPathCurrentStatus 10G WIS Status 3 SONET-MIB - sonetPathCurrentStatus 10G WIS status 3
SONET-MIB - sonetPathCurrentESs \ SONET-MIB - sonetPathCurrentESs \
SONET-MIB - sonetPathCurrentSESs \ SONET-MIB - sonetPathCurrentSESs \
SONET-MIB - sonetPathCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetPathCurrentCVs | 10G WIS status 3
SONET-MIB - sonetPathCurrentUASs | + SONET-MIB - sonetPathCurrentUASs | +
SONET-MIB - sonetPathIntervalESs | 10G WIS SONET-MIB - sonetPathIntervalESs | 10G WIS
SONET-MIB - sonetPathIntervalSESs | Path Block SONET-MIB - sonetPathIntervalSESs | path block
SONET-MIB - sonetPathIntervalCVs / Error Count SONET-MIB - sonetPathIntervalCVs / error count
SONET-MIB - sonetPathIntervalUASs / SONET-MIB - sonetPathIntervalUASs /
SONET-MIB - sonetPathIntervalValidData none required SONET-MIB - sonetPathIntervalValidData none required
ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS status 3
ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS Status 3
SONET-MIB - sonetFarEndPathCurrentESs \ SONET-MIB - sonetFarEndPathCurrentESs \
SONET-MIB - sonetFarEndPathCurrentSESs \ SONET-MIB - sonetFarEndPathCurrentSESs \
SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS status 3
SONET-MIB - sonetFarEndPathCurrentUASs | + SONET-MIB - sonetFarEndPathCurrentUASs | +
SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS Far End SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS far end
SONET-MIB - sonetFarEndPathIntervalSESs | Path Block SONET-MIB - sonetFarEndPathIntervalSESs | path block
SONET-MIB - sonetFarEndPathIntervalCVs / Error Count SONET-MIB - sonetFarEndPathIntervalCVs / error count
SONET-MIB - sonetFarEndPathIntervalUASs / SONET-MIB - sonetFarEndPathIntervalUASs /
SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS Status 3 SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS status 3
MAU-MIB - ifMauIfIndex none required MAU-MIB - ifMauIfIndex none required
MAU-MIB - ifMauIndex none required MAU-MIB - ifMauIndex none required
MAU-MIB - ifMauType 10G WIS Control 2 MAU-MIB - ifMauType 10G WIS control 2
MAU-MIB - ifMauStatus WIS Control 1 MAU-MIB - ifMauStatus WIS control 1
MAU-MIB - ifMauMediaAvailable \ WIS Status 1 + MAU-MIB - ifMauMediaAvailable \ WIS status 1 +
MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS Status 3 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS status 3
MAU-MIB - ifMauJabberState none required MAU-MIB - ifMauJabberState none required
MAU-MIB - ifMauJabberingStateEnters none required MAU-MIB - ifMauJabberingStateEnters none required
MAU-MIB - ifMauFalseCarriers none required MAU-MIB - ifMauFalseCarriers none required
MAU-MIB - ifMauDefaultType 10G WIS Control 2 MAU-MIB - ifMauDefaultType 10G WIS control 2
MAU-MIB - ifMauAutoNegSupported none required MAU-MIB - ifMauAutoNegSupported none required
MAU-MIB - ifMauTypeListBits 10G WIS Status 2 MAU-MIB - ifMauTypeListBits 10G WIS status 2
3.8. Structure of the MIB Module 3.8. Structure of the MIB Module
Four tables are defined in this MIB module. Four tables are defined in this MIB module.
3.8.1. etherWisDeviceTable 3.8.1. etherWisDeviceTable
The purpose of this table is to define managed objects to control the The purpose of this table is to define managed objects to control the
WIS test pattern mode. These objects are required to support WIS test pattern mode. These objects are required to support
mandatory and optional WIS test features specified in [P802.3ae] mandatory and optional WIS test features specified in [P802.3ae]
subclause 50.3.8. subclause 50.3.8.
The etherWisDeviceTable is a sparse augmentation of the The etherWisDeviceTable is a sparse augmentation of the
sonetMediumTable of the SONET MIB -- in other words, for each entry sonetMediumTable of the SONET-MIB -- in other words, for each entry
in the etherWisDeviceTable there MUST be an entry in the in the etherWisDeviceTable there MUST be an entry in the
sonetMediumTable and the same ifIndex value SHALL be used for both sonetMediumTable and the same ifIndex value SHALL be used for both
entries. entries.
3.8.2. etherWisSectionCurrentTable 3.8.2. etherWisSectionCurrentTable
The purpose of this table is to define managed objects for the The purpose of this table is to define managed objects for the
transmitted and received section trace messages (J0 byte). transmitted and received section trace messages (J0 byte).
The etherWisSectionCurrentTable is a sparse augmentation of the The etherWisSectionCurrentTable is a sparse augmentation of the
sonetSectionCurrentTable of the SONET MIB -- in other words, for each sonetSectionCurrentTable of the SONET-MIB -- in other words, for each
entry in the etherWisSectionCurrentTable there MUST be an entry in entry in the etherWisSectionCurrentTable there MUST be an entry in
the sonetSectionCurrentTable and the same ifIndex value SHALL be used the sonetSectionCurrentTable and the same ifIndex value SHALL be used
for both entries. for both entries.
3.8.3. etherWisPathCurrentTable 3.8.3. etherWisPathCurrentTable
The purpose of this table is to define managed objects for the The purpose of this table is to define managed objects for the
current WIS path layer status and for the transmitted and received current WIS path layer status and for the transmitted and received
path trace messages (J1 byte). The path layer status object is path trace messages (J1 byte). The path layer status object is
provided because the WIS supports some near-end path status provided because the WIS supports some near-end path status
conditions that are not reported in sonetPathCurrentStatus. conditions that are not reported in sonetPathCurrentStatus.
The etherWisPathCurrentTable is a sparse augmentation of the The etherWisPathCurrentTable is a sparse augmentation of the
sonetPathCurrentTable of the SONET MIB -- in other words, for each sonetPathCurrentTable of the SONET-MIB -- in other words, for each
entry in the etherWisPathCurrentTable there MUST be an entry in the entry in the etherWisPathCurrentTable there MUST be an entry in the
sonetPathCurrentTable and the same ifIndex value SHALL be used for sonetPathCurrentTable and the same ifIndex value SHALL be used for
both entries. both entries.
3.8.4. etherWisFarEndPathCurrentTable 3.8.4. etherWisFarEndPathCurrentTable
The purpose of this table is to define a managed object for the The purpose of this table is to define a managed object for the
current status of the far end of the path. This object is provided current status of the far end of the path. This object is provided
because the WIS supports some far-end path status conditions that are because the WIS supports some far-end path status conditions that are
not reported in sonetPathCurrentStatus. not reported in sonetPathCurrentStatus.
The etherWisFarEndPathCurrentTable is a sparse augmentation of the The etherWisFarEndPathCurrentTable is a sparse augmentation of the
sonetFarEndPathCurrentTable of the SONET MIB -- in other words, for sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for
each entry in the etherWisFarEndPathCurrentTable there MUST be an each entry in the etherWisFarEndPathCurrentTable there MUST be an
entry in the sonetFarEndPathCurrentTable and the same ifIndex value entry in the sonetFarEndPathCurrentTable and the same ifIndex value
SHALL be used for both entries. SHALL be used for both entries.
4. Object Definitions 4. Object Definitions
ETHER-WIS DEFINITIONS ::= BEGIN ETHER-WIS DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
skipping to change at page 16, line 27 skipping to change at page 16, line 27
sonetMediumStuff2, sonetSectionStuff2, sonetMediumStuff2, sonetSectionStuff2,
sonetLineStuff2, sonetFarEndLineStuff2, sonetLineStuff2, sonetFarEndLineStuff2,
sonetPathStuff2, sonetFarEndPathStuff2, sonetPathStuff2, sonetFarEndPathStuff2,
sonetMediumType, sonetMediumLineCoding, sonetMediumType, sonetMediumLineCoding,
sonetMediumLineType, sonetMediumCircuitIdentifier, sonetMediumLineType, sonetMediumCircuitIdentifier,
sonetMediumLoopbackConfig, sonetSESthresholdSet, sonetMediumLoopbackConfig, sonetSESthresholdSet,
sonetPathCurrentWidth sonetPathCurrentWidth
FROM SONET-MIB; FROM SONET-MIB;
etherWisMIB MODULE-IDENTITY etherWisMIB MODULE-IDENTITY
LAST-UPDATED "200202180140Z" -- February 18, 2002 LAST-UPDATED "200204141830Z" -- April 14, 2002
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Inc. Postal: Avaya Inc.
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
skipping to change at page 17, line 14 skipping to change at page 17, line 14
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[IEEE 802.3 Std] refers to: [IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2000 Edition: 'IEEE Standard for IEEE Std 802.3, 2000 Edition: 'IEEE Standard for
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer detection (CSMA/CD) access method and physical layer
specifications', as amended by IEEE Draft P802.3ae/D4.01: specifications', as amended by IEEE Draft P802.3ae/D4.2:
'Supplement to Carrier Sense Multiple Access with 'Supplement to Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method & Physical Collision Detection (CSMA/CD) Access Method & Physical
Layer Specifications - Media Access Control (MAC) Layer Specifications - Media Access Control (MAC)
Parameters, Physical Layer, and Management Parameters Parameters, Physical Layer, and Management Parameters
for 10 Gb/s Operation', February 4, 2002. for 10 Gb/s Operation', March 21, 2002.
Of particular interest are Clause 50, 'WAN Interface Of particular interest are Clause 50, 'WAN Interface
Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link
Aggregation Management', and Clause 45, 'Management Aggregation Management', and Clause 45, 'Management
Data Input/Output (MDIO) Interface'." Data Input/Output (MDIO) Interface'."
REVISION "200202180140Z" -- February 18, 2002 REVISION "200204141830Z" -- April 14, 2002
DESCRIPTION "Initial version, published as RFC yyyy." DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice -- RFC Ed.: replace yyyy with actual RFC number & remove this notice
::= { transmission XXX } ::= { transmission XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice
-- The main sections of the module -- The main sections of the module
etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 }
skipping to change at page 19, line 15 skipping to change at page 19, line 16
mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. mode described in [IEEE 802.3 Std.] subclause 50.3.8.3.
Any attempt to set this object to a value other than Any attempt to set this object to a value other than
none(0) when the corresponding instance of ifAdminState none(0) when the corresponding instance of ifAdminState
has the value up(1) MUST be rejected with the error has the value up(1) MUST be rejected with the error
inconsistentValue, and any attempt to set the corresponding inconsistentValue, and any attempt to set the corresponding
instance of ifAdminStatus to the value up(1) when an instance of ifAdminStatus to the value up(1) when an
instance of this object has a value other than none(0) instance of this object has a value other than none(0)
MUST be rejected with the error inconsistentValue." MUST be rejected with the error inconsistentValue."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and
checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and checker, 45.2.2.6, 10G WIS control 2 register (2.7), and
45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)."
::= { etherWisDeviceEntry 1 } ::= { etherWisDeviceEntry 1 }
etherWisDeviceRxTestPatternMode OBJECT-TYPE etherWisDeviceRxTestPatternMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(0),
prbs31(2), prbs31(2),
mixedFrequency(3) mixedFrequency(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 19, line 44 skipping to change at page 19, line 45
frequency test pattern mode described in [IEEE 802.3 Std.] frequency test pattern mode described in [IEEE 802.3 Std.]
subclause 50.3.8.3. Any attempt to set this object to a subclause 50.3.8.3. Any attempt to set this object to a
value other than none(0) when the corresponding instance value other than none(0) when the corresponding instance
of ifAdminState has the value up(1) MUST be rejected with of ifAdminState has the value up(1) MUST be rejected with
the error inconsistentValue, and any attempt to set the the error inconsistentValue, and any attempt to set the
corresponding instance of ifAdminStatus to the value up(1) corresponding instance of ifAdminStatus to the value up(1)
when an instance of this object has a value other than when an instance of this object has a value other than
none(0) MUST be rejected with the error inconsistentValue." none(0) MUST be rejected with the error inconsistentValue."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and
checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and checker, 45.2.2.6, 10G WIS control 2 register (2.7), and
45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)."
::= { etherWisDeviceEntry 2 } ::= { etherWisDeviceEntry 2 }
etherWisDeviceRxTestPatternErrors OBJECT-TYPE etherWisDeviceRxTestPatternErrors OBJECT-TYPE
SYNTAX Gauge32 ( 0..65535 ) SYNTAX Gauge32 ( 0..65535 )
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of errors detected when the "This object counts the number of errors detected when the
WIS receive path is operating in the PRBS31 test pattern WIS receive path is operating in the PRBS31 test pattern
mode. It is reset to zero when the WIS receive path mode. It is reset to zero when the WIS receive path
initially enters that mode, and it increments each time initially enters that mode, and it increments each time
the PRBS pattern checker detects an error as described in the PRBS pattern checker detects an error as described in
[IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is
65535, in which case it remains unchanged. This object is 65535, in which case it remains unchanged. This object is
writeable so that it may be reset upon explicit request writeable so that it may be reset upon explicit request
of a command generator application while the WIS receive of a command generator application while the WIS receive
path continues to operate in PRBS31 test pattern mode." path continues to operate in PRBS31 test pattern mode."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and
checker, 45.2.2.7.2, PRBS31 pattern testing ability checker, 45.2.2.7.2, PRBS31 pattern testing ability
(2.8.1), and 45.2.2.8 10G WIS test pattern error counter (2.8.1), and 45.2.2.8, 10G WIS test pattern error counter
register (2.9)." register (2.9)."
::= { etherWisDeviceEntry 3 } ::= { etherWisDeviceEntry 3 }
-- The Section group -- The Section group
-- These objects provide WIS extensions to -- These objects provide WIS extensions to
-- the SONET-MIB Section Group. -- the SONET-MIB Section Group.
etherWisSectionCurrentTable OBJECT-TYPE etherWisSectionCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 21, line 41 skipping to change at page 21, line 41
etherWisSectionCurrentJ0Received OCTET STRING etherWisSectionCurrentJ0Received OCTET STRING
} }
etherWisSectionCurrentJ0Transmitted OBJECT-TYPE etherWisSectionCurrentJ0Transmitted OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the 16-octet section trace message that is "This is the 16-octet section trace message that is
to be transmitted in the J0 byte. The value SHOULD to be transmitted in the J0 byte. The value SHOULD
be fifteen octets of '00'h followed by '89'h be '89'h followed by fifteen octets of '00'h
(or some cyclic shift thereof) when the section (or some cyclic shift thereof) when the section
trace function is not used, and the implementation trace function is not used, and the implementation
SHOULD use that value (or a cyclic shift thereof) SHOULD use that value (or a cyclic shift thereof)
as a default if no other value has been set." as a default if no other value has been set."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX."
::= { etherWisSectionCurrentEntry 1 } ::= { etherWisSectionCurrentEntry 1 }
etherWisSectionCurrentJ0Received OBJECT-TYPE etherWisSectionCurrentJ0Received OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 23, line 11 skipping to change at page 23, line 11
etherWisPathCurrentJ1Transmitted OCTET STRING, etherWisPathCurrentJ1Transmitted OCTET STRING,
etherWisPathCurrentJ1Received OCTET STRING etherWisPathCurrentJ1Received OCTET STRING
} }
etherWisPathCurrentStatus OBJECT-TYPE etherWisPathCurrentStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
etherWisPathLOP(0), etherWisPathLOP(0),
etherWisPathAIS(1), etherWisPathAIS(1),
etherWisPathPLM(2), etherWisPathPLM(2),
etherWisPathLCD(3) etherWisPathLCD(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the current status of the "This variable indicates the current status of the
path payload with a bit map that can indicate multiple path payload with a bit map that can indicate multiple
defects at once. The bit positions are assigned as defects at once. The bit positions are assigned as
follows: follows:
etherWisPathLOP(0) etherWisPathLOP(0)
This bit is set to indicate that an This bit is set to indicate that an
LOP-P (Loss of Pointer - Path) defect LOP-P (Loss of Pointer - Path) defect
skipping to change at page 24, line 4 skipping to change at page 24, line 15
etherWisPathLCD(3) etherWisPathLCD(3)
This bit is set to indicate that an This bit is set to indicate that an
LCD-P (Loss of Codegroup Delination - Path) LCD-P (Loss of Codegroup Delination - Path)
defect is being experienced. Since this defect is being experienced. Since this
defect is detected by the PCS and not by defect is detected by the PCS and not by
the path layer itself, there is no the path layer itself, there is no
corresponding bit in sonetPathCurrentStatus." corresponding bit in sonetPathCurrentStatus."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus."
::= { etherWisPathCurrentEntry 1 } ::= { etherWisPathCurrentEntry 1 }
etherWisPathCurrentJ1Transmitted OBJECT-TYPE etherWisPathCurrentJ1Transmitted OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the 16-octet path trace message that is to "This is the 16-octet path trace message that is to
be transmitted in the J1 byte. The value SHOULD be transmitted in the J1 byte. The value SHOULD
be fifteen octets of '00'h followed by '89'h be '89'h followed by fifteen octets of '00'h
(or some cyclic shift thereof) when the path (or some cyclic shift thereof) when the path
trace function is not used, and the implementation trace function is not used, and the implementation
SHOULD use that value (or a cyclic shift thereof) SHOULD use that value (or a cyclic shift thereof)
as a default if no other value has been set." as a default if no other value has been set."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX."
::= { etherWisPathCurrentEntry 2 } ::= { etherWisPathCurrentEntry 2 }
etherWisPathCurrentJ1Received OBJECT-TYPE etherWisPathCurrentJ1Received OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
skipping to change at page 25, line 25 skipping to change at page 25, line 39
EtherWisFarEndPathCurrentEntry ::= EtherWisFarEndPathCurrentEntry ::=
SEQUENCE { SEQUENCE {
etherWisFarEndPathCurrentStatus BITS etherWisFarEndPathCurrentStatus BITS
} }
etherWisFarEndPathCurrentStatus OBJECT-TYPE etherWisFarEndPathCurrentStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
etherWisFarEndPayloadDefect(0), etherWisFarEndPayloadDefect(0),
etherWisFarEndServerDefect(1) etherWisFarEndServerDefect(1)
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the current status at the "This variable indicates the current status at the
far end of the path using a bit map that can indicate far end of the path using a bit map that can indicate
multiple defects at once. The bit positions are multiple defects at once. The bit positions are
assigned as follows: assigned as follows:
etherWisFarEndPayloadDefect(0) etherWisFarEndPayloadDefect(0)
A far end payload defect (i.e., far end A far end payload defect (i.e., far end
PLM-P or LCD-P) is currently being signalled PLM-P or LCD-P) is currently being signalled
skipping to change at page 30, line 13 skipping to change at page 30, line 13
END END
5. Acknowledgments 5. Acknowledgments
This document is a product of the IETF Hubmib and AToMMIB Working This document is a product of the IETF Hubmib and AToMMIB Working
Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit
Ethernet Task Force. Ethernet Task Force.
6. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that There are five management objects defined in this MIB that have a
have a MAX-ACCESS clause of read-write and/or read-create. Such MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode,
objects may be considered sensitive or vulnerable in some network etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors,
environments. The support for SET operations in a non-secure etherWisSectionCurrentJ0Transmitted, and
etherWisPathCurrentJ1Transmitted. Setting these objects can have the
following potentially disruptive effects on network operation:
o changing the transmit or receive test pattern mode or modifying
the accumulated error count from a PRBS31 pattern test on an
administratively disabled 10GBASE-W interface, which can
interfere with an in-progress pattern test;
o modifying the transmitted section trace and/or path trace
message on an operational 10GBASE-W interface, which can cause
connectivity alarms to be raised at the remote of the link.
Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no 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 control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change) the objects in this MIB.
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. Specifically, the use
of the User-based Security Model RFC 2574 [RFC2574] and the View- of the User-based Security Model RFC 2574 [RFC2574] and the View-
based Access Control Model RFC 2575 [RFC2575] is recommended. based Access Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
7. References 7. References
7.1. Normative References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April for Describing SNMP Management Frameworks", RFC 2571, April
1999. 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
skipping to change at page 32, line 16 skipping to change at page 31, line 49
"Protocol Operations for Version 2 of the Simple Network "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999. RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, June 2000. Extension to the Interfaces Group MIB", RFC 2864, June 2000.
[SONETng] Tesink, K., "Definitions of Managed Objects for the [SONETng] Tesink, K., "Definitions of Managed Objects for the
SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis- SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-
00.txt>, work in progress. 00.txt>, work in progress.
[T1.231] American National Standard for Telecommunications - Digital [T1.231] American National Standard for Telecommunications - Digital
Hierarchy - Layer 1 In-Service Digital Transmission Hierarchy - Layer 1 In-Service Digital Transmission
Performance Monitoring, ANSI T1.231-1997, September 1997. Performance Monitoring, ANSI T1.231-1997, September 1997.
[ETHERIF] Flick, J., "Definitions of Managed Objects for the [ETHERIF] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", <draft-ietf-hubmib-etherif- Ethernet-like Interface Types", <draft-ietf-hubmib-etherif-
mib-v3-00.txt>, work in progress. mib-v3-01.txt>, work in progress.
[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau- Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau-
mib-v3-00.txt>, work in progress. mib-v3-01.txt>, work in progress.
[P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE [P802.3ae] Institute of Electrical and Electronic Engineers, IEEE Draft
Draft P802.3ae/D4.01, February 4, 2002, work in progress. P802.3ae/D4.2, "Supplement to Carrier Sense Multiple Access
with Collision Detection (CSMA/CD) Access Method & Physical
Layer Specifications - Media Access Control (MAC)
Parameters, Physical Layer, and Management Parameters for 10
Gb/s Operation", March 21, 2002, work in progress.
7.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
8. Authors' Addresses 8. Authors' Addresses
Mike Ayers Mike Ayers
BMC Software, Inc. BMC Software, Inc.
2141 North First Street 2141 North First Street
San Jose, CA 95131 San Jose, CA 95131
USA USA
Phone: +1 408 546 0947 Phone: +1 408 546 0947
Fax: +1 408 965 0359 Fax: +1 408 965 0359
Email: mayers@bmc.com Email: mayers@bmc.com
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
USA
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Fax: +1 916 785 1199 Fax: +1 916 785 1199
Email: johnf@rose.hp.com Email: johnf@rose.hp.com
C. M. Heard C. M. Heard
600 Rainbow Dr. #141 600 Rainbow Dr. #141
Mountain View, CA 94041-2542 Mountain View, CA 94041-2542
USA USA
Phone: +1 650 964 8391 Phone: +1 650 964 8391
EMail: heard@pobox.com EMail: heard@pobox.com
Kam Lam Kam Lam
Lucent Technologies Lucent Technologies
101 Crawfords Corner Road, Room 4C-616A 101 Crawfords Corner Road, Room 4C-616A
Holmdel, NJ 07733 Holmdel, NJ 07733
USA
Phone: +1 732 949 8338 Phone: +1 732 949 8338
EMail: hklam@lucent.com EMail: hklam@lucent.com
Kerry McDonald Kerry McDonald
Institute for Applied Supercomputing Institute for Applied Supercomputing
California State University San Bernardino California State University San Bernardino
Email: kerry_mcd@hotmail.com Email: kerry_mcd@hotmail.com
kmcdonal@csci.csusb.edu kmcdonal@csci.csusb.edu
K. C. Norseth K. C. Norseth
Enterasys Networks 934 S. Palos Verdes Dr.
2691 South Decker Lake Lane Kaysville, Utah 84037
Salt Lake City, Utah 84119 USA
Phone: +1 801 887 9823 Phone: +1 801 546 3316
Email: knorseth@enterasys.com Email: kcn@norseth.com
Kaj Tesink Kaj Tesink
Telcordia Technologies Telcordia Technologies
331 Newman Springs Road 331 Newman Springs Road
P.O. Box 7020 P.O. Box 7020
Red Bank, NJ 07701-7020 Red Bank, NJ 07701-7020
USA USA
Phone: +1 732 758 5254 Phone: +1 732 758 5254
EMail: kaj@research.telcordia.com EMail: kaj@research.telcordia.com
skipping to change at page 35, line 9 skipping to change at page 35, line 9
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Appendix A: Collection of Performance Data Using WIS MDIO Registers Appendix A: Collection of Performance Data Using WIS MDIO Registers
The purpose of this appendix is to illustrate how the WIS MDIO The purpose of this appendix is to illustrate how the WIS MDIO
registers specified in [P802.3ae] subclause 45.2.2 (and more registers specified in [P802.3ae] subclause 45.2.2 (and more
specifically the subset required by [P802.3ae] subclause 50.3.10) can specifically the subset required by [P802.3ae] subclause 50.3.11) can
be used to collect performance data either according to the be used to collect performance data either according to the
conventions adopted by this document or according to the conventions conventions adopted by this document or according to the conventions
specified in [P802.3ae] Clause 30. specified in [P802.3ae] Clause 30.
For an agent implementing the SNMP managed objects required by this For an agent implementing the SNMP managed objects required by this
document the first step in collecting WIS performance data would be document the first step in collecting WIS performance data would be
to poll the 10G WIS Status 3 register and the various error count to poll the 10G WIS status 3 register and the various error count
registers (10G WIS Section BIP Error Count, 10G WIS Line BIP Errors, registers (10G WIS section BIP error count, 10G WIS line BIP errors,
10G WIS Far End Line BIP Errors, 10G WIS Path Block Error Count, and 10G WIS far end line BIP errors, 10G WIS path block error count, and
10G WIS Far End Path Block Error Count) once per second. The 10G WIS 10G WIS far end path block error count) once per second. The 10G WIS
Status 3 register bits are all latched until read and so would status 3 register bits are all latched until read and so would
indicate whether a given defect occurred any time during the previous indicate whether a given defect occurred any time during the previous
second. The error count registers roll over modulo 2^16 or 2^32, and second. The error count registers roll over modulo 2^16 or 2^32, and
so to find the number of errors within the previous second the agent so to find the number of errors within the previous second the agent
would need to subtract (modulo 2^16 or 2^32) the current reading from would need to subtract (modulo 2^16 or 2^32) the current reading from
the reading taken one second ago. Armed with that information, the the reading taken one second ago. Armed with that information, the
agent could determine for any layer whether the one second interval agent could determine for any layer whether the one second interval
was an errored second, a severely errored second (that requires was an errored second, a severely errored second (that requires
comparison with a threshold unless a defect is present), or a comparison with a threshold unless a defect is present), or a
severely errored frame second. Determining whether a given second is severely errored frame second. Determining whether a given second is
or is not part of unavailable time requires additional logic; the or is not part of unavailable time requires additional logic; the
skipping to change at page 35, line 46 skipping to change at page 35, line 46
interval on time-of-day clock 1/4 hour boundaries; if the delay-line interval on time-of-day clock 1/4 hour boundaries; if the delay-line
approach is used then a time-of-day timestamp would accompany the approach is used then a time-of-day timestamp would accompany the
one-second statistics. At the end of each interval the current one-second statistics. At the end of each interval the current
registers would be pushed onto the history stack and then would be registers would be pushed onto the history stack and then would be
cleared. The xyxIntervalValidData flags would be set to False(2) if cleared. The xyxIntervalValidData flags would be set to False(2) if
the number of samples was not between 890 and 910 or, in the case of the number of samples was not between 890 and 910 or, in the case of
far-end counts, if a near-end defect occurred during the just- far-end counts, if a near-end defect occurred during the just-
completed interval (see [T1.231] Section 9.1.2.2 for details). completed interval (see [T1.231] Section 9.1.2.2 for details).
An agent implementing the [P802.3ae] Clause 30 oWIS objects could An agent implementing the [P802.3ae] Clause 30 oWIS objects could
start in much the same way, i.e., by polling the 10G WIS Status 3 also start by polling the 10G WIS status 3 register and the various
register and the various error count registers to find the defects error count registers to find the defects and error counts for the
and error counts for the previous second, and it could determine the previous second, and it could determine the number of errors and
number of errors and whether the second was an errored second, a whether the second was an errored second, a severely errored second,
severely errored second, or a severely errored frame second in the or a severely errored frame second in the same manner as above. The
same manner as above. The rest of the process would be simply to rest of the process would simply be to increment the generalized
increment the generalized non-resetable counters without non-resetable counters without consideration of any inhibiting rules.
consideration of any inhibiting rules.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
skipping to change at page 38, line 33 skipping to change at page 38, line 34
14.) OBJECT clauses were added to specify required values for 14.) OBJECT clauses were added to specify required values for
etherWisDeviceTxTestPatternMode and etherWisDeviceTxTestPatternMode and
etherWisDeviceRxTestPatternMode. etherWisDeviceRxTestPatternMode.
15.) A GROUP clause was added to state that 15.) A GROUP clause was added to state that
etherWisDeviceGroupExtra needs to be implemented in order to etherWisDeviceGroupExtra needs to be implemented in order to
support the PRBS31 test pattern mode. The DESCRIPTION clause support the PRBS31 test pattern mode. The DESCRIPTION clause
points out that the prbs31 enumeration is needed for points out that the prbs31 enumeration is needed for
etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode. etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode.
16). References [SONETng] and [P802.3ae] references were updated 16.) References [SONETng] and [P802.3ae] were updated to draft-
to draft-ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, respectively.
respectively.
The following changes were made to <draft-ietf-hubmib-wis-mib-02.txt>
to produce <draft-ietf-hubmib-wis-mib-03.txt>:
1.) The page formatting was changed to match that used in recent
RFCs.
2.) Heading numbering and bracketed references were removed from
the abstract, and "SONET MIB" was expanded to "SONET/SDH Interface
MIB".
3.) RFC 2119 terminology conventions were moved from the abstract
into a separate numbered "Conventions" section and were
wordsmithed to match the style of recent RFCs.
4.) Each occurrence of "SONET MIB" in Section 3, "Overview", was
expanded to "SONET/SDH Interface MIB".
5.) Each occurrence of "MAU-MIB" in Section 3, "Overview", was
expanded to "802.3 MAU MIB".
6.) Each occurrence of "SONET MIB" in Sections 3.1, 3.8.1, 3.8.2,
3.8.3, and 3.8.4 was changed to "SONET-MIB" (this matches the
usage elsewhere, specifically Sections 3.2 and 3.3).
7.) All occurrences of "[P802.3ae] subclause 50.3.10" were updated
to "[P802.3ae] subclause 50.3.11" in order to match the subclause
numbering in P802.3ae/D4.2 (affected sections are 3.1, 3.6, 3.7,
and Appendix A).
8.) "Ethernet-like Interfaces MIB" was changed to "Ethernet-like
Interface MIB" in Section 3.2 in order to match the usage in the
abstract.
9.) "mauModIfCompl2" was updated to "mauModIfCompl3" in Section
3.3 in order to match <draft-ietf-hubmib-mau-mib-v3-01.txt>.
10.) An unnecessary heading was removed the table in Section 3.6
that compares the semantics of IEEE threshold and counter objects
with those of the corresponding objects imported from the SONET-
MIB.
11.) The text at the end of Section 3.6 was wordsmithed to remove
unnecessary verbiage.
12.) The MDIO register name spellings in Section 3.7, Section 4,
and Appendix A were updated to match those in P802.3ae/D4.2
subclause 45.2.2.
13.) A missing comma was added to the
etherWisDeviceRxTestPatternErrors REFERENCE clause.
14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted
and etherWisPathCurrentJ1Transmitted were updates to state that
the default value should be '89'h followed by 16 octets of '00'h,
rather than 16 octets of '00'h followed by '89'h (this matches the
resolution in P802.3ae/D4.2 of a byte ordering inconsistency).
15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and
etherWisPathCurrentStatus were changed from 'read-write' to
16.) In Section 6, "Security Considerations", all read-write
objects have been explicitly listed and mention of read-create
objects has been removed.
17.) References [ETHERIF], [MAU-MIB], and [P802.3ae] were updated
to <draft-ietf-hubmib-etherif-mib-v3-01.txt>, <draft-ietf-hubmib-
mau-mib-v3-01.txt>, and P802.3ae/D4.2, respectively.
18.) Normative and informative references were moved into separate
sub-sections.
19.) A "To-Do List" section was added.
To-Do List
NOTE TO RFC Editor: prior to publishing this document please take
care of any open items listed below and then remove this section.
1.) All occurrences of "IEEE Draft P802.3ae/D4.2" must be changed
to "IEEE Std 802.3ae" once the standard has been approved, the
approval date must replace the draft publication date, and all
occurrences of the reference tag [P802.3ae] must be changed to
[802.3ae]. Note that this draft is referenced both in Section 4,
"Object Definitions", and in Section 7.1, "Normative References".
2.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must
be updated to point to the appropriate RFCs when the respective
Internet Drafts are published, and all occurrences of the
reference tags must be changed to [RFCnnnn] where nnnn is the
assigned RFC number.
Table of Contents Table of Contents
1 Abstract .................................................. 2 1 Conventions ............................................... 2
2 The SNMP Management Framework ............................. 2 2 The SNMP Management Framework ............................. 2
3 Overview .................................................. 3 3 Overview .................................................. 3
3.1 Relationship to the SONET MIB ........................... 4 3.1 Relationship to the SONET/SDH Interface MIB ............. 4
3.2 Relationship to the Ethernet-like Interfaces MIB ........ 4 3.2 Relationship to the Ethernet-like Interface MIB ......... 4
3.3 Relationship to the 802.3 MAU MIB ....................... 4 3.3 Relationship to the 802.3 MAU MIB ....................... 4
3.4 Use of the ifTable ...................................... 4 3.4 Use of the ifTable ...................................... 5
3.4.1 Layering Model ........................................ 5 3.4.1 Layering Model ........................................ 5
3.4.2 Use of ifTable for LLC Layer/MAC 3.4.2 Use of ifTable for LLC Layer/MAC
Layer/Reconciliation Sublayer/Physical Coding Layer/Reconciliation Sublayer/Physical Coding
Sublayer ............................................... 5 Sublayer ............................................... 5
3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5
3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line
Layer .................................................. 5 Layer .................................................. 6
3.5 SONET/SDH Terminology ................................... 6 3.5 SONET/SDH Terminology ................................... 6
3.6 Mapping of IEEE 802.3 Managed Objects ................... 7 3.6 Mapping of IEEE 802.3 Managed Objects ................... 7
3.7 Mapping of SNMP Objects to WIS Station Management 3.7 Mapping of SNMP Objects to WIS Station Management
Registers .............................................. 12 Registers .............................................. 12
3.8 Structure of the MIB Module ............................. 14 3.8 Structure of the MIB Module ............................. 14
3.8.1 etherWisDeviceTable ................................... 14 3.8.1 etherWisDeviceTable ................................... 14
3.8.2 etherWisSectionCurrentTable ........................... 14 3.8.2 etherWisSectionCurrentTable ........................... 14
3.8.3 etherWisPathCurrentTable .............................. 14 3.8.3 etherWisPathCurrentTable .............................. 15
3.8.4 etherWisFarEndPathCurrentTable ........................ 15 3.8.4 etherWisFarEndPathCurrentTable ........................ 15
4 Object Definitions ........................................ 16 4 Object Definitions ........................................ 16
5 Acknowledgments ........................................... 30 5 Acknowledgments ........................................... 30
6 Security Considerations ................................... 30 6 Security Considerations ................................... 30
7 References ................................................ 31 7 References ................................................ 31
7.1 Normative References .................................... 31
7.2 Informative References .................................. 32
8 Authors' Addresses ........................................ 33 8 Authors' Addresses ........................................ 33
9 Intellectual Property ..................................... 34 9 Intellectual Property ..................................... 34
Appendix A: Collection of Performance Data Using WIS Appendix A: Collection of Performance Data Using WIS
MDIO Registers ......................................... 35 MDIO Registers ......................................... 35
Full Copyright Statement ................................... 36 Full Copyright Statement ................................... 36
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/