SNMP managed objects for Middlebox Communications (MIDCOM)
draft-srisuresh-midcom-mib-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pyda Srisuresh | ||
| Last updated | 2003-10-27 | ||
| 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
Middlebox communication (midcom) was conceived to move application level gateway (ALG) intelligence out of middleboxes into application specific midcom agents. Midcom agents will be assumed to use midcom to control middlebox resources so as to permit applications to traverse a middlebox. The scope of the middleboxes is limited to NAT and firewall devices. This document defines SNMP managed midcom objects to control middlebox resources and justifies adapting SNMPv3 as the midcom protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)