RFC 3842: A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document describes a Session Initiation Protocol (SIP) event package to carry message waiting status and message summaries from a messaging system to an interested User Agent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3842
- Published
- August 2004
- Authors
- R. Mahy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
- RFC 3893Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) FormatCurrent
September 2004
- RFC 3903Session Initiation Protocol (SIP) Extension for Event State PublicationUpdated
November 2004
- RFC 3911The Session Initiation Protocol (SIP) "Join" HeaderCurrent
October 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?