Referential Integrity Considerations in Management Information Base (MIB) Design
draft-presuhn-referent-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Randy Presuhn | ||
| Last updated | 2002-10-30 | ||
| 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 identifies some of referential integrity considerations of which management information base (MIB) designers should be aware. It is intended to promote discussion and the identification of additional related issues. Comments are welcomed, from the Operations and Management Area in general, from MIB writers, and from participants in the sming and eos working groups and the xmlconf BOF in particular. Please send comments to the mibs@ops.ietf.org mailing list.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)