[Simple] Updated presence-rules

Jonathan Rosenberg <jdrosen@cisco.com> Mon, 09 July 2007 20:59 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 1I80Jy-00019w-1R; Mon, 09 Jul 2007 16:59:02 -0400
Received: from simple by megatron.ietf.org with local (Exim 4.43) id 1I80Jv-00019Y-MI for simple-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 16:58:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I80Jv-00018k-77 for simple@ietf.org; Mon, 09 Jul 2007 16:58:59 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I80Ji-0001wY-QE for simple@ietf.org; Mon, 09 Jul 2007 16:58:59 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-2.cisco.com with ESMTP; 09 Jul 2007 13:58:25 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAHs+kkarR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,518,1175497200"; d="scan'208"; a="384458302:sNHT7619434128"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l69KwORP019903 for <simple@ietf.org>; Mon, 9 Jul 2007 13:58:24 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l69Kw4nO011793 for <simple@ietf.org>; Mon, 9 Jul 2007 20:58:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 13:58:17 -0700
Received: from [10.32.241.146] ([10.32.241.146]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 13:58:16 -0700
Message-ID: <4692A16D.2080604@cisco.com>
Date: Mon, 09 Jul 2007 16:58:21 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Simple WG <simple@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2007 20:58:17.0003 (UTC) FILETIME=[DF7B2FB0:01C7C26B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1259; t=1184014704; x=1184878704; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Updated=20presence-rules |Sender:=20; bh=tDbFiuJFwx4Yjt4bfuCMvaW4oQ+Cb7A/gTY2mxpvHSs=; b=fIKMJvKn0tCvCJeWjFX91SfY8rALgLUMeYDsQ24NLyF6G/XDFoIBmTm5z/wVm+NYYMvDlI2I MD26TbPlXxmJOl6BBgM0zBcJFXQB2bsWpXLcMcbGNqYoL3uiXdxrK8tG;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Simple] Updated presence-rules
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

I've submitted an update to the presence-rules specification:
http://www.ietf.org/internet-drafts/draft-ietf-simple-presence-rules-10.txt

the changes were meant to address IESG comments:
https://datatracker.ietf.org/idtracker/ballot/1543/

These resulted in a few changes worth noting:

* the spec now as a section that documents implementation requirements 
on clients and servers. In particular, all attributes MUST be supported 
by servers, and SHOULD be supported by clients

* consideration for cases where multiple clients edit a rules document, 
but support different subsets of rules, is considered

* identity processing has been revised and generalized. Now, instead of 
enumarting handling for the currently defined SIP mechanisms (4474, 
digest, PAID), it defines a more general framework that covers all 
three. This moves PAID to informational and avoids the downref to RFC3325.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


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