[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Simple] How to show presentity's relative service preference
Hi all,
I'm wondering how a presentity can show his perferred services in presence.
A possibility seems to use the 'priority' attribute of <contact> element for this purpose.
However, RFC 3863 defines that the 'priority' attribute shows the presentity's different preference over *contact address*, so it is not clear whether this is good enough to show the presentity's relative service preference.
For example, when there are multiple SIP services that share the presentity's AOR as contact address, then how the different 'priority' attribute value for the same contact address should be interpreted?
IMHO, this happens because a service cannot be represented only with the contact information. Rather, as noted in RFC 4476, a service is identified by the "reach information", which is a set of presence information to reach the service including the contact address.
If this is the case, what should we do?
Thanks & regards,
Jaekwon OH
--Boundary_(ID_GLFrom simple-bounces at ietf.org Mon Aug 4 18:33:58 2008
Return-Path: <simple-bounces at ietf.org>
X-Original-To: simple-archive at megatron.ietf.org
Delivered-To: ietfarch-simple-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 8F31F3A6832;
Mon, 4 Aug 2008 18:33:58 -0700 (PDT)
X-Original-To: simple at core3.amsl.com
Delivered-To: simple at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id DAF333A687E
for <simple at core3.amsl.com>; Mon, 4 Aug 2008 18:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.19
X-Spam-Level:
X-Spam-Status: No, score=-3.19 tagged_above=-999 required=5
tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4,
RELAY_IS_203=0.994]
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 smUz+g8y9SFg for <simple at core3.amsl.com>;
Mon, 4 Aug 2008 18:33:56 -0700 (PDT)
Received: from mailout3.samsung.com (mailout3.samsung.com [203.254.224.33])
by core3.amsl.com (Postfix) with ESMTP id D2B3E3A6832
for <simple at ietf.org>; Mon, 4 Aug 2008 18:33:55 -0700 (PDT)
Received: from epmmp1 (mailout3.samsung.com [203.254.224.33])
by mailout3.samsung.com
(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
with ESMTP id <0K5300FTKTP6SY at mailout3.samsung.com> for simple at ietf.org;
Tue, 05 Aug 2008 10:34:18 +0900 (KST)
Received: from JKOH ([10.89.26.207])
by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
2004))
with ESMTPA id <0K53009L0TP6TS at mmp1.samsung.com> for simple at ietf.org;
Tue, 05 Aug 2008 10:34:18 +0900 (KST)
Date: Tue, 05 Aug 2008 10:33:57 +0900
From: JaekwonOH <jaekwon.oh at samsung.com>
To: Simple WG <simple at ietf.org>
Message-id: <005001c8f69b$54282520$cf1a590a at JKOH>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Simple] How to show presentity's relative service preference
X-BeenThere: simple at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions
<simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/simple>,
<mailto:simple-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/simple>
List-Post: <mailto:simple at ietf.org>
List-Help: <mailto:simple-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>,
<mailto:simple-request at ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0360301508=="
Sender: simple-bounces at ietf.org
Errors-To: simple-bounces at ietf.org
This is a multi-part message in MIME format.
Hi all,
I'm wondering how a presentity can show his perferred services in presence.
A possibility seems to use the 'priority' attribute of <contact> element for this purpose.
However, RFC 3863 defines that the 'priority' attribute shows the presentity's different preference over *contact address*, so it is not clear whether this is good enough to show the presentity's relative service preference.
For example, when there are multiple SIP services that share the presentity's AOR as contact address, then how the different 'priority' attribute value for the same contact address should be interpreted?
IMHO, this happens because a service cannot be represented only with the contact information. Rather, as noted in RFC 4476, a service is identified by the "reach information", which is a set of presence information to reach the service including the contact address.
If this is the case, what should we do?
Thanks & regards,
Jaekwon OH
--Boundary_(ID_GLx3R1YhQyx3R1YhQyvLF5aTKZlwzw)
Content-type: text/html; charset=ks_c_5601-1987
Content-transfer-encoding: 7BIT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ks_c_5601-1987">
<META content="MSHTML 6.00.6000.16674" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face="Times New Roman" size=2>Hi all,</FONT></DIV>
<DIV><FONT face="Times New Roman" size=2></FONT> </DIV>
<DIV><FONT face="Times New Roman" size=2>I'm wondering how a presentity can show
his perferred services in presence.<BR>A possibility seems to use the 'priority'
attribute of <contact> element for this purpose.<BR>However, RFC 3863
defines that the 'priority' attribute shows the presentity's different
preference over *contact address*, so it is not clear whether this is good
enough to show the presentity's relative service preference. <BR>For example,
when there are multiple SIP services that share the presentity's AOR as contact
address, then how the different 'priority' attribute value for the same contact
address should be interpreted?<BR>IMHO, this happens because a service cannot be
represented only with the contact information. Rather, as noted in RFC 4476, a
service is identified by the "reach information", which is a set of presence
information to reach the service including the contact address.</FONT></DIV>
<DIV><FONT face="Times New Roman" size=2>If this is the case, what should we
do?<BR></DIV></FONT><FONT face="Times New Roman" size=2></FONT>
<DIV><FONT face="Times New Roman" size=2>Thanks & r</FONT><FONT
face="Times New Roman" size=2>egards,</FONT></DIV>
<DIV><FONT face="Times New Roman" size=2></FONT> </DIV>
<DIV><FONT face="Times New Roman" size=2>Jaekwon OH</FONT></DIV></BODY></HTML>
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www.ietf.org/mailman/listinfo/simple