From 8b7a844d586257c6e572c56db6372d684f930539 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 7 May 2007 17:03:54 +0000 Subject: [PATCH] RFC 4227 obsoletes RFC 3288 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@812 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0072.xml | 4 ++-- xep.ent | 1 + 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/xep-0072.xml b/xep-0072.xml index 5bc6a4a2..9505ff4d 100644 --- a/xep-0072.xml +++ b/xep-0072.xml @@ -353,7 +353,7 @@ Alternate Transports - Send SOAP XML plus binary data over alternate transports such as WS-Attachments WS-Attachments <http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt> (work in progress). or SOAP-over-BEEP as defined in &rfc3288;. + Send SOAP XML plus binary data over alternate transports such as WS-Attachments WS-Attachments <http://www.watersprings.org/pub/id/draft-nielsen-dime-soap-01.txt> (work in progress). or SOAP-over-BEEP as defined in &rfc4227;. SHOULD NOT These methods are just other transport protocols and would needlessly complicate implementations of SOAP over XMPP. @@ -624,7 +624,7 @@ -

Section 4 of &w3soap1; defines a SOAP Protocol Binding Framework; two instantiations of that framework are the SOAP HTTP Binding (specified in Section 7 of &w3soap2;) and the &w3soapemail;. (Additionally, a binding to BEEP is described in RFC 3288.) As an alternative to the HTTP and Email bindings, this section formally defines the SOAP XMPP Binding in accordance with the SOAP Protocol Binding Framework.

+

Section 4 of &w3soap1; defines a SOAP Protocol Binding Framework; two instantiations of that framework are the SOAP HTTP Binding (specified in Section 7 of &w3soap2;) and the &w3soapemail;. (Additionally, a binding to BEEP is described in RFC 4227.) As an alternative to the HTTP and Email bindings, this section formally defines the SOAP XMPP Binding in accordance with the SOAP Protocol Binding Framework.

Note: The SOAP XMPP Binding is optional, and SOAP nodes are not required to implement it. A SOAP node that correctly and completely implements the SOAP XMPP Binding as described herein may be said to "conform to the SOAP 1.2 XMPP Binding".

The SOAP XMPP Binding is identified by the following URI:

diff --git a/xep.ent b/xep.ent index 03427bc0..d80e8c34 100644 --- a/xep.ent +++ b/xep.ent @@ -396,6 +396,7 @@ RFC 4032 RFC 4032: Update to the Session Initiation Protocol (SIP) Preconditions Framework <http://tools.ietf.org/html/rfc4032>." > RFC 4119 RFC 4119: A Presence-based GEOPRIV Location Object Format <http://tools.ietf.org/html/rfc4119>." > RFC 4122 RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace <http://tools.ietf.org/html/rfc4122>." > +RFC 4227 RFC 4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) <http://tools.ietf.org/html/rfc4227>." > RFC 4251 RFC 4251: The Secure Shell (SSH) Protocol Architecture <http://tools.ietf.org/html/rfc4251>." > RFC 4252 RFC 4252: The Secure Shell (SHS) Authentication Protocol <http://tools.ietf.org/html/rfc4252>." > RFC 4253 RFC 4253: The Secure Shell (SSH) Transport Layer Protocol <http://tools.ietf.org/html/rfc4253>." >