Storage Type MIB
draft-schoenw-storage-type-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jürgen Schönwälder | ||
| Last updated | 2001-06-21 | ||
| 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
The second version of the Structure of Management Information (SMIv2) introduced the StorageType textual convention in RFC 2579. It is used to describe the memory realization of rows in conceptual tables. Several standards-track MIB modules make use of this convention. Implementation experience shows that different approaches are used to actually write conceptual rows into non-volatile memory. This memo addresses this question and provides a MIB module which can be used to explicitly commit non-volatile rows into non-volatile memory.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)