view Side-By-Side changes
Network Working Group S. Bradner
Internet-Draft Harvard University
Editor
April
June 2003
IETF Rights in Submissions
<draft-ietf-ipr-submission-rights-04.txt> Contributions
<draft-ietf-ipr-submission-rights-05.txt>
Status of this Memo
This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Abstract
The IETF policies about rights in submissions Contributions to the IETF are
designed to ensure that IETF contributions such Contributions can be made available to
the IETF and Internet communities while permitting the authors to
retain as many rights in the document as possible. This memo details the IETF
policies on rights in submissions Contributions to the IETF. It also describes
the objectives that the policies are designed to meet. This memo
updates RFC 2026, and and, with RFC XXXY, replaces Section 10 of RFC
2026. [note to RFC editor: replace XXXY with number of IETF IPR]
Copyright (C) The Internet Society. (2003)
1. Introduction
Under the laws
Table of most countries and current international treaties
(for example the "Berne Convention for the Protection Contents
Status 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 this Memo.................................................1
Abstract............................................................1
1. Definitions ....................................................1
2. Introduction....................................................1
Bradner [Page 1]
Internet-Draft IETF Rights in Submissions April June 2003
author produces a work within the scope of his or her employment,
most
3. Rights in IETF Contributions....................................1
3.1 General Policy...............................................1
3.2 Confidentiality Obligations..................................1
3.3 Granting of those rights are usually assigned Rights and Permissions...........................1
3.4 Representations and Warranties...............................1
3.5 No Duty to the employer, either by
operation Publish...........................................1
3.6 Trademarks...................................................1
4. Rights in RFC Editor Contributions...............................1
4.1 Requirements from Section 3.................................1
4.2 Granting of law or, Rights and Permissions..........................1
5. Notices Required in many cases, under contract. (The Berne
Convention names some rights as "inalienable", which means that the
author retains them IETF Documents..............................1
5.1 IPR Disclosure Acknowledgement................................1
5.2 Derivative Works Limitation...................................1
5.3 Publication Limitation........................................1
5.4 Copyright Notice .............................................1
5.5 Disclaimer ...................................................1
5.6 Exceptions....................................................1
6. Notices and Rights Required in all cases.)
In order for works to be used within RFC Editor Contributions.........1
7. Exposition of why these procedures are the IETF process, certain
limited rights way they are.........1
7.1 Rights Granted in all Contributions...............................1
7.2 Rights to use Contributed Material............................1
7.3 Right to Produce Derivative Works.............................1
7.4 Rights to use Trademarks......................................1
7.5 Who Does This Apply To?.......................................1
8. Contributions must be granted Not Subject to Copyright..........................1
9. Security Considerations.........................................1
10. References......................................................1
10.1 Normative References.........................................1
10.1 Informative References.......................................1
11. Acknowledgements................................................1
12. Editor's Address................................................1
13. Full copyright statement........................................1
1. Definitions
The following definitions are for terms used in the IETF context of this
document. Other terms, including "IESG," "ISOC," "IAB" and
Internet Society (ISOC). "RFC
Editor," are defined in [RFC 2028].
a. "IETF": In addition, Contributors must make
representations to the context of this document, the IETF and ISOC regarding their ability to grant
these rights. These necessary rights and representations have until
now been laid out includes all
individuals who participate in Section 10 of [RFC 2026]. In meetings, working groups, mailing
lists, functions and other activities which are organized or
initiated by ISOC, the years since
[RFC 2026] was published there have been a number of times when IESG or the
exact intent of Section 10 has been IAB under the subject general
designation of vigorous debate
within the IETF community. The aim of this document is Internet Engineering Task Force or IETF, but
solely to clarify
various ambiguities in Section 10 the extent of [RFC 2026] that led to these
debates and to amplify such participation.
b. "IETF Standards Process": the policy in order to clarify what activities undertaken by the IETF
is currently doing.
Sections 2 and 3 in
any of this document address the rights settings described in submissions 1(c) below.
Bradner [Page 2]
Internet-Draft IETF Rights in Submissions June 2003
c. "IETF Contribution": any submission to the IETF previously covered intended by Section 10 of [RFC 2026] the
Contributor for publication as an Internet-Draft or RFC (except
for RFC Editor Contributions described below) and any statement
made within the
"Note Well" explanatory text presented at many context of an IETF activities.
Section 4 gives definitions used Standards Process. Such
statements include oral statements in describing these policies.
Sections 5, 6 IETF sessions, as well as
written and 7 then explain electronic communications made at any time or place,
which are addressed to:
o the rationale for these provisions,
including some IETF plenary session,
o any IETF working group or portion thereof,
o the IESG, or any member thereof on behalf of the clarifications that have become understood
since IESG,
o the adoption IAB or any member thereof on behalf of [RFC 2026]. The rules and procedures set out
in this document are not intended to substantially modify the IAB,
o any IETF mailing list, including the IETF list itself, any
working group or alter design team list, or any other list
functioning under IETF auspices,
o the IETF's current policy toward RFC Editor or the Internet-Drafts function (except for RFC
Editor Contributions described below).
Statements made to the IETF.
A companion document [IETF IPR] will deal with rights in technologies
developed or specified as part outside of the an IETF process. This document is session, mailing list or other
function, that are clearly not intended to address those issues.
The rights addressed in this document fall into the following
categories:
o rights be input to make use of contributed material
o copyrights in an IETF documents
o rights to produce derivative works
o rights to use trademarks
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
activity, group or the rights of the IETF in any function, are not Contributions they make.
Bradner [Page 2]
Internet-Draft IETF Rights in Submissions April 2003
2. Rights the context
of this document.
d. "Internet-Draft": temporary documents used in the IETF Submissions
2.1. General Policy
In all matters of copyright and document procedures, RFC
Editor processes. Internet-Drafts are posted on the intent is to
benefit IETF web site
by the Internet community IETF Secretariat and have a nominal maximum lifetime in the
Secretariat's public at large, while
respecting the legitimate rights directory of others.
2.2 Confidentiality Obligations
No Contribution that is subject to any requirement of confidentiality
or any restriction 6 months, after which they are
removed. Note that Internet-Drafts are archived many places on its dissemination may be considered in any part
of
the IETF Standards Process, and there must be no assumption Internet, not all of any
confidentiality obligation with respect to any such Contribution.
Each Contributor agrees that any statement in a Contribution, whether
generated automatically or otherwise, that states or implies these places remove expired Internet-
Drafts. Internet-Drafts that are under active consideration by
the
Contribution IESG are not removed from the Secretariat's public directory
until that consideration is confidential or subject to any privilege, complete. In addition, the author of
an Internet-Draft can request that the lifetime in the
Secretariat's public directory be
disregarded extended before the expiration.
e. "RFC": the basic publication series for all purposes, and will be of no force or effect.
2.3. Granting of Rights and Permissions
By submission of a Contribution, each person actually submitting the
Contribution, and each named co-contributor, is deemed to agree to IETF. RFCs are
published by the following terms and conditions, RFC Editor and once published are never modified.
(See [RFC 2026] Section 2.1)
f. "RFC Editor Contribution": An Internet-Draft intended by the
Contributor to be submitted to grant the following
rights, on his RFC Editor for publication as
an Informational or her own behalf and on behalf Experimental RFC but not intended to be part
of the organization IETF Standards Process.
g. "IETF Internet-Drafts": Internet-Drafts other than RFC Editor
Contributions. Note that under Section 3.3(a) the contributor represents or grant of rights
in regards to IETF Internet-Drafts as specified in this document
is sponsored by (if any) when
submitting perpetual and irrevocable and thus survives the Contribution.
a. To the extent that Secretariat's
removal of an Internet-Draft from the Contribution or any portion thereof is
protected public directory, except as
Bradner [Page 3]
Internet-Draft IETF Rights in Submissions June 2003
limited by copyright Section 3.3(a)(C). (See [RFC 2026] Sections 2.2 and 8)
h. "RFC Editor Internet-Drafts": Internet-Drafts that are RFC Editor
Contributions.
i. "IETF Documents": RFCs and Internet-Drafts except for Internet-
Drafts that are RFC Editor Contributions and other rights of authorship, the
Contributor, RFCs that are
published from them.
j. "RFC Editor Documents": RFCs and each named co-contributor, Internet-Drafts that are RFC
Editor Contributions and the organization
he or she represents or is sponsored by (if any) grant RFCs that may be published from them.
k. "Contribution": IETF Contributions and RFC Editor Contributions
l. "Contributor": an individual submitting a
perpetual, irrevocable, non-exclusive, royalty-free, world-wide
right Contribution
m. "Reasonably and license personally known": means something an individual
knows personally or, because of the job the individual holds,
would reasonably be expected to know.
2. Introduction
Under the ISOC laws of most countries and current international treaties
(for example the IETF under all intellectual
property "Berne Convention for the Protection of Literary and
Artistic Work" [Berne]), authors obtain numerous rights in the Contribution:
(A) to copy, publish, display works
they produce automatically upon producing them. These rights include
copyrights, moral rights and distribute the contribution as
part of the IETF standards process,
(B) unless explicitly disallowed in other rights. In many cases, if the written terms of
author produces a work within the
Contribution [pursuant to one scope of the notices contained in
Section 3.3 below], to prepare derivative works that are based
on or incorporate all his or part her employment,
most of those rights are usually assigned to the Contribution within 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.)
This document details the rights that the IETF standards process, requires in IETF
Contributions and rights the license to IETF, as publisher of Internet-Drafts,
requires in all such derivative Drafts including RFC Editor Contributions. The
RFC Editor may also define additional rights required for RFC Editor
Contributions.
In order for works to be of a scope no wider than used within the license IETF Standards Process or to
be published as Internet-Drafts, certain limited rights in all
Contributions must be granted to the original
Contribution, IETF and
(C) Internet Society
(ISOC). In addition, Contributors must make representations to reproduce any trademarks, service marks or trade names 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 [RFC 2026]. In the years since [RFC 2026] was published
there have been a number of times when the exact intent of Section 10
Bradner [Page 3] 4]
Internet-Draft IETF Rights in Submissions April June 2003
which are included in the Contribution solely in connection
with
has been the reproduction, distribution or publication subject of the
Contribution and derivative works thereof as permitted by this
paragraph. When reproducing Contributions, vigorous debate within the IETF will
preserve trademark and service mark identifiers community.
The aim of this document is to clarify various ambiguities in the format
used by the Contributor Section
10 of the contribution, including (tm) and
(r) where appropriate.
b. The Contributor grants the IETF [RFC 2026] that led to these debates and ISOC permission to reference amplify the name(s) and address(es) of policy
in order to clarify what the contributor(s) IETF is currently doing.
Section 1 gives definitions used in describing these policies.
Sections 3, 4 and 5 of this document address the
organization(s) s/he represents or is sponsored rights in
Contributions previously covered by (if any).
c. Every copy Section 10 of an IETF document made pursuant to [RFC 2026] and the licenses
granted under paragraph (a)(A) above,
"Note Well" explanatory text presented at many IETF activities.
Sections 6 and all derivative works
made pursuant to 7 then explain the licenses granted under paragraph (a)(B)
above, must include, in unaltered form, rationale for these provisions,
including some of the notices included in
such Contribution pursuant to Section 3 below.
2.4 Representations and Warranties. With respect to each Contribution,
each Contributor represents clarifications that to have become understood
since the best adoption of his or her knowledge
and ability:
a. [RFC 2026]. The contribution properly acknowledges all major Contributors. A
major Contributor is any person who has materially or
substantially contributed to the Contribution.
b. No information in the Contribution is confidential and the IETF,
ISOC, rules and its affiliated organizations may freely disclose any
information procedures set out
in the Contribution.
c. There this document are no limits not intended to substantially modify or alter
the Contributor's ability to make IETF's current policy toward Contributions.
A companion document [IETF IPR] will deal with rights in technologies
developed or specified as part of the
grants, acknowledgments and agreements herein that are reasonably
and personally known IETF process. This document is
not intended to the Contributor.
d. address those issues.
The Contributor has not intentionally included rights addressed in this document fall into the
Contribution any following
categories:
o rights to make use of contributed material which is defamatory or untrue or which
o copyrights in IETF documents
o rights to produce derivative works
o rights to use trademarks
This document is illegal under 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 laws rights of the jurisdiction IETF in which any
Contributions they make.
3. Rights in IETF Contributions
The following are the
Contributor has his or her principal place rights the IETF requires in all IETF
Contributions:.
3.1 General Policy
In all matters of business or
residence.
e. All trademarks, trade names, service marks copyright and other proprietary
names used in document procedures, the Contribution and personally and reasonably known intent is to
benefit the Contributor are clearly designated as such where
reasonable.
2.5 The Contributor, Internet community and each named co-contributor, acknowledges that the IETF has no duty to publish or otherwise use or disseminate any
Contribution. The IETF reserves public at large, while
respecting the right legitimate rights of others.
3.2 Confidentiality Obligations
No information or document that is subject to withdraw any requirement of
confidentiality or cease using any restriction on its dissemination may be
Bradner [Page 4] 5]
Internet-Draft IETF Rights in Submissions April June 2003
any
submitted as an Contribution that does not comply with the requirements of
Sections 2.3 and 2.4 above.
2.6 Contributors, and each named co-contributor, who claim trademark
rights to terms or otherwise considered in their contributions are requested to specifically
state what conditions apply to implementers any part of
the technology
relative to the use Standards Process, and there must be no assumption of any claimed trademarks. Such statements
should be submitted in the same way as is done for other intellectual
property claims. (See [IETF IPR] sec 6.)
3. Copyright notice required in IETF Documents
The IETF requires
confidentiality obligation with respect to any Contribution. Each
Contributor agrees that a copyright notice and disclaimer be
reproduced verbatim any statement in all IETF Documents. This requirement protects
IETF and its participants from liabilities connected with these
documents. The copyright notice also alerts readers an Contribution, whether
generated automatically or otherwise, that states or implies that the
document
Contribution is an IETF document, confidential or subject to any privilege, can be
disregarded for all purposes, and that ISOC claims copyright rights
in certain aspects will be of the document, such as its layout, the RFC
numbering convention no force or effect.
3.3 Granting of Rights and the prefatory language Permissions
By submission of an Contribution, each person actually submitting the document.
This legend
Contribution, and each named co-Contributor, is not intended deemed to agree to imply that ISOC has obtained ownership
of
the contribution itself, which is retained by following terms and conditions, and to grant the author(s) following
rights, on his or
remains in the public domain, as applicable.
Additional copyright notices are not permitted in IETF documents
except in her own behalf and on behalf of the case where organization
the document Contributor represents or is sponsored by (if any) when
submitting the product of a joint
development effort between Contribution.
a. To the IETF and another standards development
organization. Such exceptions must be approved on extent that an individual
basis Contribution or any portion thereof is
protected by the IAB.
3.1 Copyright notice copyright and disclaimer
One other rights of authorship, the following two copyright notice
Contributor, and each named co-contributor, and disclaimers shall be
included at the end of all IETF documents.
3.1.1 Notice for documents where 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 produce derivative works
has not been withheld. (See sec 5.3 for a discussion on derivative
works.)
"Copyright (C) The Internet Society (year). Except as set forth
below, authors retain the ISOC and the IETF under all their rights.
This document intellectual
property rights in the Contribution.
(A) to copy, publish, display and distribute the Contribution as
part of the IETF Standards Process or as an Internet-Draft,
(B) to prepare or allow the preparation of translations of it may be copied and furnished the
Contribution into languages other than English,
(C) unless explicitly disallowed in the notices contained in an
Contribution [as per Section 5.2 below], to
others, and prepare derivative
works (other than translations) that comment are based on or otherwise explain it
incorporate all or assist in its implementation may part of the Contribution, or comment upon
it, within the IETF Standards Process, the license to such
derivative works to be prepared, copied, published of a scope no wider than the license to
the original Contribution, and distributed, in whole
(D) to reproduce any trademarks, service marks or trade names
which are included in part, without restriction the Contribution solely in connection
with the reproduction, distribution or publication of any
kind, provided that the above copyright notice
Contribution and derivative works thereof as permitted by this paragraph are
paragraph. When reproducing Contributions, the IETF will
preserve trademark and service mark identifiers in the format
used by the Contributor of the Contribution, including (TM) and
(R) where appropriate.
Bradner [Page 5] 6]
Internet-Draft IETF Rights in Submissions April June 2003
included on all such copies
(E) To extract, copy, publish, distribute, modify and derivative works. However, this
document itself may not be modified in incorporate
into other works, for any way, such as by removing
the copyright notice or references purpose (and not limited to use
within the Internet Society IETF Standards Process) any executable code or other
Internet organizations, except code
fragments that are included in any IETF Document (such as needed for MIB
and PIB modules), subject to the purpose requirements of
developing Internet standards in which case the procedures for rights
in submissions defined in Section 5 (it
also being understood that the IETF Standards Process must licenses granted under this
paragraph (E) shall not be
followed, or as required deemed to translate it into languages grant any right under any
patent, patent application or other than
English. similar intellectual
property right disclosed by the Contributor under [IPR DOC]).
b. The limited permissions granted above are perpetual Contributor grants the IETF and will not be
revoked 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).
3.4 Representations and Warranties.
With respect to each Contribution, each Contributor represents that
to the Internet Society best of his or its successors her knowledge and ability:
a. The Contribution properly acknowledges all major Contributors. A
major Contributor is any person who has materially or assigns.
This document
substantially contributed to the Contribution.
b. No information in the Contribution is confidential and the IETF,
ISOC, and its affiliated organizations may freely disclose any
information contained in the Contribution.
c. There are no limits to the Contributor's ability to make the
grants, acknowledgments and agreements herein is provided on an
"AS IS" basis that are reasonably
and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
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."
3.1.2 Notice for documents personally known to the Contributor.
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.
e. All trademarks, trade names, service marks and other proprietary
names used in the Contribution and personally and reasonably known
to the Contributor are clearly designated as such where
reasonable.
3.5 No Duty to Publish
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 produce derivative works
has been withheld. (See sec 5.3 withdraw or cease using
any Contribution that does not comply with the requirements of
Bradner [Page 7]
Internet-Draft IETF Rights in Submissions June 2003
Section 3.4 and Section 3.3 or 4.2.
3.6 Trademarks
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
should be submitted in the same way as is done for a discussion on derivative
works.)
"Copyright (C) other intellectual
property claims. (See [IETF IPR] Section 6.)
4. Rights in RFC Editor Contributions
The Internet Society (year). Except following are the rights the IETF, as set forth
below, authors retain the publisher of Internet-
Drafts, requires in all their rights.
This document RDC Editor Contributions:
4.1 Requirements from Section 3
All RFC Editor Contributions must meet the requirements of Sections
3.1, 3.2, 3.4, 3.5 and translations 3.6.
4.2 Granting of it may be copied Rights and Permissions
By submission of an 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 an Contribution or any portion thereof is
protected by copyright and other rights of authorship, the
Contributor, and each named co-contributor, and furnished the organization
he or she represents or is sponsored by (if any) grant a non-
exclusive, royalty-free, world-wide right and license to
others provided that the above copyright notice ISOC
and this paragraph
are included on the IETF under all such copies. However, this document itself may
not be modified intellectual property rights in any way, such as by removing the copyright notice
or references
Contribution for at least the life of the Internet-Draft:
(A) to copy, publish, display and distribute the Internet Society or other Internet
organizations, except Contribution as required
an Internet-Draft,
(B) unless explicitly disallowed in the notices contained in an
Contribution (as per Section 5.4 below), to translate it into languages
other prepare derivative
works (other than English.
The limited permissions granted above translations) that are perpetual and will not be
revoked by the Internet Society based on or its successors
incorporate all or assigns.
This document and part of the information contained herein is provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
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."
3.2 Notices re. Derivative Works Contribution, or comment upon it
the license to such derivative works to be of a scope no wider
than the license to the original Contribution, and
Bradner [Page 8]
Internet-Draft IETF Rights in Submissions June 2003
(C) to reproduce any trademarks, service marks or trade names
which are included in the Contribution solely in connection
with the reproduction, distribution or publication rights.
Bradner [Page 6]
Internet-Draft of the
Contribution and derivative works thereof as permitted by this
paragraph. When reproducing Contributions, the IETF Rights will
preserve trademark and service mark identifiers in Submissions April 2003
In addition to the foregoing, each format
used by the Contributor of the Contribution, including (TM) and
(R) where appropriate.
b. The Contributor grants the IETF Internet-Draft must contain
one and ISOC permission to reference
the name(s) and address(es) of the following three Contributor(s) and of the
organization(s) s/he represents or is sponsored by (if any).
5. Notices Required in IETF Documents
The IETF requires that certain notices regarding and disclaimers described in
this Section 5 be reproduced verbatim in all IETF Documents
(including copies, derivative works and
publication rights on it's first page: (See sec 5.3 for a discussion
on derivative works.)
a. 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 Internet-Draft IETF Document, and is subject to all
provisions of section 2 of RFC XXXX. By submitting this Internet-
Draft, I certify that any applicable patent or other IPR
ISOC claims of
which I am aware have been disclosed copyright rights in accordance with certain aspects of the document, such
as its layout, the RFC XXXY.
b. numbering convention and the prefatory
language of the document. This document legend is an Internet-Draft 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.
Each IETF Document must include the required notices described in
this Section 5. The required notices are the following:
a. The IPR Disclosure Acknowledgement described in Section 5.1 (for
Internet-Drafts only), and is subject to all
provisions of
b. The Derivative Works Limitation described in Section 2 5.2 (for
specific types of RFC XXXX except that the right to
prepare revised versions Internet-Drafts only).
c. The Publication Limitation described in Section 5.3 (for specific
types of this specification is not granted. By 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),
5.1 IPR Disclosure Acknowledgement (required in all Internet-Drafts
only)
"By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed
in accordance with RFC XXXY.
c. This document is an
Bradner [Page 9]
Internet-Draft and is subject to all
provisions of Section 2 RFC XXXX, but the author does not provide
the IETF with any rights other than to publish as an Internet-
Draft. By submitting this Internet-Draft, I certify that Rights in Submissions June 2003
disclosed, and any
applicable patent or other IPR claims of which I am become aware have
been disclosed will be disclosed, in
accordance with RFC XXXY.
[note to XXXY."
5.2 Derivative Works Limitation
If the RFC Editor - XXXX above Contributor desires to be replaced with eliminate the number
of this document and XXXY IETF's right to be replaced the number make
modifications and derivative works of an Contribution (other than
translations), one of [IETF-IPR]]
The first statement is required for all documents that are submitted
for Standards Track publication. The primary motivation is that the
IETF retains change control, thus permitting augmenting the original
document to clarify or enhance two the protocol defined by following notices may be included
in the document.
The second statement is used when "republishing" standards produced
by other (non-IETF) standards organizations, industry consortia or
individual companies. These are typically Status of memo section of an Internet-Draft and included in a
published RFC:
a. "This document may not be modified, and derivative works of it may
not be created, except to publish it as Informational
RFCs, a RFC and do to translate it
into languages other than English."
b. "This document may not require be modified, and derivative works of it may
not be created."
In the cases of MIB or PIB modules and in other cases where the
Contribution includes material that change control is meant to be ceded extracted in order
to be used, the IETF.
Basically, these documents convey information for the Internet
community.
The third following should be appended to statement 5.2 (a) or
5.2 (b):
"other than to extract section XX as-is for separate use."
Notice 5.2(a) is used when if the document's purpose is to provide
background information to educate and to facilitate discussions
within IETF groups and Contributor intends for the document is not intended Contribution
to be published as an RFC.
4. Definitions
"Contribution": in the context of this memo, a contribution to RFC. Notice 5.2(b) is used along with the IETF
Bradner [Page 7]
Internet-Draft IETF Rights
Publication Limitation in Submissions April 2003
is any submission intended by Section 5.3 when the contributor Contributor does not
intend for publication as an
Internet-Draft or RFC and any statements made within the context of
an IETF process. Such statements include oral statements in IETF
meetings, as well as written and electronic communications made at
any time or place, which are addressed Contribution to
o the IETF plenary session,
o any IETF working group or portion thereof,
o the IESG, or be published as a RFC.
These notices may not be used with any member thereof on behalf of the IESG,
o the IAB standards-track document or any member thereof on behalf of the IAB,
o any IETF mailing list, including the IETF list itself, any
with most working group or design team list, or any other list functioning under documents, except as discussed in Section 7.3
below, since the IETF auspices,
o must retain change control over its documents
and the RFC Editor or ability to augment, clarify and enhance the Internet-Drafts function
Statements made outside of an original IETF meeting, mailing list or
Contribution in accordance with the IETF Standards Process.
Notice 5.2(a) may be appropriate when republishing standards produced
by other
function, that (non-IETF) standards organizations, industry consortia or
companies. These are clearly typically published as Informational RFCs, and
do not intended to require that change control be input ceded to an IETF
activity, group or function, are not contributions in the context IETF. Basically,
documents of this memo.
"IETF Standards Process": the activities undertaken by type convey information for the IETF in any Internet community.
A fuller discussion of the settings described rationale behind these requirements is
contained in 4 above.
"Contributors": individuals submitting Contributions
"IETF Documents": RFCs and Internet-Drafts.
"RFC": the basic publication series for Section 7.3 below.
5.3 Publication Limitation
If the IETF. RFCs are published by Contributor only wants the RFC Editor and once published are never modified. (See [RFC
2026] sec 2.1)
"Internet-Draft": temporary documents used IETF Contribution to be made
Bradner [Page 10]
Internet-Draft IETF Rights in Submissions June 2003
available as an Internet-Draft (i.e. does not want the IETF process.
Internet-Drafts are
Contribution to be published by as an RFC) then the IETF Secretariat and have a
nominal maximum lifetime Contributor may
include the following notice in the Secretariat's public directory Status of 6
months, after which they Memo section of the
Internet-Draft.
"This document may only be posted as an Internet-Draft."
This notice can be used on IETF Contributions that are removed. Since Internet-Drafts intended to
provide background information to educate and to facilitate
discussions within IETF working groups but are
archived many places on not intended to be
published as an RFCs.
5.4 Copyright Notice (required for all IETF Documents)
(Normally placed at the end of the IETF Document.)
"Copyright (C) The Internet there Society (year). This document is no effective limit on
subject to the rights, licenses and restrictions contained in RFC
XXXX and except as set forth therein, the authors retain all their actual lifetime. Internet-Drafts that are under active
consideration by
rights."
[note to the IESG RFC Editor - XXXX above to be replaced with the number
of this document]
Additional copyright notices are not removed from permitted in IETF Documents
except in the Secretariat's
public directory until that consideration case where the document is complete. In addition, the author product of a joint
development effort between the IETF and another standards development
organization. Such exceptions must be approved on an Internet-Draft can request that individual
basis by the lifetime IAB.
5.5 Disclaimer (required in all IETF Documents)
(Normally placed at the
Secretariat's public directory be extended before end of the expiration.
Note that under section 2.3(a) IETF Document after the grant of rights as specified in
this copyright
notice.)
"This document is perpetual and irrevocable and thus survives the
Secretariat's removal of information contained herein are provided
on an Internet-Draft from the public directory,
except as limited by section 2.3(a)(B). (See [RFC 2026] sections 2.2 "AS IS" basis and 8)
"IETF": In THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
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."
5.6 Exceptions.
Notwithstanding the context provisions of this document, the IETF includes all
individuals who participate Section 5, in meetings, working groups, mailing certain limited
cases an abbreviated notice may be placed on certain types of
Bradner [Page 8] 11]
Internet-Draft IETF Rights in Submissions April June 2003
lists, functions
derivative works of IETF Documents in accordance with this Section
5.6.
a. in MIB modules, PIB modules and other activities which are organized or
initiated by ISOC, similar material commonly
extracted from IETF Documents, the IESG or following abbreviated notice
may be included in the IAB under body of the general designation material that will be extracted
in lieu of the notices otherwise required by Section 5:
"Copyright (C) <year> The Internet Engineering Task Force Society. The initial version
of this MIB module was published in RFC XXXX; For full legal
notices see the RFC itself or IETF, but solely to see:
http://www.ietf.org/copyrights/ianamib.html."
Substitute "PIB" for "MIB" in the
extent statement for PIB modules. In
the case of such participation.
"Reasonably MIB and personally known": PIB modules this statement should be read placed in
the DESCRIPTION clause of the MODULE-IDENTITY macro.
[ note to RFC Editor - leave the "XXXX" in the above ]
b. short excerpts of IETF Documents presented in electronic help
systems, for example, the DESCRIPTION clauses for MIB variables,
do not need to refer include a copyright notice.
6. Notices and Rights Required in RFC Editor Contributions
Since the IETF acts as publisher of Internet Drafts, even Internet
Drafts not intended to something become part of the individual knows personally or, because Standards Process, the
following are required in all such drafts to protect the IETF and its
processes. The RFC Editor may require additional notices.
a. An IPR Disclosure Acknowledgement, identical to that specified in
Section 5.1.
b. One of the job following two copyright release statements:
A. "By submitting this Internet-Draft, I accept the individual
holds, would reasonably be expected provisions of
Section 3 of RFC XXXX."
B. "By submitting this Internet-Draft, I accept the provisions of
Section 4 of RFC XXXX."
[note to know.
5. RFC Editor - replace XXXX above with the number of this RFC]
7. Exposition of why these procedures are Why These Procedures Are the way they are
5.1 Way They Are
7.1 Rights Granted in IETF Contributions
Bradner [Page 12]
Internet-Draft IETF Rights in Submissions June 2003
The IETF/ISOC must obtain the right to publish a an IETF Contribution
as an RFC or an Internet-Draft from the Contributors.
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 Documents and to use the IETF Contributions in the IETF
standards process
Standards Process while leaving all other rights with the authors.
The non-exclusive rights that the IETF needs are:
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 sec 3.2), Section 5.2), the right to
make derivative works within the IETF process.
The authors retain all other rights, but cannot withdraw the above
rights from the IETF/ISOC.
5.2
7.2 Rights to use Contributed Material
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 6 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.
Bradner [Page 9]
Internet-Draft IETF Rights in Submissions April 2003
To this end, IETF asks Contributors to give the assurances in Section
2.4
3.4 above. These assurances are requested, however, only to the
extent of the Contributor's reasonable and personal knowledge. (See
Section 4.)
5.3 1(m))
7.3 Right to produce derivative works Produce Derivative Works
The IETF needs to be able to evolve its documents IETF Documents in response to
experience gained in the deployment of the technologies described in
the documents,
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
Bradner [Page 13]
Internet-Draft IETF Rights in Submissions June 2003
to produce derivative works. Note though that the IETF only requires
this right for the production of derivative works within the IETF
standards process.
Standards Process. The IETF does not need, nor does it obtain, the
right to let derivative works be created outside of the IETF process.
Standards Process other than as noted in Section 3.3 (E).
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.
The right to produce derivative works must be granted (i.e., an
Internet-Draft must be published with boilerplate "a" from sec 3.2)
before in order for an
IETF working group can to accept a document an IETF Contribution as a working group
document or otherwise work on it. Note: 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.
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
any the Internet-Draft with the
aim to decide if it should become a working group document, whether or not even
though the right to produce derivative works or to publish the IETF
Contribution as a RFC has been not yet been granted. For independent submissions,
the right to produce derivative works must be granted for all
standards track documents before If the IESG will issue an IETF Last-
Call and,
Contribution is accepted for most non-standards track documents, before development the Contributor must then
resubmit the IETF Contribution without the IESG
will consider limitation notices before
a working group can formally adopt the Internet-Draft for publication. IETF Contribution as a working
group document.
The IETF has historically encouraged organizations to publish details
of their technologies, even where when the technologies are proprietary
ones, 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 which that feel this way can specify that the
document an IETF
Contribution can be published following with the other provisions of rights granted under
this
section document but may withhold the right to produce derivative works. works
other than translations. The right to produce translations is
required before any IETF Contribution can be published as a RFC to
Bradner [Page 10] 14]
Internet-Draft IETF Rights in Submissions April June 2003
ensure the widest possible distribution of the material in RFCs.
In addition, IETF documents 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 documents, it can be quite helpful to
the IETF to republish, with the permission of the other standards
organization, some of these documents as IETF documents RFCs so that the IETF
community can have open access to them to better understand what they
are referring to. In these cases the IETF documents RFCs can be published without
the right for the IETF to produce derivative works.
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 3.2, Section 5.2, in order to
notify IETF participants about this restriction.
5.4
7.4 Rights to use trademarks Use Trademarks
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 2.3.a 4.2.a 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 Documents and discussions.
5.5
7.5 Who does this apply to? Does This Apply To?
Rights and licenses granted to the IETF are granted to all
individuals noted in section 4, 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.
6. Standards Process.
8. IETF Contributions Not Subject to Copyright
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 a proprietary
Bradner [Page 11] 15]
Internet-Draft IETF Rights in Submissions April June 2003
document. 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 IETF, the 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.
7. Inclusion of legal notice
Section three above defines a copyright notice to be included on IETF
documents and in derivative works. The full copyright notice does
not need to be included in some specific types of derivative works.
a/ in MIBs, PIBs and similar material commonly extracted from IETF
documents, the following copyright notice should be included in
the body of the material that will be extracted "Copyright (C)
<year> The Internet Society. This version of this MIB module is
part of RFC xxxx; see the RFC itself for the full legal notices."
(Substitute "PIB" for "MIB" in these grants and representations only to the statement for PIBs.) In
extent that the
case of MIBs and PIBs this statement should IETF Contribution may be placed in protected. We believe they
are necessary to protect the
DESCRIPTION clause of ISOC, the IETF, the MODULE-IDENTITY macro.
b/ short excerpts of IETF documents presented in electronic help
systems, for example, Standards
Process and all IETF participants, and also because the DESCRIPTION clauses for MIB variables,
do IETF does not need
have the resources or wherewithal to include a copyright notice.
8 make any independent
investigation as to the actual proprietary status of any document
submitted to it.
9. Security Considerations
This memo relates to IETF process, not any particular technology.
There are security considerations when adopting any technology,
whether IPR-protected or not. A working group should take those
security considerations into account as one part of evaluating the
technology, just as IPR is one part, but they technology. But
there are not no known issues of security with IPR procedures.
9. IETF Contribution rights
policies.
10. References
9.1
10.1 Normative references
[RFC 2026] Bradner, S.[ed], "The Internet Standards Process --
Revision 3", RFC 2026, October 1996
[IETF IPR] Bradner, S.[ed] "Intellectual Property Rights in IETF
Technology", work in progress: draft-iprwg-technology-00.txt
9.2
10.2 Informative references
[Berne] "Berne Convention for the Protection of Literary and Artistic
Bradner [Page 12]
Internet-Draft IETF Rights in Submissions April 2003
Work", http://www.wipo.int/treaties/ip/berne/index.html
10.
11. Acknowledgements
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.
11. The editor would also like to acknowledge the
extensive help John Klensin provided during the development of the
document.
12. Editor's Address
Scott Bradner
Harvard University
29 Oxford St.
Cambridge MA, 02138
Bradner [Page 16]
Internet-Draft IETF Rights in Submissions June 2003
sob@harvard.edu
+1 617 495 3864
12.
13. Full copyright statement
Copyright (C) The Internet Society (2003). Except as set forth
below, authors retain all their rights.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for rights
in submissions defined in the IETF Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE
REPRESENTS (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.
Bradner [Page 13]
Internet-Draft IETF Rights in Submissions April 2003
12.
14. change log
note to RFC Editor - remove this section before publication
ver 00 to ver 01
misc grammar changes throughout text
sec 2.2 - add note about automatic disclaimers
sec 2.3a - add "or is sponsored by" remove "unlimited"
sec 2.3 B - reword to 'of a scope no wider than the license"
sec 2.4a - add deff of major contributor
sec 2.6 - 2nd paragraph from sec 5.4 moved here
sec 3 - truncate heading
sec 3.1 5th pp - add OR IS SPONSORED BY
Bradner [Page 17]
Internet-Draft IETF Rights in Submissions June 2003
sec 3.1.2 - new section with copyright notice for use where
derivative works right are withheld
sec 3.2 - added usage guidelines for boilerplates
sec 4.1 - add "intended by the contributor"
sec 4.6 - add "actual" before lifetime
sec 4.8 - reword
sec 5.3 - insert "standards" in front of "process" last pp -
add "with permission" phrase after "republish"
sec 5.4 - change "we require" to "the IETF requires"
sec 7/a - add PIBs
sec 8 - redo security considerations
sec 9.1 - remove IPR ID as normative reference
sec 9.2 - add IPR ID as informative reference
sec 12 - add changes section
ver 01 to 02
abstract - add note about updating 2026
sec 3.2 - add patent pledge
ver 02 to 03
misc copy edits throughout document
sec 4 - "personally and reasonably known" - remove detail
ver 03 to 04
sec 4 - added note to the definition of Internet-Draft
ver 04 to 06
added ToC
moved definitions to front
change "Submissions" to "Contributions"
change MIBs & PIBs to "MIB modules" and "PIB modules"
fixes to make sure MIB & PIB modules etc could be extracted
misc grammar edits through out document
sec 1 - rearranged definitions split IETF and RFC Editor
Documents & Contributions changed "Contribution" in rest of
document to be consistent with new definitions - added
section XX and YY as part of this split
sec 3.3 - (a) (B) break out translations from other derivative
works add (a) (E) remove (b) as redundant
sec 5 - reorganized
Bradner [Page 14] 18]
----