--- 1/draft-ietf-hubmib-mau-mib-v3-01.txt 2006-02-04 23:26:21.000000000 +0100 +++ 2/draft-ietf-hubmib-mau-mib-v3-02.txt 2006-02-04 23:26:21.000000000 +0100 @@ -11,26 +11,26 @@ K. de Graaf Argon Networks D. Romascanu Avaya Inc. D. McMaster Cisco Systems, Inc. K. McCloghrie Cisco Systems, Inc. S. Roberts Farallon Computing, Inc. - February 2002 + May 2002 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. @@ -172,21 +172,21 @@ standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience this document refers to these devices as "repeater MAUs" and "interface MAUs." 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 Attachment Units (MAUs)", Section 30.6, "Management for link Auto- Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed object classes" of IEEE Std. 802.3, 2000 edition [IEEE802.3], as - ammended by IEEE Draft P802.3ae/D4.01 [P802.3ae]. That specification + amended by IEEE Draft P802.3ae/D4.3 [P802.3ae]. That specification 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 provide for management of all types of Ethernet/802.3 MAUs. 3.1. Relationship to RFC 2668 This MIB is intended to be a superset of that defined by RFC 2668 [RFC2668], which will go to historic status. 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 @@ -234,22 +234,22 @@ The sections of this document that define interface MAU-related objects specify an extension to the Interfaces MIB [RFC2863]. An agent implementing these interface-MAU related objects MUST also implement the relevant groups of Interface MIB. The value of the object ifMauIfIndex is the same as the value of 'ifIndex' used to instantiate the interface to which the given MAU is connected. It is REQUIRED that an agent implementing the interface-MAU related objects in this MIB will also implement the Ethernet-like Interfaces MIB, [ETHERIF]. Furthermore, when the interface-MAU related objects - are used to manage a 10GBASE-W PHY -- e.e., when ifMauType is equal - to dot2MauType10GigBaseW or any other 10GBASE-W variant -- then the + are used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal + to dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB [ETHERWIS] and must follow the interface layering model specified 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, i.e., for the ifTable entry that has 'ifType' equal 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 the agent SHALL create ifTable, ifStackTable, and ifInvStackTable entries that pertain to the WIS when ifMauDefaultType is changed to a 10GBASEW variant (i.e., one of dot3MauType10GigBaseW, @@ -362,21 +362,21 @@ OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI TruthValue, TEXTUAL-CONVENTION FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF InterfaceIndex FROM IF-MIB; mauMod MODULE-IDENTITY - LAST-UPDATED "200202280000Z" -- February 28, 2002 + LAST-UPDATED "200205100000Z" -- May 10, 2002 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 @@ -399,32 +399,32 @@ [IEEE 802.3 Std] refers to IEEE Std 802.3, 2000 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 - ammended by IEEE Draft P802.3ae/D4.01: + amended by IEEE Draft P802.3ae/D4.3: 'Supplement to Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method & Physica Layer Specifications - Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters - for 10 Gb/s Operation', February 2002. + for 10 Gb/s Operation', April 2002. Of particular interest is Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s and 10 Gb/s Management'." - REVISION "200202280000Z" -- February 28, 2002 + REVISION "200205100000Z" -- May 10, 2002 DESCRIPTION "This version published as RFC XXXX. Updated to include support for 10 Gb/s MAUs." REVISION "9908240400Z" -- August 24, 1999 DESCRIPTION "This version published as RFC 2668. Updated to include support for 1000 Mb/sec MAUs and flow control negotiation." REVISION "9710310000Z" -- October 31, 1997 DESCRIPTION "Version published as RFC 2239." @@ -1430,21 +1430,21 @@ aJabber.jabberFlag." ::= { ifMauEntry 7 } ifMauJabberingStateEnters OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). This counter will always - indicate zero for MAUs of type dot1MauTypeAUI + indicate zero for MAUs of type dot3MauTypeAUI and those of speeds above 10Mbps. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCounter. RFC 2863, ifCounterDiscontinuityTime." ::= { ifMauEntry 8 } @@ -2654,34 +2654,34 @@ [IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "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", (Adopted by ISO/IEC and redesignated as ISO/IEC 8802-3:2000(E), 2000. [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, - IEEE Draft P802.3ae/D4.01, February 2002, work in + IEEE Draft P802.3ae/D4.3, April 2002, work in progress. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000. [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2", RFC 2108, February 1997. [ETHERIF] Flick, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", work in progress, - draft-ietf-hubmib-etherif-mib-v3-01.txt, February, 2002. + draft-ietf-hubmib-etherif-mib-v3-02.txt, May, 2002. Non-Normative References [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. @@ -2746,21 +2746,21 @@ RFC 2239, November 1997. [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 1515, September 1993. [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, K., Norseth, K. C., and K. Tesink, "Definitions of Managed Objects for the Ethernet WAN Interface Sublayer", work in progress, - draft-ietf-hubmib-wis-mib-02.txt, February 2002. + draft-ietf-hubmib-wis-mib-04.txt, May 2002. 8. Security Considerations 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 serious effect on the operation of the network, including: enabling or disabling a MAU changing a MAU's default type enabling, disabling or restarting autonegotiation