Internet Engineering Task Force (IETF) J. Rosenberg
Request for Comments: 6914 jdrosen.net
Category: Informational April 2013
ISSN: 2070-1721
Internet Engineering Task Force (IETF) J. Rosenberg
Request for Comments: 6914 jdrosen.net
Category: Informational April 2013
ISSN: 2070-1721
SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)
简单变得简单：使用会话启动协议（SIP）的即时消息和状态的IETF规范概述
Abstract
摘要
The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP). Collectively, these specifications are known as SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE). This document serves as a guide to the SIMPLE suite of specifications. It categorizes the specifications, explains what each is for, and how they relate to each other.
IETF已经产生了许多与会话启动协议（SIP）的状态和即时消息相关的规范。这些规范统称为SIP，用于即时消息和状态利用扩展（SIMPLE）。本文档作为一套简单规范的指南。它对规范进行分类，解释每个规范的用途以及它们之间的关系。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6914.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6914.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Core Protocol Machinery . . . . . . . . . . . . . . . . . 4
2.2. Presence Documents . . . . . . . . . . . . . . . . . . . . 5
2.3. Privacy and Policy . . . . . . . . . . . . . . . . . . . . 6
2.4. Provisioning . . . . . . . . . . . . . . . . . . . . . . . 7
2.5. Federation . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6. Optimizations . . . . . . . . . . . . . . . . . . . . . . 8
3. Instant Messaging . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Page Mode . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2. Session Mode . . . . . . . . . . . . . . . . . . . . . . . 10
3.3. IM Chat Rooms . . . . . . . . . . . . . . . . . . . . . . 11
3.4. IM Features . . . . . . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
6. Informative References . . . . . . . . . . . . . . . . . . . . 12
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Core Protocol Machinery . . . . . . . . . . . . . . . . . 4
2.2. Presence Documents . . . . . . . . . . . . . . . . . . . . 5
2.3. Privacy and Policy . . . . . . . . . . . . . . . . . . . . 6
2.4. Provisioning . . . . . . . . . . . . . . . . . . . . . . . 7
2.5. Federation . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6. Optimizations . . . . . . . . . . . . . . . . . . . . . . 8
3. Instant Messaging . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Page Mode . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2. Session Mode . . . . . . . . . . . . . . . . . . . . . . . 10
3.3. IM Chat Rooms . . . . . . . . . . . . . . . . . . . . . . 11
3.4. IM Features . . . . . . . . . . . . . . . . . . . . . . . 11
4. Security Considerations . . . . . . . . . . . . . . . . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
6. Informative References . . . . . . . . . . . . . . . . . . . . 12
The IETF has produced many specifications related to Presence and Instant Messaging with the Session Initiation Protocol (SIP) [RFC3261]. Collectively, these specifications are known as SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE). These specifications cover topics ranging from protocols for subscription and publication to presence document formats to protocols for managing privacy preferences. The large number of specifications can make it hard to figure out exactly what SIMPLE is, what specifications cover it, what functionality it provides, and how these specifications relate to each other.
IETF已经制定了许多与会话启动协议（SIP）[RFC3261]的状态和即时消息相关的规范。这些规范统称为SIP，用于即时消息和状态利用扩展（SIMPLE）。这些规范涵盖的主题从订阅和发布协议到状态文档格式，再到管理隐私首选项的协议。大量的规范可能使我们很难准确地理解什么是简单的，什么规范涵盖了它，它提供了什么功能，以及这些规范如何相互关联。
This document serves to address these problems. It provides an enumeration of the protocols that make up the SIMPLE suite of specifications from IETF. It categorizes them into related areas of functionality, briefly explains the purpose of each, and how the specifications relate to each other. Each specification also includes a letter that designates its category [RFC2026]. These values are:
本文件旨在解决这些问题。它提供了构成IETF规范简单套件的协议的枚举。它将它们分类为相关的功能领域，简要解释了每个领域的用途，以及规范之间的关系。每个规范还包括一个字母，用于指定其类别[RFC2026]。这些值是：
S: Standards Track
S:标准轨道
E: Experimental
E:实验性的
B: Best Current Practice
B:目前的最佳做法
I: Informational
I:信息性
SIMPLE provides for both presence and instant messaging (IM) capabilities. Though both of these fit underneath the broad SIMPLE umbrella, they are well separated from each other and are supported by different sets of specifications. That is a key part of the SIMPLE story; presence is much broader than just IM, and it enables communications using voice and video along with IM.
SIMPLE同时提供状态和即时消息（IM）功能。虽然这两种产品都适合放在宽大的简单伞下，但它们彼此之间有很好的分离，并由不同的规格支持。这是简单故事的关键部分；存在的范围比即时通讯要广泛得多，它支持使用语音和视频以及即时通讯进行通信。
The SIMPLE presence specifications can be broken up into:
简单存在规范可分为：
o The core protocol machinery, which provides the actual SIP extensions for subscriptions, notifications, and publications
o 核心协议机制，为订阅、通知和发布提供实际的SIP扩展
o Presence documents, which are XML documents that provide for rich presence and are carried by the core protocol machinery
o 状态文档，是提供丰富状态的XML文档，由核心协议机制承载
o Privacy and policy, which are documents for expressing privacy preferences about how those presence documents are to be shown (or not shown) to other users
o 隐私和策略，这些文档用于表达关于如何向其他用户显示（或不显示）这些状态文档的隐私偏好
o Provisioning, which describes how users manage their privacy policies, buddy lists, and other pieces of information required for SIMPLE presence to work
o Provisioning，它描述了用户如何管理他们的隐私策略、好友列表以及简单状态工作所需的其他信息
o Optimizations, which are improvements in the core protocol machinery that were defined to improve the performance of SIMPLE, particularly on wireless links
o 优化，这是对核心协议机制的改进，定义该机制是为了提高SIMPLE的性能，特别是在无线链路上
RFC 6665, SIP-Specific Event Notification (S): [RFC6665] defines the SUBSCRIBE and NOTIFY methods for SIP, forming the core of the SIP event notification framework. To actually use the framework, extensions need to be defined for specific event packages. Presence is defined as an event package [RFC3856] within this framework. Packages exist for other, non-presence related functions, such as message waiting indicators and dialog state changes.
RFC 6665，SIP特定事件通知：[RFC6665]定义SIP的订阅和通知方法，构成SIP事件通知框架的核心。要实际使用该框架，需要为特定的事件包定义扩展。存在被定义为此框架内的事件包[RFC3856]。包用于其他与状态无关的功能，如消息等待指示器和对话框状态更改。
RFC 3856, A Presence Event Package for the Session Initiation Protocol (SIP) (S): [RFC3856] defines an event package for indicating user presence through SIP. Through this package, a SIP user agent (UA) can ask to be notified of the presence state of a presentity (presence entity). The contents of the NOTIFY messages in this package are presence documents discussed in Section 2.2.
RFC 3856，会话启动协议（SIP）的存在事件包：[RFC3856]定义了一个用于通过SIP指示用户存在的事件包。通过该包，SIP用户代理（UA）可以请求通知存在实体（存在实体）的存在状态。本文件包中通知消息的内容为第2.2节讨论的状态文件。
RFC 4662, A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists (S): [RFC4662] defines an extension to [RFC3265] (which has now been obsoleted by RFC 6665) that allows a client to subscribe to a list of resources using a single subscription. The server, called a Resource List Server (RLS), will "expand" the subscription and subscribe to each individual member of the list. Its primary usage with presence is to allow subscriptions to "buddy lists". Without RFC 4662, a UA would need to subscribe to each presentity individually. With RFC 4662, they can have a single subscription to all buddies. A user can manage the entries in their buddy list using the provisioning mechanisms in Section 2.4.
RFC 4662，资源列表的会话启动协议（SIP）事件通知扩展：[RFC4662]定义了[RFC3265]（现已被RFC 6665淘汰）的扩展，该扩展允许客户端使用单个订阅订阅资源列表。该服务器称为资源列表服务器（RLS），将“扩展”订阅并订阅列表中的每个成员。它的主要用途是允许订阅“好友列表”。如果没有RFC 4662，UA将需要单独订阅每个实体。使用RFC4662，他们可以订阅所有好友。用户可以使用第2.4节中的配置机制管理好友列表中的条目。
RFC 5367, Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP) (S): [RFC5367] is very similar to RFC 4662. It allows a client to subscribe to a list of resources using a single subscription. However, with this mechanism, the list is included within the body of the SUBSCRIBE request. In RFC 4662, it is provisioned ahead of time on the server.
RFC 5367，会话启动协议（SIP）（S）中包含的请求资源列表的订阅：[RFC5367]与RFC 4662非常相似。它允许客户端使用单个订阅订阅资源列表。但是，通过这种机制，列表包含在订阅请求的主体中。在RFC 4662中，它是在服务器上提前设置的。
RFC 3903, Session Initiation Protocol (SIP) Extension for Event State Publication (S): [RFC3903] defines the PUBLISH method. With this method, a UA can publish its current state for any event package, including the presence event package. Once an agent publishes its presence state, the presence server would send notifications of this state change using RFC 3856.
RFC 3903，事件状态发布的会话启动协议（SIP）扩展：[RFC3903]定义发布方法。使用此方法，UA可以发布任何事件包的当前状态，包括状态事件包。代理发布其状态后，状态服务器将使用RFC 3856发送此状态更改的通知。
Once a user has generated a subscription to presence using the core protocol machinery, they will receive notifications (SIP NOTIFY requests) that contain presence information. That presence information is in the form of an XML presence document. Several specifications have been defined to describe this document format, focusing on rich, multimedia presence.
一旦用户使用核心协议机制生成状态订阅，他们将收到包含状态信息的通知（SIP NOTIFY请求）。该状态信息是XML状态文档的形式。已经定义了几个规范来描述此文档格式，重点是丰富的多媒体呈现。
RFC 3863, Presence Information Data Format (PIDF) (S): [RFC3863] defines the baseline XML format for a presence document. It defines the concept of a tuple as representing a basic communication modality and defines a simple status for it (open or closed).
RFC 3863，状态信息数据格式（PIDF）：[RFC3863]定义状态文档的基线XML格式。它将元组的概念定义为表示基本通信模式，并为其定义一个简单的状态（打开或关闭）。
RFC 4479, A Data Model for Presence (S): [RFC4479] extends the basic model in RFC 3863. It introduces the concepts of device and person status and explains how these relate to each other. It describes how presence documents are used to represent communications systems states in a consistent fashion. More than RFC 3863, it defines what a presence document is and what it means.
RFC 4479，一个存在的数据模型：[RFC4479]扩展了RFC 3863中的基本模型。它介绍了设备和人员状态的概念，并解释了它们之间的关系。它描述了如何使用状态文档以一致的方式表示通信系统状态。与RFC3863相比，它定义了什么是状态文档及其含义。
RFC 4480, RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) (S): [RFC4480] adds many more attributes to the presence document schema, building upon the model in RFC 4479. It allows for indications of activities, moods, places and place types, icons, and indications of whether or not a user is idle.
RFC 4480，RPID:Presence Information Data Format（PIDF）（S）的丰富Presence扩展：[RFC4480]在RFC 4479中的模型基础上，向Presence文档模式添加了更多属性。它允许指示活动、情绪、地点和地点类型、图标以及用户是否空闲的指示。
RFC 4481, Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals (S): [RFC4481] adds attributes to the presence document schema, again building upon the model in RFC 4479. It allows documents to indicate status for the future or the past. For example, a user can indicate that they will be unavailable for voice communications from 2 p.m. to 3 p.m. due to a meeting.
RFC 4481，状态信息数据格式（PIDF）的定时状态扩展，用于指示过去和未来时间间隔的状态信息：[RFC4481]向状态文档模式添加属性，再次基于RFC 4479中的模型构建。它允许文档指示未来或过去的状态。例如，用户可以指出，由于会议原因，他们将无法在下午2点到3点之间进行语音通信。
RFC 4482, CIPID: Contact Information for the Presence Information Data Format (S): [RFC4482] adds attributes to the presence document schema for contact information, such as a vCard, display name, homepage, icon, or sound (such as the pronunciation of their name).
RFC 4482，CIPID：状态信息数据格式的联系人信息：[RFC4482]将联系人信息的属性添加到状态文档架构中，例如vCard、显示名称、主页、图标或声音（例如其名称的发音）。
RFC 5196, Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF) (S): [RFC5196] adds even more attributes to the presence document schema, this time to allow indication of capabilities for the user
RFC 5196，状态信息数据格式（PIDF）（S）的会话启动协议（SIP）用户代理功能扩展：[RFC5196]向状态文档模式添加了更多属性，这一次允许指示用户的功能
agent. For example, the extensions can indicate whether a UA supports audio and video, what SIP methods it supports, and so on.
代理人例如，扩展可以指示UA是否支持音频和视频，它支持哪些SIP方法，等等。
The rich presence capabilities defined by the specifications in Section 2.2 introduces a strong need for privacy preferences. Users must be able to approve or deny subscriptions to their presence and indicate what information such watchers can see. In SIMPLE, this is accomplished through policy documents uploaded to the presence server using the provisioning mechanisms in Section 2.4.
第2.2节中的规范定义了丰富的显示功能，这就引入了对隐私偏好的强烈需求。用户必须能够批准或拒绝订阅他们的状态，并指出这些观察者可以看到什么信息。简单地说，这是通过使用第2.4节中的配置机制上传到状态服务器的策略文档来实现的。
RFC 4745, Common Policy: A Document Format for Expressing Privacy Preferences (S): [RFC4745] defines a general XML framework for expressing privacy preferences for both geolocation information and presence information. It introduces the concepts of conditions, actions, and transformations that are applied to privacy-sensitive data. The common policy framework provides privacy safety, a property by which network error or version incompatibilities can never cause more information to be revealed to a watcher than the user would otherwise desire.
RFC 4745，《公共策略：表达隐私偏好的文档格式》：[RFC4745]定义了一个通用XML框架，用于表达地理位置信息和状态信息的隐私偏好。它介绍了应用于隐私敏感数据的条件、操作和转换的概念。公共策略框架提供了隐私安全性，网络错误或版本不兼容不会导致向观察者透露比用户希望的更多的信息。
RFC 5025, Presence Authorization Rules (S): [RFC5025] uses the framework of RFC 4745 to define a policy document format for describing presence-privacy policies. Besides basic yes/no approvals, this format allows a user to control what kind of information a watcher is allowed to see.
RFC 5025，状态授权规则：[RFC5025]使用RFC 4745的框架定义用于描述状态隐私策略的策略文档格式。除了基本的是/否批准外，此格式允许用户控制允许观察者查看的信息类型。
RFC 3857, A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) (S): [RFC3857], also known as watcherinfo, provides a mechanism for a user agent to find out what subscriptions are in place for a particular event package. Though it was defined to be used for any event package, it has particular applicability for presence. It is used to provide reactive authorization. With reactive authorization, a user gets alerted if someone tries to subscribe to their presence, so that they may provide an authorization decision. Watcherinfo is used to provide the alert that someone has subscribed to a user's presence.
RFC 3857是会话启动协议（SIP）（S）的观察者信息事件模板包：[RFC3857]，也称为watcherinfo，它为用户代理提供了一种机制，用于找出特定事件包的订阅。尽管它被定义为用于任何事件包，但它对存在性具有特殊的适用性。它用于提供反应式授权。使用被动授权，如果有人试图订阅他们的状态，用户会收到警报，以便他们可以提供授权决策。Watcherinfo用于提供有人已订阅用户状态的警报。
RFC 3858, An Extensible Markup Language (XML) Based Format for Watcher Information (S): [RFC3858] is the companion to RFC 3857. It specifies the XML format of watcherinfo that is carried in notifications for the event template package in RFC 3857.
RFC 3858是一种基于可扩展标记语言（XML）的观察者信息格式：[RFC3858]是RFC 3857的配套产品。它指定RFC3857中事件模板包的通知中携带的watcherinfo的XML格式。
Proper operation of a SIMPLE presence system requires that several pieces of data are correctly managed by the users and provisioned into the system. These include buddy lists (used by the resource list subscription mechanism in RFC 4662) and privacy policies (such as those described by the XML format in [RFC5025]).
简单呈现系统的正确操作要求用户正确管理多个数据段，并将其配置到系统中。这些包括好友列表（由RFC4662中的资源列表订阅机制使用）和隐私策略（如[RFC5025]中的XML格式所述）。
In SIMPLE, management of this data is handled by the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) [RFC4825]. XCAP is used by the user agent to manipulate buddy lists, privacy policy, and other data that is represented by XML documents stored on a server.
简单地说，此数据的管理由可扩展标记语言（XML）配置访问协议（XCAP）[RFC4825]处理。用户代理使用XCAP操作好友列表、隐私策略和其他数据，这些数据由存储在服务器上的XML文档表示。
RFC 4825, The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) (S): [RFC4825] specifies XCAP, a usage of HTTP that allows a user agent to manipulate the contents of XML documents stored on a server. It can be used to manipulate any kind of XML, and the protocol itself is independent of the particular schema of the data it is modifying. XML schemas have been defined for buddy lists, privacy policies, and offline presence status, allowing all of those to be managed by a user with XCAP.
RFC 4825，可扩展标记语言（XML）配置访问协议（XCAP）：[RFC4825]指定XCAP，一种允许用户代理操作存储在服务器上的XML文档内容的HTTP用法。它可以用来操作任何类型的XML，协议本身独立于它所修改的数据的特定模式。已经为好友列表、隐私策略和离线状态定义了XML模式，允许用户使用XCAP管理所有这些。
RFC 5875, An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package (S): [RFC5875] defines an extension to the SIP user agent configuration profile, allowing a user agent to learn about changes in its documents on an XCAP server. With this mechanism, there can be a change made by someone else to a buddy list or privacy policy document, and a UA will find out that a new version is available.
RFC 5875是一个可扩展标记语言（XML）配置访问协议（XCAP）差异事件包：[RFC5875]定义了SIP用户代理配置配置文件的扩展，允许用户代理了解其在XCAP服务器上的文档更改。通过这种机制，其他人可以更改好友列表或隐私政策文档，UA将发现新版本可用。
RFC 5874, An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources (S): [RFC5874] defines an XML format for indicating changes in XCAP documents. It makes use of an XML diff format defined in [RFC5261]. It is used in conjunction with [RFC5875] to alert a user agent of changes made by someone else to their provisioned data.
RFC 5874，一种用于指示XML配置访问协议（XCAP）资源更改的可扩展标记语言（XML）文档格式：[RFC5874]定义了一种用于指示XCAP文档更改的XML格式。它使用[RFC5261]中定义的XML差异格式。它与[RFC5875]结合使用，以提醒用户代理其他人对其提供的数据所做的更改。
RFC 4826, Extensible Markup Language (XML) Formats for Representing Resource Lists (S): [RFC4826] defines two XML document formats used to represent buddy lists. One is simply a list of users (or more generally, resources), and the other defines a buddy list whose membership is composed of a list of users or resources. These lists can be manipulated by XCAP, allowing a user to add or remove members from their buddy lists. The buddy list is also
RFC 4826，用于表示资源列表的可扩展标记语言（XML）格式：[RFC4826]定义了两种用于表示好友列表的XML文档格式。一个是简单的用户列表（或者更一般地说是资源），另一个定义了一个好友列表，其成员资格由用户或资源列表组成。这些列表可以由XCAP操作，允许用户从好友列表中添加或删除成员。好友名单也很重要
accessed by the resource list server specified in RFC 4662 for processing resource list subscriptions.
由RFC 4662中指定的用于处理资源列表订阅的资源列表服务器访问。
RFC 4827, An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents (S): [RFC4827] defines an XCAP usage that allows a user to store an "offline" presence document. This is a presence status that is used by a presence server when there are no presence documents published for that user by any user agents currently running.
RFC 4827，一种用于操作状态文档内容的可扩展标记语言（XML）配置访问协议（XCAP）：[RFC4827]定义了允许用户存储“脱机”状态文档的XCAP用法。这是当当前运行的任何用户代理没有为该用户发布状态文档时，状态服务器使用的状态状态状态。
Federation refers to the interconnection of different presence and instant messaging systems for the purposes of communications. Federation can be between domains or within a domain. A document has been developed that describes how presence and IM federation works.
联邦是指为了通信目的，不同的状态和即时消息系统之间的互连。联合可以是域之间的联合，也可以是域内的联合。已经开发了一个文档，描述了状态和IM联盟是如何工作的。
RFC 5344, Presence and Instant Messaging Peering Use Cases (I): [RFC5344] describes a basic set of presence and instant messaging use cases for federating between providers.
RFC 5344，状态和即时消息对等用例（I）：[RFC5344]描述了一组基本的状态和即时消息用例，用于在提供者之间进行联合。
When running over wireless links, presence can be a very expensive service. Notifications often get sent when the change is not really relevant to the watcher. Furthermore, when a notification is sent, it contains the full presence state of the watcher, rather than just an indication of what changed. Optimizations have been defined to address both of these cases.
当通过无线链路运行时，状态信息可能是一项非常昂贵的服务。当更改与观察者并不真正相关时，通常会发送通知。此外，当发送通知时，它包含观察者的完全存在状态，而不仅仅是更改内容的指示。已经定义了优化来解决这两种情况。
RFC 4660, Functional Description of Event Notification Filtering (S): [RFC4660] defines a mechanism that allows a watcher to include filters in its subscription. These filters limit the cases in which notifications are sent. It is used in conjunction with RFC 4661, which specifies the XML format of the filters themselves. The mechanism, though targeted for presence, can be applied to any SIP event package.
RFC 4660，事件通知过滤的功能描述：[RFC4660]定义了一种机制，允许观察者在其订阅中包含过滤器。这些筛选器限制发送通知的情况。它与RFC4661一起使用，RFC4661指定过滤器本身的XML格式。该机制虽然针对存在，但可以应用于任何SIP事件包。
RFC 4661, An Extensible Markup Language (XML)-Based Format for Event Notification Filtering (S): [RFC4661] defines an XML format used with the event notification filtering mechanism defined in RFC 4660 [RFC4660].
RFC 4661是一种基于可扩展标记语言（XML）的事件通知过滤格式：[RFC4661]定义了与RFC 4660[RFC4660]中定义的事件通知过滤机制一起使用的XML格式。
RFC 5262, Presence Information Data Format (PIDF) Extension for Partial Presence (S): [RFC5262] defines a new XML format for representing changes in presence documents, called a partial PIDF document. This format contains an XML patch operation [RFC5261] that, when applied to the previous presence document, yields the
RFC 5262，部分状态的状态信息数据格式（PIDF）扩展：[RFC5262]定义了一种新的XML格式，用于表示状态文档中的更改，称为部分PIDF文档。此格式包含一个XML修补程序操作[RFC5261]，当应用于上一个状态文档时，该操作将生成
new presence document. The partial PIDF document is included in presence notifications when a watcher indicates that they support the format.
新的存在文件。当观察者表示支持该格式时，部分PIDF文档将包含在状态通知中。
RFC 5263, Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information (S): [RFC5263] defines a mechanism for receiving notifications that contain partial presence documents.
RFC 5263，状态信息部分通知的会话启动协议（SIP）扩展：[RFC5263]定义了接收包含部分状态文档的通知的机制。
RFC 5264, Publication of Partial Presence Information (S): [RFC5264] defines a mechanism for publishing presence status using a partial PIDF document.
RFC 5264，部分存在信息的发布：[RFC5264]定义了使用部分PIDF文档发布存在状态的机制。
RFC 5261, An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors (S): [RFC5261] defines an XML structure for representing changes in XML documents. It is a form of "diff" but specifically for XML documents. It is used by several of the optimization mechanisms defined for SIMPLE.
RFC 5261是一个使用XML路径语言（XPath）选择器的可扩展标记语言（XML）修补程序操作框架：[RFC5261]定义了一个XML结构，用于表示XML文档中的更改。它是“diff”的一种形式，但专门用于XML文档。它被一些为SIMPLE定义的优化机制所使用。
RFC 5112, The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp) (S): [RFC5112] defines a dictionary for usage with Signaling Compression (Sigcomp) [RFC3320] to improve the compressibility of presence documents.
RFC 5112，特定于状态的信令压缩静态字典（Sigcomp）：[RFC5112]定义了一个用于信令压缩（Sigcomp）[RFC3320]的字典，以提高状态文档的压缩性。
RFC 6446, Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control (S): [RFC6446] specifies mechanisms for adjusting the rate of SIP event notifications. These mechanisms can be applied in subscriptions to all SIP event packages.
RFC 6446，通知速率控制的会话启动协议（SIP）事件通知扩展：[RFC6446]指定调整SIP事件通知速率的机制。这些机制可以应用于所有SIP事件包的订阅中。
SIMPLE defines two modes of instant messaging. These are page mode and session mode. In page mode, instant messages are sent by sending a SIP request that contains the contents of the instant message. In session mode, IM is viewed as another media type -- along with audio and video -- and an INVITE request is used to set up a session that includes IM as a media type. While page mode is more efficient for one or two message conversations, session mode is more efficient for longer conversations since the messages are not sent through the SIP servers. Furthermore, by viewing IM as a media type, all of the features available in SIP signaling -- third party call control, forking, and so on, are available for IM.
SIMPLE定义了两种即时消息传递模式。这些是页面模式和会话模式。在页面模式下，通过发送包含即时消息内容的SIP请求来发送即时消息。在会话模式下，IM与音频和视频一起被视为另一种媒体类型，INVITE请求用于设置会话，其中包括IM作为媒体类型。虽然页面模式对于一个或两个消息对话更有效，但是会话模式对于较长的对话更有效，因为消息不是通过SIP服务器发送的。此外，通过将IM视为媒体类型，SIP信令中可用的所有功能（第三方呼叫控制、分叉等）都可用于IM。
RFC 3428, Session Initiation Protocol (SIP) Extension for Instant Messaging (S): [RFC3428] introduces the MESSAGE method, which can be used to send an instant message through SIP signaling.
RFC 3428，即时消息的会话启动协议（SIP）扩展：[RFC3428]介绍了消息方法，可用于通过SIP信令发送即时消息。
RFC 5365, Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) (S): [RFC5365] defines a mechanism whereby a client can send a single SIP MESSAGE to multiple recipients. This is accomplished by including the list of recipients as an object in the body and having a network server send a copy to each recipient.
RFC 5365，会话启动协议（SIP）（S）中的多个收件人消息请求：[RFC5365]定义了一种机制，通过该机制，客户端可以向多个收件人发送单个SIP消息。这是通过将收件人列表作为对象包含在正文中并让网络服务器向每个收件人发送副本来实现的。
RFC 4975, The Message Session Relay Protocol (MSRP) (S): [RFC4975] defines a small text-based protocol for exchanging arbitrarily sized content of any kind between users. An MSRP session is set up by exchanging certain information, such as an MSRP URI, within SIP and Session Description Protocol (SDP) signaling.
RFC 4975，消息会话中继协议（MSRP）：[RFC4975]定义了一个基于文本的小型协议，用于在用户之间交换任意大小的任何类型的内容。MSRP会话是通过在SIP和会话描述协议（SDP）信令中交换某些信息（如MSRP URI）来建立的。
RFC 3862, Common Presence and Instant Messaging (CPIM): Message Format (S): [RFC3862] defines a wrapper around instant message content providing metadata, such as the sender and recipient identity. The CPIM format is carried in MSRP.
RFC 3862，公共状态和即时消息（CPIM）：消息格式：[RFC3862]定义了即时消息内容的包装器，该内容提供元数据，如发送者和接收者身份。消费物价指数格式采用管理系统更新项目。
RFC 4976, Relay Extensions for the Message Sessions Relay Protocol (MSRP) (S): [RFC4976] adds support for relays to MSRP. These relay servers receive MSRP messages and send them towards the destination. They provide support for firewall and NAT traversal and allow for features such as recording and inspection to be implemented.
RFC 4976，消息会话中继协议（MSRP）的中继扩展：[RFC4976]向MSRP添加了对中继的支持。这些中继服务器接收MSRP消息并将其发送到目标。它们支持防火墙和NAT穿越，并允许实现记录和检查等功能。
RFC 6135, An Alternative Connection Model for the Message Session Relay Protocol (MSRP) (S): [RFC6135] allows clients to negotiate which endpoint in a session will establish the MSRP connection. Without this specification, the client generating the SDP offer would initiate the connection.
RFC 6135，消息会话中继协议（MSRP）的替代连接模型：[RFC6135]允许客户端协商会话中哪个端点将建立MSRP连接。如果没有此规范，生成SDP提供的客户端将启动连接。
RFC 6714, Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP) (S): [RFC6714] allows middleboxes to anchor the MSRP connection, without the need for middleboxes to modify the MSRP messages; thus, it also enables a secure end-to-end MSRP communication in networks where such middleboxes are deployed.
RFC 6714，消息会话中继协议（MSRP）的媒体锚定连接建立（CEMA）：[RFC6714]允许中间盒锚定MSRP连接，而无需中间盒修改MSRP消息；因此，它还能够在部署此类中间盒的网络中实现安全的端到端MSRP通信。
In SIMPLE, IM multi-user chat (also known as chat-rooms) are provided using regular SIP conferencing mechanisms. The framework for SIP conferencing [RFC4353] and conference control [RFC5239] describe how all SIP-based conferencing works; including joining and leaving, persistent and temporary conferences, floor control and moderation, and learning of conference membership, amongst other functions. All that is necessary are extensions to provide features that are specific to IM.
简单地说，IM多用户聊天（也称为聊天室）是使用常规SIP会议机制提供的。SIP会议框架[RFC4353]和会议控制[RFC5239]描述了所有基于SIP的会议是如何工作的；包括参加和离开、持续和临时会议、发言控制和调节、学习会议成员资格等功能。所有这些都是必要的扩展，以提供特定于IM的功能。
Multi-party Chat Using the Message Session Relay Protocol (MSRP) (Work in Progress): [SIMPCHAT] defines how MSRP is used to provide support for nicknames and private chat within an IM conference.
使用消息会话中继协议（MSRP）的多方聊天（正在进行）：[SIMPCHAT]定义了如何使用MSRP为IM会议中的昵称和私人聊天提供支持。
Several specifications have been written to provide IM-specific features for SIMPLE. These include "is-typing" indications, allowing a user to know when their messaging peer is composing a response and allowing a user to know when their IM has been received via delivery notifications.
已经编写了几个规范来为SIMPLE提供IM特定的功能。这些包括“正在键入”指示，允许用户知道其消息传递对等方何时正在编写响应，并允许用户知道何时通过传递通知接收到其IM。
RFC 3994, Indication of Message Composition for Instant Messaging (S): [RFC3994] defines an XML format that can be sent in instant messages that indicates the status of message composition. This provides the familiar "is-typing" indication in IM systems, but also supports voice, video, and other message types.
RFC 3994，即时消息的消息组合指示：[RFC3994]定义了可在即时消息中发送的XML格式，该格式指示消息组合的状态。这在IM系统中提供了熟悉的“正在键入”指示，但也支持语音、视频和其他消息类型。
RFC 5438, Instant Message Disposition Notification (IMDN) (S): [RFC5438] provides delivery notifications of IM receipt. This allows a user to know with certainty that a message has been received.
RFC 5438，即时消息处置通知（IMDN）：[RFC5438]提供IM接收的传递通知。这允许用户确信已收到消息。
This specification is an overview of existing specifications and does not introduce any security considerations on its own.
本规范是对现有规范的概述，不单独介绍任何安全注意事项。
Thanks to Vijay Gurbani, Barry Leiba, Stephen Hanna, and Salvatore Loreto for their review and comments.
感谢Vijay Gurbani、Barry Leiba、Stephen Hanna和Salvatore Loreto的评论和评论。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC3261] 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.
[RFC3261]Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002.
[RFC3265]Roach，A.，“会话启动协议（SIP）-特定事件通知”，RFC3265，2002年6月。
[RFC3320] Price, R., Bormann, C., Christoffersson, J., Hannu, H., Liu, Z., and J. Rosenberg, "Signaling Compression (SigComp)", RFC 3320, January 2003.
[RFC3320]Price，R.，Bormann，C.，Christofferson，J.，Hannu，H.，Liu，Z.，和J.Rosenberg，“信号压缩（SigComp）”，RFC3320，2003年1月。
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., and D. Gurle, "Session Initiation Protocol (SIP) Extension for Instant Messaging", RFC 3428, December 2002.
[RFC3428]Campbell，B.，Rosenberg，J.，Schulzrinne，H.，Huitema，C.，和D.Gurle，“即时消息的会话启动协议（SIP）扩展”，RFC 34282002年12月。
[RFC3856] Rosenberg, J., "A Presence Event Package for the Session Initiation Protocol (SIP)", RFC 3856, August 2004.
[RFC3856]Rosenberg，J.，“会话启动协议（SIP）的存在事件包”，RFC3856，2004年8月。
[RFC3857] Rosenberg, J., "A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)", RFC 3857, August 2004.
[RFC3857]Rosenberg，J.，“会话启动协议（SIP）的观察者信息事件模板包”，RFC3857，2004年8月。
[RFC3858] Rosenberg, J., "An Extensible Markup Language (XML) Based Format for Watcher Information", RFC 3858, August 2004.
[RFC3858]Rosenberg，J.，“基于可扩展标记语言（XML）的观察者信息格式”，RFC3858，2004年8月。
[RFC3862] Klyne, G. and D. Atkins, "Common Presence and Instant Messaging (CPIM): Message Format", RFC 3862, August 2004.
[RFC3862]Klyne，G.和D.Atkins，“常见状态和即时消息（CPIM）：消息格式”，RFC 3862，2004年8月。
[RFC3863] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and J. Peterson, "Presence Information Data Format (PIDF)", RFC 3863, August 2004.
[RFC3863]Sugano，H.，Fujimoto，S.，Klyne，G.，Batman，A.，Carr，W.，和J.Peterson，“状态信息数据格式（PIDF）”，RFC 38632004年8月。
[RFC3903] Niemi, A., "Session Initiation Protocol (SIP) Extension for Event State Publication", RFC 3903, October 2004.
[RFC3903]Niemi，A.，“事件状态发布的会话启动协议（SIP）扩展”，RFC 3903，2004年10月。
[RFC3994] Schulzrinne, H., "Indication of Message Composition for Instant Messaging", RFC 3994, January 2005.
[RFC3994]Schulzrinne，H.，“即时消息的消息组合指示”，RFC 3994，2005年1月。
[RFC4353] Rosenberg, J., "A Framework for Conferencing with the Session Initiation Protocol (SIP)", RFC 4353, February 2006.
[RFC4353]Rosenberg，J.，“会话启动协议（SIP）会议框架”，RFC 4353，2006年2月。
[RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479, July 2006.
[RFC4479]Rosenberg，J.，“存在的数据模型”，RFC 4479，2006年7月。
[RFC4480] Schulzrinne, H., Gurbani, V., Kyzivat, P., and J. Rosenberg, "RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)", RFC 4480, July 2006.
[RFC4480]Schulzrinne，H.，Gurbani，V.，Kyzivat，P.，和J.Rosenberg，“RPID：状态信息数据格式（PIDF）的丰富状态扩展”，RFC 44802006年7月。
[RFC4481] Schulzrinne, H., "Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals", RFC 4481, July 2006.
[RFC4481]Schulzrinne，H.，“状态信息数据格式（PIDF）的定时状态扩展，用于指示过去和未来时间间隔的状态信息”，RFC 4481，2006年7月。
[RFC4482] Schulzrinne, H., "CIPID: Contact Information for the Presence Information Data Format", RFC 4482, July 2006.
[RFC4482]Schulzrinne，H.，“CIPID：状态信息数据格式的联系信息”，RFC 4482，2006年7月。
[RFC4660] Khartabil, H., Leppanen, E., Lonnfors, M., and J. Costa-Requena, "Functional Description of Event Notification Filtering", RFC 4660, September 2006.
[RFC4660]Khartabil，H.，Leppanen，E.，Lonnfors，M.，和J.Costa Requena，“事件通知过滤的功能描述”，RFC 4660，2006年9月。
[RFC4661] Khartabil, H., Leppanen, E., Lonnfors, M., and J. Costa-Requena, "An Extensible Markup Language (XML)-Based Format for Event Notification Filtering", RFC 4661, September 2006.
[RFC4661]Khartabil，H.，Leppanen，E.，Lonnfors，M.，和J.Costa Requena，“基于可扩展标记语言（XML）的事件通知过滤格式”，RFC 4661，2006年9月。
[RFC4662] Roach, A., Campbell, B., and J. Rosenberg, "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists", RFC 4662, August 2006.
[RFC4662]Roach，A.，Campbell，B.，和J.Rosenberg，“资源列表的会话启动协议（SIP）事件通知扩展”，RFC 4662，2006年8月。
[RFC4745] Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., Polk, J., and J. Rosenberg, "Common Policy: A Document Format for Expressing Privacy Preferences", RFC 4745, February 2007.
[RFC4745]Schulzrinne，H.，Tschofenig，H.，Morris，J.，Cuellar，J.，Polk，J.，和J.Rosenberg，“共同政策：表达隐私偏好的文件格式”，RFC 47452007年2月。
[RFC4825] Rosenberg, J., "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)", RFC 4825, May 2007.
[RFC4825]Rosenberg，J.，“可扩展标记语言（XML）配置访问协议（XCAP）”，RFC4825，2007年5月。
[RFC4826] Rosenberg, J., "Extensible Markup Language (XML) Formats for Representing Resource Lists", RFC 4826, May 2007.
[RFC4826]Rosenberg，J.，“用于表示资源列表的可扩展标记语言（XML）格式”，RFC 4826，2007年5月。
[RFC4827] Isomaki, M. and E. Leppanen, "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents", RFC 4827, May 2007.
[RFC4827]Isomaki，M.和E.Leppanen，“用于操纵状态文档内容的可扩展标记语言（XML）配置访问协议（XCAP）使用”，RFC 4827，2007年5月。
[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message Session Relay Protocol (MSRP)", RFC 4975, September 2007.
[RFC4975]Campbell，B.，Mahy，R.，和C.Jennings，“消息会话中继协议（MSRP）”，RFC 49752007年9月。
[RFC4976] Jennings, C., Mahy, R., and A. Roach, "Relay Extensions for the Message Sessions Relay Protocol (MSRP)", RFC 4976, September 2007.
[RFC4976]Jennings，C.，Mahy，R.，和A.Roach，“消息会话中继协议（MSRP）的中继扩展”，RFC 49762007年9月。
[RFC5025] Rosenberg, J., "Presence Authorization Rules", RFC 5025, December 2007.
[RFC5025]Rosenberg，J.，“在场授权规则”，RFC 50252，2007年12月。
[RFC5112] Garcia-Martin, M., "The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)", RFC 5112, January 2008.
[RFC5112]Garcia Martin，M.“特定于状态的信令压缩静态字典（Sigcomp）”，RFC 5112，2008年1月。
[RFC5196] Lonnfors, M. and K. Kiss, "Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF)", RFC 5196, September 2008.
[RFC5196]Lonnfors，M.和K.Kiss，“会话启动协议（SIP）用户代理能力扩展到状态信息数据格式（PIDF）”，RFC 51962008年9月。
[RFC5239] Barnes, M., Boulton, C., and O. Levin, "A Framework for Centralized Conferencing", RFC 5239, June 2008.
[RFC5239]Barnes，M.，Boulton，C.，和O.Levin，“集中会议的框架”，RFC 5239，2008年6月。
[RFC5261] Urpalainen, J., "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors", RFC 5261, September 2008.
[RFC5261]Urpalainen，J.，“利用XML路径语言（XPath）选择器的可扩展标记语言（XML）修补程序操作框架”，RFC 52612008年9月。
[RFC5262] Lonnfors, M., Leppanen, E., Khartabil, H., and J. Urpalainen, "Presence Information Data Format (PIDF) Extension for Partial Presence", RFC 5262, September 2008.
[RFC5262]Lonnfors，M.，Leppanen，E.，Khartabil，H.，和J.Urpalainen，“部分存在的存在信息数据格式（PIDF）扩展”，RFC 5262，2008年9月。
[RFC5263] Lonnfors, M., Costa-Requena, J., Leppanen, E., and H. Khartabil, "Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information", RFC 5263, September 2008.
[RFC5263]Lonnfors，M.，Costa Requena，J.，Leppanen，E.，和H.Khartabil，“存在信息部分通知的会话启动协议（SIP）扩展”，RFC 5263，2008年9月。
[RFC5264] Niemi, A., Lonnfors, M., and E. Leppanen, "Publication of Partial Presence Information", RFC 5264, September 2008.
[RFC5264]Niemi，A.，Lonnfors，M.，和E.Leppanen，“部分存在信息的发布”，RFC 5264，2008年9月。
[RFC5344] Houri, A., Aoki, E., and S. Parameswar, "Presence and Instant Messaging Peering Use Cases", RFC 5344, October 2008.
[RFC5344]Houri，A.，Aoki，E.，和S.Parameswar，“状态和即时消息对等使用案例”，RFC 5344，2008年10月。
[RFC5365] Garcia-Martin, M. and G. Camarillo, "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)", RFC 5365, October 2008.
[RFC5365]Garcia Martin，M.和G.Camarillo，“会话启动协议（SIP）中的多收件人消息请求”，RFC 5365，2008年10月。
[RFC5367] Camarillo, G., Roach, A., and O. Levin, "Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)", RFC 5367, October 2008.
[RFC5367]Camarillo，G.，Roach，A.，和O.Levin，“会话启动协议（SIP）中包含资源列表的请求订阅”，RFC 5367，2008年10月。
[RFC5438] Burger, E. and H. Khartabil, "Instant Message Disposition Notification (IMDN)", RFC 5438, February 2009.
[RFC5438]Burger，E.和H.Khartabil，“即时消息处置通知（IMDN）”，RFC 5438，2009年2月。
[RFC5874] Rosenberg, J. and J. Urpalainen, "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources", RFC 5874, May 2010.
[RFC5874]Rosenberg，J.和J.Urpalainen，“用于指示XML配置访问协议（XCAP）资源更改的可扩展标记语言（XML）文档格式”，RFC 5874，2010年5月。
[RFC5875] Urpalainen, J. and D. Willis, "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package", RFC 5875, May 2010.
[RFC5875]Urpalainen，J.和D.Willis，“可扩展标记语言（XML）配置访问协议（XCAP）差异事件包”，RFC 5875，2010年5月。
[RFC6135] Holmberg, C. and S. Blau, "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)", RFC 6135, February 2011.
[RFC6135]Holmberg，C.和S.Blau，“消息会话中继协议（MSRP）的替代连接模型”，RFC 61352011年2月。
[RFC6446] Niemi, A., Kiss, K., and S. Loreto, "Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control", RFC 6446, January 2012.
[RFC6446]Niemi，A.，Kiss，K.，和S.Loreto，“用于通知速率控制的会话启动协议（SIP）事件通知扩展”，RFC 6446，2012年1月。
[RFC6665] Roach, A., "SIP-Specific Event Notification", RFC 6665, July 2012.
[RFC6665]Roach，A.，“SIP特定事件通知”，RFC 66652012年7月。
[RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)", RFC 6714, August 2012.
[RFC6714]Holmberg，C.，Blau，S.，和E.Burger，“消息会话中继协议（MSRP）的媒体锚定连接建立（CEMA）”，RFC 67142012年8月。
[SIMPCHAT] Niemi, A., Garcia, M., and G. Sandbakken, "Multi-party Chat Using the Message Session Relay Protocol (MSRP)", Work in Progress, January 2013.
[SIMPCHAT]Niemi，A.，Garcia，M.，和G.Sandbakken，“使用消息会话中继协议（MSRP）的多方聊天”，正在进行的工作，2013年1月。
Author's Address
作者地址
Jonathan Rosenberg jdrosen.net
Jonathan Rosenberg jdrosen.net
EMail: jdrosen@jdrosen.net
URI: http://www.jdrosen.net
EMail: jdrosen@jdrosen.net
URI: http://www.jdrosen.net