Re: RFC 3861, SRV handling

Joe,

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.

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

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.

-Justin

On Wednesday 02 February 2005 11:21 am, Joe Hildebrand wrote:
> The way we envisioned interop, as specified in RFC 3922, Section 3.3, is
> for your XMPP client to turn the im: address into a JID, then process as
> usual. No SRV processing is then done on the client side.

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