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

A new Request for Comments is now available in online RFC libraries.

        RFC 4227

        Title:      Using the Simple Object Access Protocol (SOAP)
                    in Blocks Extensible Exchange Protocol (BEEP)
        Author(s):  E. O'Tuathail, M. Rose
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    eamon.otuathail@clipcode.com,
                    mrose@dbc.mtview.ca.us
        Pages:      21
        Characters: 39112
        Obsoletes:  3288

        I-D Tag:    draft-mrose-rfc3288bis-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4227.txt

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.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.