Internet Engineering Task Force (IETF) B. Campbell, Ed.
Request for Comments: 7957 Oracle
BCP: 67 A. Cooper
Updates: 5727 Cisco
Category: Best Current Practice B. Leiba
ISSN: 2070-1721 Huawei Technologies
August 2016
Internet Engineering Task Force (IETF) B. Campbell, Ed.
Request for Comments: 7957 Oracle
BCP: 67 A. Cooper
Updates: 5727 Cisco
Category: Best Current Practice B. Leiba
ISSN: 2070-1721 Huawei Technologies
August 2016
DISPATCH-Style Working Groups and the SIP Change Process
派遣式工作组和SIP变更流程
Abstract
摘要
RFC 5727 defined several processes for the former Real-time Applications and Infrastructure (RAI) area. These processes include the evolution of the Session Initiation Protocol (SIP) and related protocols, as well as the operation of the DISPATCH and SIPCORE working groups. This document updates RFC 5727 to allow flexibility for the area and working group structure, while preserving the SIP change processes. It also generalizes the DISPATCH working group processes so that they can be easily adopted by other working groups.
RFC 5727为前实时应用和基础设施（RAI）领域定义了几个过程。这些过程包括会话启动协议（SIP）和相关协议的演变，以及调度和SIPCORE工作组的运作。本文件更新了RFC 5727，以允许区域和工作组结构的灵活性，同时保留SIP变更流程。它还概括了调度工作组流程，以便其他工作组可以轻松采用这些流程。
Status of This Memo
关于下段备忘
This memo documents an Internet Best Current Practice.
本备忘录记录了互联网最佳实践。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关BCP的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7957.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7957.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. DISPATCH-Style Working Groups . . . . . . . . . . . . . . . . 3
3. Decoupling the SIP Change Process from the RAI Area . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Normative References . . . . . . . . . . . . . . . . . . 5
5.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. DISPATCH-Style Working Groups . . . . . . . . . . . . . . . . 3
3. Decoupling the SIP Change Process from the RAI Area . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Normative References . . . . . . . . . . . . . . . . . . 5
5.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
[RFC5727] described processes for evolving and maintaining the Session Initiation Protocol (SIP) [RFC3261] and related technologies in the former Real-time Application and Infrastructure (RAI) area. These processes are collectively known as the "SIP Change Process". While areas do not normally have "charters" per se, RFC 5727 effectively served as a charter for RAI. The language in RFC 5727 was tightly bound to the RAI area and to the DISPATCH and SIPCORE working groups.
[RFC5727]描述了在前实时应用和基础设施（RAI）领域中演进和维护会话发起协议（SIP）[RFC3261]和相关技术的过程。这些过程统称为“SIP变更过程”。虽然这些地区本身通常没有“特许权”，但RFC 5727实际上是RAI的特许权。RFC 5727中的语言与RAI地区以及调度和SIPCORE工作组紧密相连。
In 2015, The RAI area merged with the Applications (APP) area to form the Applications and Real-Time (ART) area. This document updates RFC 5727 to remove its dependency on RAI and its working group structure. The updates in this document do not depend on the names of the new area, or any specific working group. Rather, the authors seek to future-proof the SIP Change Process against future reorganizations.
2015年，RAI区域与应用（APP）区域合并，形成应用和实时（ART）区域。本文件更新了RFC 5727，以消除其对RAI及其工作组结构的依赖性。本文件中的更新不取决于新区域或任何特定工作组的名称。相反，作者试图针对未来的重组对SIP变更过程进行未来证明。
RFC 5727 specified that the DISPATCH working group assesses potential new work for the area, and determines where such work should occur. DISPATCH does not itself take on such new work. The SIPCORE working
RFC 5727规定，调度工作组评估该区域的潜在新工作，并确定此类工作应在何处进行。派遣公司本身并不承担这种新的工作。核心工作
group is responsible for maintenance of SIP. Other historically RAI area working groups develop extensions to SIP that do not change the core protocol, new applications of SIP, and other technologies for interactive communication among humans. This document further generalizes the processes of the DISPATCH working group so that they can be applied to other areas, or to clusters of technologies within an area.
集团负责SIP的维护。其他RAI地区的工作组开发了SIP的扩展，这些扩展不会改变核心协议、SIP的新应用以及其他用于人与人之间交互通信的技术。本文件进一步概括了调度工作组的流程，以便将其应用于其他领域或某个领域内的技术集群。
This document does not change any other aspect of RFC 5727. While areas and working groups may change over time, the rules and procedures for changing SIP and other historically RAI protocols remain the same, until such time that they are updated by future documents.
本文件不改变RFC 5727的任何其他方面。虽然区域和工作组可能会随着时间的推移而改变，但更改SIP和其他RAI协议的规则和程序保持不变，直到这些规则和程序被未来的文件更新为止。
The DISPATCH working group has proven successful at managing new work for the RAI and ART areas. Areas may choose to adopt DISPATCH-like procedures, either for an entire area, or for technology clusters in an area or across areas. A "DISPATCH-Style" working group operates according to procedures similar to those used for DISPATCH.
调度工作组在管理RAI和ART区域的新工程方面取得了成功。各地区可以选择对整个地区或某个地区或跨地区的技术集群采用类似调度的程序。“派遣式”工作组按照与派遣类似的程序运作。
This document is not intended to recommend DISPATCH-style groups for any specific IETF area other than ART. Different areas have different needs, and those needs may change over time. It is up to the community and respective Area Directors to determine if a DISPATCH-style group is appropriate for any given situation.
本文件无意为ART以外的任何特定IETF领域推荐调度样式组。不同地区有不同的需求，这些需求可能会随着时间的推移而变化。由社区和各自的区域主管来确定调度方式组是否适合任何给定情况。
The "DISPATCH-style" includes the following essential elements:
“派送风格”包括以下基本要素：
o The working group evaluates proposals for new work for an area, or for a well-defined technology cluster. It acts as a filter for the area or cluster to determine whether a proposal is a reasonable use of, or addition to, associated technologies. This determination may depend upon established criteria (for example, the SIP Change Process), the experience and expertise of the participants, or a combination of the two.
o 工作组评估某一领域或定义明确的技术集群的新工作提案。它充当区域或集群的过滤器，以确定提案是否合理使用或添加了相关技术。该确定可能取决于既定标准（例如，SIP变更流程）、参与者的经验和专业知识，或两者的组合。
o The DISPATCH-style working group determines an appropriate venue for the work. The venue could be an existing working group. If no appropriate group exists, it may develop a charter for a BoF or a new working group. The group might also recommend that a proposal progress as an AD-sponsored individual draft, or even that a proposal should not be acted upon at the time.
o 派遣风格工作组确定合适的工作地点。地点可以是现有的工作组。如果没有合适的小组，它可以为BoF或新的工作组制定章程。工作组还可能建议将提案作为广告赞助的单独草案进行处理，甚至不应在当时对提案采取行动。
o The DISPATCH-style working group does not complete the proposed work. It may, however, adopt milestones needed to properly dispatch the work. For example, it may produce charter text for a BoF or a new working group, an initial problem statement, or documentation about why certain work was not pursued.
o 派遣式工作组未完成拟定工作。但是，它可以采用适当调度工作所需的里程碑。例如，它可以为BoF或新的工作组生成章程文本、初始问题声明或关于为什么不进行某些工作的文档。
Nothing in this list prevents existing working groups from directly adopting new work that reasonably fits their charters, nor does it prevent new-work proposals from going directly to BoF meetings when appropriate. For borderline cases, the decision whether new work should start in a DISPATCH-style group or elsewhere is made by the responsible Area Directors and chairs. Likewise, in cases where an area has multiple DISPATCH-style groups for different purposes or technology clusters, deciding which group will handle a particular proposal is up to the responsible Area Directors and relevant chairs.
本清单中的任何内容都不妨碍现有工作组直接采用合理符合其章程的新工作，也不妨碍新工作提案在适当时直接提交给BoF会议。对于临界情况，由负责区域的主管和主席决定是否应在调度式小组或其他地方开始新工作。同样，如果一个区域有多个调度类型组用于不同目的或技术集群，则由负责的区域主管和相关主席决定哪个组将处理特定提案。
The charter of a DISPATCH-style group should make that fact clear, either by referencing this document, or by directly describing similar procedures.
派遣风格小组的章程应通过引用本文件或直接描述类似程序来明确这一事实。
This document clarifies that the SIP Change Process is not bound to any particular area or working group structure. All references to the RAI area in RFC 5727 should be interpreted as "the cluster of SIP and closely related application and infrastructure technologies, as well as other technologies designed primarily for interactive communication, historically among humans".
本文件澄清了SIP变更流程不受任何特定领域或工作组结构的约束。RFC 5727中对RAI区域的所有引用应解释为“SIP集群和密切相关的应用和基础设施技术，以及主要用于人类之间交互通信的其他技术”。
While the DISPATCH and SIPCORE working groups are expected to continue in their current capacities, nothing in the SIP Change Process prevents their responsibilities from being assigned to other working groups in the future.
尽管调度和SIPCORE工作组预计将以其当前的能力继续工作，但SIP变更流程中的任何内容都不会阻止其职责在未来分配给其他工作组。
All other aspects of the SIP Change Process are to continue as described in RFC 5727.
如RFC 5727所述，SIP变更过程的所有其他方面将继续进行。
This document discusses the roles and responsibilities of areas and working groups. It does not create new security considerations in the conventional sense.
本文件讨论了区域和工作组的角色和职责。它不会产生传统意义上的新的安全考虑。
However, organizational structures come with their own security considerations. A DISPATCH-style working group has the potential to concentrate the control of work for an area or cluster in the hands of a much smaller set of people than those in the whole area or cluster. This could effectively create bottlenecks or roadblocks for
然而，组织结构有其自身的安全考虑。调度式工作组有可能将某个区域或集群的工作控制权集中在比整个区域或集群的人员少得多的人员手中。这可能会有效地为企业创造瓶颈或障碍
new work in an area or cluster. Likewise, such a concentration could reduce the quality of decisions about new work. Care must be taken to avoid this risk. The best mitigation is active participation in the group by as many people in the area or cluster as possible.
一个区域或集群中的新工作。类似地，这种专注可能会降低新工作决策的质量。必须小心避免这种风险。最好的缓解措施是由该地区或集群中尽可能多的人积极参与团队。
[RFC5727] Peterson, J., Jennings, C., and R. Sparks, "Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area", BCP 67, RFC 5727, DOI 10.17487/RFC5727, March 2010, <http://www.rfc-editor.org/info/rfc5727>.
[RFC5727]Peterson，J.，Jennings，C.，和R.Sparks，“会话启动协议（SIP）和实时应用程序和基础设施领域的变更过程”，BCP 67，RFC 5727，DOI 10.17487/RFC5727，2010年3月<http://www.rfc-editor.org/info/rfc5727>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, DOI 10.17487/RFC3261, June 2002, <http://www.rfc-editor.org/info/rfc3261>.
[RFC3261]Rosenberg，J.，Schulzrinne，H.，Camarillo，G.，Johnston，A.，Peterson，J.，Sparks，R.，Handley，M.，和E.Schooler，“SIP：会话启动协议”，RFC 3261，DOI 10.17487/RFC3261，2002年6月<http://www.rfc-editor.org/info/rfc3261>.
[RFC3427] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J., and B. Rosen, "Change Process for the Session Initiation Protocol (SIP)", RFC 3427, DOI 10.17487/RFC3427, December 2002, <http://www.rfc-editor.org/info/rfc3427>.
[RFC3427]Mankin，A.，Bradner，S.，Mahy，R.，Willis，D.，Ott，J.，和B.Rosen，“会话启动协议（SIP）的变更过程”，RFC 3427，DOI 10.17487/RFC3427，2002年12月<http://www.rfc-editor.org/info/rfc3427>.
Acknowledgements
致谢
The authors would like to thank all the previous authors of the SIP Change Process for their contributions. Jon Peterson, Cullen Jennings, and Robert Sparks authored RFC 5727. That RFC obsoleted [RFC3427], which was in turn written by Allison Mankin, Scott Bradner, Rohan Mahy, Dean Willis, Brian Rosen, and Joerg Ott.
作者要感谢SIP变更流程的所有先前作者的贡献。乔恩·彼得森、卡伦·詹宁斯和罗伯特·斯帕克斯是RFC5727的作者。该RFC淘汰了[RFC3427]，后者由Allison Mankin、Scott Bradner、Rohan Mahy、Dean Willis、Brian Rosen和Joerg Ott依次撰写。
The authors additionally thank the present and past chairs of DISPATCH and SIPCORE, as well as all the participants in the former RAI area since its inception.
作者还感谢DISPATCH和SIPCORE的现任和前任主席，以及前RAI地区自成立以来的所有参与者。
Authors' Addresses
作者地址
Ben Campbell (editor) Oracle
本·坎贝尔（编辑）甲骨文
Email: ben@nostrum.com
Email: ben@nostrum.com
Alissa Cooper Cisco
艾莉莎库珀思科
Email: alcoop@cisco.com
Email: alcoop@cisco.com
Barry Leiba Huawei Technologies
巴里·雷巴华为技术有限公司
Phone: +1 646 827 0648
Email: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/
Phone: +1 646 827 0648
Email: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/