Re: [Sipping] Publish a different status for different contacts

[Dale.Worley at comcast.net]

   From: <veechi.jha at wipro.com>

   Can anyone suggest some documents which might have some information for
   implementing the scenario:A presentity wants to publish a different
   status for different contacts he has on his list.For example he could
   choose to be 'busy' to 2 contacts,'away' for 1 contact and available to
   all others.

The answer depends on exactly what the question is.  If you look at
RFC 3863, the PIDF can provide a different presence status for every
contact of the entity.  But those contacts are contacts of the entity,
addresses which can be used to reach the entity.  Different observers
of the PIDF will see the same status for each contact.

Dale
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.eFrom sipping-bounces at ietf.org  Thu Jun 26 08:22:47 2008
Return-Path: <sipping-bounces at ietf.org>
X-Original-To: sipping-archive at optimus.ietf.org
Delivered-To: ietfarch-sipping-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B77AF3A6943;
	Thu, 26 Jun 2008 08:22:47 -0700 (PDT)
X-Original-To: sipping at core3.amsl.com
Delivered-To: sipping at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D2B403A6943
	for <sipping at core3.amsl.com>; Thu, 26 Jun 2008 08:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_81=0.6]
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 TAnADR1+i3TR for <sipping at core3.amsl.com>;
	Thu, 26 Jun 2008 08:22:40 -0700 (PDT)
Received: from QMTA09.westchester.pa.mail.comcast.net
	(qmta09.westchester.pa.mail.comcast.net [76.96.62.96])
	by core3.amsl.com (Postfix) with ESMTP id 58E2D28C0E7
	for <sipping at ietf.org>; Thu, 26 Jun 2008 08:22:40 -0700 (PDT)
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28])
	by QMTA09.westchester.pa.mail.comcast.net with comcast
	id iaLt1Z0060cZkys590NZ00; Thu, 26 Jun 2008 15:22:42 +0000
Received: from dragon.ariadne.com ([76.19.174.1])
	by OMTA10.westchester.pa.mail.comcast.net with comcast
	id ifNf1Z00U02AVH03WfNf90; Thu, 26 Jun 2008 15:22:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=aQgiSkbjlHMA:10 a=YHJiJ7UuqgAA:10
	a=vdNB8mVE4l1gBwCki48A:9 a=8iei7IkyumbsEq6VmS2tLXUPdNoA:4
	a=jyxc8lkN1aAA:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id m5QFMdQh012430
	for <sipping at ietf.org>; Thu, 26 Jun 2008 11:22:39 -0400
Received: (from worley at localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id m5QFMdob012426;
	Thu, 26 Jun 2008 11:22:39 -0400
Date: Thu, 26 Jun 2008 11:22:39 -0400
Message-Id: <200806261522.m5QFMdob012426 at dragon.ariadne.com>
To: sipping at ietf.org
From: Dale.Worley at comcast.net
In-reply-to: <C037A228E2155B408E90822BF6EA059D04A051F2 at BLR-EC-MBX08.wipro.com>
	(veechi.jha at wipro.com)
References: <C037A228E2155B408E90822BF6EA059D04A051F2 at BLR-EC-MBX08.wipro.com>
Subject: Re: [Sipping] Publish a different status for different contacts
X-BeenThere: sipping at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping at ietf.org>
List-Help: <mailto:sipping-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request at ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces at ietf.org
Errors-To: sipping-bounces at ietf.org

   From: <veechi.jha at wipro.com>

   Can anyone suggest some documents which might have some information for
   implementing the scenario:A presentity wants to publish a different
   status for different contacts he has on his list.For example he could
   choose to be 'busy' to 2 contacts,'away' for 1 contact and available to
   all others.

The answer depends on exactly what the question is.  If you look at
RFC 3863, the PIDF can provide a different presence status for every
contact of the entity.  But those contacts are contacts of the entity,
addresses which can be used to reach the entity.  Different observers
of the PIDF will see the same status for each contact.

Dale
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for qdu for questions on current sip
Use sip at ietf.org for new developments of core SIP


uestions on current sip
Use sip at ietf.org for new developments of core SIP