Some Considerations for SNMP Agent Developers
draft-aromanov-snmp-hiqa-06
| Document | Type |
Expired Internet-Draft
(ops)
Expired & archived
|
|
|---|---|---|---|
| Author | Aleksey Y. Romanov | ||
| Last updated | 2004-06-17 (Latest revision 2003-09-17) | ||
| RFC stream | Independent Submission | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Stream | ISE state | (None) | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Telechat date | (None) | ||
| Responsible AD | Bert Wijnen | ||
| IESG note | |||
| Send notices to | <ralex@world.std.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
SNMP is a ubiquitous protocol. Many software developers working in the embedded space develop or interface with MIB handlers and SNMP agents one way or another. Often these developers are unfamiliar with SNMP standards and overlook a number of subtle points. This document will provide a list of steps and rules to avoid common problems in order to develop a high quality SNMP agent.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)