Re: [xmpp] 3921bis: probe + unavailable

Justin Karneges <justin@affinix.com> Tue, 02 February 2010 01:03 UTC

Return-Path: <justin@affinix.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01D173A67F2 for <xmpp@core3.amsl.com>; Mon, 1 Feb 2010 17:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59H8TPjGkmC9 for <xmpp@core3.amsl.com>; Mon, 1 Feb 2010 17:03:01 -0800 (PST)
Received: from homiemail-a5.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by core3.amsl.com (Postfix) with ESMTP id 333843A6767 for <xmpp@ietf.org>; Mon, 1 Feb 2010 17:03:01 -0800 (PST)
Received: from localhost (andross.dreamhost.com [75.119.221.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTP id 55F4CBCAC8 for <xmpp@ietf.org>; Mon, 1 Feb 2010 17:03:37 -0800 (PST)
From: Justin Karneges <justin@affinix.com>
To: xmpp@ietf.org
Date: Mon, 01 Feb 2010 17:03:36 -0800
User-Agent: KMail/1.9.10
References: <4B6202CF.6070702@stpeter.im> <952A4B1F81123B479292D4B5FDC00D8503BA5E39@SRV-EXSC03.webex.local> <4B673DBC.1020406@stpeter.im>
In-Reply-To: <4B673DBC.1020406@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201002011703.36954.justin@affinix.com>
Subject: Re: [xmpp] 3921bis: probe + unavailable
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 01:03:02 -0000

On Monday 01 February 2010 12:46:52 Peter Saint-Andre wrote:
> I understand that the MUST here is an imposition on servers. IMHO the
> deterministic nature of the unavailable has many benefits, but I can see
> why large service providers would prefer to return a stanza to the
> probing user only if the contact is online. So I think it's good that we
> discuss the tradeoffs here.

A large benefit is to prevent a jabber:iq:last storm.  We don't want there to 
be any reason for a client to poll its entire roster.

I can see why a mobile client might not be interested in having that 
information pushed at it on login, to reduce resource usage.  Jonas' 
suggestion of making this a client-controlled option is probably best, but I 
don't know what the default behavior should be.

Also, there has been discussion in the past about sending presence only of 
certain contacts, groups, etc, when mobile, so the solution for filtering out 
unavailable presence might fit right in with that maybe.

Another thing: this issue is actually two-part: 1) should remote servers reply 
to probes if the contact is unavailable?  and 2) should the local server send 
unavailable presence to contacts that just logged in?  Both of these have 
resource usage implications, but only the second one impacts the client.

-Justin