Using SNMP as Midcom Protocol
draft-quittek-midcom-snmp-eval-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Juergen Quittek | ||
| Last updated | 2002-04-24 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-quittek-midcom-snmp-eval-00.txt
Abstract
This memo evaluates the Simple Network Management Protocol (SNMP) as a candidate for realizing a Midcom protocol. The properties and capabilities of the SNMP management framework are compared to the Midcom requirements [MDC-REQ] and to the Midcom framework and architecture [MDC-FRM]. It is shown that SNMP matches almost all Midcom requirements and that with the already existing support for NATs [NAT-MIB] only little additional effort is required for creating a Midcom protocol solution based on the SNMP management framework.
Authors
Juergen Quittek (quittek@netlab.nec.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)