RFC 5839: An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) events framework enables receiving asynchronous notification of various events from other SIP user agents. This framework defines the procedures for creating, refreshing, and terminating subscriptions, as well as fetching and periodic polling of resource state. These procedures provide no tools to avoid replaying event notifications that have already been received by a user agent. This memo defines an extension to SIP events that allows the subscriber to condition the subscription request to whether the state has changed since the previous notification was received. When such a condition is true, either the body of a resulting event notification or the entire notification message is suppressed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5839
- Published
- May 2010
- Authors
- A. Niemi; D. Willis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7614Explicit Subscriptions for the REFER MethodCurrent
August 2015
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 4235An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)Updated
November 2005
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
September 2017
- RFC 9274A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) ProtocolCurrent
July 2022
- RFC 5863DomainKeys Identified Mail (DKIM) Development, Deployment, and OperationsCurrent
May 2010
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 5898Connectivity Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
July 2010
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?