<pre>Network Working Group                                         M. Isomaki
Request for Comments: 4827                                   E. Leppanen
Category: Standards Track                                          Nokia
                                                                May 2007


An Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
           Usage for Manipulating Presence Document Contents

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document describes a usage of the Extensible Markup Language
   (XML) Configuration Access Protocol (XCAP) for manipulating the
   contents of Presence Information Data Format (PIDF) based presence
   documents.  It is intended to be used in Session Initiation Protocol
   (SIP) based presence systems, where the Event State Compositor can
   use the XCAP-manipulated presence document as one of the inputs on
   which it builds the overall presence state for the presentity.





















<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
   <a href="#section-2">2</a>.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
   3.  Relationship with Presence State Published Using SIP
       PUBLISH . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
   <a href="#section-4">4</a>.  Application Usage ID  . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-5">5</a>.  MIME Type . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-6">6</a>.  Structure of Manipulated Presence Information . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-7">7</a>.  Additional Constraints  . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-8">8</a>.  Resource Interdependencies  . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-9">9</a>.  Naming Conventions  . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-10">10</a>. Authorization Policies  . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
   <a href="#section-11">11</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
   <a href="#section-12">12</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
   <a href="#section-13">13</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
     <a href="#section-13.1">13.1</a>.  XCAP Application Usage ID  . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
   <a href="#section-14">14</a>. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
   <a href="#section-15">15</a>. References  . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
     <a href="#section-15.1">15.1</a>.  Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
     <a href="#section-15.2">15.2</a>.  Informative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>






























<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The Session Initiation Protocol (SIP) for Instant Messaging and
   Presence (SIMPLE) specifications allow a user, called a watcher, to
   subscribe to another user, called a presentity, in order to learn its
   presence information [<a href="#ref-7" title="&quot;A Presence Event Package for the Session Initiation Protocol (SIP)&quot;">7</a>].  The presence data model has been specified
   in [<a href="#ref-10" title="&quot;A Data Model for Presence&quot;">10</a>].  The data model makes a clean separation between person-,
   service-, and device-related information.

   A SIP-based mechanism, SIP PUBLISH method, has been defined for
   publishing presence state [<a href="#ref-4" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">4</a>].  Using SIP PUBLISH, a Presence User
   Agent (PUA) can publish its view of the presence state, independently
   of and without the need to learn about the states set by other PUAs.
   However, SIP PUBLISH has a limited scope and does not address all the
   requirements for setting presence state.  The main issue is that SIP
   PUBLISH creates a soft state that expires after the negotiated
   lifetime unless it is refreshed.  This makes it unsuitable for cases
   where the state should prevail without active devices capable of
   refreshing the state.

   There are three main use cases where setting of permanent presence
   state that is independent of activeness of any particular device is
   useful.  The first case concerns setting person-related state.  The
   presentity would often like to set its presence state even for
   periods when it has no active devices capable of publishing
   available.  Good examples are traveling, vacations, and so on.  The
   second case is about setting state for services that are open for
   communication, even if the presentity does not have a device running
   that service online.  Examples of these kinds of services include
   e-mail, Multimedia Messaging Service (MMS), and Short Message Service
   (SMS).  In these services, the presentity is provisioned with a
   server that makes the service persistently available, at least in
   certain forms, and it would be good to be able to advertise this to
   the watchers.  Since it is not realistic to assume that all e-mail,
   MMS, or SMS servers can publish presence state on their own (and even
   if this were possible, such state would almost never change), this
   has to be done by some other device.  And since the availability of
   the service is not dependent on that device, it would be impractical
   to require that device to be constantly active just to publish such
   availability.  The third case concerns setting the default state of
   any person, service, or device in the absence of any device capable
   of actively publishing such state.  For instance, the presentity
   might want to advertise that his or her voice service is currently
   closed, just to let the watchers know that such service might be open
   at some point.  Again, this type of default state is independent of
   any particular device and can be considered rather persistent.





<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


   Even though SIP PUBLISH remains the main way of publishing presence
   state in SIMPLE-based presence systems and is especially well-suited
   for publishing dynamic state (which presence mainly is), it needs to
   be complemented by the mechanism described in this document to
   address the use cases presented above.

   XML Configuration Access Protocol (XCAP) [<a href="#ref-2" title="&quot;The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)&quot;">2</a>] allows a client to read,
   write, and modify application configuration data stored in XML format
   on a server.  The data has no expiration time, so it must be
   explicitly inserted and deleted.  The protocol allows multiple
   clients to manipulate the data, provided that they are authorized to
   do so.  XCAP is already used in SIMPLE-based presence systems for
   manipulation of presence lists and presence authorization policies.
   This makes XCAP an ideal choice for doing device-independent presence
   document manipulation.

   This document defines an XML Configuration Access Protocol (XCAP)
   application usage for manipulating the contents of presence document.
   Presence Information Document Format (PIDF) [<a href="#ref-3" title="&quot;Presence Information Data Format (PIDF)&quot;">3</a>] is used as the
   presence document format, since the event state compositor already
   has to support it, as it is used in SIP PUBLISH.

   <a href="#section-3">Section 3</a> describes in detail how the presence document manipulated
   with XCAP is related to soft state publishing done with SIP PUBLISH.

   XCAP requires application usages to standardize several pieces of
   information, including a unique application usage ID (AUID) and an
   XML schema for the manipulated data.  These are specified starting
   from <a href="#section-4">Section 4</a>.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions</span>

   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 <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>] and
   indicate requirement levels for compliant implementations.

   Comprehensive terminology of presence and event state publishing is
   provided in "Session Initiation Protocol (SIP) Extension for Event
   State Publication" [<a href="#ref-4" title="&quot;Session Initiation Protocol (SIP) Extension for Event State Publication&quot;">4</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Relationship with Presence State Published Using SIP PUBLISH</span>

   The framework for publishing presence state is described in Figure 1.
   A central part of the framework is the event state compositor
   element, whose function is to compose presence information received
   from several sources into a single coherent presence document.




<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


   The presence state manipulated with XCAP can be seen as one of the
   information sources for the compositor to be combined with the soft
   state information published using SIP PUBLISH.  This is illustrated
   in Figure 1.  It is expected that, in the normal case, there can be
   several PUAs publishing their separate views with SIP PUBLISH, but
   only a single XCAP manipulated presence document.  As shown in the
   figure, multiple XCAP clients (for instance, in different physical
   devices) can manipulate the same document on the XCAP server, but
   this still creates only one input to the event state compositor.  The
   XCAP server stores the XCAP manipulated presence document under the
   "users" tree in the XCAP document hierarchy.  See <a href="#section-9">Section 9</a> for
   details and <a href="#section-11">Section 11</a> for an example.

   As individual inputs, the presence states set by XCAP and SIP PUBLISH
   are completely separated, and it is not possible to directly
   manipulate the state set by one mechanism with the other.  How the
   compositor treats XCAP-based inputs with respect to SIP PUBLISH-based
   inputs is a matter of compositor policy, which is beyond the scope of
   this specification.  Since the SIP PUBLISH specification already
   mandates the compositor to be able to construct the overall presence
   state from multiple inputs, which may contain non-orthogonal (or in
   some ways even conflicting) information, this XCAP usage does not
   impose any new requirements on the compositor functionality.

               +---------------+         +------------+
               |   Event State |         |  Presence  |&lt;-- SIP SUBSCRIBE
               |   Compositor  +---------+  Agent     |--&gt; SIP NOTIFY
               |               |         |   (PA)     |
               +-------+-------+         +------------+
                 ^     ^     ^
                 |     |     |
                 |     |     |       +---------------+
        +--------+     |     +-------|  XCAP server  |
        |              |             +-------+-------+
        |              |                 ^         ^
        | SIP Publish  |                 |  XCAP   |
        |              |                 |         |
     +--+--+        +--+--+         +-------+   +-------+
     | PUA |        | PUA |         | XCAP  |   | XCAP  |
     |     |        |     |         | client|   | client|
     +-----+        +-----+         +-------+   +-------+


        Figure 1: Framework for Presence Publishing and Event State
                                Composition

   The protocol interface between XCAP server and the event state
   compositor is not specified here.



<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Application Usage ID</span>

   XCAP requires application usages to define a unique application usage
   ID (AUID) in either the IETF tree or a vendor tree.  This
   specification defines the 'pidf-manipulation' AUID within the IETF
   tree, via the IANA registration in <a href="#section-13">Section 13</a>.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  MIME Type</span>

   The MIME type for this application usage is 'application/pidf+xml'.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Structure of Manipulated Presence Information</span>

   The XML Schema of the presence information is defined in the Presence
   Information Data Format (PIDF) [<a href="#ref-3" title="&quot;Presence Information Data Format (PIDF)&quot;">3</a>].  The PIDF also defines a
   mechanism for extending presence information.  See [<a href="#ref-8" title="&quot;RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)&quot;">8</a>], [<a href="#ref-9" title="&quot;CIPID: Contact Information for the Presence Information Data Format&quot;">9</a>], [<a href="#ref-11" title="&quot;Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)&quot;">11</a>],
   and [<a href="#ref-12" title="&quot;Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals&quot;">12</a>] for currently defined PIDF extensions and their XML Schemas.

   The namespace URI for PIDF is 'urn:ietf:params:xml:ns:pidf' which is
   also the XCAP default document namespace.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Additional Constraints</span>

   There are no constraints on the document beyond those described in
   the XML schemas (PIDF and its extensions) and in the description of
   PIDF [<a href="#ref-3" title="&quot;Presence Information Data Format (PIDF)&quot;">3</a>].

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Resource Interdependencies</span>

   There are no resource interdependencies beyond the possible
   interdependencies defined in PIDF [<a href="#ref-3" title="&quot;Presence Information Data Format (PIDF)&quot;">3</a>] and XCAP [<a href="#ref-2" title="&quot;The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)&quot;">2</a>] that need to be
   defined for this application usage.

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Naming Conventions</span>

   The XCAP server MUST store only a single XCAP manipulated presence
   document for each user.  The presence document MUST be located under
   the "users" tree, using filename "index".  See an example in
   <a href="#section-11">Section 11</a>.

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Authorization Policies</span>

   This application usage does not modify the default XCAP authorization
   policy, which allows only a user (owner) to read, write, or modify
   their own documents.  A server can allow privileged users to modify
   documents that they do not own, but the establishment and indication
   of such policies is outside the scope of this document.




<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>.  Example</span>

   The section provides an example of a presence document provided by an
   XCAP Client to an XCAP Server.  The presence document illustrates the
   situation where a (human) presentity has left for vacation, and
   before that, has set his presence information so that he is only
   available via e-mail.  In the absence of any published soft state
   information, this would be the sole input to the compositor forming
   the presence document.  The example document contains PIDF extensions
   specified in "RPID: Rich Presence Extensions to the Presence
   Information Data Format (PIDF)" [<a href="#ref-8" title="&quot;RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)&quot;">8</a>] and "CIPID: Contact Information
   in Presence Information Data Format" [<a href="#ref-9" title="&quot;CIPID: Contact Information for the Presence Information Data Format&quot;">9</a>].

   It is assumed that the presentity is a SIP user with Address-of-
   Record (AOR) sip:someone@example.com.  The XCAP root URI for
   example.com is assumed to be http://xcap.example.com.  The XCAP User
   Identifier (XUI) is assumed to be identical to the SIP AOR, according
   to XCAP recommendations.  In this case, the presence document would
   be located at http://xcap.example.com/pidf-manipulation/users/
   sip:someone@example.com/index.

   The presence document is created with the following XCAP operation:

  PUT /pidf-manipulation/users/sip:someone@example.com/index HTTP/1.1
  Host: xcap.example.com
  Content-Type: application/pidf+xml
  ...

  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
        &lt;presence xmlns="urn:ietf:params:xml:ns:pidf"
             xmlns:rp="urn:ietf:params:xml:ns:pidf:rpid"
             xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
             xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
             entity="sip:someone@example.com"&gt;

          &lt;tuple id="x8eg92m"&gt;
            &lt;status&gt;
              &lt;basic&gt;closed&lt;/basic&gt;
            &lt;/status&gt;
            &lt;rp:user-input&gt;idle&lt;/rp:user-input&gt;
            &lt;rp:class&gt;auth-1&lt;/rp:class&gt;
            &lt;contact priority="0.5"&gt;sip:user@example.com&lt;/contact&gt;
            &lt;note&gt;I'm available only by e-mail.&lt;/note&gt;
            &lt;timestamp&gt;2004-02-06T16:49:29Z&lt;/timestamp&gt;
          &lt;/tuple&gt;

          &lt;tuple id="x8eg92n"&gt;
            &lt;status&gt;



<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


              &lt;basic&gt;open&lt;/basic&gt;
            &lt;/status&gt;
            &lt;rp:class&gt;auth-1&lt;/rp:class&gt;
            &lt;contact priority="1.0"&gt;mailto:someone@example.com&lt;/contact&gt;
            &lt;note&gt;I'm reading mail a couple of times a week&lt;/note&gt;
          &lt;/tuple&gt;

          &lt;dm:person id="p1"&gt;
             &lt;rp:class&gt;auth-A&lt;/rp:class&gt;
             &lt;ci:homepage&gt;http://www.example.com/~someone&lt;/ci:homepage&gt;
             &lt;rp:activities&gt;
                 &lt;rp:vacation/&gt;
             &lt;/rp:activities&gt;
          &lt;/dm:person&gt;

        &lt;/presence&gt;


  When the user wants to change the note related to e-mail service,
  it is done with the following XCAP operation:

  PUT /pidf-manipulation/users/sip:someone@example.com/index/
  ~~/presence/tuple%5b@id='x8eg92n'%5d/note HTTP/1.1
  If-Match: "xyz"
  Host: xcap.example.com
  Content-Type: application/xcap-el+xml
  ...

  &lt;note&gt;I'm reading mails on Tuesdays and Fridays&lt;/note&gt;

<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>.  Security Considerations</span>

   A presence document may contain information that is highly sensitive.
   Its delivery to watchers needs to happen strictly according to the
   relevant authorization policies.  It is also important that only
   authorized clients are able to manipulate the presence information.

   The XCAP base specification mandates that all XCAP servers MUST
   implement HTTP Digest authentication specified in <a href="./rfc2617">RFC 2617</a> [<a href="#ref-5" title="&quot;HTTP Authentication: Basic and Digest Access Authentication&quot;">5</a>].
   Furthermore, XCAP servers MUST implement HTTP over TLS [<a href="#ref-6" title="&quot;HTTP Over TLS&quot;">6</a>].  It is
   recommended that administrators of XCAP servers use an HTTPS URI as
   the XCAP root services' URI, so that the digest client authentication
   occurs over TLS.  By using these means, XCAP client and server can
   ensure the confidentiality and integrity of the XCAP presence
   document manipulation operations, and that only authorized clients
   are allowed to perform them.





<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>.  IANA Considerations</span>

   There is an IANA consideration associated with this specification.

<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>.  XCAP Application Usage ID</span>

   This section registers a new XCAP Application Usage ID (AUID)
   according to the IANA procedures defined in [<a href="#ref-2" title="&quot;The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)&quot;">2</a>].

   Name of the AUID: pidf-manipulation

   Description: Pidf-manipulation application usage defines how XCAP is
   used to manipulate the contents of PIDF-based presence documents.

<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>.  Acknowledgements</span>

   The authors would like to thank Jari Urpalainen, Jonathan Rosenberg,
   Hisham Khartabil, Aki Niemi, Mikko Lonnfors, Oliver Biot, Alex Audu,
   Krisztian Kiss, Jose Costa-Requena, George Foti, and Paul Kyzivat for
   their comments.

<span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>.  References</span>

<span class="h3"><a class="selflink" id="section-15.1" href="#section-15.1">15.1</a>.  Normative References</span>

   [<a id="ref-1">1</a>]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-2">2</a>]   Rosenberg, J., "The Extensible Markup Language (XML)
         Configuration Access Protocol (XCAP)", <a href="./rfc4825">RFC 4825</a>, May 2007.

   [<a id="ref-3">3</a>]   Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and
         J. Peterson, "Presence Information Data Format (PIDF)",
         <a href="./rfc3863">RFC 3863</a>, August 2004.

   [<a id="ref-4">4</a>]   Niemi, A., "Session Initiation Protocol (SIP) Extension for
         Event State Publication", <a href="./rfc3903">RFC 3903</a>, October 2004.

   [<a id="ref-5">5</a>]   Franks, J., "HTTP Authentication: Basic and Digest Access
         Authentication", <a href="./rfc2617">RFC 2617</a>, June 1999.

   [<a id="ref-6">6</a>]   Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.

<span class="h3"><a class="selflink" id="section-15.2" href="#section-15.2">15.2</a>.  Informative References</span>

   [<a id="ref-7">7</a>]   Rosenberg, J., "A Presence Event Package for the Session
         Initiation Protocol (SIP)", <a href="./rfc3856">RFC 3856</a>, August 2004.




<span class="grey">Isomaki &amp; Leppanen          Standards Track                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


   [<a id="ref-8">8</a>]   Schulzrinne, H., Gurbani, V., Kyzivat, P., and J. Rosenberg,
         "RPID: Rich Presence Extensions to the Presence Information
         Data Format (PIDF)", <a href="./rfc4480">RFC 4480</a>, July 2006.

   [<a id="ref-9">9</a>]   Schulzrinne, H., "CIPID: Contact Information for the Presence
         Information Data Format", <a href="./rfc4482">RFC 4482</a>, July 2006.

   [<a id="ref-10">10</a>]  Rosenberg, J., "A Data Model for Presence", <a href="./rfc4479">RFC 4479</a>,
         July 2006.

   [<a id="ref-11">11</a>]  Lonnfors, M. and K. Kiss, "Session Initiation Protocol (SIP)
         User Agent Capability Extension to Presence Information Data
         Format (PIDF)", Work in Progress, July 2006.

   [<a id="ref-12">12</a>]  Schulzrinne, H., "Timed Presence Extensions to the Presence
         Information Data Format (PIDF) to Indicate Status Information
         for Past and Future Time Intervals", <a href="./rfc4481">RFC 4481</a>, July 2006.

Authors' Addresses

   Markus Isomaki
   Nokia
   P.O. BOX 100
   00045 NOKIA GROUP
   Finland

   EMail: markus.isomaki@nokia.com


   Eva Leppanen
   Nokia
   P.O. BOX 785
   33101 Tampere
   Finland

   EMail: eva-maria.leppanen@nokia.com















<span class="grey">Isomaki &amp; Leppanen          Standards Track                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4827">RFC 4827</a>        XCAP for Manipulating Presence Document         May 2007</span>


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights 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; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.







Isomaki &amp; Leppanen          Standards Track                    [Page 11]
</pre>