[Rtcomm] [Rtcomm] [Bug 4098] New: XMPP server DNS resolution should use SRV lookups

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=4098

           Summary: XMPP server DNS resolution should use SRV lookups
           Product: Chat and Internet Call
           Version: 4.1.3 (5.2008.43-7)
          Platform: All
        OS/Version: Maemo
            Status: NEW
          Severity: enhancement
          Priority: Low
         Component: XMPP
        AssignedTo: rtcomm at maemo.org
        ReportedBy: maemo at subs.maneos.org
         QAContact: xmpp-bugs at maemo.bugs


SOFTWARE VERSION:
5.2008.43-7

STEPS TO REPRODUCE THE PROBLEM:
1. Set up an XMPP account to a service on a domain that publishes SRV records,
but the domain has no A records or has A records that do not offer XMPP.
2. Try to connect to the above service.

Example: For a JID like "foo at gmail.com" the currently published servers are:

$ host -t srv _xmpp-client._tcp.gmail.com
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 talk4.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 5 0 5222 talk.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 talk1.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 talk2.l.google.com.
_xmpp-client._tcp.gmail.com has SRV record 20 0 5222 talk3.l.google.com.

and although there are several A records listed for "gmail.com", they don't
listen on the XMPP port.

EXPECTED OUTCOME:
The XMPP client resolves the SRV records of the service and connects
successfully to one of the published servers.

ACTUAL OUTCOME:
The XMPP client naively only queries AAAA & A records of the domain part of the
JID and the connection will fail unless an A record exists and the host it
points to happens to offer XMPP service on the default XMPP port.

REPRODUCIBILITY:
Always.

EXTRA SOFTWARE INSTALLED:
Various packages, but not rtcomm-beta.

OTHER COMMENTS:
A partial workaround is to specify a server and port explicitly in the Advanced
account setup dialog.  This will work as long as that particular server is
reachable and working, but loses all the advantages of the failover
capabilities built into the protocol.

RFC3920 specifies SRV lookups as a SHOULD, however the next version draft
(currently http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-08.html)
makes them mandatory.  Setting severity to enhancement for now.

Connections to SIP accounts do SRV (and NAPTR) lookups correctly.

According to http://bugzilla.gnome.org/show_bug.cgi?id=150203 this may be 
already fixed upstream, but the links are dead :-(

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.5)
Gecko/2008121623 Ubuntu/8.10 (intrepid) Firefox/3.0.5


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=4098
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.