Network Working Group R. Mahy
Request for Comments: 3842 Cisco Systems, Inc.
Category: Standards Track August 2004
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)
会话启动协议（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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（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.
本文档描述了会话启动协议（SIP）事件包，该事件包将消息等待状态和消息摘要从消息传递系统传送到感兴趣的用户代理。
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 . . . . . . . . . . . . . . . . . . . . . . . . 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
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[3]中的说明进行解释。
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].
消息等待拨号音与口吃拨号音相似但不同。GR-506[11]中定义了这两种情况。
The methods in the SIP [1] base specification were only designed to solve the problem of session initiation for multimedia sessions, and rendezvous. Since Message Waiting Indication is really status information orthogonal to a session, it was not clear how an IP telephone acting as a SIP User Agent would implement comparable functionality. Members of the telephony community viewed this as a shortcoming of SIP.
SIP[1]基本规范中的方法仅设计用于解决多媒体会话的会话启动和集合问题。由于消息等待指示实际上是与会话正交的状态信息，因此不清楚作为SIP用户代理的IP电话将如何实现类似的功能。电话社区的成员认为这是SIP的一个缺点。
Users want the useful parts of the functionality they have using traditional analog, mobile, and PBX telephones. It is also desirable to provide comparable functionality in a flexible way that allows for more customization and new features. SIP Specific Event Notification (RFC 3265 -- SIP Events) [2] is an appropriate mechanism to use in this environment, as it preserves the user mobility and rendezvous features which SIP provides.
用户希望使用传统的模拟电话、移动电话和PBX电话获得功能的有用部分。还希望以灵活的方式提供类似的功能，以允许更多的定制和新功能。SIP特定事件通知（RFC 3265--SIP事件）[2]是在这种环境中使用的合适机制，因为它保留了SIP提供的用户移动性和会合特性。
Using SIP-Specific Event Notification, a Subscriber User Agent (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 user's messaging system then notifies the Subscriber each time the messaging account's messages have changed. (This Notifier could be composed with a User Agent that provides a real-time media interface to send or receive messages, or it could be a stand-alone entity.) The Notifier sends a message summary 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.
使用SIP特定事件通知，订户用户代理（通常是IP电话或SIP软件用户代理）订阅其消息的状态。然后，代表用户的消息传递系统的SIP用户代理在消息传递帐户的消息每次更改时通知订户。（此通知程序可以由提供发送或接收消息的实时媒体接口的用户代理组成，也可以是独立实体。）通知程序在通知正文中发送消息摘要，以本文档后面定义的新MIME类型编码。用户代理还可以显式获取当前状态。
A SIP User Agent MAY subscribe to multiple accounts (distinguished by the Request URI). Multiple SIP User Agents MAY subscribe to the same account.
SIP用户代理可以订阅多个帐户（通过请求URI区分）。多个SIP用户代理可以订阅同一个帐户。
Before any subscriptions or notifications are sent, each interested User Agent must be made aware of its messaging notifier(s). This MAY be manually configured on interested User Agents, manually configured on an appropriate SIP Proxy, or dynamically discovered based on
在发送任何订阅或通知之前，必须让每个感兴趣的用户代理知道其消息通知程序。这可以在感兴趣的用户代理上手动配置，在适当的SIP代理上手动配置，或者基于
requested caller preferences [4] and registered callee capabilities [5]. (For more information on usage with callee capabilities, see Section 4.2)
请求的呼叫者首选项[4]和注册的被呼叫者功能[5]。（有关使用被叫方功能的更多信息，请参阅第4.2节）
This document defines a SIP Event Package as defined in RFC 3265 [2]. The event-package token name for this package is:
本文档定义了RFC 3265[2]中定义的SIP事件包。此包的事件包令牌名称为：
"message-summary"
“消息摘要”
This package does not define any event package parameters.
此包未定义任何事件包参数。
This package does not define any SUBSCRIBE bodies.
此包不定义任何订阅主体。
Subscriptions to this event package MAY range from minutes to weeks. Subscriptions in hours or days are more typical and are RECOMMENDED. The default subscription duration for this event package is one hour.
对此事件包的订阅可能在几分钟到几周之间。以小时或天为单位的订阅更为典型，建议使用。此事件包的默认订阅持续时间为一小时。
A simple text-based format is proposed to prevent an undue burden on low-end user agents, for example, inexpensive IP phones with no display. Although this format is text-based, it is intended for machine consumption only.
提出了一种简单的基于文本的格式，以防止对低端用户代理（例如，没有显示器的廉价IP电话）造成过度负担。尽管此格式是基于文本的，但它仅用于机器使用。
A future extension MAY define other NOTIFY bodies. If no "Accept" header is present in the SUBSCRIBE, the body type defined in this document MUST be assumed.
将来的扩展可能会定义其他通知机构。如果订阅中没有“Accept”标题，则必须采用本文档中定义的正文类型。
The format specified in this proposal attempts to separate orthogonal attributes of messages as much as possible. Messages are separated by message-context-class (for example: voice-message, fax-message, pager-message, multimedia-message, text-message, and none), by message status (new and old), and urgent and non-urgent type.
本提案中指定的格式试图尽可能地分离消息的正交属性。消息按消息上下文类（例如：语音消息、传真消息、寻呼机消息、彩信、文本消息和无）、消息状态（新消息和旧消息）以及紧急和非紧急类型进行分隔。
The text format begins with a simple status line, and optionally a summary line per message-context-class. Message-context-classes are defined in [7]. For each message-context-class, the total number of new and old messages is reported in the new and old fields.
文本格式以一个简单的状态行开始，每个消息上下文类可以选择一个摘要行。[7]中定义了消息上下文类。对于每个消息上下文类，在new和old字段中报告新消息和旧消息的总数。
In some cases, detailed message summaries are not available. The status line allows messaging systems or messaging gateways to provide the traditional boolean message waiting notification.
在某些情况下，无法提供详细的消息摘要。状态行允许消息传递系统或消息传递网关提供传统的布尔消息等待通知。
Messages-Waiting: yes
等待消息：是
If the Request-URI or To header in a message-summary subscription corresponds to a group or collection of individual messaging accounts, the notifier MUST specify to which account the message-summary body corresponds. Note that the account URI MUST NOT be delimited with angle brackets ("<" and ">").
如果消息摘要订阅中的请求URI或To标头对应于单个消息帐户的组或集合，则通知程序必须指定消息摘要正文对应的帐户。请注意，帐户URI不能用尖括号（“<”和“>”）分隔。
Message-Account: sip:alice@example.com
Message-Account: sip:alice@example.com
In the example that follows, more than boolean message summary information is available to the User Agent. There are two new and four old fax messages.
在下面的示例中，用户代理可以使用不止一个布尔消息摘要信息。有两条新传真和四条旧传真。
Fax-Message: 2/4
传真：2/4
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 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 ((2^32) - 1). Notifiers MUST NOT generate a request with a larger value. Subscribers MUST treat a larger value as 2^32-1.
摘要之后，格式可以选择列出紧急消息的摘要计数。在下一个示例中，有一条新语音消息和三条旧语音消息，没有一条新消息是紧急消息，但有一条旧消息是紧急消息。所有计数器的最大值为4294967295（（2^32）-1）。通知程序不得生成具有较大值的请求。订阅者必须将较大的值视为2^32-1。
Voice-Message: 1/3 (0/1)
Voice-Message: 1/3 (0/1)
Optionally, after the summary counts, the messaging systems MAY append RFC 2822 style message headers [9], which further describe newly added messages. Message headers MUST NOT be included in an initial NOTIFY, as new messages could be essentially unbounded in size. Message headers included in subsequent notifications MUST only correspond to messages added since the previous notification for that subscription. A messaging system which includes message headers in a NOTIFY MUST provide an administrator configurable mechanism to select which headers are sent. Headers likely for inclusion are To, From, Date, Subject, and Message-ID. Note that the formatting of these headers in this body is identical to that of SIP extension-headers, not the (similar) format defined in RFC 2822.
可选地，在汇总计数之后，消息传递系统可以附加RFC 2822样式的消息头[9]，其进一步描述新添加的消息。消息头不能包含在初始通知中，因为新消息的大小基本上是无限的。后续通知中包含的消息头必须仅与自上次通知该订阅后添加的消息相对应。在NOTIFY中包含消息头的消息传递系统必须提供管理员可配置的机制来选择要发送的消息头。可能包含的标头为To、From、Date、Subject和Message-ID。请注意，此正文中这些标头的格式与SIP扩展标头的格式相同，而不是RFC 2822中定义的（类似）格式。
Implementations which generate large notifications are reminded to follow the message size restrictions for unreliable transports articulated in Section 18.1.1 of SIP [1].
提醒生成大型通知的实现遵守SIP[1]第18.1.1节中阐述的不可靠传输的消息大小限制。
Mapping local message state to new/old message status and urgency is an implementation issue of the messaging system. However, the
将本地消息状态映射到新/旧消息状态和紧急性是消息传递系统的一个实现问题。但是,
messaging notifier MUST NOT consider a message "old" merely because it generated a notification, as this could prevent another subscription from accurately receiving message-summary notifications. Likewise, the messaging system MAY use any suitable algorithm to determine that a message is "urgent".
消息通知器不能只考虑消息“旧”，因为它生成了通知，因为这可能阻止另一个订阅准确接收消息摘要通知。类似地，消息传递系统可以使用任何合适的算法来确定消息是“紧急的”。
Messaging systems MAY use any algorithm for determining the appropriate message-context-class for a specific message. Systems which use Internet Mail SHOULD use the contents of the Message-Context header [7] (defined in RFC 3458) if present as a hint to make a context determination. Note that a composed messaging system does not need to support a given context in order to generate notifications identified with that context.
消息传递系统可以使用任何算法来确定特定消息的适当消息上下文类。使用Internet邮件的系统应使用消息上下文标头[7]（在RFC 3458中定义）的内容（如果作为提示提供），以进行上下文确定。请注意，组合消息传递系统不需要支持给定的上下文来生成用该上下文标识的通知。
Subscriber User Agents will typically SUBSCRIBE to message summary information for a period of hours or days, and automatically attempt to re-SUBSCRIBE well before the subscription is completely expired. If re-subscription fails, the Subscriber SHOULD periodically retry again until a subscription is successful, taking care to backoff to avoid network congestion. If a subscription has expired, new re-subscriptions MUST use a new Call-ID.
订户用户代理通常会在数小时或数天内订阅消息摘要信息，并在订阅完全过期之前自动尝试重新订阅。如果重新订阅失败，订阅服务器应定期重试，直到订阅成功，注意退避以避免网络拥塞。如果订阅已过期，则新的重新订阅必须使用新的Call-ID。
The Subscriber SHOULD SUBSCRIBE to that user's message summaries whenever a new user becomes associated with the device (a new login). The Subscriber MAY also explicitly fetch the current status at any time. The subscriber SHOULD renew its subscription immediately after a reboot, or when the subscriber's network connectivity has just been re-established.
当新用户与设备关联（新登录）时，订户应订阅该用户的消息摘要。订户还可以在任何时候显式获取当前状态。订户应在重新启动后或刚重新建立订户的网络连接时立即续订。
The Subscriber MUST be prepared to receive and process a NOTIFY with new state immediately after sending a new SUBSCRIBE, a SUBSCRIBE renewal, an unsubscribe, a fetch, or at any other time during the subscription.
订阅方必须准备好在发送新订阅、订阅续订、取消订阅、获取或订阅期间的任何其他时间后立即接收和处理具有新状态的通知。
When a user de-registers from a device (logoff, power down of a mobile device, etc.), subscribers SHOULD unsubscribe by sending a SUBSCRIBE message with an Expires header of zero.
当用户从设备注销（注销、移动设备断电等）时，订阅者应通过发送一条Expires报头为零的SUBSCRIBE消息来取消订阅。
When a SIP Messaging System receives SUBSCRIBE messages with the message-summary event-type, it SHOULD authenticate the subscription request. If authentication is successful, the Notifier MAY limit the duration of the subscription to an administrator defined amount of time as described in SIP Events [2].
当SIP消息传递系统接收到消息摘要事件类型的订阅消息时，它应该对订阅请求进行身份验证。如果身份验证成功，通知程序可以将订阅的持续时间限制为SIP事件[2]中所述的管理员定义的时间量。
Immediately after a subscription is accepted, the Notifier MUST send a NOTIFY with the current message summary information. This allows the Subscriber to resynchronize its state. This initial synchronization NOTIFY MUST NOT include the optional RFC 2822 style message headers [8].
接受订阅后，通知程序必须立即发送包含当前消息摘要信息的通知。这允许订阅服务器重新同步其状态。此初始同步通知不得包括可选的RFC 2822样式的消息头[8]。
When the status of the messages changes sufficiently for a messaging account to change the number of new or old messages, the Notifier SHOULD send a NOTIFY message to all active subscribers of that account. NOTIFY messages sent to subscribers of a group or alias, MUST contain the message account name in the notification body.
当消息状态发生足够的变化，消息帐户可以更改新消息或旧消息的数量时，通知程序应向该帐户的所有活动订户发送通知消息。发送给组或别名的订阅者的通知邮件必须在通知正文中包含邮件帐户名。
A Messaging System MAY send a NOTIFY with an "Expires" header of "0" and a "Subscription-State" header of "terminated" before a graceful shutdown.
在正常关机之前，消息传递系统可能会发送“Expires”标头为“0”且“Subscription State”标头为“terminated”的通知。
Upon receipt of a valid NOTIFY request, the subscriber SHOULD immediately render the message status and summary information to the end user in an implementation specific way.
收到有效的通知请求后，订户应立即以特定于实现的方式向最终用户提供消息状态和摘要信息。
The Subscriber MUST be prepared to receive NOTIFYs from different Contacts corresponding to the same SUBSCRIBE. (The SUBSCRIBE may have been forked).
订阅者必须准备好接收来自同一订阅对应的不同联系人的NOTIFY。（认购可能已经分出）。
Forked requests are allowed for this event type and may install multiple subscriptions. The Subscriber MAY render multiple summaries corresponding to the same account directly to the user, or MAY merge them as described below.
此事件类型允许分叉请求，并且可以安装多个订阅。订户可以直接向用户呈现对应于同一帐户的多个摘要，或者可以如下所述合并它们。
If any of the "Messages-Waiting" status lines report "yes", then the merged state is "yes"; otherwise the merged state is "no".
如果任何“消息等待”状态行报告“是”，则合并状态为“是”；否则，合并状态为“否”。
The Subscriber MAY merge summary lines in an implementation-specific way if all notifications contain at least one msg-summary line.
如果所有通知至少包含一个msg摘要行，则订阅服务器可以以特定于实现的方式合并摘要行。
A Notifier MAY choose to hold NOTIFY requests in "quarantine" for a short administrator-defined period (seconds or minutes) when the message status is changing rapidly. Requests in the quarantine which become invalid are replaced by newer notifications, thus reducing the total volume of notifications. This behavior is encouraged for
当消息状态快速变化时，通知程序可以选择在管理员定义的短时间内（秒或分钟）将通知请求保持在“隔离”状态。隔离区中无效的请求将被更新的通知替换，从而减少通知的总量。这种行为是值得鼓励的
implementations with heavy interactive use. Note that timely notification resulting in a change of overall state (messages waiting or not) and notification of newly added messages is probably more significant to the end user than a notification of newly deleted messages which do not affect the overall message waiting state (e.g., there are still new messages).
大量交互使用的实现。注意，对最终用户而言，导致整体状态（消息等待或不等待）变化的及时通知和新添加消息的通知可能比不影响整体消息等待状态（例如，仍有新消息）的新删除消息的通知更重要。
Notifiers SHOULD NOT generate NOTIFY requests more frequently than once per second.
通知程序生成通知请求的频率不应超过每秒一次。
A Subscriber MAY use an "alias" or "group" in the Request-URI of a subscription if that name is significant to the messaging system. Implementers MAY create a service which consolidates and summarizes NOTIFYs from many Contacts. This document does not preclude implementations from building state agents which support this event package. One way to implement such a service is with the event list extension [10].
订户可以在订阅的请求URI中使用“别名”或“组”，如果该名称对消息传递系统很重要。实现者可以创建一个服务来合并和汇总来自多个联系人的NOTIFY。本文档不排除构建支持此事件包的状态代理的实现。实现此类服务的一种方法是使用事件列表扩展[10]。
There are no additional requirements on a SIP Proxy, other than to transparently forward the SUBSCRIBE and NOTIFY methods as required in SIP. However, Proxies SHOULD allow non-SIP URLs. Proxies and Redirect servers SHOULD be able to direct the SUBSCRIBE request to an appropriate messaging notifier User Agent.
除了按照SIP中的要求透明地转发SUBSCRIBE和NOTIFY方法外，SIP代理没有其他要求。但是，代理应该允许非SIP URL。代理和重定向服务器应该能够将订阅请求定向到适当的消息通知程序用户代理。
The examples shown below are for informational purposes only. For a normative description of the event package, please see sections 3 and 5 of this document.
以下示例仅供参考。有关活动包的规范性说明，请参见本文件第3节和第5节。
In the example call flow below, Alice's IP phone subscribes to the status of Alice's messages. Via headers are omitted for clarity.
在下面的示例呼叫流中，Alice的IP电话订阅Alice消息的状态。为清晰起见，省略了通孔标题。
Subscriber Notifier
| |
| A1: SUBSCRIBE (new) |
|---------------------->|
| A2: 200 OK |
|<----------------------|
| |
| A3: NOTIFY (sync) |
|<----------------------|
| A4: 200 OK |
|---------------------->|
| |
| |
| A5: NOTIFY (change) |
|<----------------------|
| A6: 200 OK |
|---------------------->|
| |
| |
| A7: (re)SUBSCRIBE |
|---------------------->|
| A8: 200 OK |
|<----------------------|
| |
| A9: NOTIFY (sync) |
|<----------------------|
| A10: 200 OK |
|---------------------->|
| |
| |
| A11: (un)SUBSCRIBE |
|---------------------->|
| A12: 200 OK |
|<----------------------|
| |
| A13: NOTIFY (sync) |
|<----------------------|
| A14: 200 OK |
|---------------------->|
Subscriber Notifier
| |
| A1: SUBSCRIBE (new) |
|---------------------->|
| A2: 200 OK |
|<----------------------|
| |
| A3: NOTIFY (sync) |
|<----------------------|
| A4: 200 OK |
|---------------------->|
| |
| |
| A5: NOTIFY (change) |
|<----------------------|
| A6: 200 OK |
|---------------------->|
| |
| |
| A7: (re)SUBSCRIBE |
|---------------------->|
| A8: 200 OK |
|<----------------------|
| |
| A9: NOTIFY (sync) |
|<----------------------|
| A10: 200 OK |
|---------------------->|
| |
| |
| A11: (un)SUBSCRIBE |
|---------------------->|
| A12: 200 OK |
|<----------------------|
| |
| A13: NOTIFY (sync) |
|<----------------------|
| A14: 200 OK |
|---------------------->|
A1: Subscriber (Alice's phone) -> Notifier (Alice's voicemail gateway) Subscribe to Alice's message summary status for 1 day.
A1：订户（Alice的电话）->通知者（Alice的语音邮件网关）订阅Alice的消息摘要状态1天。
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 03:55:06 GMT
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 03:55:06 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 4 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 86400
Accept: application/simple-message-summary
Content-Length: 0
Call-Id: 1349882@alice-phone.example.com
CSeq: 4 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 86400
Accept: application/simple-message-summary
Content-Length: 0
A2: Notifier -> Subscriber
A2: Notifier -> Subscriber
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 03:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 4 SUBSCRIBE
Expires: 86400
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 03:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 4 SUBSCRIBE
Expires: 86400
Content-Length: 0
A3: Notifier -> Subscriber
(immediate synchronization of current state:
2 new and 8 old [2 urgent] messages)
A3: Notifier -> Subscriber
(immediate synchronization of current state:
2 new and 8 old [2 urgent] messages)
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 03:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 20 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 99
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 03:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 20 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 99
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 2/8 (0/2)
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 2/8 (0/2)
A4: Subscriber -> Notifier
A4: Subscriber -> Notifier
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 03:55:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 20 NOTIFY
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 03:55:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 20 NOTIFY
Content-Length: 0
A5: Notifier -> Subscriber This is a notification of new messages. Some headers from each of the new messages are appended.
A5:Notifier->Subscriber这是新消息的通知。每个新消息的一些头都会被追加。
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 04:28:53 GMT
Contact: <sip:alice@vmail.example.com>
Call-ID: 1349882@alice-phone.example.com
CSeq: 31 NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 503
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 04:28:53 GMT
Contact: <sip:alice@vmail.example.com>
Call-ID: 1349882@alice-phone.example.com
CSeq: 31 NOTIFY
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 503
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
To: <alice@atlanta.example.com>
From: <bob@biloxi.example.com>
Subject: carpool tomorrow?
Date: Sun, 09 Jul 2000 21:23:01 -0700
Priority: normal
Message-ID: 13784434989@vmail.example.com
To: <alice@atlanta.example.com>
From: <bob@biloxi.example.com>
Subject: carpool tomorrow?
Date: Sun, 09 Jul 2000 21:23:01 -0700
Priority: normal
Message-ID: 13784434989@vmail.example.com
To: <alice@example.com>
From: <cathy-the-bob@example.com>
Subject: HELP! at home ill, present for me please
Date: Sun, 09 Jul 2000 21:25:12 -0700
Priority: urgent
Message-ID: 13684434990@vmail.example.com
To: <alice@example.com>
From: <cathy-the-bob@example.com>
Subject: HELP! at home ill, present for me please
Date: Sun, 09 Jul 2000 21:25:12 -0700
Priority: urgent
Message-ID: 13684434990@vmail.example.com
A6: Subscriber -> Notifier
A6: Subscriber -> Notifier
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 04:28:53 GMT
Call-ID: 1349882@alice-phone.example.com
CSeq: 31 NOTIFY
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 04:28:53 GMT
Call-ID: 1349882@alice-phone.example.com
CSeq: 31 NOTIFY
Content-Length: 0
A7: Subscriber -> Notifier Refresh subscription.
A7：订阅服务器->通知程序刷新订阅。
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 15:55:06 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 8 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 86400
Accept: application/simple-message-summary
Content-Length: 0
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 15:55:06 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 8 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 86400
Accept: application/simple-message-summary
Content-Length: 0
A8: Notifier -> Subscriber
A8: Notifier -> Subscriber
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 15:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 8 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Expires: 86400
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 15:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 8 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Expires: 86400
Content-Length: 0
A9: Notifier -> Subscriber
(immediate synchronization of current state)
A9: Notifier -> Subscriber
(immediate synchronization of current state)
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 15:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 47 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 99
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 15:55:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 47 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 99
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
A10: Subscriber -> Notifier
A10: Subscriber -> Notifier
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 15:55:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 47 NOTIFY
Contact: <sip:alice@vmail.example.com>
Date: Mon, 10 Jul 2000 15:55:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 47 NOTIFY
Contact: <sip:alice@vmail.example.com>
A11: Subscriber -> Notifier Un-subscribe after "alice" logs out.
A11:Subscriber->Notifier在“alice”注销后取消订阅。
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 19:35:06 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 17 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 0
Accept: application/simple-message-summary
Content-Length: 0
SUBSCRIBE sip:alice@vmail.example.com SIP/2.0
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 19:35:06 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 17 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Event: message-summary
Expires: 0
Accept: application/simple-message-summary
Content-Length: 0
A12: Notifier -> Subscriber
A12: Notifier -> Subscriber
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 19:35:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 17 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Expires: 0
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=4442
From: <sip:alice@example.com>;tag=78923
Date: Mon, 10 Jul 2000 19:35:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 17 SUBSCRIBE
Contact: <sip:alice@alice-phone.example.com>
Expires: 0
Content-Length: 0
A13: Notifier -> Subscriber (immediate synchronization of current state, which the subscriber can now ignore)
A13：通知程序->订阅服务器（当前状态的即时同步，订阅服务器现在可以忽略）
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 19:35:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 56 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: terminated;reason=timeout
Content-Type: application/simple-message-summary
Content-Length: 99
NOTIFY sip:alice@alice-phone.example.com SIP/2.0
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 19:35:07 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 56 NOTIFY
Contact: <sip:alice@vmail.example.com>
Event: message-summary
Subscription-State: terminated;reason=timeout
Content-Type: application/simple-message-summary
Content-Length: 99
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
Messages-Waiting: yes
Message-Account: sip:alice@vmail.example.com
Voice-Message: 4/8 (1/2)
A14: Subscriber -> Notifier
A14: Subscriber -> Notifier
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 19:35:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 56 NOTIFY
Event: message-summary
Content-Length: 0
SIP/2.0 200 OK
To: <sip:alice@example.com>;tag=78923
From: <sip:alice@example.com>;tag=4442
Date: Mon, 10 Jul 2000 19:35:08 GMT
Call-Id: 1349882@alice-phone.example.com
CSeq: 56 NOTIFY
Event: message-summary
Content-Length: 0
The use of callee capabilities is optional but encouraged. If callee capabilities are used, a messaging notifier MAY REGISTER a Contact with an appropriate methods and events tag as shown in the example below. To further distinguish itself, the messaging notifier MAY also REGISTER as a Contact with the actor="msg-taker" tag. An example of this kind of registration follows below.
被调用方功能的使用是可选的，但鼓励使用。如果使用了被叫方功能，消息通知程序可以使用适当的方法和事件标记注册联系人，如下例所示。为了进一步区分自己，消息通知程序还可以注册为带有actor=“msg taker”标记的联系人。下面是此类注册的一个示例。
REGISTER sip:sip3-sj.example.com SIP/2.0
To: <sip:alice@example.com>
From: <sip:alice@example.com>;tag=4442
...
Contact: <sip:alice@vm13-sj.example.com>
;actor="msg-taker";methods="SUBSCRIBE"
;automata;events="message-summary"
REGISTER sip:sip3-sj.example.com SIP/2.0
To: <sip:alice@example.com>
From: <sip:alice@example.com>;tag=4442
...
Contact: <sip:alice@vm13-sj.example.com>
;actor="msg-taker";methods="SUBSCRIBE"
;automata;events="message-summary"
The following SUBSCRIBE message would find the Contact which registered in the example above.
下面的SUBSCRIBE消息将找到在上面的示例中注册的联系人。
SUBSCRIBE sip:alice@example.com SIP/2.0
...
Accept: application/simple-message-summary
Event: message-summary
Accept-Contact: *;automata;actor="msg-taker"
SUBSCRIBE sip:alice@example.com SIP/2.0
...
Accept: application/simple-message-summary
Event: message-summary
Accept-Contact: *;automata;actor="msg-taker"
The following syntax specification uses the augmented Backus-Naur Form (BNF) as described in RFC 2234 [6].
以下语法规范使用RFC 2234[6]中所述的增广巴科斯诺尔形式（BNF）。
This document defines a new event-package with the package name:
本文档定义了一个新的事件包，其包名为：
message-summary
消息摘要
The formal syntax for the application/simple-message-summary MIME type is described below. The message-context-class production is defined in Section 6.2 of RFC 3458 [7]. Note that all productions described here are case insensitive.
下面描述应用程序/简单消息摘要MIME类型的正式语法。RFC 3458[7]第6.2节定义了消息上下文类生成。注意，这里描述的所有产品都不区分大小写。
message-summary = msg-status-line CRLF
[msg-account CRLF]
[*(msg-summary-line CRLF)]
[ *opt-msg-headers ]
message-summary = msg-status-line CRLF
[msg-account CRLF]
[*(msg-summary-line CRLF)]
[ *opt-msg-headers ]
msg-status-line = "Messages-Waiting" HCOLON msg-status
msg-status = "yes" / "no"
msg-account = "Message-Account" HCOLON Account-URI
Account-URI = SIP-URI / SIPS-URI / absoluteURI
msg-status-line = "Messages-Waiting" HCOLON msg-status
msg-status = "yes" / "no"
msg-account = "Message-Account" HCOLON Account-URI
Account-URI = SIP-URI / SIPS-URI / absoluteURI
msg-summary-line = message-context-class HCOLON newmsgs SLASH oldmsgs [ LPAREN new-urgentmsgs SLASH old-urgentmsgs RPAREN ]
msg summary line=消息上下文类HCOLON newmsgs SLASH oldmsgs[LPAREN new urgentmsgs SLASH old urgentmsgs RPAREN]
opt-msg-headers = CRLF 1*(extension-header CRLF)
opt msg headers=CRLF 1*（扩展头CRLF）
newmsgs = msgcount
oldmsgs = msgcount
new-urgentmsgs = msgcount
old-urgentmsgs = msgcount
msgcount = 1*DIGIT ; MUST NOT exceed 2^32-1
newmsgs = msgcount
oldmsgs = msgcount
new-urgentmsgs = msgcount
old-urgentmsgs = msgcount
msgcount = 1*DIGIT ; MUST NOT exceed 2^32-1
Message summaries and optional message bodies contain information which is typically very privacy sensitive. At a minimum, subscriptions to this event package SHOULD be authenticated and properly authorized. Furthermore, notifications SHOULD be encrypted and integrity protected using either end-to-end mechanisms, or the hop-by-hop protection afforded messages sent to SIPS URIs.
消息摘要和可选消息正文包含通常对隐私非常敏感的信息。对此事件包的订阅至少应经过身份验证和正确授权。此外，应使用端到端机制或为发送到SIPS URI的消息提供逐跳保护的方式对通知进行加密和完整性保护。
Additional and privacy security considerations are discussed in detail in SIP [1] and SIP Events [2].
SIP[1]和SIP事件[2]中详细讨论了其他和隐私安全注意事项。
Package name: message-summary
包名称：消息摘要
Type: package
类型：包装
Contact: [Mahy]
联系人：[Mahy]
Published Specification: This document.
已发布规范：本文件。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: simple-message-summary
MIME子类型名称：简单消息摘要
Required parameters: none.
所需参数：无。
Optional parameters: none.
可选参数：无。
Encoding considerations: This MIME type was designed for use with protocols which can carry binary-encoded data. Although the format of this MIME type is similar to RFC 2822, 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.
编码注意事项：此MIME类型设计用于可携带二进制编码数据的协议。尽管此MIME类型的格式类似于RFC 2822，但并不完全相同。（具体来说，行折叠规则是特定于SIP的，包含的URI可以包含非ASCII字符。）不携带二进制数据（例如具有行长度或字符集限制）的协议必须使用可逆传输编码（例如base64）来携带此MIME类型。
Security considerations: See the "Security Considerations" section in this document.
安全注意事项：请参阅本文档中的“安全注意事项”部分。
Interoperability considerations: none
互操作性注意事项：无
Published specification: This document.
已发布规范：本文件。
Applications which use this media: The simple-message-summary application subtype supports the exchange of message waiting and message summary information in SIP networks.
使用此媒体的应用程序：简单消息摘要应用程序子类型支持在SIP网络中交换消息等待和消息摘要信息。
Additional information:
其他信息：
1. Magic number(s): N/A
1. 幻数：不适用
2. File extension(s): N/A
2. 文件扩展名：不适用
3. Macintosh file type code: N/A
3. Macintosh文件类型代码：不适用
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, he is no longer reachable.
Ilya Slain提出了本文件中文本正文的初始格式。他以前被列为合著者，但现在已经联系不上他了。
Thanks to Dan Wing, Dave Oran, Bill Foster, Steve Levy, Denise Caballero-McCann, Jeff Michel, Priti Patil, Satyender Khatter, Bich Nguyen, Manoj Bhatia, David Williams, and Bryan Byerly of Cisco, Jonathan Rosenberg and Adam Roach of Dynamicsoft, Eric Burger of Snowshore, Nir Chen of Comverse, and Eric Tremblay of Mediatrix.
感谢思科公司的丹·温、戴夫·奥兰、比尔·福斯特、史蒂夫·利维、丹尼斯·卡巴莱罗·麦肯、杰夫·米歇尔、普里蒂·帕蒂尔、萨蒂安·卡特、比奇·阮、马诺·巴蒂亚、大卫·威廉姆斯和布莱恩·拜尔利、Dynamicsoft公司的乔纳森·罗森伯格和亚当·罗奇、斯诺肖尔公司的埃里克·伯格、康维斯公司的尼尔·陈和Mediatrix公司的埃里克·特雷姆布雷。
[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.
[1] Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
[2] Roach, A.B., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002.
[2] Roach，A.B.，“会话启动协议（SIP）-特定事件通知”，RFC3265，2002年6月。
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[3] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[4] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller Preferences for the Session Initiation Protocol (SIP)", RFC 3841, August 2004.
[4] Rosenberg，J.，Schulzrinne，H.，和P.Kyzivat，“会话启动协议（SIP）的呼叫方偏好”，RFC 38412004年8月。
[5] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)", RFC 3840, August 2004.
[5] Rosenberg，J.，Schulzrinne，H.，和P.Kyzivat，“指出会话启动协议（SIP）中的用户代理功能”，RFC 3840，2004年8月。
[6] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[6] Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[7] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message Context for Internet Mail", RFC 3458, January 2003.
[7] Burger，E.，Candell，E.，Eliot，C.，和G.Klyne，“互联网邮件的消息上下文”，RFC 3458，2003年1月。
[8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[8] Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第二部分：媒体类型”，RFC 20461996年11月。
[9] Resnick, P., Ed., "Internet Message Format", RFC 2822, April 2001.
[9] Resnick，P.，Ed.，“互联网信息格式”，RFC 2822，2001年4月。
[10] Rosenberg, J., Roach, A.B., and B. Campbell, "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists", Work in Progress, June 2003.
[10] Rosenberg，J.，Roach，A.B.和B.Campbell，“资源列表的会话启动协议（SIP）事件通知扩展”，正在进行的工作，2003年6月。
[11] Telcordia, "GR-506: Signaling for Analog Interfaces, Issue 1, Revision 1", Nov 1996.
[11] Telcordia，“GR-506：模拟接口信号，第1期，第1版”，1996年11月。
Rohan Mahy Cisco Systems, Inc. 5617 Scotts Valley Drive, Suite 200 Scotts Valley, CA 95066 USA
Rohan Mahy Cisco Systems，Inc.地址：美国加利福尼亚州斯科茨谷大道5617号斯科茨谷大道200号套房，邮编：95066
EMail: rohan@cisco.com
EMail: rohan@cisco.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。