RFC 5262: Presence Information Data Format (PIDF) Extension for Partial Presence
In plain English — editorial summary, not part of the RFC
The Presence Information Document Format (PIDF) specifies the baseline XML-based format for describing presence information. One of the characteristics of the PIDF is that the document always needs to carry all presence information available for the presentity. In some environments where low bandwidth and high latency links can exist, it is often beneficial to limit the amount of transported information over the network. This document introduces a new MIME type that enables transporting of either only the changed parts or the full PIDF-based presence information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5262
- Published
- September 2008
- Authors
- M. Lonnfors; E. Leppanen; H. Khartabil; J. Urpalainen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5261An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) SelectorsCurrent
September 2008
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 5264Publication of Partial Presence InformationCurrent
September 2008
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 5244Definition of Events for Channel-Oriented Telephony SignallingCurrent
June 2008
- RFC 5239A Framework for Centralized ConferencingCurrent
June 2008
- RFC 5285A General Mechanism for RTP Header ExtensionsObsoleted
July 2008
- RFC 5219A More Loss-Tolerant RTP Payload Format for MP3 AudioCurrent
February 2008
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?