Re: [xmpp] 3921bis: probe to full JID?

Peter Saint-Andre <stpeter@stpeter.im> Mon, 01 February 2010 21:08 UTC

Return-Path: <stpeter@stpeter.im>
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 B05CB3A68C1 for <xmpp@core3.amsl.com>; Mon, 1 Feb 2010 13:08:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 5L-C4iS366b3 for <xmpp@core3.amsl.com>; Mon, 1 Feb 2010 13:08:40 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 82B2B28C1CA for <xmpp@ietf.org>; Mon, 1 Feb 2010 13:08:35 -0800 (PST)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 90D6340332 for <xmpp@ietf.org>; Mon, 1 Feb 2010 14:09:10 -0700 (MST)
Message-ID: <4B6742F4.2090709@stpeter.im>
Date: Mon, 01 Feb 2010 14:09:08 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: xmpp@ietf.org
References: <4B6217EC.7020909@stpeter.im> <201001311244.32330.justin@affinix.com> <4B672431.7010209@webex.com> <201002011129.12739.justin@affinix.com> <4B673206.1030906@webex.com>
In-Reply-To: <4B673206.1030906@webex.com>
X-Enigmail-Version: 1.0
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050607010601070409040101"
Subject: Re: [xmpp] 3921bis: probe to full JID?
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: Mon, 01 Feb 2010 21:08:41 -0000

On 2/1/10 12:56 PM, Ben Schumacher wrote:
> On 02/01/2010 12:29 PM, Justin Karneges wrote:
>> Basically, the server should return the most recently sent presence to
>> the JID
>> doing the probing, whether directed or undirected.  So, no, if you
>> send me
>> directed presence and then I probe you, I would not expect to receive
>> your "real" (undirected) presence.
>>
>>
> 
> Therein lies the rub. I do not want to have to shove ever presence sent
> into a DB, DHT, whatever to meet these requirements. Hence the point of
> the recommendation re: probe + unavailable.

Yes, that seems onerous.

Currently, the server needs to keep track of whether another entity is
on the list for receiving unavailable presence for a given resource. The
server will remove an entity from that list if the user sends directed
unavailable presence to the entity. So the server knows if it can send
<presence/> (no details like show or status or priority) to an entity,
and perhaps that is the best thing for it to return to the entity if it
probes the full JID.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/