Network Working Group J. Halpern, Ed.
Request for Comments: 5377 Self
Category: Informational November 2008
Network Working Group J. Halpern, Ed.
Request for Comments: 5377 Self
Category: Informational November 2008
Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
就IETF文件中授予的权利向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) 2008 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2008 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)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Abstract
摘要
Contributors grant intellectual property rights to the IETF. The IETF Trust holds and manages those rights on behalf of the IETF. The Trustees of the IETF Trust are responsible for that management. This management includes granting the licenses to copy, implement, and otherwise use IETF Contributions, among them Internet-Drafts and RFCs. The Trustees of the IETF Trust accepts direction from the IETF regarding the rights to be granted. This document describes the desires of the IETF regarding outbound rights to be granted in IETF Contributions.
贡献者向IETF授予知识产权。IETF信托基金代表IETF持有和管理这些权利。IETF信托的受托人负责该管理。这种管理包括授予复制、实施和以其他方式使用IETF贡献的许可，其中包括互联网草稿和RFC。IETF信托的受托人接受IETF关于授予权利的指示。本文件描述了IETF关于在IETF贡献中授予出站权利的愿望。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Purpose in Granting Rights . . . . . . . . . . . . . . . . . . 2
3. Powers and Authority . . . . . . . . . . . . . . . . . . . . . 3
4. Recommended Grants of Right to Copy . . . . . . . . . . . . . . 4
4.1. Rights Granted for Reproduction of RFCs . . . . . . . . . . 5
4.2. Rights Granted for Quoting from IETF Contributions . . . . 5
4.3. Rights Granted for Implementing Based on IETF
Contributions . . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Rights Granted for Use of Text from IETF Contributions . . 6
4.5. Additional Licenses for IETF Contributions . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . . 7
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Purpose in Granting Rights . . . . . . . . . . . . . . . . . . 2
3. Powers and Authority . . . . . . . . . . . . . . . . . . . . . 3
4. Recommended Grants of Right to Copy . . . . . . . . . . . . . . 4
4.1. Rights Granted for Reproduction of RFCs . . . . . . . . . . 5
4.2. Rights Granted for Quoting from IETF Contributions . . . . 5
4.3. Rights Granted for Implementing Based on IETF
Contributions . . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Rights Granted for Use of Text from IETF Contributions . . 6
4.5. Additional Licenses for IETF Contributions . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Under the current operational and administrative structures, IETF intellectual property rights are vested in the IETF Trust administered by a board of trustees made up of the members of the IAOC [RFC4371]. This includes the right to make use of IETF Contributions, as granted by Contributors under the rules laid out in [RFC5378]. The Trustees of the IETF Trust are therefore responsible for defining the rights to copy granted by the IETF to people who wish to make use of the material in these documents.
在当前的运营和管理结构下，IETF知识产权属于IETF信托，由IAOC成员组成的董事会管理[RFC4371]。这包括根据[RFC5378]中规定的规则由贡献者授予的使用IETF贡献的权利。因此，IETF信托的受托人负责定义IETF授予希望使用这些文件中材料的人的复制权。
For consistency and clarity, this document uses the same terminology laid out in [RFC5378] and uses the same meanings as defined in that document.
为保持一致性和清晰性，本文件使用了[RFC5378]中列出的相同术语，并使用了该文件中定义的相同含义。
The IETF Trust, by way of its Trustees, has indicated, as is consistent with the IETF structure, that it will respect the wishes of the IETF in regard to what these granted rights ought to be. It is therefore the IETF's responsibility to articulate those wishes. This document represents the wishes of the IETF regarding the rights granted to all users in regard to IETF Contributions, until it is superseded.
IETF信托通过其受托人表示，与IETF结构一致，它将尊重IETF关于这些授予权利的意愿。因此，IETF有责任阐明这些愿望。本文件代表IETF关于授予所有用户IETF贡献相关权利的愿望，直至其被取代。
In providing a description of the wishes of the IETF with regard to rights granted in RFCs, it is helpful to keep in mind the purpose of granting such rights.
在描述IETF对RFC中授予的权利的意愿时，应牢记授予此类权利的目的。
The mission of the IETF is to produce documents that make the Internet work better (see [RFC3935] for more details). These documents, when completed, are published as RFCs.
IETF的任务是生成使互联网更好地工作的文档（有关更多详细信息，请参见[RFC3935]）。这些文件完成后将作为RFC发布。
An important subclass of RFCs is standards describing protocols; for these, the primary value to the Internet is the ability of implementors to build solutions (products, software, etc.) that interoperate using these standards. Hence, the IETF has a strong interest in seeing accurate, interoperable implementations of the material the IETF publishes. The IETF Trust grants rights to copy to people to make use of the text in the RFCs in order to encourage accurate and interoperable implementations.
RFCs的一个重要子类是描述协议的标准；对于这些，互联网的主要价值在于实施者能够构建使用这些标准进行互操作的解决方案（产品、软件等）。因此，IETF非常希望看到IETF发布的材料的准确、可互操作的实现。IETF信托基金授予人们使用RFC中的文本进行复制的权利，以鼓励准确和可互操作的实现。
As early implementations from Internet-Drafts make use of descriptions in those Internet-Drafts, similar desires apply to Internet-Drafts.
由于Internet草稿的早期实现使用了这些Internet草稿中的描述，类似的愿望也适用于Internet草稿。
Similar considerations also apply to non-standard, non-protocol documents such as BCP (Best Current Practice) and Informational documents; in this document, we recommend a common approach to the issue of right-to-use licenses for all IETF documents.
类似的考虑也适用于非标准、非协议文件，如BCP（最佳实践）和信息性文件；在本文件中，我们建议为所有IETF文件颁发使用权许可证的通用方法。
Previous documents regarding rights in IETF documents have included in the RFC text specific text to be used to achieve the stated goals. This has proved problematic. When problems are found with such text, even when the problem is not a change in intent, it is necessary to revise the RFC to fix the problem. At best, this delays fixing legal issues that need prompt attention. As such, this document describes the IETF desires to the Trustees of the IETF Trust, but does not provide the specific legal wording to address the goals. The selection, and updating as necessary, of legal wording is left to the Trustees of the IETF Trust. Appeals of the actions of the Trustees of the IETF Trust are governed by other documents. As the Trustees are the members of the IAOC, the appeals procedure documented in BCP 101 (currently [RFC4371]) is applicable.
先前关于IETF文件中权利的文件已包含在RFC文本中，用于实现所述目标的特定文本。事实证明，这是有问题的。当发现此类文本存在问题时，即使问题不是意图变更，也有必要修改RFC以解决问题。充其量，这会推迟解决需要立即关注的法律问题。因此，本文件向IETF信托的受托人描述了IETF的愿望，但未提供具体的法律措辞来实现这些目标。法律措辞的选择和必要时的更新由IETF信托的受托人负责。IETF信托受托人的诉讼上诉受其他文件管辖。由于受托人是IAOC的成员，BCP 101（目前为[RFC4371]）中记录的上诉程序适用。
As described in the introduction, and formally specified in [RFC5378], the legal authority for determining and granting users rights to copy material in RFCs and other IETF Contributions rests with the Trustees for the IETF Trust, which is made up of the members of the IAOC, as described in [RFC4071] and [RFC4371]. This document provides guidance to that body, based on the rough consensus of the IETF. The Trustees of the IETF Trust have the authority and responsibility to determine the exact text insertions (or other mechanisms), if any, needed in Internet-Drafts, RFCs, and all IETF
如引言所述，并在[RFC5378]中正式规定，确定和授予用户在RFC和其他IETF贡献中复制材料的权利的法律权威在于IETF信托的受托人，该信托由IAOC的成员组成，如[RFC4071]和[RFC4371]所述。本文件根据IETF的大致共识，为该机构提供指导。IETF信托的受托人有权和责任确定互联网草案、RFC和所有IETF中所需的确切文本插入（或其他机制，如有）
Contributions to meet these goals. The IETF Trust License Policy is available from http://trustee.ietf.org/license-info.
为实现这些目标作出的贡献。IETF信任许可证策略可从http://trustee.ietf.org/license-info.
The rough consensus described in this document reflects the agreement of the IETF as of the IETF Last Call, and the Trustees of the IETF Trust are to begin drafting license text and other materials to act on these instructions upon IESG approval of this document for RFC publication. Changes to the IETF documentation, and document policies themselves, take effect as determined by the Trustees of the IETF Trust.
本文件中描述的大致共识反映了IETF在IETF最后一次呼叫时的一致意见，IETF信托的受托人将在IESG批准本文件用于RFC发布后开始起草许可文本和其他材料，以按照这些指示行事。IETF文件和文件政策本身的变更将根据IETF信托受托人的决定生效。
This document does not specify what rights the IETF Trust receives from others in IETF Contributions. That is left to another document ([RFC5378]). While care has been taken by the working group in developing this document, and care will be taken by the Trustees of the IETF Trust, to see that sufficient rights are granted to the IETF Trust in IETF Contributions, it is also the case that the Trust can not grant rights it has not or does not receive, and it is expected that policies will be in line with that fact. Similarly, the rights granted for pre-existing documents can not be expanded unless the holders of rights in those Contributions choose to grant expanded rights. Nonetheless, to the degree it can, and without embarking on a massive effort, it is desirable if similar rights to those described below can be granted in older RFCs.
本文件未规定IETF信托从其他人处获得的IETF贡献的权利。这将留给另一个文档（[RFC5378]）。虽然工作组在编制本文件时已谨慎行事，IETF信托的受托人也将谨慎行事，以确保IETF信托在IETF贡献方面获得足够的权利，但信托也不能授予其未获得或未获得的权利，预计政策将符合这一事实。同样，除非这些捐款的权利持有人选择授予扩大的权利，否则不能扩大对现有文件授予的权利。尽管如此，在不进行大规模努力的情况下，尽可能在较旧的RFC中授予与下文所述类似的权利是可取的。
The IETF grants rights to copy and modify parts of IETF Contributions in order to meet the objectives described earlier. As such, different circumstances and different parts of documents may need different grants. This section contains subsections for each such different grant that is currently envisioned. Each section is intended to describe a particular usage, to describe how that usage is recognizable, and to provide guidance to the Trustees of the IETF Trust as to what rights the IETF would like to see granted in that circumstance and what limitations should be put on such granting.
IETF授予复制和修改IETF部分贡献的权利，以实现上述目标。因此，不同的情况和文件的不同部分可能需要不同的补助金。本节包含当前设想的每种不同补助金的小节。每一节旨在描述一种特定的用法，描述该用法如何被识别，并向IETF信托的受托人提供指导，说明IETF希望在这种情况下授予哪些权利，以及对此类授予应施加哪些限制。
These recommendations for outgoing rights are structured around the assumptions documented in [RFC5378]. Thus, this document is about granting rights derived from those granted to the IETF Trust. The recommendations below are how those granted rights should in turn be passed on to others using IETF documents in ways and for purposes that fit with the goals of the IETF. This discussion is also separate from discussion of the rights the IETF itself requires in documents to do its job, as those are not "outbound" rights. It is expected that the rights granted to the IETF will be a superset of those copying rights we wish to grant to others.
这些关于外发权利的建议是围绕[RFC5378]中记录的假设构建的。因此，本文件是关于授予IETF信托的权利。下面的建议是如何将这些授予的权利以符合IETF目标的方式和目的传递给使用IETF文件的其他人。这一讨论也与IETF本身在文件中要求的权利的讨论分开，因为这些权利不是“出站”权利。预计授予IETF的权利将是我们希望授予他人的复制权利的超集。
It has long been IETF policy to encourage copying of RFCs in full. This permits wide dissemination of the material, without risking loss of context or meaning. The IETF wishes to continue to permit anyone to make full copies and translations of RFCs.
长期以来，IETF的政策是鼓励完全复制RFC。这使得材料得以广泛传播，而不会有失去上下文或意义的风险。IETF希望继续允许任何人制作RFC的完整副本和翻译。
There is rough consensus that it is useful to permit quoting without modification of excerpts from IETF Contributions. Such excerpts may be of any length and in any context. Translation of quotations is also to be permitted. All such quotations should be attributed properly to the IETF and the IETF Contribution from which they are taken.
人们普遍认为，允许在不修改IETF贡献摘录的情况下引用是有益的。此类摘录可以是任何长度和任何上下文。还允许翻译引文。所有此类报价均应适当归因于IETF及其来源的IETF贡献。
IETF Contributions often include components intended to be directly processed by a computer. Examples of these include ABNF definitions, XML Schemas, XML DTDs, XML RelaxNG definitions, tables of values, MIBs, ASN.1, and classical programming code. These are included in IETF Contributions for clarity and precision in specification. It is clearly beneficial, when such items are included in IETF Contributions, to permit the inclusion of such code components in products that implement the Contribution. It has been pointed out that in several important contexts, use of such code requires the ability to modify the code. One common example of this is simply the need to adapt code for use in specific contexts (languages, compilers, tool systems, etc.) Such use frequently requires some changes to the text of the code from the IETF Contribution. Another example is that code included in open source products is frequently licensed to permit any and all of the code to be modified. Since we want this code included in such products, it follows that we need to permit such modification. While there has been discussion of restricting in some way the rights to make such modifications, the rough consensus of the IETF is that such restrictions are likely a bad idea, and are certainly very complex to define.
IETF贡献通常包括打算由计算机直接处理的组件。这些示例包括ABNF定义、XML模式、XML DTD、XML RelaxNG定义、值表、MIB、ASN.1和经典编程代码。为了规范的清晰性和精确性，这些都包含在IETF贡献中。当这些项目包含在IETF贡献中时，允许在实现贡献的产品中包含这些代码组件显然是有益的。有人指出，在一些重要的上下文中，使用此类代码需要修改代码的能力。一个常见的例子就是需要调整代码以在特定环境（语言、编译器、工具系统等）中使用。这种使用通常需要对IETF贡献的代码文本进行一些更改。另一个例子是，开源产品中包含的代码经常被授权允许修改任何和所有代码。由于我们希望在这些产品中包含此代码，因此我们需要允许此类修改。虽然已经讨论过以某种方式限制进行此类修改的权利，但IETF的大致共识是，此类限制可能是个坏主意，而且定义起来肯定非常复杂。
As such, the rough consensus is that the IETF Trust is to grant rights such that code components of IETF Contributions can be extracted, modified, and used by anyone in any way desired. To enable the broadest possible extraction, modification, and usage, the IETF Trust should avoid adding software license obligations beyond those already present in a Contribution. The granted rights to extract, modify, and use code should allow creation of derived works outside the IETF that may carry additional license obligations. As the IETF Trust can not grant rights it does not receive, the rights
因此，大致的共识是，IETF信托将授予权利，使IETF贡献的代码组件可以被任何人以任何想要的方式提取、修改和使用。为了实现尽可能广泛的提取、修改和使用，IETF信托基金应避免在贡献中已经存在的软件许可义务之外增加软件许可义务。授予的提取、修改和使用代码的权利应允许在IETF之外创建衍生作品，这些衍生作品可能承担额外的许可义务。由于IETF信托无法授予其未收到的权利，因此
to extract, modify, and use code described in this paragraph can not be granted in IETF Contributions that are explicitly marked as not permitting derivative works.
提取、修改和使用本段中描述的代码不能在明确标记为不允许衍生作品的IETF贡献中授予。
While it is up to the Trustees of the IETF Trust to determine the best way of meeting this objective, two mechanisms are suggested here that are believed to be helpful in documenting the intended grant to readers and users of IETF Contributions.
虽然IETF信托的受托人有权决定实现这一目标的最佳方式，但本文提出了两种机制，据信有助于记录向IETF贡献的读者和用户提供的预期补助金。
Firstly, the Trustees of the IETF Trust should maintain, in a suitable, easily accessible fashion, a list of common RFC components that will be considered to be code. To start, this list should include at least the items listed above. The Trustees of the IETF Trust will add to this list as they deem suitable or as they are directed by the IETF.
首先，IETF信托的受托人应以一种合适的、易于访问的方式维护一份将被视为代码的通用RFC组件列表。首先，此列表应至少包括上面列出的项目。IETF信托的受托人将根据其认为合适的情况或IETF的指示添加到此列表中。
Additionally, the Trustees of the IETF Trust should define a textual representation to be included in an IETF Contribution to indicate that a portion of the document is considered by the authors (and later, the working group, and upon approval, the IETF) to be code and thus subject to the permissions granted to use code.
此外，IETF信托的受托人应定义要包含在IETF贡献中的文本表示，以表明文件的一部分被作者（以及后来的工作组，以及在批准后的IETF）视为代码，因此受授予使用代码的许可的约束。
There is no consensus at this time to permit the use of text from RFCs in contexts where the right to modify the text is required. The authors of IETF Contributions may be able and willing to grant such rights independently of the rights they have granted to the IETF by making the Contribution.
目前还没有达成共识，允许在需要修改文本的情况下使用来自RFC的文本。IETF贡献的作者可能能够并愿意通过贡献而独立于他们授予IETF的权利授予这些权利。
There have been contexts where the material in an IETF Contribution is also available under other license terms. The IETF wishes to be able to include content that is available under such licenses. It is desirable to indicate in the IETF Contribution that other licenses are available. It would be inappropriate and confusing if such additional licenses restricted the rights the IETF intends to grant in the content of RFCS.
在某些情况下，IETF贡献中的材料也可根据其他许可条款获得。IETF希望能够包括此类许可下可用的内容。希望在IETF贡献中指出其他许可证可用。如果此类附加许可证限制了IETF打算授予的RFC内容的权利，这将是不恰当和令人困惑的。
However, the IETF does not wish to have IETF Contributions contain additional licenses, as that introduces a number of additional difficulties. Specifically, additional text in the document, and any additional license referred to by permitted additional text, must not in any way restrict the rights the IETF intends to grant to others for using the contents of IETF Contributions.
然而，IETF不希望IETF贡献包含额外的许可证，因为这会带来许多额外的困难。具体而言，文件中的附加文本以及允许的附加文本所指的任何附加许可不得以任何方式限制IETF打算授予他人使用IETF贡献内容的权利。
Authors of Contributions retain all rights in their Contributions. As such, an author may directly grant any rights they wish separately from what the IETF grants. However, a reader wishing to determine or make use of such grants will need to either consult external sources of information, possibly including open source code and documents, or contact the author directly.
稿件作者保留其稿件的所有权利。因此，作者可以直接授予他们希望独立于IETF授予的任何权利。然而，希望确定或使用此类补助金的读者需要查阅外部信息来源，可能包括开源代码和文档，或者直接与作者联系。
No values are assigned in this document, no registries are created, and there is no action assigned to the IANA by this document. One list (of kinds of code sections) is anticipated, to be created and maintained by the Trustees of the IETF Trust. It is up to the Trustees of the IETF Trust whether they create such a list and whether they choose to involve the IANA in maintaining that list.
本文档中未分配任何值，未创建任何注册表，且本文档未向IANA分配任何操作。预计IETF信托的受托人将创建和维护一份清单（各种代码部分）。IETF信托的受托人是否创建此类列表以及是否选择让IANA参与维护该列表取决于IETF信托的受托人。
This document introduces no new security considerations. It is a process document about the IETF's IPR rights being granted to other people. While there may be attacks against the integrity or effectiveness of the IETF processes, this document does not address such issues.
本文档没有引入新的安全注意事项。这是一份关于IETF将知识产权授予他人的过程文件。尽管可能存在对IETF过程完整性或有效性的攻击，但本文件并未解决此类问题。
[RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, November 2008.
[RFC5378]Bradner，S.，Ed.和J.Contreras，Ed.，“向IETF信托提供的权利出资人”，BCP 78，RFC 5378，2008年11月。
[RFC3935] Alvestrand, H., "A Mission Statement for the IETF", BCP 95, RFC 3935, October 2004.
[RFC3935]Alvestrand，H.，“IETF的使命声明”，BCP 95，RFC 3935，2004年10月。
[RFC4071] Austein, R. and B. Wijnen, "Structure of the IETF Administrative Support Activity (IASA)", BCP 101, RFC 4071, April 2005.
[RFC4071]Austein，R.和B.Wijnen，“IETF行政支持活动（IASA）的结构”，BCP 101，RFC 4071，2005年4月。
[RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR Trust", BCP 101, RFC 4371, January 2006.
[RFC4371]Carpenter，B.和L.Lynch，“知识产权信托的BCP 101更新”，BCP 101，RFC 4371，2006年1月。
Author's Address
作者地址
Joel M. Halpern (editor) Self P. O. Box 6049 Leesburg, VA 20178 US
Joel M.Halpern（编辑）Self邮政信箱6049弗吉尼亚州利斯堡，美国20178
EMail: jmh@joelhalpern.com
EMail: jmh@joelhalpern.com