Asynchronous Management Protocol

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Edward Birrane  , Jeremy Pierce-Mayer 
Last updated 2016-12-28 (latest revision 2016-06-26)
Stream (None)
Intended RFC status (None)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Edward Birrane (
Jeremy Pierce-Mayer (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)