draft-ietf-sipping-mwi-02.txt   draft-ietf-sipping-mwi-03.txt 
SIPPING WG R. Mahy SIPPING WG R. Mahy
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: September 1, 2003 March 3, 2003 Expires: December 27, 2003 June 28, 2003
A Message Summary and Message Waiting Indication Event Package for A Message Summary and Message Waiting Indication Event Package for
the Session Initiation Protocol (SIP) the Session Initiation Protocol (SIP)
draft-ietf-sipping-mwi-02.txt draft-ietf-sipping-mwi-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 1, 2003. This Internet-Draft will expire on December 27, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This draft proposes a SIP event package to carry message waiting This document describes a SIP event package to carry message waiting
status and message summaries from a messaging system to an interested status and message summaries from a messaging system to an interested
User Agent. User Agent.
Table of Contents Table of Contents
1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Background and Appropriateness . . . . . . . . . . . . . . . 3 2. Background and Appropriateness . . . . . . . . . . . . . . . 3
3. Event Package Formal Definition . . . . . . . . . . . . . . 4 3. Event Package Formal Definition . . . . . . . . . . . . . . 4
3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . . 4 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . . 4
3.2 Event Package Parameters . . . . . . . . . . . . . . . . . . 4 3.2 Event Package Parameters . . . . . . . . . . . . . . . . . . 4
3.3 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . . 4 3.3 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . . 4
3.4 Subscription Duration . . . . . . . . . . . . . . . . . . . 4 3.4 Subscription Duration . . . . . . . . . . . . . . . . . . . 4
3.5 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . . 4 3.5 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . . 4
3.6 Subscriber generation of SUBSCRIBE requests . . . . . . . . 6 3.6 Subscriber generation of SUBSCRIBE requests . . . . . . . . 6
3.7 Notifier processing of SUBSCRIBE requests . . . . . . . . . 6 3.7 Notifier processing of SUBSCRIBE requests . . . . . . . . . 6
3.8 Notifier generation of NOTIFY requests . . . . . . . . . . . 7 3.8 Notifier generation of NOTIFY requests . . . . . . . . . . . 7
3.9 Subscriber processing of NOTIFY requests . . . . . . . . . . 7 3.9 Subscriber processing of NOTIFY requests . . . . . . . . . . 7
3.10 Handling of Forked Requests . . . . . . . . . . . . . . . . 7 3.10 Handling of Forked Requests . . . . . . . . . . . . . . . . 7
3.11 Rate of notifications . . . . . . . . . . . . . . . . . . . 7 3.11 Rate of notifications . . . . . . . . . . . . . . . . . . . 7
3.12 State Agents . . . . . . . . . . . . . . . . . . . . . . . . 8 3.12 State Agents and Lists . . . . . . . . . . . . . . . . . . . 8
3.13 Behavior of a Proxy Server . . . . . . . . . . . . . . . . . 8 3.13 Behavior of a Proxy Server . . . . . . . . . . . . . . . . . 8
4. Examples of Usage . . . . . . . . . . . . . . . . . . . . . 8 4. Examples of Usage . . . . . . . . . . . . . . . . . . . . . 8
4.1 Example Message Flow . . . . . . . . . . . . . . . . . . . . 8 4.1 Example Message Flow . . . . . . . . . . . . . . . . . . . . 8
4.2 Example Usage with Caller Preferences . . . . . . . . . . . 14 4.2 Example Usage with Callee Capabilities . . . . . . . . . . . 14
5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 14 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 14
5.1 New event-package definition . . . . . . . . . . . . . . . . 14 5.1 New event-package definition . . . . . . . . . . . . . . . . 14
5.2 Body Format Syntax . . . . . . . . . . . . . . . . . . . . . 15 5.2 Body Format Syntax . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . 15
7.1 SIP Event Package Registration for message-summary . . . . . 16 7.1 SIP Event Package Registration for message-summary . . . . . 15
7.2 MIME Registration for application/simple-message-summary . . 16 7.2 MIME Registration for application/simple-message-summary . . 16
8. Revision history . . . . . . . . . . . . . . . . . . . . . . 16 8. Revision history . . . . . . . . . . . . . . . . . . . . . . 16
8.1 Open Issues . . . . . . . . . . . . . . . . . . . . . . . . 17 8.1 Changes from draft-ietf-sipping-mwi-01 and -02 . . . . . . . 16
8.2 Changes from draft-ietf-sipping-mwi-00 . . . . . . . . . . . 17 8.2 Changes from draft-ietf-sipping-mwi-00 . . . . . . . . . . . 17
8.3 Changes from draft-mahy-sipping-mwi-00 . . . . . . . . . . . 17 8.3 Changes from draft-mahy-sipping-mwi-00 . . . . . . . . . . . 17
8.4 Changes from draft-mahy-sip-mwi-01 . . . . . . . . . . . . . 18 8.4 Changes from draft-mahy-sip-mwi-01 . . . . . . . . . . . . . 17
8.5 Changes from draft-mahy-sip-mwi-00 . . . . . . . . . . . . . 18 8.5 Changes from draft-mahy-sip-mwi-00 . . . . . . . . . . . . . 18
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 19 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 18
Normative References . . . . . . . . . . . . . . . . . . . . 19 Normative References . . . . . . . . . . . . . . . . . . . . 19
Informational References . . . . . . . . . . . . . . . . . . 19 Informational References . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . 20
Intellectual Property and Copyright Statements . . . . . . . 21 Intellectual Property and Copyright Statements . . . . . . . 21
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [3]. document are to be interpreted as described in RFC-2119 [3].
2. Background and Appropriateness 2. Background and Appropriateness
Messaging Waiting Indication is a common feature of telephone Messaging Waiting Indication is a common feature of telephone
networks. It typically involves an audible or visible indication networks. It typically involves an audible or visible indication
that messages are waiting, such as playing a special dial tone that messages are waiting, such as playing a special dial tone (which
(called message-waiting dial tone), lighting a light or indicator on in telephone networks is called message-waiting dial tone), lighting
the phone, displaying icons or text, or some combination. a light or indicator on the phone, displaying icons or text, or some
Message-waiting dial tone is similar but distinct from stutter dial combination.
tone. Both are defined in GR-506 [10].
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 The methods in the SIP [1] base specification were only designed to
solve the problem of session initiation for multimedia sessions, and solve the problem of session initiation for multimedia sessions, and
rendezvous. Since Message Waiting Indication is really status rendezvous. Since Message Waiting Indication is really status
information orthogonal to a session, it was not clear how an IP information orthogonal to a session, it was not clear how an IP
telephone acting as a SIP User Agent would implement comparable telephone acting as a SIP User Agent would implement comparable
functionality. Members of the telephony community viewed this as a functionality. Members of the telephony community viewed this as a
shortcoming of SIP. shortcoming of SIP.
Users want the useful parts of the functionality they have using Users want the useful parts of the functionality they have using
traditional analog, mobile, and PBX telephones. It is also desirable traditional analog, mobile, and PBX telephones. It is also desirable
to provide comparable functionality in a flexible way that allows for to provide comparable functionality in a flexible way that allows for
more customization and new features. more customization and new features. SIP Specific Event Notification
(RFC 3265 -- SIP Events) [2] is an appropriate mechanism to use in
SIP Specific Event Notification (RFC 3265 -- SIP Events) [2] is an this environment, as it preserves the user mobility and rendezvous
appropriate mechanism to use in this environment, as it preserves the features which SIP provides.
user mobility and rendezvous features which SIP provides.
Using SIP-Specific Event Notification, A Subscriber User Agent Using SIP-Specific Event Notification, A Subscriber User Agent
(typically an IP phone or SIP software User Agent) subscribes to the (typically an IP phone or SIP software User Agent) subscribes to the
status of their messages. A SIP User Agent acting on behalf of the status of their messages. A SIP User Agent acting on behalf of the
user's messaging system then notifies the Subscriber whenever the user's messaging system then notifies the Subscriber whenever the
messaging account's messages have changed. The Notifier sends this messaging account's messages have changed.(This Notifier could be
message summary information in the body of the NOTIFY, encoded in a composed with a User Agent that provides a real-time media interface
new MIME type defined later in this draft. A User Agent can also to send or receive messages, or it could be a standalone entitiy.)
explicitly fetch the current status. The Notifier sends message summary information in the body of a
NOTIFY, encoded in a new MIME type defined later in this document. A
User Agent can also explicitly fetch the current status.
A SIP User Agent MAY subscribe to multiple accounts (distinguished by A SIP User Agent MAY subscribe to multiple accounts (distinguished by
the Request URI). Multiple SIP User Agents MAY subscribe to the same the Request URI). Multiple SIP User Agents MAY subscribe to the same
account. account.
Before any subscriptions or notifications are sent, each interested Before any subscriptions or notifications are sent, each interested
User Agent must be made aware of its messaging server(s). This MAY User Agent must be made aware of its messaging notifier(s). This MAY
be manually configured on interested User Agents, manually configured be manually configured on interested User Agents, manually configured
on an appropriate SIP Proxy, or dynamically discovered using caller on an appropriate SIP Proxy, or dynamically discovered based on
preferences [4]. (For more information on usage with caller registered callee capabilities [4]. (For more information on usage
preferences, see Section 4.2) with callee capabilities, see Section 4.2)
3. Event Package Formal Definition 3. Event Package Formal Definition
3.1 Event Package Name 3.1 Event Package Name
This document defines a SIP Event Package as defined in RFC 3265 [2]. This document defines a SIP Event Package as defined in RFC 3265 [2].
The event-package token name for this package is: The event-package token name for this package is:
"message-summary" "message-summary"
skipping to change at page 5, line 46 skipping to change at page 5, line 49
Optionally, after the summary counts, the messaging systems MAY Optionally, after the summary counts, the messaging systems MAY
append RFC 2822 [9]-style message headers, which further describe append RFC 2822 [9]-style message headers, which further describe
newly added messages. Message headers MUST NOT be included in an newly added messages. Message headers MUST NOT be included in an
initial NOTIFY, as new messages could be essentially unbounded in initial NOTIFY, as new messages could be essentially unbounded in
size. Message headers included in subsequent notifications MUST only size. Message headers included in subsequent notifications MUST only
correspond to messages added since the previous notification for that correspond to messages added since the previous notification for that
subscription. A messaging system which includes message headers in a subscription. A messaging system which includes message headers in a
NOTIFY, MUST provide an administrator configurable mechanism for NOTIFY, MUST provide an administrator configurable mechanism for
selecting which headers are sent. Likely headers for inclusion selecting which headers are sent. Likely headers for inclusion
include To, From, Date, Subject, and Message-ID. Note that the include To, From, Date, Subject, and Message-ID. Note that the
formatting of these headers is identical to that of SIP formatting of these headers in this body is identical to that of SIP
extension-headers, not the (similar) format defined in RFC 2822. extension-headers, not the (similar) format defined in RFC 2822.
Implementations which generate large notifications are reminded to Implementations which generate large notifications are reminded to
follow the message size restrictions for unreliable transports follow the message size restrictions for unreliable transports
articulated in Section 18.1.1 of SIP. articulated in Section 18.1.1 of SIP.
Mapping local message state to new/old message status and urgency is Mapping local message state to new/old message status and urgency is
an implementation issue of the messaging system. However, the an implementation issue of the messaging system. However, the
messaging system MUST NOT consider a message "old" merely because it messaging notifier MUST NOT consider a message "old" merely because
generated a notification , as this could prevent another subscription it generated a notification, as this could prevent another
from accurately receiving message-summary notifications. Likewise, subscription from accurately receiving message-summary notifications.
the messaging system MAY use any suitable algorithm to determine that Likewise, the messaging system MAY use any suitable algorithm to
a message is "urgent". determine that a message is "urgent".
Messaging systems MAY use any algorithm for determining the Messaging systems MAY use any algorithm for determining the
approporiate message-context-class for a specific message. Systems approporiate message-context-class for a specific message. Systems
which use Internet Mail SHOULD use the contents of the which use Internet Mail SHOULD use the contents of the
Message-Context header [6] (defined in RFC 3458) if present as a hint Message-Context header [6] (defined in RFC 3458) if present as a hint
to make a context determination. Note that a messaging system does to make a context determination. Note that a composed messaging
not need to support a given context in order to generate system does not need to support a given context in order to generate
notifications identified with that context. notifications identified with that context.
3.6 Subscriber generation of SUBSCRIBE requests 3.6 Subscriber generation of SUBSCRIBE requests
Subscriber User Agents will typically SUBSCRIBE to message summary Subscriber User Agents will typically SUBSCRIBE to message summary
information for a period of hours or days, and automatically attempt information for a period of hours or days, and automatically attempt
to re-SUBSCRIBE well before the subscription is completely expired. to re-SUBSCRIBE well before the subscription is completely expired.
If re-subscription fails, the Subscriber SHOULD periodically retry If re-subscription fails, the Subscriber SHOULD periodically retry
again until a subscription is successful, taking care to backoff to again until a subscription is successful, taking care to backoff to
avoid network congestion. If a subscription has expired, new avoid network congestion. If a subscription has expired, new
re-subscriptions MUST use a new Call-ID. re-subscriptions MUST use a new Call-ID.
The Subscriber SHOULD SUBSCRIBE to that user's message summaries The Subscriber SHOULD SUBSCRIBE to that user's message summaries
whenever a new user becomes associated with the device (a new login). whenever a new user becomes associated with the device (a new login).
The Subscriber MAY also explicitly fetch the current status at any The Subscriber MAY also explicitly fetch the current status at any
time. The subscriber SHOULD renew its subscription immediately after time. The subscriber SHOULD renew its subscription immediately after
a reboot, or when the subscriber's network connectivity has just been a reboot, or when the subscriber's network connectivity has just been
re-established. re-established.
The Subscriber MUST be prepared to receive and process a NOTIFY with The Subscriber MUST be prepared to receive and process a NOTIFY with
new state immediately after sending a new SUBSCRIBE, a SUBSCRIBE, new state immediately after sending a new SUBSCRIBE, a SUBSCRIBE
renewal, an unSUBSCRIBE or a fetch; or at any time during the renewal, an unsubscribe, or a fetch; or at any time during the
subscription. subscription.
When a user de-registers from a device (logoff, power down of a When a user de-registers from a device (logoff, power down of a
mobile device, etc.), subscribers SHOULD unsubscribe by sending a mobile device, etc.), subscribers SHOULD unsubscribe by sending a
SUBSCRIBE message with an Expires header of zero. SUBSCRIBE message with an Expires header of zero.
3.7 Notifier processing of SUBSCRIBE requests 3.7 Notifier processing of SUBSCRIBE requests
When a SIP Messaging System receives SUBSCRIBE messages with the When a SIP Messaging System receives SUBSCRIBE messages with the
message-summary event-type, it SHOULD authenticate the subscription message-summary event-type, it SHOULD authenticate the subscription
skipping to change at page 8, line 16 skipping to change at page 8, line 19
implementations with heavy interactive use. Note that timely implementations with heavy interactive use. Note that timely
notification which results in a change of overall state (messages notification which results in a change of overall state (messages
waiting or not), and notification of newly added messages is probably waiting or not), and notification of newly added messages is probably
more significant to the end user than a notification of newly deleted more significant to the end user than a notification of newly deleted
messages which do not affect the overall message waiting state (e.g. messages which do not affect the overall message waiting state (e.g.
there are still new messages). there are still new messages).
Notifiers SHOULD NOT generate NOTIFY requests more frequently than Notifiers SHOULD NOT generate NOTIFY requests more frequently than
once per second. once per second.
3.12 State Agents 3.12 State Agents and Lists
A Subscriber MAY use an "alias" or "group" in the Request-URI of a A Subscriber MAY use an "alias" or "group" in the Request-URI of a
subscription if that name is significant to the messaging system. subscription if that name is significant to the messaging system.
Implementers MAY create a service which consolidates and summarizes Implementers MAY create a service which consolidates and summarizes
NOTIFYs from many Contacts. This document does not preclude NOTIFYs from many Contacts. This document does not preclude
implementations from building state agents which support this event implementations from building state agents which support this event
package. package. One way to implement such a service is with the event list
extension [10].
3.13 Behavior of a Proxy Server 3.13 Behavior of a Proxy Server
There are no additional requirements on a SIP Proxy, other than to There are no additional requirements on a SIP Proxy, other than to
transparently forward the SUBSCRIBE and NOTIFY methods as required in transparently forward the SUBSCRIBE and NOTIFY methods as required in
SIP. However, Proxies SHOULD allow non-SIP URLs. Proxies and SIP. However, Proxies SHOULD allow non-SIP URLs. Proxies and
Redirect servers SHOULD be able to direct the SUBSCRIBE request to an Redirect servers SHOULD be able to direct the SUBSCRIBE request to an
appropriate messaging server User Agent. Proxies are encouraged to appropriate messaging notifier User Agent.
support routing to Contacts based on the the method of the request
and the existence of a feature="voice-mail" parameter in an
Accept-Contact header (as specified in the caller preferences
specification).
4. Examples of Usage 4. Examples of Usage
4.1 Example Message Flow 4.1 Example Message Flow
The examples shown below are for informational purposes only. For a The examples shown below are for informational purposes only. For a
normative description of the event package, please see sections 3 and normative description of the event package, please see sections 3 and
5 of this document. 5 of this document.
In the example call flow below, Alice's IP phone subscribes to the In the example call flow below, Alice's IP phone subscribes to the
skipping to change at page 14, line 17 skipping to change at page 14, line 17
SIP/2.0 200 OK SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923 To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442 From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 19:35:08 GMT Date: Mon, 10 Jul 2000 19:35:08 GMT
Call-Id: 1349882@alice-phone.example.com Call-Id: 1349882@alice-phone.example.com
CSeq: 56 NOTIFY CSeq: 56 NOTIFY
Event: message-summary Event: message-summary
Content-Length: 0 Content-Length: 0
4.2 Example Usage with Caller Preferences 4.2 Example Usage with Callee Capabilities
The use of caller preferences is optional but encouraged. If caller The use of callee capabilities is optional but encouraged. If callee
preferences is used, a messaging server MAY REGISTER a Contact with capabilities is used, a messaging notifier MAY REGISTER a Contact
an appropriate methods and events tag as shown in the example below. with an appropriate methods and events tag as shown in the example
To further distinguish itself, the messaging server MAY also REGISTER below. To further distinguish itself, the messaging notifier MAY
as a Contact with the feature="voice-mail" tag. An example of this also REGISTER as a Contact with the feature="msgserver" tag. An
kind of registration follows below. example of this kind of registration follows below.
REGISTER sip:sip3-sj.example.com SIP/2.0 REGISTER sip:sip3-sj.example.com SIP/2.0
To: <sip:alice@example.com> To: <sip:alice@example.com>
From: <sip:alice@example.com>;tag=4442 From: <sip:alice@example.com>;tag=4442
... ...
Contact: <sip:alice@vm13-sj.example.com> Contact: <sip:alice@vm13-sj.example.com>
;feature="voice-mail";methods="SUBSCRIBE" ;msgserver="true";methods="SUBSCRIBE"
;events="message-summary" ;events="message-summary"
The following SUBSCRIBE message would find the Contact which
registered in the example above.
SUSBCRIBE sip:alice@example.com SIP/2.0
...
Accept: application/simple-message-summary
Event: message-summary
Accept-Contact: *;feature="voice-mail"
5. Formal Syntax 5. Formal Syntax
The following syntax specification uses the augmented Backus-Naur The following syntax specification uses the augmented Backus-Naur
Form (BNF) as described in RFC-2234 [5]. Form (BNF) as described in RFC-2234 [5].
5.1 New event-package definition 5.1 New event-package definition
This document defines a new event-package with the package name: This document defines a new event-package with the package name:
message-summary message-summary
5.2 Body Format Syntax 5.2 Body Format Syntax
The formal syntax for application/simple-message-summary is below: The formal syntax for application/simple-message-summary is below:
messsage-summary = msg-status-line CRLF messsage-summary = msg-status-line CRLF
[msg-account CRLF] [msg-account CRLF]
skipping to change at page 15, line 35 skipping to change at page 15, line 28
opt-msg-headers = CRLF 1*(extension-header CRLF) opt-msg-headers = CRLF 1*(extension-header CRLF)
newmsgs = msgcount newmsgs = msgcount
oldmsgs = msgcount oldmsgs = msgcount
new-urgentmsgs = msgcount new-urgentmsgs = msgcount
old-urgentmsgs = msgcount old-urgentmsgs = msgcount
msgcount = 1*DIGIT ; MUST NOT exceed 2^32-1 msgcount = 1*DIGIT ; MUST NOT exceed 2^32-1
6. Security Considerations 6. Security Considerations
Message Summaries and optional message bodies contain information Message summaries and optional message bodies contain information
which is typically very privacy sensitive. At minimum, subscriptions which is typically very privacy sensitive. At minimum, subscriptions
to this event package SHOULD be authenticated and properly to this event package SHOULD be authenticated and properly
authorized. Furthermore, notifications SHOULD be encrypted and authorized. Furthermore, notifications SHOULD be encrypted and
integrity protected using either end-to-end mechanisms, or the integrity protected using either end-to-end mechanisms, or the
hop-by-hop protection afforded messages sent to SIPS URIs. hop-by-hop protection afforded messages sent to SIPS URIs.
Additional security considerations are covered in SIP [1] and SIP Additional and privacy security considerations are discussed in
Events [2]. detail in SIP [1] and SIP Events [2].
7. IANA Considerations 7. IANA Considerations
7.1 SIP Event Package Registration for message-summary 7.1 SIP Event Package Registration for message-summary
Package name: message-summary Package name: message-summary
Type: package Type: package
Contact: [Mahy] Contact: [Mahy]
skipping to change at page 17, line 5 skipping to change at page 16, line 39
Additional information: Additional information:
1. Magic number(s): N/A 1. Magic number(s): N/A
2. File extension(s): N/A 2. File extension(s): N/A
3. Macintosh file type code: N/A 3. Macintosh file type code: N/A
8. Revision history 8. Revision history
8.1 Open Issues ** Note to the RFC editor: please remove this entire section upon
publication. **
1. Need to update the caller-preference section to reflect whatever 8.1 Changes from draft-ietf-sipping-mwi-01 and -02
the replacement will be for feature="voice-mail".
2. Would be nice to add a pointer to the "collections" work 1. Updated the caller-preference section (now the callee
capabilities section) to reflect the split of these drafts and
the new tag ;msgserver="true".
2. Added some text in the overview to further clarify how message
notifiers can be composed/decomposed with media processing.
3. Add a pointer to the event-list extension.
8.2 Changes from draft-ietf-sipping-mwi-00 8.2 Changes from draft-ietf-sipping-mwi-00
1. Replaced the "media types" concept with message contexts. This is 1. Replaced the "media types" concept with message contexts. This is
a better semantic match than what was in the draft before, and a better semantic match than what was in the draft before, and
also controls extensibility and change control in a single also controls extensibility and change control in a single
document. The list of valid message-context-classes are document. The list of valid message-context-classes are
voice-message, fax-message, pager-message, multimedia-message, voice-message, fax-message, pager-message, multimedia-message,
text-message, and none. text-message, and none.
skipping to change at page 19, line 17 skipping to change at page 19, line 7
Ilya Slain came up with the initial format of the text body contained Ilya Slain came up with the initial format of the text body contained
in this document. He was previously listed as a co-author, however, in this document. He was previously listed as a co-author, however,
he is no longer reachable. he is no longer reachable.
10. Acknowledgments 10. Acknowledgments
Thanks to Dan Wing, Dave Oran, Bill Foster, Steve Levy, Denise Thanks to Dan Wing, Dave Oran, Bill Foster, Steve Levy, Denise
Caballero-McCann, Jeff Michel, Priti Patil, Satyender Khatter, Bich Caballero-McCann, Jeff Michel, Priti Patil, Satyender Khatter, Bich
Nguyen, Manoj Bhatia, David Williams, and Bryan Byerly of Cisco; Nguyen, Manoj Bhatia, David Williams, and Bryan Byerly of Cisco;
Jonathan Rosenberg and Adam Roach of Dynamicsoft; Eric Burger of Jonathan Rosenberg and Adam Roach of Dynamicsoft; Eric Burger of
Snowshore; and Eric Tremblay of Mediatrix. Snowshore; Nir Chen of iComverse, and Eric Tremblay of Mediatrix.
Normative References Normative References
[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[2] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [2] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[4] Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol [4] Rosenberg, J., "Indicating User Agent Capabilities in the
(SIP) Caller Preferences and Callee Capabilities", Session Initiation Protocol (SIP)",
draft-ietf-sip-callerprefs-07 (work in progress), November 2002. draft-ietf-sip-callee-caps-00 (work in progress), June 2003.
[5] Crocker, D. and P. Overell, "Augmented BNF for Syntax [5] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[6] Burger, E., Candell, E., Eliot, C. and G. Klyne, "Message [6] Burger, E., Candell, E., Eliot, C. and G. Klyne, "Message
Context for Internet Mail", RFC 3458, January 2003. Context for Internet Mail", RFC 3458, January 2003.
Informational References Informational References
[7] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet Mail [7] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet Mail
- version 2", RFC 2421, September 1998. - version 2", RFC 2421, September 1998.
[8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, November Extensions (MIME) Part Two: Media Types", RFC 2046, November
1996. 1996.
[9] Resnick, P., "Internet Message Format", RFC 2822, April 2001. [9] Resnick, P., "Internet Message Format", RFC 2822, April 2001.
[10] Telcordia, "GR-506: Signaling for Analog Interfaces, Issue 1, [10] Rosenberg, J., Roach, A. and B. Campbell, "A Session Initiation
Protocol (SIP) Event Notification Extension for Resource
Lists", draft-ietf-simple-event-list-04 (work in progress),
June 2003.
[11] Telcordia, "GR-506: Signaling for Analog Interfaces, Issue 1,
Revision 1", Nov 1996. Revision 1", Nov 1996.
Author's Address Author's Address
Rohan Mahy Rohan Mahy
Cisco Systems, Inc. Cisco Systems, Inc.
101 Cooper Street 101 Cooper Street
Santa Cruz, CA 95060 Santa Cruz, CA 95060
USA USA
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/