Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org> Subject: Protocol Action: 'Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)' to Proposed Standard The IESG has approved the following document: - 'Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) ' <draft-mrose-rfc3288bis-03.txt> as a Proposed Standard This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Scott Hollenbeck. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mrose-rfc3288bis-03.txt
Technical Summary 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. If approved, this document obsoletes RFC 3288. Working Group Summary This document is the work of individual submitters. It was subjected to a 4-week IETF last call. Last call comments were addressed prior to IESG review. Protocol Quality Scott Hollenbeck has reviewed this specification for the IESG. RFC Editor Note In section 6.1.1, please change IP address "10.0.0.2" to "192.0.2.0" to conform to the conventions described in RFC 3330.