Asynchronous Services Bus Protocol
draft-adligo-hybi-asbp-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT
expiration date: April 9, 2016
Intended status: Draft Standard

draft-adligo-hybi-asbp-02
Internet Engineering Task Force (IETF)                        S. Morgan
Request for Comments:                                        Adligo Inc
Obsoletes:                                              October 7, 2016
Category: Standards Track                                    
ISSN: 

                Asynchronous Services Bus Protocol

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.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with
   respect to this document.
Morgan                       Standards Track                   [Page 1]

RFC <rfc-no>      Asynchronous Services Bus Protocol       October 2016

Table of Contents

   1. Introduction ...................................................3
      1.1. Background.................................................3
      1.2. Conventions and Terminology................................3
      1.3. Protocol Overview..........................................5
           1.3.1 ASBP Layered on HTTP.................................6
           1.3.2 ASBP Layered on WebSocket............................6
           1.3.3 ASBP Layered on Extended WebSocket...................6
           1.3.4 Header Overview......................................6
                 1.3.4.1 Header Syntax................................7
                 1.3.4.2 Reserved Header Keys.........................7
   2. Asynchronous-Services-Bus Components............................9
      2.1. Channels...................................................9
      2.2. Course.....................................................9
      2.3. Tubes......................................................9
      2.4. Brokers....................................................8
      2.5. Broker-Agents.............................................10
      2.6. User Agents...............................................10
      2.7. Application Agents........................................10
   3  Advantages of Asynchronous-Services-Bus Architecture...........11
      3.1. Maintenance and Upgrades Without Down Time................11
         3.1.1 Large Scale Deployment Diagram........................12
      3.2. Asynchronous-Services-Bus Architecture Usage in 
                Three Tiers..........................................13
         3.2.1 Three Tier Command Diagram............................13
      3.3. Asynchronous-Services-Bus Architecture Usage on 
                Four+ Tiers..........................................13
         3.3.1 Four Tier Command Diagram.............................14
      3.4. Unlimited Extension of Tiers..............................14
         3.4.1 Unlimited Tier Command Diagram........................15
   4. Protocol Versions..............................................15
   5. IANA Considerations............................................15
   6. Internationalization Considerations............................16
   7. Security Considerations........................................16
Show full document text