SNMP Textual Convention for Reusable Conceptual Rows
draft-ietf-ops-rowpointer-tc-01
| Document | Type |
Expired Internet-Draft
(candidate for opsarea AG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Robert C. Moore , Kwok H. Chan | ||
| Last updated | 2001-03-06 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 document defines a textual convention, ReusableRow, similar to the RowStatus and StorageType textual conventions defined in RFC 2579 [7]. Like these two textual conventions, ReusableRow characterizes the conceptual row of which it is a part. It indicates whether, in the course of a cloning activity, the row should be duplicated (with, obviously, a different index value), or simply pointed to by one or more newly cloned objects. This cloning may involve the scripting- based techniques defined under the SNMP Configuration umbrella, but it need not: cloning can also be realized with ordinary SNMP Get and Set operations.
Authors
Dr. Robert C. Moore
Kwok H. Chan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)