<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.mrose-rfc3288bis" target="https://datatracker.ietf.org/doc/html/draft-mrose-rfc3288bis-02">
   <front>
      <title>Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)</title>
      <author initials="E." surname="O&#x27;Tuathail" fullname="Eamon O&#x27;Tuathail">
         <organization>Clipcode.com</organization>
      </author>
      <author initials="M. T." surname="Rose" fullname="Dr. Marshall T. Rose">
         <organization>Dover Beach Consulting</organization>
      </author>
      <date month="May" day="13" year="2005" />
      <abstract>
	 <t>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.

 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]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-mrose-rfc3288bis-02" />
   
</reference>
