Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 21
- 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]
- Publication Date
- 2006-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4227- Link
- https://doi.org/10.17487/RFC4227
- Author(s)
- Eamon O'TuathailDr. Marshall T. Rose
- Keyword(s)
- XML, RPC, Asynchronous Event Notification, Unacknowledged Messages
Latest version of IETF RFC 4227
Document Versions — IETF RFC 4227
-
▶ IETF RFC 4227 (2006-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Amended by:
- RFC8553 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 2045 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2782 [Active*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 3080 [Active*]
- IETF RFC 3156 [Active*]
- IETF RFC 3851 [Superseded*]
- RFC3902 — 5 EXTERNAL
- IETF RFC 3986 [Active, Amended*]
- W3C.soap12-mtom.20050125 — 7 EXTERNAL
- W3C.soap12-part1.20030624 — 2 EXTERNAL
- W3C.soap12-part2.20030624 — 3 EXTERNAL
- W3C.xop10.20050125 — 8 EXTERNAL
Bibliographic Reference(s)
- Barton, J., Thatte, S., and H. Nielsen, "SOAP Messages with Attachments", W3C NOTE NOTE-SOAP-attachments-20001211, December 2000. EXTERNAL
- Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H., Thatte, S., and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", W3C NOTE NOTE-SOAP-20000508, May 2000. EXTERNAL
- IETF RFC 2387 [Active*]
- IETF RFC 2392 [Active*]
- IETF RFC 2557 [Active*]
- RFC3288 — 16 EXTERNAL
- W3C.soap12-part0.20030624 — 15 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4227.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4227, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP). Available at https://doi.org/10.17487/RFC4227
Snippet:
IETF RFC 4227, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP). Available at https://doi.org/10.17487/RFC4227
HTML (ISO 690 compliant)
Preview:
IETF RFC 4227, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP). Available at https://doi.org/10.17487/RFC4227
Snippet:
<span class="citation"><cite>IETF RFC 4227</cite>, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP). Available at <a href="https://doi.org/10.17487/RFC4227" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4227</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4227, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
doi: 10.17487/RFC4227
url: https://doi.org/10.17487/RFC4227
doi: 10.17487/RFC4227
url: https://doi.org/10.17487/RFC4227
Snippet:
<li> <cite id="bib-rfc4227">IETF RFC 4227</cite>, Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) <span class="doi">10.17487/RFC4227</span> </li>
Referenced By
- IETF RFC 4743 [Active*]