--- 1/draft-ietf-hubmib-mau-mib-v3-03.txt 2006-02-04 23:26:23.000000000 +0100 +++ 2/draft-ietf-hubmib-mau-mib-v3-04.txt 2006-02-04 23:26:23.000000000 +0100 @@ -1,19 +1,19 @@ Ethernet Interfaces and Hub MIB Working Group J. Flick INTERNET DRAFT Hewlett-Packard Company - March 2003 + June 2003 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) - + Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -24,21 +24,21 @@ 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 (C) The Internet Society (2002). All Rights Reserved. + Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo extends that specification by including management information useful for the management of 10 @@ -54,30 +54,30 @@ 3. Overview ................................................... 3 3.1. Relationship to RFC 2668 ................................. 3 3.2. Relationship to RFC 2239 ................................. 4 3.3. Relationship to RFC 1515 ................................. 4 3.4. Relationship to Other MIBs ............................... 4 3.4.1. Relationship to the Interfaces MIB ..................... 4 3.4.2. Relationship to the 802.3 Repeater MIB ................. 5 3.5. Management of Internal MAUs .............................. 5 3.6. Mapping of IEEE 802.3 Managed Objects .................... 6 4. Definitions ................................................ 7 - 5. Intellectual Property ...................................... 56 + 5. Intellectual Property ...................................... 55 6. Acknowledgements ........................................... 56 7. Normative References ....................................... 57 8. Informative References ..................................... 58 9. Security Considerations .................................... 58 - 10. Authors' Addresses ........................................ 59 + 10. Author's Address .......................................... 59 A. Change Log ................................................. 60 A.1. Changes since 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 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo also includes a MIB module. This MIB module extends the list of managed objects specified in the earlier version of this MIB @@ -313,21 +313,21 @@ OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI TruthValue, AutonomousType, TEXTUAL-CONVENTION FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF InterfaceIndex FROM IF-MIB; mauMod MODULE-IDENTITY - LAST-UPDATED "200302280000Z" -- February 28, 2003 + LAST-UPDATED "200306020000Z" -- June 2, 2003 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO "WG E-mail: hubmib@ietf.org To subscribe: hubmib-request@ietf.org Chair: Dan Romascanu Postal: Avaya Inc. Atidim Technology Park, Bldg. 3 Tel Aviv 61131 Israel @@ -364,21 +364,21 @@ Of particular interest is Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s and 10 Gb/s Management'. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." -- RFC Ed.: Replace XXXX with the actual RFC number & remove -- this note - REVISION "200302280000Z" -- February 28, 2003 + REVISION "200306020000Z" -- June 2, 2003 DESCRIPTION "Updated to include support for 10 Gb/s MAUs. This resulted in the following revisions: - Added OBJECT-IDENTITY definitions for 10 gigabit MAU types - Added fiberLC jack type to JackType TC - Extended ifMauTypeListBits with bits for the 10 gigabit MAU types - Added enumerations to ifMauMediaAvailable, and updated its DESCRIPTION to reflect @@ -790,25 +790,24 @@ described by this entry from among other MAUs connected to the same port (rpMauPortIndex)." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." ::= { rpMauEntry 3 } rpMauType OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-only STATUS current - DESCRIPTION "This object identifies the MAU type. An - initial set of MAU types are defined above. The - assignment of OBJECT IDENTIFIERs to new types of - MAUs is managed by the IANA. If the MAU type is - unknown, the object identifier + DESCRIPTION "This object identifies the MAU type. Values for + standard IEEE 802.3 MAU types are defined above. + + If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." ::= { rpMauEntry 4 } @@ -1162,25 +1163,23 @@ DESCRIPTION "This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same interface (ifMauIfIndex)." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." ::= { ifMauEntry 2 } ifMauType OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-only STATUS current - DESCRIPTION "This object identifies the MAU type. An - initial set of MAU types are defined above. The - assignment of OBJECT IDENTIFIERs to new types of - MAUs is managed by the IANA. If the MAU type is - unknown, the object identifier + DESCRIPTION "This object identifies the MAU type. Values for + standard IEEE 802.3 MAU types are defined above. + IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. This object represents the operational type of @@ -2522,21 +2524,21 @@ ::= { mauModCompls 3 } mauModRpCompl2 MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to repeater ports. Note that compliance with this compliance statement requires compliance with the snmpRptrModCompl MODULE-COMPLIANCE statement of - the SNMP-REPEATER-MIB [RFC2108]." + the SNMP-REPEATER-MIB (RFC 2108)." MODULE -- this module MANDATORY-GROUPS { mauRpGrpBasic } GROUP mauRpGrp100Mbs DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s or greater capability." GROUP mauRpGrpJack @@ -2553,21 +2555,21 @@ DESCRIPTION "Write access is not required." ::= { mauModCompls 4 } mauModIfCompl3 MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to interfaces. Note that compliance with this compliance statement requires compliance with 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 EtherLike-MIB [ETHERIF]." MODULE -- this module MANDATORY-GROUPS { mauIfGrpBasic } GROUP mauIfGrpHighCapacity DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s or greater capability." @@ -2781,21 +2783,21 @@ (for authentication and privacy). Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. -10. Authors' Addresses +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 @@ -2881,22 +2884,21 @@ (12) Refer to the Interfaces MIB, rather than the interfaces group of MIB-II. (13) Updated references to refer to latest edition of IEEE 802.3. (14) An intellectual property notice was added, as required by RFC 2026. B. Full Copyright Statement - - Copyright (C) The Internet Society (2002). All Rights Reserved. + Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of