RFC 5196: Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)
In plain English — editorial summary, not part of the RFC
Presence Information Data Format (PIDF) defines a common presence data format for Common Profile for Presence (CPP) compliant presence protocols. This memo defines a PIDF extension to represent SIP User Agent capabilities. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5196
- Published
- September 2008
- Authors
- M. Lonnfors; K. Kiss
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3863Presence Information Data Format (PIDF)Current
August 2004
- RFC 3859Common Profile for Presence (CPP)Current
August 2004
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 5188RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B CodecCurrent
February 2008
- RFC 5215RTP Payload Format for Vorbis Encoded AudioCurrent
August 2008
- RFC 5219A More Loss-Tolerant RTP Payload Format for MP3 AudioCurrent
February 2008
- RFC 5167Media Server Control Protocol RequirementsCurrent
March 2008
- RFC 5239A Framework for Centralized ConferencingCurrent
June 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?