Using the Simple Object Access Protocol in Blocks Extensible Exchange Protocol
RFC 4227, “Using the Simple Object Access Protocol in Blocks Extensible Exchange Protocol”, is a Proposed Standard document published in January 2006 by E. O'Tuathail, M. Rose. It obsoletes RFC 3288. It has since been updated by RFC 8553. The canonical text is published by the RFC Editor.
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.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4227 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4224 RObust Header Compression : ROHC over Channels That Can Reorder Packets
- RFC 4233 Integrated Services Digital Network Q.921-User Adaptation Layer
- RFC 4246 International Standard Audiovisual Number URN Definition
- RFC 4249 Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components
- RFC 4250 The Secure Shell Protocol Assigned Numbers
- RFC 4251 The Secure Shell Protocol Architecture
- RFC 4252 The Secure Shell Authentication Protocol
- RFC 4253 The Secure Shell Transport Layer Protocol