Internet Engineering Task Force (IETF) G. Camarillo
Request for Comments: 6502 Ericsson
Category: Standards Track S. Srinivasan
ISSN: 2070-1721
R. Even
Gesher Erove Ltd
J. Urpalainen
Nokia
March 2012
Internet Engineering Task Force (IETF) G. Camarillo
Request for Comments: 6502 Ericsson
Category: Standards Track S. Srinivasan
ISSN: 2070-1721
R. Even
Gesher Erove Ltd
J. Urpalainen
Nokia
March 2012
Conference Event Package Data Format Extension for Centralized Conferencing (XCON)
集中式会议（XCON）的会议事件包数据格式扩展
Abstract
摘要
This document specifies the notification mechanism for XCON (centralized conferencing). This mechanism reuses the SIP (Session Initiation Protocol) event package for conference state. Additionally, the notification mechanism includes support for the XCON data model and for partial notifications.
本文档指定了XCON（集中式会议）的通知机制。该机制将SIP（会话启动协议）事件包重用为会议状态。此外，通知机制还包括对XCON数据模型和部分通知的支持。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
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). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc6502.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6502.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 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许可证中所述的无担保。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Notification Formats ............................................5
4. Full Notifications ..............................................5
4.1. Backwards Compatibility ....................................5
5. Partial Notifications ...........................................6
5.1. Generation of Partial Notifications ........................6
5.2. Processing of Partial Notifications ........................7
5.3. Partial Notification Format ................................8
5.4. XML Schema for Partial Notifications .......................8
5.5. Examples ...................................................9
6. IANA Considerations ............................................10
6.1. MIME type Registration:
application/xcon-conference-info+xml ......................10
6.2. MIME type Registration:
application/xcon-conference-info-diff+xml .................11
6.3. URN Sub-Namespace Registration:
xcon-conference-info-diff .................................12
6.4. XML Schema Registration ...................................12
7. Security Considerations ........................................12
8. References .....................................................13
8.1. Normative References ......................................13
8.2. Informative References ....................................13
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Notification Formats ............................................5
4. Full Notifications ..............................................5
4.1. Backwards Compatibility ....................................5
5. Partial Notifications ...........................................6
5.1. Generation of Partial Notifications ........................6
5.2. Processing of Partial Notifications ........................7
5.3. Partial Notification Format ................................8
5.4. XML Schema for Partial Notifications .......................8
5.5. Examples ...................................................9
6. IANA Considerations ............................................10
6.1. MIME type Registration:
application/xcon-conference-info+xml ......................10
6.2. MIME type Registration:
application/xcon-conference-info-diff+xml .................11
6.3. URN Sub-Namespace Registration:
xcon-conference-info-diff .................................12
6.4. XML Schema Registration ...................................12
7. Security Considerations ........................................12
8. References .....................................................13
8.1. Normative References ......................................13
8.2. Informative References ....................................13
The XCON (Centralized Conferencing) framework [RFC5239] defines a notification service that provides updates about a conference instance's state to authorized parties using a notification protocol, as shown in Figure 1. This document specifies how to use the SIP (Session Initiation Protocol [RFC3261]) event package for conference state defined in [RFC4575] as a notification protocol between a client and a conference's notification server.
XCON（集中式会议）框架[RFC5239]定义了一个通知服务，该服务使用通知协议向授权方提供关于会议实例状态的更新，如图1所示。本文档规定了如何将[RFC4575]中定义的会议状态的SIP（会话启动协议[RFC3261]）事件包用作客户端和会议通知服务器之间的通知协议。
...........................
. Conferencing System .
. .
. +--------------+ .
. | Conf. object | .
. | | .
. +--------------+ .
. | .
. v .
. +------------+ .
. |Notification| .
. |Service | .
. +------------+ .
. ^ .
..........|................
|
| Notification
| Protocol
|(notifications following the
| XCON data model)
|
..........|............
. v .
. +------------+ .
. |Notification| .
. | Client | .
. +------------+ .
. .
. Conferencing Client .
.......................
...........................
. Conferencing System .
. .
. +--------------+ .
. | Conf. object | .
. | | .
. +--------------+ .
. | .
. v .
. +------------+ .
. |Notification| .
. |Service | .
. +------------+ .
. ^ .
..........|................
|
| Notification
| Protocol
|(notifications following the
| XCON data model)
|
..........|............
. v .
. +------------+ .
. |Notification| .
. | Client | .
. +------------+ .
. .
. Conferencing Client .
.......................
Figure 1: Notification service and protocol in the XCON architecture
图1:XCON体系结构中的通知服务和协议
In addition to specifying the SIP event package for conference state, [RFC4575] specifies a data format to be used with the event package. The XCON data model [RFC6501] extends that format with new elements and attributes so that the extended format supports more functionality (e.g., floor control). The notification protocol specified in this document supports all the data defined in the XCON data model (i.e., the data originally defined in [RFC4575] plus all the extensions defined in [RFC6501]) plus a partial notification mechanism based on XML patch operations [RFC5261].
除了为会议状态指定SIP事件包外，[RFC4575]还指定要与事件包一起使用的数据格式。XCON数据模型[RFC6501]使用新的元素和属性扩展该格式，以便扩展格式支持更多功能（例如，楼层控制）。本文档中指定的通知协议支持XCON数据模型中定义的所有数据（即，[RFC4575]中最初定义的数据加上[RFC6501]中定义的所有扩展）以及基于XML修补操作[RFC5261]的部分通知机制。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
In order to obtain notifications from a conference server's notification service, a client subscribes to the 'conference' event package at the server as specified in [RFC4575]. Per [RFC4575], NOTIFY requests within this event package can carry an XML document in the "application/conference-info+xml" format. Additionally, per this specification, NOTIFY requests can also carry XML documents in the "application/xcon-conference-info+xml" and the "application/ xcon-conference-info-diff+xml" formats.
为了从会议服务器的通知服务获取通知，客户机在服务器上订阅[RFC4575]中指定的“会议”事件包。根据[RFC4575]，此事件包中的NOTIFY请求可以包含“应用程序/会议信息+XML”格式的XML文档。此外，根据本规范，NOTIFY请求还可以携带“application/xcon conference info+XML”和“application/xcon conference info diff+XML”格式的XML文档。
A document in the "application/xcon-conference-info+xml" format provides the user agent with the whole state of a conference instance. A document in the "application/ xcon-conference-info-diff+xml" format provides the user agent with the changes the state of the conference instance has experienced since the last notification sent to the user agent.
“application/xcon conference info+xml”格式的文档为用户代理提供会议实例的整个状态。“application/xcon conference info diff+xml”格式的文档向用户代理提供自上次向用户代理发送通知以来会议实例的状态所经历的更改。
Subscribers signal support for full notifications by including the "application/xcon-conference-info+xml" format in the Accept header field of the SUBSCRIBE requests they generate. If a client subscribing to the 'conference' event package generates an Accept header field that includes the MIME type "application/ xcon-conference-info+xml", the server has the option of returning documents that follow the XML format specified in [RFC6501] and are carried in "application/xcon-conference-info+xml" message bodies.
订阅者通过在其生成的订阅请求的接受头字段中包含“application/xcon conference info+xml”格式来表示对完整通知的支持。如果订阅“conference”事件包的客户端生成一个包含MIME类型“application/xcon conference info+xml”的Accept标头字段，则服务器可以选择返回遵循[RFC6501]中指定的xml格式并包含在“application/xcon conference info+xml”消息体中的文档。
Conference servers that implement the SIP event package for conference state and support the "application/ xcon-conference-info+xml" MIME type MUST also support the "application/conference-info+xml" MIME type. This way, legacy clients, which only support "application/conference-info+xml", are able to receive notifications in a format they understand.
为会议状态实现SIP事件包并支持“application/xcon Conference info+xml”MIME类型的会议服务器还必须支持“application/Conference info+xml”MIME类型。这样，仅支持“应用程序/会议信息+xml”的旧客户端就能够以他们理解的格式接收通知。
Clients that implement the SIP event package for conference state and support the "application/xcon-conference-info+xml" MIME type SHOULD also support the "application/conference-info+xml" MIME type. This way, these clients are able to receive notifications from legacy servers, which only support "application/conference-info+xml", in a format they understand.
为会议状态实现SIP事件包并支持“application/xcon conference info+xml”MIME类型的客户端还应支持“application/conference info+xml”MIME类型。通过这种方式，这些客户机能够接收来自传统服务器的通知，这些服务器只支持“应用程序/会议信息+xml”，其格式是他们能够理解的。
The conference state reported by this event package may contain many elements. When the "xcon-conference-info+xml" format is used and there is a change in the state of an element, the server generates a notification with the whole conference state. Generating large notifications to report small changes does not meet the efficiency requirements of some bandwidth-constrained environments. The partial notifications mechanism specified in this section is a more efficient way to report changes in the conference state.
此事件包报告的会议状态可能包含许多元素。当使用“xcon conference info+xml”格式并且某个元素的状态发生更改时，服务器将生成一个包含整个会议状态的通知。生成大通知以报告小更改无法满足某些带宽受限环境的效率要求。本节中指定的部分通知机制是报告会议状态更改的更有效的方法。
The SIP event package for conference state defined a partial notification mechanism based on <state> elements. Servers compliant with this specification MUST NOT use that partial notification mechanism. Instead, they MUST use the mechanism specified in this section.
会议状态的SIP事件包基于<state>元素定义了部分通知机制。符合此规范的服务器不得使用该部分通知机制。相反，它们必须使用本节中指定的机制。
Subscribers signal support for partial notifications by including the "application/xcon-conference-info-diff+xml" format in the Accept header field of the SUBSCRIBE requests they generate. If a client subscribing to the 'conference' event package generates an Accept header field that includes the MIME type "application/ xcon-conference-info-diff+xml", the server has the option of returning documents that follow the XML format specified in Section 5.4 and are carried in "application/ xcon-conference-diff-info+xml" message bodies.
订阅者通过在其生成的订阅请求的接受头字段中包含“application/xcon conference info diff+xml”格式来表示对部分通知的支持。如果订阅“conference”事件包的客户端生成一个包含MIME类型“application/xcon conference info diff+xml”的Accept header字段，则服务器可以选择返回遵循第5.4节中指定的xml格式并在“application/xcon conference diff info+xml”消息体中携带的文档。
Once a subscription is accepted and installed, the server MUST deliver full state in its first notification. To report full state, the server MUST set the Content-Type header field to the value "application/xcon-conference-info+xml".
接受并安装订阅后，服务器必须在第一次通知中传递完整状态。要报告完整状态，服务器必须将内容类型头字段设置为值“application/xcon conference info+xml”。
In order to deliver a partial notification, the server MUST set the Content-Type header field to the value "application/ xcon-conference-info-diff+xml". When the server generates a partial notification, the server SHOULD only include the information that has changed compared to the previous notification. It is up to the server's local policy to determine what is considered as a change to the previous state.
为了传递部分通知，服务器必须将Content-Type头字段设置为值“application/xcon-conference-info-diff+xml”。当服务器生成部分通知时，服务器应仅包含与先前通知相比已更改的信息。由服务器的本地策略来确定对以前状态的更改。
The server MUST construct partial notifications according to the following logic: all the information that has been added to the document is listed inside <add> elements. All information that has been removed from the document is listed inside <remove> elements, and all information that has been changed is listed under <replace> elements.
服务器必须根据以下逻辑构造部分通知：添加到文档中的所有信息都列在<add>元素中。所有从文档中删除的信息都列在<remove>元素中，所有已更改的信息都列在<replace>元素下。
The server MUST NOT send a new NOTIFY request with a partial notification until it has received a final response from the subscriber for the previous one or the previous NOTIFY request has timed out.
服务器在收到订户对上一个通知请求的最终响应或上一个通知请求超时之前，不得发送带有部分通知的新通知请求。
When the server receives a SUBSCRIBE request (refresh or termination) within the associated subscription, it SHOULD send a NOTIFY request containing the full document using the 'application/ xcon-conference-info+xml' content type.
当服务器在关联订阅中收到订阅请求（刷新或终止）时，它应使用“application/xcon conference info+xml”内容类型发送包含完整文档的通知请求。
If the server has used a content type other than 'application/ xcon-conference-info+xml' in notifications within the existing subscription and changes to deliver partial notifications, the server MUST deliver full state using the 'application/ xcon-conference-info+xml' content type before generating its first partial notification.
如果服务器在现有订阅中的通知中使用了除“application/xcon conference info+xml”以外的内容类型，并更改为传递部分通知，则服务器必须在生成其第一个部分通知之前使用“application/xcon conference info+xml”内容类型传递完整状态。
When a subscriber receives the first notification containing full state in a 'application/xcon-conference-info+xml' MIME body, the subscriber MUST store the received full document as its local copy.
当订阅者在“application/xcon conference info+xml”MIME正文中收到包含完整状态的第一个通知时，订阅者必须将收到的完整文档存储为其本地副本。
When the subscriber receives a subsequent notification, the subscriber MUST modify its locally stored information according to the following logic:
当订户收到后续通知时，订户必须根据以下逻辑修改其本地存储的信息：
o If the notification carries an 'application/ xcon-conference-info+xml' document, the subscriber MUST replace its local copy of the document with the document received in the notification.
o 如果通知包含“application/xcon conference info+xml”文档，订阅者必须用通知中收到的文档替换其文档的本地副本。
o If the notification carries an 'application/ xcon-conference-info-diff+xml' document, the subscriber MUST apply the changes indicated in the received 'application/ xcon-conference-info-diff+xml' document to its local copy of the full document.
o 如果通知包含“application/xcon conference info diff+xml”文档，订阅者必须将收到的“application/xcon conference info diff+xml”文档中指示的更改应用于其完整文档的本地副本。
If the subscriber encounters a processing error while processing an 'application/xcon-conference-info-diff+xml' encoded document, the subscriber SHOULD renew its subscription. A subscriber can fall back to normal operations by not including the "application/ xcon-conference-info-diff+xml" format in a new SUBSCRIBE request.
如果订阅服务器在处理“application/xcon conference info diff+xml”编码文档时遇到处理错误，则订阅服务器应续订。订阅者可以通过在新的订阅请求中不包含“application/xcon conference info diff+xml”格式而返回到正常操作。
If the server changes the content type used in notifications within the existing subscription, the subscriber MUST discard all the previously received information and process the new content as specified for that content type.
如果服务器更改了现有订阅中通知中使用的内容类型，订阅服务器必须放弃以前收到的所有信息，并按照为该内容类型指定的方式处理新内容。
An xcon-conference-info-diff document is an XML [W3C.REC-xml-20081126] document that MUST be well-formed and SHOULD be valid. The namespace URI for the <conference-info-diff> root document element is defined in [RFC6501]:
xcon会议信息差异文档是一个XML[W3C.REC-XML-20081126]文档，必须格式正确且有效。<conference info diff>根文档元素的命名空间URI在[RFC6501]中定义：
urn:ietf:params:xml:ns:xcon-conference-info
urn:ietf:params:xml:ns:xcon-conference-info
The root document element <conference-info-diff> has a single mandatory attribute, "entity". The value of this attribute is the conference object identifier (XCON-URI) that identifies the conference being described in the document.
根文档元素<conference info diff>有一个强制属性“entity”。此属性的值是会议对象标识符（XCON-URI），用于标识文档中描述的会议。
The content of the <conference-info-diff> element is an unordered sequence of <add>, <replace>, and <remove> elements followed by elements from other namespaces for the purposes of extensibility. Any such unknown elements MUST be ignored by the client. The <add>, <replace>, and <remove> elements can contain other extension attributes than what are defined in the corresponding base types of [RFC5261].
<conference info diff>元素的内容是一个无序的序列，依次是<add>、<replace>和<remove>元素，然后是其他名称空间中的元素，以实现可扩展性。客户端必须忽略任何此类未知元素。<add>、<replace>和<remove>元素可以包含与[RFC5261]的相应基类型中定义的扩展属性不同的其他扩展属性。
This is the XML schema for the "application/ xcon-conference-info-diff+xml" data format. The "urn:ietf:params:xml:schema:xml-patch-ops" schema is defined in [RFC5261].
这是“application/xcon conference info diff+XML”数据格式的XML模式。[RFC5261]中定义了“urn:ietf:params:xml:schema:xml patch ops”模式。
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- include patch-ops type definitions -->
<xs:include
schemaLocation="urn:ietf:params:xml:schema:patch-ops"/>
<!-- partial updates -->
<xs:element name="conference-info-diff">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:choice>
<!-- add some content -->
<xs:element name="add">
<xs:complexType mixed="true">
<xs:complexContent>
<!-- include patch-ops type definitions -->
<xs:include
schemaLocation="urn:ietf:params:xml:schema:patch-ops"/>
<!-- partial updates -->
<xs:element name="conference-info-diff">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:choice>
<!-- add some content -->
<xs:element name="add">
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="add">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- remove some content -->
<xs:element name="remove">
<xs:complexType>
<xs:complexContent>
<xs:extension base="remove">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- replace some content -->
<xs:element name="replace">
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="replace">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- allow extension elements from other namespaces -->
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="entity" type="xs:anyURI" use="required"/>
<xs:anyAttribute processContents="lax"/>
</xs:complexType>
</xs:element>
</xs:schema>
<xs:extension base="add">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- remove some content -->
<xs:element name="remove">
<xs:complexType>
<xs:complexContent>
<xs:extension base="remove">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- replace some content -->
<xs:element name="replace">
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="replace">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- allow extension elements from other namespaces -->
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="entity" type="xs:anyURI" use="required"/>
<xs:anyAttribute processContents="lax"/>
</xs:complexType>
</xs:element>
</xs:schema>
The following is an 'application/xcon-conference-info-diff+xml' partial update document:
以下是“应用程序/xcon会议信息差异+xml”部分更新文档：
<?xml version="1.0" encoding="UTF-8"?>
<conference-info-diff
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
entity="conference123@example.com">
<?xml version="1.0" encoding="UTF-8"?>
<conference-info-diff
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
entity="conference123@example.com">
<add
sel="*/users/allowed-users-list"> <target
uri="sip:john@example.com" method="refer"/>
</add>
<add
sel="*/users/allowed-users-list"> <target
uri="sip:john@example.com" method="refer"/>
</add>
<replace sel="*/conference-state/user-count/text()">5</replace>
<replace sel="*/conference-state/user-count/text()">5</replace>
</conference-info-diff>
</conference-info-diff>
There are four IANA considerations associated with this specification.
本规范涉及四个IANA注意事项。
This section registers the 'application/xcon-conference-info+xml' MIME type.
本节注册“应用程序/xcon会议信息+xml”MIME类型。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: xcon-conference-info+xml
MIME子类型名称：xcon会议信息+xml
Mandatory parameters: none
强制参数：无
Optional Parameters: Same as charset parameter application/xml as specified in [RFC3023].
可选参数：与[RFC3023]中指定的字符集参数application/xml相同。
Encoding considerations: Same as encoding considerations of application/xml as specified in [RFC3023].
编码注意事项：与[RFC3023]中指定的应用程序/xml的编码注意事项相同。
Security considerations: Security considerations: See Section 10 of [RFC3023].
安全注意事项：安全注意事项：见[RFC3023]第10节。
Interoperability considerations: none
互操作性注意事项：无
Published specification: RFC 6502
已发布规范：RFC6502
Applications that use this media type: This document type has been defined to support centralized conferencing applications.
使用此媒体类型的应用程序：已定义此文档类型以支持集中式会议应用程序。
Additional Information:
其他信息：
Magic Number: none
神奇数字：无
File extension: .xml
文件扩展名：.xml
Macintosh file type code: "TEXT"
Macintosh文件类型代码：“文本”
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Intended usage: COMMON
预期用途：普通
Author/Change controller: The IETF.
作者/变更控制者：IETF。
This section registers the 'application/ xcon-conference-info-diff+xml' MIME type.
本节注册“application/xcon conference info diff+xml”MIME类型。
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: xcon-conference-info-diff+xml
MIME子类型名称：xcon会议信息差异+xml
Mandatory parameters: none
强制参数：无
Optional Parameters: Same as charset parameter application/xml as specified in [RFC3023].
可选参数：与[RFC3023]中指定的字符集参数application/xml相同。
Encoding considerations: Same as encoding considerations of application/xml as specified in [RFC3023].
编码注意事项：与[RFC3023]中指定的应用程序/xml的编码注意事项相同。
Security considerations: Security considerations: See Section 10 of [RFC3023].
安全注意事项：安全注意事项：见[RFC3023]第10节。
Interoperability considerations: none
互操作性注意事项：无
Published specification: RFC 6502
已发布规范：RFC6502
Applications that use this media type: This document type has been defined to support partial notifications in centralized conferencing applications.
使用此媒体类型的应用程序：此文档类型已定义为支持集中式会议应用程序中的部分通知。
Additional Information:
其他信息：
Magic Number: none
神奇数字：无
File extension: .xml
文件扩展名：.xml
Macintosh file type code: "TEXT"
Macintosh文件类型代码：“文本”
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Intended usage: COMMON
预期用途：普通
Author/Change controller: The IETF.
作者/变更控制者：IETF。
This section registers a new XML namespace per the procedures in [RFC3688].
本节根据[RFC3688]中的过程注册一个新的XML命名空间。
URI: urn:ietf:params:xml:ns:xcon-conference-info-diff
URI: urn:ietf:params:xml:ns:xcon-conference-info-diff
Registrant Contact: IETF SIPPING working group <sipping@ietf.org>,
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Registrant Contact: IETF SIPPING working group <sipping@ietf.org>,
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
XML:
XML:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Partial Notifications in Centralized Conferencing</title>
</head>
<body>
<h1>Namespace for Partial Notifications in</h1>
<h1>Centralized Conferencing</h1>
<h2>urn:ietf:params:xml:ns:xcon-conference-info-diff</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc6502.txt">
RFC 6502</a>.</p>
</body>
</html>
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Partial Notifications in Centralized Conferencing</title>
</head>
<body>
<h1>Namespace for Partial Notifications in</h1>
<h1>Centralized Conferencing</h1>
<h2>urn:ietf:params:xml:ns:xcon-conference-info-diff</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc6502.txt">
RFC 6502</a>.</p>
</body>
</html>
This section registers an XML schema per the procedures in [RFC3688].
本节根据[RFC3688]中的过程注册XML模式。
URI: urn:ietf:params:xml:schema:xcon-conference-info-diff
URI: urn:ietf:params:xml:schema:xcon-conference-info-diff
Registrant Contact: IETF XCON working group, <xcon@ietf.org>, Gonzalo
Camarillo <Gonzalo.Camarillo@ericsson.com>
Registrant Contact: IETF XCON working group, <xcon@ietf.org>, Gonzalo
Camarillo <Gonzalo.Camarillo@ericsson.com>
The XML for this schema can be found in Section 5.4.
该模式的XML可在第5.4节中找到。
This document specifies how to deliver notifications using the SIP event package for conference state in two new formats. The fact that notifications are encoded in a different format does not have
本文档指定了如何使用SIP事件包以两种新格式发送会议状态通知。通知是以不同格式编码的，这一事实不具有任何意义
security implications. Section 8 of [RFC4575] contains security considerations related to the use of the event package. Implementers of the event package need to follow those considerations regardless of the format used to encode their notifications.
安全影响。[RFC4575]第8节包含与使用事件包相关的安全注意事项。事件包的实现者需要遵循这些注意事项，而不考虑用于编码其通知的格式。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[RFC3023]Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[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月。
[RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session Initiation Protocol (SIP) Event Package for Conference State", RFC 4575, August 2006.
[RFC4575]Rosenberg，J.，Schulzrinne，H.，和O.Levin，“会议状态的会话启动协议（SIP）事件包”，RFC 45752006年8月。
[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月。
[RFC6501] Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen, "Conference Information Data Model for Centralized Conferencing (XCON)", RFC 6501, March 2012.
[RFC6501]Novo，O.，Camarillo，G.，Morgan，D.，和J.Urpalainen，“集中会议的会议信息数据模型（XCON）”，RFC 65012012年3月。
[W3C.REC-xml-20081126] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-xml-20081126, November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126>.
[W3C.REC-xml-20081126]Bray，T.，Paoli，J.，Sperberg McQueen，C.，Maler，E.，和F.Yergeau，“可扩展标记语言（xml）1.0（第五版）”，万维网联盟建议REC-xml-20081126，2008年11月<http://www.w3.org/TR/2008/REC-xml-20081126>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[RFC3688]Mealling，M.“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[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月。
Authors' Addresses
作者地址
Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420 Finland
Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420芬兰
EMail: Gonzalo.Camarillo@ericsson.com
EMail: Gonzalo.Camarillo@ericsson.com
Srivatsa Srinivasan
斯里瓦萨斯里尼瓦桑
EMail: srivatsa.srinivasan@gmail.com
EMail: srivatsa.srinivasan@gmail.com
Roni Even Gesher Erove Ltd 14 David Hamelech Tel Aviv 64953 Israel
Roni Even Gesher Erove有限公司14 David Hamelech特拉维夫64953以色列
EMail: ron.even.tlv@gmail.com
EMail: ron.even.tlv@gmail.com
Jari Urpalainen Nokia Itamerenkatu 11-13 Helsinki 00180 Finland
芬兰赫尔辛基乌尔帕莱宁诺基亚伊塔梅伦卡图11-13 00180
EMail: jari.urpalainen@nokia.com
EMail: jari.urpalainen@nokia.com