[Standards-JIG] proto-JEP: Smart Presence Distribution
jean-louis.seguineau at laposte.net
Tue May 16 16:52:22 UTC 2006
This JEP highlights a point where XMPP could improve its presence
distribution model. Obviously we would streamline traffic by delegating
probing and advertising to the target server. The greater gains thought
would only be achieved when a particular user has more than one contact
located on a remote server. If one user has a widely spread remote contact
distribution (i.e. many remote contacts each on different servers), the real
gain would be lower than expected.
But beyond any discussions about how much traffic decrease would be
incurred, the proposed implementation will break the XMPP inter domain
routing. And that is not acceptable.
I could also agree to add some extension inside a <presence/> stanza
indicating it is a 'smart unicast' destined to a remote server. It must in
any case be addressed to the remote server, because without a 'to' attribute
for an s2s, routing becomes impossible.
If we believe the gain of this approach is worth modifying servers behavior,
I propose to change the implementation to something like
<presence from='romeo at montague/inlove' to='capulet'/>
Or if we want to be more specific
<presence from='romeo at montague/inlove' to='capulet'>
In both cases note the to attribute with the bare JID of the remote server.
Date: Tue, 16 May 2006 10:17:33 -0500
From: JEP Editor <editor at jabber.org>
Subject: [Standards-JIG] proto-JEP: Smart Presence Distribution
To: standards-jig at jabber.org
Message-ID: <E1Fg1Ij-0002bi-00 at apollo>
The JEP Editor has received a proposal for a new JEP.
Title: Smart Presence Distribution
Abstract: This document documents the current distribution model for
presence and introduces a smart presence distribution strategy to cut down
on S2S traffic and load.
The Jabber Council will decide within 7 days (or at its next meeting)
whether to accept this proposal as an official JEP.
More information about the Standards