{
  "draft": "draft-mrose-rfc3288bis-02",
  "doc_id": "RFC4227",
  "title": "Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)",
  "authors": [
    "E. O'Tuathail",
    "M. Rose"
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "21",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "IETF - NON WORKING GROUP",
  "abstract": "This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding describes how SOAP messages are transmitted in the network.\n\n The SOAP is an XML-based (eXtensible Markup Language) messaging protocol used to implement a wide variety of distributed messaging models. It defines a message format and describes a variety of message patterns, including, but not limited to, Remote Procedure Calling (RPC), asynchronous event notification, unacknowledged messages, and forwarding via SOAP intermediaries. [STANDARDS-TRACK]",
  "pub_date": "January 2006",
  "keywords": [
    "xml",
    "extensible markup language",
    "remote procedure calling",
    "rpc",
    "asynchronous event notification",
    "unacknowledged messages",
    "binding"
  ],
  "obsoletes": [
    "RFC3288"
  ],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [
    "RFC8553"
  ],
  "see_also": [],
  "doi": "10.17487/RFC4227",
  "errata_url": "https://www.rfc-editor.org/errata/rfc4227"
}