ObsoletedPROPOSED STANDARDIETF stream

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

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4227.

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

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 core (BEEP). A SOAP binding describes how SOAP messages are transmitted in the network. [STANDARDS-TRACK]

Document record

Document ID
RFC3288
Published
June 2002
Authors
E. O'Tuathail; M. Rose
Status
PROPOSED STANDARD
Stream
IETF
Area
Pages
20
Also known as
Obsoleted by:
RFC 4227

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/3288-using-the-simple-object-access-protocol-soap-in-blocks-extensible-exchange-proto