RE: RFC 3861, SRV handling

Joe Hildebrand <[email protected]> Wed, 2 Feb 2005 12:21:00 -0700
Newsgroups gmane.ietf.impp
Message-ID <[email protected]>
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.

-- 
Joe Hildebrand  

> -----Original Message-----
> From: Justin Karneges 
> [mailto:[email protected]] 
> Sent: Wednesday, February 02, 2005 10:31 AM
> To: [email protected]
> Subject: RFC 3861, SRV handling
> 
> Hi folks,
> 
> According to RFC 3861, the destination server of an instant 
> messaging address can be determined by doing an SRV lookup on 
> the domain name within that address.  For example, if you 
> want to send a message to an address via XMPP, one might do a 
> lookup on:
> 
>   _im._xmpp.example.com
> 
> However, what confuses me is how this is supposed to play 
> with XMPP's own delivery procedure, particularly regarding 
> the fact that XMPP uses SRV as well.  For example, when one 
> XMPP server delivers a message to another, the sending server 
> does an SRV lookup:
> 
>   _xmpp-server._tcp.example.com
> 
> Should both of these SRV lookups produce the same set of 
> hostname/port pairs, meaning that they are two ways to do the 
> same thing and the sender can just pick one?  Or should these 
> procedures be "stacked", such that the _im._xmpp lookup would 
> result in a domain name that would in turn be passed through 
> the _xmpp-server._tcp lookup?
> 
> Thank you,
> -Justin
> 
>   [reminder: [email protected] for non-technical 
> discussions, please]
> 


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]