Internet Research Task Force (IRTF) S. Dawkins, Ed.
Request for Comments: 7418 Huawei
Category: Informational December 2014
ISSN: 2070-1721
Internet Research Task Force (IRTF) S. Dawkins, Ed.
Request for Comments: 7418 Huawei
Category: Informational December 2014
ISSN: 2070-1721
An IRTF Primer for IETF Participants
IETF参与者的IRTF入门
Abstract
摘要
This document provides a high-level description of things for Internet Engineering Task Force (IETF) participants to consider when bringing proposals for new research groups (RGs) into the Internet Research Task Force (IRTF). This document emphasizes differences in expectations between the two organizations.
该文件提供了互联网工程任务组（IETF）参与者在将新研究小组（RGS）的建议纳入互联网研究工作组（IRTF）时所要考虑的内容的高级描述。本文件强调了两个组织之间的期望差异。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Research Task Force (IRTF). The IRTF publishes the results of Internet-related research and development activities. These results might not be suitable for deployment. This RFC represents the individual opinion(s) of one or more members of the IRSG Research Group of the Internet Research Task Force (IRTF). Documents approved for publication by the IRSG are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网研究工作组（IRTF）的产品。IRTF发布互联网相关研究和开发活动的结果。这些结果可能不适合部署。本RFC代表互联网研究工作队（IRTF）IRSG研究小组一名或多名成员的个人意见。IRSG批准发布的文件不适用于任何级别的互联网标准；见RFC 5741第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/rfc7418.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7418.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 2
2. The IRTF Is Not the IETF . . . . . . . . . . . . . . . . . . 2
2.1. Research and Engineering . . . . . . . . . . . . . . . . 3
2.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Time Frames . . . . . . . . . . . . . . . . . . . . . . . 3
2.4. Alternatives . . . . . . . . . . . . . . . . . . . . . . 4
2.5. Process . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.6. Charters . . . . . . . . . . . . . . . . . . . . . . . . 4
2.7. Deliverables . . . . . . . . . . . . . . . . . . . . . . 5
2.8. Completion . . . . . . . . . . . . . . . . . . . . . . . 5
3. Now That You Know What Not to Do . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 2
2. The IRTF Is Not the IETF . . . . . . . . . . . . . . . . . . 2
2.1. Research and Engineering . . . . . . . . . . . . . . . . 3
2.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Time Frames . . . . . . . . . . . . . . . . . . . . . . . 3
2.4. Alternatives . . . . . . . . . . . . . . . . . . . . . . 4
2.5. Process . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.6. Charters . . . . . . . . . . . . . . . . . . . . . . . . 4
2.7. Deliverables . . . . . . . . . . . . . . . . . . . . . . 5
2.8. Completion . . . . . . . . . . . . . . . . . . . . . . . 5
3. Now That You Know What Not to Do . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
This document provides a high-level description of things for Internet Engineering Task Force (IETF) participants to consider when bringing proposals for new research groups (RGs) into the Internet Research Task Force (IRTF). This document emphasizes differences in expectations between the two organizations.
该文件提供了互联网工程任务组（IETF）参与者在将新研究小组（RGS）的建议纳入互联网研究工作组（IRTF）时所要考虑的内容的高级描述。本文件强调了两个组织之间的期望差异。
IRTF RG guidelines and procedures are described in BCP 8 [RFC2014], and this document does not change those guidelines and procedures in any way.
IRTF RG指南和程序在BCP 8[RFC2014]中有描述，本文件不会以任何方式更改这些指南和程序。
A number of proposals from experienced IETF participants for new IRTF RGs have encountered problems because the IETF participants were making proposals appropriate for the IETF, but not for the IRTF. [RFC2014] describes the origin of IRTF RGs but doesn't provide much detail about the process, which is intended to be flexible and accommodate new types of RGs. Lacking that detail, experienced IETF participants fall back on what they know, assume that chartering an IRTF RG will be similar to chartering an IETF working group (WG), follow the suggestions in [RFC6771] to gather a group of interested parties, and then follow the suggestions in [RFC5434] to prepare for a successful BOF and eventually, a chartered WG.
有经验的IETF参与者针对新的IRTF RG提出的许多建议都遇到了问题，因为IETF参与者提出的建议适合IETF，但不适合IRTF。[RFC2014]描述了IRTF RGs的起源，但没有提供有关该过程的详细信息，该过程旨在灵活并适应新类型的RGs。缺乏这些细节，经验丰富的IETF参与者只能依靠他们所知道的，假设租用一个IRTF RG类似于租用一个IETF工作组（WG），遵循[RFC6771]中的建议，聚集一组相关方，然后遵循[RFC5434]中的建议，为成功的BOF做准备，并最终，特许工作组。
Both of these documents are excellent references for proposals in the IETF, but their suggestions may result in a proposal that is almost the opposite of what the IRTF Chair is looking for in a proposal for an IRTF RG. The mismatches fall into some consistent categories, and this document lists the ones that come up repeatedly.
这两份文件都是IETF提案的优秀参考文件，但他们的建议可能会导致一份提案，该提案几乎与IRTF主席在IRTF RG提案中所寻求的内容相反。不匹配分为一些一致的类别，本文档列出了重复出现的不匹配。
The target audience of this document is IETF participants bringing proposals to the IRTF.
本文件的目标受众是向IRTF提交提案的IETF参与者。
It's worth noting that the IRTF Chair has substantial autonomy on what RGs are chartered and how they reach that stage. The IRTF Chair at the time of writing is Lars Eggert.
值得注意的是，IRTF主席在特许RG以及RG如何达到该阶段方面拥有很大的自主权。撰写本文时，IRTF主席是拉尔斯·艾格特。
"To me, the fundamental outcome of research is understanding, and the fundamental outcome of engineering is a product." - Fred Baker
“对我来说，研究的基本成果是理解，而工程的基本成果是产品。”-弗雷德·贝克
In some ways, research is about a journey, and engineering is about a destination. If a researcher answers a question in a way that opens another question, that can be success. If an engineer keeps working on a product without finishing it, that is usually a failure.
在某些方面，研究是一次旅行，而工程是一个目的地。如果一个研究者回答一个问题的方式开启了另一个问题，那就是成功。如果一个工程师继续在一个产品上工作而没有完成它，那通常是失败的。
Research can be open-ended, while engineering can come to a stopping point when the result is "good enough" -- good enough to ship.
研究可以是无止境的，而当结果“足够好”——足够好到可以出货时，工程可以停下来。
"If it has to work when you're finished, it wasn't research, it was engineering." - attributed to Dave Clark
“如果它必须在你完成的时候工作，那不是研究，而是工程。”-戴夫·克拉克
IRTF RGs have a scope large enough to interest researchers, attract them to the IRTF, and keep them busy doing significant work. Their charters are therefore usually much broader than IETF WG charters, and RGs often discuss different topics underneath the charter umbrella at different times, based on current research interests in the field.
IRTF RGs的范围足够大，足以引起研究人员的兴趣，吸引他们加入IRTF，并让他们忙于做重要的工作。因此，他们的章程通常比IETF工作组章程要广泛得多，RGs通常根据该领域当前的研究兴趣，在不同的时间讨论章程框架下的不同主题。
IETF WGs are chartered with a limited scope and specific deliverables. If deliverables and milestones are known, the proposal is likely too limited for the IRTF.
IETF工作组具有有限的范围和特定的可交付成果。如果已知可交付成果和里程碑，则对于IRTF而言，提案可能过于有限。
IRTF RGs bring researchers together to work on significant problems. That takes time. The effort required by a RG is likely to take at least three to five years, significantly longer than IETF WGs envision when they are chartered.
IRTF RGs将研究人员聚集在一起研究重大问题。这需要时间。RG所需的工作可能至少需要三到五年的时间，远远超过IETF工作组在获得特许时所设想的时间。
IRTF RGs are encouraged to explore more than one alternative approach to the chartered problem area. There is no expectation that the RG will "come to consensus" on one approach. The RG may publish multiple competing proposals as research produces results.
鼓励IRTF RG探索特许问题区域的多种替代方法。预计RG不会就一种方法“达成共识”。研究产生结果时，RG可能会发布多个相互竞争的提案。
IETF WGs normally use the IETF consensus process (as described in [RFC7282]) to drive interoperable solutions into the market place. That often includes reducing the number of approaches to something manageable for an implementer, preferably one, whether that means starting with an approach the WG participants agree on, or considering alternatives with a view to picking one rather than spending significant effort on alternatives that won't go forward.
IETF工作组通常使用IETF共识流程（如[RFC7282]所述）将互操作解决方案推向市场。这通常包括减少实现者可以管理的方法的数量，最好是减少一种，无论这意味着从工作组参与者同意的方法开始，还是考虑选择一种替代方法，而不是花费大量精力在无法继续的替代方法上。
The IRTF, as an organization, may also charter multiple RGs with somewhat overlapping areas of interest, which the IETF tries very hard to avoid.
IRTF作为一个组织，也可以租用多个RG，其兴趣领域有些重叠，IETF会尽力避免。
All IRTF participants have the obligation to disclose IPR and otherwise follow the IRTF's IPR policies, which closely mirror the IETF's IPR policies; in all other aspects, IRTF RG operation is much less constrained than IETF WG operation.
所有IRTF参与者都有义务披露知识产权，并遵守IRTF的知识产权政策，该政策与IETF的知识产权政策密切相关；在所有其他方面，IRTF RG操作比IETF WG操作的约束要小得多。
Each IRTF RG is permitted (and encouraged) to agree on a way of working together that best supports the specific needs of the group. This freedom allows IRTF RGs to bypass fundamental IETF ways of working, such as the need to reach at least rough consensus, which IRTF RGs need not do. Therefore, the mode of operation of IRTF RGs can also change over time, for example, perhaps becoming more like IETF WG operation as the research the group has been progressing matures.
允许（并鼓励）各IRTF RG商定一种最能支持团队特定需求的合作方式。这种自由允许IRTF RGs绕过基本的IETF工作方式，例如需要达成至少粗略的共识，而IRTF RGs不需要这样做。因此，IRTF RGs的运行模式也会随着时间的推移而改变，例如，随着该小组研究的不断成熟，可能会变得更像IETF WG的运行。
The purpose of charters in the IRTF is to broadly sketch the field of research that a group is interested in pursuing and to serve as an advertisement to other researchers who may be wondering if the group is the right place to participate.
IRTF章程的目的是大致勾勒出一个群体感兴趣的研究领域，并向其他可能想知道该群体是否适合参与的研究人员提供广告。
IETF WG charters tend to be very narrow. They are intended to constrain the work that the working group will be doing, and they may contain considerable text about what the working group will not be working on.
IETF工作组章程往往非常狭窄。它们旨在限制工作组将要做的工作，并且可能包含大量关于工作组将不做的工作的文本。
There is no expectation that IRTF RGs publish RFCs, although many do. Some IRTF research groups produce IRTF-stream RFCs, while others produce Internet-Drafts that form the basis of IETF-stream RFCs, and still others may deliver reports, white papers, academic journal articles, or even carry out relevant high-level discussions that aren't ever published but influence other research. IRTF RGs are successful when they stimulate discussion, produce relevant outputs, and impact the research community.
没有人期望IRTF RGs发布RFC，尽管很多人是这样做的。一些IRTF研究小组制作IRTF流式RFC，而另一些小组制作形成IETF流式RFC基础的互联网草稿，还有一些小组可能发表报告、白皮书、学术期刊文章，甚至进行从未发表过但影响其他研究的相关高层讨论。当IRTF RG激发讨论、产生相关输出并影响研究社区时，它是成功的。
IETF WG deliverables tend to be specific protocol, deployment, and operational specifications, along with problem statements, use cases, requirements, and architectures that inform those specifications. Almost all IETF working groups are chartered to deliver Internet standards, which isn't an option for IRTF RGs.
IETF工作组的可交付成果往往是特定的协议、部署和操作规范，以及为这些规范提供信息的问题陈述、用例、需求和体系结构。几乎所有IETF工作组都被特许提供互联网标准，这不是IRTF RGs的选择。
IRTF RGs may produce the outputs they expected to produce when they were chartered, but it also happens that researchers consider what they've learned and start work on better solutions. This can happen whether or not the research underway has been completed, and the process can continue until the RG itself decides that it is time to conclude or when the IRTF Chair determines that there is no more energy in the group to do research.
IRTF RGS可以产生他们预期的产量，当他们被特许，但也发生，研究人员考虑他们所学到的，并开始工作的更好的解决方案。无论正在进行的研究是否已经完成，这种情况都可能发生，并且这一过程可以继续，直到RG自己决定是时候结束了，或者当IRTF主席确定团队中没有更多的精力进行研究时。
IETF WGs will typically conclude when they meet their chartered milestones, allowing participants to focus on implementation and deployment, although the WG mailing list may remain open for a time.
IETF工作组通常在达到其特许里程碑时结束，允许参与者专注于实施和部署，尽管工作组邮件列表可能会保持开放一段时间。
The current IRTF Chair, Lars Eggert, is fond of saying, "Just act like an IRTF research group for a year, and we'll see if you are one."
现任IRTF主席拉尔斯·艾格特（Lars Eggert）喜欢说：“只要像一个IRTF研究小组一样工作一年，我们就会看看你是不是其中之一。”
There are many ways to "act like an IRTF research group". [RFC4440] contains a number of points to consider when proposing a new RG. Some possibilities include:
“像IRTF研究小组一样行动”有很多方法。[RCFC4040]包含在提出新RG时要考虑的一些要点。一些可能性包括：
1. Identify and recruit a critical mass of researchers who can review and build off each other's work.
1. 确定并招募一批关键的研究人员，他们可以相互回顾和借鉴彼此的研究成果。
2. Identify other venues that may overlap the proposed RG, and understand what value the proposed RG provides beyond what's already underway elsewhere.
2. 确定可能与拟议RG重叠的其他场馆，并了解拟议RG提供的价值超出其他地方已经开展的价值。
3. Hold a workshop to survey work that might set the stage for a RG on questions of interest, perhaps in concert with existing academic events.
3. 举办研讨会，调查可能会为RG就感兴趣的问题进行讨论的工作，可能与现有的学术活动相一致。
4. If the proposed RG expects to have outputs that will ultimately be standardized in the IETF, identify and recruit engineers who can review and provide feedback on intermediate results.
4. 如果提议的RG期望有最终在IETF中标准化的输出，则确定并招募能够审查中间结果并提供反馈的工程师。
But every proposed RG is different, so e-mailing the IRTF Chair to start the conversation is a perfectly reasonable strategy.
但每一个提议的RG都是不同的，因此通过电子邮件发送IRTF主席开始对话是一个完全合理的策略。
This document provides guidance about the IRTF chartering process to IETF participants and has no direct Internet security implications.
本文件为IETF参与者提供有关IRTF包租流程的指导，没有直接的互联网安全影响。
[RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines and Procedures", BCP 8, RFC 2014, October 1996, <http://www.rfc-editor.org/info/rfc2014>.
[RFC2014]Weinrib，A.和J.Postel，“IRTF研究小组指南和程序”，BCP 8，RFC 2014，1996年10月<http://www.rfc-editor.org/info/rfc2014>.
[RFC4440] Floyd, S., Paxson, V., Falk, A., and IAB, "IAB Thoughts on the Role of the Internet Research Task Force (IRTF)", RFC 4440, March 2006, <http://www.rfc-editor.org/info/rfc4440>.
[RFC4440]Floyd，S.，Paxson，V.，Falk，A.，和IAB，“IAB对互联网研究工作队（IRTF）作用的思考”，RFC 44402006年3月<http://www.rfc-editor.org/info/rfc4440>.
[RFC5434] Narten, T., "Considerations for Having a Successful Birds-of-a-Feather (BOF) Session", RFC 5434, February 2009, <http://www.rfc-editor.org/info/rfc5434>.
[RFC5434]Narten，T.，“成功举行羽鸟（BOF）会议的考虑因素”，RFC 5434，2009年2月<http://www.rfc-editor.org/info/rfc5434>.
[RFC6771] Eggert, L. and G. Camarillo, "Considerations for Having a Successful "Bar BOF" Side Meeting", RFC 6771, October 2012, <http://www.rfc-editor.org/info/rfc6771>.
[RFC6771]Eggert，L.和G.Camarillo，“成功召开“Bar BOF”边会的考虑因素”，RFC 67712012年10月<http://www.rfc-editor.org/info/rfc6771>.
[RFC7282] Resnick, P., "On Consensus and Humming in the IETF", RFC 7282, June 2014, <http://www.rfc-editor.org/info/rfc7282>.
[RFC7282]Resnick，P.，“关于IETF中的共识和嗡嗡声”，RFC 7282，2014年6月<http://www.rfc-editor.org/info/rfc7282>.
Acknowledgements
致谢
Thanks go to Lars Eggert, who became IRTF Chair in 2011 and has been carrying this information around in his head ever since. Lars also provided helpful comments on early versions of this document.
感谢Lars Eggert，他于2011年成为IRTF主席，从那时起，他就一直在脑子里想着这些信息。拉尔斯还就本文件的早期版本提供了有益的意见。
Thanks especially to Fred Baker for sharing thoughts about the motivations of research and engineering that resulted in a complete rewrite of Section 2.1.
特别感谢Fred Baker分享了关于研究和工程动机的想法，这导致了第2.1节的完全重写。
Thanks also to Scott Brim, Kevin Fall, Eliot Lear, David Meyer, and Stephen Farrell for providing helpful review comments, and to Denis Ovsienko for careful proofreading.
还要感谢Scott Brim、Kevin Fall、Eliot Lear、David Meyer和Stephen Farrell提供了有用的评论，并感谢Denis Ovsienko仔细校对。
Author's Address
作者地址
Spencer Dawkins (editor) Huawei Technologies
斯宾塞·道金斯（编辑）华为技术
EMail: spencerdawkins.ietf@gmail.com
EMail: spencerdawkins.ietf@gmail.com