@techreport{adligo-hybi-asbp-02,
    number =    {draft-adligo-hybi-asbp-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-adligo-hybi-asbp/02/},
    author =    {Scott Morgan and Adligo Inc},
    title =     {{Asynchronous Services Bus Protocol}},
    pagetotal = 21,
    year =      2016,
    month =     oct,
    day =       7,
    abstract =  {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 http://datatracker.ietf.org/drafts/current. 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.},
}