RFC 4235: An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a dialog event package for the SIP Events architecture, along with a data format used in notifications for this package. The dialog package allows users to subscribe to another user and to receive notification of the changes in state of INVITE-initiated dialog usages in which the subscribed-to user is involved. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4235
- Published
- November 2005
- Authors
- J. Rosenberg; H. Schulzrinne; R. Mahy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 39
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5839An Extension to Session Initiation Protocol (SIP) Events for Conditional Event NotificationCurrent
May 2010
- RFC 7614Explicit Subscriptions for the REFER MethodCurrent
August 2015
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 4244An Extension to the Session Initiation Protocol (SIP) for Request History InformationObsoleted
November 2005
- RFC 4245High-Level Requirements for Tightly Coupled SIP ConferencingCurrent
November 2005
- RFC 4247Requirements for Header Compression over MPLSCurrent
November 2005
- RFC 4190Framework for Supporting Emergency Telecommunications Service (ETS) in IP TelephonyCurrent
November 2005
- RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current
October 2005
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?