Unlike for XMPP connections via TCP as specified in &rfc6120;, there exists no specificiation of implicit connection endpoints for XMPP over WebSocket (&rfc7395;). As a result, XMPP services which whish to provide WebSocket connectivity need to announce their WebSocket endpoints, so that clients are able to discover them (RFC 7395 § 4). This XEP fills this gap. It eventually enables, under certain conditions, XMPP services to provide WebSocket connectivty, without resorting to &xep0156; nor requiring manual configuration by the user.

The following implicit XMPP WebSocket endpoints are specified:

• wss://<xmpp-service-name>:5443/ws
• ws://<xmpp-service-name>:5443/ws
• wss://<xmpp-service-name>/ws
• ws://<xmpp-service-name>/ws

TODO: Use implicit endpoints only if no other endpoints were discovered?

Implementations should note that due this XEP, the collection of potential endpoints may contain duplicates. This is because the implicit WebSocket connection endpoints defined herein may match the ones that where discovered (RFC 7395 § 4, XEP-0156). Implementations may want to ensure that no such duplicates exist.

Furthermore, implementations attempting to connect to the discovered endpoints serially, as opposed to concurrently, may use the implicit endpoints only as last resort.

Since the implicit WebSocket connection endpoints are defined to include the XMPP service name, the verification required when using the secured variant of the WebSocket transport provides the necessary security.

This document requires no interaction with &IANA;.

This document requires no interaction with the XMPP registrar.

No XML schema specification is required, as this XEP does not specify any XML data.