RFC 4227:Using the Simple Object Access Protocol (...
RFC-Ref

1. Introduction


   This memo specifies how SOAP envelopes [15] are transmitted using a
   BEEP profile [1].  Conforming implementations MUST support SOAP
   version 1.2 [15] and MAY support other versions, such as SOAP version
   1.1 [17].  This memo specifies how SOAP envelopes [15] are
   transmitted using a BEEP profile [1].  Unlike its predecessor,
   RFC3288(-> 4227prop) [16], this memo does not mandate the use of SOAP version 1.1.

   Throughout this memo, the term "envelope" refers to the top-level
   element exchanged by SOAP senders and receivers.  For example, when
   referring to SOAP version 1.2, the term "envelope" refers to the
   "Envelope" element defined in Section 5.1 of [2].  Furthermore, the
   terms "peer", "client", "server", "one-to-one", and "one-to-many" are
   used in the context of BEEP.  In particular, Sections 2.1 and 2.1.1
   of [1] discuss BEEP roles and exchange styles.



Google
Web
RFC-Ref