diff --git a/inbox/websocket-s2s.xml b/inbox/websocket-s2s.xml new file mode 100644 index 00000000..778a232b --- /dev/null +++ b/inbox/websocket-s2s.xml @@ -0,0 +1,69 @@ + + +%ents; +]> + + +
+ WebSocket S2S + This specification defines a procedure to make s2s XMPP connections over WebSocket. + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + XEP-0156 + + + + NOT_YET_ASSIGNED + + Travis + Burtrum + travis@burtrum.org + travis@burtrum.org + + + 0.0.1 + 2022-06-13 + tjb +

First draft.

+
+
+ +

&rfc7395; specifies how to make c2s connections over WebSocket. This XEP extends that to also support s2s connections over WebSocket.

+
+ +

Everything mentioned in &rfc7395; should be followed with the following changes:

+
    +
  1. Connection details are discovered by using &xep0156;
  2. +
  3. For c2s, &rfc7395; requires replacing the 'jabber:client' namespace with 'urn:ietf:params:xml:ns:xmpp-framing', for s2s, the 'jabber:server' namespace should be replaced with 'urn:ietf:params:xml:ns:xmpp-framing-server'.
  4. +
  5. wss (TLS) upgraded to a MUST be used, therefore SASL EXTERNAL authentication can be used as defined in &xmppcore;
  6. +
+
+ +

Some hosting services only allow HTTPS proxies to access servers, meaning federating XMPP servers cannot be ran on these hosts unless s2s is accessible over HTTPS.

+
+ +

Identical to RFC 7395 Security Considerations.

+
+ + +

A URN sub-namespace for framing of s2s Extensible Messaging and Presence + Protocol (XMPP) streams is defined as follows.

+ +

URI: urn:ietf:params:xml:ns:xmpp-framing-server

+ +

Specification: this document

+ +

Registrant Contact: IESG <iesg@ietf.org>

+ +
+ +

This document requires no interaction with the ®ISTRAR;.

+
+