Ralph Meijer <jabber.org <at> ralphm.ik.nu>
2005-10-28 09:50:17 GMT
On Thu, Oct 20, 2005 at 02:04:09PM +0100, Tony Finch wrote:
> [sorry if this is the wrong list for this kind of question]
> I'm trying to get to grips with jabber, so I've read the XMPP RFCs. I was
> puzzled by the special case handling for subdomains which is written into
> the specs (especially section 10 of RFC 3920). The assumption seems to be
> that the service provided by a subdomain is intimately tied to the service
> provided by the domain itself. This assumption can be wrong.
> I would have thought that the restriction is unnecessary. It would seem
> simpler to just treat domains as opaque strings, which the server either
> knows how to handle locally (either processing stanzas itself or passing
> them to a specialized service), or routes routes stanzas to in the usual
> s2s way.
> Section 10.3 seems to prevent a large organization from having both an
> organization-wide jabber server and departmental servers. For example, if
> I set up a jabber server at cam.ac.uk then that server is required to
> consider all subdomains of cam.ac.uk to be its responsibility. This
> prevents a department from setting up their own jabber server (e.g.
> because they want closer integration with their departmental email server)
> without co-operation from me and extra configuration of my server.
> Have I understood this part of the protocol correctly? Is this how
> server implementations work in practice?
If you have deployed a company wide and some departmental servers the
stanzas destined for those departmental servers would be delivered
directly to them by the origin server, based on DNS.