RFC 5263: Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information
In plain English — editorial summary, not part of the RFC
By default, presence delivered using the presence event package for the Session Initiation Protocol (SIP) is represented in the Presence Information Data Format (PIDF). A PIDF document contains a set of elements, each representing a different aspect of the presence being reported. When any subset of the elements change, even just a single element, a new document containing the full set of elements is delivered. This memo defines an extension allowing delivery of only the presence data that has actually changed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5263
- Published
- September 2008
- Authors
- M. Lonnfors; J. Costa-Requena; E. Leppanen; H. Khartabil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4119A Presence-based GEOPRIV Location Object FormatUpdated
December 2005
- RFC 6910Completion of Calls for the Session Initiation Protocol (SIP)Current
April 2013
- RFC 4827An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document ContentsCurrent
May 2007
- RFC 4482CIPID: Contact Information for the Presence Information Data FormatCurrent
July 2006
- RFC 5264Publication of Partial Presence InformationCurrent
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
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?