Network Working Group R. Braden
Request for Comments: 5744 ISI
Updates: 4846 J. Halpern
Category: Informational Ericsson
December 2009
Network Working Group R. Braden
Request for Comments: 5744 ISI
Updates: 4846 J. Halpern
Category: Informational Ericsson
December 2009
Procedures for Rights Handling in the RFC Independent Submission Stream
RFC独立提交流中的权限处理过程
Abstract
摘要
This document specifies the procedures by which authors of RFC Independent Submission documents grant the community "incoming" rights for copying and using the text. It also specifies the "outgoing" rights the community grants to readers and users of those documents, and it requests that the IETF Trust manage the outgoing rights to effect this result.
本文件规定了RFC独立提交文件的作者授予社区复制和使用文本的“传入”权利的程序。它还指定了社区授予这些文档的读者和用户的“传出”权限，并要求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) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 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 BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括《信托法律条款》第4.e节中所述的简化BSD许可文本，并且提供BSD许可中所述的代码组件时不提供任何担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Rules for Submission and Use of Material . . . . . . . . . . . 4
5. Procedures Requested of the IETF Trust . . . . . . . . . . . . 4
6. Patent and Trademark Rules for the Independent Submission
Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Rules for Submission and Use of Material . . . . . . . . . . . 4
5. Procedures Requested of the IETF Trust . . . . . . . . . . . . 4
6. Patent and Trademark Rules for the Independent Submission
Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
As the IETF has grown, the process and the community have gotten more careful about defining the rights relating to copying documents that are granted by authors to the community, and the corresponding rights that are granted by the community to readers and users of these documents.
随着IETF的发展，该流程和社区在定义作者授予社区的复制文档相关权利以及社区授予这些文档的读者和用户的相应权利时变得更加谨慎。
This document defines the copyright procedures for RFC Independent Submission documents. It parallels the procedures for IETF-produced documents defined in [RFC5377] and [RFC5378].
本文件规定了RFC独立提交文件的版权程序。它与[RFC5377]和[RFC5378]中定义的IETF生成文档的过程相似。
In summary, submissions in the Independent Submission stream use the same submission procedures and mechanisms that are defined in RFC 5378, and hence require the same "incoming rights" as IETF-stream documents. This document provides advice to the Trustees of the IETF Trust on "outgoing" rights to be granted to readers and users of Independent Submission documents, and it explicitly requests the IETF Trust to manage the rights in accordance with this advice.
总之，独立提交流中的提交使用RFC 5378中定义的相同提交程序和机制，因此需要与IETF流文档相同的“传入权限”。本文件就授予独立提交文件的读者和用户的“传出”权利向IETF信托受托人提供建议，并明确要求IETF信托根据本建议管理这些权利。
This document also specifies the policies regarding the disclosure of Patents and Trademarks that may be relevant to a submission intended for the Independent Submission stream.
本文件还规定了有关专利和商标披露的政策，这些政策可能与针对独立提交流的提交相关。
The concept of RFC streams in general, and the Independent Submission stream in particular, are described in Section 5 of [RFC4844] and in RFC 4846 [RFC4846]. In general terms, the Independent Submission stream continues the long-established tradition in the Internet community of allowing and encouraging the RFC Editor to publish documents that are relevant to the community but are not products of, and do not conflict with, the IETF process. These may be comments on
[RFC4844]第5节和RFC 4846[RFC4846]中描述了RFC流的一般概念，特别是独立提交流。一般而言，独立提交流延续了互联网社区的悠久传统，即允许并鼓励RFC编辑发布与社区相关但不是IETF过程的产物且不与IETF过程冲突的文档。这些可能是对
IETF documents or they may be other work relevant to the Internet that, historically, the RFC Editor has chosen to publish.
IETF文件或它们可能是其他与互联网相关的工作，在历史上，RFC编辑选择出版这些文件。
With the publication of [RFC5620], the IETF began a process shift in which the responsibility for Independent Submission stream publication will move to an individual designated by the IAB as the Independent Submission Editor (ISE).
随着[RFC5620]的发布，IETF开始了一个过程转移，独立提交流发布的责任将转移到IAB指定的个人身上，作为独立提交编辑器（ISE）。
Section 8 of RFC 4846 presented the copyright rules for the Independent Submission stream. The present document is intended to be fully consistent with that section and to update it by clarifying the formal procedures that the IETF Trust will use to effect those rules.
RFC 4846第8节介绍了独立提交流的版权规则。本文件旨在与该节完全一致，并通过澄清IETF信托基金将用于实施这些规则的正式程序对其进行更新。
The goal of the RFC Independent Submission stream is to publish information that is intended to advance the state of the art and the interoperability of solutions for use in conjunction with the Internet. As specified in Section 8 of RFC 4846, the community has determined that this objective will best be met with a liberal copyright policy on Independent Submission documents. Therefore, the Independent Submission policy is to allow any individual reading such documents to use the content thereof in any manner. The only restriction is that proper credit ("attribution") must be given. Lawyers describe this liberal policy by saying that this stream normally permits "unlimited derivative works". (It should be noted that this liberal policy was always followed by the original RFC Editor, Jon Postel; in a sense, the present document is a formalization of a 30-year-old policy on RFC copyrights.)
RFC独立提交流的目标是发布旨在提高与互联网结合使用的解决方案的最新技术和互操作性的信息。如RFC 4846第8节所述，社区已确定，对于独立提交的文件，自由版权政策将最好地实现这一目标。因此，独立提交政策允许阅读此类文件的任何个人以任何方式使用其内容。唯一的限制是必须给予适当的信用（“归属”）。律师们描述这一自由政策时说，这一潮流通常允许“无限衍生作品”。（应该注意的是，最初的RFC编辑Jon Postel始终遵循这一自由政策；从某种意义上说，本文件是对已有30年历史的RFC版权政策的正式化。）
However, for a small subset of documents published as Independent Submissions, it is not reasonable to permit unlimited derivative works. Examples are proprietary protocols and output from other standards bodies. In such cases, authors are permitted to request that the published Independent Submission documents permit no derivative works.
然而，对于作为独立提交文件发布的一小部分文件，允许无限衍生作品是不合理的。例如专有协议和其他标准机构的输出。在这种情况下，作者可以要求出版的独立提交文件不允许衍生作品。
Note also that this unlimited derivative works policy applies to all parts of an Independent Submission document, including any code. Therefore, no separate licensing procedure is required for extracting and adapting code that is contained in an Independent Submission document submitted under the (preferred) unlimited derivative works terms. On the other hand, code may not be extracted and adapted from Independent Submission documents submitted under the no derivative works terms.
还请注意，此无限衍生产品工程政策适用于独立提交文件的所有部分，包括任何代码。因此，提取和修改根据（首选）无限衍生产品条款提交的独立提交文件中包含的代码不需要单独的许可程序。另一方面，不得从根据无衍生工程条款提交的独立提交文件中提取和改编代码。
Independent Submission authors will submit their material as Internet-Drafts. These drafts will be submitted to, and stored in, the IETF Internet-Drafts repository in the same fashion as IETF Internet-Drafts.
独立提交作者将以互联网草稿的形式提交材料。这些草案将以与IETF互联网草案相同的方式提交并存储在IETF互联网草案存储库中。
During Internet-Draft submission, authors who intend to submit their document for publication in the Independent Submission stream will grant rights as described in [RFC5378]. To request that the contribution be published as an RFC that permits no derivative works, an author may use the form specified for use with RFC 5378.
在互联网草案提交期间，打算提交其文件以在独立提交流中发布的作者将授予[RFC5378]中所述的权利。为了要求以RFC的形式出版稿件，不允许衍生作品，作者可以使用RFC 5378指定的格式。
The IETF Trust will indicate that, in cooperation with the Independent Submission Editor, the Trust grants to readers and users of material from Independent Submission documents the right to make unlimited derivative works, unless the document specifies that no derivative works are permitted. This will permit anyone to copy, extract, modify, or otherwise use material from Independent Submission documents as long as suitable attribution is given.
IETF信托将表明，与独立提交编辑合作，信托授予独立提交文件材料的读者和用户制作无限衍生作品的权利，除非文件规定不允许衍生作品。这将允许任何人复制、摘录、修改或以其他方式使用独立提交文件中的材料，只要给出适当的归属。
Contributors of Internet-Drafts intended for the Independent Submission stream will include suitable boilerplate defined by the IETF Trust. This boilerplate shall indicate compliance with RFC 5378 and shall explicitly indicate either that no derivative works can be based on the contribution or, as is preferred, that unlimited derivative works may be crafted from the contribution.
用于独立提交流的互联网草案的贡献者将包括IETF信托定义的适当样板。该样板应表明符合RFC 5378的要求，并应明确说明不得基于该贡献创作任何衍生作品，或如首选，可根据该贡献创作无限衍生作品。
It should be understood that the final publication decision for the Independent Submission stream rests with the Independent Submission Editor (ISE). Compliance with these terms is not a guarantee of publication. In particular, the ISE may question the appropriateness of a "no derivative works" restriction requested by an author. The appropriateness of such usage must be negotiated among the authors and the ISE.
应该理解的是，独立提交流的最终发布决定取决于独立提交编辑器（ISE）。遵守这些条款并不是发布的保证。特别是，ISE可能会质疑作者要求的“无衍生作品”限制的适当性。这种用法的适当性必须在作者和ISE之间协商。
The Independent Submission Editor requests that the IETF Trust and its Trustees assist in meeting the goals and procedures set forth in this document.
独立提交编辑要求IETF信托及其受托人协助实现本文件规定的目标和程序。
The Trustees are requested to publicly confirm their willingness and ability to accept responsibility for the Intellectual Property Rights for the Independent Submission stream. They are also requested to indicate their willingness and intent to work according to the procedures and goals defined by the ISE.
受托人被要求公开确认其愿意并有能力承担独立提交流的知识产权责任。他们还需要表明他们愿意并打算按照ISE规定的程序和目标开展工作。
Specifically, the Trustees are asked to develop the necessary boilerplate to enable the suitable marking of documents so that the IETF Trust receives the rights as specified in RFC 5378. These procedures need to also allow documents to grant either no rights to make derivative works or, preferentially, the right to make unlimited derivative works from the documents. It is left to the Trust to specify exactly how this shall be clearly indicated in each document.
具体而言，受托人被要求开发必要的样板文件，以便对文件进行适当标记，从而使IETF信托获得RFC 5378中规定的权利。这些程序还需要允许文件不授予制作衍生作品的权利，或者优先授予从文件制作无限衍生作品的权利。信托基金应明确规定如何在每份文件中明确说明这一点。
As specified above, contributors of documents for the Independent Submission stream are expected to use the IETF Internet-Draft process, complying therein with the rules specified in the latest version of BCP 9, whose version at the time of writing was [RFC2026]. This includes the disclosure of Patent and Trademark issues that are known, or can be reasonably expected to be known, by the contributor.
如上所述，独立提交流文件的投稿人应使用IETF互联网草稿流程，遵守最新版本的BCP 9中规定的规则，其在撰写本文时的版本为[RFC2026]。这包括披露撰稿人已知或可以合理预期已知的专利和商标问题。
Disclosure of license terms for patents is also requested, as specified in the most recent version of BCP 79. The version of BCP 79 at the time of this writing was [RFC3979], updated by [RFC4879]. The Independent Submission stream has chosen to use the IETF's IPR disclosure mechanism, www.ietf.org/ipr/, for this purpose. The Independent Submission Editor would prefer the most liberal terms possible be made available for specifications published as Independent Submission documents. Terms that do not require fees or licensing are preferable. Non-discriminatory terms are strongly preferred over those that discriminate among users. However, although disclosure is required, there are no specific requirements on the licensing terms for intellectual property related to Independent Submission publication.
根据BCP 79最新版本的规定，还要求披露专利许可条款。撰写本文时，BCP 79的版本为[RFC3979]，更新为[RFC4879]。为此，独立提交流选择使用IETF的知识产权披露机制www.IETF.org/IPR/。独立提交编辑器更愿意为作为独立提交文件发布的规范提供尽可能宽松的条款。不需要收费或许可的条款更可取。非歧视性条款比歧视用户的条款更受欢迎。然而，尽管要求披露，但对与独立提交出版物相关的知识产权的许可条款没有具体要求。
The integrity and quality of the Independent Submission stream are the responsibility of the Independent Submission Editor. This document does not change those responsibilities.
独立提交流的完整性和质量由独立提交编辑器负责。本文件不会改变这些责任。
[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月。
[RFC3979] Bradner, S., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005.
[RFC3979]Bradner，S.，“IETF技术中的知识产权”，BCP 79，RFC 3979，2005年3月。
[RFC4844] Daigle, L. and Internet Architecture Board, "The RFC Series and RFC Editor", RFC 4844, July 2007.
[RFC4844]Daigle，L.和互联网架构委员会，“RFC系列和RFC编辑器”，RFC 48442007年7月。
[RFC4846] Klensin, J. and D. Thaler, "Independent Submissions to the RFC Editor", RFC 4846, July 2007.
[RFC4846]Klensin，J.和D.Thaler，“向RFC编辑提交的独立意见”，RFC 48462007年7月。
[RFC4879] Narten, T., "Clarification of the Third Party Disclosure Procedure in RFC 3979", BCP 79, RFC 4879, April 2007.
[RFC4879]Narten，T.，“RFC 3979中第三方披露程序的澄清”，BCP 79，RFC 4879，2007年4月。
[RFC5378] Bradner, S. and J. Contreras, "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, November 2008.
[RFC5378]Bradner，S.和J.Contreras，“IETF信托基金的权利出资人”，BCP 78，RFC 5378，2008年11月。
[RFC5620] Kolkman, O. and IAB, "RFC Editor Model (Version 1)", RFC 5620, August 2009.
[RFC5620]Kolkman，O.和IAB，“RFC编辑器模型（版本1）”，RFC562009年8月。
[RFC5377] Halpern, J., "Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents", RFC 5377, November 2008.
[RFC5377]Halpern，J.，“就IETF文件中授予的权利向IETF信托受托人提供建议”，RFC 5377，2008年11月。
Authors' Addresses
作者地址
Robert Braden USC Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 US
Robert Braden USC信息科学研究所美国加利福尼亚州马里纳德雷海军部路4676号，邮编90292
EMail: braden@isi.edu
EMail: braden@isi.edu
Joel M. Halpern Ericsson P. O. Box 6049 Leesburg, VA 20178 US
美国弗吉尼亚州利斯堡市Joel M.Halpern Ericsson邮政信箱6049邮编：20178
EMail: jhalpern@redback.com
EMail: jhalpern@redback.com