Asynchronous Management Protocol
draft-birrane-dtn-amp-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Edward J. Birrane , Jeremy Pierce-Mayer | ||
| Last updated | 2016-12-28 (Latest revision 2016-06-26) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Associated None milestone |
|
||
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-birrane-dtn-amp-03.txt
Abstract
This document describes an Asynchronous Management Protocol (AMP) in conformance with the Asynchronous Management Architecture (AMA). The AMP provides monitoring and configuration services between managing devices (Managers) and managed devices (Agents), some of which may operate on the far side of high-delay or high-disruption links. The AMP reduces the number of transmitted bytes, operates without sessions or (concurrent) two-way links, and functions autonomously when there is no timely contact with a network operator. The AMP accomplishes this without requiring mobile code.
Authors
Edward J. Birrane
Jeremy Pierce-Mayer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)