Definitions of Managed Objects for MIDCOM Server
draft-stiemerling-midcom-server-mib-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Stiemerling | ||
| Last updated | 2003-12-03 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 describes a set of managed objects that allow monitoring and configuration of middleboxes running a MIDCOM server, i.e. the MIDCOM MIB module RFC YYYY.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)