Network Working Group J. Rosenberg
Request for Comments: 4575 Cisco Systems
Category: Standards Track H. Schulzrinne
Columbia University
O. Levin, Ed.
Microsoft Corporation
August 2006
Network Working Group J. Rosenberg
Request for Comments: 4575 Cisco Systems
Category: Standards Track H. Schulzrinne
Columbia University
O. Levin, Ed.
Microsoft Corporation
August 2006
A Session Initiation Protocol (SIP) Event Package for Conference State
用于会议状态的会话启动协议（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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document defines a conference event package for tightly coupled conferences using the Session Initiation Protocol (SIP) events framework, along with a data format used in notifications for this package. The conference package allows users to subscribe to a conference Uniform Resource Identifier (URI). Notifications are sent about changes in the membership of this conference and optionally about changes in the state of additional conference components.
本文档使用会话启动协议（SIP）事件框架为紧密耦合的会议定义了一个会议事件包，以及该包的通知中使用的数据格式。会议包允许用户订阅会议统一资源标识符（URI）。将发送有关此会议成员资格更改的通知，以及关于其他会议组件状态更改的通知（可选）。
Table of Contents
目录
1. Introduction ....................................................4
2. Terminology .....................................................4
3. Conference Event Package ........................................4
3.1. Event Package Name .........................................5
3.2. Filtering ..................................................5
3.3. Subscription Duration ......................................5
3.4. NOTIFY Bodies ..............................................5
3.5. Notifier Processing of SUBSCRIBE Requests ..................6
3.6. Notifier Generation of NOTIFY Requests .....................6
3.7. Subscriber Processing of NOTIFY Requests ...................6
3.8. Handling of Forked Requests ................................7
3.9. Rate of Notifications ......................................7
3.10. State Agents ..............................................7
4. Conference Document .............................................7
4.1. Format .....................................................7
4.2. Namespace ..................................................7
4.3. Versioning .................................................8
4.4. Partial Notifications Mechanism ............................8
4.5. Element Keys ...............................................9
4.6. Constructing Coherent State Procedure ......................9
5. Conference Data ................................................11
5.1. Overview ..................................................11
5.2. <conference-info> .........................................13
5.3. <conference-description> ..................................14
5.3.1. <conf-uris> ........................................14
5.3.2. <service-uris> .....................................15
5.3.3. <maximum-user-count> ...............................16
5.3.4. <available-media> ..................................16
5.4. <host-info> ...............................................17
5.4.1. <display-text> .....................................17
5.4.2. <web-page> .........................................17
5.4.3. <uris> .............................................17
5.5. <conference-state> ........................................17
5.5.1. <user-count> .......................................17
5.5.2. <active> ...........................................18
5.5.3. <locked> ...........................................18
5.6. <users> and Its <user> Sub-elements .......................18
5.6.1. <display-text> .....................................19
5.6.2. <associated-aors> ..................................19
5.6.3. <roles> ............................................19
5.6.4. <languages> ........................................19
5.6.5. <cascaded-focus> ...................................19
5.6.6. <endpoint> .........................................20
5.7. <endpoint> ................................................20
5.7.1. <display-text> .....................................20
5.7.2. <referred> .........................................21
1. Introduction ....................................................4
2. Terminology .....................................................4
3. Conference Event Package ........................................4
3.1. Event Package Name .........................................5
3.2. Filtering ..................................................5
3.3. Subscription Duration ......................................5
3.4. NOTIFY Bodies ..............................................5
3.5. Notifier Processing of SUBSCRIBE Requests ..................6
3.6. Notifier Generation of NOTIFY Requests .....................6
3.7. Subscriber Processing of NOTIFY Requests ...................6
3.8. Handling of Forked Requests ................................7
3.9. Rate of Notifications ......................................7
3.10. State Agents ..............................................7
4. Conference Document .............................................7
4.1. Format .....................................................7
4.2. Namespace ..................................................7
4.3. Versioning .................................................8
4.4. Partial Notifications Mechanism ............................8
4.5. Element Keys ...............................................9
4.6. Constructing Coherent State Procedure ......................9
5. Conference Data ................................................11
5.1. Overview ..................................................11
5.2. <conference-info> .........................................13
5.3. <conference-description> ..................................14
5.3.1. <conf-uris> ........................................14
5.3.2. <service-uris> .....................................15
5.3.3. <maximum-user-count> ...............................16
5.3.4. <available-media> ..................................16
5.4. <host-info> ...............................................17
5.4.1. <display-text> .....................................17
5.4.2. <web-page> .........................................17
5.4.3. <uris> .............................................17
5.5. <conference-state> ........................................17
5.5.1. <user-count> .......................................17
5.5.2. <active> ...........................................18
5.5.3. <locked> ...........................................18
5.6. <users> and Its <user> Sub-elements .......................18
5.6.1. <display-text> .....................................19
5.6.2. <associated-aors> ..................................19
5.6.3. <roles> ............................................19
5.6.4. <languages> ........................................19
5.6.5. <cascaded-focus> ...................................19
5.6.6. <endpoint> .........................................20
5.7. <endpoint> ................................................20
5.7.1. <display-text> .....................................20
5.7.2. <referred> .........................................21
5.7.3. <status> ...........................................21
5.7.4. <joining-method> ...................................22
5.7.5. <joining-info> .....................................23
5.7.6. <disconnection-method> .............................23
5.7.7. <disconnection-info> ...............................23
5.7.8. <media> ............................................24
5.7.9. <call-info> ........................................24
5.8. <media> ...................................................24
5.8.1. <display-text> .....................................25
5.8.2. <type> .............................................25
5.8.3. <label> ............................................25
5.8.4. <src-id> ...........................................25
5.8.5. <status> ...........................................26
5.9. Sidebars ..................................................26
5.9.1. <sidebars-by-ref> ..................................26
5.9.2. <sidebar-by-val> ...................................26
6. XML Schema .....................................................26
7. Examples .......................................................35
7.1. Basic Example .............................................35
7.2. Rich Example ..............................................36
8. Security Considerations ........................................40
8.1. Connection Security .......................................40
8.2. Authorization Considerations ..............................41
9. IANA Considerations ............................................41
9.1. conference Event Package Registration .....................41
9.2. application/conference-info+xml MIME Registration .........42
9.3. URN Sub-Namespace Registration for ........................43
9.4. XML Schema Registration ...................................43
9.5. URI Purposes Sub-registry Establishment ...................44
10. Acknowledgements ..............................................45
11. References ....................................................45
11.1. Normative References .....................................45
11.2. Informative References ...................................46
5.7.3. <status> ...........................................21
5.7.4. <joining-method> ...................................22
5.7.5. <joining-info> .....................................23
5.7.6. <disconnection-method> .............................23
5.7.7. <disconnection-info> ...............................23
5.7.8. <media> ............................................24
5.7.9. <call-info> ........................................24
5.8. <media> ...................................................24
5.8.1. <display-text> .....................................25
5.8.2. <type> .............................................25
5.8.3. <label> ............................................25
5.8.4. <src-id> ...........................................25
5.8.5. <status> ...........................................26
5.9. Sidebars ..................................................26
5.9.1. <sidebars-by-ref> ..................................26
5.9.2. <sidebar-by-val> ...................................26
6. XML Schema .....................................................26
7. Examples .......................................................35
7.1. Basic Example .............................................35
7.2. Rich Example ..............................................36
8. Security Considerations ........................................40
8.1. Connection Security .......................................40
8.2. Authorization Considerations ..............................41
9. IANA Considerations ............................................41
9.1. conference Event Package Registration .....................41
9.2. application/conference-info+xml MIME Registration .........42
9.3. URN Sub-Namespace Registration for ........................43
9.4. XML Schema Registration ...................................43
9.5. URI Purposes Sub-registry Establishment ...................44
10. Acknowledgements ..............................................45
11. References ....................................................45
11.1. Normative References .....................................45
11.2. Informative References ...................................46
The Session Initiation Protocol (SIP) events framework [10] defines general mechanisms for subscribing to, and receiving notifications of, events within SIP networks. It introduces the notion of a package, which is a specific "instantiation" of the events framework for a well-defined set of events. Here, we define a SIP event package for tightly coupled conferences. This package can be used by the conference notification service as outlined in the SIP conferencing framework [16]. As described there, subscriptions to a conference URI are routed to the focus that is handling the conference. It acts as the notifier and provides clients with updates on conference state.
会话发起协议（SIP）事件框架[10]定义了订阅SIP网络中的事件并接收其通知的一般机制。它引入了包的概念，包是一组定义良好的事件的事件框架的特定“实例化”。这里，我们为紧密耦合的会议定义一个SIP事件包。如SIP会议框架[16]所述，会议通知服务可以使用此包。如上所述，对会议URI的订阅被路由到处理会议的焦点。它充当通知程序，向客户端提供会议状态的更新。
The information provided by this package is comprised of conference identifier(s), conference participants (optionally with their statuses and media description), conference sidebars, conference service URIs, etc.
此软件包提供的信息包括会议标识符、会议参与者（可选包括其状态和媒体描述）、会议侧栏、会议服务URI等。
In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and indicate requirement levels for compliant implementations.
在本文件中，关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释，并指出符合性实施的要求级别。
This document uses the conferencing terminology defined in Conferencing Framework [16]. In addition, the "roster" term is used to collectively refer to participants in a conference or a sub-conference.
本文档使用会议框架[16]中定义的会议术语。此外，“名册”一词用于统称会议或分会议的与会者。
The conference event package allows a user to subscribe to the information relating to a conference. In SIP, conferences are represented by URIs. These URIs identify a SIP user agent (UA), called a focus, that is responsible for ensuring that all users in the conference can communicate with each other, as described in Conferencing Framework [16]. The focus has sufficient information about the state of the conference to inform subscribers about it.
会议事件包允许用户订阅与会议相关的信息。在SIP中，会议由URI表示。这些URI识别一个称为焦点的SIP用户代理（UA），该代理负责确保会议中的所有用户都可以相互通信，如会议框架[16]中所述。focus有足够的关于会议状态的信息，可以通知订阅者。
It is possible that a participant in the conference may in fact be another focus. In order to provide a more complete participant list, the focus MAY subscribe to the conference package of the other focus to discover the participant list in the cascaded conference. This information can then be included in notifications by use of the <cascaded-focus> element as specified by this package.
会议的一名与会者可能实际上是另一个焦点。为了提供更完整的参与者列表，焦点可以订阅另一个焦点的会议包以发现级联会议中的参与者列表。然后，可以使用此包指定的<cascaded focus>元素将此信息包含在通知中。
This section provides the details for defining a SIP-specific event notification package, as specified by RFC 3265 [10].
本节提供了定义RFC 3265[10]指定的SIP特定事件通知包的详细信息。
The name of this event package is "conference". This package name is carried in the Event and Allow-Events header, as defined in RFC 3265 [10].
此活动包的名称为“会议”。按照RFC 3265[10]中的定义，此包名包含在事件和允许事件标题中。
Filters, which can be applied to conference subscriptions, are a desirable feature and can be considered as a subject of future standardization activities. This document does not define the filters for the conference package to be included in the SUBSCRIBE body.
可以应用于会议订阅的过滤器是一种理想的功能，可以被视为未来标准化活动的主题。本文档未定义要包含在订阅正文中的会议包的筛选器。
A SUBSCRIBE for a conference package, being sent without a body, implies the default subscription filtering policy. The default policy is as follows:
在没有正文的情况下发送会议包的订阅意味着默认的订阅筛选策略。默认策略如下所示：
o Notifications are generated every time there is any change in the state of the conference.
o 每次会议状态发生任何变化时都会生成通知。
o Notifications do not normally contain full state; rather, they only indicate the state that has changed. The exception is a NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the full state of the information requested by the subscriber.
o 通知通常不包含完整状态；相反，它们只指示已更改的状态。例外情况是为响应订阅而发送的通知。这些NOTIFY包含订阅者请求的信息的完整状态。
The default expiration time for a subscription to a conference is one hour. Once the conference ends, all subscriptions to that particular conference are terminated, with a reason of "noresource" as defined in RFC 3265 [10].
会议订阅的默认过期时间为一小时。会议结束后，由于RFC 3265[10]中定义的“noresource”，该特定会议的所有订阅都将终止。
According to RFC 3265 [10], the NOTIFY message will contain bodies that describe the state of the subscribed resource. This body is in a format listed in the Accept header field of the SUBSCRIBE, or a package-specific default if the Accept header field was omitted from the SUBSCRIBE.
根据RFC 3265[10]，NOTIFY消息将包含描述订阅资源状态的主体。此正文采用订阅的Accept header字段中列出的格式，如果订阅中省略了Accept header字段，则为特定于包的默认格式。
In this event package, the body of the notification contains a conference information document that describes the state of a conference. All subscribers and notifiers MUST support the "application/conference-info+xml" data format described in Sections 9
在此事件包中，通知正文包含一个会议信息文档，该文档描述了会议的状态。所有订阅者和通知者必须支持第9节中描述的“应用程序/会议信息+xml”数据格式
and 5. By default, i.e., if no Accept header is specified to a SUBSCRIBE request, the NOTIFY will contain a body in the "application/conference-info+xml" data format. If the Accept header field is present, it MUST include "application/conference-info+xml" and MAY include any other types.
五,。默认情况下，即，如果没有为订阅请求指定Accept标头，则通知将包含“应用程序/会议信息+xml”数据格式的正文。如果存在Accept header字段，则该字段必须包括“应用程序/会议信息+xml”，并且可以包括任何其他类型。
The conference information contains very sensitive information. Therefore, all subscriptions SHOULD be authenticated and then authorized before approval. Authorization policy is at the discretion of the administrator, as always.
会议信息包含非常敏感的信息。因此，在批准之前，所有订阅都应该经过身份验证和授权。与往常一样，授权策略由管理员自行决定。
However, it is RECOMMENDED that all users in the conference be allowed to subscribe to the conference event package.
但是，建议允许会议中的所有用户订阅会议活动包。
Notifications SHOULD be generated for the conference state when a new participant joins (i.e., gets "connected" to) or a participant leaves (i.e., gets "disconnected" from) the conference.
当新参与者加入（即“连接”到）或参与者离开（即“断开”）会议时，应为会议状态生成通知。
Subject to a local focus policy, additional changes in participants' status, changes in their media types, and other optional information MAY be reported by the focus.
根据当地焦点政策，焦点可能会报告参与者状态的其他变化、媒体类型的变化以及其他可选信息。
Changes in sidebar rosters SHOULD be reported by the focus to their participants and MAY be reported to others, subject to local policy.
侧边栏名册的更改应由焦点向其参与者报告，并可根据当地政策向其他人报告。
Changes in conference identifiers and service URIs SHOULD be reported by the focus to the conference package subscribers.
focus应向会议包订户报告会议标识符和服务URI的更改。
Changes in other conference state information MAY be reported by the focus to the conference package subscribers.
焦点可以向会议包订户报告其他会议状态信息的更改。
The SIP events framework expects packages to specify how a subscriber processes NOTIFY requests in any package-specific ways, and in particular, how it uses the NOTIFY requests to construct a coherent view of the state of the subscribed resource.
SIP事件框架期望包指定订阅者如何以包特定的方式处理NOTIFY请求，特别是如何使用NOTIFY请求来构建订阅资源状态的一致视图。
Typically, the NOTIFY for the conference package will only contain information about those users whose state in the conference has changed. To construct a coherent view of the total state of all users, a subscriber to the conference package will need to combine NOTIFYs received over time.
通常，NotifyfortheConference包将只包含有关其在会议中的状态已更改的用户的信息。为了构建所有用户的总体状态的一致视图，会议包的订户需要合并随时间接收的NOTIFY。
Notifications within this package can convey partial information; that is, they can indicate information about a subset of the state associated with the subscription. This means that an explicit algorithm needs to be defined in order to construct coherent and consistent state. The details of this mechanism are specific to the particular document type. See Section 4.6 for information on constructing coherent information from an application/ conference-info+xml document.
此包中的通知可以传递部分信息；也就是说，它们可以指示与订阅关联的状态子集的信息。这意味着需要定义一个显式算法来构造相干和一致的状态。此机制的详细信息特定于特定的文档类型。有关从应用程序/会议信息+xml文档构建连贯信息的信息，请参见第4.6节。
By their nature, the conferences supported by this package are centralized. Therefore, SUBSCRIBE requests for a conference should not generally fork. If forking happens in the network, subscribers to this package MUST NOT establish more than a single SIP dialog as a result of a single SUBSCRIBE request. In the foci cascading case, detailed conference information can be retrieved by establishing an individual SUBSCRIBE dialog with each participating focus.
就其性质而言，此包支持的会议是集中的。因此，会议的订阅请求通常不应该是fork。如果网络中发生分叉，则此包的订阅者不得因单个订阅请求而建立多个SIP对话框。在foci级联情况下，可以通过与每个参与的焦点建立单独的订阅对话框来检索详细的会议信息。
For reasons of congestion control, it is important that the rate of notifications not become excessive. As a result, it is RECOMMENDED that the server does not generate notifications for a single subscriber at a rate faster than once every 5 seconds.
出于拥塞控制的原因，重要的是通知速率不要过高。因此，建议服务器不要以超过每5秒一次的速度为单个订户生成通知。
Conference state is ideally maintained in the element in which the conference resides. Therefore, a conference focus is the best-suited element to handle subscriptions to it. Cascaded foci MAY implement state agents (as defined in RFC 3265 [10]) for this package.
会议状态理想地保持在会议所在的元素中。因此，会议焦点是最适合处理订阅的元素。级联foci可以为该包实现状态代理（如RFC 3265[10]中的定义）。
Conference information is an XML document that MUST be well-formed and valid. It MUST be based on Extensible Markup Language (XML) 1.0 and MUST be encoded using UTF-8 [14].
会议信息是一个XML文档，必须格式良好且有效。它必须基于可扩展标记语言（XML）1.0，并且必须使用UTF-8编码[14]。
This specification makes use of XML namespaces for identifying conference information documents and document fragments. The namespace URI for elements defined by this specification is a Uniform Resource Namespace (URN) [2], using the namespace identifier 'ietf'
本规范使用XML名称空间来标识会议信息文档和文档片段。本规范定义的元素的名称空间URI是统一资源名称空间（URN）[2]，使用名称空间标识符“ietf”
defined by [6] and extended by RFC 3688 [21]. This URN is as follows:
由[6]定义，并由RFC 3688[21]扩展。该骨灰盒如下：
urn:ietf:params:xml:ns:conference-info
urn:ietf:params:xml:ns:conference-info
The conference information is described by a hierarchical XML structure with the root element <conference-info>. The root element is the only element in the schema that carries a meaningful version number for all the elements in the document. The whole conference information is associated with this version number.
会议信息由根元素<conference info>的分层XML结构描述。根元素是模式中唯一为文档中的所有元素携带有意义的版本号的元素。整个会议信息都与此版本号关联。
The 'version' attribute MUST be included in the root <conference-info> element.
“version”属性必须包含在根<conference info>元素中。
This specification defines a basic partial notifications mechanism by using a 'state' attribute as described below. This mechanism MUST be supported by all subscribing clients. Additional general partial notifications mechanisms can be defined and applied to this package in the future.
本规范通过使用“状态”属性定义基本的部分通知机制，如下所述。所有订阅客户端都必须支持此机制。将来可以定义附加的通用部分通知机制并将其应用于此包。
All sub-elements in the <conference-info> hierarchical XML structure can be classified in two groups: permissible for partial notifications or not. Elements that carry a substantial amount of data that is subject to frequent changes are permissible for partial notifications and have a 'state' attribute attached to them. All future extensions to this schema MUST define which extension elements can also use this mechanism. All other elements can be updated as atomic pieces of data only.
<conference info>分层XML结构中的所有子元素可以分为两组：允许部分通知还是不允许部分通知。包含大量数据且经常更改的元素可用于部分通知，并且具有“状态”属性。此模式的所有未来扩展必须定义哪些扩展元素也可以使用此机制。所有其他元素只能作为原子数据块更新。
Below is the complete list of elements permissible to use the partial notifications mechanism defined in this specification. (Note that future partial notifications mechanisms can potentially be applicable to additional elements.)
下面是允许使用本规范中定义的部分通知机制的元素的完整列表。（请注意，未来的部分通知机制可能适用于其他元素。）
o Element <conference-info> o Element <users> o Element <user> o Element <endpoint> o Element <sidebars-by-val> o Element <sidebars-by-ref>
o 元素<conference info>o元素<users>o元素<user>o元素<endpoint>o元素<sidebars by val>o元素<sidebars by ref>
The 'state' attribute value indicates whether the reported information about the element is "full" or "partial", or whether the element has been "deleted" from the conference state document. The default value of any 'state' attribute is "full".
“状态”属性值表示报告的元素信息是“完整”还是“部分”，或者该元素是否已从会议状态文档中“删除”。任何“state”属性的默认值都是“full”。
A 'state' attribute of a child element in the document MUST be consistent with its parent 'state'. This means that if the parent's 'state' is "full", the state of its children MUST be "full". If the parent's 'state' is "partial", the state of its children MAY be either "partial", "full", or "deleted". A parent element with "deleted" 'state' SHOULD NOT contain child elements. Any information provided for child elements of a "deleted" parent MUST be ignored by the package subscriber.
文档中子元素的“状态”属性必须与其父元素“状态”一致。这意味着，如果父母的“状态”为“满”，则其子女的状态必须为“满”。如果父母的“状态”为“部分”，则其子女的状态可能为“部分”、“完全”或“已删除”。具有“已删除”“状态”的父元素不应包含子元素。包订阅服务器必须忽略为“已删除”父元素的子元素提供的任何信息。
The defined XML schema has a property of unique identification among sub-elements of a common parent, which makes it possible to use the partial notifications mechanism defined in this document. This property is achieved by defining a key to each sub-element that can appear multiple times under the common parent.
定义的XML模式在公共父元素的子元素之间具有唯一标识的属性，这使得可以使用本文档中定义的部分通知机制。此属性是通过为每个子元素定义一个键来实现的，这些子元素可以在公共父元素下多次出现。
In the context of this specification, the element key is the set of mandatory attributes or sub-elements of an element. The key value MUST be unique for the element among its siblings of the same type.
在本规范的上下文中，元素键是元素的一组必需属性或子元素。元素的键值在其相同类型的同级中必须是唯一的。
In the context of this specification, two keys of type xs:anyURI are considered to be equal if the UTF-8 representations of the keys (including all URI parameters that can be included with the URI) are identical. Consequently, using relative URIs and lexical white space in these keys is NOT RECOMMENDED.
在本规范的上下文中，如果两个xs:anyURI类型的键的UTF-8表示（包括可以包含在URI中的所有URI参数）相同，则认为它们相等。因此，不建议在这些键中使用相对URI和词汇空白。
Below is the list of elements (subject to partial notifications of their parent elements) with their keys as defined by this specification:
以下是元素列表（根据其父元素的部分通知）及其键，如本规范所定义：
o Element <user> uses as the key 'entity' o Element <endpoint> uses as the key 'entity' o Element <media> uses as the key 'id' o Element <entry> (child to <sidebars-by-val>) uses as the key 'entity' o Element <sidebars-by-ref> uses as the key <uri>
o 元素<user>用作键“entity”o元素<endpoint>用作键“entity”o元素<media>用作键“id”o元素<entry>（子元素<sidebars by val>）用作键“entity”o元素<sidebars by ref>用作键<uri>
This section describes the algorithm for constructing a coherent conference state by a subscriber to the conference package. Using software programming abstraction, the subscriber maintains a single
本节描述由会议包的订户构造相干会议状态的算法。使用软件编程抽象，订户维护单个
local version number for the whole conference document and a local element instance for each element in the schema. Also, for each element with keys (as defined above), the subscriber maintains a virtual table with a row for each existing key value.
整个会议文档的本地版本号和架构中每个元素的本地元素实例。此外，对于具有键的每个元素（如上所述），订阅者维护一个虚拟表，其中每个现有键值都有一行。
The first time a NOTIFY with a "full" document is received (as indicated by the value of the 'state' attribute in the <conference-info> element), the conference package subscriber MUST set the local 'version' number to the value of the 'version' attribute from the received <conference-info> and populate local data with the received information.
第一次收到带有“完整”文档的通知时（如<conference info>元素中“state”属性的值所示），会议包订户必须将本地“version”编号设置为收到的<conference info>中“version”属性的值，并用收到的信息填充本地数据。
Each time a new NOTIFY is received, the value of the local version number and the value of the 'version' attribute in the new received document are compared. If the value in the document is equal to or less than the local version, the document is discarded without processing.
每次收到新通知时，都会比较本地版本号的值和新接收文档中“版本”属性的值。如果文档中的值等于或小于本地版本，则文档将在不进行处理的情况下丢弃。
Otherwise, if the received NOTIFY contains a "full" or "deleted" state, the conference package subscriber MUST set the local 'version' number to the value of the 'version' attribute from the received <conference-info> and replace the local information with the received document. Receiving "deleted" state for the <conference-info> element means that the conference has ceased to exist and the subscriber SHOULD terminate the subscription by sending the SUBSCRIBE with Expires = 0.
否则，如果收到的通知包含“完整”或“已删除”状态，则会议包订户必须将本地“版本”编号设置为收到的<conference info>中的“版本”属性值，并用收到的文档替换本地信息。接收到<conference info>元素的“deleted”状态意味着会议已不存在，订阅者应通过发送Expires=0的订阅来终止订阅。
Otherwise (i.e., if the received NOTIFY contains "partial" state), if the 'version' number in the received document is more than one number higher than the previous local version number, the subscriber MUST generate a subscription refresh request to trigger a full state notification. If the 'version' number in the document is one higher than the local version number, the local version number is updated accordingly and the document is used to update the local content as described below.
否则（即，如果收到的通知包含“部分”状态），如果收到的文档中的“版本”号比以前的本地版本号高出一个以上，则订阅者必须生成订阅刷新请求以触发完全状态通知。如果文档中的“版本”号比本地版本号高一个，则本地版本号将相应更新，文档用于更新本地内容，如下所述。
For each sub-element of the <conference-info> element in the received document,
对于所接收文档中<conference info>元素的每个子元素，
1. If the element contains "full" state, the whole local element content is flushed and repopulated from the document.
1. 如果元素包含“full”状态，则从文档中刷新并重新填充整个本地元素内容。
2. Otherwise, if the element contains "deleted" state, the whole element MUST be removed from the local content.
2. 否则，如果元素包含“已删除”状态，则必须从本地内容中删除整个元素。
3. Otherwise, if the element contains "partial" state:
3. 否则，如果元素包含“部分”状态：
3.1. For elements with keys, the subscriber compares the keys received in the update with the keys in the local tables.
3.1. 对于具有键的元素，订阅者将更新中接收的键与本地表中的键进行比较。
3.1.1. If a key does not exist in the local table, a row is added, and its content is set to the element information from the update.
3.1.1. 如果本地表中不存在键，则会添加一行，并将其内容设置为更新中的元素信息。
3.1.2. Otherwise, if a key of the same value does exist, for each sub-element in the row, the algorithm is applied from step 3.2.
3.1.2. 否则，如果存在相同值的键，则对于行中的每个子元素，从步骤3.2开始应用算法。
3.2. For each atomic element received in the schema, the element is replaced with the new information as a whole. For each non-atomic element received in the schema with either no 'state' attribute included or the state attribute is set to "full", the element is replaced with the new information as a whole. Also, for each element with the state attribute set to "deleted", the whole element is removed from the local content.
3.2. 对于模式中接收到的每个原子元素，该元素作为一个整体替换为新信息。对于架构中接收到的每个非原子元素，如果没有包含“state”属性，或者state属性设置为“full”，则整个元素将替换为新信息。另外，对于state属性设置为“deleted”的每个元素，将从本地内容中删除整个元素。
3.3. For each non-atomic element with the state attribute set to "partial", the algorithm is applied recursively starting from step 3.1.
3.3. 对于state属性设置为“partial”的每个非原子元素，从步骤3.1开始递归应用该算法。
The <conference-info> document format is designed to convey information about the conference and about participation in the conference. The following non-normative diagram gives an example of the overall hierarchy used in this format. Conferences contain users who can be represented by multiple endpoints, each of which can have multiple media streams. Conferences can also include or reference "sidebar conferences". When sidebar information is incorporated into a conference information document in a <sidebars-by-val> element, each <entry> element represents a sidebar and can include any sub-elements permitted in the <conference-info> top-level element.
<conference info>文档格式旨在传达有关会议和参与会议的信息。以下非规范性图表给出了此格式中使用的整体层次结构的示例。会议包含可以由多个端点表示的用户，每个端点可以有多个媒体流。会议还可以包括或引用“侧栏会议”。当边栏信息被合并到<sidebars by val>元素中的会议信息文档中时，每个<entry>元素表示一个边栏，并且可以包括<conference info>顶级元素中允许的任何子元素。
conference-info
|
|-- conference-description
|
|-- host-info
|
|-- conference-state
|
|-- users
| |-- user
| | |-- endpoint
| | | |-- media
| | | |-- media
| | | |-- call-info
| | |
| | |-- endpoint
| | |-- media
| |-- user
| |-- endpoint
| |-- media
|
conference-info
|
|-- conference-description
|
|-- host-info
|
|-- conference-state
|
|-- users
| |-- user
| | |-- endpoint
| | | |-- media
| | | |-- media
| | | |-- call-info
| | |
| | |-- endpoint
| | |-- media
| |-- user
| |-- endpoint
| |-- media
|
|-- sidebars-by-ref
| |-- entry
| |-- entry
|
|-- sidebars-by-val
|-- entry
| |-- users
| |-- user
| |-- user
|-- entry
|-- users
|-- user
|-- user
|-- user
|-- sidebars-by-ref
| |-- entry
| |-- entry
|
|-- sidebars-by-val
|-- entry
| |-- users
| |-- user
| |-- user
|-- entry
|-- users
|-- user
|-- user
|-- user
In most cases, this document does not mandate how the information, presented through the conference document to the subscribers, is obtained by the focus. In many cases, the information can be dynamically learned from the call signaling and can also be manually populated by an administrator - all subject to local policies. This document specifies what the XML elements mean in order to allow the subscribers to appropriately interpret it. Some portions of the information are intended for processing by automata; others are for human consumption only. For example, the <display-text> sub-elements of elements <conf-uris>, <service-uris>, <available-media>,
在大多数情况下，本文件并不规定焦点如何获得通过会议文件向订阅者提供的信息。在许多情况下，信息可以从呼叫信令中动态学习，也可以由管理员手动填充-所有这些都受本地策略的约束。此文档指定XML元素的含义，以便允许订阅者对其进行适当的解释。信息的某些部分用于自动机处理；其他的只供人类食用。例如，元素<conf uris>，<service uris>，<available media>的<display text>子元素，
<host-info>, <endpoint>, and <media> are intended for display to human subscribers only.
<host info>、<endpoint>和<media>仅用于向人类订阅者显示。
Although in multiple places this document states that specific information "SHOULD" be communicated to the subscribers, note that particular conference package subscribers (e.g., representing a moderator, an administrator, or a cascaded focus) rely on accuracy of this information for their proper operation. Therefore, a conferencing server MUST ensure that all critical changes (stated as "SHOULD") are communicated to these specific subscribers; otherwise, these changes MUST be communicated to all subscribers to the conference information.
尽管在多个地方，本文件规定特定信息“应”传达给订阅者，但请注意，特定的会议包订阅者（例如，代表主持人、管理员或级联焦点）依赖于该信息的准确性来进行正确操作。因此，会议服务器必须确保将所有关键更改（声明为“应该”）传达给这些特定订户；否则，这些更改必须传达给会议信息的所有订阅者。
Following sections describe the XML schema in more detail.
以下各节将更详细地描述XML模式。
A conference information document begins with the root element tag <conference-info> of conference-type.
会议信息文档以会议类型的根元素标记<conference info>开头。
The following attributes are defined for <conference-info>:
为<conference info>定义了以下属性：
entity: This attribute contains the conference URI that identifies the conference being described in the document. This is the SIP URI that an interested entity needs to SUBSCRIBE to in order to get the conference package information. Note that this URI can be listed as one of the URIs to be used in order to access the conference by SIP means and in accordance with Section 5.3.1 below.
实体：此属性包含会议URI，用于标识文档中描述的会议。这是感兴趣的实体需要订阅的SIPURI，以便获取会议包信息。请注意，根据下面第5.3.1节的规定，该URI可以列为通过SIP方式访问会议所使用的URI之一。
state: This attribute indicates whether the document contains the whole conference information ("full") or only the information that has changed since the previous document ("partial"), or whether the conference ceased to exist ("deleted"). For more detail, see Section 4.
状态：此属性表示文档是否包含整个会议信息（“完整”）或仅包含自上一个文档以来已更改的信息（“部分”），或会议是否已不存在（“删除”）。有关更多详细信息，请参见第4节。
version: This attribute allows the recipient of conference information documents to properly order the received notifications, and it MUST be used with the root <conference-info> element. Version number is a 32-bit monotonically increasing integer scoped within a subscription. A server MUST increment the version number for each notification (full, partial, and deleted) being sent to a subscriber and reporting a change in the conference document state. For each partial notification, the version number MUST be increased by one. Note that a partial notification and a subsequent full notification over the same dialog MAY contain the same version number if no change in the conference state occurred in between.
版本：此属性允许会议信息文档的收件人正确排序收到的通知，并且必须与root<conference info>元素一起使用。版本号是订阅中作用域内的32位单调递增整数。服务器必须为发送给订阅服务器并报告会议文档状态更改的每个通知（完整、部分和删除）增加版本号。对于每个部分通知，版本号必须增加一个。请注意，如果在此期间会议状态没有发生更改，则通过同一对话框的部分通知和后续完整通知可能包含相同的版本号。
The <conference-info> element is comprised of <conference-description>, <host-info>, <conference-state>, <users>, <sidebars-by-ref> and <sidebars-by-val> child elements. A "full" conference document MUST at least include the <conference-description> and <users> child elements.
<conference info>元素由<conference description>、<host info>、<conference state>、<users>、<sidebars by ref>和<sidebars by val>子元素组成。“完整”会议文档必须至少包含<conference description>和<users>子元素。
Following sections describe these elements in detail. The full XML schema is provided in Section 6.
以下各节将详细介绍这些元素。第6节提供了完整的XML模式。
The <conference-description> element describes the conference as a whole.
<conference description>元素将会议描述为一个整体。
The child elements <display-text>, <subject>, <free-text>, and <keywords> are used to describe the conference content:
子元素<display text>、<subject>、<free text>和<keywords>用于描述会议内容：
<display-text>: Contains descriptive text suitable for human consumption, for example, listing in a directory
<display text>：包含适合人类使用的描述性文本，例如，在目录中列出
<subject>: Contains the subject of the conference
<subject>: Contains the subject of the conference
<free-text>: Contains an additional longer description of the conference
<free text>：包含会议的附加更长描述
<keywords>: Contains a list of space-separated string tokens that can be used by search engines to better classify the conference
<keywords>：包含空格分隔的字符串标记列表，搜索引擎可以使用这些标记更好地对会议进行分类
Additional child elements <conf-uris> and <service-uris> are used to describe the conference-related URIs; <maximum-user-count> and <available-media> are used to describe the overall characteristics.
附加的子元素<conf uri>和<service uri>用于描述与会议相关的uri<最大用户数>和<available media>用于描述总体特征。
This information is typically derived from the system conference policies, is set before the conference activation, and is rarely changed during the conference lifetime.
此信息通常来自系统会议策略，在会议激活之前设置，在会议生命周期内很少更改。
The following sections describe the remaining elements in more detail. Other sub-elements can extend <conference-description> in the future.
以下各节将更详细地描述其余元素。其他子元素将来可以扩展<conference description>。
This element contains a sequence of <entry> child elements - each containing the URI to be used in order to access the conference by different signaling means. The value of the URI MUST be unique in the conference context and is included in the <uri> sub-element.
该元素包含一系列<entry>子元素，每个子元素都包含要使用的URI，以便通过不同的信令方式访问会议。URI的值在会议上下文中必须是唯一的，并且包含在<URI>子元素中。
Each <entry> MAY contain additional information useful to the participant when accessing the conference.
每个<entry>可能包含对参与者访问会议时有用的附加信息。
An <entry> element MAY contain the <display-text> sub-element that provides a textual description meant for human consumption.
一个<entry>元素可能包含<display text>子元素，该子元素提供供人类使用的文本描述。
Each <entry> element SHOULD contain a <purpose> sub-element that describes what happens when accessing the URI. The currently defined <purpose> values to be used with the <conf-uris> are the following:
每个<entry>元素都应该包含一个子元素<purpose>，该子元素描述访问URI时发生的情况。与<conf uri>一起使用的当前定义的<purpose>值如下：
participation: Accessing a URI with this <purpose> will bring the party into the conference.
参与：使用此<purpose>访问URI将使该方加入会议。
streaming: Accessing a URI with this <purpose> will commence streaming the conference, but not allow active participation.
流式传输：使用此<purpose>访问URI将开始流式传输会议，但不允许主动参与。
Examples of suitable URI schemes include sip: and sips: [8], xmpp: [22], h323: [20], and tel: [19] URIs. The rtsp [18] URI is suitable for streaming.
合适的URI方案的示例包括sip:和sips:[8]、xmpp:[22]、h323:[20]和tel:[19]URI。rtsp[18]URI适合于流式传输。
Future extensions to this schema may define new values and register them with IANA under the registry established by this specification.
此模式的未来扩展可能会定义新值，并在本规范建立的注册表下向IANA注册这些值。
This element describes auxiliary services available for the conference. Like <conference-uris>, this element contains a set of <entry> child elements - each containing the URI to be used in order to access different services available for the particular conference. The value of the URI MUST be unique in the conference context and is included in the <uri> sub-element.
此元素描述可用于会议的辅助服务。与<conference URI>类似，此元素包含一组<entry>子元素，每个子元素都包含用于访问特定会议的不同服务的URI。URI的值在会议上下文中必须是唯一的，并且包含在<URI>子元素中。
An <entry> element MAY contain the <display-text> sub-element that provides a textual description meant for user consumption.
<entry>元素可能包含<display text>子元素，该子元素提供供用户使用的文本描述。
Each <entry> element SHOULD contain a <purpose> sub-element. The currently defined <purpose> values to be used with the <service-uris> are the following:
每个<entry>元素应包含一个子元素<purpose>。与<service uri>一起使用的当前定义的<purpose>值如下：
web-page: Indicates the web page containing the additional information about the conference.
网页：表示包含会议附加信息的网页。
recording: Indicates the link at which the recorded conference context can be retrieved.
录制：表示可在其中检索录制的会议上下文的链接。
event: Indicates the URI at which a subscription to the conference event package may be requested. This would typically be the conference URI of the main conference.
事件：表示可以请求订阅会议事件包的URI。这通常是主会议的会议URI。
Future extensions to this schema may define new values and register them with IANA under the registry established by this specification.
此模式的未来扩展可能会定义新值，并在本规范建立的注册表下向IANA注册这些值。
The value of this element provides a hint to the recipient of the conference document about the number of users that can be invited to the conference. Typically, this value represents the overall number of users allowed to join the conference by different means as published through the conference document in <conf-uris>. Note that this value is set by an administrator and can reflect any local policies combination such as network consumption, CPU processing power, and licensing rules.
此元素的值向会议文档的接收者提供有关可邀请参加会议的用户数的提示。通常，此值表示通过<conf uris>中的会议文档发布的允许通过不同方式加入会议的用户总数。请注意，此值由管理员设置，可以反映任何本地策略组合，如网络消耗、CPU处理能力和许可规则。
This element contains a sequence of <entry> child elements of conference-medium-type, each being indexed by the attribute 'label'.
此元素包含会议媒体类型的<entry>子元素序列，每个子元素都由属性“label”索引。
The 'label' attribute is the media stream identifier assigned by the conferencing server: its value will be unique in the <conference-info> context. The value of this attribute will typically correspond to the Session Description Protocol (SDP) "label" media attribute defined in [17].
“label”属性是会议服务器分配的媒体流标识符：其值在<conference info>上下文中是唯一的。该属性的值通常对应于[17]中定义的会话描述协议（SDP）“标签”媒体属性。
Each <entry> describes a single media stream available to the participants in the conference and contains the following information:
每个<entry>描述可供会议参与者使用的单个媒体流，并包含以下信息：
<display-text>: This element contains the display text for the media stream.
<display text>：此元素包含媒体流的显示文本。
<type>: This element contains the media type of the media stream. The value of this element MUST be one of the values registered for "media" of SDP [3] and its later revision(s), for example, "audio", "video", "text", and "message".
<type>：此元素包含媒体流的媒体类型。此元素的值必须是SDP[3]及其更高版本的“媒体”注册值之一，例如，“音频”、“视频”、“文本”和“消息”。
<status>: This element indicates the available status of the media stream available to the conference participants. For example, this would be the status of the media stream, which would be offered by the focus, in a 'dial-out' scenario. Using normal SIP offer/answer mechanisms (being defined in RFC 3264 [9]) in both dial-in and dial-out scenarios, a participant can of course establish only a subset of the available stream (i.e., request or accept the stream in one direction only, if both directions are available). The valid values are "sendrecv", "sendonly", "recvonly", or "inactive" as defined in SDP [3] and its later
<status>：此元素指示可供会议参与者使用的媒体流的可用状态。例如，在“拨出”场景中，这将是由焦点提供的媒体流的状态。在拨入和拨出场景中使用正常的SIP提供/应答机制（在RFC 3264[9]中定义），参与者当然只能建立可用流的子集（即，如果两个方向都可用，则仅在一个方向上请求或接受流）。有效值为SDP[3]及其更高版本中定义的“sendrecv”、“sendonly”、“RecVoOnly”或“inactive”
revision(s). (Note that the value specifies the direction from the participants' point of view.)
修订本。（请注意，该值指定了参与者视角的方向。）
This element contains information about the entity hosting the conference. This information is set before the conference activation, and it is rarely changed during the conference lifetime, unless the whole conference is moved to be hosted by another entity. The host information is comprised of the following elements:
此元素包含有关会议主办实体的信息。此信息在会议激活之前设置，在会议生命周期内很少更改，除非整个会议被移动到另一个实体主持。主机信息由以下元素组成：
This element contains display text describing the entity hosting the conference.
此元素包含描述会议主办实体的显示文本。
This element contains HTTP: or HTTPS: URI of a web page describing either the conference service or the user hosting the conference.
此元素包含描述会议服务或主持会议的用户的网页的HTTP:或HTTPS:URI。
This element contains a set of <entry> child elements, each containing the URI value and optionally its description.
该元素包含一组<entry>子元素，每个子元素都包含URI值和可选的描述。
By including this element in the conference document, the server can inform the subscribers about the changes in the overall conference information. The <conference-state> child elements are described below.
通过在会议文档中包含此元素，服务器可以将整个会议信息中的更改通知订阅者。下面描述<conference state>子元素。
The value of this element tells the recipient of the conference document the overall number of users participating in the conference at a certain moment. Typically, this value represents the overall number of users who joined the conference by different means as published through the conference document in <conf-uris>. Note that this number does not necessarily need to match and MAY exceed the number of the entries in the <users> container. For example, in a lecturing scenario, large conference notifications may not include every participant in the <users> element, but instead report only the panelists or the speakers.
该元素的值告诉会议文档的接收者在某一时刻参与会议的用户总数。通常，此值表示通过<conf uris>中的会议文档发布的以不同方式加入会议的用户总数。请注意，此数字不一定需要匹配，可能会超过<users>容器中的条目数。例如，在演讲场景中，大型会议通知可能不包括<users>元素中的每个参与者，而是只报告小组成员或发言人。
This Boolean element indicates whether the conference is currently active. A conference is active if calling one of the <conf-uris> by an authorized client results in successful establishment of a signaling session between the client and the focus and a successful joining of the conference.
此布尔元素指示会议当前是否处于活动状态。如果授权客户端调用其中一个<conf uri>导致在客户端和焦点之间成功建立信令会话并成功加入会议，则会议处于活动状态。
This Boolean element says whether the conference is currently locked. In this context, "locked" means that the conference roster cannot be added to (although participants may leave or be removed from the conference).
此布尔元素表示会议当前是否已锁定。在这种情况下，“锁定”意味着无法将会议名册添加到（尽管与会者可能离开或从会议中删除）。
The <users> element is a container of <user> child elements, each describing a single participant in the conference.
<users>元素是<user>子元素的容器，每个子元素描述会议中的单个参与者。
The following attributes are defined for <user> element:
为<user>元素定义了以下属性：
entity: This attribute contains the URI for the user in the conference. This is a logical identifier, which corresponds to the call signaling authenticated identity of the participant. The 'entity' value MUST be unique among all participants in the conference. If, for some participants, the focus decides not to reveal this information (e.g., due to local policies or security reasons), the host portion of the user URI MUST use the .invalid top level domain (TLD) according to definitions of RFC 2606 [5]. The focus also MUST construct the user portion of the URI so that the URI is unique among all participants of the same domain. For example, the convention
实体：此属性包含会议中用户的URI。这是一个逻辑标识符，对应于参与者的呼叫信令认证标识。“实体”价值在会议的所有参与者中必须是唯一的。如果对于某些参与者，focus决定不披露此信息（例如，由于本地策略或安全原因），则用户URI的主机部分必须根据RFC 2606[5]的定义使用.invalid top level domain（TLD）。焦点还必须构造URI的用户部分，以便URI在同一域的所有参与者中是唯一的。例如，公约
"AnonymousX" <sip:anonymousX@anonymous.invalid>
"AnonymousX" <sip:anonymousX@anonymous.invalid>
SHOULD be used for a participant requesting privacy in accordance with the guidelines for generating anonymous URIs of RFC 3323 [11]. Note that in a different case, such as when used in conjunction with Enhancements for Authenticated Identity Management in SIP [25], the following convention can be used:
应根据RFC 3323[11]中生成匿名URI的指南，用于请求隐私的参与者。请注意，在不同的情况下，例如与SIP[25]中的身份验证管理增强功能结合使用时，可以使用以下约定：
"AnonymousX" <sip:anonymousX@example.com>
"AnonymousX" <sip:anonymousX@example.com>
state: This attribute indicates whether the document contains the whole user information ("full") or only the information that has changed since the previous document ("partial"), or whether the user was removed from the conference ("deleted").
状态：此属性表示文档是否包含整个用户信息（“完整”）或仅包含自上一个文档以来已更改的信息（“部分”），或者用户是否已从会议中删除（“删除”）。
The following child elements are defined for <user> element:
为<user>元素定义了以下子元素：
This element is used to display the user-friendly name in the conference.
此元素用于在会议中显示用户友好的名称。
This element contains additional (to the 'entity') URIs being associated with the <user>. Typically, this information will be manually provided by an administrator showing the logical association between signaling entities otherwise independent. For example, if the 'entity' of a <user> contains a Globally Routable User URI (GRUU) [24] or tel: URI RFC 3966 [19], it would be useful to populate this field with the Address of Record (AOR) of the person who uses these devices, each represented as an independent <user>.
此元素包含与<user>关联的其他（实体）URI。通常，该信息将由管理员手动提供，显示信令实体之间的逻辑关联。例如，如果<user>的“实体”包含全局可路由用户URI（GRUU）[24]或tel:URI RFC 3966[19]，则使用使用这些设备的人的记录地址（AOR）填充此字段将非常有用，每个设备都表示为独立的<user>。
This element MAY contain a set of human-readable strings describing the roles of the user in the conference. Note that this information is applicable for human consumption only. This specification does not define the set of possible conferencing roles or the semantics associated with each. It is expected that future conferencing specifications will define these and the corresponding schema extensions, as appropriate.
该元素可以包含描述用户在会议中的角色的一组人类可读字符串。请注意，此信息仅适用于人类消费。本规范未定义可能的会议角色集或与每个角色关联的语义。预计未来的会议规范将酌情定义这些和相应的模式扩展。
This element contains a list of tokens, separated by spaces, each containing a language understood by the user. This information can be automatically learned via call signaling or be manually set per participant.
该元素包含一个标记列表，标记之间用空格分隔，每个标记都包含用户可以理解的语言。该信息可以通过呼叫信号自动学习，也可以根据每个参与者手动设置。
This element contains a conference URI (different from the main conference URI) for users that are connected to the main conference as a result of focus cascading. In accordance with the SIP Conferencing Framework [16], this package allows for representation of peer-to-peer (i.e., "flat") focus cascading only. The actual cascading graph cannot be deduced from the information provided in the package alone. Advanced applications can construct the graph by subscribing to both this package and the Dialog Package [23] of each cascaded focus and correlating the relevant information.
此元素包含一个会议URI（与主会议URI不同），用于通过焦点级联连接到主会议的用户。根据SIP会议框架[16]，此包仅允许表示点对点（即“平面”）焦点级联。实际的级联图不能仅从包中提供的信息推断出来。高级应用程序可以通过订阅此包和每个级联焦点的对话框包[23]并关联相关信息来构建图形。
By including one or more <endpoint> elements under a parent <user> element, the server can provide the desired level of detail (including the state, media streams, and access information) about the user's devices and signaling sessions taking part in the conference.
通过在父<user>元素下包括一个或多个<endpoint>元素，服务器可以提供关于参与会议的用户设备和信令会话的所需详细程度（包括状态、媒体流和访问信息）。
In a conferencing system where authentication is performed per endpoint (rather than per user), the focus can be unaware of the logical association of multiple endpoints under a common user. In this case, each endpoint will appear as a separate <user> with its own <endpoint> sub-element(s) in the conference document.
在每个端点（而不是每个用户）执行身份验证的会议系统中，焦点可能不知道公共用户下多个端点的逻辑关联。在这种情况下，每个端点将在会议文档中显示为一个单独的<user>，具有自己的<endpoint>子元素。
In a different case, the focus may choose to shield the information about the participant's multiple endpoints and signaling sessions from other subscribers altogether (e.g., due to privacy policies). To do so, the focus MAY aggregate the multiple signaling sessions' information under a single <endpoint> element. Note that in this case, the detailed call signaling information (represented by <call-info> sub-element) will not be included.
在不同的情况下，焦点可以选择将关于参与者的多个端点和信令会话的信息完全屏蔽给其他订户（例如，由于隐私策略）。为此，焦点可以在单个<endpoint>元素下聚合多个信令会话的信息。注意，在这种情况下，将不包括详细的呼叫信令信息（由<call info>子元素表示）。
This section describes the <endpoint> element in more detail.
本节更详细地描述<endpoint>元素。
The following attributes are defined for the <endpoint> element:
为<endpoint>元素定义了以下属性：
entity: The server MUST generate the 'entity' key for each <endpoint> element included under the parent <user>, such that its value is unique in the user context. In SIP terms, this can be the Contact URI, GRUU, etc.
实体：服务器必须为父<user>下包含的每个<endpoint>元素生成“实体”键，以便其值在用户上下文中是唯一的。在SIP术语中，这可以是联系人URI、GRUU等。
state: This attribute indicates whether the element contains the whole endpoint information ("full") or only the information that has changed since the previous document ("partial"), or whether the endpoint has been removed from the conference ("deleted").
状态：此属性指示元素是否包含整个端点信息（“完整”）或仅包含自上一个文档以来已更改的信息（“部分”），或端点是否已从会议中删除（“删除”）。
The following child elements are defined for the <endpoint> element:
为<endpoint>元素定义了以下子元素：
This element contains the display text for the endpoint.
此元素包含端点的显示文本。
This element contains information about the user whose action resulted in this endpoint being brought into the conference (e.g., the SIP user identified by this URI sent a REFER to the focus). It MAY contain the following sub-elements:
此元素包含有关其操作导致此端点进入会议的用户的信息（例如，此URI标识的SIP用户发送了一个指向焦点的引用）。它可能包含以下子元素：
when: This element of the XML dateTime type contains the date and time that the endpoint was referred to the conference and SHOULD be expressed in Coordinated Universal Time (UTC) format. For example,
when：XML dateTime类型的此元素包含端点引用到会议的日期和时间，并且应以协调世界时（UTC）格式表示。例如
<when>2005-03-04T20:00:00Z</when>
<when>2005-03-04T20:00:00Z</when>
reason: This element contains the reason the endpoint was referred to the conference. Including the information in the format defined by RFC 3326 [12] is RECOMMENDED. For example,
原因：此元素包含端点被引用到会议的原因。建议以RFC 3326[12]定义的格式包含信息。例如
<reason>Reason: SIP;text="Ad-hoc Invitation"</reason>
<reason>Reason: SIP;text="Ad-hoc Invitation"</reason>
by: This element contains the URI of the entity that caused the endpoint to be referred to the conference. In the case of SIP, it will be populated from the Referred-By header defined in RFC 3892 [15].
by：此元素包含导致端点被引用到会议的实体的URI。在SIP的情况下，将从RFC 3892[15]中定义的Referenced By标头填充它。
This element contains the status of the endpoint and can assume the following values:
此元素包含端点的状态，可以采用以下值：
connected: The endpoint is a participant in the conference. Depending on the media policies, he/she can send and receive media to and from other participants.
已连接：端点是会议的参与者。根据媒体政策，他/她可以向其他参与者发送和接收媒体。
disconnected: The endpoint is not a participant in the conference, and no active dialog exists between the endpoint and the focus.
断开连接：终结点不是会议的参与者，并且终结点和焦点之间不存在活动对话框。
on-hold: Active signaling dialog exists between an endpoint and a focus, but endpoint is "on-hold" for this conference, i.e., he/she is neither "hearing" the conference mix nor is his/her media being mixed in the conference. As an example, the endpoint has asked to join the conference using SIP, but his/her participation is pending based on moderator approval. In the meantime, he/she is hearing music-on-hold or some other kind of related content.
暂停：端点和焦点之间存在活动信令对话，但端点对此会议“暂停”，即他/她既没有“听到”会议混合，也没有在会议中混合他/她的媒体。例如，端点已请求使用SIP加入会议，但根据主持人的批准，他/她的参与尚未确定。与此同时，他/她正在收听暂停播放的音乐或其他相关内容。
muted-via-focus: Active signaling dialog exists between an endpoint and a focus and the endpoint can "listen" to the conference, but the endpoint's media is not being mixed into the conference. Note
通过焦点静音：端点和焦点之间存在活动信令对话框，端点可以“侦听”会议，但端点的媒体未混合到会议中。笔记
that sometimes a subset of endpoint media streams can be muted by focus (such as poor-quality video) while others (such as voice or IM) can still be active. In this case, it is RECOMMENDED that the "aggregated" endpoint connectivity <status> reflects the status of the most active media.
有时，端点媒体流的一个子集可以通过焦点（如劣质视频）静音，而其他媒体流（如语音或IM）仍然可以活动。在这种情况下，建议“聚合”端点连接<status>反映最活跃介质的状态。
pending: Endpoint is not yet in the session, but it is anticipated that he/she will join in the near future.
待定：Endpoint尚未在会话中，但预计他/她将在不久的将来加入。
alerting: A Public Switched Telephone Network (PSTN) ALERTING or SIP 180 Ringing was returned for the outbound call; endpoint is being alerted.
警报：为出站呼叫返回公共交换电话网络（PSTN）警报或SIP 180铃声；正在向终结点发出警报。
dialing-in: Endpoint is dialing into the conference, not yet in the roster (probably being authenticated).
拨入：端点正在拨入会议，但尚未在花名册中（可能正在验证）。
dialing-out: Focus has dialed out to connect the endpoint to the conference, but the endpoint is not yet in the roster (probably being authenticated).
拨出：Focus已拨出以将端点连接到会议，但端点尚未在名册中（可能正在验证）。
disconnecting: Focus is in the process of disconnecting the endpoint (e.g., in SIP a DISCONNECT or BYE was sent to the endpoint).
断开连接：焦点处于断开端点连接的过程中（例如，在SIP中，向端点发送了断开连接或BYE）。
Note that the defined transient statuses (e.g., disconnecting, alerting, etc.) could generate a lot of traffic. Therefore, implementations MAY choose to generate notifications on these statuses to certain participants only or not generate them at all, subject to local policy.
请注意，定义的瞬态状态（例如，断开连接、报警等）可能会产生大量流量。因此，根据本地策略，实现可以选择仅向某些参与者生成关于这些状态的通知，也可以选择根本不生成通知。
This element contains the method by which the endpoint joined the conference and can assume the following values:
此元素包含端点加入会议的方法，可以采用以下值：
dialed-in: The endpoint dialed into the conference (e.g., in a SIP sent INVITE to the focus), which resulted in successful dialog establishment.
拨入：端点拨入会议（例如，在SIP中向焦点发送邀请），从而成功建立对话。
dialed-out: The focus has brought the endpoint into the conference (e.g., in SIP, the focus sent a successful INVITE to the endpoint).
拨出：焦点已将端点带入会议（例如，在SIP中，焦点向端点发送了成功的邀请）。
focus-owner: The endpoint is the focus for this conference. This status is used only when a participant's UA acts as a conference focus.
焦点所有者：端点是本次会议的焦点。此状态仅在参与者的UA作为会议焦点时使用。
This element contains information about how the endpoint joined and MAY contain the following sub-elements:
此元素包含有关端点如何连接的信息，并且可能包含以下子元素：
when: This element of the XML dateTime type contains the date and time that the endpoint joined the conference and SHOULD be expressed in Coordinated Universal Time (UTC).
when：XML dateTime类型的此元素包含端点加入会议的日期和时间，并应以协调世界时（UTC）表示。
reason: This element contains the reason the endpoint joined the conference. Including the information in the format defined by RFC 3326 [12] is RECOMMENDED. For example,
原因：此元素包含终结点加入会议的原因。建议以RFC 3326[12]定义的格式包含信息。例如
<reason>Reason: SIP;text="Ad-hoc Invitation"</reason>
<reason>Reason: SIP;text="Ad-hoc Invitation"</reason>
by: This element contains the URI of the entity that caused the endpoint to join the conference.
by：此元素包含导致端点加入会议的实体的URI。
This element contains the method by which the endpoint departed the conference and can assume the following values:
此元素包含端点离开会议的方法，可以采用以下值：
departed: In SIP, the endpoint sent a BYE, thus leaving the conference.
离开：在SIP中，端点发送了一个BYE，从而离开了会议。
booted: In SIP, the endpoint was sent a BYE by the focus, ejecting him/her out of the conference. Alternatively, the endpoint tried to dial into the conference but was rejected by the focus due to local policy.
booted：在SIP中，焦点向端点发送“再见”，将其逐出会议。或者，端点尝试拨入会议，但由于本地策略，被focus拒绝。
failed: In SIP, the server tried to bring the endpoint into the conference, but its attempt to contact the specific endpoint resulted in a non-200 class final response. Alternatively, the endpoint tried to dial into the conference without success due to technical reasons.
失败：在SIP中，服务器尝试将端点引入会议，但其尝试联系特定端点导致非200类最终响应。或者，由于技术原因，端点尝试拨入会议，但未成功。
busy: In SIP, the server tried to bring the endpoint into the conference, but its attempt to contact the specific endpoint resulted in a 486 "Busy Here" final response. Alternatively, the endpoint tried to dial into the conference but the focus responded with 486 response.
忙：在SIP中，服务器试图将端点引入会议，但其联系特定端点的尝试导致486“busy Here”最终响应。或者，端点尝试拨入会议，但焦点以486响应响应。
This element contains information about the endpoint's departure from the conference and MAY contain the following sub-elements:
此元素包含有关端点离开会议的信息，并可能包含以下子元素：
when: This element of the XML dateTime type contains the date and time that the endpoint departed the conference and SHOULD be expressed in Coordinated Universal Time (UTC).
when：XML dateTime类型的此元素包含端点离开会议的日期和时间，应以协调世界时（UTC）表示。
reason: This element contains the reason the endpoint departed the conference. When known and meaningful, including the information as conveyed/reported by the call signaling in the format defined by RFC 3326 [12] is RECOMMENDED. For example,
原因：此元素包含终结点离开会议的原因。当已知且有意义时，建议以RFC 3326[12]定义的格式包括呼叫信令所传达/报告的信息。例如
<reason>Reason: SIP;cause=415;text="Unsupported Media Type"</reason>
<reason>Reason: SIP;cause=415;text="Unsupported Media Type"</reason>
by: This element contains the URI of the entity that caused the endpoint to depart the conference.
by：此元素包含导致端点离开会议的实体的URI。
This element contains information about a single media stream and is included for each media stream being established between the focus and the <endpoint>. The media stream definition can be found in SDP [3].
此元素包含有关单个媒体流的信息，并包含在焦点和<endpoint>之间建立的每个媒体流中。媒体流定义可在SDP[3]中找到。
Note that if the <call-info> sub-element of the endpoint is not included in the document by the server, it is possible that the media streams listed under the common <endpoint> were established by separate signaling sessions.
注意，如果服务器未将端点的<call info>子元素包括在文档中，则公共<endpoint>下列出的媒体流可能是通过单独的信令会话建立的。
The <call-info> element provides detailed call signaling information for a call being maintained between the participant and the focus. Privacy policies MUST be consulted before revealing this information to other participants.
<call info>元素为参与者和焦点之间正在维护的呼叫提供详细的呼叫信令信息。在向其他参与者披露此信息之前，必须咨询隐私政策。
The <sip> sub-element contains the SIP dialog identifier of the endpoint's dialog with the focus. The element includes sub-elements <display-text>, <call-id>, <to-tag>, <from-tag>.
<sip>子元素包含端点对话的sip对话标识符和焦点。元素包括子元素<display text>，<call id>，<to tag>，<from tag>。
In future, the <call-info> element can be expanded to include call signaling protocol information for other protocols besides SIP.
将来，<call info>元素可以扩展为包括SIP之外的其他协议的呼叫信令协议信息。
This section describes the <media> element in more detail.
本节更详细地描述<media>元素。
A single 'id' attribute is defined for this element. This is the media stream identifier being generated by the server such that its
为此元素定义了一个“id”属性。这是服务器生成的媒体流标识符，以便
value is unique in the endpoint context. This attribute is the key to refer to a particular media stream in the conference document.
值在端点上下文中是唯一的。此属性是引用会议文档中特定媒体流的关键。
The following child elements are defined for <media>:
为<media>定义了以下子元素：
This element contains the display text for the media stream. The value of this element corresponds to the SDP description media attribute ("i") defined in SDP [3].
此元素包含媒体流的显示文本。此元素的值对应于SDP[3]中定义的SDP描述媒体属性（“i”）。
This element contains the media type for the media stream. The value of this element MUST be one of the values registered for "media" of SDP [3] and its later revision(s).
此元素包含媒体流的媒体类型。此元素的值必须是为SDP[3]及其更高版本的“介质”注册的值之一。
The <label> element carries a unique identifier for this stream among all streams in the conference and is assigned by the focus. The value of this element will typically correspond to the SDP "label" media attribute defined in [17] and is exchanged between a participant and a focus over the signaling connection between them.
<label>元素在会议中的所有流中携带该流的唯一标识符，并由焦点分配。该元素的值通常对应于[17]中定义的SDP“标签”媒体属性，并在参与者和焦点之间通过它们之间的信令连接进行交换。
If the <available-media> information (described in Section 5.3.4) is included in the conference document, the value of this element MUST be equal to the 'label' value of the corresponding media stream <entry> in the <available-media> container.
如果会议文件中包含<available media>信息（如第5.3.4节所述），则该元素的值必须等于<available media>容器中相应媒体流<entry>的“标签”值。
The <src-id> element, if applicable, carries the information about the actual source of the media. For example, for Real-time Transport Protocol (RTP) / RTP Control Protocol (RTCP) [13] media streams, the value MUST contain the synchronization source (SSRC) identifier value generated by the endpoint for the stream it sends.
<src id>元素（如果适用）包含有关介质实际来源的信息。例如，对于实时传输协议（RTP）/RTP控制协议（RTCP）[13]媒体流，该值必须包含端点为其发送的流生成的同步源（SSRC）标识符值。
When an RTP mixer generates a contributing source (CSRC) identifiers' list according to RTP/RTCP [13], it inserts a list of the SSRC identifiers of the sources that contributed to the generation of a particular packet into the RTP header of that packet. A quote from RFC 3550 [13] explains as follows: "An example application is audio conferencing where a mixer indicates all the talkers whose speech was combined to produce the outgoing packet, allowing the receiver to indicate the current talker, even though all the audio packets contain the same SSRC identifier (that of the mixer)."
当RTP混合器根据RTP/RTCP[13]生成贡献源（CSC）标识符列表时，它会将有助于生成特定数据包的源的SSRC标识符列表插入该数据包的RTP报头中。RFC 3550[13]的一段引文解释如下：“音频会议是一个示例应用，其中混音器指示其语音被组合以产生传出分组的所有说话者，允许接收机指示当前说话者，即使所有音频分组包含相同的SSRC标识符（混音器的标识符）。”
If an RTP mixer compliant to the above is used, participants can perform an SSRC to user mapping and identify "a current speaker".
如果使用符合上述要求的RTP混音器，参与者可以执行SSRC到用户映射，并识别“当前演讲者”。
The element <status> indicates the status in both directions of the media stream and has the values "sendrecv", "sendonly", "recvonly", or "inactive" as defined in SDP [3] and its later revision(s). Note that value specifies the direction from the participant's point of view. For example, a muted participant's stream will have the value of "recvonly".
元素<status>指示媒体流两个方向的状态，并具有SDP[3]及其更高版本中定义的值“sendrecv”、“sendonly”、“RecVoOnly”或“inactive”。请注意，该值从参与者的角度指定方向。例如，静音参与者的流的值为“recvonly”。
If a participant in the main conference joins a sidebar, a new <user> element representing the user is created either as a part of a separate sub-conference referenced from the <sidebars-by-ref> element or under one of the <sidebars-by-val> elements as described below.
如果主会议的参与者加入侧栏，则代表该用户的新<user>元素将被创建为从<sidebars by ref>元素引用的单独子会议的一部分，或在<sidebars by val>元素之一下创建，如下所述。
Note that the <user> in the main roster is not being deleted, but its media statuses can be updated to reflect the effect being caused by his/her participation in the sidebar. The display of this information can vary among subscribers to the same conference information, subject to local policies and to the subscriber role both in the sidebar and in the main conference.
请注意，主花名册中的<user>不会被删除，但其媒体状态可以更新，以反映他/她参与侧边栏所造成的影响。根据本地策略以及侧栏和主会议中的订阅者角色，此信息的显示在相同会议信息的订阅者之间可能有所不同。
This element contains a set of <entry> child elements, each containing a sidebar conference URI. The recipient of the information can then subscribe to sidebar information independently from the main conference package subscription.
此元素包含一组<entry>子元素，每个子元素都包含一个侧栏会议URI。然后，信息的接收者可以独立于主会议包订阅订阅订阅侧栏信息。
This element contains a set of <entry> child elements, each containing information about a single sidebar. By using this element of conference-type, the server can include a full or partial description of each sidebar (as a sub-conference) in the body of the main conference document.
该元素包含一组<entry>子元素，每个子元素都包含关于单个边栏的信息。通过使用会议类型的此元素，服务器可以在主会议文档的正文中包含每个侧栏（作为子会议）的完整或部分描述。
<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:conference-info"
xmlns:tns="urn:ietf:params:xml:ns:conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:conference-info"
xmlns:tns="urn:ietf:params:xml:ns:conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:conference-info"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<!--
This imports the xml:language definition
-->
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
<!--
CONFERENCE ELEMENT
-->
<xs:element name="conference-info" type="conference-type"/>
<!--
CONFERENCE TYPE
-->
<xs:complexType name="conference-type">
<xs:sequence>
<xs:element name="conference-description"
type="conference-description-type" minOccurs="0"/>
<xs:element name="host-info"
type="host-type" minOccurs="0"/>
<xs:element name="conference-state"
type="conference-state-type" minOccurs="0"/>
<xs:element name="users"
type="users-type" minOccurs="0"/>
<xs:element name="sidebars-by-ref"
type="uris-type" minOccurs="0"/>
<xs:element name="sidebars-by-val"
type="sidebars-by-val-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity"
type="xs:anyURI" use="required"/>
<xs:attribute name="state"
type="state-type" use="optional" default="full"/>
<xs:attribute name="version"
type="xs:unsignedInt" use="optional"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
STATE TYPE
-->
<xs:simpleType name="state-type">
<xs:restriction base="xs:string">
<xs:enumeration value="full"/>
<xs:enumeration value="partial"/>
<xs:enumeration value="deleted"/>
xmlns="urn:ietf:params:xml:ns:conference-info"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<!--
This imports the xml:language definition
-->
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
<!--
CONFERENCE ELEMENT
-->
<xs:element name="conference-info" type="conference-type"/>
<!--
CONFERENCE TYPE
-->
<xs:complexType name="conference-type">
<xs:sequence>
<xs:element name="conference-description"
type="conference-description-type" minOccurs="0"/>
<xs:element name="host-info"
type="host-type" minOccurs="0"/>
<xs:element name="conference-state"
type="conference-state-type" minOccurs="0"/>
<xs:element name="users"
type="users-type" minOccurs="0"/>
<xs:element name="sidebars-by-ref"
type="uris-type" minOccurs="0"/>
<xs:element name="sidebars-by-val"
type="sidebars-by-val-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity"
type="xs:anyURI" use="required"/>
<xs:attribute name="state"
type="state-type" use="optional" default="full"/>
<xs:attribute name="version"
type="xs:unsignedInt" use="optional"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
STATE TYPE
-->
<xs:simpleType name="state-type">
<xs:restriction base="xs:string">
<xs:enumeration value="full"/>
<xs:enumeration value="partial"/>
<xs:enumeration value="deleted"/>
</xs:restriction>
</xs:simpleType>
<!--
CONFERENCE DESCRIPTION TYPE
-->
<xs:complexType name="conference-description-type">
<xs:sequence>
<xs:element name="display-text"
type="xs:string" minOccurs="0"/>
<xs:element name="subject"
type="xs:string" minOccurs="0"/>
<xs:element name="free-text"
type="xs:string" minOccurs="0"/>
<xs:element name="keywords"
type="keywords-type" minOccurs="0"/>
<xs:element name="conf-uris"
type="uris-type" minOccurs="0"/>
<xs:element name="service-uris"
type="uris-type" minOccurs="0"/>
<xs:element name="maximum-user-count"
type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="available-media"
type="conference-media-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
HOST TYPE
-->
<xs:complexType name="host-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="web-page" type="xs:anyURI"
minOccurs="0"/>
<xs:element name="uris" type="uris-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE STATE TYPE
-->
<xs:complexType name="conference-state-type">
</xs:restriction>
</xs:simpleType>
<!--
CONFERENCE DESCRIPTION TYPE
-->
<xs:complexType name="conference-description-type">
<xs:sequence>
<xs:element name="display-text"
type="xs:string" minOccurs="0"/>
<xs:element name="subject"
type="xs:string" minOccurs="0"/>
<xs:element name="free-text"
type="xs:string" minOccurs="0"/>
<xs:element name="keywords"
type="keywords-type" minOccurs="0"/>
<xs:element name="conf-uris"
type="uris-type" minOccurs="0"/>
<xs:element name="service-uris"
type="uris-type" minOccurs="0"/>
<xs:element name="maximum-user-count"
type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="available-media"
type="conference-media-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
HOST TYPE
-->
<xs:complexType name="host-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="web-page" type="xs:anyURI"
minOccurs="0"/>
<xs:element name="uris" type="uris-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE STATE TYPE
-->
<xs:complexType name="conference-state-type">
<xs:sequence>
<xs:element name="user-count" type="xs:unsignedInt"
minOccurs="0"/>
<xs:element name="active" type="xs:boolean"
minOccurs="0"/>
<xs:element name="locked" type="xs:boolean"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE MEDIA TYPE
-->
<xs:complexType name="conference-media-type">
<xs:sequence>
<xs:element name="entry" type="conference-medium-type"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE MEDIUM TYPE
-->
<xs:complexType name="conference-medium-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="type" type="xs:string"/>
<xs:element name="status" type="media-status-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="label" type="xs:string"
use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
URIs TYPE
-->
<xs:complexType name="uris-type">
<xs:sequence>
<xs:element name="entry" type="uri-type"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
<xs:sequence>
<xs:element name="user-count" type="xs:unsignedInt"
minOccurs="0"/>
<xs:element name="active" type="xs:boolean"
minOccurs="0"/>
<xs:element name="locked" type="xs:boolean"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE MEDIA TYPE
-->
<xs:complexType name="conference-media-type">
<xs:sequence>
<xs:element name="entry" type="conference-medium-type"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CONFERENCE MEDIUM TYPE
-->
<xs:complexType name="conference-medium-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="type" type="xs:string"/>
<xs:element name="status" type="media-status-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="label" type="xs:string"
use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
URIs TYPE
-->
<xs:complexType name="uris-type">
<xs:sequence>
<xs:element name="entry" type="uri-type"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
URI TYPE
-->
<xs:complexType name="uri-type">
<xs:sequence>
<xs:element name="uri" type="xs:anyURI"/>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="purpose" type="xs:string"
minOccurs="0"/>
<xs:element name="modified" type="execution-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
KEYWORDS TYPE
-->
<xs:simpleType name="keywords-type">
<xs:list itemType="xs:string"/>
</xs:simpleType>
<!--
USERS TYPE
-->
<xs:complexType name="users-type">
<xs:sequence>
<xs:element name="user" type="user-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER TYPE
-->
<xs:complexType name="user-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="associated-aors" type="uris-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
URI TYPE
-->
<xs:complexType name="uri-type">
<xs:sequence>
<xs:element name="uri" type="xs:anyURI"/>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="purpose" type="xs:string"
minOccurs="0"/>
<xs:element name="modified" type="execution-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
KEYWORDS TYPE
-->
<xs:simpleType name="keywords-type">
<xs:list itemType="xs:string"/>
</xs:simpleType>
<!--
USERS TYPE
-->
<xs:complexType name="users-type">
<xs:sequence>
<xs:element name="user" type="user-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER TYPE
-->
<xs:complexType name="user-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="associated-aors" type="uris-type"
minOccurs="0"/>
<xs:element name="roles" type="user-roles-type"
minOccurs="0"/>
<xs:element name="languages" type="user-languages-type"
minOccurs="0"/>
<xs:element name="cascaded-focus" type="xs:anyURI"
minOccurs="0"/>
<xs:element name="endpoint" type="endpoint-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity" type="xs:anyURI"/>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER ROLES TYPE
-->
<xs:complexType name="user-roles-type">
<xs:sequence>
<xs:element name="entry" type="xs:string"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER LANGUAGES TYPE
-->
<xs:simpleType name="user-languages-type">
<xs:list itemType="xs:language"/>
</xs:simpleType>
<!--
ENDPOINT TYPE
-->
<xs:complexType name="endpoint-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="referred" type="execution-type"
minOccurs="0"/>
<xs:element name="status" type="endpoint-status-type"
minOccurs="0"/>
<xs:element name="joining-method" type="joining-type"
minOccurs="0"/>
<xs:element name="joining-info"
type="execution-type"
minOccurs="0"/>
<xs:element name="roles" type="user-roles-type"
minOccurs="0"/>
<xs:element name="languages" type="user-languages-type"
minOccurs="0"/>
<xs:element name="cascaded-focus" type="xs:anyURI"
minOccurs="0"/>
<xs:element name="endpoint" type="endpoint-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity" type="xs:anyURI"/>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER ROLES TYPE
-->
<xs:complexType name="user-roles-type">
<xs:sequence>
<xs:element name="entry" type="xs:string"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
USER LANGUAGES TYPE
-->
<xs:simpleType name="user-languages-type">
<xs:list itemType="xs:language"/>
</xs:simpleType>
<!--
ENDPOINT TYPE
-->
<xs:complexType name="endpoint-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="referred" type="execution-type"
minOccurs="0"/>
<xs:element name="status" type="endpoint-status-type"
minOccurs="0"/>
<xs:element name="joining-method" type="joining-type"
minOccurs="0"/>
<xs:element name="joining-info"
type="execution-type"
minOccurs="0"/>
<xs:element name="disconnection-method"
type="disconnection-type"
minOccurs="0"/>
<xs:element name="disconnection-info"
type="execution-type"
minOccurs="0"/>
<xs:element name="media" type="media-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="call-info" type="call-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity" type="xs:string"/>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
ENDPOINT STATUS TYPE
-->
<xs:simpleType name="endpoint-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="pending"/>
<xs:enumeration value="dialing-out"/>
<xs:enumeration value="dialing-in"/>
<xs:enumeration value="alerting"/>
<xs:enumeration value="on-hold"/>
<xs:enumeration value="connected"/>
<xs:enumeration value="muted-via-focus"/>
<xs:enumeration value="disconnecting"/>
<xs:enumeration value="disconnected"/>
</xs:restriction>
</xs:simpleType>
<!--
JOINING TYPE
-->
<xs:simpleType name="joining-type">
<xs:restriction base="xs:string">
<xs:enumeration value="dialed-in"/>
<xs:enumeration value="dialed-out"/>
<xs:enumeration value="focus-owner"/>
</xs:restriction>
</xs:simpleType>
<!--
DISCONNECTION TYPE
-->
minOccurs="0"/>
<xs:element name="disconnection-method"
type="disconnection-type"
minOccurs="0"/>
<xs:element name="disconnection-info"
type="execution-type"
minOccurs="0"/>
<xs:element name="media" type="media-type"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="call-info" type="call-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="entity" type="xs:string"/>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
ENDPOINT STATUS TYPE
-->
<xs:simpleType name="endpoint-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="pending"/>
<xs:enumeration value="dialing-out"/>
<xs:enumeration value="dialing-in"/>
<xs:enumeration value="alerting"/>
<xs:enumeration value="on-hold"/>
<xs:enumeration value="connected"/>
<xs:enumeration value="muted-via-focus"/>
<xs:enumeration value="disconnecting"/>
<xs:enumeration value="disconnected"/>
</xs:restriction>
</xs:simpleType>
<!--
JOINING TYPE
-->
<xs:simpleType name="joining-type">
<xs:restriction base="xs:string">
<xs:enumeration value="dialed-in"/>
<xs:enumeration value="dialed-out"/>
<xs:enumeration value="focus-owner"/>
</xs:restriction>
</xs:simpleType>
<!--
DISCONNECTION TYPE
-->
<xs:simpleType name="disconnection-type">
<xs:restriction base="xs:string">
<xs:enumeration value="departed"/>
<xs:enumeration value="booted"/>
<xs:enumeration value="failed"/>
<xs:enumeration value="busy"/>
</xs:restriction>
</xs:simpleType>
<!--
EXECUTION TYPE
-->
<xs:complexType name="execution-type">
<xs:sequence>
<xs:element name="when" type="xs:dateTime"
minOccurs="0"/>
<xs:element name="reason" type="xs:string"
minOccurs="0"/>
<xs:element name="by" type="xs:anyURI"
minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CALL TYPE
-->
<xs:complexType name="call-type">
<xs:choice>
<xs:element name="sip" type="sip-dialog-id-type"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
SIP DIALOG ID TYPE
-->
<xs:complexType name="sip-dialog-id-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="call-id" type="xs:string"/>
<xs:element name="from-tag" type="xs:string"/>
<xs:element name="to-tag" type="xs:string"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<xs:simpleType name="disconnection-type">
<xs:restriction base="xs:string">
<xs:enumeration value="departed"/>
<xs:enumeration value="booted"/>
<xs:enumeration value="failed"/>
<xs:enumeration value="busy"/>
</xs:restriction>
</xs:simpleType>
<!--
EXECUTION TYPE
-->
<xs:complexType name="execution-type">
<xs:sequence>
<xs:element name="when" type="xs:dateTime"
minOccurs="0"/>
<xs:element name="reason" type="xs:string"
minOccurs="0"/>
<xs:element name="by" type="xs:anyURI"
minOccurs="0"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
CALL TYPE
-->
<xs:complexType name="call-type">
<xs:choice>
<xs:element name="sip" type="sip-dialog-id-type"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
SIP DIALOG ID TYPE
-->
<xs:complexType name="sip-dialog-id-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="call-id" type="xs:string"/>
<xs:element name="from-tag" type="xs:string"/>
<xs:element name="to-tag" type="xs:string"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
MEDIA TYPE
-->
<xs:complexType name="media-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="type" type="xs:string"
minOccurs="0"/>
<xs:element name="label" type="xs:string"
minOccurs="0"/>
<xs:element name="src-id" type="xs:string"
minOccurs="0"/>
<xs:element name="status" type="media-status-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="id" type="xs:string"
use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
MEDIA STATUS TYPE
-->
<xs:simpleType name="media-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="recvonly"/>
<xs:enumeration value="sendonly"/>
<xs:enumeration value="sendrecv"/>
<xs:enumeration value="inactive"/>
</xs:restriction>
</xs:simpleType>
<!--
SIDEBARS BY VAL TYPE
-->
<xs:complexType name="sidebars-by-val-type">
<xs:sequence>
<xs:element name="entry" type="conference-type"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:schema>
<!--
MEDIA TYPE
-->
<xs:complexType name="media-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string"
minOccurs="0"/>
<xs:element name="type" type="xs:string"
minOccurs="0"/>
<xs:element name="label" type="xs:string"
minOccurs="0"/>
<xs:element name="src-id" type="xs:string"
minOccurs="0"/>
<xs:element name="status" type="media-status-type"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="id" type="xs:string"
use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!--
MEDIA STATUS TYPE
-->
<xs:simpleType name="media-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="recvonly"/>
<xs:enumeration value="sendonly"/>
<xs:enumeration value="sendrecv"/>
<xs:enumeration value="inactive"/>
</xs:restriction>
</xs:simpleType>
<!--
SIDEBARS BY VAL TYPE
-->
<xs:complexType name="sidebars-by-val-type">
<xs:sequence>
<xs:element name="entry" type="conference-type"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type"
use="optional" default="full"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:schema>
The following is an example of a full conference information document:
以下是完整会议信息文件的示例：
<?xml version="1.0" encoding="UTF-8"?>
<conference-info
xmlns="urn:ietf:params:xml:ns:conference-info"
entity="sips:conf233@example.com"
state="full" version="1">
<!--
CONFERENCE INFO
-->
<conference-description>
<subject>Agenda: This month's goals</subject>
<service-uris>
<entry>
<uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose>
</entry>
</service-uris>
</conference-description>
<!--
CONFERENCE STATE
-->
<conference-state>
<user-count>33</user-count>
</conference-state>
<!--
USERS
-->
<users>
<user entity="sip:bob@example.com" state="full">
<display-text>Bob Hoskins</display-text>
<!--
ENDPOINTS
-->
<endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text>
<status>disconnected</status>
<disconnection-method>departed</disconnection-method>
<disconnection-info>
<when>2005-03-04T20:00:00Z</when>
<reason>bad voice quality</reason>
<by>sip:mike@example.com</by>
</disconnection-info>
<?xml version="1.0" encoding="UTF-8"?>
<conference-info
xmlns="urn:ietf:params:xml:ns:conference-info"
entity="sips:conf233@example.com"
state="full" version="1">
<!--
CONFERENCE INFO
-->
<conference-description>
<subject>Agenda: This month's goals</subject>
<service-uris>
<entry>
<uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose>
</entry>
</service-uris>
</conference-description>
<!--
CONFERENCE STATE
-->
<conference-state>
<user-count>33</user-count>
</conference-state>
<!--
USERS
-->
<users>
<user entity="sip:bob@example.com" state="full">
<display-text>Bob Hoskins</display-text>
<!--
ENDPOINTS
-->
<endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text>
<status>disconnected</status>
<disconnection-method>departed</disconnection-method>
<disconnection-info>
<when>2005-03-04T20:00:00Z</when>
<reason>bad voice quality</reason>
<by>sip:mike@example.com</by>
</disconnection-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status>
</media>
</endpoint>
</user>
<!--
USER
-->
<user entity="sip:alice@example.com" state="full">
<display-text>Alice</display-text>
<!--
ENDPOINTS
-->
<endpoint entity="sip:4kfk4j392jsu@example.com;grid=433kj4j3u">
<status>connected</status>
<joining-method>dialed-out</joining-method>
<joining-info>
<when>2005-03-04T20:00:00Z</when>
<by>sip:mike@example.com</by>
</joining-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>534232</src-id>
<status>sendrecv</status>
</media>
</endpoint>
</user>
</users>
</conference-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status>
</media>
</endpoint>
</user>
<!--
USER
-->
<user entity="sip:alice@example.com" state="full">
<display-text>Alice</display-text>
<!--
ENDPOINTS
-->
<endpoint entity="sip:4kfk4j392jsu@example.com;grid=433kj4j3u">
<status>connected</status>
<joining-method>dialed-out</joining-method>
<joining-info>
<when>2005-03-04T20:00:00Z</when>
<by>sip:mike@example.com</by>
</joining-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>534232</src-id>
<status>sendrecv</status>
</media>
</endpoint>
</user>
</users>
</conference-info>
The following is an example of a partial conference information document. In this example, there are 32 participants in a voice conference. The user Bob has been ejected from the conference by Mike due to bad voice quality. Note that there are three sidebars in
以下是部分会议信息文档的示例。在本例中，语音会议有32名参与者。由于语音质量差，用户Bob已被Mike逐出会议。请注意，中有三个侧栏
the conference; two are referenced just by their sidebar URIs, and information about the third sidebar is included in this notification. Also note that while this conference offers both audio and video capabilities, only audio is currently in use.
会议；其中两个仅由侧栏URI引用，有关第三个侧栏的信息包含在本通知中。还请注意，虽然本次会议同时提供音频和视频功能，但目前仅使用音频。
<?xml version="1.0" encoding="UTF-8"?>
<conference-info
xmlns="urn:ietf:params:xml:ns:conference-info"
entity="sips:conf233@example.com"
state="partial" version="5">
<!--
CONFERENCE INFO
-->
<conference-description>
<display-text>Weekly Sales Meeting</display-text>
<subject>Agenda: This month's goals</subject>
<free-text>We will start strict on time</free-text>
<keywords>sales meeting weekly</keywords>
<conf-uris>
<entry>
<uri>tel:+18005671234</uri>
<display-text>TTI Bridge</display-text>
<purpose>participation</purpose>
</entry>
<entry>
<uri>h323:conf545@h323.example.com</uri>
<purpose>participation</purpose>
</entry>
<entry>
<uri>http://real.streaming.com/54634/live.ram</uri>
<purpose>streaming</purpose>
</entry>
</conf-uris>
<service-uris>
<entry>
<uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose>
</entry>
<entry>
<uri>http://quicktime.com/54634/recording.mov</uri>
<display-text>Quicktime</display-text>
<purpose>recording</purpose>
</entry>
</service-uris>
<maximum-user-count>100</maximum-user-count>
<available-media>
<entry label="34567">
<display-text>main audio</display-text>
<?xml version="1.0" encoding="UTF-8"?>
<conference-info
xmlns="urn:ietf:params:xml:ns:conference-info"
entity="sips:conf233@example.com"
state="partial" version="5">
<!--
CONFERENCE INFO
-->
<conference-description>
<display-text>Weekly Sales Meeting</display-text>
<subject>Agenda: This month's goals</subject>
<free-text>We will start strict on time</free-text>
<keywords>sales meeting weekly</keywords>
<conf-uris>
<entry>
<uri>tel:+18005671234</uri>
<display-text>TTI Bridge</display-text>
<purpose>participation</purpose>
</entry>
<entry>
<uri>h323:conf545@h323.example.com</uri>
<purpose>participation</purpose>
</entry>
<entry>
<uri>http://real.streaming.com/54634/live.ram</uri>
<purpose>streaming</purpose>
</entry>
</conf-uris>
<service-uris>
<entry>
<uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose>
</entry>
<entry>
<uri>http://quicktime.com/54634/recording.mov</uri>
<display-text>Quicktime</display-text>
<purpose>recording</purpose>
</entry>
</service-uris>
<maximum-user-count>100</maximum-user-count>
<available-media>
<entry label="34567">
<display-text>main audio</display-text>
<type>audio</type>
<status>sendrecv</status>
</entry>
<entry label="34569">
<display-text>main video</display-text>
<type>video</type>
<status>inactive</status>
</entry>
</available-media>
</conference-description>
<!--
HOST INFO
-->
<host-info>
<display-text>Sales Host</display-text>
<web-page>http://sharepoint/salesgroup/hosts/</web-page>
<uris>
<entry>
<uri>sip:sales@example.com</uri>
</entry>
</uris>
</host-info>
<!--
CONFERENCE STATE
-->
<conference-state>
<user-count>32</user-count>
<active>true</active>
<locked>false</locked>
</conference-state>
<!--
USERS
-->
<users>
<user entity="sip:bob@example.com">
<display-text>Bob Hoskins</display-text>
<associated-aors>
<entry>
<uri>mailto:bob@example.com</uri>
<display-text>email</display-text>
</entry>
</associated-aors>
<roles>
<entry>participant</entry>
</roles>
<languages>en</languages>
<!--
ENDPOINTS
<type>audio</type>
<status>sendrecv</status>
</entry>
<entry label="34569">
<display-text>main video</display-text>
<type>video</type>
<status>inactive</status>
</entry>
</available-media>
</conference-description>
<!--
HOST INFO
-->
<host-info>
<display-text>Sales Host</display-text>
<web-page>http://sharepoint/salesgroup/hosts/</web-page>
<uris>
<entry>
<uri>sip:sales@example.com</uri>
</entry>
</uris>
</host-info>
<!--
CONFERENCE STATE
-->
<conference-state>
<user-count>32</user-count>
<active>true</active>
<locked>false</locked>
</conference-state>
<!--
USERS
-->
<users>
<user entity="sip:bob@example.com">
<display-text>Bob Hoskins</display-text>
<associated-aors>
<entry>
<uri>mailto:bob@example.com</uri>
<display-text>email</display-text>
</entry>
</associated-aors>
<roles>
<entry>participant</entry>
</roles>
<languages>en</languages>
<!--
ENDPOINTS
-->
<endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text>
<referred>
<when>2005-03-04T20:00:00Z</when>
<reason>expert required</reason>
<by>sip:mike@example.com</by>
</referred>
<status>disconnecting</status>
<joining-method>dialed-out</joining-method>
<joining-info>
<when>2005-03-04T20:00:00Z</when>
<reason>invitation</reason>
<by>sip:mike@example.com</by>
</joining-info>
<disconnection-method>booted</disconnection-method>
<disconnection-info>
-->
<endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text>
<referred>
<when>2005-03-04T20:00:00Z</when>
<reason>expert required</reason>
<by>sip:mike@example.com</by>
</referred>
<status>disconnecting</status>
<joining-method>dialed-out</joining-method>
<joining-info>
<when>2005-03-04T20:00:00Z</when>
<reason>invitation</reason>
<by>sip:mike@example.com</by>
</joining-info>
<disconnection-method>booted</disconnection-method>
<disconnection-info>
<when>2005-03-04T20:00:00Z</when>
<reason>bad voice quality</reason>
<by>sip:mike@example.com</by>
</disconnection-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status>
</media>
<!--
CALL INFO
-->
<call-info>
<sip>
<display-text>full info</display-text>
<call-id>hsjh8980vhsb78</call-id>
<from-tag>vav738dvbs</from-tag>
<to-tag>8954jgjg8432</to-tag>
</sip>
</call-info>
</endpoint>
</user>
</users>
<!--
SIDEBARS BY REFERENCE
<when>2005-03-04T20:00:00Z</when>
<reason>bad voice quality</reason>
<by>sip:mike@example.com</by>
</disconnection-info>
<!--
MEDIA
-->
<media id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status>
</media>
<!--
CALL INFO
-->
<call-info>
<sip>
<display-text>full info</display-text>
<call-id>hsjh8980vhsb78</call-id>
<from-tag>vav738dvbs</from-tag>
<to-tag>8954jgjg8432</to-tag>
</sip>
</call-info>
</endpoint>
</user>
</users>
<!--
SIDEBARS BY REFERENCE
-->
<sidebars-by-ref state="partial">
<entry>
<uri>sips:conf233@example.com;grid=45</uri>
<display-text>sidebar with Carol</display-text>
</entry>
<entry>
<uri>sips:conf233@example.com;grid=21</uri>
<display-text>private with Peter</display-text>
</entry>
</sidebars-by-ref>
<!--
SIDEBARS BY VALUE
-->
<sidebars-by-val state="partial">
<entry entity="sips:conf233@example.com;grid=77"
-->
<sidebars-by-ref state="partial">
<entry>
<uri>sips:conf233@example.com;grid=45</uri>
<display-text>sidebar with Carol</display-text>
</entry>
<entry>
<uri>sips:conf233@example.com;grid=21</uri>
<display-text>private with Peter</display-text>
</entry>
</sidebars-by-ref>
<!--
SIDEBARS BY VALUE
-->
<sidebars-by-val state="partial">
<entry entity="sips:conf233@example.com;grid=77"
state="partial">
<users>
<user entity="sip:bob@example.com"/>
<user entity="sip:mark@example.com"/>
<user entity="sip:dan@example.com"/>
</users>
</entry>
</sidebars-by-val>
</conference-info>
state="partial">
<users>
<user entity="sip:bob@example.com"/>
<user entity="sip:mark@example.com"/>
<user entity="sip:dan@example.com"/>
</users>
</entry>
</sidebars-by-val>
</conference-info>
Subscriptions to conference state information can reveal very sensitive information. For this reason, it is RECOMMENDED that a focus use a strong means for authentication and conference information protection and that it apply comprehensive authorization rules when using the conference notification mechanism defined in this document. The following sections will discuss each of these aspects in more detail.
订阅会议状态信息可能会泄露非常敏感的信息。因此，建议focus使用强大的身份验证和会议信息保护手段，并在使用本文件中定义的会议通知机制时应用全面的授权规则。以下各节将更详细地讨论这些方面。
It is RECOMMENDED that a focus authenticate a conference package subscriber using the normal SIP authentication mechanisms, such as Digest as defined in Section 22 of RFC 3261 [8].
建议focus使用常规SIP认证机制（如RFC 3261[8]第22节中定义的摘要）对会议包订户进行认证。
The mechanism used for conveying the conference information MUST ensure integrity and SHOULD ensure confidentially of the information. In order to achieve these, an end-to-end SIP encryption mechanism,
用于传达会议信息的机制必须确保完整性，并应确保信息的机密性。为了实现这些，一种端到端SIP加密机制，
such as S/MIME described in Section 26.2.4 of RFC 3261 [8], SHOULD be used.
应使用RFC 3261[8]第26.2.4节中描述的S/MIME。
If a strong end-to-end security means (such as above) is not available, it is RECOMMENDED that a focus use mutual hop-by-hop Transport Layer Security (TLS) authentication and encryption mechanisms described in Section 26.2.2 "SIPS URI Scheme" and Section 26.3.2.2 "Interdomain Requests" of RFC 3261 [8].
如果没有强大的端到端安全手段（如上文所述），建议focus使用RFC 3261[8]第26.2.2节“SIPS URI方案”和第26.3.2.2节“域间请求”中描述的相互逐跳传输层安全（TLS）认证和加密机制。
Generally speaking, conference applications are very concerned about authorization decisions. Mechanisms for establishing and enforcing such authorization rules are a central concept throughout the SIP Conferencing Framework [16]. Because most of the information about a conference can be presented using the conference package, many of the authorization rules directly apply to this specification. As a result, a notification server MUST be capable of generating distinct conference information views to different subscribers, subject to a subscriber's role in a conference, personal access rights, etc. - all subject to local authorization policies and rules.
一般来说，会议应用程序非常关注授权决策。建立和实施此类授权规则的机制是整个SIP会议框架的核心概念[16]。由于有关会议的大多数信息都可以使用会议包呈现，因此许多授权规则直接应用于此规范。因此，通知服务器必须能够根据订阅者在会议中的角色、个人访问权限等，为不同订阅者生成不同的会议信息视图，所有这些都必须遵守本地授权策略和规则。
Since a focus provides participant identity information using this event package, participant privacy needs to be taken into account. A focus MUST support requests by participants for privacy. Privacy can be indicated by the conference policy - for every participant or select participants. It can also be indicated in the session signaling. In SIP, this can be done using the Privacy header field described in RFC 3323 [11]. For a participant requesting privacy, no identity information SHOULD be revealed by the focus in any included URI (e.g., the Address of Record, Contact, or GRUU). For these cases, the anonymous URI generation method outlined in Section 5.6 of this document MUST be followed.
由于focus使用此事件包提供参与者身份信息，因此需要考虑参与者隐私。焦点必须支持参与者的隐私请求。隐私可以通过会议政策来表示-对于每个参与者或选定的参与者。它也可以在会话信令中指示。在SIP中，这可以使用RFC 3323[11]中描述的隐私头字段来完成。对于请求隐私的参与者，焦点不应在任何包含的URI（例如记录地址、联系人或GRUU）中透露身份信息。对于这些情况，必须遵循本文档第5.6节中概述的匿名URI生成方法。
This document registers a SIP event package, a new MIME type, application/conference-info+xml, a new XML namespace, and a new XML schema, and creates a sub-registry "URI purposes" under the existing registry: http://www.iana.org/assignments/sip-parameters.
本文档注册一个SIP事件包、一个新的MIME类型、应用程序/会议信息+xml、一个新的xml命名空间和一个新的xml模式，并在现有注册表下创建一个子注册表“URI用途”：http://www.iana.org/assignments/sip-parameters.
This specification registers an event package, based on the registration procedures defined in RFC 3265 [10]. The following is the information required for such a registration:
本规范根据RFC 3265[10]中定义的注册过程注册事件包。以下是此类注册所需的信息：
Package Name: conference
包裹名称：会议
Package or Template-Package: This is a package.
包或模板包：这是一个包。
Published Document: RFC 4575
出版文件：RFC 4575
Person to Contact: IETF SIPPING Working Group <sipping@ietf.org>, as
designated by the IESG <iesg@ietf.org>
Person to Contact: IETF SIPPING Working Group <sipping@ietf.org>, as
designated by the IESG <iesg@ietf.org>
MIME media type name: application
MIME媒体类型名称：应用程序
MIME subtype name: conference-info+xml
MIME子类型名称：会议信息+xml
Mandatory parameters: none
强制参数：无
Optional parameters: Same as charset parameter application/xml as specified in RFC 3023 [7]
可选参数：与RFC 3023[7]中指定的字符集参数application/xml相同
Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [7]
编码注意事项：与RFC 3023[7]中指定的应用程序/xml的编码注意事项相同
Security considerations: See Section 10 of RFC 3023 [7] and Section 8 of this specification
安全注意事项：参见RFC 3023[7]第10节和本规范第8节
Interoperability considerations: none
互操作性注意事项：无
Published specification: This document
已发布规范：本文件
Applications which use this media type: This document type has been used to support SIP conferencing applications
使用此媒体类型的应用程序：此文档类型已用于支持SIP会议应用程序
Additional Information:
其他信息：
Magic Number: None
神奇数字：无
File Extension: .xml
文件扩展名：.xml
Macintosh file type code: "TEXT"
Macintosh文件类型代码：“文本”
Personal and email address for further information: IETF SIPPING
Working Group <sipping@ietf.org>, as designated by the IESG
<iesg@ietf.org>
Personal and email address for further information: IETF SIPPING
Working Group <sipping@ietf.org>, as designated by the IESG
<iesg@ietf.org>
Intended usage: COMMON
预期用途：普通
Author/Change controller: IETF SIPPING Working Group
<sipping@ietf.org>, as designated by the IESG <iesg@ietf.org>
Author/Change controller: IETF SIPPING Working Group
<sipping@ietf.org>, as designated by the IESG <iesg@ietf.org>
9.3. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info
9.3. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info
This section registers a new XML namespace, as per the guidelines in RFC 3688 [21].
本节根据RFC 3688[21]中的指导原则注册一个新的XML名称空间。
URI: The URI for this namespace is
urn:ietf:params:xml:ns:conference-info
URI: The URI for this namespace is
urn:ietf:params:xml:ns:conference-info
Registrant Contact: IETF SIPPING Working Group <sipping@ietf.org>,
as designated by the IESG <iesg@ietf.org>
Registrant Contact: IETF SIPPING Working Group <sipping@ietf.org>,
as designated by the IESG <iesg@ietf.org>
XML:
XML:
BEGIN
<?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>Conference Information Namespace</title>
BEGIN
<?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>Conference Information Namespace</title>
</head
<body>
<h1>Namespace for Conference Information</h1>
<h2>urn:ietf:params:xml:ns:conference-info</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4575.txt">
RFC4575</a>.</p>
</body>
</html>
END
</head
<body>
<h1>Namespace for Conference Information</h1>
<h2>urn:ietf:params:xml:ns:conference-info</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc4575.txt">
RFC4575</a>.</p>
</body>
</html>
END
This specification registers a schema, as per the guidelines in RFC 3688 [21].
根据RFC 3688[21]中的指南，本规范注册了一个模式。
URI: please assign
URI:请指定
Registrant Contact: IETF SIPPING Working Group <sipping@ietf.org>,
as designated by the IESG <iesg@ietf.org>
Registrant Contact: IETF SIPPING Working Group <sipping@ietf.org>,
as designated by the IESG <iesg@ietf.org>
XML: The XML can be found as the sole content of Section 6.
XML：XML是第6节的唯一内容。
The IANA has created a new sub-registry, "URI purposes", under the already existing registry: http://www.iana.org/assignments/sip-parameters.
IANA已在现有注册表下创建了一个新的子注册表“URI用途”：http://www.iana.org/assignments/sip-parameters.
The purpose of a URI is an XML element, encoded in the conference event package RFC 4575. The value of the <purpose> element indicates the intended usage of the URI in the context of the conference event package and is defined in Sections 5.3.1 and 5.3.2 of this specification.
URI的用途是XML元素，编码在会议事件包RFC4575中。<purpose>元素的值表示URI在会议事件包上下文中的预期用途，并在本规范第5.3.1节和第5.3.2节中定义。
This sub-registry is defined as a table that contains the following three columns:
此子注册表定义为包含以下三列的表：
Value: The token under registration
值：正在注册的令牌
Description: A descriptive text defining the intended usage of the URI
描述：定义URI预期用途的描述性文本
Document: A reference to the document defining the registration
文档：对定义注册的文档的引用
The IANA has created the table with the initial content as defined below:
IANA已创建具有以下初始内容的表：
Value Description Document
------- ---------------------------------- ----------
Value Description Document
------- ---------------------------------- ----------
participation The URI can be used to join the [RFC 4575] conference
参与URI可用于加入[RFC 4575]会议
streaming The URI can be used to access the [RFC 4575] streamed conference data
流式传输URI可用于访问[RFC 4575]流式会议数据
event The URI can be used to subscribe [RFC 4575] to the conference event package
事件URI可用于订阅[RFC 4575]会议事件包
recording The URI can be used to access the [RFC 4575] recorded conference data
记录URI可用于访问[RFC 4575]记录的会议数据
web-page The URI can be used to access a [RFC 4575] web page that contains additional information of the conference
网页URI可用于访问包含会议附加信息的[RFC 4575]网页
New values of the "URI purposes" are registered by the IANA and are specification required according to the definition of RFC 2434 [4]. The IANA Considerations section of the specification MUST include the following information:
IANA注册了“URI用途”的新值，根据RFC 2434[4]的定义，这些值是规范要求的。规范的IANA注意事项部分必须包括以下信息：
Value: The value of the <purpose> element to be registered
Value: The value of the <purpose> element to be registered
Description: A short description of the intended usage of the URI
描述：URI预期用途的简短描述
The authors would like to thank Dan Petrie, Sean Olson, Alan Johnston, Rohan Mahy, Cullen Jennings, Brian Rosen, Roni Even, and Miguel Garcia for their comments and inputs.
作者要感谢Dan Petrie、Sean Olson、Alan Johnston、Rohan Mahy、Cullen Jennings、Brian Rosen、Roni Even和Miguel Garcia的评论和意见。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Moats, R., "URN Syntax", RFC 2141, May 1997.
[2] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[3] Handley, M., Jacobson, V. and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006.
[3] Handley，M.，Jacobson，V.和C.Perkins，“SDP：会话描述协议”，RFC4566，2006年7月。
[4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[4] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[5] Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS Names", BCP 32, RFC 2606, June 1999.
[5] Eastlake 3rd，D.和A.Panitz，“保留顶级域名”，BCP 32，RFC 26061999年6月。
[6] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999.
[6] Moats，R.，“IETF文档的URN名称空间”，RFC 2648，1999年8月。
[7] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[7] Murata，M.，St.Laurent，S.，和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[8] 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.
[8] Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
[9] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002.
[9] Rosenberg，J.和H.Schulzrinne，“具有会话描述协议（SDP）的提供/应答模型”，RFC 3264，2002年6月。
[10] Roach, A.B., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002.
[10] Roach，A.B.，“会话启动协议（SIP）-特定事件通知”，RFC3265，2002年6月。
[11] Peterson, J., "A Privacy Mechanism for the Session Initiation Protocol (SIP)", RFC 3323, November 2002.
[11] Peterson，J.，“会话启动协议（SIP）的隐私机制”，RFC3323，2002年11月。
[12] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason Header Field for the Session Initiation Protocol (SIP)", RFC 3326, December 2002.
[12] Schulzrinne，H.，Oran，D.，和G.Camarillo，“会话启动协议（SIP）的原因头字段”，RFC3326，2002年12月。
[13] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003.
[13] Schulzrinne，H.，Casner，S.，Frederick，R.，和V.Jacobson，“RTP：实时应用的传输协议”，STD 64，RFC 35502003年7月。
[14] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[14] Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[15] Sparks, R., "The Session Initiation Protocol (SIP) Referred-By Mechanism", RFC 3892, September 2004.
[15] Sparks，R.，“机制引用的会话启动协议（SIP）”，RFC 38922004年9月。
[16] Rosenberg, J., "A Framework for Conferencing with the Session Initiation Protocol (SIP)", RFC 4353, February 2006.
[16] Rosenberg，J.，“会话启动协议（SIP）会议框架”，RFC 4353，2006年2月。
[17] Levin, O. and G. Camarillo, "The Session Description Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[17] Levin，O.和G.Camarillo，“会话描述协议（SDP）标签属性”，RFC 45742006年8月。
[18] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
[18] Schulzrinne，H.，Rao，A.，和R.Lanphier，“实时流协议（RTSP）”，RFC2326，1998年4月。
[19] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, December 2004.
[19] Schulzrinne，H.，“电话号码的电话URI”，RFC 3966，2004年12月。
[20] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme Registration", RFC 3508, April 2003.
[20] Levin，O.，“H.323统一资源定位器（URL）方案注册”，RFC 3508，2003年4月。
[21] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[21] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[22] Saint-Andre, P., "A Uniform Resource Identifier (URI) Scheme for the Extensible Messaging and Presence Protocol (XMPP)", Work in Progress, December 2004.
[22] Saint Andre，P.，“可扩展消息和状态协议（XMPP）的统一资源标识符（URI）方案”，正在进行的工作，2004年12月。
[23] Rosenberg, J., Schulzrinne, H., and R. Mahy, "An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)", RFC 4235, November 2005.
[23] Rosenberg，J.，Schulzrinne，H.，和R.Mahy，“会话启动协议（SIP）的邀请启动对话事件包”，RFC 42352005年11月。
[24] Rosenberg, J., "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)", Work in Progress, May 2006.
[24] Rosenberg，J.，“在会话启动协议（SIP）中获取和使用全局可路由用户代理（UA）URI（GRUU）”，正在进行的工作，2006年5月。
[25] Peterson, J. and C. Jennings, "Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)", RFC 4474, August 2006.
[25] Peterson，J.和C.Jennings，“会话启动协议（SIP）中身份验证管理的增强”，RFC 4474，2006年8月。
Authors' Addresses
作者地址
Jonathan Rosenberg Cisco Systems 600 Lanidex Plaza Parsippany, NJ 07054 US
Jonathan Rosenberg Cisco Systems 600美国新泽西州帕西帕尼拉尼德广场07054号
Phone: +1 973 952-5000
EMail: jdrosen@cisco.com
URI: http://www.jdrosen.net
Phone: +1 973 952-5000
EMail: jdrosen@cisco.com
URI: http://www.jdrosen.net
Henning Schulzrinne Columbia University M/S 0401 1214 Amsterdam Ave. New York, NY 10027 US
Henning Schulzrinne哥伦比亚大学M/S 0401 1214美国纽约州阿姆斯特丹大道10027号
EMail: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs
EMail: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs
Orit Levin (editor) Microsoft Corporation One Microsoft Way Redmond, WA 98052 US
Orit Levin（编辑）美国华盛顿州雷德蒙市微软公司一号微软路98052
EMail: oritl@microsoft.com
EMail: oritl@microsoft.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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.
本文件受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 provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。