draft-ietf-hubmib-mau-mib-v3-04.txt   rfc3636.txt 
Ethernet Interfaces and Hub MIB Working Group J. Flick Network Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company Request for Comments: 3636 Hewlett-Packard Company
June 2003 Obsoletes: 2668, 1515 September 2003
Category: Standards Track
Definitions of Managed Objects for Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) IEEE 802.3 Medium Attachment Units (MAUs)
<draft-ietf-hubmib-mau-mib-v3-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
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). Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo
extends that specification by including management information useful
This memo obsoletes RFC 2668. This memo extends that specification for the management of 10 gigabit per second (Gb/s) MAUs. This memo
by including management information useful for the management of 10 also obsoletes RFC 1515.
gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515.
Distribution of this memo is unlimited. Please forward comments to
hubmib@ietf.org.
Table of Contents Table of Contents
1. Introduction ............................................... 2 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework ................. 3 2. The Internet-Standard Management Framework. . . . . . . . . . 3
3. Overview ................................................... 3 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Relationship to RFC 2668 ................................. 3 3.1. Relationship to RFC 2668. . . . . . . . . . . . . . . . 3
3.2. Relationship to RFC 2239 ................................. 4 3.2. Relationship to RFC 2239. . . . . . . . . . . . . . . . 4
3.3. Relationship to RFC 1515 ................................. 4 3.3. Relationship to RFC 1515. . . . . . . . . . . . . . . . 4
3.4. Relationship to Other MIBs ............................... 4 3.4. Relationship to Other MIBs. . . . . . . . . . . . . . . 4
3.4.1. Relationship to the Interfaces MIB ..................... 4 3.4.1. Relationship to the Interfaces MIB. . . . . . . 4
3.4.2. Relationship to the 802.3 Repeater MIB ................. 5 3.4.2. Relationship to the 802.3 Repeater MIB. . . . . 5
3.5. Management of Internal MAUs .............................. 5 3.5. Management of Internal MAUs . . . . . . . . . . . . . . 5
3.6. Mapping of IEEE 802.3 Managed Objects .................... 6 3.6. Mapping of IEEE 802.3 Managed Objects . . . . . . . . . 6
4. Definitions ................................................ 7 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Intellectual Property ...................................... 55 5. Intellectual Property Statement . . . . . . . . . . . . . . . 55
6. Acknowledgements ........................................... 56 6. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 56
7. Normative References ....................................... 57 7. Normative References. . . . . . . . . . . . . . . . . . . . . 57
8. Informative References ..................................... 58 8. Informative References. . . . . . . . . . . . . . . . . . . . 57
9. Security Considerations .................................... 58 9. Security Considerations . . . . . . . . . . . . . . . . . . . 58
10. Author's Address .......................................... 59 A. Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . 60
A. Change Log ................................................. 60 A.1. Changes since RFC 2668. . . . . . . . . . . . . . . . . 60
A.1. Changes since RFC 2668 ................................... 60 A.2. Changes between RFC 2239 and RFC 2668 . . . . . . . . . 60
A.2. Changes between RFC 2239 and RFC 2668 .................... 60 Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . 61
B. Full Copyright Statement ................................... 61 Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 62
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).
This memo also includes a MIB module. This MIB module extends the This memo also includes a MIB module. This MIB module extends the
list of managed objects specified in the earlier version of this MIB list of managed objects specified in the earlier version of this MIB
skipping to change at page 3, line 31 skipping to change at page 3, line 29
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
Instances of these object types represent attributes of an IEEE 802.3 Instances of these object types represent attributes of an IEEE 802.3
MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
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]. That specification amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae]. That specification
includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s
devices. This specification is intended to serve the same purpose: to devices. This specification is intended to serve the same purpose:
provide for management of all types of Ethernet/802.3 MAUs. to provide for management of all types of Ethernet/802.3 MAUs.
3.1. Relationship to RFC 2668 3.1. Relationship to RFC 2668
This MIB is intended to be a superset of that defined by RFC 2668 This MIB is intended to be a superset of that defined by RFC 2668
[RFC2668]. This MIB includes all of the objects contained in that [RFC2668]. This MIB includes all of the objects contained in that
MIB, with new and updated definitions which provide support for MIB, with new and updated definitions which provide support for
additional capabilities. Implementors are encouraged to support all additional capabilities. Implementors are encouraged to support all
applicable conformance groups in order to make the best use of the applicable conformance groups in order to make the best use of the
new functionality provided by this MIB. The new and updated new functionality provided by this MIB. The new and updated
definitions provide management support for 10 Gb/s devices. definitions provide management support for 10 Gb/s devices.
3.2. Relationship to RFC 2239 3.2. 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.3. Relationship to RFC 1515 3.3. 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.4. Relationship to Other MIBs 3.4. 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.4.1. Relationship to the Interfaces MIB. 3.4.1. Relationship to the Interfaces MIB.
skipping to change at page 5, line 10 skipping to change at page 5, line 4
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
objects in this MIB will also fully comply with the dot3Compliance2 objects in this MIB will also fully comply with the dot3Compliance2
MODULE-COMPLIANCE statement of the Ethernet-like Interfaces MIB, MODULE-COMPLIANCE statement of the Ethernet-like Interfaces MIB,
[ETHERIF]. Furthermore, when the interface-MAU related objects are
[RFC3635]. Furthermore, when the interface-MAU related objects are
used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal to used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal to
dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the
agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB
[ETHERWIS] and must follow the interface layering model specified [RFC3637] and must follow the interface layering model specified
therein. In that case the value of the object ifMauIfIndex is the therein. In that case the value of the object ifMauIfIndex is the
same as the value of 'ifIndex' for the layer at the top of the stack, same as the value of 'ifIndex' for the layer at the top of the stack,
i.e., for the ifTable entry that has 'ifType' equal to i.e., for the ifTable entry that has 'ifType' equal to
ethernetCsmacd(6). If the interface-MAU related objects are used to ethernetCsmacd(6). If the interface-MAU related objects are used to
manage a PHY that allows the MAU type to be changed dynamically, then manage a PHY that allows the MAU type to be changed dynamically, then
the agent SHALL create ifTable, ifStackTable, and ifInvStackTable the agent SHALL create ifTable, ifStackTable, and ifInvStackTable
entries that pertain to the WIS when ifMauDefaultType is changed to a entries that pertain to the WIS when ifMauDefaultType is changed to a
10GBASEW variant (i.e., one of dot3MauType10GigBaseW, 10GBASEW variant (i.e., one of dot3MauType10GigBaseW,
dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or
dot3MauType10GigBaseSW) from any other type, and shall destroy the dot3MauType10GigBaseSW) from any other type, and shall destroy the
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 [ETHERIF] and [ETHERWIS] 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.4.2. Relationship to the 802.3 Repeater MIB 3.4.2. Relationship to the 802.3 Repeater MIB
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
skipping to change at page 7, line 45 skipping to change at page 7, line 38
OBJECT-IDENTITY, mib-2 OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, AutonomousType, TEXTUAL-CONVENTION TruthValue, AutonomousType, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndex InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "200306020000Z" -- June 2, 2003 LAST-UPDATED "200309190000Z" -- September 19, 2003
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@ietf.org "WG E-mail: hubmib@ietf.org
To subscribe: hubmib-request@ietf.org To subscribe: hubmib-request@ietf.org
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
Israel Israel
skipping to change at page 8, line 44 skipping to change at page 8, line 36
amended by IEEE Std 802.3ae-2002: amended by IEEE Std 802.3ae-2002:
'Amendment: Media Access Control (MAC) 'Amendment: Media Access Control (MAC)
Parameters, Physical Layer, and Management Parameters, Physical Layer, and Management
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 (2003). This Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC XXXX; version of this MIB module is part of RFC 3636;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "200306020000Z" -- June 2, 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.
This resulted in the following revisions: This resulted in the following revisions:
- Added OBJECT-IDENTITY definitions for - Added OBJECT-IDENTITY definitions for
10 gigabit MAU types 10 gigabit MAU types
- Added fiberLC jack type to JackType TC - Added fiberLC jack type to JackType TC
- Extended ifMauTypeListBits with bits for - Extended ifMauTypeListBits with bits for
the 10 gigabit MAU types the 10 gigabit MAU types
- Added enumerations to ifMauMediaAvailable, - Added enumerations to ifMauMediaAvailable,
and updated its DESCRIPTION to reflect and updated its DESCRIPTION to reflect
behaviour at 10 Gb/s behaviour at 10 Gb/s
- Added 64-bit version of ifMauFalseCarriers - Added 64-bit version of ifMauFalseCarriers
and added mauIfGrpHCStats object group to and added mauIfGrpHCStats object group to
skipping to change at page 9, line 20 skipping to change at page 9, line 9
- Added enumerations to ifMauMediaAvailable, - Added enumerations to ifMauMediaAvailable,
and updated its DESCRIPTION to reflect and updated its DESCRIPTION to reflect
behaviour at 10 Gb/s behaviour at 10 Gb/s
- Added 64-bit version of ifMauFalseCarriers - Added 64-bit version of ifMauFalseCarriers
and added mauIfGrpHCStats object group to and added mauIfGrpHCStats object group to
contain the new object contain the new object
- Deprecated mauModIfCompl2 and replaced it - Deprecated mauModIfCompl2 and replaced it
with mauModIfCompl3, which includes the new with mauModIfCompl3, which includes the new
object group object group
This version published as RFC XXXX." This version published as RFC 3636."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "199908240400Z" -- August 24, 1999 REVISION "199908240400Z" -- August 24, 1999
DESCRIPTION "This version published as RFC 2668. Updated DESCRIPTION "This version published as RFC 2668. Updated
to include support for 1000 Mb/sec to include support for 1000 Mb/sec
MAUs and flow control negotiation." MAUs and flow control negotiation."
REVISION "199710310000Z" -- October 31, 1997 REVISION "199710310000Z" -- October 31, 1997
DESCRIPTION "Version published as RFC 2239." DESCRIPTION "Version published as RFC 2239."
REVISION "199309300000Z" -- September30, 1993 REVISION "199309300000Z" -- September30, 1993
skipping to change at page 25, line 40 skipping to change at page 25, line 19
connected to the same interface (ifMauIfIndex)." connected to the same interface (ifMauIfIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 } ::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE ifMauType OBJECT-TYPE
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 above. standard IEEE 802.3 MAU types are defined above.
IANA. If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a is returned. Note that unknownMauType is a
syntactically valid object identifier, and any syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER conformant implementation of ASN.1 and the BER
must be able to generate and recognize this must be able to generate and recognize this
value. value.
This object represents the operational type of This object represents the operational type of
skipping to change at page 55, line 5 skipping to change at page 54, line 21
mauModIfCompl3 MODULE-COMPLIANCE mauModIfCompl3 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to interfaces. DESCRIPTION "Compliance for MAUs attached to interfaces.
Note that compliance with this compliance Note that compliance with this compliance
statement requires compliance with the statement requires compliance with the
ifCompliance3 MODULE-COMPLIANCE statement of the ifCompliance3 MODULE-COMPLIANCE statement of the
IF-MIB (RFC 2863) and the dot3Compliance2 IF-MIB (RFC 2863) and the dot3Compliance2
MODULE-COMPLIANCE statement of the MODULE-COMPLIANCE statement of the
EtherLike-MIB [ETHERIF]." EtherLike-MIB (RFC3635)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic } MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrpHighCapacity GROUP mauIfGrpHighCapacity
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s recommended for MAUs which have 100Mb/s
or greater capability." or greater capability."
GROUP mauIfGrpHCStats GROUP mauIfGrpHCStats
DESCRIPTION "Implemention of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which have 1000Mb/s capacity, and for MAUs which have 1000Mb/s capacity, and
is recommended for MAUs which have 100Mb/s is recommended for MAUs which have 100Mb/s
capacity." capacity."
GROUP mauIfGrpJack GROUP mauIfGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs which have one or more
external jacks." external jacks."
GROUP mauIfGrpAutoNeg2 GROUP mauIfGrpAutoNeg2
skipping to change at page 55, line 48 skipping to change at page 55, line 16
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. Intellectual Property 5. 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 or other rights that might be claimed to intellectual property 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; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
skipping to change at page 56, line 29 skipping to change at page 56, line 11
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.
6. Acknowledgements 6. Acknowledgements
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 Ayers Mike Ayers
Mike Heard Mike Heard
Chuck Black Chuck Black
John Flick John Flick
Jeff Johnson Jeff Johnson
Kam Lam Kam Lam
Leon Leong Leon Leong
Mike Lui Mike Lui
Kerry McDonald Kerry McDonald
K.C. Norseth K.C. Norseth
Dave Perkins Dave Perkins
Dan Romascanu Dan Romascanu
Andrew Smith Andrew Smith
Kaj Tesink Kaj Tesink
Geoff Thompson Geoff Thompson
Maurice Turcotte Maurice Turcotte
Paul Woodruff Paul Woodruff
This document is based on the Proposed Standard MAU MIB, RFC 2668 This document is based on the Proposed Standard MAU MIB, RFC 2668
[RFC2668], edited by John Flick of Hewlett-Packard and Andrew Smith, [RFC2668], edited by John Flick of Hewlett-Packard and Andrew Smith,
then of Extreme Networks, and produced by the Ethernet Interfaces and then of Extreme Networks, and produced by the Ethernet Interfaces and
Hub MIB Working Group. It extends that document by providing Hub MIB Working Group. It extends that document by providing support
suppport for 10 Gb/s MAUs as defined in [IEEE802.3ae]. 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
Interfaces and Hub MIB Working Group. It extended that document by Interfaces and Hub MIB Working Group. It extended that document by
providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3]. providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3].
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].
7. Normative References 7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Structure of "Structure of Management Information Version 2
Management Information Version 2 (SMIv2)", STD 58, RFC (SMIv2)", STD 58, RFC 2578, April 1999.
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Textual Conventions "Textual Conventions for SMIv2", STD 58, RFC 2579,
for SMIv2", STD 58, RFC 2579, April 1999. April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
J., Rose, M. and S. Waldbusser, "Conformance Statements "Conformance Statements for SMIv2", STD 58, RFC 2580,
for SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense [IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense
Multiple Access with Collision Detection (CSMA/CD) Multiple Access with Collision Detection (CSMA/CD)
Access Method and Physical Layer Specifications", Access Method and Physical Layer Specifications", March
March 2002. 2002.
[IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media [IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media Access
Access Control (MAC) Parameters, Physical Layers, Control (MAC) Parameters, Physical Layers, and
and Management Parameters for 10 Gb/s Operation", Management Parameters for 10 Gb/s Operation", August,
August, 2002. 2002.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Group MIB using SMIv2", RFC 2863, June 2000. MIB using SMIv2", RFC 2863, June 2000.
[RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. [RFC2108] de Graaf, K., Romascanu, D., McMaster, D. and K.
McCloghrie, "Definitions of Managed Objects for IEEE McCloghrie, "Definitions of Managed Objects for IEEE
802.3 Repeater Devices using SMIv2", RFC 2108, February 802.3 Repeater Devices using SMIv2", RFC 2108, February
1997. 1997.
[ETHERIF] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", work in progress, Ethernet-like Interface Types", RFC 3635, September
draft-ietf-hubmib-etherif-mib-v3-02.txt, March, 2003. 2003.
8. Informative References 8. Informative References
[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-Standard Network Management Framework", Internet-Standard Network Management Framework", RFC
RFC 3410, December 2002. 3410, December 2002.
[RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. [RFC3418] Presuhn, R., Ed., "Management Information Base (MIB)
Waldbusser, "Management Information Base (MIB) for the for the Simple Network Management Protocol (SNMP)", STD
Simple Network Management Protocol (SNMP)", RFC 3418, 62, RFC 3418, December 2002.
December 2002.
[RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D.,
McMaster, D., McCloghrie, K. and S. Roberts, McMaster, D., McCloghrie, K. and S. Roberts,
"Definitions of Managed Objects for IEEE 802.3 Medium "Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 2668, August 1999. Attachment Units (MAUs)", RFC 2668, August 1999.
[RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie,
K. and S. Roberts, "Definitions of Managed Objects for K. and S. Roberts, "Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2",
RFC 2239, November 1997. RFC 2239, November 1997.
[RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts,
"Definitions of Managed Objects for IEEE 802.3 Medium "Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 1515, September 1993. Attachment Units (MAUs)", RFC 1515, September 1993.
[ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, [RFC3637] Heard, C. M., Ed., "Definitions of Managed Objects for
K., Norseth, K. C., and K. Tesink, "Definitions of the Ethernet WAN Interface Sublayer", RFC 3637,
Managed Objects for the Ethernet WAN Interface September 2003.
Sublayer", work in progress,
draft-ietf-hubmib-wis-mib-04.txt, May 2002.
9. Security Considerations 9. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write. Setting these objects can have a MAX-ACCESS clause of read-write. Setting these objects can
have a serious effect on the operation of the network, including: have a serious effect on the operation of the network, including:
enabling or disabling a MAU o enabling or disabling a MAU
changing a MAU's default type
enabling, disabling or restarting autonegotiation o changing a MAU's default type
modifying the capabilities that a MAU advertizes during
autonegotiation. o enabling, disabling or restarting autonegotiation
o modifying the capabilities that a MAU advertizes during
autonegotiation.
Such objects may be considered sensitive or vulnerable in some Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a non-secure 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.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. In some environments it may vulnerable in some network environments. In some environments it may
be undesirable to allow unauthorized parties to access statistics or be undesirable to allow unauthorized parties to access statistics or
skipping to change at page 59, line 44 skipping to change at page 60, line 5
(for authentication and privacy). (for authentication and privacy).
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.
10. Author's Address
John Flick
Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557
Phone: +1 916 785 4018
E-mail: johnf@rose.hp.com
A. Change Log A. Change Log
A.1. Changes since RFC 2668 A.1. Changes since RFC 2668
This section enumerates changes made to RFC 2668 to produce this This section enumerates changes made to RFC 2668 to produce this
document. document.
(1) Updated references to the IEEE 802.3 standard to (1) Updated references to the IEEE 802.3 standard to refer to the
refer to the 2000 edition. 2002 edition.
(2) Added reference to 802.3ae. (2) Added reference to 802.3ae.
(3) Updated WG e-mail address. (3) Updated WG e-mail address.
(4) The following DESCRIPTION clauses have been updated (4) The following DESCRIPTION clauses have been updated to reflect
to reflect behaviour on 10 Gb/s interfaces: behavior on 10 Gb/s interfaces: ifMauMediaAvailable.
ifMauMediaAvailable.
(5) OBJECT-IDENTITY definitions have been added for 10 gigabit (5) OBJECT-IDENTITY definitions have been added for 10 gigabit MAU
MAU types. types.
(6) Enumerations for 'pmdLinkFault', 'wisFrameLoss', (6) Enumerations for 'pmdLinkFault', 'wisFrameLoss',
'wisSignalLoss', pcsLinkFault', excessiveBER', 'wisSignalLoss', pcsLinkFault', excessiveBER', 'dxsLinkFault'
'dxsLinkFault' and 'pxsLinkFault' have been and 'pxsLinkFault' have been added for the ifMauMediaAvailable
added for the ifMauMediaAvailable object. object.
(7) ifMauTypeListBits has been extended with bits for the (7) ifMauTypeListBits has been extended with bits for the 10 Gb/s
10 Gb/s MAU types. MAU types.
(8) The MODULE-IDENTITY clause has been updated to (8) The MODULE-IDENTITY clause has been updated to reflect the
reflect the changes in the MIB module. changes in the MIB module.
(9) MIB boilerplate in section 2 has been updated to the (9) MIB boilerplate in section 2 has been updated to the latest
latest approved text. approved text.
(10) Added 64-bit version of ifMauFalseCarriers, and updated (10) Added 64-bit version of ifMauFalseCarriers, and updated
compliances accordingly. compliances accordingly.
(11) Added section on mapping of IEEE managed objects to the (11) Added section on mapping of IEEE managed objects to the objects
objects in this MIB module. in this MIB module.
A.2. Changes between RFC 2239 and RFC 2668 A.2. Changes between RFC 2239 and RFC 2668
This section enumerates the changes made to RFC 2239 to produce RFC This section enumerates the changes made to RFC 2239 to produce RFC
2668. 2668.
(1) The MODULE-IDENTITY has been updated to reflect the changes (1) The MODULE-IDENTITY has been updated to reflect the changes in
in the MIB. the MIB.
(2) OBJECT-IDENTITY definitions have been added for gigabit MAU (2) OBJECT-IDENTITY definitions have been added for gigabit MAU
types. types.
(3) The ifMauTypeList, ifMauAutoNegCapability, (3) The ifMauTypeList, ifMauAutoNegCapability,
ifMauAutoNegCapAdvertised and ifMauAutoNegCapReceived ifMauAutoNegCapAdvertised and ifMauAutoNegCapReceived objects
objects have been deprecated and replaced by have been deprecated and replaced by ifMauTypeListBits,
ifMauTypeListBits, ifMauAutoNegCapabilityBits, ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits and
ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapReceivedBits.
ifMauAutoNegCapReceivedBits.
(4) Two new objects, ifMauAutoNegRemoteFaultAdvertised and (4) Two new objects, ifMauAutoNegRemoteFaultAdvertised and
ifMauAutoNegRemoteFaultReceived have been added. ifMauAutoNegRemoteFaultReceived have been added.
(5) Enumerations for 'offline' and 'autoNegError' have been (5) Enumerations for 'offline' and 'autoNegError' have been added
added for the rpMauMediaAvailable and ifMauMediaAvailable for the rpMauMediaAvailable and ifMauMediaAvailable objects.
objects.
(6) The broadMauBasicTable and mauBroadBasic object group have (6) The broadMauBasicTable and mauBroadBasic object group have been
been deprecated. deprecated.
(7) The mauIfGrp100Mbs and mauIfGrpAutoNeg object groups have (7) The mauIfGrp100Mbs and mauIfGrpAutoNeg object groups have been
been deprecated and replaced by mauIfGrpHighCapacity and deprecated and replaced by mauIfGrpHighCapacity and
mauIfGrpAutoNeg2. mauIfGrpAutoNeg2.
(8) A new object group, mauIfGrpAutoNeg1000Mbps, has been added. (8) A new object group, mauIfGrpAutoNeg1000Mbps, has been added.
(9) The mauModIfCompl and mauModRpCompl compliances have been (9) The mauModIfCompl and mauModRpCompl compliances have been
deprecated and replaced by mauModIfCompl2 and deprecated and replaced by mauModIfCompl2 and mauModRpCompl2.
mauModRpCompl2.
(10) Added section on relationship to RFC 2239. (10) Added section on relationship to RFC 2239.
(11) Updated the SNMP Network Management Framework boilerplate. (11) Updated the SNMP Network Management Framework boilerplate.
(12) Refer to the Interfaces MIB, rather than the interfaces (12) Refer to the Interfaces MIB, rather than the interfaces group
group of MIB-II. of MIB-II.
(13) Updated references to refer to latest edition of IEEE 802.3. (13) Updated references to refer to latest edition of IEEE 802.3.
(14) An intellectual property notice was added, as required by (14) An intellectual property notice was added, as required by RFC
RFC 2026. 2026.
Author's Address
John Flick
Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557
Phone: +1 916 785 4018
EMail: johnf@rose.hp.com
Full Copyright Statement
B. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 73 change blocks. 
214 lines changed or deleted 189 lines changed or added

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