Network Working Group                                    S. Bradner, Ed.
Request for Comments: 3978                            Harvard University
BCP: 78                                                       March 2005
Obsoletes: 3667
Updates: 2026
Category: Best Current Practice
        
Network Working Group                                    S. Bradner, Ed.
Request for Comments: 3978                            Harvard University
BCP: 78                                                       March 2005
Obsoletes: 3667
Updates: 2026
Category: Best Current Practice
        

IETF Rights in Contributions

IETF在捐款中的权利

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

摘要

The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC 2026.

IETF关于IETF稿件权利的政策旨在确保IETF和互联网社区可以获得此类稿件,同时允许作者保留尽可能多的权利。本备忘录详细说明了IETF关于向IETF捐款的权利的政策。它还描述了政策旨在实现的目标。本备忘录更新了RFC 2026,并用RFC 3979取代了RFC 2026第10节。

Table of Contents

目录

   1.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Rights in IETF Contributions. . . . . . . . . . . . . . . . .   5
       3.1.  General Policy. . . . . . . . . . . . . . . . . . . . .   5
       3.2.  Confidentiality Obligations . . . . . . . . . . . . . .   5
       3.3.  Granting of Rights and Permissions. . . . . . . . . . .   6
       3.4.  Representations and Warranties. . . . . . . . . . . . .   7
       3.5.  No Duty to Publish. . . . . . . . . . . . . . . . . . .   7
       3.6.  Trademarks. . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Rights in RFC Editor Contributions. . . . . . . . . . . . . .   8
       4.1.  Requirements from Section 3 . . . . . . . . . . . . . .   8
       4.2.  Granting of Rights and Permissions. . . . . . . . . . .   8
   5.  Notices Required in IETF Documents. . . . . . . . . . . . . .   9
       5.1.  IPR Disclosure Acknowledgement. . . . . . . . . . . . .  10
       5.2.  Derivative Works Limitation . . . . . . . . . . . . . .  10
        
   1.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction. . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Rights in IETF Contributions. . . . . . . . . . . . . . . . .   5
       3.1.  General Policy. . . . . . . . . . . . . . . . . . . . .   5
       3.2.  Confidentiality Obligations . . . . . . . . . . . . . .   5
       3.3.  Granting of Rights and Permissions. . . . . . . . . . .   6
       3.4.  Representations and Warranties. . . . . . . . . . . . .   7
       3.5.  No Duty to Publish. . . . . . . . . . . . . . . . . . .   7
       3.6.  Trademarks. . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Rights in RFC Editor Contributions. . . . . . . . . . . . . .   8
       4.1.  Requirements from Section 3 . . . . . . . . . . . . . .   8
       4.2.  Granting of Rights and Permissions. . . . . . . . . . .   8
   5.  Notices Required in IETF Documents. . . . . . . . . . . . . .   9
       5.1.  IPR Disclosure Acknowledgement. . . . . . . . . . . . .  10
       5.2.  Derivative Works Limitation . . . . . . . . . . . . . .  10
        
       5.3.  Publication Limitation. . . . . . . . . . . . . . . . .  11
       5.4.  Copyright Notice. . . . . . . . . . . . . . . . . . . .  11
       5.5.  Disclaimer. . . . . . . . . . . . . . . . . . . . . . .  11
       5.6.  Exceptions. . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Notices and Rights Required in RFC Editor Contributions . . .  13
   7.  Exposition of why these procedures are the way they are . . .  13
       7.1.  Rights Granted in IETF Contributions. . . . . . . . . .  13
       7.2.  Rights to use Contributed Material. . . . . . . . . . .  14
       7.3.  Right to Produce Derivative Works . . . . . . . . . . .  14
       7.4.  Rights to use Trademarks. . . . . . . . . . . . . . . .  16
       7.5.  Who Does This Apply To? . . . . . . . . . . . . . . . .  16
   8.  Contributions Not Subject to Copyright. . . . . . . . . . . .  16
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   10. References. . . . . . . . . . . . . . . . . . . . . . . . . .  17
       10.1. Normative References. . . . . . . . . . . . . . . . . .  17
       10.2. Informative References. . . . . . . . . . . . . . . . .  17
   11. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  17
       Editor's Address. . . . . . . . . . . . . . . . . . . . . . .  17
       Full Copyright Statement. . . . . . . . . . . . . . . . . . .  18
        
       5.3.  Publication Limitation. . . . . . . . . . . . . . . . .  11
       5.4.  Copyright Notice. . . . . . . . . . . . . . . . . . . .  11
       5.5.  Disclaimer. . . . . . . . . . . . . . . . . . . . . . .  11
       5.6.  Exceptions. . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Notices and Rights Required in RFC Editor Contributions . . .  13
   7.  Exposition of why these procedures are the way they are . . .  13
       7.1.  Rights Granted in IETF Contributions. . . . . . . . . .  13
       7.2.  Rights to use Contributed Material. . . . . . . . . . .  14
       7.3.  Right to Produce Derivative Works . . . . . . . . . . .  14
       7.4.  Rights to use Trademarks. . . . . . . . . . . . . . . .  16
       7.5.  Who Does This Apply To? . . . . . . . . . . . . . . . .  16
   8.  Contributions Not Subject to Copyright. . . . . . . . . . . .  16
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   10. References. . . . . . . . . . . . . . . . . . . . . . . . . .  17
       10.1. Normative References. . . . . . . . . . . . . . . . . .  17
       10.2. Informative References. . . . . . . . . . . . . . . . .  17
   11. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . .  17
       Editor's Address. . . . . . . . . . . . . . . . . . . . . . .  17
       Full Copyright Statement. . . . . . . . . . . . . . . . . . .  18
        
1. Definitions
1. 定义

The following definitions are for terms used in the context of this document. Other terms, including "IESG," "ISOC," "IAB," and "RFC Editor," are defined in [RFC2028].

以下定义适用于本文件中使用的术语。[RFC2028]中定义了其他术语,包括“IESG”、“ISOC”、“IAB”和“RFC编辑器”。

a. "IETF": In the context of this document, the IETF includes all individuals who participate in meetings, working groups, mailing lists, functions and other activities which are organized or initiated by ISOC, the IESG or the IAB under the general designation of the Internet Engineering Task Force or IETF, but solely to the extent of such participation.

a. “IETF”:在本文件中,IETF包括所有参加由ISOC、IESG或IAB在互联网工程任务组或IETF的总体指定下组织或发起的会议、工作组、邮件列表、职能和其他活动的个人,但仅限于此类参与的范围。

b. "IETF Standards Process": the activities undertaken by the IETF in any of the settings described in 1(c) below.

b. “IETF标准过程”:IETF在下文第1(c)条所述的任何环境中开展的活动。

c. "IETF Contribution": any submission to the IETF intended by the Contributor for publication as all or part of an Internet-Draft or RFC (except for RFC Editor Contributions described below) and any statement made within the context of an IETF activity. Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

c. “IETF贡献”:由贡献者向IETF提交的、作为互联网草案或RFC(下文所述RFC编者贡献除外)全部或部分发布的任何信息,以及在IETF活动背景下所作的任何声明。此类声明包括IETF会议上的口头声明,以及在任何时间或地点进行的书面和电子通信,其目的是:

o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB,

o IETF全体会议、任何IETF工作组或其部分、IESG或代表IESG的任何成员、IAB或代表IAB的任何成员,

o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function (except for RFC Editor Contributions described below).

o 任何IETF邮件列表,包括IETF列表本身、任何工作组或设计团队列表,或在IETF主持下运行的任何其他列表,或RFC编辑器或互联网草稿功能(下文描述的RFC编辑器贡献除外)。

Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this document.

在IETF会话、邮件列表或其他功能之外做出的声明,显然不打算输入到IETF活动、组或功能中,在本文件上下文中不属于IETF贡献。

d. "Internet-Draft": temporary documents used in the IETF and RFC Editor processes. Internet-Drafts are posted on the IETF web site by the IETF Secretariat and have a nominal maximum lifetime in the Secretariat's public directory of 6 months, after which they are removed. Note that Internet-Drafts are archived many places on the Internet, and not all of these places remove expired Internet-Drafts. Internet-Drafts that are under active consideration by the IESG are not removed from the Secretariat's public directory until that consideration is complete. In addition, the author of an Internet-Draft can request that the lifetime in the Secretariat's public directory be extended before the expiration.

d. “互联网草案”:IETF和RFC编辑过程中使用的临时文件。互联网草稿由IETF秘书处发布在IETF网站上,在秘书处的公共目录中名义上最长使用期限为6个月,之后将被删除。请注意,Internet草稿在Internet上的许多位置存档,并且并非所有这些位置都会删除过期的Internet草稿。IESG正在积极审议的互联网草案在审议完成之前不会从秘书处的公共目录中删除。此外,因特网草案的作者可以要求在期满之前延长秘书处公共目录中的有效期。

e. "RFC": the basic publication series for the IETF. RFCs are published by the RFC Editor and once published are never modified. (See [RFC2026] Section 2.1)

e. “RFC”:IETF的基本出版物系列。RFC由RFC编辑器发布,一旦发布,就不会修改。(见[RFC2026]第2.1节)

f. "RFC Editor Contribution": An Internet-Draft intended by the Contributor to be submitted to the RFC Editor for publication as an Informational or Experimental RFC but not intended to be part of the IETF Standards Process.

f. “RFC编者贡献”:由贡献者提交给RFC编者的互联网草稿,作为信息性或实验性RFC发布,但不作为IETF标准过程的一部分。

g. "IETF Internet-Drafts": Internet-Drafts other than RFC Editor Contributions. Note that under Section 3.3(a) the grant of rights in regards to IETF Internet-Drafts as specified in this document is perpetual and irrevocable and thus survives the Secretariat's removal of an Internet-Draft from the public directory, except as limited by Section 3.3(a)(C). (See [RFC2026] Sections 2.2 and 8)

g. “IETF互联网草案”:除RFC编辑贡献之外的互联网草案。注意,根据第3.3(a)节,本文件中规定的IETF互联网草案相关权利的授予是永久和不可撤销的,因此在秘书处从公共目录中删除互联网草案后仍然有效,但第3.3(a)(C)节限制的情况除外。(见[RFC2026]第2.2节和第8节)

h. "IETF Documents": RFCs and Internet-Drafts except for Internet-Drafts that are RFC Editor Contributions and the RFCs that are published from them.

h. “IETF文件”:RFC和互联网草稿,但作为RFC编辑贡献的互联网草稿以及由此发布的RFC除外。

i. "RFC Editor Documents": RFCs and Internet-Drafts that are RFC Editor Contributions and the RFCs that may be published from them.

i. “RFC编辑文档”:RFC编辑贡献的RFC和互联网草稿,以及可能从中发布的RFC。

j. "Contribution": IETF Contributions and RFC Editor Contributions.

j. “贡献”:IETF贡献和RFC编辑贡献。

k. "Contributor": an individual submitting a Contribution.

k. “贡献者”:提交贡献的个人。

l. "Reasonably and personally known": means something an individual knows personally or, because of the job the individual holds, would reasonably be expected to know. This wording is used to indicate that an organization cannot purposely keep an individual in the dark about patents or patent applications just to avoid the disclosure requirement. But this requirement should not be interpreted as requiring the IETF Contributor or participant (or his or her represented organization, if any) to perform a patent search to find applicable IPR.

l. “合理和个人知晓”:指个人亲自知道的事情,或由于个人所从事的工作,合理预期会知道的事情。该措辞用于表示组织不能为了避免披露要求而故意将个人的专利或专利申请蒙在鼓里。但这一要求不应被解释为要求IETF贡献者或参与者(或其代表的组织,如有)进行专利搜索以找到适用的知识产权。

2. Introduction
2. 介绍

Under the laws of most countries and current international treaties (for example the "Berne Convention for the Protection of Literary and Artistic Work" [Berne]), authors obtain numerous rights in the works they produce automatically upon producing them. These rights include copyrights, moral rights and other rights. In many cases, if the author produces a work within the scope of his or her employment, most of those rights are usually assigned to the employer, either by operation of law or, in many cases, under contract. (The Berne Convention names some rights as "inalienable", which means that the author retains them in all cases.)

根据大多数国家的法律和现行国际条约(例如《伯尔尼保护文学和艺术作品公约》[Berne]),作者在创作作品时自动获得作品的多项权利。这些权利包括版权、精神权利和其他权利。在许多情况下,如果作者在其受雇范围内创作作品,这些权利中的大多数通常通过法律或在许多情况下根据合同转让给雇主。(伯尔尼公约将某些权利命名为“不可剥夺”,这意味着提交人在所有情况下都保留这些权利。)

This document details the rights that the IETF requires in IETF Contributions and rights the IETF, as publisher of Internet-Drafts, requires in all such Drafts including RFC Editor Contributions. The RFC Editor may also define additional rights required for RFC Editor Contributions.

本文件详细说明了IETF在IETF稿件中要求的权利,以及IETF作为互联网草稿出版商在所有此类草稿(包括RFC编辑器稿件)中要求的权利。RFC编辑器还可以定义RFC编辑器贡献所需的其他权限。

In order for works to be used within the IETF Standards Process or to be published as Internet-Drafts, certain limited rights in all Contributions must be granted to the IETF and Internet Society (ISOC). In addition, Contributors must make representations to IETF and ISOC regarding their ability to grant these rights. These necessary rights and representations have until now been laid out in Section 10 of [RFC2026]. In the years since [RFC2026] was published there have been a number of times when the exact intent of Section 10 has been the subject of vigorous debate within the IETF community. The aim of this document is to clarify various ambiguities in Section 10 of [RFC2026] that led to these debates and to amplify the policy in order to clarify what the IETF is currently doing.

为了使作品在IETF标准过程中使用或作为互联网草案发布,必须向IETF和互联网协会(ISOC)授予所有贡献中的某些有限权利。此外,贡献者必须向IETF和ISOC陈述其授予这些权利的能力。到目前为止,这些必要的权利和陈述已在[RFC2026]第10节中列出。自[RFC2026]出版以来,第10节的确切意图曾多次成为IETF界激烈辩论的主题。本文件的目的是澄清[RFC2026]第10节中导致这些辩论的各种含糊不清之处,并扩大政策,以澄清IETF目前正在做什么。

Section 1 gives definitions used in describing these policies. Sections 3, 4, 5, and 6 of this document address the rights in Contributions previously covered by Section 10 of [RFC2026] and the "Note Well" explanatory text presented at many IETF activities.

第1节给出了描述这些政策时使用的定义。本文件第3节、第4节、第5节和第6节阐述了[RFC2026]第10节之前涵盖的贡献权利,以及在许多IETF活动中呈现的“注释良好”解释性文本。

Sections 7 and 8 then explain the rationale for these provisions, including some of the clarifications that have become understood since the adoption of [RFC2026]. The rules and procedures set out in this document are not intended to substantially modify or alter the IETF's current policy toward Contributions.

然后,第7节和第8节解释了这些规定的基本原理,包括自[RFC2026]通过以来已经理解的一些澄清。本文件中规定的规则和程序无意实质性修改或改变IETF当前的供款政策。

A companion document [RFC3979] deals with rights in technologies developed or specified as part of the IETF Standards Process. This document is not intended to address those issues.

附带文件[RFC3979]涉及作为IETF标准过程一部分开发或指定的技术的权利。本文件无意解决这些问题。

The rights addressed in this document fall into the following categories:

本文件中涉及的权利分为以下几类:

o rights to make use of contributed material o copyrights in IETF documents o rights to produce derivative works o rights to use trademarks

o 使用捐赠材料的权利或IETF文件中的版权权利或制作衍生作品的权利或使用商标的权利

This document is not intended as legal advice. Readers are advised to consult their own legal advisors if they would like a legal interpretation of their rights or the rights of the IETF in any Contributions they make.

本文件不作为法律意见。建议读者咨询自己的法律顾问,如果他们希望对自己的权利或IETF在其所做贡献中的权利进行法律解释。

3. Rights in IETF Contributions
3. IETF贡献中的权利

The following are the rights the IETF requires in all IETF Contributions:

以下是IETF在所有IETF贡献中要求的权利:

3.1. General Policy
3.1. 总方针

In all matters of copyright and document procedures, the intent is to benefit the Internet community and the public at large, while respecting the legitimate rights of others.

在版权和文件程序的所有事项中,目的是使互联网社区和广大公众受益,同时尊重他人的合法权利。

3.2. Confidentiality Obligations
3.2. 保密义务

No information or document that is subject to any requirement of confidentiality or any restriction on its dissemination may be submitted as a Contribution or otherwise considered in any part of the IETF Standards Process, and there must be no assumption of any confidentiality obligation with respect to any Contribution. Each Contributor agrees that any statement in a Contribution, whether generated automatically or otherwise, that states or implies that the Contribution is confidential or subject to any privilege, can be disregarded for all purposes, and will be of no force or effect.

受保密要求或传播限制的任何信息或文件不得作为贡献提交,或在IETF标准过程的任何部分中以其他方式考虑,且不得承担任何贡献的保密义务。每位供款人同意,供款中任何声明,无论是自动生成的还是以其他方式生成的,声明或暗示该供款是保密的或受任何特权约束的,均可出于所有目的不予理会,且不具有任何效力。

3.3. Granting of Rights and Permissions
3.3. 授予权利和许可

By submission of a Contribution, each person actually submitting the Contribution, and each named co-Contributor, is deemed to agree to the following terms and conditions, and to grant the following rights, on his or her own behalf and on behalf of the organization the Contributor represents or is sponsored by (if any) when submitting the Contribution.

通过提交出资,实际提交出资的每个人和每个指定共同出资人被视为同意以下条款和条件,并代表其本人和出资人所代表或赞助的组织(如有)授予以下权利在提交贡献时。

a. To the extent that a Contribution or any portion thereof is protected by copyright and other rights of authorship, the Contributor, and each named co-Contributor, and the organization he or she represents or is sponsored by (if any) grant a perpetual, irrevocable, non-exclusive, royalty-free, world-wide right and license to the ISOC and the IETF under all intellectual property rights in the Contribution:

a. 如果某一贡献或其任何部分受版权和其他作者权利的保护,贡献者、各指定共同贡献者以及其代表或赞助的组织(如有)授予永久、不可撤销、非排他性、免版税的权利,贡献中所有知识产权下的ISOC和IETF全球权利和许可:

(A) to copy, publish, display, and distribute the Contribution as part of the IETF Standards Process or in an Internet-Draft,

(A) 作为IETF标准过程的一部分或在互联网草案中复制、发布、显示和分发贡献,

(B) to prepare or allow the preparation of translations of the Contribution into languages other than English,

(B) 准备或允许准备将稿件翻译成英语以外的语言,

(C) unless explicitly disallowed in the notices contained in a Contribution [as per Section 5.2 below], to prepare derivative works (other than translations) that are based on or incorporate all or part of the Contribution, or comment upon it, within the IETF Standards Process. The license to such derivative works not granting the ISOC and the IETF any more rights than the license to the original Contribution,

(C) 除非[根据下文第5.2节]的贡献中包含的通知明确禁止,否则在IETF标准过程中,准备基于或包含贡献的全部或部分的衍生作品(翻译除外),或对其进行评论。此类衍生作品的许可证不授予ISOC和IETF比原始贡献许可证更多的权利,

(D) to reproduce any trademarks, service marks or trade names which are included in the Contribution solely in connection with the reproduction, distribution or publication of the Contribution and derivative works thereof as permitted by this paragraph. When reproducing Contributions, the IETF will preserve trademark and service mark identifiers used by the Contributor of the Contribution, including (TM) and (R) where appropriate, and

(D) 在本段允许的情况下,复制仅与复制、分发或出版本贡献及其衍生作品有关的贡献中包含的任何商标、服务商标或商号。在复制贡献时,IETF将保留贡献者使用的商标和服务标记标识符,包括(TM)和(R)(如适用),以及

(E) to extract, copy, publish, display, distribute, modify and incorporate into other works, for any purpose (and not limited to use within the IETF Standards Process) any executable code or code fragments that are included in any IETF Document (such as MIB and PIB modules), subject to the requirements of Section 5 (it also being understood that the licenses granted under this paragraph (E) shall not be deemed to grant any right under any patent, patent application or other similar

(E) 根据第5节的要求,出于任何目的(但不限于在IETF标准过程中使用)提取、复制、发布、显示、分发、修改并纳入其他作品中,包括在任何IETF文件(如MIB和PIB模块)中的任何可执行代码或代码片段(还应理解,根据本(E)段授予的许可不得视为授予任何专利、专利申请或其他类似权利

intellectual property right disclosed by the Contributor under [RFC3979]).

出资人根据[RFC3979]披露的知识产权。

b. The Contributor grants the IETF and ISOC permission to reference the name(s) and address(es) of the Contributor(s) and of the organization(s) s/he represents or is sponsored by (if any).

b. 投稿人授予IETF和ISOC引用投稿人及其代表或赞助的组织(如有)的名称和地址的权限。

3.4. Representations and Warranties
3.4. 陈述和保证

With respect to each Contribution, each Contributor represents that to the best of his or her knowledge and ability:

对于每项贡献,每位贡献者尽其知识和能力表示:

a. The Contribution properly acknowledges all major Contributors. A major Contributor is any person who has materially or substantially contributed to the IETF Contribution.

a. 该贡献恰当地承认了所有主要贡献者。主要贡献者是对IETF贡献做出实质性或实质性贡献的任何人。

b. No information in the Contribution is confidential and the IETF, ISOC, and its affiliated organizations may freely disclose any information in the Contribution.

b. 贡献中的任何信息均不保密,IETF、ISOC及其附属组织可自由披露贡献中的任何信息。

c. There are no limits to the Contributor's ability to make the grants, acknowledgments and agreements herein that are reasonably and personally known to the Contributor.

c. 供款人在本协议中做出供款人合理且亲自知晓的授予、确认和协议的能力不受限制。

d. The Contributor has not intentionally included in the Contribution any material which is defamatory or untrue or which is illegal under the laws of the jurisdiction in which the Contributor has his or her principal place of business or residence.

d. 出资人未故意在出资中包含任何诽谤性或不真实的材料,或根据出资人主要营业地或居住地所在司法管辖区的法律属于非法的材料。

e. All trademarks, trade names, service marks and other proprietary names used in the Contribution that are reasonably and personally known to the Contributor are clearly designated as such where reasonable.

e. 出资人合理且个人知晓的所有商标、商号、服务商标和出资中使用的其他专有名称在合理情况下均明确指定为此类名称。

3.5. No Duty to Publish
3.5. 没有出版的义务

The Contributor, and each named co-Contributor, acknowledges that the IETF has no duty to publish or otherwise use or disseminate any Contribution. The IETF reserves the right to withdraw or cease using any Contribution that does not comply with the requirements of Section 3.4 and Section 3.3 or 4.2.

投稿人和各指定共同投稿人承认,IETF没有义务发布或以其他方式使用或传播任何投稿。IETF保留撤回或停止使用不符合第3.4节和第3.3或4.2节要求的任何出资的权利。

3.6. Trademarks
3.6. 商标

Contributors, and each named co-Contributor, who claim trademark rights in terms used in their IETF Contributions are requested to state specifically what conditions apply to implementers of the technology relative to the use of such trademarks. Such statements

要求在IETF贡献中使用的术语主张商标权的贡献者和每个指定的共同贡献者具体说明与使用此类商标相关的技术实现者适用的条件。这种说法

should be submitted in the same way as is done for other intellectual property claims. (See [RFC3979] Section 6.)

应以与提交其他知识产权索赔相同的方式提交。(参见[RFC3979]第6节。)

4. Rights in RFC Editor Contributions
4. RFC编辑器贡献中的权限

The following are the rights the IETF, as the publisher of Internet-Drafts, requires in all RFC Editor Contributions:

以下是IETF作为Internet草稿的发布者在所有RFC编辑器贡献中所要求的权利:

4.1. Requirements from Section 3
4.1. 第3节的要求

All RFC Editor Contributions must meet the requirements of Sections 3.1, 3.2, 3.4, 3.5 and 3.6.

所有RFC编辑投稿必须满足第3.1、3.2、3.4、3.5和3.6节的要求。

4.2. Granting of Rights and Permissions
4.2. 授予权利和许可

By submission of an RFC Editor Contribution, each person actually submitting the RFC Editor Contribution, and each named co-Contributor, is deemed to agree to the following terms and conditions, and to grant the following rights, on his or her own behalf and on behalf of the organization the Contributor represents or is sponsored by (if any) when submitting the RFC Editor Contribution.

通过提交RFC编辑贡献,实际提交RFC编辑贡献的每个人和每个指定的共同贡献者被视为同意以下条款和条件,并代表其本人和贡献者所代表或赞助的组织(如有)授予以下权利提交RFC编辑器贡献时。

a. To the extent that an RFC Editor Contribution or any portion thereof is protected by copyright and other rights of authorship, the Contributor, and each named co-Contributor, and the organization he or she represents or is sponsored by (if any) grant a perpetual, irrevocable, non-exclusive, royalty-free, world-wide right and license to the ISOC and the IETF under all intellectual property rights in the RFC Editor Contribution for at least the life of the Internet-Draft:

a. 在RFC编辑贡献或其任何部分受版权和其他作者权利保护的情况下,贡献者和每个指定共同贡献者,以及他或她所代表或赞助的组织(如有)授予永久、不可撤销、非排他性、免版税,根据RFC编辑器贡献中的所有知识产权,对ISOC和IETF的全球权利和许可,至少在互联网草稿的生命周期内:

(A) to copy, publish, display, and distribute the RFC Editor Contribution as an Internet-Draft,

(A) 要复制、发布、显示和分发RFC编辑器作为互联网草稿的贡献,

(B) to prepare or allow the preparation of translations of the RFC into languages other than English.

(B) 准备或允许准备将RFC翻译成英语以外的语言。

(C) unless explicitly disallowed in the notices contained in an RFC Editor Contribution (as per Section 5.2 below), to prepare derivative works (other than translations) that are based on or incorporate all or part of the RFC Editor Contribution, or comment upon it. The license to such derivative works not granting the ISOC and the IETF any more rights than the license to the original RFC Editor Contribution, and

(C) 除非RFC编辑贡献(根据下文第5.2节)中包含的通知明确禁止,否则准备基于或包含全部或部分RFC编辑贡献的衍生作品(翻译除外),或对其进行评论。此类衍生作品的许可证不授予ISOC和IETF比原始RFC编辑器贡献的许可证更多的权利,以及

(D) to reproduce any trademarks, service marks or trade names which are included in the RFC Editor Contribution solely in connection with the reproduction, distribution or publication of the RFC Editor Contribution and derivative works thereof as permitted by this paragraph. When reproducing RFC Editor Contributions, the IETF will preserve trademark and service mark identifiers used by the Contributor of the RFC Editor Contribution, including (TM) and (R) where appropriate.

(D) 复制RFC编辑贡献中包含的任何商标、服务商标或商号,仅与本段允许的RFC编辑贡献及其衍生作品的复制、分发或出版有关。在复制RFC编辑器贡献时,IETF将保留RFC编辑器贡献者使用的商标和服务标记标识符,包括(TM)和(R)(如适用)。

b. The Contributor grants the IETF and ISOC permission to reference the name(s) and address(es) of the Contributor(s) and of the organization(s) s/he represents or is sponsored by (if any).

b. 投稿人授予IETF和ISOC引用投稿人及其代表或赞助的组织(如有)的名称和地址的权限。

5. Notices Required in IETF Documents
5. IETF文件中要求的通知

The IETF requires that certain notices and disclaimers described in this Section 5 be reproduced verbatim in all IETF Documents (including copies, derivative works and translations of IETF Documents, but subject to the limited exceptions noted in Section 5.2). This requirement protects IETF and its participants from liabilities connected with these documents. The copyright notice also alerts readers that the document is an IETF Document, and that ISOC claims copyright rights to certain aspects of the document, such as its layout, the RFC numbering convention and the prefatory language of the document. This legend is not intended to imply that ISOC has obtained ownership of the IETF Contribution itself, which is retained by the author(s) or remains in the public domain, as applicable.

IETF要求在所有IETF文件(包括IETF文件的副本、衍生作品和译本,但受第5.2节所述有限例外情况的限制)中逐字复制本第5节所述的某些通知和免责声明。本要求保护IETF及其参与者免于承担与这些文件相关的责任。版权声明还提醒读者,该文件是IETF文件,ISOC声称对该文件的某些方面拥有版权,如其布局、RFC编号约定和该文件的序言语言。本图例并不意味着ISOC已获得IETF贡献本身的所有权,该贡献由作者保留或保留在公共领域(如适用)。

Each IETF Document must include the required notices described in this Section 5. The required notices are the following:

每个IETF文件必须包括第5节所述的必要通知。所需通知如下:

a. The IPR Disclosure Acknowledgement described in Section 5.1 (required in all Internet-Drafts). b. The Derivative Works Limitation described in Section 5.2 (for specific IETF Documents only). c. The Publication Limitation described in Section 5.3 (for specific types of Internet-Drafts only). d. The Copyright Notice described in Section 5.4 (for all IETF Documents). e. The Disclaimer described in Section 5.5 (for all IETF Documents).

a. 第5.1节中所述的知识产权披露确认书(所有互联网草案中都需要)。B第5.2节中描述的衍生作品限制(仅适用于特定IETF文件)。C第5.3节所述的出版限制(仅适用于特定类型的互联网草稿)。D第5.4节所述的版权声明(适用于所有IETF文件)。E第5.5节中描述的免责声明(适用于所有IETF文件)。

5.1. IPR Disclosure Acknowledgement (required in all Internet-Drafts only)

5.1. 知识产权披露确认书(仅在所有互联网草案中要求)

"By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79."

“通过提交本互联网草案,每位作者表示,根据BCP 79第6节,他或她知道的任何适用专利或其他知识产权权利要求已经或将被披露,他或她知道的任何专利或其他知识产权权利要求将被披露。”

5.2. Derivative Works Limitation
5.2. 衍生作品限制

If the Contributor desires to eliminate the IETF's right to make modifications and derivative works of an IETF Contribution (other than translations), one of the two of the following notices may be included in the Status of Memo section of an Internet-Draft and included in a published RFC:

如果投稿人希望取消IETF对IETF投稿进行修改和衍生作品(翻译除外)的权利,则以下两种通知之一可包含在互联网草稿的备忘录状态部分,并包含在已发布的RFC中:

a. "This document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English."

a. 本文件不得修改,也不得创作其衍生作品,除非以RFC形式发布并翻译成英语以外的其他语言

b. "This document may not be modified, and derivative works of it may not be created."

b. 本文件不得修改,也不得创作其衍生作品

In the cases of MIB or PIB modules and in other cases where the Contribution includes material that is meant to be extracted in order to be used, the following should be appended to statement 5.2 (a) or 5.2 (b):

在MIB或PIB模块的情况下,以及在其他情况下,如果贡献包括为了使用而提取的材料,则应在报表5.2(a)或5.2(b)中附加以下内容:

"other than to extract section XX as-is for separate use."

“除按原样提取第XX节以供单独使用外。”

Notice 5.2(a) is used if the Contributor intends for the IETF Contribution to be published as an RFC. Notice 5.2(b) is used along with the Publication Limitation in Section 5.3 when the Contributor does not intend for the IETF Contribution to be published as an RFC.

如果投稿人打算将IETF投稿发布为RFC,则使用通知5.2(a)。当投稿人不打算将IETF投稿作为RFC发布时,通知5.2(b)与第5.3节中的发布限制一起使用。

These notices may not be used with any standards-track document or with most working group documents, except as discussed in Section 7.3 below, since the IETF must retain change control over its documents and the ability to augment, clarify and enhance the original IETF Contribution in accordance with the IETF Standards Process.

这些通知不得与任何标准跟踪文件或大多数工作组文件一起使用,除非下文第7.3节中讨论过,因为IETF必须保留对其文件的变更控制,以及根据IETF标准流程增加、澄清和增强原始IETF贡献的能力。

Notice 5.2(a) may be appropriate when republishing standards produced by other (non-IETF) standards organizations, industry consortia or companies. These are typically published as Informational RFCs, and do not require that change control be ceded to the IETF. Basically, documents of this type convey information for the Internet community.

通知5.2(a)在重新发布其他(非IETF)标准组织、行业联盟或公司制定的标准时可能适用。这些文件通常作为信息RFC发布,不要求将变更控制权交给IETF。基本上,这类文档为互联网社区传递信息。

A fuller discussion of the rationale behind these requirements is contained in Section 7.3 below.

下文第7.3节对这些要求背后的理由进行了更全面的讨论。

5.3. Publication Limitation
5.3. 出版限制

If the Contributor only wants the IETF Contribution to be made available in an Internet-Draft (i.e., does not want the IETF Contribution to be published as an RFC) then the Contributor may include the following notice in the Status of Memo section of the Internet-Draft.

如果投稿人只希望IETF投稿在互联网草稿中可用(即,不希望IETF投稿作为RFC发布),则投稿人可在互联网草稿的备忘录状态部分包含以下通知。

"This document may only be posted in an Internet-Draft."

“此文档只能在Internet草稿中发布。”

This notice can be used on IETF Contributions that are intended to provide background information to educate and to facilitate discussions within IETF working groups but are not intended to be published as an RFCs.

本通知可用于旨在提供背景信息以进行教育和促进IETF工作组内讨论,但不打算作为RFCs发布的IETF贡献。

5.4. Copyright Notice (required for all IETF Documents)
5.4. 版权声明(所有IETF文件都需要)

(Normally placed at the end of the IETF Document.)

(通常放在IETF文件的末尾。)

"Copyright (C) The Internet Society (year).

“版权(C)互联网协会(年)。

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中包含的权利、许可和限制的约束,除其中规定外,作者保留其所有权利。”

Additional copyright notices are not permitted in IETF Documents except in the case where such document is the product of a joint development effort between the IETF and another standards development organization or the document is a republication of the work of another standards organization. Such exceptions must be approved on an individual basis by the IAB.

IETF文件中不允许附加版权声明,除非该文件是IETF与另一标准开发组织共同开发的产品,或者该文件是另一标准组织作品的再版。此类例外情况必须由IAB单独批准。

5.5. Disclaimer (required in all IETF Documents)
5.5. 免责声明(所有IETF文件中都需要)

(Normally placed at the end of the IETF Document after the copyright notice.)

(通常放在IETF文档末尾版权声明之后。)

"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."

“本文件及其包含的信息是按“原样”提供的,且提交人、他/她所代表或赞助的组织(如有),INTERNET SOCIETY和INTERNET ENGINEERING TASK FORCE不承担任何明示或暗示的担保,包括但不限于以下任何担保,即使用本文中的信息不会侵犯任何权利或对适销性或特定用途适用性的任何暗示担保。”

5.6. Exceptions
5.6. 例外情况

Notwithstanding the provisions of this Section 5, in certain limited cases an abbreviated notice may be placed on certain types of derivative works of IETF Documents in accordance with this Section 5.6.

尽管有第5节的规定,在某些有限的情况下,根据第5.6节的规定,可以在IETF文件的某些类型的衍生作品上放置一个简短的通知。

a. in MIB modules, PIB modules and similar material commonly extracted from IETF Documents, except for material that is being placed under IANA maintenance, the following abbreviated notice shall be included in the body of the material that will be extracted in lieu of the notices otherwise required by Section 5:

a. 在MIB模块、PIB模块和通常从IETF文件中提取的类似材料中,除正在进行IANA维护的材料外,以下缩写通知应包含在将提取的材料正文中,以代替第5节另行要求的通知:

"Copyright (C) The Internet Society <year>. This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices."

“版权所有(C)互联网协会<year>。此MIB模块的此版本是RFC XXXX的一部分;有关完整的法律通知,请参阅RFC本身。”

When the MIB or PIB module is the initial version of a module that is to be maintained by the IANA, the following abbreviated notice shall be included:

当MIB或PIB模块是IANA维护的模块的初始版本时,应包括以下简短通知:

         "Copyright (C) The Internet Society <year>.  The initial
         version of this MIB module was published in RFC XXXX; for full
         legal notices see the RFC itself.  Supplementary information
         may be available at:
         http://www.ietf.org/copyrights/ianamib.html."
        
         "Copyright (C) The Internet Society <year>.  The initial
         version of this MIB module was published in RFC XXXX; for full
         legal notices see the RFC itself.  Supplementary information
         may be available at:
         http://www.ietf.org/copyrights/ianamib.html."
        

For other types of components than "MIB", substitute "MIB module" with an appropriate identifier. In the case of MIB and PIB modules this statement should be placed in the DESCRIPTION clause of the MODULE-IDENTITY macro.

对于“MIB”以外的其他类型的组件,用适当的标识符替换“MIB模块”。对于MIB和PIB模块,此语句应放在MODULE-IDENTITY宏的DESCRIPTION子句中。

Variations of these abbreviated notices are not permitted except in cases where the material to be extracted is the product of a joint development effort between the IETF and another standards development organization or is a republication of the work of another standards organization. Such variations must be approved on an individual basis by the IAB.

除非要提取的材料是IETF和另一标准开发组织联合开发工作的产物,或者是另一标准开发组织工作的再版,否则不允许对这些缩写通知进行变更。此类变更必须由IAB单独批准。

b. short excerpts of IETF Documents presented in electronic help systems, for example, the DESCRIPTION clauses for MIB variables, do not need to include a copyright notice.

b. 电子帮助系统中提供的IETF文档的简短摘录,例如,MIB变量的描述条款,不需要包含版权声明。

6. Notices and Rights Required in RFC Editor Contributions
6. RFC编辑器投稿中要求的通知和权利

Since the IETF acts as publisher of Internet Drafts, even for Internet Drafts that are not intended to become part of the Standards Process, the following are required in all such drafts to protect the IETF and its processes. The RFC Editor may require additional notices.

由于IETF作为互联网草案的发布者,即使是不打算成为标准过程一部分的互联网草案,所有此类草案都需要以下内容来保护IETF及其过程。RFC编辑器可能需要额外的通知。

a. An IPR Disclosure Acknowledgement, identical to that specified in Section 5.1.

a. 知识产权披露确认书,与第5.1节规定的内容相同。

b. One of the following three copyright release statements:

b. 以下三种版权发布声明之一:

A. "By submitting this Internet-Draft, I accept the provisions of Section 3 of BCP 78."

A.“通过提交此互联网草案,我接受BCP 78第3节的规定。”

B. "By submitting this Internet-Draft, I accept the provisions of Section 4 of BCP 78."

B.“通过提交此互联网草案,我接受BCP 78第4节的规定。”

C. The Copyright Notice specified in Section 5.4 and the disclaimer specified in section 5.5.

C.第5.4节规定的版权声明和第5.5节规定的免责声明。

7. Exposition of Why These Procedures Are the Way They Are
7. 解释为什么这些程序是这样的
7.1. Rights Granted in IETF Contributions
7.1. IETF捐款中授予的权利

The IETF/ISOC must obtain the right to publish an IETF Contribution as an RFC or an Internet-Draft from the Contributors.

IETF/ISOC必须从贡献者处获得将IETF贡献作为RFC或互联网草稿发布的权利。

A primary objective of this policy is to obtain from the document authors only the non-exclusive rights that are needed to develop and publish IETF Documents and to use the IETF Contributions in the IETF Standards Process while leaving all other rights with the authors.

本政策的主要目标是仅从文件作者处获得开发和发布IETF文件以及在IETF标准过程中使用IETF贡献所需的非排他性权利,同时将所有其他权利留给作者。

The non-exclusive rights that the IETF needs are:

IETF需要的非排他性权利包括:

a. the right to publish the document b. the right to let the document be freely reproduced in the formats that the IETF publishes it in c. the right to let third parties translate it into languages other than English d. except where explicitly excluded (see Section 5.2), the right to make derivative works within the IETF process. e. the right to let third parties extract some logical parts, for example MIB modules

a. 发布文件的权利b。允许以IETF以c语言发布的格式自由复制文件的权利。有权让第三方将其翻译成英语以外的语言。除非明确排除(见第5.2节),在IETF过程中进行衍生作品的权利。E允许第三方提取某些逻辑部分的权利,例如MIB模块

The authors retain all other rights, but cannot withdraw the above rights from the IETF/ISOC.

作者保留所有其他权利,但不能从IETF/ISOC中撤销上述权利。

7.2. Rights to use Contributed Material
7.2. 使用捐赠材料的权利

Because, under the laws of most countries and applicable international treaties, copyright rights come into existence whenever a work of authorship is created (but see Section 8 below regarding public domain documents), and IETF cannot make use of IETF Contributions if it does not have sufficient rights with respect to these copyright rights, it is important that the IETF receive assurances from all Contributors that they have the authority to grant the IETF the rights that they claim to grant. Without this assurance, IETF and its participants would run a greater risk of liability to the owners of these rights.

因为,根据大多数国家的法律和适用的国际条约,只要创作了作者作品,版权就开始存在(但见下文第8节关于公共领域文件),如果IETF没有足够的版权,IETF就不能使用IETF的贡献,IETF必须得到所有贡献者的保证,即他们有权授予IETF他们声称授予的权利。如果没有这一保证,IETF及其参与者将面临对这些权利所有者承担责任的更大风险。

To this end, IETF asks Contributors to give the assurances in Section 3.4 above. These assurances are requested, however, only to the extent of the Contributor's reasonable and personal knowledge. (See Section 1(l))

为此,IETF要求贡献者提供上述第3.4节中的保证。然而,这些保证仅在出资人合理和个人了解的范围内提出。(见第1(l)条)

7.3. Right to Produce Derivative Works
7.3. 创作衍生作品的权利

The IETF needs to be able to evolve IETF Documents in response to experience gained in the deployment of the technologies described in such IETF Documents, to incorporate developments in research and to react to changing conditions on the Internet and other IP networks. In order to do this the IETF must be able to produce derivatives of its documents; thus the IETF must obtain the right from Contributors to produce derivative works. Note though that the IETF only requires this right for the production of derivative works within the IETF Standards Process. The IETF does not need, nor does it obtain, the right to let derivative works be created outside of the IETF Standards Process other than as noted in Section 3.3 (E).

IETF需要能够根据在此类IETF文件中描述的技术部署过程中获得的经验,发展IETF文件,将研究进展纳入其中,并对互联网和其他IP网络上不断变化的条件作出反应。为了做到这一点,IETF必须能够产生其文件的衍生产品;因此,IETF必须从贡献者那里获得创作衍生作品的权利。但请注意,IETF仅要求在IETF标准流程内制作衍生作品时享有该权利。除第3.3(E)节所述外,IETF不需要也不获得在IETF标准流程之外创建衍生作品的权利。

The right to produce derivative works is required for all IETF standards track documents and for most IETF non-standards track documents. There are two exceptions to this requirement: documents describing proprietary technologies and documents that are republications of the work of other standards organizations.

所有IETF标准跟踪文件和大多数IETF非标准跟踪文件均要求有权制作衍生作品。此要求有两个例外:描述专有技术的文件和其他标准组织工作的再版文件。

The right to produce derivative works must be granted in order for an IETF working group to accept an IETF Contribution as a working group document or otherwise work on it. For non-working group IETF Contributions where the Contributor requests publication as a standards track RFC the right to produce derivative works must be granted before the IESG will issue an IETF Last-Call and, for most non-standards track non-working group IETF Contributions, before the IESG will consider the Internet-Draft for publication.

为了使IETF工作组接受IETF贡献作为工作组文件或以其他方式进行工作,必须授予制作衍生作品的权利。对于非工作组IETF的贡献,其中贡献者要求出版作为标准轨道RFC,在IESG将发出IETF最后呼叫之前,必须授予生产衍生作品的权利,并且对于大多数非标准轨道非工作组IETF贡献,在IESG将考虑互联网出版的草案之前。

Occasionally a Contributor may not want to grant publication rights or the right to produce derivative works before finding out if an IETF Contribution has been accepted for development in the IETF Standards Process. In these cases the Contributor may include the Derivative Works Limitation described in Section 5.2 and the Publication Limitation described in Section 5.3 in their IETF Contribution. A working group can discuss the Internet-Draft with the aim to decide if it should become a working group document, even though the right to produce derivative works or to publish the IETF Contribution as an RFC has not yet been granted. If the IETF Contribution is accepted for development the Contributor must then resubmit the IETF Contribution without the limitation notices before a working group can formally adopt the IETF Contribution as a working group document.

有时,在发现IETF贡献是否已被接受用于IETF标准过程中的开发之前,贡献者可能不想授予出版权或创作衍生作品的权利。在这些情况下,投稿人可在其IETF投稿中包括第5.2节所述的衍生作品限制和第5.3节所述的出版限制。工作组可以讨论互联网草案,目的是决定它是否应成为工作组文件,即使尚未授予制作衍生作品或以RFC形式发布IETF贡献的权利。如果IETF贡献被接受用于开发,那么贡献者必须在工作组正式将IETF贡献作为工作组文件之前,重新提交IETF贡献,而无限制通知。

The IETF has historically encouraged organizations to publish details of their technologies, even when the technologies are proprietary, because understanding how existing technology is being used helps when developing new technology. But organizations that publish information about proprietary technologies are frequently not willing to have the IETF produce revisions of the technologies and then claim that the IETF version is the "new version" of the organization's technology. Organizations that feel this way can specify that an IETF Contribution can be published with the other rights granted under this document but may withhold the right to produce derivative works other than translations. The right to produce translations is required before any IETF Contribution can be published as an RFC to ensure the widest possible distribution of the material in RFCs.

IETF历来鼓励组织发布其技术的详细信息,即使这些技术是专有的,因为了解现有技术的使用方式有助于开发新技术。但是,发布专有技术信息的组织通常不愿意让IETF对这些技术进行修订,然后声称IETF版本是该组织技术的“新版本”。认为这种方式的组织可以指定IETF贡献可以与本文件授予的其他权利一起发布,但可以保留产生除翻译以外的衍生作品的权利。在IETF的任何贡献可以作为RFC出版之前,需要有翻译权,以确保在RFC中尽可能广泛地分发材料。

In addition, IETF Documents frequently make normative references to standards or recommendations developed by other standards organizations. Since the publications of some standards organizations are not public documents, it can be quite helpful to the IETF to republish, with the permission of the other standards organization, some of these documents as RFCs so that the IETF community can have open access to them to better understand what they are referring to. In these cases the RFCs can be published without the right for the IETF to produce derivative works.

此外,IETF文件经常引用其他标准组织制定的标准或建议。由于一些标准组织的出版物不是公共文件,因此,在其他标准组织的许可下,将其中一些文件重新发布为RFC对IETF非常有帮助,以便IETF社区可以公开访问这些文件,以便更好地理解它们所指的内容。在这些情况下,RFC可以在IETF无权制作衍生作品的情况下发布。

In both of the above cases in which the production of derivative works is excluded, the Contributor must include a special legend in the IETF Contribution, as specified in Section 5.2, in order to notify IETF participants about this restriction.

在上述两种不包括衍生作品制作的情况下,投稿人必须按照第5.2节的规定在IETF投稿中包含特殊图例,以便将此限制通知IETF参与者。

7.4. Rights to Use Trademarks
7.4. 商标使用权

Contributors may wish to seek trademark or service mark protection on any terms that are coined or used in their IETF Contributions. IETF makes no judgment about the validity of any such trademark rights. However, the IETF requires each Contributor, under the licenses described in Section 3.3 above, to grant IETF a perpetual license to use any such trademarks or service marks solely in exercising its rights to reproduce, publish and modify the IETF Contribution. This license does not authorize any IETF participant to use any trademark or service mark in connection with any product or service offering, but only in the context of IETF Documents and discussions.

贡献者可能希望根据IETF贡献中创造或使用的任何条款寻求商标或服务商标保护。IETF不对任何此类商标权的有效性做出判断。然而,IETF要求每个贡献者根据上述第3.3节所述的许可证,授予IETF永久许可证,仅在行使其复制、发布和修改IETF贡献的权利时使用任何此类商标或服务标记。本许可证不授权任何IETF参与者在任何产品或服务提供中使用任何商标或服务标记,但仅在IETF文件和讨论中使用。

7.5. Who Does This Apply To?
7.5. 这适用于谁?

Rights and licenses granted to the IETF under this document are granted to all individuals noted in Section 1(a), irrespective of their employment or institutional affiliation. However, these licenses do not extend broadly to the employers, sponsors or institutions of such individuals, nor do they authorize the individuals to exercise any rights outside the specific context of the IETF Standards Process.

根据本文件授予IETF的权利和许可证授予第1(a)节所述的所有个人,无论其就业或机构隶属关系如何。然而,这些许可证并不广泛适用于此类个人的雇主、赞助者或机构,也不授权这些个人在IETF标准过程的特定环境之外行使任何权利。

8. Contributions Not Subject to Copyright
8. 不受版权限制的贡献

Certain documents, including those produced by the U.S. government and those which are in the public domain, may not be protected by the same copyright and other legal rights as other documents. Nevertheless, we ask each Contributor to grant to the IETF the same rights as he or she would grant, and to make the same representations, as though the IETF Contribution were protected by the same legal rights as other documents, and as though the Contributor could be able to grant these rights. We ask for these grants and representations only to the extent that the Contribution may be protected. We believe they are necessary to protect the ISOC, the IETF, the IETF Standards Process and all IETF participants, and also because the IETF does not have the resources or wherewithal to make any independent investigation as to the actual proprietary status of any document submitted to it.

某些文件,包括美国政府制作的文件和属于公共领域的文件,可能不受与其他文件相同的版权和其他法律权利的保护。尽管如此,我们要求每位贡献者向IETF授予他或她将授予的相同权利,并做出相同的陈述,就好像IETF贡献与其他文件一样受到相同法律权利的保护,就好像贡献者能够授予这些权利一样。我们仅在捐款可能受到保护的情况下才要求这些赠款和陈述。我们认为,为了保护ISOC、IETF、IETF标准过程和所有IETF参与者,以及IETF没有资源或资金对提交给它的任何文件的实际所有权状态进行任何独立调查,它们是必要的。

9. Security Considerations
9. 安全考虑

This memo relates to IETF process, not any particular technology. There are security considerations when adopting any technology, but there are no known issues of security with IETF Contribution rights policies.

本备忘录涉及IETF过程,而非任何特定技术。采用任何技术时都会考虑到安全问题,但IETF贡献权策略不存在已知的安全问题。

10. References
10. 工具书类
10.1. Normative References
10.1. 规范性引用文件

[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月。

[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.

[RFC2028]Hovey,R.和S.Bradner,“参与IETF标准过程的组织”,BCP 11,RFC 2028,1996年10月。

[RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3979, March 2005.

[RFC3979]Bradner,S.,Ed,“IETF技术中的知识产权”,BCP 79,RFC 3979,2005年3月。

10.2. Informative References
10.2. 资料性引用
   [Berne]    "Berne Convention for the Protection of Literary and
              Artistic Work",
              http://www.wipo.int/edocs/trtdocs/en/wo/wo001en.htm
        
   [Berne]    "Berne Convention for the Protection of Literary and
              Artistic Work",
              http://www.wipo.int/edocs/trtdocs/en/wo/wo001en.htm
        
11. Acknowledgements
11. 致谢

The editor would like to acknowledge the help of the IETF IPR Working Group and, in particular the help of Jorge Contreras of Hale and Dorr for his careful legal reviews of this and other IETF IPR-related and process documents. The editor would also like to acknowledge the extensive help John Klensin provided during the development of the document.

编辑要感谢IETF知识产权工作组的帮助,特别是Hale和Dorr的Jorge Contreras对本文件和其他IETF知识产权相关文件和过程文件进行了仔细的法律审查。编辑还想感谢John Klesin在文件编制过程中提供的广泛帮助。

Editor's Address

编辑地址

Scott Bradner Harvard University 29 Oxford St. Cambridge MA, 02138

斯科特·布拉德纳哈佛大学马萨诸塞州牛津圣剑桥29号,邮编02138

   Phone: +1 617 495 3864
   EMail: sob@harvard.edu
        
   Phone: +1 617 495 3864
   EMail: sob@harvard.edu
        

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