1© 2002, Cisco Systems, Inc. All rights reserved.

SIP and Jabber:Better together?

Rohan Mahy

rohan@cisco.com

222© 2002, Cisco Systems, Inc. All rights reserved.

Agenda

• Problem statement:

IM&P systems are being deployed by enterprises and carriers. The network effect of those communities is severely limited by the number of participants. There is no current standard for server-to-server connectivity. This is driving further adoption of proprietary public networks (which are quickly becoming the PSTN of IM&P) and slowing the penetration of both XMPP and SIMPLE based solutions.

• Quick update:

XMPP standards progress, implementation, adoption

SIMPLE standards progress, implementations, adoption

• Business Needs:

• Proposal:

Search for a consensus position with respect to an interop profile/protocol for server to server IM&P communications with the intent to drive that position to a standard.

333© 2002, Cisco Systems, Inc. All rights reserved.

SIMPLE and Jabber: better together?

• Combined “Super Clients”

has a SIP UA

can act as minimal XMPP host

self-test through well-known XMPP host

runs as regular XMPP node when behind a firewall or NAT

security provided by immediate sending of thread IDs

444© 2002, Cisco Systems, Inc. All rights reserved.

Using the fewest intermediaries possible

• client to client

• (client host) client

client primes its host before host will receive its messages

• client (host client)

• (client host) (host client)

555© 2002, Cisco Systems, Inc. All rights reserved.

Interop between SIP+XMPP hosts and today’s Jabber nodes

• SIP+XMPP host acts as SIP UA and an XMPP host.

• Buddy list management and basic presence are handled on behalf of Jabber nodes.

• Sessions of messages terminate on the Jabber host, and then relay through to Jabber nodes

• Jabber nodes rely on buddy lists to authorize incoming messages.

666© 2002, Cisco Systems, Inc. All rights reserved.Presentation_ID