Re: CPIM changes and XMPP

John,


Tuesday, November 5, 2002, 5:45:22 AM, you wrote:
John> I wonder why the issue of hop counts and loop detection is part of
John> the document on instant messaging.  Don't we have to worry about the
John> same thing for subscription requests and notifications?

Yes.  Looping is an issue for any store-and-forward service.  If the
transfer service below does not do loop prevention, then looping is a
concern.

The real problem is that both of these are gateway specifications. For
maximum interoperability, a gateway spec needs to provide for only the core
mechanisms and information that will be common to all likely connected
service. Loop control is a long way from having the possibility of common
capabilities across all the services that are likely to connect through
either of these gateway mechanisms.

John> On another subject, I just read drafts from the Jabber Software
John> Foundation on the eXtensible Messaging and Presence Protocol (XMPP).

Sounds like you have some issues that should be discussed on the xmpp list.


John> What is the relation of XMPP to the IMPP working group?

Take a look at the working group's charter. Your question is answered
explicitly:

        <http://www.ietf.org/html.charters/xmpp-charter.html>

d/
-- 
 Dave Crocker  <mailto:[email protected]>
 TribalWise <http://www.tribalwise.com>
 t +1.408.246.8253; f +1.408.850.1850




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