Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000008627D
Original Publication Date: 2002-Jun-01
Included in the Prior Art Database: 2002-Jun-28
Document File: 21 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. O'Tuathail: AUTHOR [+2]

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 13% of the total text.

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 S...