draft-ietf-sipping-mwi-03.txt   draft-ietf-sipping-mwi-04.txt 
SIPPING WG R. Mahy SIPPING WG R. Mahy
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: December 27, 2003 June 28, 2003 Expires: May 31, 2004 Dec 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-03.txt draft-ietf-sipping-mwi-04.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 December 27, 2003. This Internet-Draft will expire on May 31, 2004.
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 document describes 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.
skipping to change at page 2, line 25 skipping to change at page 2, line 25
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 and Lists . . . . . . . . . . . . . . . . . . . 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 Callee Capabilities . . . . . . . . . . . 14 4.2 Example Usage with Callee Capabilities and Caller
Preferences . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 14 5.2 Body Format Syntax . . . . . . . . . . . . . . . . . . . . . 15
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 . . . . . 15 7.1 SIP Event Package Registration for message-summary . . . . . 16
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 . . . . . . . . . . . . . . . . . . . . . . 17
8.1 Changes from draft-ietf-sipping-mwi-01 and -02 . . . . . . . 16 8.1 Changes from draft-ietf-sipping-mwi-03 . . . . . . . . . . . 17
8.2 Changes from draft-ietf-sipping-mwi-00 . . . . . . . . . . . 17 8.2 Changes from draft-ietf-sipping-mwi-01 and -02 . . . . . . . 17
8.3 Changes from draft-mahy-sipping-mwi-00 . . . . . . . . . . . 17 8.3 Changes from draft-ietf-sipping-mwi-00 . . . . . . . . . . . 17
8.4 Changes from draft-mahy-sip-mwi-01 . . . . . . . . . . . . . 17 8.4 Changes from draft-mahy-sipping-mwi-00 . . . . . . . . . . . 18
8.5 Changes from draft-mahy-sip-mwi-00 . . . . . . . . . . . . . 18 8.5 Changes from draft-mahy-sip-mwi-01 . . . . . . . . . . . . . 18
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 8.6 Changes from draft-mahy-sip-mwi-00 . . . . . . . . . . . . . 18
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 18 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 19
Normative References . . . . . . . . . . . . . . . . . . . . 19 Normative References . . . . . . . . . . . . . . . . . . . . 19
Informational References . . . . . . . . . . . . . . . . . . 19 Informational References . . . . . . . . . . . . . . . . . . 20
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 (which that messages are waiting, such as playing a special dial tone (which
in telephone networks is called message-waiting dial tone), lighting in telephone networks is called message-waiting dial tone), lighting
a light or indicator on the phone, displaying icons or text, or some a light or indicator on the phone, displaying icons or text, or some
combination. combination.
Message-waiting dial tone is similar to but distinct from stutter Message-waiting dial tone is similar to but distinct from stutter
dial tone. Both are defined in GR-506 [11]. dial tone. Both are defined in GR-506 [12].
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
skipping to change at page 3, line 46 skipping to change at page 3, line 46
this environment, as it preserves the user mobility and rendezvous this environment, as it preserves the user mobility and rendezvous
features which SIP provides. 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.(This Notifier could be messaging account's messages have changed.(This Notifier could be
composed with a User Agent that provides a real-time media interface composed with a User Agent that provides a real-time media interface
to send or receive messages, or it could be a standalone entitiy.) to send or receive messages, or it could be a standalone entitiy.)
The Notifier sends message summary information in the body of a The Notifier sends a message summary in the body of a NOTIFY, encoded
NOTIFY, encoded in a new MIME type defined later in this document. A in a new MIME type defined later in this document. A User Agent can
User Agent can also explicitly fetch the current status. 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 notifier(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 based on on an appropriate SIP Proxy, or dynamically discovered based on
registered callee capabilities [4]. (For more information on usage requested caller preferences [4] and registered callee capabilities
with callee capabilities, see Section 4.2) [5]. (For more information on usage 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 7 skipping to change at page 5, line 7
document MUST be assumed. document MUST be assumed.
The format specified in this proposal attempts to separate orthogonal The format specified in this proposal attempts to separate orthogonal
attributes of messages as much as possible. Messages are separated attributes of messages as much as possible. Messages are separated
by message-context-class (for example: voice-message, fax-message, by message-context-class (for example: voice-message, fax-message,
pager-message, multimedia-message, text-message, and none); by pager-message, multimedia-message, text-message, and none); by
message status (new and old); and by urgent and non-urgent type. message status (new and old); and by urgent and non-urgent type.
The text format begins with a simple status line, and optionally a The text format begins with a simple status line, and optionally a
summary line per message-context-class. Message-context-classes are summary line per message-context-class. Message-context-classes are
defined in [6]. For each message-context-class, the total number of defined in [7]. For each message-context-class, the total number of
new and old messages is reported in the new and old fields. new and old messages is reported in the new and old fields.
In some cases, detailed message summaries are not available. The In some cases, detailed message summaries are not available. The
status line allows messaging systems or messaging gateways to provide status line allows messaging systems or messaging gateways to provide
the traditional boolean message waiting notification. the traditional boolean message waiting notification.
Messages-Waiting: yes Messages-Waiting: yes
If the Request-URI or To header in a message-summary subscription If the Request-URI or To header in a message-summary subscription
corresponds to a group or collection of individual messaging corresponds to a group or collection of individual messaging
skipping to change at page 5, line 40 skipping to change at page 5, line 40
After the summary, the format can optionally list a summary count of After the summary, the format can optionally list a summary count of
urgent messages. In the next example there are one new and three old urgent messages. In the next example there are one new and three old
voice messages, none of the new messages are urgent, but one of the voice messages, none of the new messages are urgent, but one of the
old messages is. All counters have a maximum value of 4,294,967,295 old messages is. All counters have a maximum value of 4,294,967,295
((2^32) - 1). Notifiers MUST NOT generate a request with a larger ((2^32) - 1). Notifiers MUST NOT generate a request with a larger
value. Subscribers MUST treat a larger value as 2^32-1. value. Subscribers MUST treat a larger value as 2^32-1.
Voice-Message: 1/3 (0/1) Voice-Message: 1/3 (0/1)
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 [10]-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 in this body 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.
skipping to change at page 6, line 18 skipping to change at page 6, line 18
an implementation issue of the messaging system. However, the an implementation issue of the messaging system. However, the
messaging notifier MUST NOT consider a message "old" merely because messaging notifier MUST NOT consider a message "old" merely because
it generated a notification, as this could prevent another it generated a notification, as this could prevent another
subscription from accurately receiving message-summary notifications. subscription from accurately receiving message-summary notifications.
Likewise, the messaging system MAY use any suitable algorithm to Likewise, the messaging system MAY use any suitable algorithm to
determine that 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 [7] (defined in RFC 3458) if present as a hint
to make a context determination. Note that a composed messaging to make a context determination. Note that a composed messaging
system does 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
skipping to change at page 8, line 27 skipping to change at page 8, line 27
once per second. once per second.
3.12 State Agents and Lists 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. One way to implement such a service is with the event list package. One way to implement such a service is with the event list
extension [10]. extension [11].
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 notifier User Agent. appropriate messaging notifier User Agent.
4. Examples of Usage 4. Examples of Usage
skipping to change at page 14, line 6 skipping to change at page 14, line 6
Contact: <sip:alice@vmail.example.com> Contact: <sip:alice@vmail.example.com>
Event: message-summary Event: message-summary
Subscription-State: terminated;reason=timeout Subscription-State: terminated;reason=timeout
Content-Type: application/simple-message-summary Content-Type: application/simple-message-summary
Content-Length: 99 Content-Length: 99
Messages-Waiting: yes Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2) Voice-Message: 4/8 (1/2)
A10: Subscriber -> Notifier A14: Subscriber -> Notifier
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 Callee Capabilities 4.2 Example Usage with Callee Capabilities and Caller Preferences
The use of callee capabilities is optional but encouraged. If callee The use of callee capabilities is optional but encouraged. If callee
capabilities is used, a messaging notifier MAY REGISTER a Contact capabilities is used, a messaging notifier MAY REGISTER a Contact
with an appropriate methods and events tag as shown in the example with an appropriate methods and events tag as shown in the example
below. To further distinguish itself, the messaging notifier MAY below. To further distinguish itself, the messaging notifier MAY
also REGISTER as a Contact with the feature="msgserver" tag. An also REGISTER as a Contact with the actor="msg-taker" tag. An
example of this 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>
;msgserver="true";methods="SUBSCRIBE" ;actor="msg-taker";methods="SUBSCRIBE"
;events="message-summary" ;automata;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: *;automata;actor="msg-taker"
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 [6].
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 the application/simple-message-summary MIME
type is described below:
messsage-summary = msg-status-line CRLF messsage-summary = msg-status-line CRLF
[msg-account CRLF] [msg-account CRLF]
[*(msg-summary-line CRLF)] [*(msg-summary-line CRLF)]
[ *opt-msg-headers ] [ *opt-msg-headers ]
msg-status-line = "Messages-Waiting" HCOLON msg-status msg-status-line = "Messages-Waiting" HCOLON msg-status
msg-status = "yes" / "no" msg-status = "yes" / "no"
msg-account = "Message-Account" HCOLON Account-URI msg-account = "Message-Account" HCOLON Account-URI
Account-URI = SIP-URI / SIPS-URI / absoluteURI Account-URI = SIP-URI / SIPS-URI / absoluteURI
skipping to change at page 16, line 15 skipping to change at page 16, line 25
7.2 MIME Registration for application/simple-message-summary 7.2 MIME Registration for application/simple-message-summary
MIME media type name: application MIME media type name: application
MIME subtype name: simple-message-summary MIME subtype name: simple-message-summary
Required parameters: none. Required parameters: none.
Optional parameters: none. Optional parameters: none.
Encoding considerations: This type is only defined for transfer Encoding considerations: This MIME type was designed for
via SIP [1]. use with protocols which can carry binary-encoded data.
Although the format of this MIME type is similar to RFC2822,
it is not identical. (Specifically, line folding rules are
SIP-specific and included URIs can contain non-ASCII
characters.) Protocols which do not carry binary data
(which have line length or character-set restrictions
for example) MUST use a reversible transfer encoding
(such as base64) to carry this MIME type.
Security considerations: See the "Security Considerations" Security considerations: See the "Security Considerations"
section in this document. section in this document.
Interoperability considerations: none Interoperability considerations: none
Published specification: This document. Published specification: This document.
Applications which use this media: The simple-message-summary Applications which use this media: The simple-message-summary
application subtype supports the exchange of message waiting and application subtype supports the exchange of message waiting and
skipping to change at page 16, line 34 skipping to change at page 17, line 4
Applications which use this media: The simple-message-summary Applications which use this media: The simple-message-summary
application subtype supports the exchange of message waiting and application subtype supports the exchange of message waiting and
message summary information in SIP networks. message summary information in SIP networks.
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
** Note to the RFC editor: please remove this entire section upon ** Note to the RFC editor: please remove this entire section upon
publication. ** publication. **
8.1 Changes from draft-ietf-sipping-mwi-01 and -02 8.1 Changes from draft-ietf-sipping-mwi-03
1. Updated MIME type registration to permit transfer encoding using
any binary-clean encoding.
2. Changed caller preferences and callee capabilities usage to be
consistent with change from msg-server="true" to
actor="msg-taker".
8.2 Changes from draft-ietf-sipping-mwi-01 and -02
1. Updated the caller-preference section (now the callee 1. Updated the caller-preference section (now the callee
capabilities section) to reflect the split of these drafts and capabilities section) to reflect the split of these drafts and
the new tag ;msgserver="true". the new tag ;msgserver="true".
2. Added some text in the overview to further clarify how message 2. Added some text in the overview to further clarify how message
notifiers can be composed/decomposed with media processing. notifiers can be composed/decomposed with media processing.
3. Add a pointer to the event-list extension. 3. Add a pointer to the event-list extension.
8.2 Changes from draft-ietf-sipping-mwi-00 8.3 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.
2. Completely updated the syntax to follow that of SIP instead of 2. Completely updated the syntax to follow that of SIP instead of
the previously more restrictive (and somewhat arbitrary) syntax. the previously more restrictive (and somewhat arbitrary) syntax.
skipping to change at page 17, line 30 skipping to change at page 18, line 11
3. Added a Message-Account field in the body format to provide the 3. Added a Message-Account field in the body format to provide the
specific account name which corresponds to the notification when specific account name which corresponds to the notification when
forking or state agents are used with group aliases (or forking or state agents are used with group aliases (or
collections). collections).
4. Changed caller preferences example to exclude methods="SUBSCRIBE" 4. Changed caller preferences example to exclude methods="SUBSCRIBE"
in the SUBSCRIBE request (removed redundant information). in the SUBSCRIBE request (removed redundant information).
5. Changed examples to be consistent with IESG recommendations 5. Changed examples to be consistent with IESG recommendations
8.3 Changes from draft-mahy-sipping-mwi-00 8.4 Changes from draft-mahy-sipping-mwi-00
1. Updated references and split into normative and informational 1. Updated references and split into normative and informational
2. Removed normative behavior now specified in Events 2. Removed normative behavior now specified in Events
3. Updated to address the event package sections now specified in 3. Updated to address the event package sections now specified in
Events. Events.
4. Added the Subscription-State header field to the examples and 4. Added the Subscription-State header field to the examples and
removed the Event header field from responses. removed the Event header field from responses.
5. Removed redundant BNF 5. Removed redundant BNF
6. Simplified text on how to choose the media type. For Internet 6. Simplified text on how to choose the media type. For Internet
Mail, this now references the Message-Context header. Mail, this now references the Message-Context header.
8.4 Changes from draft-mahy-sip-mwi-01 8.5 Changes from draft-mahy-sip-mwi-01
1. This document is now formatted as a SIP Event Package as defined 1. This document is now formatted as a SIP Event Package as defined
in Section 4 of RFC 3265 (SIP Events) [2]. in Section 4 of RFC 3265 (SIP Events) [2].
2. The event-package name is now "message-summary", to allow for 2. The event-package name is now "message-summary", to allow for
other bodies to extend the package. other bodies to extend the package.
3. The "urgent" token was missing from the BNF. 3. The "urgent" token was missing from the BNF.
8.5 Changes from draft-mahy-sip-mwi-00 8.6 Changes from draft-mahy-sip-mwi-00
This draft greatly simplifies and shortens the -00 version. This draft greatly simplifies and shortens the -00 version.
1. The generic behavior of SUBSCRIBE/NOTIFY is now greatly clarified 1. The generic behavior of SUBSCRIBE/NOTIFY is now greatly clarified
in SIP Events [2] and made consistent with PINT and SIP for in SIP Events [2] and made consistent with PINT and SIP for
presence. This message waiting draft is now consistent with SIP presence. This message waiting draft is now consistent with SIP
Events. Events.
2. The XML format has been removed due to lack of immediate 2. The XML format has been removed due to lack of immediate
interest. At a future date, similar functionality may be added interest. At a future date, similar functionality may be added
skipping to change at page 19, line 21 skipping to change at page 20, line 5
[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., "Indicating User Agent Capabilities in the [4] Rosenberg, J., Schulzrinne, H. and P. Kyzivat, "Caller
Preferences and Callee Capabilities for the Session Initiation
Protocol (SIP)", draft-ietf-sip-callerprefs-08 (work in
progress), March 2003.
[5] Rosenberg, J., "Indicating User Agent Capabilities in the
Session Initiation Protocol (SIP)", Session Initiation Protocol (SIP)",
draft-ietf-sip-callee-caps-00 (work in progress), June 2003. draft-ietf-sip-callee-caps-00 (work in progress), June 2003.
[5] Crocker, D. and P. Overell, "Augmented BNF for Syntax [6] 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 [7] 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 [8] 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 [9] 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. [10] Resnick, P., "Internet Message Format", RFC 2822, April 2001.
[10] Rosenberg, J., Roach, A. and B. Campbell, "A Session Initiation [11] Rosenberg, J., Roach, A. and B. Campbell, "A Session Initiation
Protocol (SIP) Event Notification Extension for Resource Protocol (SIP) Event Notification Extension for Resource
Lists", draft-ietf-simple-event-list-04 (work in progress), Lists", draft-ietf-simple-event-list-04 (work in progress),
June 2003. June 2003.
[11] Telcordia, "GR-506: Signaling for Analog Interfaces, Issue 1, [12] 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/