RFC 5264: Publication of Partial Presence Information
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) Extension for Event State Publication describes a mechanism with which a presence user agent is able to publish presence information to a presence agent. Using the Presence Information Data Format (PIDF), each presence publication contains full state, regardless of how much of that information has actually changed since the previous update. As a consequence, updating a sizeable presence document with small changes bears a considerable overhead and is therefore inefficient. Especially with low bandwidth and high latency links, this can constitute a considerable burden to the system. This memo defines a solution that aids in reducing the impact of those constraints and increases transport efficiency by introducing a mechanism that allows for publication of partial presence information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5264
- Published
- September 2008
- Authors
- A. Niemi; M. Lonnfors; E. Leppanen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 5262Presence Information Data Format (PIDF) Extension for Partial PresenceCurrent
September 2008
- RFC 5261An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) SelectorsCurrent
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 5285A General Mechanism for RTP Header ExtensionsObsoleted
July 2008
- RFC 5239A Framework for Centralized ConferencingCurrent
June 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?