RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
RFC 4480
Document | Type | RFC - Proposed Standard (July 2006; Errata) | |
---|---|---|---|
Authors | Paul Kyzivat , Vijay Gurbani , Henning Schulzrinne , Jonathan Rosenberg | ||
Last updated | 2020-01-21 | ||
Replaces | draft-ietf-simple-rpids | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4480 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
Network Working Group H. Schulzrinne Request for Comments: 4480 Columbia U. Category: Standards Track V. Gurbani Lucent P. Kyzivat J. Rosenberg Cisco July 2006 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) 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 Internet Society (2006). Abstract The Presence Information Data Format (PIDF) defines a basic format for representing presence information for a presentity. This format defines a textual note, an indication of availability (open or closed) and a Uniform Resource Identifier (URI) for communication. The Rich Presence Information Data format (RPID) described here is an extension that adds optional elements to the Presence Information Data Format (PIDF). These extensions provide additional information about the presentity and its contacts. The information is designed so that much of it can be derived automatically, e.g., from calendar files or user activity. This extension includes information about what the person is doing, a grouping identifier for a tuple, when a service or device was last used, the type of place a person is in, what media communications might remain private, the relationship of a service tuple to another presentity, the person's mood, the time zone it is located in, the type of service it offers, an icon reflecting the presentity's status, and the overall role of the presentity. These extensions include presence information for persons, services (tuples), and devices. Schulzrinne, et al. Standards Track [Page 1] RFC 4480 RIPD July 2006 Table of Contents 1. Introduction ....................................................2 2. Terminology and Conventions .....................................4 3. RPID Elements ...................................................4 3.1. Overview ...................................................4 3.2. Activities Element .........................................7 3.3. Class Element .............................................10 3.4. Device Identifier .........................................10 3.5. Mood Element ..............................................10 3.6. Place-is Element ..........................................12 3.7. Place-type Element ........................................13 3.8. Privacy Element ...........................................14 3.9. Relationship Element ......................................15 3.10. Service Class ............................................15 3.11. Sphere Element ...........................................16 3.12. Status-Icon Element ......................................16 3.13. Time Offset ..............................................17 3.14. User-Input Element .......................................17 4. Example ........................................................18 5. XML Schema Definitions .........................................20 5.1. urn:ietf:params:xml:ns:pidf:rpid ..........................20 6. Extending RPID .................................................30 7. IANA Considerations ............................................31 7.1. URN Sub-Namespace Registration for ........................31 'urn:ietf:params:xml:ns:pidf:rpid' 7.2. Schema Registration for Schema ............................32 'urn:ietf:params:xml:ns:pidf:status:rpid' 8. Internationalization Considerations ............................32 9. Security Considerations ........................................32 10. References ....................................................33 10.1. Normative References .....................................33 10.2. Informative References ...................................34 Appendix A. Acknowledgements .....................................35 1. Introduction The Presence Information Data Format (PIDF) definition [8] describes a basic presence information data format, encoded as an ExtensibleShow full document text