draft-ietf-hubmib-rfc3636bis-01.txt   draft-ietf-hubmib-rfc3636bis-02.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: October 15, 2005 Apr 16, 2005 Expires: April 27, 2006 October 24, 2005
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs) (MAUs)
draft-ietf-hubmib-rfc3636bis-01.txt draft-ietf-hubmib-rfc3636bis-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
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 other groups may also distribute working documents as Internet-
Internet-Drafts. 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
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 15, 2005. This Internet-Draft will expire on April 27, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). This memo obsoletes RFC 3636. This memo Attachment Units (MAUs). This memo obsoletes RFC 3636. It amends
extends that specification by moving MAU type object identities and that specification by moving MAU type OBJECT-IDENTITY definitions and
some other relevant textual conventions into a separate Internet relevant textual conventions into a separate Internet Assigned Number
Assigned Number Authority (IANA) maintained MIB module, first version Authority (IANA) maintained MIB module. In addition, management
of which is defined in this document. Thus, when the new MAU types information is added to enable support for Ethernet in the First Mile
are defined by IEEE, only the IANA MIB module needs to be modified, (EFM) and 10GBASE-CX4 MAUs.
leaving the MAU MIB module unchanged. In addition, management
information is added for the management of Ethernet in the First Mile
(EFM) and 10GBASE-CX4 MAUs. This memo also obsoletes RFC 2668 and
RFC 1515.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 Relationship to RFC 3636 . . . . . . . . . . . . . . . . . 4 3.1. Relationship to RFC 3636 . . . . . . . . . . . . . . . . . 4
3.2 Relationship to RFC 2668 . . . . . . . . . . . . . . . . . 4 3.2. Relationship to RFC 2668 . . . . . . . . . . . . . . . . . 5
3.3 Relationship to RFC 2239 . . . . . . . . . . . . . . . . . 5 3.3. Relationship to RFC 2239 . . . . . . . . . . . . . . . . . 5
3.4 Relationship to RFC 1515 . . . . . . . . . . . . . . . . . 5 3.4. Relationship to RFC 1515 . . . . . . . . . . . . . . . . . 5
3.5 Relationship to other MIBs . . . . . . . . . . . . . . . . 5 3.5. Relationship to other MIBs . . . . . . . . . . . . . . . . 5
3.5.1 Relationship to the Interfaces MIB . . . . . . . . . . 5 3.5.1. Relationship to the Interfaces MIB . . . . . . . . . . 6
3.5.2 Relationship to the 802.3 Repeater MIB module . . . . 6 3.5.2. Relationship to the 802.3 Repeater MIB module . . . . 6
3.6 Management of Internal MAUs . . . . . . . . . . . . . . . 6 3.6. Management of Internal MAUs . . . . . . . . . . . . . . . 7
3.7 Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 3.7. Management of IEEE 802.3 Managed Objects . . . . . . . . . 7
3.8 Addition of new MAU Types . . . . . . . . . . . . . . . . 8 3.8. Addition of new MAU Types . . . . . . . . . . . . . . . . 8
3.8.1 dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 3.8.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8
3.8.2 IANAifMauTypeListBits Textual Convention . . . . . . . 8 3.8.2. IANAifMauTypeListBits Textual Convention . . . . . . . 9
3.8.3 JackType Textual Convention . . . . . . . . . . . . . 9 3.8.3. JackType Textual Convention . . . . . . . . . . . . . 9
4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9 4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9
5. IANA maintained MAU TC Definitions . . . . . . . . . . . . . . 51 5. IANA-maintained MAU TC Definitions . . . . . . . . . . . . . . 51
6. Security Considerations . . . . . . . . . . . . . . . . . . . 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 62
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 62 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 63 9.1. Normative References . . . . . . . . . . . . . . . . . . . 64
9.2 Informative References . . . . . . . . . . . . . . . . . . . 65 9.2. Informative References . . . . . . . . . . . . . . . . . . 66
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 67
Intellectual Property and Copyright Statements . . . . . . . . 67 Intellectual Property and Copyright Statements . . . . . . . . . . 68
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 defines objects for managing IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). Attachment Units (MAUs).
The previous version of this memo, RFC 3636 [RFC3636], defined a The previous version of this memo, RFC 3636 [RFC3636], defined a
single MIB module. This memo splits the original MIB module into single MIB module. This memo splits the original MIB module into
two, putting frequently updated object identities and textual two, putting frequently updated object identities and textual
conventions into a separate, IANA maintained MIB module, in order to conventions into a separate, IANA-maintained MIB module, in order to
decrease re-issues of the basic MIB module. decrease re-issues of the basic MIB module.
The first version of the IANA maintaned MIB module also extends the The first version of the IANA-maintained MIB module also extends the
list of managed objects to support Ethernet in the First Mile (EFM) list of managed objects to support Ethernet in the First Mile (EFM)
and 10GBASE-CX4 interfaces. and 10GBASE-CX4 interfaces.
Ethernet technology, as defined by the 802.3 Working Group of the Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new IEEE, continues to evolve, with scalable increases in speed, new
types of cabling and interfaces, and new features. This evolution types of cabling and interfaces, and new features. This evolution
may require changes in the managed objects in order to reflect this may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised, Ethernet technology. In the future, this document might be revised,
skipping to change at page 4, line 19 skipping to change at page 4, line 19
standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3
repeaters or to 802.3 (Ethernet-like) interfaces. For convenience repeaters or to 802.3 (Ethernet-like) interfaces. For convenience
this document refers to these devices as "repeater MAUs" and this document refers to these devices as "repeater MAUs" and
"interface MAUs." "interface MAUs."
The definitions presented here are based on Section 30.5, "Layer The definitions presented here are based on Section 30.5, "Layer
Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium
Attachment Units (MAUs)", Section 30.6, "Management for link Auto- Attachment Units (MAUs)", Section 30.6, "Management for link Auto-
Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed
object classes" of IEEE Std. 802.3, 2002 edition [IEEE802.3], as object classes" of IEEE Std. 802.3, 2002 edition [IEEE802.3], as
amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae], IEEE Std. amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae], IEEE Std. 802.3ah-
802.3ah-2004 [IEEE802.3ah] and IEEE Std. 802.3ak-2004 [IEEE802.3ak]. 2004 [IEEE802.3ah] and IEEE Std. 802.3ak-2004 [IEEE802.3ak]. This
This specification is intended to provide for management of all types specification is intended to provide for management of all types of
of Ethernet/802.3 MAUs. Ethernet/802.3 MAUs.
3.1 Relationship to RFC 3636 3.1. Relationship to RFC 3636
The management definitions provided in this memo are intended to be a The management definitions provided in this memo are intended to be a
superset of those defined by RFC 3636 [RFC3636]. superset of those defined by RFC 3636 [RFC3636].
In order to decrease re-issues of this document due to the new MAU In order to decrease re-issues of this document due to the new MAU
type introduction, all relevant object identities and textual type and/or Jack type introduction, all relevant object identities
conventions have been moved to a separate, IANA maintained MIB and textual conventions have been moved to a separate, IANA-
module, first version of which is defined in this memo. Thus when a maintained MIB module IANA-MAU-MIB, the first version of which is
new MAU type is defined by the IEEE 802.3 working group, only the defined in this memo. Thus when a new MAU type and/or Jack type is
IANA maintaned module would be re-issued by IANA, leaving the basic defined by the IEEE 802.3 working group, only the IANA-maintained
MIB module defined in this memo unchanged. module needs to be revised, leaving the basic MAU-MIB module defined
in this memo unchanged.
In addition, the new definitions are added to the IANA maintaned MIB In addition, the new definitions are added to the IANA-maintained MIB
module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4 module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4
interfaces defined in IEEE Std 802.3ah-2004 and IEEE Std 802.3ak-2004 interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE
respectively. Std 802.3ak-2004 [IEEE802.3ak] respectively.
3.2 Relationship to RFC 2668 It should be noted that the changes made in this revision will not be
entirely backward-compatible with MIB modules that currently import
MAU type object identity descriptors from the MAU-MIB; such modules
will need to be revised to import those DESCRIPTORS from the IANA-
MAU-MIB. Similarly, any management applications that process the
object identity definitions (e.g., to present the DESCRIPTION text to
a user) will need to be get those definitions from the IANA-MAU-MIB
instead of the MAU-MIB. While it is true that changes that require
such adjustments are not strictly compliant with the SMIv2 rules
governing MIB module revisions (see [RFC2578] Section 10), in this
case continued high maintenance costs that would result from not
making these changes maked the deviation from the rules justified.
It should be noted that the working group was not able to find any
examples of MIB modules or management applications that would
actually be negatively affected by the changes.
This MIB is intended to be a superset of that defined by RFC 2668 3.2. Relationship to RFC 2668
[RFC2668]. This MIB includes all of the objects contained in that
MIB, with new and updated definitions which provide support for
additional capabilities. Implementors are encouraged to support all
applicable conformance groups in order to make the best use of the
new functionality provided by this MIB. The new and updated
definitions provide management support for 10 Gb/s devices.
3.3 Relationship to RFC 2239 RFC 3636 was a replacement for RFC 2668 [RFC2668]. RFC 3636 included
all of the objects contained in RFC 2668, plus new and updated
definitions to provide management support for 10 Gb/s devices.
3.3. Relationship to RFC 2239
RFC 2668 was a replacement for RFC 2239 [RFC2239]. RFC 2668 defined RFC 2668 was a replacement for RFC 2239 [RFC2239]. RFC 2668 defined
a superset of that defined by RFC 2239, which contained all of the a superset of that defined by RFC 2239, which contained all of the
objects defined in RFC 2239, plus several new ones which provide objects defined in RFC 2239, plus several new ones which provide
additional capabilities. The new objects provided management support additional capabilities. The new objects provided management support
for: for:
o management of 1000 Mb/s devices o management of 1000 Mb/s devices
o management of PAUSE negotiation o management of PAUSE negotiation
o management of remote fault status o management of remote fault status
3.4 Relationship to RFC 1515 3.4. Relationship to RFC 1515
RFC 2239 was a replacement for RFC 1515 [RFC1515]. RFC 2239 defined RFC 2239 was a replacement for RFC 1515 [RFC1515]. RFC 2239 defined
a superset of RFC 1515 which contained all of the objects defined in a superset of RFC 1515 which contained all of the objects defined in
RFC 1515, plus several new ones which provided additional RFC 1515, plus several new ones which provided additional
capabilities. The new objects in RFC 2239 provided management capabilities. The new objects in RFC 2239 provided management
support for: support for:
o management of 100 Mb/s devices o management of 100 Mb/s devices
o auto-negotiation on interface MAUs o auto-negotiation on interface MAUs
o jack management o jack management
3.5 Relationship to other MIBs 3.5. Relationship to other MIBs
It is assumed that an agent implementing this MIB will also implement It is assumed that an agent implementing this MIB will also implement
(at least) the 'system' group defined in the SNMPv2 MIB [RFC3418]. (at least) the 'system' group defined in the SNMPv2 MIB [RFC3418].
The following sections identify other MIBs that such an agent should The following sections identify other MIBs that such an agent should
implement. implement.
3.5.1 Relationship to the Interfaces MIB 3.5.1. Relationship to the Interfaces MIB
The sections of this document that define interface MAU-related The sections of this document that define interface MAU-related
objects specify an extension to the Interfaces MIB [RFC2863]. An objects specify an extension to the Interfaces MIB [RFC2863]. An
agent implementing these interface-MAU related objects MUST also agent implementing these interface-MAU related objects MUST also
implement the relevant groups of the ifCompliance3 MODULE-COMPLIANCE implement the relevant groups of the ifCompliance3 MODULE-COMPLIANCE
statement of the Interface MIB. The value of the object ifMauIfIndex statement of the Interface MIB. The value of the object ifMauIfIndex
is the same as the value of 'ifIndex' used to instantiate the is the same as the value of 'ifIndex' used to instantiate the
interface to which the given MAU is connected. interface to which the given MAU is connected.
It is REQUIRED that an agent implementing the interface-MAU related It is REQUIRED that an agent implementing the interface-MAU related
skipping to change at page 6, line 31 skipping to change at page 6, line 43
WIS-related entries when ifMauDefaultType is changed to a non- WIS-related entries when ifMauDefaultType is changed to a non-
10GBASE-W type. The agent SHALL also change the values of 10GBASE-W type. The agent SHALL also change the values of
'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed
by ifMauIfIndex as specified in [RFC3635] and [RFC3637] when by ifMauIfIndex as specified in [RFC3635] and [RFC3637] when
ifMauDefaultType is manipulated in this way but SHALL NOT otherwise ifMauDefaultType is manipulated in this way but SHALL NOT otherwise
alter that entry. alter that entry.
(Note that repeater ports are not represented as interfaces in the (Note that repeater ports are not represented as interfaces in the
Interface MIB.) Interface MIB.)
3.5.2 Relationship to the 802.3 Repeater MIB module 3.5.2. Relationship to the 802.3 Repeater MIB module
The section of this document that defines repeater MAU-related The section of this document that defines repeater MAU-related
objects specifies an extension to the 802.3 Repeater MIB defined in objects specifies an extension to the 802.3 Repeater MIB defined in
[RFC2108]. An agent implementing these repeater-MAU related objects [RFC2108]. An agent implementing these repeater-MAU related objects
MUST also comply with the snmpRptrModCompl compliance statement of MUST also comply with the snmpRptrModCompl compliance statement of
the 802.3 Repeater MIB module. the 802.3 Repeater MIB module.
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
instantiate a repeater MAU variable SHALL be the same as the values instantiate a repeater MAU variable SHALL be the same as the values
of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the
port to which the given MAU is connected. port to which the given MAU is connected.
3.6 Management of Internal MAUs 3.6. Management of Internal MAUs
In some situations, a MAU can be "internal" -- i.e., its In some situations, a MAU can be "internal" -- i.e., its
functionality is implemented entirely within a device. For example, functionality is implemented entirely within a device. For example,
a managed repeater may contain an internal repeater-MAU and/or an a managed repeater may contain an internal repeater-MAU and/or an
internal interface-MAU through which management communications internal interface-MAU through which management communications
originating on one of the repeater's external ports pass in order to originating on one of the repeater's external ports pass in order to
reach the management agent associated with the repeater. Such reach the management agent associated with the repeater. Such
internal MAUs may or may not be managed. If they are managed, internal MAUs may or may not be managed. If they are managed,
objects describing their attributes should appear in the appropriate objects describing their attributes should appear in the appropriate
MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and
dot3IfMauBasicGroup for internal interface-MAUs. dot3IfMauBasicGroup for internal interface-MAUs.
3.7 Management of IEEE 802.3 Managed Objects 3.7. Management of IEEE 802.3 Managed Objects
+---------------------------------+---------------------------------+ +----------------------------------+--------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +----------------------------------+--------------------------------+
| oMAU | | | oMAU | |
| .aMAUID | rpMauIndex or ifMauIndex or | | .aMAUID | rpMauIndex or ifMauIndex or |
| | broadMauIndex | | | broadMauIndex |
| .aMAUType | rpMauType or ifMauType | | .aMAUType | rpMauType or ifMauType |
| .aMAUTypeList | ifMauTypeListBits | | .aMAUTypeList | ifMauTypeListBits |
| .aMediaAvailable | rpMauMediaAvailable or | | .aMediaAvailable | rpMauMediaAvailable or |
| | ifMauMediaAvailable | | | ifMauMediaAvailable |
| .aLoseMediaCounter | rpMauMediaAvailableStateExits | | .aLoseMediaCounter | rpMauMediaAvailableStateExits |
| | or | | | or |
| | ifMauMediaAvailableStateExits | | | ifMauMediaAvailableStateExits |
skipping to change at page 7, line 44 skipping to change at page 8, line 7
| .acResetMAU | rpMauStatus or ifMauStatus | | .acResetMAU | rpMauStatus or ifMauStatus |
| .acMAUAdminControl | rpMauStatus or ifMauStatus | | .acMAUAdminControl | rpMauStatus or ifMauStatus |
| .nJabber | rpMauJabberTrap or | | .nJabber | rpMauJabberTrap or |
| | ifMauJabberTrap | | | ifMauJabberTrap |
| oAutoNegotiation | | | oAutoNegotiation | |
| .aAutoNegID | ifMauIndex | | .aAutoNegID | ifMauIndex |
| .aAutoNegAdminState | ifMauAutoNegAdminStatus | | .aAutoNegAdminState | ifMauAutoNegAdminStatus |
| .aAutoNegRemoteSignalling | ifMauAutoNegRemoteSignalling | | .aAutoNegRemoteSignalling | ifMauAutoNegRemoteSignalling |
| .aAutoNegAutoConfig | ifMauAutoNegConfig | | .aAutoNegAutoConfig | ifMauAutoNegConfig |
| .aAutoNegLocalTechnologyAbility | ifMauAutoNegCapabilityBits | | .aAutoNegLocalTechnologyAbility | ifMauAutoNegCapabilityBits |
| .aAutoNegAdvertisedTechnologyAb | ifMauAutoNegAdvertisedBits and | | .aAutoNegAdvertisedTechnologyAbi | ifMauAutoNegAdvertisedBits and |
| ility | ifMauAutoNegRemoteFaultAdvertis | | lity | ifMauAutoNegRemoteFaultAdverti |
| | ed | | | sed |
| .aAutoNegReceivedTechnologyAbil | ifMauAutoNegReceivedBits and | | .aAutoNegReceivedTechnologyAbili | ifMauAutoNegReceivedBits and |
| ity | ifMauAutoNegRemoteFaultReceived | | ty | ifMauAutoNegRemoteFaultReceive |
| | d |
| .acAutoNegRestartAutoConfig | ifMauAutoNegRestart | | .acAutoNegRestartAutoConfig | ifMauAutoNegRestart |
| .acAutoNegAdminControl | ifMauAutoNegAdminStatus | | .acAutoNegAdminControl | ifMauAutoNegAdminStatus |
+---------------------------------+---------------------------------+ +----------------------------------+--------------------------------+
Table 1 Table 1
The following IEEE 802.3 managed objects have not been included in The following IEEE 802.3 managed objects have not been included in
this MIB for the following reasons. this MIB for the following reasons.
+---------------------------------+---------------------------------+ +------------------------------------+------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +------------------------------------+------------------------------+
| oMAU | | | oMAU | |
| .aIdleErrorCount | Only useful for 100BaseT2, | | .aIdleErrorCount | Only useful for 100BaseT2, |
| | which is not widely | | | which is not widely |
| | implemented. | | | implemented. |
| oAutoNegotiation | | | oAutoNegotiation | |
| .aAutoNegLocalSelectorAbility | Only needed for support of | | .aAutoNegLocalSelectorAbility | Only needed for support of |
| | isoethernet (802.9a), which is | | | isoethernet (802.9a), which |
| | not supported by this MIB. | | | is not supported by this |
| .aAutoNegAdvertisedSelectorAbil | | | | MIB. |
| ity | | | .aAutoNegAdvertisedSelectorAbility | |
| .aAutoNegReceivedSelectorAbilit | | | .aAutoNegReceivedSelectorAbility | |
| y | | +------------------------------------+------------------------------+
+---------------------------------+---------------------------------+
Table 2 Table 2
3.8 Addition of new MAU Types 3.8. Addition of new MAU Types
3.8.1 dot3MauType OBJECT-IDENTITIES 3.8.1. dot3MauType OBJECT-IDENTITIES
The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions
has been moved from the MAU-MIB into the IANA maintained has been moved from the MAU-MIB into the IANA-maintained IANA-MAU-
IANA-MAU-MIB, first version of which is defined in this memo. MIB, first version of which is defined in this memo.
When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of
IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its
matching IANAifMauTypeListBits textual convention value and, matching IANAifMauTypeListBits textual convention value and,
possibly, with a new IANAifJackType value. possibly, with a new IANAifJackType value.
An Expert Review is REQUIRED for the addition of the new MAU and Jack An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for
types. the addition of the new MAU and/or Jack types.
Any document that proposes such an addition is REQUIRED to note any In some cases new MAU types may require additional managed objects or
special properties of the MAU types that it defines - for example, may have side effects on the behavior of existing managed objects.
side effects on the ifStackTable as noted for 10GBASE-W MAUs. In such cases a standards-track specification (which may be a new
document or a revision of this document) is also REQUIRED. Any such
document is REQUIRED to note any special properties of the MAU types
that it defines - for example, side effects on the ifStackTable as
noted in this document for 10GBASE-W MAUs.
3.8.2 IANAifMauTypeListBits Textual Convention 3.8.2. IANAifMauTypeListBits Textual Convention
The syntax of ifMauTypeListBits is changed to be a textual The syntax of ifMauTypeListBits is changed to be a textual
convention, such that the enumerated integer values are now defined convention, such that the enumerated integer values are now defined
in the textual convention, IANAifMauTypeListBits, which can be in the textual convention, IANAifMauTypeListBits, which can be re-
re-specified (with additional values) in the IANA mainained MIB specified (with additional values) in the IANA-maintained MIB module,
module, without issuing a new version of this document. without issuing a new version of this document.
3.8.3 JackType Textual Convention 3.8.3. JackType Textual Convention
The JackType Textual Convention has been deprecated in favor of The JackType Textual Convention has been deprecated in favor of
IANAifJackType defined in the IANA mainained MIB module, so the new IANAifJackType defined in the IANA-maintained MIB module, so the new
Jack types can be added (when defined by IEEE 802.3) without issuing Jack types can be added (when defined by IEEE 802.3) without issuing
a new version of this document. a new version of this document.
4. MAU MIB Definitions 4. MAU MIB Definitions
MAU-MIB DEFINITIONS ::= BEGIN MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Integer32, Counter64, zeroDotZero, Counter32, Integer32, Counter64,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TruthValue, AutonomousType, TEXTUAL-CONVENTION TruthValue, AutonomousType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InterfaceIndex InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
IANAifMauTypeListBits, IANAifJackType IANAifMauTypeListBits, IANAifJackType
FROM IANA-MAU-MIB -- RFC 3636bis FROM IANA-MAU-MIB -- RFC 3636bis
skipping to change at page 9, line 35 skipping to change at page 10, line 4
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InterfaceIndex InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
IANAifMauTypeListBits, IANAifJackType IANAifMauTypeListBits, IANAifJackType
FROM IANA-MAU-MIB -- RFC 3636bis FROM IANA-MAU-MIB -- RFC 3636bis
-- EdNote: Replace RFC 3636bis above with the URL of the -- EdNote: Replace RFC 3636bis above with the URL of the
-- actual IANA-maintained module & remove this note. -- actual IANA-maintained module & remove this note.
; ;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "200504150000Z" -- April 15, 2005 LAST-UPDATED "200510240000Z" -- Oct 24, 2005
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 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
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 10, line 43 skipping to change at page 11, line 12
Parameters for 10 Gb/s Operation', August, Parameters for 10 Gb/s Operation', August,
2002. 2002.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s and 10 Gb/s Management'. 100Mb/s, 1000Mb/s and 10 Gb/s Management'.
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFC XXXX; version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "200504150000Z" -- April 15, 2005 REVISION "200510240000Z" -- Oct 24, 2005
DESCRIPTION "Updated to reference IANA maintaned textual DESCRIPTION "Updated to reference IANA maintaned textual
conventions for MAU types and jack types, conventions for MAU types and jack types,
instead of using internally defined values. instead of using internally defined values.
This version is published as RFC XXXX." This version is published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number -- EdNote: Replace XXXX with the actual RFC number
-- & remove this note. -- & remove this note.
REVISION "200309190000Z" -- September 19, 2003 REVISION "200309190000Z" -- September 19, 2003
DESCRIPTION "Updated to include support for 10 Gb/s MAUs. DESCRIPTION "Updated to include support for 10 Gb/s MAUs.
skipping to change at page 12, line 26 skipping to change at page 12, line 41
fiberLC(14) fiberLC(14)
} }
dot3RpMauBasicGroup dot3RpMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup dot3IfMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
-- OIDs under the following branch are reserved for
-- the IANA-MAU-MIB to assign as MAU type values:
-- { snmpDot3MauMgt 4 }
dot3IfMauAutoNegGroup dot3IfMauAutoNegGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- the following OID is the MODULE-IDENTITY value
-- for this MIB module: { snmpDot3MauMgt 6 }
-- the following OID is the MODULE-IDENTITY value
-- for the IANA-MAU-MIB: { snmpDot3MauMgt 7 }
-- --
-- The Basic Repeater MAU Table -- The Basic Repeater MAU Table
-- --
rpMauTable OBJECT-TYPE rpMauTable OBJECT-TYPE
SYNTAX SEQUENCE OF RpMauEntry SYNTAX SEQUENCE OF RpMauEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Table of descriptive and status information DESCRIPTION "Table of descriptive and status information
about the MAU(s) attached to the ports of a about the MAU(s) attached to the ports of a
skipping to change at page 14, line 27 skipping to change at page 15, line 4
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. Values for DESCRIPTION "This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined in the standard IEEE 802.3 MAU types are defined in the
IANA maintained IANA-MAU-MIB module, as IANA maintained IANA-MAU-MIB module, as
OBJECT-IDENTITIES of dot3MauType. OBJECT-IDENTITIES of dot3MauType.
If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
zeroDotZero is returned." zeroDotZero is returned."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
DEFVAL { zeroDotZero }
::= { rpMauEntry 4 } ::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE rpMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 22, line 19 skipping to change at page 22, line 44
This object represents the operational type of This object represents the operational type of
the MAU, as determined by either (1) the result the MAU, as determined by either (1) the result
of the auto-negotiation function or (2) if of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not auto-negotiation is not enabled or is not
implemented for this MAU, by the value of the implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to object ifMauDefaultType. In case (2), a set to
the object ifMauDefaultType will force the MAU the object ifMauDefaultType will force the MAU
into the new operating mode." into the new operating mode."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
DEFVAL { zeroDotZero }
::= { ifMauEntry 3 } ::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE ifMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 30, line 28 skipping to change at page 31, line 4
STATUS current STATUS current
DESCRIPTION "A value that uniquely identifies the set of DESCRIPTION "A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be. possible IEEE 802.3 types that the MAU could be.
If auto-negotiation is present on this MAU, this If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapabilityBits. object will map to ifMauAutoNegCapabilityBits.
Note that this MAU may be capable of operating Note that this MAU may be capable of operating
as a MAU type that is beyond the scope of this as a MAU type that is beyond the scope of this
MIB. This is indicated by returning the MIB. This is indicated by returning the
bit value bOther in addition to any bit values bit value bOther in addition to any bit values
for capabilities that are listed above." for standard capabilities that are listed in the
IANAifMauTypeListBits TC."
::= { ifMauEntry 13 } ::= { ifMauEntry 13 }
ifMauHCFalseCarriers OBJECT-TYPE ifMauHCFalseCarriers OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of false carrier events DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links. during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will For all other MAU types, this counter will
skipping to change at page 50, line 49 skipping to change at page 51, line 26
DESCRIPTION "Implementation of this group is recommended DESCRIPTION "Implementation of this group is recommended
for MAUs attached to interfaces." for MAUs attached to interfaces."
OBJECT ifMauStatus OBJECT ifMauStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mauModCompls 5 } ::= { mauModCompls 5 }
END END
5. IANA maintained MAU TC Definitions 5. IANA-maintained MAU TC Definitions
IANA-MAU-MIB DEFINITIONS ::= BEGIN IANA-MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
; ;
ianaMauMIB MODULE-IDENTITY ianaMauMIB MODULE-IDENTITY
LAST-UPDATED "200504160000Z" -- April 16, 2005 LAST-UPDATED "200510240000Z" -- Oct 24, 2005
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1 310 823 9358
E-Mail: iana@iana.org" E-Mail: iana@iana.org"
DESCRIPTION DESCRIPTION
"This MIB module defines dot3MauType OBJECT-IDENTITIES and "This MIB module defines dot3MauType OBJECT-IDENTITIES and
IANAifMauListBits and IANAifJackType Textual Conventions, IANAifMauListBits and IANAifJackType Textual Conventions,
specifying enumerated values of the ifMauTypeListBits and specifying enumerated values of the ifMauTypeListBits and
ifJackType objects respectively, defined in the MAU-MIB. ifJackType objects respectively, defined in the MAU-MIB.
An Expert Review is REQUIRED for the addition of the new It is intended that each new MAU type and/or Jack type defined
MAU types, when they are defined in the [IEEE 802.3 Std.]. by the IEEE 802.3 working group and approved for publication
Any document that proposes such an addition is REQUIRED to in a revision of IEEE Std 802.3 will be added to this MIB
note any special properties of the MAU types that it defines module, provided that it is suitable for being managed by the
- for example, side effects on the ifStackTable such as those base objects in the MAU-MIB. An Expert Review, as defined in
noted in RFC 3636 Section 3.4.1 for 10GBASE-W MAUs. RFC 2434 [RFC2434], is REQUIRED for such additions.
Copyright (C) The Internet Society (2004). The following reference is used throughout this MIB module:
[IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2002 Edition: 'IEEE Standard for
Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area
networks - Specific requirements -
Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer
specifications', as amended by the following specifications:
IEEE Std 802.3ae-2002:
'Amendment: Media Access Control (MAC) Parameters,
Physical Layer, and Management Parameters for 10 Gb/s
Operation', August 2002;
IEEE Std 802.3ak-2004:
'Amendment: Media Access Control (MAC) Parameters,
Physical Layer, and Management Parameters for 10 Gb/s
Operation, Type 10GBASE-CX4', March 2004;
IEEE Std 802.3ah-2004:
'Amendment: Media Access Control Parameters, Physical
Layers and Management Parameters for Subscriber Access
Networks', September 2004;.
This reference should be updated as appropriate when new
MAU types and/or Jack types are added to this MIB module.
Copyright (C) The Internet Society (2005).
The initial version of this MIB module was published in The initial version of this MIB module was published in
RFC XXXX; for full legal notices see the RFC itself. RFC XXXX; for full legal notices see the RFC itself.
Supplementary information may be available at: Supplementary information may be available at:
http://www.ietf.org/copyrights/ianamib.html" http://www.ietf.org/copyrights/ianamib.html"
REVISION "200504160000Z" -- April 16, 2005 REVISION "200510240000Z" -- Oct 24, 2005
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC XXX." RFC XXX."
-- EdNote: Replace XXXX with the actual RFC number & remove this note -- EdNote: Replace XXXX with the actual RFC number & remove this note
::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1 ::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
-- Textual Conventions -- Textual Conventions
IANAifMauTypeListBits ::= TEXTUAL-CONVENTION IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the ifMauTypeListBits "This data type is used as the syntax of the ifMauTypeListBits
object in the (updated) definition of MAU-MIB's ifMauTable. object in the (updated) definition of MAU-MIB's ifMauTable.
The definition of this textual convention with the addition of The most recent version of this textual convention is
newly assigned values is published periodically by the IANA, available in the on-line version of this MIB module
in either the Assigned Numbers RFC, or some derivative of it on the IANA web site.
specific to Internet Network Management number assignments.
(The latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org). (iana@iana.org).
Note that changes in this textual convention SHALL be Note that changes in this textual convention SHALL be
synchronized with relevant changes in the dot3MauType synchronized with relevant changes in the dot3MauType
OBJECT-IDENTITIES." OBJECT-IDENTITIES."
SYNTAX BITS { SYNTAX BITS {
bOther(0), -- other or unknown bOther(0), -- other or unknown
bAUI(1), -- AUI bAUI(1), -- AUI
skipping to change at page 53, line 44 skipping to change at page 54, line 46
} }
IANAifJackType ::= TEXTUAL-CONVENTION IANAifJackType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Common enumeration values for repeater and interface MAU "Common enumeration values for repeater and interface MAU
jack types. This data type is used as the syntax of the jack types. This data type is used as the syntax of the
ifJackType and rpJackType objects in the (updated) definition ifJackType and rpJackType objects in the (updated) definition
of MAU-MIB's ifJackTable and RpJackTable respectively. of MAU-MIB's ifJackTable and RpJackTable respectively.
The definition of this textual convention with the addition of The most recent version of this textual convention is
newly assigned values is published periodically by the IANA, available in the on-line version of this MIB module
in either the Assigned Numbers RFC, or some derivative of it on the IANA web site.
specific to Internet Network Management number assignments.
(The latest arrangements can be obtained by contacting the
IANA.)
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org)." (iana@iana.org)."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
rj45(2), rj45(2),
rj45S(3), -- rj45 shielded rj45S(3), -- rj45 shielded
db9(4), db9(4),
bnc(5), bnc(5),
fAUI(6), -- female aui fAUI(6), -- female aui
skipping to change at page 60, line 16 skipping to change at page 61, line 14
------ new since RFC 3636: ------ new since RFC 3636:
dot3MauType10GigBaseCX4 OBJECT-IDENTITY dot3MauType10GigBaseCX4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable" DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable"
REFERENCE "[IEEE 802.3 Std.], Section 54" REFERENCE "[IEEE 802.3 Std.], Section 54"
::= { dot3MauType 41 } ::= { dot3MauType 41 }
dot3MauType2BaseTL OBJECT-IDENTITY dot3MauType2BaseTL OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Voice grade UTP copper, up to 2700m " DESCRIPTION "Voice grade UTP copper, up to 2700m "
REFERENCE "[IEEE 802.3 Std.], Sections 61 and 63; [EFM-CU-MIB]" REFERENCE "[IEEE 802.3 Std.], Sections 61 and 63"
::= { dot3MauType 42 } ::= { dot3MauType 42 }
dot3MauType10PassTS OBJECT-IDENTITY dot3MauType10PassTS OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Voice grade UTP copper, up to 750m" DESCRIPTION "Voice grade UTP copper, up to 750m"
REFERENCE "[IEEE 802.3 Std.], Sections 61 and 62; [EFM-CU-MIB]" REFERENCE "[IEEE 802.3 Std.], Sections 61 and 62"
::= { dot3MauType 43 } ::= { dot3MauType 43 }
dot3MauType100BaseBX10D OBJECT-IDENTITY dot3MauType100BaseBX10D OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber OLT" DESCRIPTION "One single-mode fiber OLT"
REFERENCE "[IEEE 802.3 Std.], Section 58" REFERENCE "[IEEE 802.3 Std.], Section 58"
::= { dot3MauType 44 } ::= { dot3MauType 44 }
dot3MauType100BaseBX10U OBJECT-IDENTITY dot3MauType100BaseBX10U OBJECT-IDENTITY
STATUS current STATUS current
skipping to change at page 62, line 42 skipping to change at page 63, line 42
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
This document defines first version of the IANA maintaned MIB module. This document defines first version of the IANA-maintained MIB
When a new MAU type and/or Jack type is defined by the IEEE 802.3 module. It is intended that each new MAU type and/or Jack type
working group, it MAY be added to the IANA maintaned module via an defined by the IEEE 802.3 working group and approved for publication
Expert Review. in a revision of IEEE Std 802.3 will be added to the IANA-maintaned
module. An Expert Review, as defined in RFC 2434 [RFC2434], is
REQUIRED.
8. Acknowledgments 8. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people: contributions of the following people:
Mike Heard Mike Heard
John Flick John Flick
Dan Romascanu Dan Romascanu
This document is based on the Proposed Standard MAU MIB, RFC 3636 This document is based on the Proposed Standard MAU MIB, RFC 3636
[RFC3636], edited by John Flick of Hewlett-Packard, and produced by [RFC3636], edited by John Flick of Hewlett-Packard, and produced by
the Ethernet Interfaces and Hub MIB Working Group. It extends that the Ethernet Interfaces and Hub MIB Working Group. It extends that
document by moving the object identities and textual conventions for document by moving the object identities and textual conventions for
MAU types into a IANA maintained MIB module. In addition, support is MAU types into a IANA-maintained MIB module. In addition, support is
provided for the EFM and 10GBASE-CX4 MAUs as defined in provided for the EFM and 10GBASE-CX4 MAUs as defined in [IEEE802.3ah]
[IEEE802.3ah] and [IEEE802.3ak] respectively. and [IEEE802.3ak] respectively.
RFC 3636, in turn, was based on the Proposed Standard MAU MIB, RFC RFC 3636, in turn, was based on the Proposed Standard MAU MIB, RFC
2668 [RFC2668], edited by John Flick of Hewlett-Packard and Andrew 2668 [RFC2668], edited by John Flick of Hewlett-Packard and Andrew
Smith, then of Extreme Networks, and produced by the Ethernet Smith, then of Extreme Networks, and produced by the Ethernet
Interfaces and Hub MIB Working Group. It extends that document by Interfaces and Hub MIB Working Group. It extends that document by
providing support for 10 Gb/s MAUs as defined in [IEEE802.3ae]. providing support for 10 Gb/s MAUs as defined in [IEEE802.3ae].
RFC 2668, in turn, was based on the Proposed Standard MAU MIB, RFC RFC 2668, in turn, was based on the Proposed Standard MAU MIB, RFC
2239 [RFC2239], edited by Kathryn de Graaf, then of 3Com, and Dan 2239 [RFC2239], edited by Kathryn de Graaf, then of 3Com, and Dan
Romascanu, then of Madge Networks, and produced by the Ethernet Romascanu, then of Madge Networks, and produced by the Ethernet
skipping to change at page 63, line 41 skipping to change at page 64, line 47
RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC
1515 [RFC1515], edited by Donna McMaster, then of SynOptics 1515 [RFC1515], edited by Donna McMaster, then of SynOptics
Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam
Roberts, then of Farallon Computing, and produced by the Hub MIB Roberts, then of Farallon Computing, and produced by the Hub MIB
Working Group. It extends that document by providing support for 100 Working Group. It extends that document by providing support for 100
Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in
[IEEE802.3]. [IEEE802.3].
9. References 9. References
9.1 Normative References 9.1. Normative References
[IEEE802.3] [IEEE802.3]
IEEE, "IEEE Standard for Information technology - IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical collision detection (CSMA/CD) access method and physical
layer specifications", IEEE Std 802.3-2002, March 2002. layer specifications", IEEE Std 802.3-2002, March 2002.
[IEEE802.3ae] [IEEE802.3ae]
skipping to change at page 64, line 32 skipping to change at page 65, line 39
[IEEE802.3ak] [IEEE802.3ak]
IEEE, "IEEE Standard for Information technology - IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical collision detection (CSMA/CD) access method and physical
layer specifications - Physical Layer and Management layer specifications - Physical Layer and Management
Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE
Std 802.3ak-2004, March 2004. Std 802.3ak-2004, March 2004.
[RFC2108] de Graaf, K., Romascanu, D., McMaster, D. and K. [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K.
McCloghrie, "Definitions of Managed Objects for IEEE 802.3 McCloghrie, "Definitions of Managed Objects for IEEE 802.3
Repeater Devices using SMIv2", RFC 2108, February 1997. Repeater Devices using SMIv2", RFC 2108, February 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58,
2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[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.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
9.2 Informative References 9.2. Informative References
[RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions [RFC1515] McMaster, D., McCloghrie, K., and S. Roberts, "Definitions
of Managed Objects for IEEE 802.3 Medium Attachment Units of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs)", RFC 1515, September 1993. (MAUs)", RFC 1515, September 1993.
[RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K. [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K.,
and S. Roberts, "Definitions of Managed Objects for IEEE and S. Roberts, "Definitions of Managed Objects for IEEE
802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 802.3 Medium Attachment Units (MAUs) using SMIv2",
2239, November 1997. RFC 2239, November 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2668] Smith, A., Flick, J., de Graaf, K., Romascanu, D., [RFC2668] Smith, A., Flick, J., de Graaf, K., Romascanu, D.,
McMaster, D., McCloghrie, K. and S. Roberts, "Definitions McMaster, D., McCloghrie, K., and S. Roberts, "Definitions
of Managed Objects for IEEE 802.3 Medium Attachment Units of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs)", RFC 2668, August 1999. (MAUs)", RFC 2668, August 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for Internet-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC Simple Network Management Protocol (SNMP)", STD 62,
3418, December 2002. RFC 3418, December 2002.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 3636, September 2003. Medium Attachment Units (MAUs)", RFC 3636, September 2003.
[RFC3637] Heard, C., "Definitions of Managed Objects for the [RFC3637] Heard, C., "Definitions of Managed Objects for the
Ethernet WAN Interface Sublayer", RFC 3637, September Ethernet WAN Interface Sublayer", RFC 3637,
2003. September 2003.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
EMail: edward.beili@actelis.com Email: edward.beili@actelis.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 77 change blocks. 
171 lines changed or deleted 213 lines changed or added

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