Asynchronous Services Bus Protocol

Document Type Expired Internet-Draft (individual)
Last updated 2017-04-10 (latest revision 2016-10-07)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html 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


ASBP (Asynchronous Services Bus Protocol) is a simple command based application-level protocol for routing data and messages. ASBP is intended to allow implementation of fully Asynchronous Service Bus Architectures, in a simple standardized manor. ASBP is intended to be layered over WebSocket or HTTP. The protocol consists of a simple ASCII or UTF-8 key value(s) header and any arbitrary data (text, binary, XML, JSON, etc.), which the application's specific Command-Attendant or Command-Respondent processes. In addition this document touches on an extension to ASBP, CP (Conversation Protocol) a protocol used to facilitate communication between Asynchronous Service Busses implemented or hosted by different organizations. CP will be covered in more detail in another RFC still in progress. Internet-Draft This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress.


Scott Morgan (
Adligo Inc

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