Network Working Group O. Levin
Request for Comments: 4245 Microsoft Corporation
Category: Informational R. Even
Polycom
November 2005
Network Working Group O. Levin
Request for Comments: 4245 Microsoft Corporation
Category: Informational R. Even
Polycom
November 2005
High-Level Requirements for Tightly Coupled SIP Conferencing
紧密耦合SIP会议的高级别要求
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document examines a wide range of conferencing requirements for tightly coupled SIP conferences. Separate documents will map the requirements to existing protocol primitives, define new protocol extensions, and introduce new protocols as needed. Together, these documents will provide a guide for building interoperable SIP conferencing applications.
本文档研究紧密耦合SIP会议的各种会议需求。单独的文档将把需求映射到现有的协议原语，定义新的协议扩展，并根据需要引入新的协议。这些文档将共同为构建可互操作的SIP会议应用程序提供指南。
Table of Contents
目录
1. Introduction ....................................................2
2. An Overview .....................................................2
3. High-Level Requirements .........................................3
3.1. Discovery Phase ............................................3
3.2. Conference Creation ........................................4
3.3. Conference Termination .....................................4
3.4. Participants' Manipulations ................................4
3.4.1. Participation of a Conference-Unaware User Agent ......5
3.4.2. Dial-Out Scenarios ....................................5
3.4.3. Dial-In Scenarios .....................................5
3.4.4. Third-Party Invitation to a Conference ................6
3.4.5. Participants' Removal .................................6
3.4.6. Participants' Privacy .................................6
3.5. Conference State Information ...............................7
3.5.1. Description ...........................................7
3.5.2. Dissemination of Changes ..............................7
3.5.3. On-demand Information Dissemination ...................8
3.6. Focus Role Migration .......................................8
1. Introduction ....................................................2
2. An Overview .....................................................2
3. High-Level Requirements .........................................3
3.1. Discovery Phase ............................................3
3.2. Conference Creation ........................................4
3.3. Conference Termination .....................................4
3.4. Participants' Manipulations ................................4
3.4.1. Participation of a Conference-Unaware User Agent ......5
3.4.2. Dial-Out Scenarios ....................................5
3.4.3. Dial-In Scenarios .....................................5
3.4.4. Third-Party Invitation to a Conference ................6
3.4.5. Participants' Removal .................................6
3.4.6. Participants' Privacy .................................6
3.5. Conference State Information ...............................7
3.5.1. Description ...........................................7
3.5.2. Dissemination of Changes ..............................7
3.5.3. On-demand Information Dissemination ...................8
3.6. Focus Role Migration .......................................8
3.7. Side-bar Conferences .......................................8
3.8. Cascading of Conferences ...................................9
3.9. SIMPLE and SIP Conferencing Coordination ...................9
4. Security Considerations ........................................10
5. Contributors ...................................................10
6. References .....................................................10
6.1. Normative References ......................................10
3.7. Side-bar Conferences .......................................8
3.8. Cascading of Conferences ...................................9
3.9. SIMPLE and SIP Conferencing Coordination ...................9
4. Security Considerations ........................................10
5. Contributors ...................................................10
6. References .....................................................10
6.1. Normative References ......................................10
This document examines a wide range of conferencing requirements for tightly coupled SIP (RFC 3261 [2]) conferencing.
本文档研究了紧密耦合SIP（RFC 3261[2]）会议的广泛会议需求。
The requirements are grouped by subjects in various areas allowing solutions to progress in parallel.
需求按不同领域的主题进行分组，从而使解决方案能够并行进行。
Separate documents will map the requirements to existing protocol primitives, define new protocol extensions, and introduce new protocols as needed.
单独的文档将把需求映射到现有的协议原语，定义新的协议扩展，并根据需要引入新的协议。
Together, these documents will provide a guide for building interoperable SIP conferencing applications.
这些文档将共同为构建可互操作的SIP会议应用程序提供指南。
The terms "MAY", "SHOULD", and "MUST" are to be interpreted as described in RFC 2119 [1].
术语“可以”、“应该”和“必须”应按照RFC 2119[1]中所述进行解释。
A SIP conference is an association of SIP user agents (i.e., conference participants) with a central point (i.e., a conference focus), where the focus has direct peer-wise relationships with the participants by maintaining a separate SIP dialog with each.
SIP会议是SIP用户代理（即，会议参与者）与中心点（即，会议焦点）的关联，其中焦点通过与每个参与者保持单独的SIP对话而与参与者具有直接的对等关系。
The focus is a SIP user agent that has abilities to host SIP conferences including their creation, maintenance, and manipulation using SIP call control means and potentially other non-SIP means.
重点是SIP用户代理，该代理能够使用SIP呼叫控制手段和潜在的其他非SIP手段主持SIP会议，包括会议的创建、维护和操作。
In this tightly coupled model, the SIP conference graph is always a star. The conference focus maintains the correlation among conference's dialogs internally.
在这种紧耦合模型中，SIP会议图始终是星形的。会议焦点在内部维护会议对话之间的相关性。
The conference focus can be implemented either by a participant or by a separate application server.
会议焦点可以由参与者或单独的应用服务器实现。
In the first case, a focus is typically capable of hosting a simple ad hoc conference only. We envision that such basic conference can be established using SIP call control primitives only.
在第一种情况下，焦点通常只能主持一个简单的临时会议。我们设想这样的基本会议可以只使用SIP呼叫控制原语来建立。
A dedicated conference server, in addition to the basic features, offers richer functionality including simultaneous conferences, large scalable conferences, reserved conferences, and managed conferences. A conferencing server can support any subset of the advanced conferencing functions presented in this document.
除了基本功能外，专用会议服务器还提供更丰富的功能，包括同步会议、大型可扩展会议、保留会议和托管会议。会议服务器可以支持本文档中介绍的高级会议功能的任何子集。
The media graph of a SIP conference can be centralized, decentralized, or any combination of both, and potentially differ per media type. In the centralized case, the media sessions are established between the focus and each one of the participants. In the de-centralized (i.e., distributed) case, the media graph is a (multicast or multi-unicast) mesh among the participants. Consequently, the media processing (e.g., mixing) can be performed either by the focus alone or by the participants.
SIP会议的媒体图可以是集中式、分散式或两者的任意组合，并且可能因媒体类型而异。在集中的情况下，媒体会话在焦点和每个参与者之间建立。在非集中式（即分布式）情况下，媒体图是参与者之间的（多播或多单播）网格。因此，媒体处理（例如，混合）可以由焦点单独执行，也可以由参与者执行。
Conference participants and third parties can have different roles and privileges in a certain conference. For example, conferencing policy can state that the rights to disconnect from and to invite to a conference are limited to the conference chair only.
会议参与者和第三方在某个会议中可以有不同的角色和特权。例如，会议策略可以规定，与会议断开连接和邀请参加会议的权利仅限于会议主席。
Throughout the document, by conference policies we mean a set of parameters and rules (e.g., maximum number of participants, needs chair-person supervision or not, password protected or not, duration, or a way of media mixing) that are defined at the onset of a conference. Typically, conference policies would be specified by a conference creator and need special privileges to be manipulated.
在整个文件中，我们所说的会议政策是指在会议开始时定义的一组参数和规则（例如，最大与会者人数、是否需要主持人监督、是否有密码保护、持续时间或媒体混合方式）。通常情况下，会议策略将由会议创建者指定，并且需要特殊权限进行操作。
Throughout the document, by a conference state we mean a set of information describing the conference in progress. This includes participants' information (such as dialog identifiers), media sessions in progress, the current loudest speaker, the current chair, etc.
在整个文件中，会议状态是指描述正在进行的会议的一组信息。这包括参与者的信息（如对话标识符）、正在进行的媒体会议、当前声音最大的发言人、当前主席等。
In addition to the requirements presented in this document, supplementary requirements for conferencing policy, media mixing and other manipulations, floor control, privilege control, etc. will be discussed in separate documents.
除本文件中提出的要求外，会议策略、媒体混合和其他操作、楼层控制、权限控制等的补充要求将在单独的文件中讨论。
Some of the requirements presented in this section can be met either by configuration means or by using proprietary conventions. Nevertheless, there is consensus that standard means for implementing these functions by automata MUST be defined.
本节中提出的一些要求可以通过配置方式或使用专有约定来满足。然而，人们一致认为，必须定义通过自动机实现这些功能的标准方法。
REQ-1: Discovery of a location of an arbitrary SIP conferencing server(s).
REQ-1：发现任意SIP会议服务器的位置。
REQ-2: Given a SIP Address-of-Record (AOR) of a certain entity, resolution whether the SIP entity has focus capabilities.
REQ-2：给定某个实体的SIP记录地址（AOR），解析该SIP实体是否具有焦点功能。
REQ-3: Given a global identifier of a particular conference, locating the conference focus.
REQ-3：给定特定会议的全局标识符，定位会议焦点。
REQ-4: Given a global identifier of a particular conference, obtaining the conference properties.
REQ-4：给定特定会议的全局标识符，获取会议属性。
REQ-5: Given a global identifier of a particular conference, obtaining the conference state information.
REQ-5：给定特定会议的全局标识符，获取会议状态信息。
Given a focus location, a means MUST be defined for an interested entity (including a user agent) to implement the procedures below:
给定焦点位置，必须为感兴趣的实体（包括用户代理）定义一种方法，以实施以下程序：
REQ-1: Creation of an ad-hoc conference identifier and the conference with specified properties.
REQ-1：创建临时会议标识符和具有指定属性的会议。
REQ-2: Creation of a reserved conference identifier for a conference with specified properties.
REQ-2：为具有指定属性的会议创建保留会议标识符。
REQ-3: Specifying properties upon conference creation in any of the following ways: default, profiles, and explicitly.
REQ-3：在创建会议时以以下任一方式指定属性：默认、配置文件和显式。
REQ-1: Given a conference identifier, a means MUST be defined for a user agent to disconnect all participants from the conference and terminate the conference including the release of the associated resources.
REQ-1：给定会议标识符，必须为用户代理定义一种方法，以断开所有参与者与会议的连接，并终止会议，包括释放相关资源。
REQ-2: A means MAY be defined for requesting a focus to revert a two-party conference to a basic SIP point-to-point session including the release of the associated conferencing resources.
REQ-2：可以定义一种方法，用于请求焦点将两方会议恢复为基本SIP点对点会话，包括释放相关会议资源。
Some of the requirements presented in this section can be met by human intervention, configuration means, or proprietary conventions. Nevertheless, there is consensus that standard means for implementing these functions by automata MUST be defined.
本节中提出的一些要求可以通过人工干预、配置方式或专有约定来满足。然而，人们一致认为，必须定义通过自动机实现这些功能的标准方法。
REQ-1: Focus MUST be able to invite and disconnect an RFC 3261 compliant only SIP user agent to and from a SIP conference.
REQ-1:Focus必须能够邀请和断开仅符合RFC 3261的SIP用户代理与SIP会议的连接。
REQ-2: An RFC 3261 compliant only SIP user agent MUST be able to dial-in to a particular SIP conference. In this case, only the human knows that he/she is connected to the conference.
REQ-2：仅符合RFC 3261的SIP用户代理必须能够拨入特定的SIP会议。在这种情况下，只有人知道他/她与会议有关。
REQ-1: A means MUST be defined for a focus to invite another user agent to one of the focus' conferences. This procedure MUST result in the establishment of a single SIP dialog between the two.
REQ-1：必须为focus定义邀请另一个用户代理参加focus会议的方式。此过程必须导致在两者之间建立单个SIP对话。
REQ-2: Given an existing SIP dialog between two user agents, if at least one user agent has focus capabilities, a means MUST be defined for the conference focus to invite the other user agent to one of the focus' conferences without additional SIP dialog establishment.
REQ-2：给定两个用户代理之间的现有SIP对话，如果至少一个用户代理具有焦点功能，则必须为会议焦点定义一种方法，以邀请另一个用户代理参加焦点的一个会议，而无需建立额外的SIP对话。
REQ-3: An invitation to a user agent to join a conference MUST include a standard indication that it is a conference and the conference identifier.
REQ-3：向用户代理发出的加入会议的邀请必须包括一个标准指示，表明它是一个会议和会议标识符。
REQ-1: A means MUST be defined for a user agent to create an ad hoc conference with default properties (as per "Conference Creation" REQ-1 above) and to become a participant using a single SIP dialog.
REQ-1：必须为用户代理定义一种方法，以创建具有默认属性的临时会议（根据上面的“会议创建”REQ-1），并使用单个SIP对话框成为参与者。
REQ-2: Given a reserved conference identifier, a means MUST be defined for a user agent to activate the conference and to become a participant using a single SIP dialog.
REQ-2：给定保留的会议标识符，必须为用户代理定义一种方式，以激活会议并使用单个SIP对话框成为参与者。
REQ-3: Given a conference identifier of an active conference, a means MUST be defined for a user agent to dial-in the conference and to become a participant using a single SIP dialog between the two.
REQ-3：给定一个活动会议的会议标识符，必须为用户代理定义一种方法，以拨入会议，并使用两者之间的单个SIP对话成为参与者。
REQ-4: Given an identifier of one of the dialogs of a particular active conference, a means MUST be defined for a user agent to dial-in the conference and to become a participant.
REQ-4：给定特定活动会议的一个对话框的标识符，必须定义用户代理拨入会议并成为参与者的方式。
REQ-1: Given a conference identifier, a means MUST be defined for a user agent to invite another user agent to this conference.
REQ-1：给定会议标识符，必须为用户代理定义邀请另一个用户代理参加此会议的方式。
REQ-2: Given an identifier of one of the dialogs of a particular active conference, a means MUST be defined for a user agent to invite another user agent to this conference.
REQ-2：给定特定活动会议的一个对话框的标识符，必须为用户代理定义邀请另一个用户代理参加此会议的方式。
EQ-3: Given a conference identifier, a means SHOULD be defined for a user agent to invite a list of user agents to this conference (a so-called "mass invitation").
EQ-3：给定会议标识符，应为用户代理定义一种方法，以邀请用户代理列表参加本次会议（所谓的“大规模邀请”）。
REQ-1: A means MUST be defined for a conference focus to remove a conference participant from the conference.
REQ-1：必须为会议焦点定义将会议参与者从会议中移除的方法。
REQ-2: Given a conference identifier, a means MUST be defined for a
REQ-2：给定会议标识符，必须为会议定义方法
user agent to remove a participant from the conference.
用户代理从会议中删除参与者。
REQ-3: Given an identifier of one of the dialogs of a particular active conference, a means MUST be defined for a user agent to remove a participant from the conference.
REQ-3：给定特定活动会议的一个对话框的标识符，必须为用户代理定义将参与者从会议中移除的方法。
REQ-4: Given a conference identifier, a means MUST be defined for a user agent to remove all the participants from the conference.
REQ-4：给定会议标识符，必须为用户代理定义一种将所有参与者从会议中移除的方法。
REQ-5: Given a conference identifier and a sub-list of participants, a means MAY be defined for a user agent to remove the specified participants from the conference (a so-called "mass ejection").
REQ-5：给定会议标识符和参与者子列表，可以为用户代理定义将指定参与者从会议中移除的方法（所谓的“大规模喷射”）。
A conference focus SHOULD support the procedures described in this section. A conference participant MAY support the procedures described in this section. The requirements imply that "anonymizing" operations MUST be performed on all: the call control, the media control, and the media content when appropriate.
会议焦点应支持本节所述的程序。会议参与者可支持本节所述的程序。这些要求意味着必须对所有内容执行“匿名化”操作：呼叫控制、媒体控制和媒体内容（如果适用）。
REQ-1: A conference participant joins the conference "anonymously"; that is, his/her presence can be announced but without disclosing his/her identity.
REQ-1：会议参与者“匿名”加入会议；也就是说，可以宣布他/她的存在，但不披露他的/她的身份。
REQ-2: A conference participant requests a focus for anonymous participation in the conference.
REQ-2：会议参与者请求匿名参与会议的焦点。
REQ-3: A conference participant joins a conference in a "hidden mode"; that is, his/her presence and identity are not to be disclosed to other participants.
REQ-3：会议参与者以“隐藏模式”加入会议；也就是说，他/她的存在和身份不得透露给其他参与者。
REQ-4: A conference participant requests a focus for participation in the conference in a hidden mode.
REQ-4：会议参与者请求焦点以隐藏模式参与会议。
By a conference state, we mean a virtual database describing the conference in progress. This includes different conference aspects: participants' information (such as dialog identifiers and state), media sessions in progress (such as current stream contributing sources and encoding schemes), the current loudest speaker, the current chair, etc. Conference state is the latest conference snapshot triggered by changes in participants' state, conference policy changes, etc.
会议状态是指描述正在进行的会议的虚拟数据库。这包括不同的会议方面：与会者信息（如对话标识符和状态）、正在进行的媒体会议（如当前流贡献源和编码方案）、当前声音最大的发言人、当前主席、，etc.会议状态是由参与者状态更改、会议策略更改等触发的最新会议快照。
REQ-1: A conference state virtual database MUST have a modular definition that is, it MUST be possible to access different conference aspects independently.
REQ-1：会议状态虚拟数据库必须具有模块化定义，即必须能够独立访问不同的会议方面。
REQ-2: It MUST be possible to aggregate information relating to different conference aspects in a single report.
REQ-2：必须能够在一份报告中汇总与不同会议方面相关的信息。
REQ-3: A mechanism for extensible definition and registration of conference state evolving aspects MUST be present.
REQ-3：必须提供会议状态演化方面的可扩展定义和注册机制。
REQ-4: A default conference state report MUST be defined. It SHOULD contain a minimal useful set of information (e.g., a list of current conference participants).
REQ-4：必须定义默认会议状态报告。它应该包含一组最有用的信息（例如，当前会议参与者的名单）。
REQ-1: A means MUST be defined for reporting the conference state changes to interested parties (including non-conference participants) in a timely manner.
REQ-1：必须定义及时向相关方（包括非会议参与者）报告会议状态变化的方法。
REQ-2: A means MUST be defined for a SIP user agent to express its interest in selected state changes only.
REQ-2：必须为SIP用户代理定义一种方法，以仅表示其对所选状态更改的兴趣。
REQ-3: A means MUST be defined for a SIP user agent to express the minimum interval between receiving state change reports.
REQ-3：必须为SIP用户代理定义一种方法，以表示接收状态更改报告之间的最小间隔。
REQ-4: It MUST be possible to aggregate recent changes in a single reporting event.
REQ-4：必须能够在单个报告事件中聚合最近的更改。
REQ-5: Default conference state change reports MUST be defined. They SHOULD contain minimal useful to the participants information (e.g., participants' joining and leaving the conference).
REQ-5：必须定义默认会议状态更改报告。它们应包含对参与者有用的最少信息（例如，参与者参加和离开会议）。
REQ-1: A means MUST be defined to disseminate any conference state information to interested parties (including SIP user agents) on-demand.
REQ-1：必须定义一种按需向相关方（包括SIP用户代理）传播任何会议状态信息的方法。
REQ-2: A means MUST be defined for an interested party (including a SIP user agent) to request conference state information of a particular conference defined by the conference identifier.
REQ-2：必须为相关方（包括SIP用户代理）定义一种方式，以请求由会议标识符定义的特定会议的会议状态信息。
REQ-3: A means MUST be defined for an interested party (including a SIP user agent) to specify the subset of the conference state information it wants and is capable of receiving.
REQ-3：必须为相关方（包括SIP用户代理）定义一种方法，以指定其想要并能够接收的会议状态信息的子集。
REQ-1: A procedure for delegating a focus role by the current focus to another participant MUST be defined.
REQ-1：必须定义当前焦点将焦点角色委派给其他参与者的过程。
REQ-2: A procedure for requesting a conference focus to transfer its role to another participant MUST be defined.
REQ-2：必须定义请求会议焦点将其角色转移给其他参与者的程序。
REQ-3: A procedure for on-demand unconditional transfer of the focus role to a different participant MUST be defined.
REQ-3：必须定义按需无条件将焦点角色转移给不同参与者的程序。
REQ-4: A detection procedure for a focus failure condition MUST be defined.
REQ-4：必须定义聚焦故障条件的检测程序。
A standard means MUST be defined in order to implement the operations defined in this section below.
必须定义标准方法，以实施下文本节中定义的操作。
REQ-1: A user agent (not a conference participant) joins a side-bar within the conference by SIP means.
REQ-1：用户代理（不是会议参与者）通过SIP方式加入会议内的侧栏。
REQ-2: A user agent (not a conference participant) is invited to a side-bar within the conference by SIP means.
REQ-2：通过SIP方式邀请用户代理（不是会议参与者）到会议内的侧栏。
REQ-3: A conference participant creates a side-bar conference with one or more participants in a conference by SIP means.
REQ-3：会议参与者通过SIP方式与会议中的一个或多个参与者创建侧栏会议。
REQ-4: A conference participant joins a side-bar within the conference by SIP means.
REQ-4：会议参与者通过SIP方式加入会议内的侧栏。
REQ-5: A conference participant is invited to a side-bar within the conference by SIP means.
REQ-5：会议参与者通过SIP方式被邀请到会议内的侧栏。
REQ-6: A conference-unaware user agent (a participant or not) creates and participates in side-bar conferences. It MAY be achieved by non-SIP means.
REQ-6：不知道会议的用户代理（参与者或非参与者）创建并参与侧栏会议。它可以通过非SIP方式实现。
REQ-7: A conference participant creates side-bar conferences within the conference without establishing any additional SIP dialogs with the focus. It MAY be achieved by non-SIP means.
REQ-7：会议参与者在会议中创建侧栏会议，而不建立任何附加的SIP对话。它可以通过非SIP方式实现。
REQ-8: A conference participant joins any number of side-bars within the conference without establishing any additional SIP dialogs with the focus. It MAY be achieved by non-SIP means.
REQ-8：会议参与者在会议中加入任意数量的侧栏，而无需与焦点建立任何额外的SIP对话。它可以通过非SIP方式实现。
REQ-9: A conference participant is invited to any number of side-bars within the conference without establishing any additional SIP dialogs with the focus. It MAY be achieved by non-SIP means.
REQ-9：会议参与者被邀请参加会议内的任意数量的侧栏，而无需建立任何与焦点相关的附加SIP对话。它可以通过非SIP方式实现。
"Cascading of Conferences" is a term that has different meanings in different contexts. Some examples are listed below:
“会议级联”是一个术语，在不同的上下文中有不同的含义。下面列出了一些例子：
- Peer-to-peer chaining of signaling. (Many ways exist to build the media graph in this case.)
- 信令的点对点链接。（在这种情况下，有许多方法可以构建媒体图。）
- Conferences have hierarchal signaling relations. (Many ways exists to build the media graph in this case.)
- 会议具有层级信号关系。（在这种情况下，有许多方法可以构建媒体图。）
- "Cascading" is used to distribute the media "mixing" only. The distribution of signaling is not required.
- “级联”仅用于分发媒体“混合”。不需要分配信号。
As it can be seen from the examples, each will define a different set of requirements.
从示例中可以看出，每个示例将定义一组不同的需求。
REQ-1: SIMPLE-based Presence and Instant Messaging architecture SHOULD fit into the general SIP Conferencing architecture.
REQ-1：基于简单的状态和即时消息体系结构应该适合于一般的SIP会议体系结构。
REQ-2: A scenario where a multimedia SIP conference and a multiparty instant messaging conversation take place among the same group of participants MUST be addressed.
REQ-2：必须解决在同一组参与者之间进行多媒体SIP会议和多方即时消息会话的场景。
REQ-3: A scenario where a side-bar and/or a sub-IM-conference is being held as a part of SIP conference MUST be addressed.
REQ-3：必须解决侧栏和/或子IM会议作为SIP会议的一部分举行的情况。
This document discusses high-level requirements for SIP conferencing. Conferencing has some specific security requirements, which will be summarized here at a very high level.
本文档讨论SIP会议的高级需求。会议有一些特定的安全要求，这里将从一个非常高的级别对其进行总结。
All of the operations and functions described in this document need to be authorized by a focus or a participant. It is expected that conferences will be governed by a set of authorization rules defined as a part of the conference policy. In order for the conference policy to be implemented, the focus needs to be able to authenticate potential participants. Normal SIP mechanisms including Digest authentication and certificates can be used [2]. These conference-specific security requirements will be discussed in detail in the protocol documents.
本文档中描述的所有操作和功能都需要获得focus或参与者的授权。预计会议将由一套作为会议政策一部分的授权规则管理。为了实施会议政策，焦点需要能够认证潜在参与者。可以使用正常的SIP机制，包括摘要身份验证和证书[2]。这些会议特定的安全要求将在议定书文件中详细讨论。
Conferencing also has privacy implications. Some of these are discussed in this document. Standard SIP mechanisms for a user agent to request privacy should be utilized by a focus and will be detailed in the protocol documents.
会议还涉及隐私问题。本文将讨论其中的一些问题。focus应使用用户代理请求隐私的标准SIP机制，并将在协议文档中详细说明。
This work is based on the discussions among the members of the SIP Conferencing design team.
这项工作基于SIP会议设计团队成员之间的讨论。
[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] 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.
[2] Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.和E.Schooler，“SIP：会话启动协议”，RFC 3261，2002年6月。
Authors' Addresses
作者地址
Orit Levin Microsoft Corporation One Microsoft Way Redmond, WA 98052
奥利特·莱文微软公司华盛顿州雷德蒙微软大道一号，邮编：98052
EMail: oritl@microsoft.com
EMail: oritl@microsoft.com
Roni Even Polycom 94 Derech Em Hamoshavot Petach Tikva, Israel
Roni Even Polycom 94 Derech Em Hamoshavot Petach Tikva，以色列
EMail: roni.even@polycom.co.il
EMail: roni.even@polycom.co.il
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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 currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。