metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)

Still current, but amended. Parts of this document are changed or extended by RFC 8553. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC4227
Published
January 2006
Authors
E. O'Tuathail; M. Rose
Status
PROPOSED STANDARD
Stream
IETF
Area
—
Pages
21
Also known as
—
Obsoletes:
RFC 3288
Updated by:
RFC 8553

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4227-using-the-simple-object-access-protocol-soap-in-blocks-extensible-exchange-proto