On Wed, Sep 9, 2009 at 11:10 PM, Peter Saint-Andre <[email protected]> wrote: > *** > > Unfortunately, the notion of a subdomain was never really defined -- it > basically meant that you added another domain part to the left-hand side > of a server JID, such as foo.example.com if the XMPP server is hosted at > example.com or bar.im.example.net if the XMPP server is hosted at > im.example.net. Yet we don't really know if what looks like a subdomain > really is associated with a given XMPP server. So for instance there > might be one XMPP server running at example.net and an entirely > different XMPP server running at im.example.net. A long-running example > is provided by jabber.com because there is also a server corp.jabber.com > for employees (well, they now work for Cisco but you see what I mean!), > and corp.jabber.com might look like a "subdomain" of jabber.com but in > practice it is not. This is why we removed the notion of a subdomain > from rfc3920bis.
Well I think there is a way to define the difference using SRV records: if there is one we should consider it separate domain (even if it should point to the same host of the main domain, since they must be virtual hosts) > Similarly, I suggest that we remove it from the JID > matching rules in XEP-0016, XEP-0045, etc. > > Objections? No, since all the cases where we may need the concept of subdomain could be solved at application level with other extensions (e.g. I'm thinking of a case we worked on time ago where we had to consider a subdomain trusted and autoaccept all subscribe from that subdomain) -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: [email protected]
