Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

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 June 23, 2006.

Copyright Notice

Copyright © The Internet Society (2005).

Abstract

The Presence Information Data Format (PIDF) defines a basic XML format for presenting presence information for a presentity. This document extends PIDF, adding a timed status extension (<timed-status> element) that allows a presentity to declare its status for a time interval fully in the future or the past.

Table of Contents

1.  Introduction
2.  Terminology and Conventions
3.  Timed-Status Element
4.  Example
5.  The XML Schema Definition
6.  IANA Considerations
    6.1  URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:pidf:timed-status'
    6.2  Schema Registration for Schema urn:ietf:params:xml:ns:pidf:timed-status'
7.  Security Considerations
8.  References
    8.1  Normative References
    8.2  Informative References
§  Author's Address
A.  Contributors
B.  Acknowledgments
§  Intellectual Property and Copyright Statements

1. Introduction

Traditionally, presence information, e.g., represented as PIDF (Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and J. Peterson, “Presence Information Data Format (PIDF),” August 2004.)[3] (Presence Information Data Format) and augmented by RPID (Schulzrinne, H., “RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF),” September 2005.)[7] (Rich Presence Information Data format), describes the current state of the presentity. However, a watcher can better plan communications if it knows about the presentity's future plans. For example, if a watcher knows that the presentity is about to travel, it might place a phone call earlier.

In this document, we use terms defined in RFC 2778 (Day, M., Rosenberg, J., and H. Sugano, “A Model for Presence and Instant Messaging,” February 2000.)[4]. In particular, a "presentity", abbreviating presence entity, provides presence information to a presence service. It is typically a uniquely-identified person.

RPID already allows a presentity to indicate the period when a particular aspect of its presence is valid. However, the <status> element in the PIDF <tuple> does not have this facility, so that it is not possible to indicate that a presentity will be OPEN or CLOSED in the future, for example.

It is also occasionally useful to represent past information since it may be the only known presence information; it may give watchers an indication of the current status. For example, indicating that the presentity was at an off-site meeting that ended an hour ago indicates that the presentity is likely in transit at the current time.

It is unfortunately not possible to simply add time range attributes to the PIDF <status> element, as PIDF parsers without this capability would ignore these attributes and thus not be able to distinguish current from future presence status information.

This document defines the <timed-status> element that describes the status of a presentity that is either no longer valid or covers some future time period.

2. Terminology and Conventions

The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in BCP 14, RFC 2119 (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.)[1].

3. Timed-Status Element

The <timed-status> element is a child of the <tuple> element and MUST NOT appear as a child of a PIDF <status> element or another <timed-status> element. More than one such element MAY appear within a PIDF <tuple> element.

Sources of <timed-status> information should avoid overlapping elements, but since overlapping appointments are common in calendars, for example, receivers MUST be able to render such overlapping <timed-status> indications.

The <timed-status> element MUST be qualified with the 'from' attribute and MAY be qualified with an 'until' attribute to describe the time when the status assumed this value and the time until which this element is expected to be valid. If the 'until' attribute is missing, the information is assumed valid until the tuple is explicitly overridden or expires as defined by the publication mechanism used. The time range MUST NOT encompass the present time, i.e., the <timestamp> value, as that would provide an unnecessary and confusing alternate mechanism to describe presence. Thus, the 'from' attribute for tuples without an 'until' attribute MUST refer to the future.

During composition, a presence agent (PA) may encounter a stored <timed-status> elements that covers the present time. The PA MAY either discard those elements or MAY convert it to a regular <status> element if it considers that information more credible.

The <timed-status> element may contain the <basic> and <note> elements, as well as any other element that is appropriate as a PIDF <status> extension and that has a limited validity period. Examples include the PIDF-LO (Peterson, J., “A Presence-based GEOPRIV Location Object Format,” September 2004.)[6] extensions for location objects.

This extension chose absolute rather than relative times, since relative times would be too hard to keep properly updated when spacing notifications, for example. Originators of presence information MUST generate time values in the <timed-status> elements that are fully in the past or future relative to local real (wallclock) time and the time information contained in the optional PIDF <timestamp> element.

4. Example

An example combining PIDF and timed-status is shown below:

<presence xmlns="urn:ietf:params:xml:ns:pidf"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
  xsi:schemaLocation="urn:ietf:params:xml:ns:pidf pidf.xsd
  urn:ietf:params:xml:ns:pidf:data-model data-model.xsd
  urn:ietf:params:xml:ns:pidf:timed-status timed-status.xsd"
  entity="pres:someone@example.com">

  <tuple id="c8dqui">
    <status>
      <basic>open</basic>
    </status>
    <ts:timed-status from="2005-08-15T10:20:00.000-05:00"
       until="2005-08-22T19:30:00.000-05:00">
       <ts:basic>closed</ts:basic>
    </ts:timed-status>
    <contact>sip:someone@example.com</contact>
  </tuple>
  <note>I'll be in Tokyo next week</note>
</presence>

5. The XML Schema Definition

The schema is shown below.

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:ts="urn:ietf:params:xml:ns:pidf:timed-status"
xmlns:pidf="urn:ietf:params:xml:ns:pidf"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:pidf:timed-status"
elementFormDefault="qualified" attributeFormDefault="unqualified">

  <xs:import namespace="urn:ietf:params:xml:ns:pidf"
    schemaLocation="pidf.xsd"/>

  <xs:annotation>
     <xs:documentation>
       Describes timed-status tuple extensions for PIDF.
     </xs:documentation>
  </xs:annotation>
  <xs:element name="timed-status" type="ts:timed-status"/>
  <xs:complexType name="timed-status">
    <xs:sequence>
      <xs:element name="basic" type="pidf:basic" minOccurs="0"/>
      <xs:element name="note" type="pidf:note" minOccurs="0"/>
      <xs:any namespace="##other" processContents="lax" minOccurs="0"
        maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute name="from" type="xs:dateTime" use="required"/>
    <xs:attribute name="until" type="xs:dateTime"/>
  </xs:complexType>
</xs:schema>

6. IANA Considerations

This document calls for IANA to register a new XML namespace URN and schema per [2] (Mealling, M., “The IETF XML Registry,” January 2004.).

6.1 URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:pidf:timed-status'

URI:

urn:ietf:params:xml:ns:pidf:timed-status

Description:

This is the XML namespace for XML elements defined by RFCXXXX to describe timed-status presence information extensions for the status element in the PIDF presence document format in the application/pidf+xml content type.

Registrant Contact:

IETF, SIMPLE working group, simple@ietf.org; Henning Schulzrinne, hgs@cs.columbia.edu

XML:

 BEGIN
   <?xml version="1.0"?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
   "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml
   <head>
        <meta http-equiv="content-type"
        content="text/html;charset=iso-8859-1"/>
        <title>Timed Presence Extensions to the Presence
        Information Data Format (PIDF) to Indicate Presence
        Information for Past and Future Time Intervals</title>
   </head>
   <body>
       <h1>Namespace for timed-status presence extension</h1>
       <h2>urn:ietf:params:xml:ns:pidf:timed-status</h2>
       <p>See <a href="URL of published RFC">RFCXXXX</a>.</p>
    </body>
    </html>
   END

6.2 Schema Registration for Schema urn:ietf:params:xml:ns:pidf:timed-status'

URI:

please assign

Registrant Contact:

IESG

XML:

See Section 5 (The XML Schema Definition)

7. Security Considerations

The security issues are similar to those for RPID (Schulzrinne, H., “RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF),” September 2005.)[7].

8. References

8.1 Normative References

8.2 Informative References

Author's Address

Appendix A. Contributors

Jonathan Rosenberg
dynamicsoft
600 Lanidex Plaza
Parsippany, NJ 07054-2711
USA
Email: jdrosen@dynamicsoft.com

Appendix B. Acknowledgments

This document is based on the discussions within the IETF SIMPLE working group. Mary Barnes, Avri Doria, Miguel Garcia, Vijay Gurbani, Hisham Khartabil, Paul Kyzivat, Mikko Lonnfors, Yannis Pavlidis and Jon Peterson provided helpful comments.

Intellectual Property Statement

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 BCP 78 and BCP 79.

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 http://www.ietf.org/ipr.

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.

Disclaimer of Validity

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 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.

Copyright Statement

Copyright © The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

Acknowledgment

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