Introduction - Microsoft



[MS-SWSB]: SOAP Over WebSocket Protocol BindingIntellectual Property Rights Notice for Open Specifications DocumentationTechnical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit trademarks. Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.Revision SummaryDateRevision HistoryRevision ClassComments12/16/20111.0NewReleased new document.3/30/20121.0NoneNo changes to the meaning, language, or formatting of the technical content.7/12/20122.0MajorSignificantly changed the technical content.10/25/20122.0NoneNo changes to the meaning, language, or formatting of the technical content.1/31/20132.0NoneNo changes to the meaning, language, or formatting of the technical content.8/8/20132.1MinorClarified the meaning of the technical content.11/14/20132.1NoneNo changes to the meaning, language, or formatting of the technical content.2/13/20142.1NoneNo changes to the meaning, language, or formatting of the technical content.5/15/20142.1NoneNo changes to the meaning, language, or formatting of the technical content.6/30/20153.0MajorSignificantly changed the technical content.10/16/20153.0No ChangeNo changes to the meaning, language, or formatting of the technical content.Table of ContentsTOC \o "1-9" \h \z1Introduction PAGEREF _Toc432489345 \h 41.1Glossary PAGEREF _Toc432489346 \h 41.2References PAGEREF _Toc432489347 \h 41.2.1Normative References PAGEREF _Toc432489348 \h 51.2.2Informative References PAGEREF _Toc432489349 \h 51.3Overview PAGEREF _Toc432489350 \h 51.4Relationship to Other Protocols PAGEREF _Toc432489351 \h 61.5Prerequisites/Preconditions PAGEREF _Toc432489352 \h 61.6Applicability Statement PAGEREF _Toc432489353 \h 61.7Versioning and Capability Negotiation PAGEREF _Toc432489354 \h 61.8Vendor-Extensible Fields PAGEREF _Toc432489355 \h 61.9Standards Assignments PAGEREF _Toc432489356 \h 72Messages PAGEREF _Toc432489357 \h 82.1Transport PAGEREF _Toc432489358 \h 82.2Common Message Syntax PAGEREF _Toc432489359 \h 82.2.1Namespaces PAGEREF _Toc432489360 \h 82.2.2Messages PAGEREF _Toc432489361 \h 82.2.3Elements PAGEREF _Toc432489362 \h 82.2.4Complex Types PAGEREF _Toc432489363 \h 82.2.5Simple Types PAGEREF _Toc432489364 \h 82.2.6Attributes PAGEREF _Toc432489365 \h 82.2.7Groups PAGEREF _Toc432489366 \h 82.2.8Attribute Groups PAGEREF _Toc432489367 \h 92.2.9Common Data Structures PAGEREF _Toc432489368 \h 92.3Directory Service Schema Elements PAGEREF _Toc432489369 \h 93Protocol Details PAGEREF _Toc432489370 \h 103.1Server Details PAGEREF _Toc432489371 \h 103.1.1Abstract Data Model PAGEREF _Toc432489372 \h 103.1.2Timers PAGEREF _Toc432489373 \h 103.1.3Initialization PAGEREF _Toc432489374 \h 103.1.4Message Processing Events and Sequencing Rules PAGEREF _Toc432489375 \h 103.1.5Timer Events PAGEREF _Toc432489376 \h 103.1.6Other Local Events PAGEREF _Toc432489377 \h 103.2Client Details PAGEREF _Toc432489378 \h 103.2.1Abstract Data Model PAGEREF _Toc432489379 \h 113.2.2Timers PAGEREF _Toc432489380 \h 113.2.3Initialization PAGEREF _Toc432489381 \h 113.2.4Message Processing Events and Sequencing Rules PAGEREF _Toc432489382 \h 113.2.5Timer Events PAGEREF _Toc432489383 \h 113.2.6Other Local Events PAGEREF _Toc432489384 \h 114Protocol Examples PAGEREF _Toc432489385 \h 125Security PAGEREF _Toc432489386 \h 135.1Security Considerations for Implementers PAGEREF _Toc432489387 \h 135.2Index of Security Parameters PAGEREF _Toc432489388 \h 136Appendix A: Full WSDL PAGEREF _Toc432489389 \h 147Appendix B: Product Behavior PAGEREF _Toc432489390 \h 158Change Tracking PAGEREF _Toc432489391 \h 169Index PAGEREF _Toc432489392 \h 17Introduction XE "Introduction" XE "Introduction"The SOAP over WebSocket Protocol Binding Specification defines a binding of SOAP to the WebSocket protocol (as defined in [RFC6455]), including a WSDL transport URI and supported message exchange patterns (MEPs). This specification also defines a WebSocket subprotocol. Note This specification does not define any SOAP messages. Rather, it specifies how messages defined by a higher-layer protocol are formed and framed for transport over [RFC6455]. Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in [RFC2119]. Sections 1.5 and 1.9 are also normative but do not contain those terms. All other sections and examples in this specification are informative.Glossary XE "Glossary" The following terms are specific to this document:endpoint: A client that is on a network and is requesting access to a network access server (NAS).SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].SOAP message: An XML document consisting of a mandatory SOAP envelope, an optional SOAP header, and a mandatory SOAP body. See [SOAP1.2-1/2007] section 5 for more information.Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.References XE "References" Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata. Normative References XE "References:normative" XE "Normative references" We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact dochelp@. We will assist you in finding the relevant information. [MC-NBFSE] Microsoft Corporation, ".NET Binary Format: SOAP Extension".[MC-NBFS] Microsoft Corporation, ".NET Binary Format: SOAP Data Structure".[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, [RFC3902] Baker, M., and Nottingham, M., "The 'application/soap+xml' media type", RFC 3902, September 2004, [RFC6455] Fette, I., and Melnikov, A., "The WebSocket Protocol", RFC 6455, December 2011, [SOAP1.2-1/2007] Gudgin, M., Hadley, M., Mendelsohn, N., et al., "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)", W3C Recommendation 27, April 2007, [SOAP1.2-2/2007] Gudgin, M., Hadley, M., Mendelsohn, N., et al., "SOAP Version 1.2 Part 2: Adjuncts (Second Edition)", W3C Recommendation, April 2007, [SOAP1.2-3/2007] W3C, "SOAP 1.2 Part 3: One-Way MEP", W3C Working Group Note 2, July 2007, [WSDLSOAP] Angelov, D., Ballinger, K., Butek, R., et al., "WSDL 1.1 Binding Extension for SOAP 1.2", W3C Member Submission, April 2006, [WSDL] Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S., "Web Services Description Language (WSDL) 1.1", W3C Note, March 2001, [XMLNS-2ED] World Wide Web Consortium, "Namespaces in XML 1.0 (Second Edition)", August 2006, [XMLSCHEMA1] Thompson, H., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, [XMLSCHEMA2] Biron, P.V., Ed. and Malhotra, A., Ed., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, References XE "References:informative" XE "Informative references" None.Overview XE "Overview (synopsis)" XE "Overview (synopsis)"The SOAP over WebSocket Protocol Binding:Specifies a WSDL Transport URI () for identifying this protocol as the transport for sending SOAP 1.2 messages [SOAP1.2-2/2007]. Defines a new WebSocket subprotocol (soap), as described in [RFC6455], which is used by the client to indicate to the service that it intends to use the SOAP-over-WebSockets protocol for message exchange.Defines two new HTTP headers ('soap-content-type' and 'microsoft-binary-transfer-mode') that are used by the client during the initial WebSocket handshake to indicate the SOAP content-type and the transfer-mode of the subsequent messages.Relationship to Other Protocols XE "Relationship to other protocols" XE "Relationship to other protocols"The SOAP over WebSocket Protocol Binding uses the WebSocket protocol, as described in [RFC6455], as the transport. The SOAP over WebSocket Protocol Binding uses WebSocket framing as defined in section 5 of [RFC6455] to send SOAP 1.2 messages [SOAP1.2-2/2007].The following figure shows the protocol stack.Figure 1: Protocol stackPrerequisites/Preconditions XE "Prerequisites" XE "Preconditions" XE "Preconditions" XE "Prerequisites"The SOAP over WebSocket Protocol Binding requires that a client can connect to the service over the WebSocket protocol, as described in [RFC6455].Applicability Statement XE "Applicability" XE "Applicability"The SOAP over WebSocket Protocol Binding is applicable in scenarios where a client and a service require a communication mechanism to send and receive SOAP messages over WebSocket ([RFC6455]).Versioning and Capability Negotiation XE "Versioning" XE "Capability negotiation" XE "Capability negotiation" XE "Versioning"This document covers versioning issues in the following areas:Supported transports: This protocol requires WebSocket ([RFC6455]) as the transport. Protocol versions: The use of SOAP version 1.2 [SOAP1.2-1/2007] is required.Capability negotiation: This protocol does not support negotiation of the version or the capabilities to use.Vendor-Extensible Fields XE "Vendor-extensible fields" XE "Fields - vendor-extensible" XE "Fields - vendor-extensible" XE "Vendor-extensible fields"This protocol has no vendor-extensible fields.Standards Assignments XE "Standards assignments" XE "Standards assignments"There are no standards assignments for this protocol.MessagesTransport XE "Messages:transport" XE "Transport" XE "Transport" XE "Messages:transport"The SOAP over WebSocket Protocol Binding requires the WebSocket transport protocol (as specified in [RFC6455]).A service endpoint that uses the SOAP over WebSocket Protocol Binding with SOAP 1.2 [SOAP1.2-1/2007] MUST set the value of the transport attribute of the wsoap12:binding element [WSDLSOAP] to Message Syntax XE "Messages:syntax" XE "Syntax: messages - overview" XE "Syntax:messages - overview" XE "Messages:syntax"This section contains common definitions used by this protocol. The syntax of the definitions uses XML schema as defined in [XMLSCHEMA1] and [XMLSCHEMA2], and Web Services Description Language (WSDL) as defined in [WSDL].Namespaces XE "Messages:namespaces" XE "Namespaces" XE "Namespaces" XE "Messages:namespaces"This specification defines and references various XML namespaces using the mechanisms specified in [XMLNS-2ED]. Although this specification associates a specific XML namespace prefix for each XML namespace that is used, the choice of any particular XML namespace prefix is implementation-specific and not significant for interoperability.PrefixNamespace URIReferencesoap12 [WSDLSOAP] wsdl [WSDL] Messages XE "Messages:enumerated" XE "Messages:enumerated"This specification does not define any common XML schema message definitions.Elements XE "Messages:elements" XE "Messages:elements"This specification does not define any common XML schema element plex Types XE "Messages:complex types" XE "Complex types" XE "Types:complex" XE "Types:complex" XE "Complex types" XE "Messages:complex types"This specification does not define any common XML schema complex type definitions.Simple Types XE "Messages:simple types" XE "Simple types" XE "Types:simple" XE "Types:simple" XE "Simple types" XE "Messages:simple types"This specification does not define any common XML schema simple type definitions.Attributes XE "Messages:attributes" XE "Attributes" XE "Attributes" XE "Messages:attributes"This specification does not define any common XML schema attribute definitions.Groups XE "Messages:groups" XE "Groups" XE "Groups" XE "Messages:groups"This specification does not define any common XML schema group definitions.Attribute Groups XE "Messages:attribute groups" XE "Attribute groups" XE "Attribute groups" XE "Messages:attribute groups"This specification does not define any common XML schema attribute group mon Data Structures XE "Messages:common data structures" XE "Common data structures" XE "Messages:data structures" XE "Data structures"This specification does not define any common XML schema data structures.Directory Service Schema Elements XE "Elements - directory service schema" XE "Directory service schema elements" XE "Schema elements - directory service" XE "Schema elements - directory service" XE "Directory service schema elements" XE "Elements - directory service schema"None.Protocol DetailsServer DetailsA service endpoint MUST support the following message exchange patterns: (defined in [SOAP1.2-2/2007]) (defined in [SOAP1.2-3/2007])Abstract Data Model XE "Server:abstract data model" XE "Abstract data model:server" XE "Data model - abstract:server" XE "Data model - abstract:server" XE "Abstract data model:server" XE "Server:abstract data model"None.Timers XE "Server:timers" XE "Timers:server" XE "Timers:server" XE "Server:timers"None.Initialization XE "Server:initialization" XE "Initialization:server" XE "Initialization:server" XE "Server:initialization"None.Message Processing Events and Sequencing Rules XE "Server:message processing" XE "Message processing:server" XE "Server:sequencing rules" XE "Sequencing rules:server" XE "Sequencing rules:server" XE "Server:sequencing rules" XE "Message processing:server" XE "Server:message processing"None.Timer Events XE "Server:timer events" XE "Timer events:server" XE "Events:timer - server" XE "Events:timer - server" XE "Timer events:server" XE "Server:timer events"None.Other Local Events XE "Server:local events" XE "Local events:server" XE "Events:local - server" XE "Events:local - server" XE "Local events:server" XE "Server:local events"None.Client DetailsA client initiates the process by establishing a WebSocket connection, as specified in [RFC6455], to a service. A client MUST specify that it intends to communicate with the service using this SOAP-over-Websocket subprotocol by providing a "soap" value in the "Sec-WebSocket-Protocol" HTTP header during the initialization while performing a WebSocket handshake as specified in [RFC6455] section 1.3. A client MUST also specify a soap-content-type header to indicate the content-type of the subsequent SOAP messages once the WebSocket handshake is successfully completed. A client SHOULD also specify a 'microsoft-binary-transfer-mode' with the transfer-mode while using the binary encoding as specified in [MC-NBFS] or [MC-NBFSE]. Valid values for the transfer-mode are: 'Streamed', which indicates that messages sent and received from the web service endpoint are transferred as a stream of bytes.'StreamedRequest', which indicates that only the messages sent to a web service endpoint are transferred as a stream of bytes.'StreamedResponse', which indicates that the messages received from the web service endpoint are interpreted as a stream of bytes.Once a WebSocket connection has been successfully established between the client and the server, all subsequent message exchanges MUST conform to the SOAP 1.2 [SOAP1.2-1/2007] specification with the encoding as specified in [RFC3902] while sending the messages using the framing as defined in [RFC6455]. Abstract Data Model XE "Client:abstract data model" XE "Abstract data model:client" XE "Data model - abstract:client" XE "Data model - abstract:client" XE "Abstract data model:client" XE "Client:abstract data model"None.Timers XE "Client:timers" XE "Timers:client" XE "Timers:client" XE "Client:timers"None.Initialization XE "Client:initialization" XE "Initialization:client" XE "Initialization:client" XE "Client:initialization"None.Message Processing Events and Sequencing Rules XE "Client:message processing" XE "Message processing:client" XE "Client:sequencing rules" XE "Sequencing rules:client" XE "Sequencing rules:client" XE "Client:sequencing rules" XE "Message processing:client" XE "Client:message processing"None.Timer Events XE "Client:timer events" XE "Timer events:client" XE "Events:timer - client" XE "Events:timer - client" XE "Timer events:client" XE "Client:timer events"None.Other Local Events XE "Client:local events" XE "Local events:client" XE "Events:local - client" XE "Events:local - client" XE "Local events:client" XE "Client:local events"None.Protocol Examples XE "Examples"Section 6, Appendix A: Full WSDL, specifies the SOAP over WebSocket Binding Transport URI defined in this document.The following HTTP headers section is an example of the WebSocket subprotocol defined by this specification:GET HTTP/1.1Connection: Upgrade,Keep-AliveUpgrade: websocketSec-WebSocket-Key: ROOw9dYOJkStW2nx5r1k9w==Sec-WebSocket-Version: 13Sec-WebSocket-Protocol: soapsoap-content-type: application/soap+msbinsession1microsoft-binary-transfer-mode: BufferedAccept-Encoding: gzip, deflate HTTP/1.1 101 Switching ProtocolsUpgrade: websocketConnection: UpgradeSec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=Sec-WebSocket-Protocol: soapSecuritySecurity Considerations for Implementers XE "Security:implementer considerations" XE "Implementer - security considerations" XE "Implementer - security considerations" XE "Security:implementer considerations"Security considerations are discussed in detail under the security considerations section (section 10) in [RFC6455]. There are no special security considerations for this protocol.Index of Security Parameters XE "Security:parameter index" XE "Index of security parameters" XE "Parameters - security index" XE "Parameters - security index" XE "Index of security parameters" XE "Security:parameter index"None.Appendix A: Full WSDL XE "WSDL" XE "Full WSDL" XE "Full WSDL" XE "WSDL"The following WSDL specifies the WSDL 1.1 binding extension transport URI with SOAP1.2:WSDL 1.1 binding extension transport URI with SOAP 1.2 [SOAP1.2-2/2007]<?xml version="1.0" encoding="utf-8"?><wsdl:definitions xmlns:wsdl="" xmlns:soap12=""> <!-- omitted elements --> <wsdl:binding name="MyBinding" type="MyPortType"> <!-- omitted elements --> <soap12:binding transport=""/> <wsdl:operation name="MyOperation"> <!-- ommitted elements --> </wsdl:operation> </wsdl:binding> <wsdl:service name="MyService"> ?? <wsdl:port name="MyPort" binding="MyBinding"> <soap12:address location=" ws://myHost/myService/" /> </wsdl:port> </wsdl:service> </wsdl:definitions>Appendix B: Product Behavior XE "Product behavior" The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.This document specifies version-specific details in the Microsoft .NET Framework. For information about which versions of the .NET Framework are available in each released Windows product or as supplemental software, see [MS-NETOD] section 4.Note: Some of the information in this section is subject to change because it applies to a preliminary product version, and thus may differ from the final version of the software when released. All behavior notes that pertain to the preliminary product version contain specific references to it as an aid to the reader. Microsoft .NET Framework 4.5Microsoft .NET Framework 4.6Windows 8 operating systemWindows Server 2012 operating systemWindows 8.1 operating systemWindows Server 2012 R2 operating systemWindows 10 operating systemWindows Server 2016 Technical Preview operating system Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.Change Tracking XE "Change tracking" XE "Tracking changes" No table of changes is available. The document is either new or has had no changes since its last release.IndexAAbstract data model client PAGEREF section_2b6bb1f820b84c3a8b1845ecba2273ad11 server PAGEREF section_17e26ab3fcfc43589d05934e7908828610Applicability PAGEREF section_4901400eb99e4eec885bac0924a761316Attribute groups PAGEREF section_1a0eb81f2b1045fd9dd949c801a6e4399Attributes PAGEREF section_9a9789e8f95943b8bbb946ce765a425d8CCapability negotiation PAGEREF section_f60dc939fb3c45138856d1351764defd6Change tracking PAGEREF section_fb1a2b812d144901ab4f13c0c8d3c34c16Client abstract data model PAGEREF section_2b6bb1f820b84c3a8b1845ecba2273ad11 initialization PAGEREF section_54b48625359c4482ba41cde2184e3ca211 local events PAGEREF section_8db8a78be7264dfa80e88b9bf2359e1d11 message processing PAGEREF section_11463eb662f5488ba7a7d5f95780304511 sequencing rules PAGEREF section_11463eb662f5488ba7a7d5f95780304511 timer events PAGEREF section_32fda5b03a694c549c4edae6c0956a4a11 timers PAGEREF section_7250624f7c82434e9e7acda91cbab22411Common data structures PAGEREF section_942c9ba6a01747449e86702ed76ee5279Complex types PAGEREF section_8351bf7313504971bb4e17790d4ce3088DData model - abstract client PAGEREF section_2b6bb1f820b84c3a8b1845ecba2273ad11 server PAGEREF section_17e26ab3fcfc43589d05934e7908828610Data structures PAGEREF section_942c9ba6a01747449e86702ed76ee5279Directory service schema elements PAGEREF section_e4b489dfcbb54d6cb7b36102f8566e3c9EElements - directory service schema PAGEREF section_e4b489dfcbb54d6cb7b36102f8566e3c9Events local - client PAGEREF section_8db8a78be7264dfa80e88b9bf2359e1d11 local - server PAGEREF section_6cff99a5af5d480ca0cf3da9a18e617910 timer - client PAGEREF section_32fda5b03a694c549c4edae6c0956a4a11 timer - server PAGEREF section_7b24380b00d8430a9d69407bcddd0da110Examples PAGEREF section_e1fe956031f54680aa27f61a37c8536112FFields - vendor-extensible PAGEREF section_87173c91fcee4fdcb7e6e81bd3da90066Full WSDL PAGEREF section_10a0ed2b76374f61933fae0f126b4a8314GGlossary PAGEREF section_e6cc9737233c47b7b4b9345de3e7a0b24Groups PAGEREF section_d87d8df5f8f84074872be1cef07941598IImplementer - security considerations PAGEREF section_472d4f2d8c364638aedabb06d818b2e213Index of security parameters PAGEREF section_8933cb288e484a8f83d8323039f702d913Informative references PAGEREF section_5f1f1c32f683483c83c7ea866c2d3b015Initialization client PAGEREF section_54b48625359c4482ba41cde2184e3ca211 server PAGEREF section_57ed18ba78824b139a6538abff02eb7110Introduction PAGEREF section_64b46e311ff948828b2aae9756e7bbb64LLocal events client PAGEREF section_8db8a78be7264dfa80e88b9bf2359e1d11 server PAGEREF section_6cff99a5af5d480ca0cf3da9a18e617910MMessage processing client PAGEREF section_11463eb662f5488ba7a7d5f95780304511 server PAGEREF section_bdb57c3d46eb4fe68fb37038ed02a2ed10Messages attribute groups PAGEREF section_1a0eb81f2b1045fd9dd949c801a6e4399 attributes PAGEREF section_9a9789e8f95943b8bbb946ce765a425d8 common data structures PAGEREF section_942c9ba6a01747449e86702ed76ee5279 complex types PAGEREF section_8351bf7313504971bb4e17790d4ce3088 data structures PAGEREF section_942c9ba6a01747449e86702ed76ee5279 elements PAGEREF section_8b5af41f3cb34fff8ce363f5abf00db48 enumerated PAGEREF section_24bf740c78e84b6d932c3f985979c1ff8 groups PAGEREF section_d87d8df5f8f84074872be1cef07941598 namespaces PAGEREF section_7fbcdd3e8b804481b172a9d6374419af8 simple types PAGEREF section_085c60e7b0bd4ec68340957f75d595ae8 syntax PAGEREF section_12ab875d34f541df8df36f5852a040c58 transport PAGEREF section_0fc8968d230d44cb9aeaf54e8795adf18NNamespaces PAGEREF section_7fbcdd3e8b804481b172a9d6374419af8Normative references PAGEREF section_19c9f815f6f34ec1bf3d63236de092225OOverview (synopsis) PAGEREF section_5867828f4b8b41579efa15805af5e9485PParameters - security index PAGEREF section_8933cb288e484a8f83d8323039f702d913Preconditions PAGEREF section_c692f96e52be47f29bbee4ccc32c0d1c6Prerequisites PAGEREF section_c692f96e52be47f29bbee4ccc32c0d1c6Product behavior PAGEREF section_5f41a963b3c74ed19dd5ae07cb11b1ff15RReferences PAGEREF section_ed52d1fe26644b27a0314a54d01b38644 informative PAGEREF section_5f1f1c32f683483c83c7ea866c2d3b015 normative PAGEREF section_19c9f815f6f34ec1bf3d63236de092225Relationship to other protocols PAGEREF section_b93290b29ae94bd6818a9db6994100be6SSchema elements - directory service PAGEREF section_e4b489dfcbb54d6cb7b36102f8566e3c9Security implementer considerations PAGEREF section_472d4f2d8c364638aedabb06d818b2e213 parameter index PAGEREF section_8933cb288e484a8f83d8323039f702d913Sequencing rules client PAGEREF section_11463eb662f5488ba7a7d5f95780304511 server PAGEREF section_bdb57c3d46eb4fe68fb37038ed02a2ed10Server abstract data model PAGEREF section_17e26ab3fcfc43589d05934e7908828610 initialization PAGEREF section_57ed18ba78824b139a6538abff02eb7110 local events PAGEREF section_6cff99a5af5d480ca0cf3da9a18e617910 message processing PAGEREF section_bdb57c3d46eb4fe68fb37038ed02a2ed10 sequencing rules PAGEREF section_bdb57c3d46eb4fe68fb37038ed02a2ed10 timer events PAGEREF section_7b24380b00d8430a9d69407bcddd0da110 timers PAGEREF section_2d89f6bd3da84eae90c8113b2595639410Simple types PAGEREF section_085c60e7b0bd4ec68340957f75d595ae8Standards assignments PAGEREF section_c1eb0021db504b72b2d6569ce8db70427Syntax messages - overview PAGEREF section_12ab875d34f541df8df36f5852a040c58TTimer events client PAGEREF section_32fda5b03a694c549c4edae6c0956a4a11 server PAGEREF section_7b24380b00d8430a9d69407bcddd0da110Timers client PAGEREF section_7250624f7c82434e9e7acda91cbab22411 server PAGEREF section_2d89f6bd3da84eae90c8113b2595639410Tracking changes PAGEREF section_fb1a2b812d144901ab4f13c0c8d3c34c16Transport PAGEREF section_0fc8968d230d44cb9aeaf54e8795adf18Types complex PAGEREF section_8351bf7313504971bb4e17790d4ce3088 simple PAGEREF section_085c60e7b0bd4ec68340957f75d595ae8VVendor-extensible fields PAGEREF section_87173c91fcee4fdcb7e6e81bd3da90066Versioning PAGEREF section_f60dc939fb3c45138856d1351764defd6WWSDL PAGEREF section_10a0ed2b76374f61933fae0f126b4a8314 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download