draft-ietf-hubmib-mau-mib-v3-03.txt   draft-ietf-hubmib-mau-mib-v3-04.txt 
Ethernet Interfaces and Hub MIB Working Group J. Flick Ethernet Interfaces and Hub MIB Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company INTERNET DRAFT Hewlett-Packard Company
March 2003 June 2003
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-03.txt> <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 is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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
To view the list Internet-Draft Shadow Directories, see To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (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 This memo obsoletes RFC 2668. This memo extends that specification
by including management information useful for the management of 10 by including management information useful for the management of 10
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 ...................................... 56 5. Intellectual Property ...................................... 55
6. Acknowledgements ........................................... 56 6. Acknowledgements ........................................... 56
7. Normative References ....................................... 57 7. Normative References ....................................... 57
8. Informative References ..................................... 58 8. Informative References ..................................... 58
9. Security Considerations .................................... 58 9. Security Considerations .................................... 58
10. Authors' Addresses ........................................ 59 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
B. Full Copyright Statement ................................... 62 B. Full Copyright Statement ................................... 61
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 7, line 45 skipping to change at page 7, line 45
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 "200302280000Z" -- February 28, 2003 LAST-UPDATED "200306020000Z" -- June 2, 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 49 skipping to change at page 8, line 49
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 XXXX;
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 -- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note -- this note
REVISION "200302280000Z" -- February 28, 2003 REVISION "200306020000Z" -- June 2, 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
skipping to change at page 17, line 50 skipping to change at page 17, line 50
described by this entry from among other described by this entry from among other
MAUs connected to the same port MAUs connected to the same port
(rpMauPortIndex)." (rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 } ::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauType 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. An DESCRIPTION "This object identifies the MAU type. Values for
initial set of MAU types are defined above. The standard IEEE 802.3 MAU types are defined above.
assignment of OBJECT IDENTIFIERs to new types of
MAUs is managed by the IANA. If the MAU type is If the MAU type is unknown, the object identifier
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."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 } ::= { rpMauEntry 4 }
skipping to change at page 25, line 41 skipping to change at page 25, line 38
DESCRIPTION "This variable uniquely identifies the MAU DESCRIPTION "This variable uniquely identifies the MAU
described by this entry from among other MAUs described by this entry from among other MAUs
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. An DESCRIPTION "This object identifies the MAU type. Values for
initial set of MAU types are defined above. The standard IEEE 802.3 MAU types are defined above.
assignment of OBJECT IDENTIFIERs to new types of IANA. If the MAU type is unknown, the object identifier
MAUs is managed by the IANA. 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 54, line 25 skipping to change at page 54, line 20
::= { mauModCompls 3 } ::= { mauModCompls 3 }
mauModRpCompl2 MODULE-COMPLIANCE mauModRpCompl2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to repeater DESCRIPTION "Compliance for MAUs attached to repeater
ports. ports.
Note that compliance with this compliance Note that compliance with this compliance
statement requires compliance with the statement requires compliance with the
snmpRptrModCompl MODULE-COMPLIANCE statement of snmpRptrModCompl MODULE-COMPLIANCE statement of
the SNMP-REPEATER-MIB [RFC2108]." the SNMP-REPEATER-MIB (RFC 2108)."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauRpGrpBasic } MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrp100Mbs GROUP mauRpGrp100Mbs
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s or recommended for MAUs which have 100Mb/s or
greater capability." greater capability."
GROUP mauRpGrpJack GROUP mauRpGrpJack
skipping to change at page 55, line 8 skipping to change at page 54, line 51
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mauModCompls 4 } ::= { mauModCompls 4 }
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 [RFC2863] 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 [ETHERIF]."
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."
skipping to change at page 59, line 46 skipping to change at page 59, line 44
(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. Authors' Addresses 10. Author's Address
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
E-mail: johnf@rose.hp.com E-mail: johnf@rose.hp.com
A. Change Log A. Change Log
skipping to change at page 62, line 6 skipping to change at page 62, line 4
(12) Refer to the Interfaces MIB, rather than the interfaces (12) Refer to the Interfaces MIB, rather than the interfaces
group of MIB-II. group 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 2026. RFC 2026.
B. Full Copyright Statement B. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
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
 End of changes. 

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