[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FW: Protocol Action: 'Using the Simple Object Access Protocol (S OAP) in Blocks Extensible Exchange Protocol (BEEP)' to Proposed Standard
- To: "Netconf (E-mail)" <netconf@ops.ietf.org>
- Subject: FW: Protocol Action: 'Using the Simple Object Access Protocol (S OAP) in Blocks Extensible Exchange Protocol (BEEP)' to Proposed Standard
- From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
- Date: Tue, 17 May 2005 18:25:07 +0200
I believe this WG had a dependency on this update,
so here it is.
Bert
-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org]On Behalf Of The IESG
Sent: Tuesday, May 17, 2005 01:05
To: IETF-Announce
Cc: Internet Architecture Board; RFC Editor
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-02.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.
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.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>