[Standards] [Council] component-s2s
kurt.zeilenga at isode.com
Fri Feb 27 15:23:06 UTC 2015
> On Feb 27, 2015, at 7:09 AM, Kurt Zeilenga <kurt.zeilenga at isode.com> wrote:
> Maybe we’re got the wrong model here…
> Consider the model where an XMPP server C wants to service XMPP requests for domain D which another service hosts. That is, this hosting service is what the DNS records of H point to, hence I’ll call this H.
> C connects to “H” (the host) as “C” using S2S and then can ask “I’d like to takeover servicing of ‘H’’. Upon acceptance, any stanza addressed to “H” which “H” receives is forwarded (using XEP 297 extension) to C for servicing. C responds using the 297 as well.
and if you want connections to made in the reverse direction, H can have config info (possibly in DNS) that says C is to service H traffic. In this case, H connects to C, authenticates, and asks C if will take over H. Then traffic flows as in above case.
> Just food for thought…
> — Kurt
More information about the Standards