RFC 4480: RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4480
- Published
- July 2006
- Authors
- H. Schulzrinne; V. Gurbani; P. Kyzivat; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 37
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 4481Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time IntervalsCurrent
July 2006
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 4483A Mechanism for Content Indirection in Session Initiation Protocol (SIP) MessagesCurrent
May 2006
- RFC 4484Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)Current
August 2006
- RFC 4485Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)Current
May 2006
- RFC 4475Session Initiation Protocol (SIP) Torture Test MessagesCurrent
May 2006
- RFC 4474Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)Obsoleted
August 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?