Concluded WG Interfaces MIB (ifmib)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Interfaces MIB | |
|---|---|---|---|
| Acronym | ifmib | ||
| Area | Internet Area (int) | ||
| State | Concluded | ||
| Charter | charter-ietf-ifmib-01 Approved | ||
| Document dependencies | |||
| Personnel | Chair | Dr. Theodore O. Brunner | |
| Mailing list | Address | ifmib@ietf.org | |
| To subscribe | http://www.ietf.org/mailman/listinfo/ifmib | ||
| Archive | ftp://thumper.bellcore.com/pub/Group.archive/if-mib |
Final Charter for Working Group
The Interfaces MIB working group is reactivated and chartered to
accomplish one task: to prepare a recommendation to the IESG evaluating
RFC 1573 with respect to the standards track.
The recommendation will document implementation, interoperability, and
deployment experience. If this experiences suggests that changes
should
be made to the documents, new drafts may be prepared.
The recommendation will report one of four outcomes: that the RFC
should
be advanced from proposed to draft status, without changes (if no
problems are found); that a draft prepared by the working group, should
replace the RFC, and be designated a draft standard (if only minor
changes are made); that a draft prepared by the working group, should
replace the RFC, and be designated a proposed standard (if major
changes
or feature enhancements are made); or, that the RFC should be
designated
as historic (if this technology is problematic).
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Mar 1997 | Submit the interfaces MIB to the IESG for consideration as a Draft Standard |
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Meet at Montreal IETF | |
| Done | Post a internet-draft of the interface test mib | |
| Done | Meet at Dallas IETF | |
| Done | Post a internet-draft of the revised interfaces mib | |
| Done | Meet at 33rd IETF to review RFC1573 to ascertain if it is ready to be elevated to Draft Standard status. | |
| Done | Issue a call for implementation and operations experience with RFC1573 |