idnits 2.17.1 draft-etal-beep-soap-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3288 5 Title: Using the Simple Object Access Protocol (SOAP) in 6 Blocks Extensible Exchange Protocol (BEEP) 7 Author(s): E. O'Tuathail, M. Rose 8 Status: Standards Track 9 Date: June 2002 10 Mailbox: eamon.otuathail@clipcode.com, 11 mrose@dbc.mtview.ca.us 12 Pages: 20 13 Characters: 27434 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-etal-beep-soap-06.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3288.txt 20 This memo specifies a Simple Object Access Protocol (SOAP) binding to 21 the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding 22 describes how SOAP messages are transmitted in the 23 network. 25 The SOAP is an XML-based (extensible markup language) messaging 26 protocol used to implement a wide variety of distributed messaging 27 models. It defines a message format and describes a variety of 28 message patterns, including, but not limited to, RPC, asynchronous 29 event notification, unacknowledged messages, and forwarding via SOAP 30 intermediaries. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.