SIMPLE H. Schulzrinne
Internet-Draft Columbia U.
Expires: September 18, 2004 March 20, 2004
CIPID: Contact Information in Presence Information Data Format
draft-ietf-simple-cipid-01
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3667.
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 September 18, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
The Contact Information for Presence Information Data Format (CIPID)
adds elements to the Presence Information Data Format (PIDF) that
provide additional contact information about a presentity and its
contacts, including references to address book entries and icons.
Schulzrinne Expires September 18, 2004 [Page 1]
Internet-Draft CIPID March 2004
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Card Element . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Homepage Element . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Icon Element . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Map Element . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.5 Sound Element . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5.1 URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:cipid' . . . . . . . . . . . . . 5
5.2 Schema Registration for Schema
urn:ietf:params:xml:ns:pidf:cipid' . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
Normative References . . . . . . . . . . . . . . . . . . . . . 6
Informative References . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . 8
Schulzrinne Expires September 18, 2004 [Page 2]
Internet-Draft CIPID March 2004
1. Introduction
In its function of facilitating communication, the usefulness of
presence information can be enhanced by providing basic information
about a presentity or contact. This document describes a basic set of
information elements that allow a watcher to retrieve additional
information about a presentity or contact.
We describe elements for providing a "business card", references to
the homepage and an icon. All can be used either for a presentity or
for a tuple (or both).
This additional presence information can be used in PIDF [3]
documents or together with RPID [4].
2. Elements
2.1 Card Element
The <card> element includes a URI pointing to a business card, e.g.,
in LDIF or vCard [5] format.
2.2 Homepage Element
The <homepage> element provides a URI pointing to general information
about the tuple or presentity, typically a web home page.
2.3 Icon Element
The <icon> element provides a URI pointing to an image (icon)
representing the tuple or presentity. The watcher MAY use this
information to represent the tuple or presentity in a graphical user
interface. Presentities SHOULD provide images of sizes and aspect
ratios that are appropriate for rendering as an icon. Support for
JPEG, PNG and GIF formats is RECOMMENDED.
2.4 Map Element
The <map> element provides a URI pointing to a map related to the
tuple or presentity. The watcher MAY use this information to
represent the tuple or presentity in a graphical user interface.
2.5 Sound Element
The <sound> element provides a URI pointing to a sound related to the
tuple or presentity. The watcher MAY use the sound object, such as a
MIDI or MP3 file, referenced by the URL to inform the watcher that
the presentity has assumed the status OPEN. User interfaces MUST
Schulzrinne Expires September 18, 2004 [Page 3]
Internet-Draft CIPID March 2004
provide the watcher with the opportunity to choose whether to play
such sounds.
3. Example
An example, combining RPID and CIPID, is shown in Fig. Figure 1.
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:es="urn:ietf:params:xml:ns:pidf:status:rpid-status"
xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"
xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
entity="pres:someone@example.com">
<tuple id="b8xk">
<status>
<basic>closed</basic>
</status>
</tuple>
<tuple id="c8dqui">
<et:class>assistant</et:class>
<status>
<basic>open</basic>
</status>
<ci:homepage>http://example.com/~secretary</ci:homepage>
<ci:icon>http://example.com/~secretary/icon.gif</ci:icon>
<ci:card>http://example.com/~secretary/card.vcd</ci:card>
<et:relationship>assistant</et:relationship>
<et:contact-type>presentity</et:contact-type>
<contact>sip:secretary@example.com</contact>
<note>My secretary</note>
</tuple>
<ci:homepage>http://example.com/~someone</ci:homepage>
<ci:icon>http://example.com/~someone/icon.gif</ci:icon>
<ci:card>http://example.com/~someone/card.vcd</ci:card>
</presence>
A CIPID Example
Figure 1
Schulzrinne Expires September 18, 2004 [Page 4]
Internet-Draft CIPID March 2004
4. Schema
The schema is shown in Fig. Figure 2.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="urn:ietf:params:xml:ns:pidf:cipid"
xmlns:pidf="urn:ietf:params:xml:ns:pidf"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<!-- This import brings in the XML language attribute xml:lang-->
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:annotation>
<xs:documentation xml:lang="en">
Describes CIPID tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:element name="card" type="xs:anyURI"/>
<xs:element name="homepage" type="xs:anyURI"/>
<xs:element name="icon" type="xs:anyURI"/>
</xs:schema>
The CIPID Schema
Figure 2
5. IANA Considerations
This document calls for IANA to register a new XML namespace URN and
schema per [2].
5.1 URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:pidf:cipid'
URI: urn:ietf:params:xml:ns:pidf:cipid
Description: This is the XML namespace for XML elements defined by
RFCXXXX to describe contact information presence information
extensions for the status element in the PIDF presence document
format in the application/cpim-pidf+xml content type.
Registrant Contact: IETF, SIMPLE working group, simple@ietf.org;
Henning Schulzrinne, hgs@cs.columbia.edu
Schulzrinne Expires September 18, 2004 [Page 5]
Internet-Draft CIPID March 2004
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>CIPID -- Contact Information in Presence Information Data Format</title>
</head>
<body>
<h1>Namespace for contact information presence extension (status)</h1>
<h2>urn:ietf:params:xml:ns:pidf:cipid</h2>
<p>See <a href="URL of published RFC">RFCXXXX</a>.</p>
</body>
</html>
END
5.2 Schema Registration for Schema urn:ietf:params:xml:ns:pidf:cipid'
URI: please assign
Registrant Contact: IESG
XML: See Figure 2
6. Security Considerations
The security issues are similar to those for RPID [4]. Watchers need
to restrict which types of content pointed to by <icon> elements they
render.
Also, accessing these URIs may in turn provide hints that the watcher
is currently using the presence application. Thus, a presence
application may want to cache these objects for later use.
Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January
2004.
[3] Sugano, H. and S. Fujimoto, "Presence Information Data Format
Schulzrinne Expires September 18, 2004 [Page 6]
Internet-Draft CIPID March 2004
(PIDF)", draft-ietf-impp-cpim-pidf-08 (work in progress), May
2003.
Informative References
[4] Schulzrinne, H., Gurbani, V., Kyzivat, P. and J. Rosenberg,
"RPID: Rich Presence: Extensions to the Presence Information
Data Format (PIDF)", draft-ietf-simple-rpid-02 (work in
progress), March 2004.
[5] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC
2426, September 1998.
Author's Address
Henning Schulzrinne
Columbia University
Department of Computer Science
450 Computer Science Building
New York, NY 10027
US
Phone: +1 212 939 7042
EMail: hgs+simple@cs.columbia.edu
URI: http://www.cs.columbia.edu
Appendix A. Acknowledgments
This document is based on the discussions within the IETF SIMPLE
working group. Vijay Gurbani, Paul Kyzivat, Jon Peterson and
Jonathan Rosenberg have provided helpful comments.
Schulzrinne Expires September 18, 2004 [Page 7]
Internet-Draft CIPID March 2004
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 IETF's procedures with respect to rights in IETF 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 (C) The Internet Society (2004). 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.
Schulzrinne Expires September 18, 2004 [Page 8]
