RE: RFC 3861, SRV handling

> Certainly, but what I'm talking about is the server.  Do the 
> RFC 3861 rules apply to delivery between XMPP servers?  It 
> seems to me that the compliant way would be for an XMPP 
> server to first use the RFC 3861 SRV lookup to determine if 
> the destination address supports XMPP.  If that fails, then 
> another protocol (like SIMPLE) could be queried for.  
> However, no existing XMPP servers operate this way, as far as 
> I know, even for those that just support XMPP.

We're shipping one in a couple of weeks.

> So what's the deal here?  Why is the RFC 3861 SRV procedure 
> being ignored?

Because it wasn't needed.

> It seems to me that one of the following has to be true:
> 
> 1) The RFC 3861 SRV procedure is the right way, and XMPP-Core 
> is wrong.
> 
> 2) The XMPP-Core SRV procedure supercedes the RFC 3861 SRV 
> procedure (and therefore the RFC 3861 SRV procedure is wrong, 
> at least within the context of delivering to an XMPP target).
> 
> 3) Both are to be used, perhaps by doing the RFC 3861 SRV 
> lookup first to determine if the destination supports XMPP, 
> followed by doing the XMPP-Core SRV procedure on the result 
> of the RFC 3861 lookup.
> 
> In other words, one, the other, or both.  I guess 'none' is 
> the logical fourth option, but that wouldn't make any sense.
> 
> So, which is it?  Certainly #1 is false, so it has to be #2 
> or #3.  My money's on #2.

4) Try _xmpp._tcp, then try the RFC 3861 rules, or just look up _simple._tcp
(or _sip._tcp, I suppose).  If you want the receiving server to express a
preference, when implementing more than one, you could use S-NAPTR (RFC
3958).

This is pretty close to #2.


Confidentiality Note: 
This email is intended only for the use of the individual or entity to which
it is addressed and may contain information that is privileged, confidential
and exempt from disclosure under applicable law. If the reader of this email
message is not the intended recipient, or the employee or agent responsible
for delivery of the message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is prohibited. If you have received this email in error,
please notify Jabber, Inc. immediately by telephone at +303-308-3231.

  [reminder: [email protected] for non-technical discussions, please]