Norman Rasmussen wrote:
The reason why i think TXT records should be authoritative (if they exist), is that it's a nice way for a server admin to say: 'don't try tcp, it won't work'. It would save the client the SRV lookup (two if the legacy jabber service is checked), plus the 'default port' connection attempt.
The whole point of the TXT records is to advertise the URLs for HTTP connection methods, which we can't do with SRV since it disallows the DNS u-line. As described in the introduction, the other methods of doing that are pretty heavy (NAPTR, WSDL) so TXT records were the most lightweight approach. But SRV should be authoritive for the stuff it handles (standard XMPP port lookups) and TXT should supplement that for non-standard connection methods.
The bonus/problem with this is that the DNS admin MUST add the tcp record, otherwise tcp will not be used. (This is not really a bad-thing(tm))
Not sure I follow you there, but I do agree that we need to better specify the order of lookups and which records are authoritative for which connection methods (SRV vs. TXT).
Peter
smime.p7s
Description: S/MIME Cryptographic Signature
