From: http://www.ietf.org/internet-drafts/draft-rosenberg-simple-pres-policy-caps-00.txt Title: An Extensible Markup Language (XML) Representation for Expressing Presence Policy Capabilities Reference: IETF SIMPLE Working Group, Internet Draft, 'draft-rosenberg-simple-pres-policy-caps-00' Date: February 9, 2004 ------------------------------------------------------------------------ SIMPLE J. Rosenberg Internet-Draft dynamicsoft Expires: August 9, 2004 February 9, 2004 An Extensible Markup Language (XML) Representation for Expressing Presence Policy Capabilities draft-rosenberg-simple-pres-policy-caps-00 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 9, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract An important component of presence services is policy. Policy systems allow the presentity to grant access to specific pieces of information to specific watchers. To allow for interoperability between clients which set such policies, and servers which execute them, it is necessary for clients to be able to determine the capabilities of the server to which it is connected. This specification defines a set of Extensible Markup Language (XML) elements for expressing presence policy capabilities. Rosenberg Expires August 9, 2004 [Page 1] Internet-Draft Presence Policy Capabilities February 2004 Table of Contents 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Structure of Presence Policy Capabilities . . . . . . . . . . 3 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7.1 URN Sub-Namespace Registrations . . . . . . . . . . . . . . . 5 7.2 XML Schema Registration . . . . . . . . . . . . . . . . . . . 5 Normative References . . . . . . . . . . . . . . . . . . . . . 6 Informative References . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . 7 Rosenberg Expires August 9, 2004 [Page 2] Internet-Draft Presence Policy Capabilities February 2004 1. Terminology In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119 [3] and indicate requirement levels for compliant implementations. 2. Introduction An important component of presence [5] is policy. Policy systems allow the presentity to grant access to specific pieces of information to specific watchers. These policy systems can be extremely simple or extremely complex. For this reason [1] defines a generic Extensible Markup Language (XML) based format for representing policy capabilities. That format applies to many services, including location and presence. This specification extends that one by defining policy capabilities specific to presence. Those policy capabilities correspond to the conditions, actions and transformations defined in [2]. 3. Structure of Presence Policy Capabilities [1] defines the structure of common policy capability documents. In that specification, each policy capability document has three components - a list of supported conditions, a list of supported actions, and a list of supported transformations. This specification merely extends that document with the conditions, actions and transformations defined in [2]. It does so by defining six empty elements - "anonymous", "accept-subscription", "provide-presence", "show-namespace", "show-tuple", "show-element" - each of which indicates whether the respective attribute in [2] is supported. All of these elements are defined within the namespace: urn:ietf:params:xml:ns:supported-pres-permissions Rosenberg Expires August 9, 2004 [Page 3] Internet-Draft Presence Policy Capabilities February 2004 4. XML Schema 5. Example Document The following document indicates that the identity, validity, sphere and confirmation attributes are supported. It also indicates that a vendor-specific condition, called "temp", is supported, in addition to two vendor-specific transformations - "max-security" and "min-security". The "show-tuple" element is also supported. Rosenberg Expires August 9, 2004 [Page 4] Internet-Draft Presence Policy Capabilities February 2004 6. Security Considerations This specification does not introduce any new security considerations beyond those discussed in [1]. 7. IANA Considerations There are several IANA considerations associated with this specification. 7.1 URN Sub-Namespace Registrations This section registers a new XML namespace, as per the guidelines in [4] URI: The URI for this namespace is urn:ietf:params:xml:ns:supported-pres-permissions. Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net). XML: BEGIN Supported Presence Permissions Namespace

Namespace for Supported Permissions

urn:ietf:params:xml:ns:supported-pres-permissions

See RFCXXXX.

END 7.2 XML Schema Registration This section registers an XML schema as per the procedures in [4]. Rosenberg Expires August 9, 2004 [Page 5] Internet-Draft Presence Policy Capabilities February 2004 URI: please assign. Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net). The XML for this schema can be found as the sole content of Section 4. Normative References [1] Rosenberg, J., "An Extensible Markup Language (XML) Representation for Expressing Policy Capabilities", draft-rosenberg-simple-common-policy-caps-00 (work in progress), February 2004. [2] Rosenberg, J., "Presence Authorization Rules", draft-rosenberg-simple-rules-00 (work in progress), February 2004. [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. Informative References [5] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and Instant Messaging", RFC 2778, February 2000. Author's Address Jonathan Rosenberg dynamicsoft 600 Lanidex Plaza Parsippany, NJ 07054 US Phone: +1 973 952-5000 EMail: jdrosen@dynamicsoft.com URI: http://www.jdrosen.net Rosenberg Expires August 9, 2004 [Page 6] Internet-Draft Presence Policy Capabilities February 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Rosenberg Expires August 9, 2004 [Page 7] Internet-Draft Presence Policy Capabilities February 2004 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Rosenberg Expires August 9, 2004 [Page 8]