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

Network Working Group                                      E. O'Tuathail
Request for Comments: 4227                                  Clipcode.com
Obsoletes: 3288                                                  M. Rose
Category: Standards Track                   Dover Beach Consulting, Inc.
                                                            January 2006

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

Status of This Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2006).

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.

O'Tuathail & Rose           Standards Track                     [Page 1]
RFC 4227                   Using SOAP in BEEP               January 2006

Table of Contents

   1. Introduction ....................................................3
   2. BEEP Profile Identification .....................................3
      2.1. Profile Initialization .....................................4
   3. SOAP Message Packages ...........................................6
   4. SOAP Message Patterns ...........................................8
      4.1. One-Way Message ............................................8
      4.2. Request-Response Exchange ..................................8
      4.3. Request/N-Responses Exchange ...............................8
      4.4. Error Handling .............................................9
   5. SOAP Protocol Binding Framework Conformance .....................9
      5.1. Binding Name ...............................................9
      5.2. Base URI ...................................................9
      5.3. Supported SOAP Message Exchange Patterns ...................9
      5.4. Supported Features .........................................9
      5.5. MEP Operation .............................................10
           5.5.1. Behavior of Requesting SOAP Node ...................10
                  5.5.1.1. Init ......................................10
                  5.5.1.2. Requesting ................................10
                  5.5.1.3. Sending+Receiving .........................10
                  5.5.1.4. Success and Fail ..........................11
           5.5.2. Behavior of Responding SOAP Node ...................11
                  5.5.2.1. Init ......................................11
                  5.5.2.2. Receiving .................................11
                  5.5.2.3. Receiving+Sending .........................11
                  5.5.2.4. Success and Fail ..........................11
   6. URL Schemes ....................................................11
      6.1. The soap.beep URL Scheme ..................................11
           6.1.1. Resolving IP/TCP Address Information ...............12
      6.2. The soap.beeps URL Scheme .................................13
   7. Registration Templates .........................................13
      7.1. SOAP Profile Feature Registration Template ................13
   8. Initial Registrations ..........................................13
      8.1. Registration: The SOAP Profile ............................13
      8.2. Registration: The soap.beep URL Scheme ....................14
      8.3. Registration: The soap.beeps URL Scheme ...................14
      8.4. Registration: The System (Well-Known) TCP Port
           Number for SOAP ...........................................15
   9. Security Considerations ........................................15
   10. IANA Considerations ...........................................16
   11. Changes from RFC 3288 .........................................16
   12. Acknowledgements ..............................................17
   13. References ....................................................17
      13.1. Normative References .....................................17