A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
RFC 3842

 
Document Type RFC - Proposed Standard (August 2004; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3842 (Proposed Standard)
Telechat date
Responsible AD Allison Mankin
Send notices to <gonzalo.camarillo@ericsson.com>, <dean.willis@softarmor.com>, <rohan@cisco.com>
Network Working Group                                            R. Mahy
Request for Comments: 3842                           Cisco Systems, Inc.
Category: Standards Track                                    August 2004

   A Message Summary and Message Waiting Indication Event Package for
                 the Session Initiation Protocol (SIP)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

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.

Mahy                        Standards Track                     [Page 1]
RFC 3842                  SIP Message Waiting                August 2004

Table of Contents

   1.   Conventions  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.   Background and Appropriateness . . . . . . . . . . . . . . .   3
   3.   Event Package Formal Definition  . . . . . . . . . . . . . .   4
        3.1.  Event Package Name . . . . . . . . . . . . . . . . . .   4
        3.2.  Event Package Parameters . . . . . . . . . . . . . . .   4
        3.3.  SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . .   4
        3.4.  Subscription Duration. . . . . . . . . . . . . . . . .   4
        3.5.  NOTIFY Bodies. . . . . . . . . . . . . . . . . . . . .   4
        3.6.  Subscriber Generation of SUBSCRIBE Requests. . . . . .   6
        3.7.  Notifier Processing of SUBSCRIBE Requests. . . . . . .   6
        3.8.  Notifier Generation of NOTIFY Requests . . . . . . . .   7
        3.9.  Subscriber Processing of NOTIFY Requests . . . . . . .   7
        3.10. Handling of Forked Requests. . . . . . . . . . . . . .   7
        3.11. Rate of Notifications. . . . . . . . . . . . . . . . .   7
        3.12. State Agents and Lists . . . . . . . . . . . . . . . .   8
        3.13. Behavior of a Proxy Server . . . . . . . . . . . . . .   8
   4.   Examples of Usage  . . . . . . . . . . . . . . . . . . . . .   8
        4.1.  Example Message Flow . . . . . . . . . . . . . . . . .   8
        4.2.  Example Usage with Callee Capabilities and Caller
              Preferences. . . . . . . . . . . . . . . . . . . . . .  14
   5.   Formal Syntax  . . . . . . . . . . . . . . . . . . . . . . .  14
        5.1.  New Event-Package Definition . . . . . . . . . . . . .  15
        5.2.  Body Format Syntax . . . . . . . . . . . . . . . . . .  15
   6.   Security Considerations  . . . . . . . . . . . . . . . . . .  15
   7.   IANA Considerations  . . . . . . . . . . . . . . . . . . . .  16
        7.1.  SIP Event Package Registration for message-summary . .  16
        7.2.  MIME Registration for application/
              simple-message-summary . . . . . . . . . . . . . . . .  16
   8.   Contributors . . . . . . . . . . . . . . . . . . . . . . . .  17
   9.   Acknowledgments  . . . . . . . . . . . . . . . . . . . . . .  17
   10.  References . . . . . . . . . . . . . . . . . . . . . . . . .  17
        10.1. Normative References . . . . . . . . . . . . . . . . .  17
        10.2. Informational References . . . . . . . . . . . . . . .  18
   11.  Author's Address . . . . . . . . . . . . . . . . . . . . . .  18
   12.  Full Copyright Statement . . . . . . . . . . . . . . . . . .  19

1.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119 [3].

Mahy                        Standards Track                     [Page 2]
RFC 3842                  SIP Message Waiting                August 2004

2.  Background and Appropriateness

   Message Waiting Indication is a common feature of telephone networks.
   It typically involves an audible or visible indication that messages
   are waiting, such as playing a special dial tone (which in telephone
   networks is called message-waiting dial tone), lighting a light or
   indicator on the phone, displaying icons or text, or some
   combination.

      Message-waiting dial tone is similar to but distinct from stutter
      dial tone.  Both are defined in GR-506 [11].

   The methods in the SIP [1] base specification were only designed to
Show full document text