RE: [Simple] Appear Offline

sunqian 32328 <sunqian@huawei.com> Mon, 16 April 2007 14:33 UTC

Return-path: <simple-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdSGi-0001TG-JF; Mon, 16 Apr 2007 10:33:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdSGh-0001T6-W3 for simple@ietf.org; Mon, 16 Apr 2007 10:33:23 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdSGc-0000Rh-RB for simple@ietf.org; Mon, 16 Apr 2007 10:33:23 -0400
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JGL00BLNHNYLN@usaga01-in.huawei.com> for simple@ietf.org; Mon, 16 Apr 2007 07:31:11 -0700 (PDT)
Received: from huawei.com ([172.17.1.36]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JGL00BQHHNXLQ@usaga01-in.huawei.com> for simple@ietf.org; Mon, 16 Apr 2007 07:31:10 -0700 (PDT)
Received: from [172.24.1.6] (Forwarded-For: [62.159.183.141]) by szxmc04-in.huawei.com (mshttpd); Mon, 16 Apr 2007 22:31:09 +0800
Date: Mon, 16 Apr 2007 22:31:09 +0800
From: sunqian 32328 <sunqian@huawei.com>
Subject: RE: [Simple] Appear Offline
To: krisztian.kiss@nokia.com
Message-id: <3d165cd3d1a48c.3d1a48c3d165cd@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004)
Content-type: text/plain; charset="us-ascii"
Content-language: en
Content-transfer-encoding: 7bit
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: simple@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
Errors-To: simple-bounces@ietf.org

Hi, 
In that case you have to set <class>appear offline</class> or the alike in tuples of the presence document, and at the same time set <provide-services><class>appear offline</class></provide-services> in the Presence Authorization Rules.

I prefer to only use "polite-block" Action in the Presence Authorization Rules, it needn't set anything in the presence document. this seems simpler.

And you know, the Watcher Information[rfc3857] will disclose who are subscribing the presence information of a presentity. So a user can not indeed hide himself in a SIMPLE presence service with Watcher Information mechanism. Because if you are offline, you must not have a active subscription.

In fact, the usage of Watcher Information is primarily presence authorization of the pending subscription mentioned in [rfc3857]. Maybe we should use other method e.g. consent mechanism mentioned in [rfc4453] and discard Watcher Information mechanism, 
or don't provide the presentity with the Watcher Information which subscription is "active", you can find this don't affect the presence authorization of the pending subscription, because it just need the "pending" subscription.  

Best Regards,
Qian

----- Original Message -----
From: krisztian.kiss@nokia.com
Date: Monday, April 16, 2007 7:56 pm
Subject: RE: [Simple] Appear Offline

> Hi Qian,
> 
> Sources may publish multiple tuples (one with status 'open', one with
> status 'closed') and set authorization rules appropriately.
> 
> Cheers,
> Krisztian 
> 
> >-----Original Message-----
> >From: ext sunqian 32328 [sunqian@huawei.com] 
> >Sent: Sunday, April 15, 2007 8:35 AM
> >To: simple@ietf.org
> >Subject: RE: [Simple] Appear Offline
> >
> >Hi,
> >Sometimes a user just wants to appear offline to some specific 
> >persons, not all of his buddies, especially not the person who 
> >is communicating with the user.
> >
> >How to realize this feature?
> >
> >Best Regards,
> >Qian Sun
> >
> >----- Original Message -----
> >From: krisztian.kiss@nokia.com
> >Date: Sunday, April 15, 2007 1:51 pm
> >Subject: RE: [Simple] Appear Offline
> >
> >> >Does it make sense?
> >> 
> >> Yes. The presence source needs to publish status 'closed' in 
> >order to 
> >> appear to be offline.
> >> 
> >> Cheers,
> >> Krisztian
> >> 
> >> >-----Original Message-----
> >> >From: ext simple-bounces@ietf.org [simple-bounces@ietf.org]
> >> >Sent: Thursday, April 12, 2007 11:04 PM
> >> >To: sunqian@huawei.com
> >> >Cc: simple@ietf.org
> >> >Subject: RE: [Simple] Appear Offline
> >> >
> >> >Hi
> >> >
> >> >I've been thinking about it, and my previous suggestion (do not
> >> publish>anything) is not correct. I agree with David Viamonte,
> >> that if
> >> >you want to appear offline you simply set your status to 
> closed. 
> >> >
> >> >You want to appear offline, which means that you want to be 
> able to 
> >> >use IM service, but you do not want to be seen.
> >> >Setting your presence status to "closed" should not have 
> impact on 
> >> >your usage of IM. So I think you do not need "appear 
> >offline" option 
> >> >in presence document. When you indicate to your IM client that 
> you 
> >> >want to appear offline, it will set presence status of IM 
> service 
> >> >tuple to closed while keeping your online.
> >> >
> >> >Does it make sense?
> >> >
> >> >Silvestr
> >> >
> >> >
> >> >>-----Original Message-----
> >> >>From: Qian Sun [sunqian@huawei.com]
> >> >>Sent: Thursday, April 12, 2007 9:46 AM
> >> >>To: 'Robert Sparks'
> >> >>Cc: simple@ietf.org
> >> >>Subject: RE: [Simple] Appear Offline
> >> >>
> >> >>Dear all,
> >> >>I have received several different answers so far:
> >> >>1. The first one is from "Presence Authorization Rules" as
> >> Robert
> >> >>indicated,
> >> >http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-
> >> >>rules-09.txt
> >> >>It uses a specific Action in presence rules, i.e. 
> <actions><sub-
> >> >>handling>polite-block</sub-handling>, to "tell the server to
> >> >>place the subscription into the "active" state, and to 
> produce a
> >> >presence
> >> >>document that indicates that the presentity is unavailable.  A
> >> >reasonable
> >> >>document would exclude device and person information elements,
> >> and
> >> >>include only a single service whose basic status is set to 
> closed.">> >>
> >> >>2. The second one is from IM SIMPLE of OMA, it looks like what
> >> David
> >> >>replied.
> >> >>"The IM subscriber SHALL be shown to his contacts with
> >> >presence status
> >> >>"offline" to his contacts when the "invisible" option is
> >> switched on."
> >> >>"Upon receiving a service setting request containing the
> >> ><vis-settings>
> >> >>element, as defined in Appendix E, from an IM User the IM Server
> >> SHALL>act
> >> >>as a Presence Source."
> >> >>"In the case when the value of the active attribute of the
> >> ><vis-status>
> >> >>element is "closed", the IM Server SHALL perform the publication
> >> of
> >> >>presence information as defined in [OMA-Pres-Spec] 
> "Publication of
> >> >presence
> >> >>information". The IM Server: SHALL set the value of
> >> >"Application-specific
> >> >>Availability for IM" Presence information element to unavailable"
> >> >>
> >> >>3. I did saw some products had realized this feature using <note>
> >> >element.
> >> >>:)
> >> >>4. Do not publish your presence information, very simple!
> >> >>
> >> >>Maybe we can also use "transformations" to archive this job,
> >> >><transformations><provide-services><hidden/></provide-
> >> >>services></transformations>, this transformation turns the
> >> status of
> >> >all
> >> >>service into "closed". It looks not bad.
> >> >>
> >> >>Anyway, should we do something here to avoid confusion and 
> >potential
> >> >IOP
> >> >>issues?
> >> >>
> >> >>Best Regard,
> >> >>Qian
> >> >>
> >> >
> >> >_______________________________________________
> >> >Simple mailing list
> >> >Simple@ietf.org
> >> >https://www1.ietf.org/mailman/listinfo/simple
> >> >
> >> 
> >
> >
> >_______________________________________________
> >Simple mailing list
> >Simple@ietf.org
> >https://www1.ietf.org/mailman/listinfo/simple
> >
> 


_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple