Last Modified: 2004-01-22
Close coordination with hardware standards development in IEEE 802.3 will be followed. The WG chair will support the communication with IEEE 802.3. When objects are added that require hardware support, IEEE 802.3 shall be informed, so that they consider to add them to their draft/standard.
The MIB object definitions produced will be for use by SNMP and will be adequately consistent with other SNMP objects, standards and conventions.
The working group will work on the following MIB modules for the IEEE 802.3ah (Ethernet First Mile) interfaces and devices:
- Ethernet First Mile (EFM) MIB common attributes, OAM operations and statistics
- Copper EFM MIB
- Ethernet Passive Optical Networks (EPON) MIB
The base for the definition of the managed objects in these MIB modules will be the management-related clauses in IEEE 802.3ah specification. The working group will also take into consideration management objects defined by other Working Groups in the IETF (ADSL MIB for example), or other standard bodies (G.983.2), will avoid work duplication, and describe the relationship with these specifications.
Done | Meet at the 41st IETF to discuss implementation experience of RFC 2108 and RFC 2239, and to consider future extensions for Full Duplex operation and 1 Gigabit Ethernet Speeds | |
Done | Gather implementation experience feedback concerning RFC 2108 and RFC 2239 | |
Done | Post Internet-Draft(s) for Full Duplex and 1 Gigabit Ethernet MIB extensions | |
Done | Meet at the 42nd IETF to discuss the Internet-Draft(s) and issue recomendations concerning advancement of RFC 2108 and RFC 2239 on the standards track | |
Done | Post revised Internet-Draft(s) | |
Done | Conduct WG Last Call on Internet-Draft(s) | |
Done | Submit final version of the Internet-Draft(s) to the IESG for consideration as Proposed Standards | |
Done | Submit revised version of the Internet-Drafts, following the Area Directorate review | |
Done | Submit final versions of the MAU MIB and Ethernet-like Interfaces MIB Internet-Draft(s) to the IESG for consideration as Proposed Standards | |
Done | Submit the Ethernet Chipsets document to IESG for consideration as an Informational RFC | |
Done | Begin identifying new work items for future work | |
Done | Issue WG Drafts for MIBs for P802.3ae & P802.3af | |
Done | Issue revised WG Drafts for MIBs for P802.3ae/P802.3af | |
Done | Gather implementation experience concerning WG documents already on the standards track | |
Done | WG Last Call All documents | |
Done | Issue revised WG drafts for existing stds track documents if so required by the implementation reports | |
Done | Forward Internet-Drafts to the AD/IESG Stds track considerations | |
Done | Power Ethernet MIB Last Call | |
Done | Submit Power Ethernet MIB to AD/IESG for Standards track consideration | |
Oct 03 | Individual submissions for the EFM MIB modules | |
Dec 03 | First round of WG Internet-Drafts for the EFM MIB modules | |
Apr 04 | Working Group Last Call | |
Jun 04 | Submit the Internet-Drafts to the IESG for consideration as Proposed Standards |
RFC | Status | Title |
---|---|---|
RFC1368 | PS | Definitions of Managed Objects for IEEE 802.3 Repeater Devices |
RFC1516 | DS | Definitions of Managed Objects for IEEE 802.3 Repeater Devices |
RFC1515 | PS | Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) |
RFC2108 | PS | Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 |
RFC2239 | PS | Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 |
RFC2358 | PS | Definitions of Managed Objects for the Ethernet-like Interface Types |
RFC2665 | PS | Definitions of Managed Objects for the Ethernet-like Interface Types |
RFC2666 | I | Definitions of Object Identifiers for Identifying Ethernet Chip Sets |
RFC2668 | PS | Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 |
RFC3635 | PS | Definitions of Managed Objects for the Ethernet-like Interface Types |
RFC3637 | PS | Definition of Managed Objects for the Ethernet WAN Interface Sublayer |
RFC3636 | PS | Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) |
RFC3638 | I | Applicability Statement for Reclassification of RFC 1643 to Historic Status |
RFC3621 | Standard | Power Ethernet MIB |
Monday. WG:Ethernet Interfaces and Hub MIB WG (hubmib) Date:Wednesday, March 3 at 0900-1130 CHAIR: Dan Romascanu <dromasca@avaya.com> Reported by: Shailaja General Comment: Since next versions of the drafts will be the last call and hence authors need to do give special attention to all the aspects of the draft like formatting,compilation of the MIB etc. 3. Generic EFM MIB Issues (Dan on behalf of Matt) - 30 minutes Slide-Common MIB or OAM MIB There was a discussion about OAM and MIB seem to represent the same meaning and hence need to consider removing the word OAM. Dan to take this matter to the list. Slide-loopback(I) More detailed mail sent by Matt Squire to the list. It will be included in the next draft, unless there are objections. Slide -Counters and Discontinuities Proposal - include the clarification text unless there are objections on the list. Slide -Event Counter Inconsistency (II) Proposal - Include read-only objects to reflect the internal counters, unless objected on the list. Event Controls Proposal - provide event control mechanism as recommended in the slides, unless objected on the list 4. EPON MIB Issues (Lior) Accept all editorial comments made by Dan Settling Time and Lock Time - either do not include at all, or include with a conformance clause, so that we do not delay the IEEE process. Lior to look into Entity Sensor MIB for power and temperature reporting, in Entity State MIB for functional status, and in Alarm MIB for alarm status. Lior to take it to the WG list discussion about de-asserting mechanism, alarm thresholding and the events. Preference to referencing existing IETF MIB All other resolution - as proposed by Lior on the list, unless there are objections. 5. EFM Cu Issues Slide ifstackTable/efmCu MIB -Leave it as it is unless it bothers someone in the WG list. SHDSL/VDSL MIB Just leave it as it is. - Notifications - add if there is a need for EFM Cu specific events. Edward will bring this to the list. Some events do not seem Cu specific (power loss, device fault) - use Alarm MIB for these -MAU-MIB Recommendation to add the sub-layers as distinct sub-types MAU MIB will be open and re-cycled on Proposed, unless there are objections on the list. - TC/PME layer - define new entry if there are objects specific to the new layer |