Network Working Group                                     L. Daigle, Ed.
Request for Comments: 4052                   Internet Architecture Board
BCP: 102                                                      April 2005
Category: Best Current Practice
        
Network Working Group                                     L. Daigle, Ed.
Request for Comments: 4052                   Internet Architecture Board
BCP: 102                                                      April 2005
Category: Best Current Practice
        

IAB Processes for Management of IETF Liaison Relationships

IETF联络关系管理的IAB流程

Status of This Memo

关于下段备忘

This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

本文件规定了互联网社区的最佳现行做法,并要求进行讨论和提出改进建议。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2005).

版权所有(C)互联网协会(2005年)。

Abstract

摘要

This document discusses the procedures used by the IAB to establish and maintain liaison relationships between the IETF and other Standards Development Organizations (SDOs), consortia and industry fora. This document also discusses the appointment and responsibilities of IETF liaison managers and representatives, and the expectations of the IAB for organizations with whom liaison relationships are established.

本文件讨论了IAB用于建立和维护IETF与其他标准开发组织(SDO)、联盟和行业论坛之间联络关系的程序。本文件还讨论了IETF联络经理和代表的任命和职责,以及IAB对与之建立联络关系的组织的期望。

Table of Contents

目录

   1. Liaison Relationships and Personnel .............................2
   2. Aspects of Liaisons and Liaison Management ......................3
      2.1. Liaison Relationships ......................................3
      2.2. Liaison Manager ............................................3
      2.3. Liaison Representatives ....................................4
      2.4. Liaison Communications .....................................4
   3. Summary of IETF Liaison Manager Responsibilities ................5
   4. Approval and Transmission of Liaison Statements .................6
   5. Security Considerations .........................................6
   6. Acknowledgements ................................................7
   7. References ......................................................8
      7.1. Normative References .......................................8
      7.2. Informative References .....................................8
        
   1. Liaison Relationships and Personnel .............................2
   2. Aspects of Liaisons and Liaison Management ......................3
      2.1. Liaison Relationships ......................................3
      2.2. Liaison Manager ............................................3
      2.3. Liaison Representatives ....................................4
      2.4. Liaison Communications .....................................4
   3. Summary of IETF Liaison Manager Responsibilities ................5
   4. Approval and Transmission of Liaison Statements .................6
   5. Security Considerations .........................................6
   6. Acknowledgements ................................................7
   7. References ......................................................8
      7.1. Normative References .......................................8
      7.2. Informative References .....................................8
        
1. Liaison Relationships and Personnel
1. 联络关系和人员

The IETF, as an organization, has the need to engage in direct communication or joint endeavors with various other formal organizations. For example, the IETF is one of several Standards Development Organizations, or SDOs, and all SDOs including the IETF find it increasingly necessary to communicate and coordinate their activities involving Internet-related technologies. This is useful in order to avoid overlap in work efforts and to manage interactions between their groups. In cases where the mutual effort to communicate and coordinate activities is formalized, these relationships are generically referred to as "liaison relationships".

IETF作为一个组织,需要与其他各种正式组织进行直接沟通或共同努力。例如,IETF是多个标准开发组织(SDO)之一,包括IETF在内的所有SDO发现越来越有必要沟通和协调其涉及互联网相关技术的活动。这对于避免工作重叠和管理团队之间的交互非常有用。在沟通和协调活动的共同努力正式化的情况下,这些关系一般称为“联络关系”。

In such cases, a person from the IETF is designated to manage a given liaison relationship; that person is generally called the "IETF liaison manager" to the other organization. When the liaison relationship is expected to encompass a complex or broad range of activities, more people may be designated to undertake some portions of the communications, coordinated by the liaison manager. Often, the other organization will similarly designate their own liaison manager to the IETF.

在这种情况下,IETF指定一名人员管理给定的联络关系;该人员通常被称为其他组织的“IETF联络经理”。当联络关系预计包含复杂或广泛的活动时,可能会指定更多的人在联络经理的协调下进行部分沟通。通常,其他组织也会同样指定自己的联络经理加入IETF。

This document is chiefly concerned with:

本文件主要涉及:

o the establishment and maintenance of liaison relationships, and

o 建立和维持联络关系,以及

o the appointment and responsibilities of IETF liaison managers and representatives.

o IETF联络经理和代表的任命和职责。

The management of other organizations' liaison managers to the IETF, whether or not in the context of a liaison relationship, is outside the scope of this document.

其他组织向IETF的联络经理的管理,无论是否在联络关系中,均不在本文件范围内。

The IETF has chartered the Internet Architecture Board to manage liaison relationships. Consistent with its charter [2], the IAB acts as representative of the interests of the IETF and the Internet Society in technical liaison relationships with other organizations concerned with standards and other technical and organizational issues relevant to the worldwide Internet. Liaison relationships are kept as informal as possible and must be of demonstrable value to the IETF's technical mandate. Individual participants of the IETF are appointed as liaison managers or representatives to other organizations by the IAB.

IETF已授权互联网架构委员会管理联络关系。根据其章程[2],IAB代表IETF和互联网协会的利益,与涉及标准和其他与全球互联网相关的技术和组织问题的其他组织建立技术联络关系。联络关系尽可能非正式,必须对IETF的技术授权具有明显的价值。IETF的个人参与者由IAB任命为联络经理或其他组织的代表。

In general, a liaison relationship is most valuable when there are areas of technical development of mutual interest. For the most part, SDOs would rather leverage existing work done by other organizations than recreate it themselves (and would like the same done with respect to their own work). Establishing a liaison relationship can provide the framework for ongoing communications to

一般来说,当存在共同感兴趣的技术开发领域时,联络关系最有价值。在大多数情况下,SDO宁愿利用其他组织完成的现有工作,也不愿自己重新创建(并且希望自己的工作也能完成)。建立联络关系可以为与客户的持续沟通提供框架

o prevent inadvertent duplication of effort, without obstructing either organization from pursuing its own mandate;

o 在不妨碍任何一个组织执行其任务的情况下,防止工作的无意重复;

o provide authoritative information of one organization's dependencies on the other's work.

o 提供一个组织对另一个组织工作的依赖性的权威信息。

2. Aspects of Liaisons and Liaison Management
2. 联络和联络管理方面
2.1. Liaison Relationships
2.1. 联络关系

A liaison relationship is set up when it is mutually agreeable and needed for some specific purpose, in the view of the other organization, the IAB, and the IETF participants conducting the work. There is no set process or form for this; the IETF participants and the peer organization approach the IAB, and after discussion come to an agreement to form the relationship. In some cases, the intended scope and guidelines for the collaboration are documented specifically (e.g., see [3], [4], and [5]).

在其他组织、IAB和执行工作的IETF参与者看来,如果双方同意并且出于某些特定目的需要,则建立联络关系。这方面没有固定的流程或形式;IETF参与者和同行组织接近IAB,并在讨论后达成协议以形成关系。在某些情况下,合作的预期范围和指南会被明确记录(例如,见[3]、[4]和[5])。

In setting up the relationship, the IAB expects that there will be a mutual exchange of views and discussion of the best approach for undertaking new standardization work items. Any work items resulting for the IETF will be undertaken in the usual IETF procedures, defined in [1]. The peer organization often has different organizational structure and procedures than the IETF, which will require some flexibility on the part of both organizations to accommodate. The IAB expects that each organization will use the relationship carefully, allowing time for the processes it requests to occur in the other organization, and will not make unreasonable demands.

在建立关系的过程中,IAB希望双方就开展新的标准化工作项目的最佳方法进行意见交流和讨论。IETF产生的任何工作项将按照[1]中定义的通常IETF程序进行。对等组织通常具有与IETF不同的组织结构和程序,这需要两个组织都有一定的灵活性来适应。IAB希望每个组织都能谨慎使用这种关系,为其请求的过程在另一个组织中发生留出时间,并且不会提出不合理的要求。

2.2. Liaison Manager
2.2. 外联部经理

As described above, most work on mutually interesting topics will be carried out in the usual way within the IETF and the peer organization. Therefore, most communications will be informal in nature (for example, Working Group (WG) or mailing list discussions).

如上所述,在IETF和对等组织内,大多数关于共同感兴趣主题的工作将以通常的方式进行。因此,大多数通信都是非正式的(例如,工作组(WG)或邮件列表讨论)。

An important function of the liaison manager is to ensure that communication is maintained, productive, and timely. He or she may use any applicable businesslike approach, from private to public communications, and bring in other parties as needed. If a

联络经理的一项重要职能是确保保持沟通、高效和及时。他或她可以使用任何适用的商业方法,从私人通信到公共通信,并根据需要引入其他方。如果

communication from a peer organization is addressed to an inappropriate party, such as being sent to the WG but not copying the Area Director (AD) or being sent to the wrong WG, the liaison manager will help redirect or otherwise augment the communication.

来自同级组织的通信发送给不适当的一方,例如发送给工作组但未抄送区域主管(AD)或发送给错误的工作组,联络经理将帮助重新定向或以其他方式增加通信。

IETF liaison managers should also communicate and coordinate with other liaison managers where concerned technical activities overlap.

当相关技术活动重叠时,IETF联络经理还应与其他联络经理进行沟通和协调。

Since the IAB is ultimately responsible for liaison relationships, anyone who has a problem with a relationship (whether an IETF participant or a person from the peer organization) should first consult the IAB's designated liaison manager, and if that does not result in a satisfactory outcome, the IAB itself.

由于IAB对联络关系负有最终责任,任何与联络关系有问题的人(无论是IETF参与者还是同行组织的人员)都应首先咨询IAB指定的联络经理,如果这不能产生令人满意的结果,则应咨询IAB本身。

2.3. Liaison Representatives
2.3. 联络代表

The liaison manager is, specifically, a representative of the IETF for the purpose of managing the liaison relationship. There may be occasion to identify other representatives for the same relationship. For example, if the area of mutual work is extensive, it might be appropriate to name several people as liaison representatives to different parts of the other organization. Or, it might be appropriate to name a liaison representative to attend a particular meeting.

具体而言,联络经理是IETF的代表,负责管理联络关系。可能有机会为同一关系确定其他代表。例如,如果共同工作的领域很广,那么可以指定几个人作为其他组织不同部门的联络代表。或者,指定一名联络代表出席特定会议可能是适当的。

These other liaison representatives are selected by the IAB and work in conjunction (and close communication) with the liaison manager. In some cases, this may also require communication and coordination with other liaison managers or representatives where concerned technical activities overlap. The specific responsibilities of the liaison representative will be identified at the time of appointment.

这些其他联络代表由IAB挑选,并与联络经理共同工作(并密切沟通)。在某些情况下,如果相关技术活动重叠,还可能需要与其他联络经理或代表进行沟通和协调。联络代表的具体职责将在任命时确定。

2.4. Liaison Communications
2.4. 联络通信

Communications between organizations use a variety of formal and informal channels. The stated preference of the IETF, which is largely an informal organization, is to use informal channels, as these have historically worked well to expedite matters. In some cases, however, a more formal communication is appropriate, either as an adjunct to the informal channel or in its place. In the case of formal communications, the established procedures of many organizations use a form known as a "liaison statement". Procedures for sending, managing, and responding to liaison statements are discussed in [6].

组织之间的沟通使用各种正式和非正式渠道。IETF基本上是一个非正式组织,其公开的偏好是使用非正式渠道,因为这些渠道在历史上很好地促进了事情的发展。然而,在某些情况下,更正式的沟通是合适的,要么作为非正式渠道的附属品,要么取而代之。就正式来文而言,许多组织的既定程序使用一种称为“联络声明”的形式。[6]讨论了发送、管理和回复联络声明的程序。

3. Summary of IETF Liaison Manager Responsibilities
3. IETF联络经理职责总结

While the requirements will certainly vary depending on the nature of the peer organization and the type of joint work being undertaken, the general expectations of a liaison manager appointed by the IAB are as follows:

虽然要求肯定会因同行组织的性质和正在进行的联合工作类型而有所不同,但IAB任命的联络经理的一般期望如下:

o Attend relevant meetings of the peer organization as needed and report back to the appropriate IETF organization any material updates.

o 根据需要参加同行组织的相关会议,并向相应的IETF组织报告任何材料更新。

o Carry any messages from the IETF to the peer organization, when specifically instructed. Generally, these communications "represent the IETF", and therefore due care and consensus must be applied in their construction.

o 当特别指示时,将IETF中的任何消息传送给对等组织。一般来说,这些通信“代表IETF”,因此在其构建过程中必须谨慎行事并达成共识。

o Prepare occasional updates. The target of these updates (e.g., the IAB, an AD, a WG) will generally be identified upon appointment.

o 准备偶尔的更新。这些更新的目标(例如,IAB、广告、工作组)通常在任命时确定。

o Oversee delivery of liaison statements addressed to the IETF, ensuring that they reach the appropriate destination within the IETF, and ensure that relevant responses from the IETF are created and sent in a timely fashion.

o 监督向IETF提交的联络声明的交付,确保其到达IETF内的适当目的地,并确保及时创建和发送IETF的相关回复。

o Work with the other organization to ensure that the IETF's liaison statements are appropriately directed and responded to in a timely fashion.

o 与其他组织合作,确保IETF的联络声明得到适当指导并及时响应。

o Communicate and coordinate with other IETF liaison managers and representatives where concerned technical activities overlap.

o 在相关技术活动重叠的情况下,与其他IETF联络经理和代表进行沟通和协调。

4. Approval and Transmission of Liaison Statements
4. 批准和传送联络声明

It is important that appropriate leadership review be made of proposed IETF liaison statements and that those writing such statements, who claim to be speaking on behalf of IETF, are truly representing IETF views.

重要的是,要对提议的IETF联络声明进行适当的领导审查,并确保那些声称代表IETF发言的撰写此类声明的人真正代表了IETF的观点。

All outgoing liaison statements will be copied to IETF Secretariat using procedures defined in [6] or its successors.

所有发出的联络声明将使用[6]或其后续文件中规定的程序复制给IETF秘书处。

For a liaison statement generated on behalf of an IETF WG, the WG chair(s) must create a statement based on appropriate discussions within the WG to ensure working group consensus for the position(s) presented. The chair(s) must have generated or must agree with the sending of the liaison statement, and must advise the AD(s) that the liaison statement has been sent by copying the appropriate ADs on the message.

对于代表IETF工作组生成的联络声明,工作组主席必须根据工作组内的适当讨论创建一份声明,以确保工作组就所提出的立场达成共识。主席必须已经生成或同意发送联络声明,并且必须通过复制信息上的适当广告告知广告,联络声明已经发送。

For a liaison statement generated on behalf of an IETF Area, the AD(s) must have generated or must agree with the sending of the liaison statement. If the liaison statement is not sent by the ADs, then their agreement must be obtained in advance and confirmed by copying the ADs on the message.

对于代表IETF区域生成的联络声明,AD必须已经生成或同意发送联络声明。如果联络声明不是由ADs发送的,则必须事先获得他们的同意,并通过复制邮件上的ADs进行确认。

For a liaison statement generated on behalf of the IETF as a whole, the IETF Chair must have generated or must agree with the sending of the liaison statement. If the liaison statement is not sent by the IETF Chair, then his or her agreement must be obtained in advance and confirmed by copying the IETF Chair on the message.

对于代表整个IETF生成的联络声明,IETF主席必须已经生成或同意发送联络声明。如果联络声明不是由IETF主席发送的,则必须事先获得其同意,并通过复制信息上的IETF主席来确认。

For a liaison statement generated by the IAB, the IAB Chair must have generated or must agree with the sending of the liaison statement. If the liaison statement is not sent by the IAB Chair, then his or her agreement must be obtained in advance and confirmed by copying the IAB Chair on the message.

对于IAB生成的联络声明,IAB主席必须已经生成或同意发送联络声明。如果联络声明不是由IAB主席发送的,则必须事先获得其同意,并通过在邮件上复制IAB主席来确认。

In cases where prior agreement was not obtained as outlined above, and the designated authority (AD, IETF Chair, or IAB Chair) in fact does not agree with the message, the designated authority will work with the liaison manager to follow up as appropriate, including emitting a revised liaison statement if necessary. Clearly, this is a situation best avoided by assuring appropriate agreement in advance of sending the liaison message.

如果未获得上述事先协议,且指定机构(AD、IETF主席或IAB主席)事实上不同意该信息,指定机构将与联络经理合作,酌情跟进,包括在必要时发布修订后的联络声明。显然,最好通过在发送联络信息之前确保达成适当协议来避免这种情况。

5. Security Considerations
5. 安全考虑

The security of the Internet is not threatened by these procedures.

互联网的安全不受这些程序的威胁。

6. Acknowledgements
6. 致谢

This document was developed as part of a conversation regarding the management of [6], and the authors of that document contributed significantly to it. Also, this version of the document has been improved over its predecessor by several suggestions from Stephen J. Trowbridge, Peter Saint-Andre, Michael Patton, Bert Wijnen, Fred Baker, Scott Bradner, Scott Brim, Avri Doria, Allison Mankin, Thomas Narten, Russ Housley and Dan Romasanu.

本文件是作为[6]管理对话的一部分编写的,该文件的作者对此做出了重大贡献。此外,Stephen J.Trowbridge、Peter Saint Andre、Michael Patton、Bert Wijnen、Fred Baker、Scott Bradner、Scott Brim、Avri Doria、Allison Mankin、Thomas Narten、Russ Housley和Dan Romasanu的几项建议也对本文件的版本进行了改进。

Members of the IAB at the time of approval of this document were:

在批准本文件时,IAB的成员为:

Bernard Aboba Harald Alvestrand (IETF chair) Rob Austein Leslie Daigle (IAB chair) Patrik Faltstrom Sally Floyd Jun-ichiro Itojun Hagino Mark Handley Bob Hinden Geoff Huston (IAB Executive Director) Eric Rescorla Pete Resnick Jonathan Rosenberg

Bernard Aboba Harald Alvestrand(IETF主席)Rob Austein Leslie Daigle(IAB主席)Patrik Faltstrom Sally Floyd Jun ichiro Itojun Hagino Mark Handley Bob Hinden Geoff Huston(IAB执行董事)Eric Rescorla Pete Resnick Jonathan Rosenberg

7. References
7. 工具书类
7.1. Normative References
7.1. 规范性引用文件

[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 09, RFC 2026, October 1996.

[1] Bradner,S.,“互联网标准过程——第3版”,BCP 09,RFC 2026,1996年10月。

[2] Internet Architecture Board and B. Carpenter, "Charter of the Internet Architecture Board (IAB)", BCP 39, RFC 2850, May 2000.

[2] 互联网架构委员会和B.Carpenter,“互联网架构委员会(IAB)章程”,BCP 39,RFC 2850,2000年5月。

7.2. Informative References
7.2. 资料性引用

[3] Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin, "3GPP-IETF Standardization Collaboration", RFC 3113, June 2001.

[3] Rosenbrock,K.,Sanmugam,R.,Bradner,S.,和J.Klesin,“3GPP-IETF标准化协作”,RFC31132001年6月。

[4] Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S., Flynn, G., Lipford, M., and M. McPheters, "3GPP2-IETF Standardization Collaboration", RFC 3131, June 2001.

[4] Bradner,S.,Calhoun,P.,Cuschieri,H.,Dennett,S.,Flynn,G.,Lipford,M.,和M.McPheters,“3GPP2-IETF标准化协作”,RFC31312001年6月。

[5] Fishman, G. and S. Bradner, "Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines", RFC 3356, August 2002.

[5] Fishman,G.和S.Bradner,“互联网工程工作队和国际电信联盟-电信标准化部门协作指南”,RFC 3356,2002年8月。

[6] Trowbridge, S., Bradner, S., and F. Baker, "Procedure for Handling Liaison Statements Between Standards Bodies", June 2004.

[6] Trowbridge,S.,Bradner,S.,和F.Baker,“处理标准机构间联络声明的程序”,2004年6月。

Authors' Addresses

作者地址

Leslie Daigle Editor

莱斯利·戴格尔编辑

Internet Architecture Board IAB

互联网架构委员会

   EMail: iab@iab.org
        
   EMail: iab@iab.org
        

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编辑功能的资金目前由互联网协会提供。