[JDEV] Jabber server redirection
dwd at bell-labs.com
Mon Feb 25 15:29:16 CST 2002
On Fri, Feb 22, 2002 at 07:39:31PM -0700, David Waite wrote:
> Matthias Wimmer wrote:
> >Hi Dave!
> >On Fri, Feb 22, 2002 at 03:33:49PM -0600, Dave Dykstra wrote:
> >>>It would be no problem to add that to gabber. The only thing is that SRV
> >>>records are only defined for s2s at the moment ... not for c2s.
> >>Ok, what would it take to define them?
> >A sort of an agreement ... a standard for that.
> >>Also, that still doesn't completely solve the problem, as Thomas Parslow
> >>pointed out; I think it would also take a couple more client changes. The
> >>c2s SRV record in the DNS could allow a client to automatically discover
> >>its server name,
> >No ... you don't discover the server name. That you have to know already
> >to make the SRV request. The SRV record only gives priority, host and
> >port for the connection.
> >E.g. if _jabber._tcp.company.com directs you to im.company.com the
> >server name is company.com ... only the host it runs on is
Yes! You're right. The client should use company.com as the server
name. The Microsoft client is doing the wrong thing by making the host
> >We just would have to define the "prefix". Somethink like
> >BTW: Why are the services prefixed by an underscore?
> see http://www.ietf.org/rfc/rfc2052.txt.
Cool! I googled "SRV RR underscore" and found that rfc2052 has been
superceded by rfc2782 which requires the underscore "to prevent collisions
with DNS labels that occur in nature".
> Since we now have
> jabber-client and jabber-server defined by the IANA, it should be
What about SSL client connections on port 5223? Should they be
For implementation, I guess it would make sense to adapt the dnsrv code
from the open source jabber server in the clients. It does look
complicated enough and common enough that it ought to become integrated
into a unix operating system library call; does anybody know of such a
thing in the works? Turning to google again on "rfc 2782 gnu" I find
but it doesn't look to be quite ready to go.
- Dave Dykstra
More information about the JDev