--- 1/draft-ietf-hubmib-wis-mib-03.txt 2006-02-04 23:26:40.000000000 +0100 +++ 2/draft-ietf-hubmib-wis-mib-04.txt 2006-02-04 23:26:40.000000000 +0100 @@ -1,30 +1,30 @@ Ethernet Interfaces and Hub MIB Working Group Mike Ayers -INTERNET DRAFT BMC Software, Inc. +INTERNET DRAFT Consultant John Flick Hewlett-Packard Company C. M. Heard Consultant Kam Lam Lucent Technologies Kerry McDonald CSU San Bernardino K. C. Norseth Consultant Kaj Tesink Telcordia Technologies - April 14, 2002 + May 2, 2002 Definitions of Managed Objects for the Ethernet WAN Interface Sublayer - + 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. Internet-Drafts are draft documents valid for a maximum of six months @@ -561,22 +561,22 @@ SONET-MIB - sonetMediumType none required SONET-MIB - sonetMediumTimeElapsed none required SONET-MIB - sonetMediumValidIntervals none required SONET-MIB - sonetMediumLineCoding none required SONET-MIB - sonetMediumLineType none required SONET-MIB - sonetMediumCircuitIdentifier none required SONET-MIB - sonetMediumInvalidIntervals none required SONET-MIB - sonetMediumLoopbackConfig none required SONET-MIB - sonetSESthresholdSet none required - ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 tx - ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 rx + ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 transmit + ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 receive SONET-MIB - sonetSectionCurrentStatus 10G WIS status 3 SONET-MIB - sonetSectionCurrentESs \ SONET-MIB - sonetSectionCurrentSESs \ SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS status 3 SONET-MIB - sonetSectionCurrentCVs | + SONET-MIB - sonetSectionIntervalESs | 10G WIS section SONET-MIB - sonetSectionIntervalSESs | BIP error count SONET-MIB - sonetSectionIntervalSEFSs / SONET-MIB - sonetSectionIntervalCVs / SONET-MIB - sonetSectionIntervalValidData none required @@ -596,22 +596,22 @@ SONET-MIB - sonetFarEndLineCurrentSESs \ SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS status 3 SONET-MIB - sonetFarEndLineCurrentUASs | + SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS far end SONET-MIB - sonetFarEndLineIntervalSESs | line BIP errors SONET-MIB - sonetFarEndLineIntervalCVs / SONET-MIB - sonetFarEndLineIntervalUASs / SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS status 3 ETHER-WIS - etherWisPathCurrentStatus 10G WIS status 3 - ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 tx - ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 rx + ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 transmit + ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 receive SONET-MIB - sonetPathCurrentWidth none required SONET-MIB - sonetPathCurrentStatus 10G WIS status 3 SONET-MIB - sonetPathCurrentESs \ SONET-MIB - sonetPathCurrentSESs \ SONET-MIB - sonetPathCurrentCVs | 10G WIS status 3 SONET-MIB - sonetPathCurrentUASs | + SONET-MIB - sonetPathIntervalESs | 10G WIS SONET-MIB - sonetPathIntervalSESs | path block SONET-MIB - sonetPathIntervalCVs / error count @@ -712,21 +712,21 @@ sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, sonetFarEndLineStuff2, sonetPathStuff2, sonetFarEndPathStuff2, sonetMediumType, sonetMediumLineCoding, sonetMediumLineType, sonetMediumCircuitIdentifier, sonetMediumLoopbackConfig, sonetSESthresholdSet, sonetPathCurrentWidth FROM SONET-MIB; etherWisMIB MODULE-IDENTITY - LAST-UPDATED "200204141830Z" -- April 14, 2002 + LAST-UPDATED "200205022034Z" -- May 2, 2002 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO "WG charter: http://www.ietf.org/html.charters/hubmib-charter.html Chair: Dan Romascanu Postal: Avaya Inc. Atidim Technology Park, Bldg. 3 Tel Aviv 61131 @@ -748,34 +748,34 @@ The following reference is used throughout this MIB module: [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 amended by IEEE Draft P802.3ae/D4.2: + specifications', as amended by IEEE Draft P802.3ae/D5.0: 'Supplement to Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method & Physical Layer Specifications - Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters - for 10 Gb/s Operation', March 21, 2002. + for 10 Gb/s Operation', May 1, 2002. Of particular interest are Clause 50, 'WAN Interface Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link Aggregation Management', and Clause 45, 'Management Data Input/Output (MDIO) Interface'." - REVISION "200204141830Z" -- April 14, 2002 + REVISION "200205022034Z" -- May 2, 2002 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice ::= { transmission XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice -- The main sections of the module etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } @@ -1400,25 +1400,25 @@ [ETHERIF] Flick, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", , work in progress. [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", , work in progress. [P802.3ae] Institute of Electrical and Electronic Engineers, IEEE Draft - P802.3ae/D4.2, "Supplement to Carrier Sense Multiple Access + P802.3ae/D5.0, "Supplement to Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method & Physical Layer Specifications - Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters for 10 - Gb/s Operation", March 21, 2002, work in progress. + Gb/s Operation", May 1, 2002, work in progress. 7.2. Informative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. @@ -1435,38 +1435,36 @@ "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. 8. Authors' Addresses Mike Ayers - BMC Software, Inc. - 2141 North First Street - San Jose, CA 95131 + 1204 Knox Ave. + San Jose, CA 95122 USA - Phone: +1 408 546 0947 - Fax: +1 408 965 0359 - Email: mayers@bmc.com + Phone: +1 408 857 6810 + EMail: mike.ayers@earthling.net John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 USA Phone: +1 916 785 4018 Fax: +1 916 785 1199 - Email: johnf@rose.hp.com + EMail: johnf@rose.hp.com C. M. Heard 600 Rainbow Dr. #141 Mountain View, CA 94041-2542 USA Phone: +1 650 964 8391 EMail: heard@pobox.com Kam Lam @@ -1474,30 +1472,30 @@ 101 Crawfords Corner Road, Room 4C-616A Holmdel, NJ 07733 USA Phone: +1 732 949 8338 EMail: hklam@lucent.com Kerry McDonald Institute for Applied Supercomputing California State University San Bernardino - Email: kerry_mcd@hotmail.com + EMail: kerry_mcd@hotmail.com kmcdonal@csci.csusb.edu K. C. Norseth 934 S. Palos Verdes Dr. Kaysville, Utah 84037 USA Phone: +1 801 546 3316 - Email: kcn@norseth.com + EMail: kcn@norseth.com Kaj Tesink Telcordia Technologies 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 USA Phone: +1 732 758 5254 EMail: kaj@research.telcordia.com @@ -1748,26 +1746,38 @@ 17.) References [ETHERIF], [MAU-MIB], and [P802.3ae] were updated to , , and P802.3ae/D4.2, respectively. 18.) Normative and informative references were moved into separate sub-sections. 19.) A "To-Do List" section was added. + The following changes were made to + to produce : + + 1.) "tx" and "rx" were spelled out in the MDIO register names in + Section 3.7 in order to match the usage in P802.3ae/D4.3 and + P802.3ae/D5.0. + + 2.) References [IEEE 802.3 Std] in the MIB module and [P802.3ae] + in the text were updated to point to P802.3ae/D5.0. + + 3.) Author contact information was updated. + To-Do List NOTE TO RFC Editor: prior to publishing this document please take care of any open items listed below and then remove this section. - 1.) All occurrences of "IEEE Draft P802.3ae/D4.2" must be changed + 1.) All occurrences of "IEEE Draft P802.3ae/D5.0" must be changed to "IEEE Std 802.3ae" once the standard has been approved, the approval date must replace the draft publication date, and all occurrences of the reference tag [P802.3ae] must be changed to [802.3ae]. Note that this draft is referenced both in Section 4, "Object Definitions", and in Section 7.1, "Normative References". 2.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must be updated to point to the appropriate RFCs when the respective Internet Drafts are published, and all occurrences of the reference tags must be changed to [RFCnnnn] where nnnn is the