Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
RFC 3288
Document | Type |
RFC - Proposed Standard
(June 2002; No errata)
Obsoleted by RFC 4227
Was draft-etal-beep-soap (individual)
|
|
---|---|---|---|
Authors | Eamon O'Tuathail , Marshall Rose | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3288 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group E. O'Tuathail Request for Comments: 3288 Clipcode.com Category: Standards Track M. Rose Dover Beach Consulting, Inc. June 2002 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 (2002). All Rights Reserved. Abstract 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. 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, RPC, asynchronous event notification, unacknowledged messages, and forwarding via SOAP intermediaries. O'Tuathail & Rose Standards Track [Page 1] RFC 3288 Using SOAP in BEEP June 2002 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. BEEP Profile Identification . . . . . . . . . . . . . . . . 4 2.1 Profile Initialization . . . . . . . . . . . . . . . . . . . 5 3. SOAP Message Packages . . . . . . . . . . . . . . . . . . . 7 4. SOAP Message Patterns . . . . . . . . . . . . . . . . . . . 9 4.1 One-way Message . . . . . . . . . . . . . . . . . . . . . . 9 4.2 Request-Response Exchange . . . . . . . . . . . . . . . . . 9 4.3 Request/N-Responses Exchange . . . . . . . . . . . . . . . . 9 5. URL Schemes . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1 The soap.beep URL Scheme . . . . . . . . . . . . . . . . . . 10 5.1.1 Resolving IP/TCP Address Information . . . . . . . . . . . . 10 5.2 The soap.beeps URL Scheme . . . . . . . . . . . . . . . . . 11 6. Registration Templates . . . . . . . . . . . . . . . . . . . 12 6.1 SOAP Profile Feature Registration Template . . . . . . . . . 12 7. Initial Registrations . . . . . . . . . . . . . . . . . . . 13 7.1 Registration: The SOAP Profile . . . . . . . . . . . . . . . 13 7.2 Registration: The soap.beep URL Scheme . . . . . . . . . . . 14 7.3 Registration: The soap.beeps URL Scheme . . . . . . . . . . 15 7.4 Registration: The System (Well-Known) TCP port number for SOAP over BEEP . . . . . . . . . . . . . . . . . . . . . . . 15 8. Security Considerations . . . . . . . . . . . . . . . . . . 16 References . . . . . . . . . . . . . . . . . . . . . . . . . 17 IANA Considerations . . . . . . . . . . . . . . . . . . . . 18 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19 Full Copyright Statement . . . . . . . . . . . . . . . . . . 20 O'Tuathail & Rose Standards Track [Page 2] RFC 3288 Using SOAP in BEEP June 2002 1. Introduction This memo specifies how SOAP 1.1 envelopes[1] are transmitted using a BEEP profile[2]. In the W3C, the XMLP effort is evolving SOAP. Accordingly, this memo provides a mechanism for negotiating the use of new features. Throughout this memo, the term "envelope" refers to the "SOAP- Env:Envelope" element defined in Section 4 of [1]. Further, the terms "peer", "client", "server", "one-to-one", and "one-to-many" are used in the context of BEEP. In particular, Sections 2.1 and 2.1.1 of [2] discuss BEEP roles and exchange styles. O'Tuathail & Rose Standards Track [Page 3] RFC 3288 Using SOAP in BEEP June 2002 2. BEEP Profile Identification The BEEP profile for SOAP is identified as http://iana.org/beep/soap in the BEEP "profile" element during channel creation. In BEEP, when the first channel is successfully created, the "serverName" attribute in the "start" element identifies the "virtual host" associated with the peer acting in the server role, e.g., <start number='1' serverName='stockquoteserver.example.com'> <profile uri='http://iana.org/beep/soap' />Show full document text