RFC 3903: Session Initiation Protocol (SIP) Extension for Event State Publication
In plain English — editorial summary, not part of the RFC
This document describes an extension to the Session Initiation Protocol (SIP) for publishing event state used within the SIP Events framework. The first application of this extension is for the publication of presence information. The mechanism described in this document can be extended to support publication of any event state for which there exists an appropriate event package. It is not intended to be a general-purpose mechanism for transport of arbitrary data, as there are better-suited mechanisms for this purpose. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3903
- Published
- November 2004
- Authors
- A. Niemi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 32
- 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 2976The SIP INFO MethodObsoleted
October 2000
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 3911The Session Initiation Protocol (SIP) "Join" HeaderCurrent
October 2004
- RFC 3893Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) FormatCurrent
September 2004
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3959The Early Session Disposition Type for the Session Initiation Protocol (SIP)Current
December 2004
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?