Electronic Data Interchange MIB (EDIMIB) Version 1
draft-bolton-edimib-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Bolton , John Andrukonis | ||
| Last updated | 1996-09-25 | ||
| 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
This memo defines a MIB for use with managing EDI systems. The term EDI systems includes large scale systems providing translator functions such as the US federal government's Electronic Commerce Processing Node (ECPN) for which this MIB was specifically designed, as well as smaller Value Added Network (VAN) systems. Because of the desire for scalability variable names are deliberately vague, so that a channel may represent a single user, a group of users that use the same network entry point or that are defined by the implementor as functionally similar, or (as in the case of the ECPN) a connection to a third party network. This MIB does not address management of client systems which connect to the various EDI systems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)