IETF Rights in Contributions
RFC 3667
| Document | Type |
RFC - Best Current Practice
(February 2004; No errata)
Obsoleted by RFC 3978
Updates RFC 2026
|
|
|---|---|---|---|
| Last updated | 2013-03-02 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3667 (Best Current Practice) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Harald Alvestrand | ||
| Send notices to | <smb@research.att.com>, <sra@hactrn.net> | ||
Network Working Group S. Bradner
Request for Comments: 3667 Harvard University
BCP: 78 February 2004
Updates: 2026
Category: Best Current Practice
IETF Rights in Contributions
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 (2004). All Rights Reserved.
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 3668, replaces Section 10 of RFC
2026.
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
5.3. Publication Limitation . . . . . . . . . . . . . . . . . 11
Bradner Best Current Practice [Page 1]
RFC 3667 IETF Rights in Submissions February 2004
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
12. Editor's Address . . . . . . . . . . . . . . . . . . . . . . . 17
13. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 18
1. Definitions
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 [RFC 2028].
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.
b. "IETF Standards Process": the activities undertaken by the IETF in
any of the settings described in 1(c) below.
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
Show full document text