CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 01:19:00 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=H8RpS2kp58CDtccoYZcMAXy5ME3aX7LdVCZkxG2Luag-1760145540-1.0.1.1-69xZbY_FPUBLKkQgV6aDCJsdrOfS.o3yAGuf7PdF1nn_iqG3Si8ZZ1ia7GQhfKi4rPHdJYBzwbhv2K1OKsStwg_CmDqaU7afQxaJui7tbrk; path=/; expires=Sat, 11-Oct-25 01:49:00 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ca86d5aaf5a8b0-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 3842 » RFC Editor
Search RFCs
RFC 3842
A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP), August 2004
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3842
Discuss this RFC: Send questions or comments to the mailing list sipping@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3842
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us