Subject: Support for XEP 114 and XEP 225
I,
For performance reason, the best choice to our developement is to design its as a Jabber component. It is like a subdomain and decrease the XMPP server load.
However, there are a number of perceived limitations with that protocol:
· It does not support Transport Layer Security (TLS; see RFC 5246 [2]) for channel encryption.
· It does not support the Simple Authentication and Security Layer (SASL; see RFC 4422 [3]) for authentication.
To add the TLs and SASL authentication another XEP is existing: XEP-0225 - Component Connections: http://xmpp.org/extensions/xep-0225.html TLS and SASL are supported for XEP-0225.
Is Matrix compatible with the XEP 0225 , for the transport and authentication ?
Thks,
For performance reason, the best choice to our developement is to design its as a Jabber component. It is like a subdomain and decrease the XMPP server load.
However, there are a number of perceived limitations with that protocol:
· It does not support Transport Layer Security (TLS; see RFC 5246 [2]) for channel encryption.
· It does not support the Simple Authentication and Security Layer (SASL; see RFC 4422 [3]) for authentication.
To add the TLs and SASL authentication another XEP is existing: XEP-0225 - Component Connections: http://xmpp.org/extensions/xep-0225.html TLS and SASL are supported for XEP-0225.
Is Matrix compatible with the XEP 0225 , for the transport and authentication ?
Thks,