Network Working Group L. Andersson, Ed.
Request for Comments: 4691 IAB
Category: Informational October 2006
Network Working Group L. Andersson, Ed.
Request for Comments: 4691 IAB
Category: Informational October 2006
Guidelines for Acting as an IETF Liaison to Another Organization
作为IETF与其他组织的联络人的指南
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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
Whenever the IETF decides to enter into a liaison relationship with another organization, such as a Standards Development Organization (SDO), a consortium, or an industrial forum, a liaison manager is appointed. The procedures used by the IAB to establish and maintain liaison relationships between the IETF and other organizations are described in RFC 4052. This document expands on the role of liaison managers and liaison representatives, giving guidelines on their mandate and the expectations, tasks, and responsibilities placed on them.
每当IETF决定与另一个组织（如标准开发组织（SDO）、联合体或工业论坛）建立联络关系时，都会任命一名联络经理。IAB用于建立和维护IETF与其他组织之间联络关系的程序在RFC 4052中进行了描述。本文件详述了联络经理和联络代表的作用，为他们的任务规定、期望、任务和责任提供了指导。
Table of Contents
目录
1. Introduction ....................................................2
2. IETF Liaison Relationships ......................................3
2.1. Related Documents ..........................................3
2.2. Liaison Managers and Liaison Representatives ...............3
2.3. Written Communications .....................................4
2.4. Terminology and Conventions ................................5
3. Guidelines for Liaison Managers and Representatives .............5
3.1. Mandate ....................................................6
3.1.1. Speaking for the IETF ...............................6
3.2. Expectations ...............................................6
3.3. Responsibilities ...........................................8
3.4. Tasks ......................................................9
3.5. Relationship Management ...................................10
3.5.1. IETF Consensus Process on Liaison Statements .......10
3.5.2. Incoming Liaison Statements ........................10
3.5.3. Ambiguous Incoming Liaison Statements ..............11
3.5.4. Liaison Managers Representing Peer Organizations ...11
1. Introduction ....................................................2
2. IETF Liaison Relationships ......................................3
2.1. Related Documents ..........................................3
2.2. Liaison Managers and Liaison Representatives ...............3
2.3. Written Communications .....................................4
2.4. Terminology and Conventions ................................5
3. Guidelines for Liaison Managers and Representatives .............5
3.1. Mandate ....................................................6
3.1.1. Speaking for the IETF ...............................6
3.2. Expectations ...............................................6
3.3. Responsibilities ...........................................8
3.4. Tasks ......................................................9
3.5. Relationship Management ...................................10
3.5.1. IETF Consensus Process on Liaison Statements .......10
3.5.2. Incoming Liaison Statements ........................10
3.5.3. Ambiguous Incoming Liaison Statements ..............11
3.5.4. Liaison Managers Representing Peer Organizations ...11
4. Security Considerations ........................................12
5. IANA Considerations ............................................12
6. Acknowledgements ...............................................12
7. References .....................................................13
7.1. Normative References ......................................13
7.2. Informative References ....................................13
4. Security Considerations ........................................12
5. IANA Considerations ............................................12
6. Acknowledgements ...............................................12
7. References .....................................................13
7.1. Normative References ......................................13
7.2. Informative References ....................................13
In the course of developing Internet standards, the IETF needs to communicate extensively with various other peer organizations, including the following:
在制定互联网标准的过程中，IETF需要与各种其他对等组织进行广泛的沟通，包括：
o Standards Development Organizations (SDOs) such as the Telecommunication Standardization Sector of the International Telecommunication Union (ITU-T) or standardization working groups of the Institute of Electrical and Electronics Engineers (e.g., IEEE 802)
o 标准开发组织（SDO），如国际电信联盟（ITU-T）的电信标准化部门或电气和电子工程师协会的标准化工作组（如IEEE 802）
o Consortia such as the World Wide Web Consortium (W3C)
o 联合体，如万维网联合体（W3C）
o Industrial forums such as the Global Grid Forum (GGF)
o 行业论坛，如全球电网论坛（GGF）
These organizations are usually concerned with developing related standards and technical specifications, so that from time to time issues of coordination and mutual interest may arise. To facilitate communications, the IETF, through the Internet Architecture Board (IAB), establishes permanent liaison relationships with appropriate parts of these organizations according to the processes described in RFC 4052 [RFC4052].
这些组织通常关心制定相关标准和技术规范，以便不时出现协调和共同利益的问题。为了促进通信，IETF通过互联网体系结构委员会（IAB），根据RFC 4052[RFC4052]中描述的流程，与这些组织的适当部分建立永久联络关系。
Whenever the IETF decides to enter into a liaison relationship, a liaison manager and possibly some liaison representatives are appointed by the IAB to act as a channel between the IETF and the peer organization, typically in tandem with counterparts appointed by the peer organization.
每当IETF决定建立联络关系时，IAB将任命一名联络经理和一些可能的联络代表作为IETF与对等组织之间的渠道，通常与对等组织指定的对应方协同工作。
Sections 2.2, 2.3, and 3 of RFC 4052 briefly set out the basic functions of the tasks of liaison managers and representatives. Over time, the number and importance of liaisons have grown, and the importance of the personal role of IETF liaison managers and representatives in maintaining effective relationships with peer organizations has grown concomitantly. This document supplements [RFC4052] by providing guidelines for liaison managers and liaison representatives in maintaining communications to peer organizations.
RFC 4052第2.2、2.3和3节简要阐述了联络经理和代表任务的基本职能。随着时间的推移，联络的数量和重要性不断增加，IETF联络经理和代表在维持与同行组织的有效关系方面的个人角色的重要性也随之增加。本文件补充了[RFC4052]，为联络经理和联络代表提供了与同行组织保持沟通的指南。
A major goal of the IETF is to develop standards for the Internet, enabling the development of interoperable implementations. In order to develop Internet standards, it is frequently necessary for the IETF to communicate with other organizations that develop standards for other types of networks, for Internet applications, or for technologies that the Internet uses.
IETF的一个主要目标是为互联网制定标准，从而能够开发可互操作的实现。为了制定互联网标准，IETF经常需要与为其他类型的网络、互联网应用或互联网使用的技术制定标准的其他组织进行沟通。
In some cases, the IETF and peer organizations consider it mutually beneficial to have a permanent formal relationship with certain rules governing the relationship. The organizations then enter into a "liaison relationship". At a high level, both sides agree to undertake certain responsibilities with respect to each other. The most basic liaison responsibility is to communicate information as necessary, and to respond to requests from peer organizations to which liaisons are maintained.
在某些情况下，IETF和对等组织认为与某些关系规则有永久的正式关系是互利的。各组织随后建立“联络关系”。在高层，双方同意对彼此承担某些责任。最基本的联络职责是在必要时传达信息，并响应保持联络的同行组织的请求。
Decisions on IETF liaison relationships are the responsibility of the IAB. This includes whether or not the IETF should have a liaison relationship with a particular organization.
IETF联络关系的决定由IAB负责。这包括IETF是否应与特定组织建立联络关系。
The IETF liaison process is specified in several documents. RFC 4052 [RFC4052] specifies how the IAB manages the IETF liaison relationship; RFC 4053 [RFC4053] specifies how liaison statements should be treated. Organization-specific agreements and documents may also be generated in some cases, e.g., RFC 3356 [RFC3356] describes the collaboration between the IETF and ITU-T, RFC 3113 [RFC3113] describes the relationship with the 3rd Generation Partnership Project (3GPP), and RFC 3131 [RFC3131] describes the one with the Third Generation Partnership Project 2 (3GPP2).
IETF联络流程在多个文件中有详细说明。RFC 4052[RFC4052]规定了IAB如何管理IETF联络关系；RFC 4053[RFC4053]规定了如何处理联络声明。在某些情况下，也可能生成特定于组织的协议和文件，例如，RFC 3356[RFC3356]描述IETF和ITU-T之间的协作，RFC 3113[RFC3113]描述与第三代合作伙伴关系项目（3GPP）的关系，以及RFC 3131[RFC3131]描述与第三代合作伙伴关系项目2（3GPP2）的一个。
Whenever the IETF enters into a liaison relationship with another organization, a liaison manager (often referred to as "the IETF liaison") is appointed by the IAB. This document expands on the mandate of and the expectations, tasks, and responsibilities placed on the liaison manager by Section 2.2 of RFC 4052.
每当IETF与其他组织建立联络关系时，IAB都会任命一名联络经理（通常称为“IETF联络人”）。本文件详述了RFC 4052第2.2节赋予联络经理的任务、期望、任务和责任。
In some cases, it may be necessary to have more than one person handling the liaison relationship with a given organization. For example, the time commitment required may be too substantial, or the technical scope of the liaison relationship may be too broad to be handled by a single individual.
在某些情况下，可能需要有一名以上的人员处理与特定组织的联络关系。例如，所需时间可能太长，或者联络关系的技术范围可能太广，无法由一个人处理。
In such cases, the IAB may appoint one or more liaison representatives to supplement the work of the liaison manager by managing different aspects of the liaison relationship between the IETF and the other organization.
在这种情况下，IAB可任命一名或多名联络代表，通过管理IETF与其他组织之间联络关系的不同方面，补充联络经理的工作。
The value of personal relationships between the IETF liaison manager and representatives and members of the peer organization is central to the roles. The IAB will be looking for people who have both a good technical understanding of the work being carried out and effective personal relationships within the peer organization. Ongoing face-to-face interactions between the IETF liaisons and members of the peer organization are seen as critical to the effective functioning of the role. These interactions should allow the liaisons to keep the IETF abreast, and preferably ahead, of matters of mutual interest or potential conflict. When the liaison is working effectively, it should facilitate the IETF and the peer organization working synergistically and reduce the chance of overlapping or conflicting standards being created.
IETF联络经理与同行组织的代表和成员之间的人际关系对角色至关重要。IAB将寻找对正在开展的工作有良好技术理解和在同行组织内有有效人际关系的人员。IETF联络人与同行组织成员之间的持续面对面互动被视为该角色有效运作的关键。这些互动应使联络人能够及时了解IETF，最好提前了解共同利益或潜在冲突的事项。当联络有效工作时，应促进IETF和同行组织协同工作，减少产生重叠或冲突标准的机会。
Aside from the personal contacts between liaisons and the peer organization, extensive communication may occur between the IETF and the peer organizations through written materials. Much of this communication is through liaison statements that typically contain plans, new developments, and time schedules of which one party believes that the other party should be aware.
除了联络人和同行组织之间的个人联系外，IETF和同行组织之间还可以通过书面材料进行广泛的沟通。大部分沟通是通过联络声明进行的，通常包括一方认为另一方应该知道的计划、新发展和时间表。
The liaison manager should be aware of these written communications and assist both parties to see that appropriate action is taken in relation to liaison statements passing in both directions.
联络经理应了解这些书面沟通，并协助双方就双向传递的联络声明采取适当行动。
For example, when a liaison organization, such as ITU-T, needs to reference material that is under development in the IETF: the final reference in the peer organization's document needs the permanent identifier (RFC number) that will be assigned to the Internet Draft when it is approved and published. To meet the publication schedule of the peer organization, a liaison statement is often sent to the IETF requesting that an RFC number be assigned within the required timeframe. In response, the IETF can provide the RFC number or explain why it is not possible to provide this within the timeframe requested.
例如，当一个联络组织（如ITU-T）需要参考IETF中正在开发的材料时：对等组织文件中的最终参考需要永久标识符（RFC编号），该标识符将在互联网草案批准和发布时分配给互联网草案。为了满足同行组织的出版时间表，通常会向IETF发送一份联络声明，要求在要求的时间范围内分配RFC编号。作为回应，IETF可以提供RFC编号，或者解释为什么不能在要求的时间范围内提供该编号。
An alternative situation that involves more specific action by the liaison manager also involves requests for this kind of expedited action on RFCs. For example, 3GPP/3GPP2 and the Open Mobile Alliance (OMA) provide the IETF with an updated list of dependencies between their documents and IETF documents on a monthly basis, indicating
另一种情况涉及联络经理采取更具体的行动，也涉及请求对RFC采取此类快速行动。例如，3GPP/3GPP2和开放移动联盟（OMA）每月向IETF提供其文档和IETF文档之间的依赖关系的更新列表，表明
what documents are needed and the required timeframe. In this case, the liaison manager tracks the dependency list and, when necessary, conveys the request for expedited assignment to the appropriate IETF Area Director (AD).
需要哪些文件以及所需的时间范围。在这种情况下，联络经理跟踪依赖项列表，并在必要时将快速分配请求传达给相应的IETF区域主管（AD）。
Terminology relating to IETF liaison procedures is found in [RFC4052]. Terms defined below are valid for this document only.
与IETF联络程序相关的术语见[RFC4052]。以下定义的术语仅对本文件有效。
Liaison manager
联络经理
A person appointed to manage an IETF liaison relationship with another organization.
被任命管理IETF与其他组织的联络关系的人员。
Liaison representative
联络代表
A person appointed to manage a certain (sub-)aspect of an IETF liaison relationship with another organization. Since it is only the scale of the responsibilities, mandate, and tasks that is different, the rest of this document only explicitly mentions liaison managers.
被任命管理IETF与另一组织联络关系的某一（子）方面的人员。由于只有责任、授权和任务的规模不同，本文件其余部分仅明确提及联络经理。
IETF consensus
IETF共识
RFC 2026 [RFC2026] and RFC 2418 [RFC2418] discuss the IETF consensus process. In this document, the term "IETF consensus" is used to indicate either consensus of the IETF as an organization, an area within IETF, or a working group. There the term "IETF consensus" needs to be interpreted in the context in which it is used.
RFC 2026[RFC2026]和RFC 2418[RFC2418]讨论了IETF共识过程。在本文件中，“IETF共识”一词用于表示IETF作为一个组织、IETF内的一个领域或一个工作组的共识。在这里，“IETF共识”一词需要在其使用的上下文中加以解释。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
Since liaison relationships are intended to be mutually beneficial, the IETF liaison to another organization must act as a bi-directional communication link between the IETF and the other organization. Since the liaison manager has been appointed by the IETF, the liaison manager needs to be responsive to the needs and aims of the IETF.
由于联络关系旨在互惠互利，IETF与另一组织的联络必须作为IETF与另一组织之间的双向通信链路。由于联络经理是由IETF任命的，因此联络经理需要响应IETF的需求和目标。
RFC 4052 lists some of the tasks and expectations relating to liaison managers and liaison representatives. This document expands on their mandate, provides more detailed discussion, and describes how the role is executed.
RFC 4052列出了与联络经理和联络代表相关的一些任务和期望。本文档扩展了他们的任务，提供了更详细的讨论，并描述了如何执行角色。
The mandate for IETF liaison managers is strictly limited to conveying IETF consensus to the liaised organization. The liaison manager MUST NOT on their own initiative send liaison statements to a liaised organization on behalf of IETF, or any of its areas and working groups. Liaison statements are only sent following the process specified in [RFC4052]. Liaison statements are only sent on the initiative of the IETF chair, the IAB chair, IETF Area Directors, or IETF working group chairs.
IETF联络经理的任务严格限于向联络组织传达IETF共识。联络经理不得主动代表IETF或其任何区域和工作组向联络组织发送联络声明。以下是RFC4052中规定的联络声明。联络声明仅在IETF主席、IAB主席、IETF区域总监或IETF工作组主席的倡议下发送。
In Section 3.3 and Section 3.4, responsibilities and tasks are listed that enable the IETF to obtain the information to correctly interact with the liaised organizations and to develop and clearly communicate IETF consensus.
在第3.3节和第3.4节中，列出了使IETF能够获得与联络组织正确互动的信息，并形成和明确传达IETF共识的责任和任务。
The IETF functions based on rough consensus, which means that the right to speak for the IETF cannot be delegated. The liaison manager speaks on behalf of the IETF on the subject matter of the liaison, but only after making sure that the IETF consensus is understood. Some guidelines for understanding IETF consensus are provided above; however, the most important requirement is close and detailed coordination/consultation with the IETF community.
IETF的功能基于粗略的共识，这意味着不能授予IETF发言权。联络经理代表IETF就联络主题发言，但仅在确保IETF共识被理解之后。上面提供了一些理解IETF共识的指南；然而，最重要的要求是与IETF社区进行密切和详细的协调/协商。
There are certain expectations placed on liaison managers appointed by the IETF. Examples of these expectations are listed below.
对IETF任命的联络经理有一定的期望。下面列出了这些期望的示例。
Competences required
所需能力
The key competence needed in the liaison manager or representative role is effective management of the liaison process according to the rules that have been agreed upon. The liaison acts as a representative of the IETF and not an independent voice with respect to topics of discussion in the liaison relationship. The liaison must therefore be careful to distinguish his or her own views from documented IETF consensus in dealings with the peer organization.
联络经理或代表角色所需的关键能力是根据商定的规则对联络过程进行有效管理。联络人作为IETF的代表，而不是联络关系中讨论主题的独立声音。因此，联络人在与同行组织打交道时，必须小心区分自己的观点与记录在案的IETF共识。
To this end, the liaison manager or representative must be able to communicate effectively with members of the peer organization, especially in face-to-face situations. This is important both to communicate the IETF's viewpoint and to gather information about the issues in the peer organization that the IETF needs to understand.
为此，联络经理或代表必须能够与同行组织的成员进行有效沟通，尤其是在面对面的情况下。这对于传达IETF的观点和收集IETF需要了解的同行组织中的问题信息都很重要。
In support of the liaison process, a person appointed to act as a liaison manager or representative on behalf of the IETF is expected to have a good technical understanding of the key issues in the subject area, as well as an understanding of the concerns important to stakeholders in both organizations.
为支持联络过程，被任命为IETF联络经理或代表的人员应充分了解主题领域中的关键问题，并了解对两个组织的利益相关者都很重要的问题。
An IETF liaison needs to have knowledge of the IETF's consensus process in general, as well as the consensus process(es) applying to the key issues within the liaison relationship.
IETF联络员一般需要了解IETF的协商一致过程，以及适用于联络关系中关键问题的协商一致过程。
The liaison must also have a good understanding of the processes used by the peer organization involved.
联络员还必须充分了解相关同行组织使用的流程。
Perspective
态度
Liaison relationships are designed for the mutual benefit of the organizations participating in the liaison. As such, swift information flow in both directions is a firm requirement. The role of an IETF liaison manager is to promote the interests of the IETF with respect to all topics within the scope of the liaison relationship. Since the liaison manager "wears an IETF hat", it is NOT the task of a liaison manager to promote the interests of the liaised organization within the IETF.
联络关系是为参与联络的各组织的共同利益而设计的。因此，两个方向的快速信息流是一项坚定的要求。IETF联络经理的职责是促进IETF在联络关系范围内所有主题方面的利益。由于联络经理“戴着IETF帽子”，因此在IETF内促进联络组织的利益不是联络经理的任务。
Distance
距离
A liaison may not be able to maintain the required perspective if he or she is closely involved in the outcome of the work in the peer organization. A conflict of interest might arise if the liaison is involved in the management of the relevant part of the peer organization, has a close technical involvement in the work that is the subject of the liaison, or has a close interest in the outcome of the work in the peer organization through his or her employment. When appointing an appropriate person to manage a liaison relationship, the IAB needs to take into account any conflicts of interest that the individual being considered might have. Before a person is appointed to manage a liaison relationship, he or she will be asked to explicitly state any conflicts of interest. The IAB will not appoint a person to a liaison manager position if there is a strong conflict of interest. For example, an individual with an industry or organizational leadership position in an organization would typically not be suitable for appointment as an IETF liaison to that organization.
如果联络员密切参与同级组织的工作成果，则联络员可能无法保持所需的视角。如果联络人参与管理同行组织的相关部分，密切参与作为联络主题的工作，或通过其受雇关系密切关注同行组织的工作成果，则可能会产生利益冲突。在任命适当人员管理联络关系时，IAB需要考虑被考虑的个人可能存在的任何利益冲突。在任命一个人管理联络关系之前，他或她将被要求明确说明任何利益冲突。如果存在强烈的利益冲突，IAB不会任命任何人担任联络经理职位。例如，在组织中担任行业或组织领导职务的个人通常不适合被任命为该组织的IETF联络员。
Commitment and opportunity
承诺和机会
A liaison manager needs to be committed to addressing the issues relevant to the liaison relationship. To handle the job properly, it is necessary that the liaison be able to allocate sufficient time to the task.
联络经理需要致力于解决与联络关系相关的问题。为了妥善处理这项工作，联络员必须能够为这项任务分配足够的时间。
Timeliness
及时性
It is expected that a liaison manger will make the IETF aware of new developments in the subject area in a timely fashion.
预计联络经理将使IETF及时了解主题领域的新发展。
The liaison manager and representatives provide information to the IETF community in order to enable the IETF to make decisions based on the best possible information regarding the work in the peer organization. In turn, information communicated by the IETF liaison to the liaised organization MUST be based on the relevant IETF consensus. The liaison manager works with the liaised organization to ensure that communication is clear. As part of this, the liaison must clearly differentiate his or her own independent positions from those that represent IETF consensus.
联络经理和代表向IETF社区提供信息，以使IETF能够根据同行组织工作的最佳信息做出决策。反过来，IETF联络人向联络组织传达的信息必须基于相关IETF共识。联络经理与被联络组织合作，确保沟通清晰。作为这项工作的一部分，联络人必须明确区分其独立立场与代表IETF共识的立场。
It is the responsibility of the liaison manager to ensure that the liaised organization communicates its requirements to the IETF in a timely fashion and that the IETF consensus is clearly understood. This is particularly important in situations where the IETF and the liaised organization differ substantially in their positions. In this situation, the liaison manager needs to facilitate prompt communication so that the IETF and the liaised organization can stay in close communication and avoid misunderstandings.
联络经理有责任确保联络组织及时向IETF传达其要求，并确保IETF共识得到明确理解。在IETF和联络组织的立场存在重大差异的情况下，这一点尤为重要。在这种情况下，联络经理需要促进及时沟通，以便IETF和被联络组织保持密切沟通，避免误解。
The liaison manager and representatives are responsible for clearly and correctly communicating the IETF consensus position to the liaised organization. This includes, when specifically instructed, carrying any messages from the IETF to the peer organization. Generally, these communications "represent the IETF", and therefore due care and consensus must be applied in their construction.
联络经理和代表负责向被联络组织清楚、正确地传达IETF共识立场。这包括，当特别指示时，将任何消息从IETF传送到对等组织。一般来说，这些通信“代表IETF”，因此在其构建过程中必须谨慎行事并达成共识。
The liaison manager and representatives are responsible for ensuring that relevant information originating from the liaised organization, or other information coming to the attention of the liaison, reaches the correct destination within the IETF, in a timely and effective way.
联络经理和代表负责确保来自被联络组织的相关信息或联络人注意到的其他信息及时有效地到达IETF内的正确目的地。
Examples of tasks performed by the liaison manager are provided below. Depending on the nature of the liaised organization, the task may vary in frequency and relative importance.
联络经理执行的任务示例如下所示。根据联络组织的性质，任务的频率和相对重要性可能有所不同。
1. Attend relevant meetings and participate in conference calls and mailing lists within the liaised organization to gather information relevant to the liaison relationship. Note developments of interest for onward communication to the IETF. Communicate the point of view of the IETF consensus to the peer organization.
1. 参加相关会议，参加联络组织内的电话会议和邮件列表，以收集与联络关系相关的信息。注意与IETF进行后续通信的相关发展。向同行组织传达IETF共识的观点。
2. Communicate information relevant to the liaison relationship to the relevant part of the IETF either by written reports or verbally; this may involve briefings with a team of IETFers involved in the liaised organization and other interested parties within the IETF, e.g., working group chairs and ADs.
2. 通过书面报告或口头方式将与联络关系相关的信息传达给IETF的相关部分；这可能涉及与联络组织中涉及的IETF团队和IETF内的其他相关方（如工作组主席和ADs）进行简报。
3. Understand the concerns of both the IETF and the peer organization, while ensuring that interests of the IETF are maintained; where there appear to be problems to solve or conflicts between approaches, work with both parties to encourage engineers from both organizations to collaborate on solving the problem and facilitate the development of engineering solutions in the appropriate organization.
3. 了解IETF和同行组织的关注点，同时确保维护IETF的利益；如果出现需要解决的问题或方法之间存在冲突，请与双方合作，鼓励双方组织的工程师合作解决问题，并促进在适当的组织中开发工程解决方案。
4. Prepare reports giving updates on developments in the peer organization as requested by the IAB or other interested parties in the IETF. The target for these updates (e.g., the IAB, an AD, a WG) will typically be identified upon establishment of the liaison relationship and/or the appointment of the liaison manager.
4. 根据IAB或IETF中其他相关方的要求，编制报告，提供同行组织发展的最新情况。这些更新的目标（例如，IAB、AD、WG）通常在建立联络关系和/或任命联络经理后确定。
5. Oversee delivery of liaison statements addressed to the IETF. This includes ensuring that liaison statements are delivered to the appropriate destination within the IETF, as well as shepherding the timely creation of responses by the IETF.
5. 监督向IETF提交的联络声明的交付。这包括确保联络声明送达IETF内的适当目的地，以及指导IETF及时创建响应。
6. Work with the liaised organization to ensure that the IETF's liaison statements are appropriately directed and responded to in a timely fashion. To accomplish this, the liaison needs to build a contact network.
6. 与联络组织合作，确保IETF的联络声明得到适当指导并及时响应。为此，联络员需要建立一个联络网。
7. Communicate and coordinate with other IETF liaison managers where the activities of two or more liaised organizations overlap.
7. 当两个或多个联络组织的活动重叠时，与其他IETF联络经理进行沟通和协调。
8. Assist with the preparation of IETF liaison statements based on IETF consensus.
8. 根据IETF共识，协助编制IETF联络声明。
9. From time to time, liaison managers and liaison representatives will have to report to the IETF on the status of the liaison relationship. For this purpose, they will need to keep track of outstanding issues on behalf of the IETF. The frequency of the reports and the recipients of the reports within the IETF will be decided when the liaison relationship is set up and may be changed at any time by an IAB decision. IAB or other parties within the IETF may probe for liaison reports as needed or at regular intervals.
9. 联络经理和联络代表必须不时向IETF报告联络关系的状态。为此，他们需要代表IETF跟踪未决问题。IETF内的报告频率和报告接收人将在建立联络关系时决定，并可随时通过IAB决定进行更改。IAB或IETF内的其他各方可根据需要或定期调查联络报告。
Liaison managers will be involved in activities for which they are not directly responsible, but that might greatly benefit from their expertise. Some of these activities are outlined below.
联络经理将参与他们不直接负责的活动，但这可能会从他们的专业知识中受益匪浅。下文概述了其中一些活动。
Liaison statements and other messages sent to a liaised organization should be based on rough consensus within the IETF or one of its working groups or areas. Though the liaison manager is not responsible for determining consensus, it is important that the liaison manager participate in the process and makes his or her expertise and knowledge available.
发送给联络组织的联络声明和其他信息应基于IETF或其工作组或区域内的大致共识。尽管联络经理不负责确定共识，但重要的是联络经理应参与该过程并提供其专业知识和知识。
How consensus is arrived at may vary according to the circumstances. Some issues are new, and in these cases an open discussion on a mailing list should be undertaken. For some issues, consensus has already been arrived at or the liaison statement is a mere statement of facts (e.g., to inform the liaised organization that an IETF Last Call had started on a document it had previously expressed interest in) and in these cases the liaison statement can be written and sent (such as by a working group chair), possibly involving the liaison manager.
达成共识的方式可能因情况而异。有些问题是新问题，在这些情况下，应就邮件列表进行公开讨论。对于某些问题，已经达成共识，或者联络声明仅仅是一份事实陈述（例如，通知被联络组织IETF上一次通话是针对其先前表示感兴趣的文件开始的），在这些情况下，可以编写并发送联络声明（如由工作组主席），可能涉及到联络经理。
When the IETF receives a liaison statement or other communication from an organization with which it has a liaison relationship that includes a request for a response to the communication, the IETF is committed to providing a timely response. This means that the IETF will respond within the time requested and provide information as accurately as possible. This commitment has been one of the key discussion points in the past, such as within the (g)mpls change process [GMPLS].
当IETF收到与之有联络关系的组织的联络声明或其他通信，包括对通信的响应请求时，IETF承诺提供及时响应。这意味着IETF将在要求的时间内做出响应，并尽可能准确地提供信息。这一承诺在过去一直是关键讨论点之一，例如在（g）mpls变更过程[GMPLS]中。
This commitment does not mean that the IETF will uncritically accept the content in the incoming liaison statement. To the extent that the liaison contains requirements on IETF technology or protocols, they will be taken into consideration based on their technical merit.
这一承诺并不意味着IETF将不加批判地接受即将到来的联络声明中的内容。如果联络中包含IETF技术或协议的要求，则将根据其技术优点予以考虑。
Sometimes the IETF, an IETF area, or an IETF working group receives liaison statements from a liaised organization that are sent to the wrong destination. At other times, the liaison statement is sent to working groups that are not chartered to do the work that the liaison statement addresses. In some cases, it might be the situation that no working group is chartered to do the work.
有时，IETF、IETF区域或IETF工作组收到联络组织发送到错误目的地的联络声明。在其他情况下，联络声明被发送给没有特许从事联络声明所述工作的工作组。在某些情况下，可能是没有特许工作组开展工作。
In such cases, the liaison manager should assist in finding the appropriate recipient within the IETF that might respond to the incoming liaison statement. Sometimes this might require that the intended response is made available for review on one of the IETF mailing lists.
在这种情况下，联络经理应协助在IETF内找到可能对收到的联络声明作出响应的适当接收人。有时，这可能需要在一个IETF邮件列表上提供预期响应以供审查。
Liaised organizations may appoint a person to act as a liaison manager for "their side" of the relationship. This is the person that will speak authoritatively, within the IETF, on the activities performed by the other organization. The other organization needs to make this person known to the IETF. This person might request a slot on a working group agenda to discuss developments and plans of the liaised organization.
被联络的组织可以指定一个人作为关系“他们一方”的联络经理。该人员将在IETF内就其他组织执行的活动进行权威性发言。另一个组织需要让IETF知道此人。此人可能要求在工作组议程上安排一个时段，讨论联络组织的发展和计划。
Opinions expressed by a liaison mangers of other SDOs, other than reports on work within the liaised organization, are given equal weight with opinions expressed by other working group participants. RFC 3356 [RFC3356] describes this in the context of the relationship between the IETF and the ITU-T; however, the same model is applicable to all other organizations with which the IETF has a liaison relationship.
由其他SDO的联络经理发表的意见（关于联络组织内工作的报告除外）与其他工作组参与者发表的意见同等重要。RFC 3356[RFC3356]在IETF和ITU-T之间关系的上下文中描述了这一点；然而，同一模式适用于IETF与之有联络关系的所有其他组织。
The mandates of liaison managers from other organizations are recognized by the IETF to the extent needed to understand the information received from the liaison manager. In all other respects he or she participates in IETF activities under the same conditions and rules as any other IETF participant. It is important that the IETF liaison manager understands the extent to which the peer liaison manager is mandated or delegated to speak on behalf of the peer organization, and to inform the relevant part of the IETF if the peer liaison manager appears to be stepping outside the role or stance given to him or her by the peer organization.
IETF在理解从联络经理处收到的信息所需的范围内，承认来自其他组织的联络经理的授权。在所有其他方面，他或她在与任何其他IETF参与者相同的条件和规则下参与IETF活动。重要的是，IETF联络经理应了解同行联络经理被授权或委托代表同行组织发言的程度，并在同行联络经理似乎超越了同行组织赋予他的角色或立场时通知IETF的相关部分。
IETF liaison managers should work to include the liaison manager from the liaised organization within their contact network, and to understand the positions being communicated by the peer liaison manager.
IETF联络经理应努力将联络组织的联络经理纳入其联络网络，并了解同行联络经理传达的职位。
This document does not specify any protocol or "bits on the wire". However, since interaction with other standards-making organizations often relates to security, the liaison manager can assist with security-related issues, resulting in improved security for Internet protocols.
本文件未规定任何协议或“线路上的位”。然而，由于与其他标准制定组织的互动通常涉及安全问题，联络经理可以协助解决安全相关问题，从而提高互联网协议的安全性。
There are no requests to the IANA herein. Note that the liaison manager very often has to understand and convey questions regarding IETF namespaces managed by IANA.
此处没有对IANA的请求。请注意，联络经理通常必须理解并传达有关IANA管理的IETF名称空间的问题。
This document was developed as part of a conversation regarding the requirements on IETF liaison managers and representatives. Several IAB members have significantly contributed to the document. Also, the document has been improved thanks to suggestions and review from Allison Mankin, Dave Meyer, and Leslie Daigle.
本文件是关于IETF联络经理和代表要求的对话的一部分。IAB的几个成员对该文件做出了重大贡献。此外，由于Allison Mankin、Dave Meyer和Leslie Daigle的建议和审查，该文件得到了改进。
A special thanks to Bernard Aboba, who, based on his experience as a liaison manager, has made many useful comments on the subject matter. Elwyn Davies and Bernard Aboba have both spent time correcting language and grammar.
特别感谢Bernard Aboba，他根据自己作为联络经理的经验，就这一主题发表了许多有益的评论。Elwyn Davies和Bernard Aboba都花时间纠正语言和语法。
Members of the IAB at the time of approval of this document were the following:
在批准本文件时，IAB的成员如下：
Bernard Aboba Loa Andersson Brian Carpenter Leslie Daigle Elwyn Davies Kevin Fall Olaf Kolkman Kurtis Lindqvist David Meyer Dave Oran Eric Rescorla Dave Thaler Lixia Zhang
Bernard Aboba Loa Andersson Brian Carpenter Leslie Daigle Elwyn Davies Kevin Fall Olaf Kolkman Kurtis Lindqvist David Meyer Dave Oran Eric Rescorla Dave Thaler Lixia Zhang
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2418] Bradner, S., "IETF Working Group Guidelines and Procedures", BCP 25, RFC 2418, September 1998.
[RFC2418]Bradner，S.，“IETF工作组指南和程序”，BCP 25，RFC 2418，1998年9月。
[RFC4052] Daigle, L. and Internet Architecture Board, "IAB Processes for Management of IETF Liaison Relationships", BCP 102, RFC 4052, April 2005.
[RFC4052]Daigle，L.和互联网架构委员会，“IETF联络关系管理的IAB流程”，BCP 102，RFC 4052，2005年4月。
[GMPLS] Andersson, L., "MPLS and GMPLS Change Process", Work in Progress, December 2005.
[GMPLS]Andersson，L.，“MPLS和GMPLS变更过程”，正在进行的工作，2005年12月。
[RFC3113] Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin, "3GPP-IETF Standardization Collaboration", RFC 3113, June 2001.
[RFC3113]Rosenbrock，K.，Sanmugam，R.，Bradner，S.，和J.Klensin，“3GPP-IETF标准化协作”，RFC31132001年6月。
[RFC3131] Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S., Flynn, G., Lipford, M., and M. McPheters, "3GPP2-IETF Standardization Collaboration", RFC 3131, June 2001.
[RFC3131]Bradner，S.，Calhoun，P.，Cuschieri，H.，Dennett，S.，Flynn，G.，Lipford，M.，和M.McPheters，“3GPP2-IETF标准化协作”，RFC31312001年6月。
[RFC3356] Fishman, G. and S. Bradner, "Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines", RFC 3356, August 2002.
[RFC3356]Fishman，G.和S.Bradner，“互联网工程任务组和国际电信联盟-电信标准化部门协作指南”，RFC 3356，2002年8月。
[RFC4053] Trowbridge, S., Bradner, S., and F. Baker, "Procedures for Handling Liaison Statements to and from the IETF", BCP 103, RFC 4053, April 2005.
[RFC4053]Trowbridge，S.，Bradner，S.，和F.Baker，“处理进出IETF的联络声明的程序”，BCP 103，RFC 4053，2005年4月。
Editor's Address
编辑地址
Loa Andersson IAB
安徒生律师事务所
EMail: loa@pi.se
EMail: loa@pi.se
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）提供。