THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Initiating XMPP server (IS) attempts to look up the SRV record(s) for
_xmpp-server._tcp.other.com
(OS). - If the lookup succeeds, proceed to step 5.
- If the lookup fails, attempt an A record lookup for other.com
- If the lookup succeeds, proceed to step 5, otherwise go to step 13.
- IS connects to the XMPP server OS and initiates XMPP discovery.
- If OS supports XMPP discovery, IS enumerates services, one item of which is hopefully "category: collaboration, type: google-wave". The enumerated item is available on a jid, e.g. "waveservice.other.com".
- If IS finds the disco record, and the provided jid does not match the hostname of the existing connection, it will attempt to resolve the provided jid via the regular XMPP SRV record lookup e.g.
_xmpp-server._tcp.waveservice.other.com
or the A record fallback e.g.waveservice.other.com
. - If step 7 succeeds, proceed to step 12, otherwise goto step 9.
- If OS does not support XMPP discovery, or does not return a discovery item for "google-wave", or the lookup on the discovery item failed, IS will make a guess at a service jid by adding "wave." to the remote domain name, e.g. "wave.other.com".
- IS will attempt to resolve the guessed "wave" jid via the regular XMPP SRV record lookup e.g.
_xmpp-server._tcp.wave.other.com
or the A record fallback e.g.wave.other.com
. - If the lookup succeeds, and the IP or port is different to the connection established in 5. above, connect to the new IP/port. If the lookup fails, goto step 13.
- IS and OS are ready to establish TLS. Stop.
- Failed to establish a connection. Stop.
Background
Anchor | ||||
---|---|---|---|---|
|
SRV Settings
In order to expose a federation server, you require SRV records that describe which servers and ports that the incoming connection should use.
...