draft-ietf-ipr-subm-rights-fix-00.txt   rfc3978.txt 
Network Working Group S. Bradner Network Working Group S. Bradner, Ed.
Internet-Draft Harvard University Request for Comments: 3978 Harvard University
Editor BCP: 78 March 2005
June 2004 Obsoletes: 3667
Updates: 2026
Category: Best Current Practice
IETF Rights in Contributions IETF Rights in Contributions
<draft-ietf-ipr-subm-rights-fix-00.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This document specifies an Internet Best Current Practices for the
applicable patent or other IPR claims of which he or she is aware Internet Community, and requests discussion and suggestions for
have been or will be disclosed, and any of which he or she becomes improvements. Distribution of this memo is unlimited.
aware will be disclosed, in accordance with Section 6 of RFC 3668.
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 Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2005).
http://www.ietf.org/shadow.html
Abstract Abstract
The IETF policies about rights in Contributions to the IETF are The IETF policies about rights in Contributions to the IETF are
designed to ensure that such Contributions can be made available to designed to ensure that such Contributions can be made available to
the IETF and Internet communities while permitting the authors to the IETF and Internet communities while permitting the authors to
retain as many rights as possible. This memo details the IETF retain as many rights as possible. This memo details the IETF
policies on rights in Contributions to the IETF. It also describes policies on rights in Contributions to the IETF. It also describes
the objectives that the policies are designed to meet. This memo the objectives that the policies are designed to meet. This memo
updates RFC 2026, and, with RFC XXXY, replaces Section 10 of RFC updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC
2026. [note to RFC editor: replace XXXY with number of IETF IPR] 2026.
Copyright Notice
Copyright (C) The Internet Society. (2004)
Table of Contents Table of Contents
Status of this Memo ................................................1
Abstract ...........................................................1 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2
1. Definitions ....................................................1 2. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction ...................................................1 3. Rights in IETF Contributions. . . . . . . . . . . . . . . . . 5
3. Rights in IETF Contributions ...................................1 3.1. General Policy. . . . . . . . . . . . . . . . . . . . . 5
3.1. General Policy .............................................1 3.2. Confidentiality Obligations . . . . . . . . . . . . . . 5
3.2. Confidentiality Obligations ................................1 3.3. Granting of Rights and Permissions. . . . . . . . . . . 6
3.3. Granting of Rights and Permissions .........................1 3.4. Representations and Warranties. . . . . . . . . . . . . 7
3.4. Representations and Warranties .............................1 3.5. No Duty to Publish. . . . . . . . . . . . . . . . . . . 7
3.5. No Duty to Publish .........................................1 3.6. Trademarks. . . . . . . . . . . . . . . . . . . . . . . 7
3.6. Trademarks .................................................1 4. Rights in RFC Editor Contributions. . . . . . . . . . . . . . 8
4. Rights in RFC Editor Contributions ..............................1 4.1. Requirements from Section 3 . . . . . . . . . . . . . . 8
4.1. Requirements from Section 3 ...............................1 4.2. Granting of Rights and Permissions. . . . . . . . . . . 8
4.2. Granting of Rights and Permissions ........................1 5. Notices Required in IETF Documents. . . . . . . . . . . . . . 9
5. Notices Required in IETF Documents .............................1 5.1. IPR Disclosure Acknowledgement. . . . . . . . . . . . . 10
5.1. IPR Disclosure Acknowledgement ..............................1 5.2. Derivative Works Limitation . . . . . . . . . . . . . . 10
5.2. Derivative Works Limitation .................................1 5.3. Publication Limitation. . . . . . . . . . . . . . . . . 11
5.3. Publication Limitation ......................................1 5.4. Copyright Notice. . . . . . . . . . . . . . . . . . . . 11
5.4. Copyright Notice ............................................1 5.5. Disclaimer. . . . . . . . . . . . . . . . . . . . . . . 11
5.5. Disclaimer ..................................................1 5.6. Exceptions. . . . . . . . . . . . . . . . . . . . . . . 12
5.6. Exceptions ..................................................1 6. Notices and Rights Required in RFC Editor Contributions . . . 13
6. Notices and Rights Required in RFC Editor Contributions ........1 7. Exposition of why these procedures are the way they are . . . 13
7. Exposition of why these procedures are the way they are ........1 7.1. Rights Granted in IETF Contributions. . . . . . . . . . 13
7.1. Rights Granted in IETF Contributions ........................1 7.2. Rights to use Contributed Material. . . . . . . . . . . 14
7.2. Rights to use Contributed Material ..........................1 7.3. Right to Produce Derivative Works . . . . . . . . . . . 14
7.3. Right to Produce Derivative Works ...........................1 7.4. Rights to use Trademarks. . . . . . . . . . . . . . . . 16
7.4. Rights to use Trademarks ....................................1 7.5. Who Does This Apply To? . . . . . . . . . . . . . . . . 16
7.5. Who Does This Apply To? .....................................1 8. Contributions Not Subject to Copyright. . . . . . . . . . . . 16
8. Contributions Not Subject to Copyright .........................1 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations ........................................1 10. References. . . . . . . . . . . . . . . . . . . . . . . . . . 17
10. References .....................................................1 10.1. Normative References. . . . . . . . . . . . . . . . . . 17
10.1. Normative References .......................................1 10.2. Informative References. . . . . . . . . . . . . . . . . 17
10.2. Informative References .....................................1 11. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 17
11. Acknowledgements ...............................................1 Editor's Address. . . . . . . . . . . . . . . . . . . . . . . 17
12. Editor's Address ...............................................1 Full Copyright Statement. . . . . . . . . . . . . . . . . . . 18
13. Full Copyright Statement .......................................1
1. Definitions 1. Definitions
The following definitions are for terms used in the context of this The following definitions are for terms used in the context of this
document. Other terms, including "IESG," "ISOC," "IAB" and "RFC document. Other terms, including "IESG," "ISOC," "IAB," and "RFC
Editor," are defined in [RFC 2028]. Editor," are defined in [RFC 2028].
a. "IETF": In the context of this document, the IETF includes all a. "IETF": In the context of this document, the IETF includes all
individuals who participate in meetings, working groups, mailing individuals who participate in meetings, working groups, mailing
lists, functions and other activities which are organized or lists, functions and other activities which are organized or
initiated by ISOC, the IESG or the IAB under the general initiated by ISOC, the IESG or the IAB under the general
designation of the Internet Engineering Task Force or IETF, but designation of the Internet Engineering Task Force or IETF, but
solely to the extent of such participation. solely to the extent of such participation.
b. "IETF Standards Process": the activities undertaken by the IETF in b. "IETF Standards Process": the activities undertaken by the IETF in
skipping to change at page 3, line 37 skipping to change at page 3, line 20
Statements made outside of an IETF session, mailing list or other Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the activity, group or function, are not IETF Contributions in the
context of this document. context of this document.
d. "Internet-Draft": temporary documents used in the IETF and RFC d. "Internet-Draft": temporary documents used in the IETF and RFC
Editor processes. Internet-Drafts are posted on the IETF web site Editor processes. Internet-Drafts are posted on the IETF web site
by the IETF Secretariat and have a nominal maximum lifetime in the by the IETF Secretariat and have a nominal maximum lifetime in the
Secretariat's public directory of 6 months, after which they are Secretariat's public directory of 6 months, after which they are
removed. Note that Internet-Drafts are archived many places on removed. Note that Internet-Drafts are archived many places on
the Internet, and not all of these places remove expired Internet- the Internet, and not all of these places remove expired
Drafts. Internet-Drafts that are under active consideration by Internet-Drafts. Internet-Drafts that are under active
the IESG are not removed from the Secretariat's public directory consideration by the IESG are not removed from the Secretariat's
until that consideration is complete. In addition, the author of public directory until that consideration is complete. In
an Internet-Draft can request that the lifetime in the addition, the author of an Internet-Draft can request that the
Secretariat's public directory be extended before the expiration. lifetime in the Secretariat's public directory be extended before
the expiration.
e. "RFC": the basic publication series for the IETF. RFCs are e. "RFC": the basic publication series for the IETF. RFCs are
published by the RFC Editor and once published are never modified. published by the RFC Editor and once published are never modified.
(See [RFC 2026] Section 2.1) (See [RFC 2026] Section 2.1)
f. "RFC Editor Contribution": An Internet-Draft intended by the f. "RFC Editor Contribution": An Internet-Draft intended by the
Contributor to be submitted to the RFC Editor for publication as Contributor to be submitted to the RFC Editor for publication as
an Informational or Experimental RFC but not intended to be part an Informational or Experimental RFC but not intended to be part
of the IETF Standards Process. of the IETF Standards Process.
skipping to change at page 5, line 19 skipping to change at page 4, line 50
and ISOC regarding their ability to grant these rights. These and ISOC regarding their ability to grant these rights. These
necessary rights and representations have until now been laid out in necessary rights and representations have until now been laid out in
Section 10 of [RFC 2026]. In the years since [RFC 2026] was published 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 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. has been the subject of vigorous debate within the IETF community.
The aim of this document is to clarify various ambiguities in Section The aim of this document is to clarify various ambiguities in Section
10 of [RFC 2026] that led to these debates and to amplify the policy 10 of [RFC 2026] that led to these debates and to amplify the policy
in order to clarify what the IETF is currently doing. in order to clarify what the IETF is currently doing.
Section 1 gives definitions used in describing these policies. Section 1 gives definitions used in describing these policies.
Sections 3, 4, 5 and 6 of this document address the rights in Sections 3, 4, 5, and 6 of this document address the rights in
Contributions previously covered by Section 10 of [RFC 2026] and the Contributions previously covered by Section 10 of [RFC 2026] and the
"Note Well" explanatory text presented at many IETF activities. "Note Well" explanatory text presented at many IETF activities.
Sections 7 and 8 then explain the rationale for these provisions, Sections 7 and 8 then explain the rationale for these provisions,
including some of the clarifications that have become understood including some of the clarifications that have become understood
since the adoption of [RFC 2026]. The rules and procedures set out since the adoption of [RFC2026]. The rules and procedures set out in
in this document are not intended to substantially modify or alter this document are not intended to substantially modify or alter the
the IETF's current policy toward Contributions. IETF's current policy toward Contributions.
A companion document [IETF IPR] deals with rights in technologies A companion document [RFC3979] deals with rights in technologies
developed or specified as part of the IETF Standards Process. This developed or specified as part of the IETF Standards Process. This
document is not intended to address those issues. document is not intended to address those issues.
The rights addressed in this document fall into the following The rights addressed in this document fall into the following
categories: categories:
o rights to make use of contributed material o rights to make use of contributed material
o copyrights in IETF documents o copyrights in IETF documents
o rights to produce derivative works o rights to produce derivative works
o rights to use trademarks o rights to use trademarks
skipping to change at page 6, line 37 skipping to change at page 6, line 22
submitting the Contribution. submitting the Contribution.
a. To the extent that a Contribution or any portion thereof is a. To the extent that a Contribution or any portion thereof is
protected by copyright and other rights of authorship, the protected by copyright and other rights of authorship, the
Contributor, and each named co-Contributor, and the organization Contributor, and each named co-Contributor, and the organization
he or she represents or is sponsored by (if any) grant a he or she represents or is sponsored by (if any) grant a
perpetual, irrevocable, non-exclusive, royalty-free, world-wide perpetual, irrevocable, non-exclusive, royalty-free, world-wide
right and license to the ISOC and the IETF under all intellectual right and license to the ISOC and the IETF under all intellectual
property rights in the Contribution: property rights in the Contribution:
(A) to copy, publish, display and distribute the Contribution as (A) to copy, publish, display, and distribute the Contribution as
part of the IETF Standards Process or in an Internet-Draft, part of the IETF Standards Process or in an Internet-Draft,
(B) to prepare or allow the preparation of translations of the (B) to prepare or allow the preparation of translations of the
Contribution into languages other than English, Contribution into languages other than English,
(C) unless explicitly disallowed in the notices contained in a (C) unless explicitly disallowed in the notices contained in a
Contribution [as per Section 5.2 below], to prepare derivative Contribution [as per Section 5.2 below], to prepare derivative
works (other than translations) that are based on or works (other than translations) that are based on or
incorporate all or part of the Contribution, or comment upon incorporate all or part of the Contribution, or comment upon
it, within the IETF Standards Process. The license to such it, within the IETF Standards Process. The license to such
skipping to change at page 7, line 16 skipping to change at page 6, line 49
Contribution and derivative works thereof as permitted by this Contribution and derivative works thereof as permitted by this
paragraph. When reproducing Contributions, the IETF will paragraph. When reproducing Contributions, the IETF will
preserve trademark and service mark identifiers used by the preserve trademark and service mark identifiers used by the
Contributor of the Contribution, including (TM) and (R) where Contributor of the Contribution, including (TM) and (R) where
appropriate, and appropriate, and
(E) to extract, copy, publish, display, distribute, modify and (E) to extract, copy, publish, display, distribute, modify and
incorporate into other works, for any purpose (and not limited incorporate into other works, for any purpose (and not limited
to use within the IETF Standards Process) any executable code to use within the IETF Standards Process) any executable code
or code fragments that are included in any IETF Document (such or code fragments that are included in any IETF Document (such
as MIB and PIB modules), subject to the requirements of Section as MIB and PIB modules), subject to the requirements of
5 (it also being understood that the licenses granted under Section 5 (it also being understood that the licenses granted
this paragraph (E) shall not be deemed to grant any right under under this paragraph (E) shall not be deemed to grant any
any patent, patent application or other similar intellectual right under any patent, patent application or other similar
property right disclosed by the Contributor under [IETF IPR]). intellectual property right disclosed by the Contributor under
[RFC3979]).
b. The Contributor grants the IETF and ISOC permission to reference b. The Contributor grants the IETF and ISOC permission to reference
the name(s) and address(es) of the Contributor(s) and of the the name(s) and address(es) of the Contributor(s) and of the
organization(s) s/he represents or is sponsored by (if any). organization(s) s/he represents or is sponsored by (if any).
3.4. Representations and Warranties 3.4. Representations and Warranties
With respect to each Contribution, each Contributor represents that With respect to each Contribution, each Contributor represents that
to the best of his or her knowledge and ability: to the best of his or her knowledge and ability:
skipping to change at page 8, line 20 skipping to change at page 8, line 5
any Contribution that does not comply with the requirements of any Contribution that does not comply with the requirements of
Section 3.4 and Section 3.3 or 4.2. Section 3.4 and Section 3.3 or 4.2.
3.6. Trademarks 3.6. Trademarks
Contributors, and each named co-Contributor, who claim trademark Contributors, and each named co-Contributor, who claim trademark
rights in terms used in their IETF Contributions are requested to rights in terms used in their IETF Contributions are requested to
state specifically what conditions apply to implementers of the state specifically what conditions apply to implementers of the
technology relative to the use of such trademarks. Such statements technology relative to the use of such trademarks. Such statements
should be submitted in the same way as is done for other intellectual should be submitted in the same way as is done for other intellectual
property claims. (See [IETF IPR] Section 6.) property claims. (See [RFC3979] Section 6.)
4. Rights in RFC Editor Contributions 4. Rights in RFC Editor Contributions
The following are the rights the IETF, as the publisher of Internet- The following are the rights the IETF, as the publisher of Internet-
Drafts, requires in all RFC Editor Contributions: Drafts, requires in all RFC Editor Contributions:
4.1. Requirements from Section 3 4.1. Requirements from Section 3
All RFC Editor Contributions must meet the requirements of Sections All RFC Editor Contributions must meet the requirements of Sections
3.1, 3.2, 3.4, 3.5 and 3.6. 3.1, 3.2, 3.4, 3.5 and 3.6.
skipping to change at page 8, line 51 skipping to change at page 8, line 36
a. To the extent that an RFC Editor Contribution or any portion a. To the extent that an RFC Editor Contribution or any portion
thereof is protected by copyright and other rights of authorship, thereof is protected by copyright and other rights of authorship,
the Contributor, and each named co-Contributor, and the the Contributor, and each named co-Contributor, and the
organization he or she represents or is sponsored by (if any) organization he or she represents or is sponsored by (if any)
grant a perpetual, irrevocable, non-exclusive, royalty-free, grant a perpetual, irrevocable, non-exclusive, royalty-free,
world-wide right and license to the ISOC and the IETF under all world-wide right and license to the ISOC and the IETF under all
intellectual property rights in the RFC Editor Contribution for at intellectual property rights in the RFC Editor Contribution for at
least the life of the Internet-Draft: least the life of the Internet-Draft:
(A) to copy, publish, display and distribute the RFC Editor (A) to copy, publish, display, and distribute the RFC Editor
Contribution as an Internet-Draft, Contribution as an Internet-Draft,
(B) to prepare or allow the preparation of translations of the RFC (B) to prepare or allow the preparation of translations of the RFC
into languages other than English. into languages other than English.
(C) unless explicitly disallowed in the notices contained in an (C) unless explicitly disallowed in the notices contained in an
RFC Editor Contribution (as per Section 5.2 below), to prepare RFC Editor Contribution (as per Section 5.2 below), to prepare
derivative works (other than translations) that are based on or derivative works (other than translations) that are based on
incorporate all or part of the RFC Editor Contribution, or or incorporate all or part of the RFC Editor Contribution, or
comment upon it. The license to such derivative works not comment upon it. The license to such derivative works not
granting the ISOC and the IETF any more rights than the license granting the ISOC and the IETF any more rights than the
to the original RFC Editor Contribution, and license to the original RFC Editor Contribution, and
(D) to reproduce any trademarks, service marks or trade names (D) to reproduce any trademarks, service marks or trade names
which are included in the RFC Editor Contribution solely in which are included in the RFC Editor Contribution solely in
connection with the reproduction, distribution or publication connection with the reproduction, distribution or publication
of the RFC Editor Contribution and derivative works thereof as of the RFC Editor Contribution and derivative works thereof as
permitted by this paragraph. When reproducing RFC Editor permitted by this paragraph. When reproducing RFC Editor
Contributions, the IETF will preserve trademark and service Contributions, the IETF will preserve trademark and service
mark identifiers used by the Contributor of the RFC Editor mark identifiers used by the Contributor of the RFC Editor
Contribution, including (TM) and (R) where appropriate. Contribution, including (TM) and (R) where appropriate.
b. The Contributor grants the IETF and ISOC permission to reference b. The Contributor grants the IETF and ISOC permission to reference
skipping to change at page 10, line 20 skipping to change at page 10, line 12
Documents). Documents).
e. The Disclaimer described in Section 5.5 (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 5.1. IPR Disclosure Acknowledgement (required in all Internet-Drafts
only) only)
"By submitting this Internet-Draft, each author represents that "By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is 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 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 becomes aware will be disclosed, in accordance with Section 6 of
RFC XXXY." BCP 79."
5.2. Derivative Works Limitation 5.2. Derivative Works Limitation
If the Contributor desires to eliminate the IETF's right to make If the Contributor desires to eliminate the IETF's right to make
modifications and derivative works of an IETF Contribution (other modifications and derivative works of an IETF Contribution (other
than translations), one of the two of the following notices may be 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 the Status of Memo section of an Internet-Draft and
included in a published RFC: included in a published RFC:
a. "This document may not be modified, and derivative works of it may a. "This document may not be modified, and derivative works of it may
skipping to change at page 11, line 34 skipping to change at page 11, line 27
This notice can be used on IETF Contributions that are intended to This notice can be used on IETF Contributions that are intended to
provide background information to educate and to facilitate provide background information to educate and to facilitate
discussions within IETF working groups but are not intended to be discussions within IETF working groups but are not intended to be
published as an RFCs. published as an RFCs.
5.4. Copyright Notice (required for all IETF Documents) 5.4. Copyright Notice (required for all IETF Documents)
(Normally placed at the end of the IETF Document.) (Normally placed at the end of the IETF Document.)
"Copyright (C) The Internet Society (year). This document is "Copyright (C) The Internet Society (year).
subject to the rights, licenses and restrictions contained in RFC
XXXX and except as set forth therein, the authors retain all their
rights."
[note to the RFC Editor - XXXX above to be replaced with the number This document is subject to the rights, licenses and restrictions
of this document] contained in BCP 78, and except as set forth therein, the authors
retain all their rights."
Additional copyright notices are not permitted in IETF Documents Additional copyright notices are not permitted in IETF Documents
except in the case where such document is the product of a joint except in the case where such document is the product of a joint
development effort between the IETF and another standards development development effort between the IETF and another standards development
organization or the document is a republication of the work of organization or the document is a republication of the work of
another standards organization. Such exceptions must be approved on another standards organization. Such exceptions must be approved on
an individual basis by the IAB. an individual basis by the IAB.
5.5. Disclaimer (required in all IETF Documents) 5.5. Disclaimer (required in all IETF Documents)
skipping to change at page 13, line 6 skipping to change at page 12, line 44
modules this statement should be placed in the DESCRIPTION clause modules this statement should be placed in the DESCRIPTION clause
of the MODULE-IDENTITY macro. of the MODULE-IDENTITY macro.
Variations of these abbreviated notices are not permitted except Variations of these abbreviated notices are not permitted except
in cases where the material to be extracted is the product of a in cases where the material to be extracted is the product of a
joint development effort between the IETF and another standards joint development effort between the IETF and another standards
development organization or is a republication of the work of development organization or is a republication of the work of
another standards organization. Such variations must be approved another standards organization. Such variations must be approved
on an individual basis by the IAB. on an individual basis by the IAB.
[ note to RFC Editor - leave the "XXXX" in the above ]
b. short excerpts of IETF Documents presented in electronic help b. short excerpts of IETF Documents presented in electronic help
systems, for example, the DESCRIPTION clauses for MIB variables, systems, for example, the DESCRIPTION clauses for MIB variables,
do not need to include a copyright notice. do not need to include a copyright notice.
6. Notices and Rights Required in RFC Editor Contributions 6. Notices and Rights Required in RFC Editor Contributions
Since the IETF acts as publisher of Internet Drafts, even for Since the IETF acts as publisher of Internet Drafts, even for
Internet Drafts that are not intended to become part of the Standards Internet Drafts that are not intended to become part of the Standards
Process, the following are required in all such drafts to protect the Process, the following are required in all such drafts to protect the
IETF and its processes. The RFC Editor may require additional IETF and its processes. The RFC Editor may require additional
notices. notices.
a. An IPR Disclosure Acknowledgement, identical to that specified in a. An IPR Disclosure Acknowledgement, identical to that specified in
Section 5.1. Section 5.1.
b. One of the following two copyright release statements: b. One of the following three copyright release statements:
A. "By submitting this Internet-Draft, I accept the provisions of A. "By submitting this Internet-Draft, I accept the provisions of
Section 3 of RFC XXXX." Section 3 of BCP 78."
B. "By submitting this Internet-Draft, I accept the provisions of B. "By submitting this Internet-Draft, I accept the provisions of
Section 4 of RFC XXXX." Section 4 of BCP 78."
[note to RFC Editor - replace XXXX above with the number of this RFC] C. The Copyright Notice specified in Section 5.4 and the
disclaimer specified in section 5.5.
7. Exposition of Why These Procedures Are the Way They Are 7. Exposition of Why These Procedures Are the Way They Are
7.1. Rights Granted in IETF Contributions 7.1. Rights Granted in IETF Contributions
The IETF/ISOC must obtain the right to publish an IETF Contribution The IETF/ISOC must obtain the right to publish an IETF Contribution
as an RFC or an Internet-Draft from the Contributors. as an RFC or an Internet-Draft from the Contributors.
A primary objective of this policy is to obtain from the document A primary objective of this policy is to obtain from the document
authors only the non-exclusive rights that are needed to develop and authors only the non-exclusive rights that are needed to develop and
skipping to change at page 15, line 21 skipping to change at page 15, line 11
granted before the IESG will issue an IETF Last-Call and, for most granted before the IESG will issue an IETF Last-Call and, for most
non-standards track non-working group IETF Contributions, before the non-standards track non-working group IETF Contributions, before the
IESG will consider the Internet-Draft for publication. IESG will consider the Internet-Draft for publication.
Occasionally a Contributor may not want to grant publication rights Occasionally a Contributor may not want to grant publication rights
or the right to produce derivative works before finding out if an or the right to produce derivative works before finding out if an
IETF Contribution has been accepted for development in the IETF IETF Contribution has been accepted for development in the IETF
Standards Process. In these cases the Contributor may include the Standards Process. In these cases the Contributor may include the
Derivative Works Limitation described in Section 5.2 and the Derivative Works Limitation described in Section 5.2 and the
Publication Limitation described in Section 5.3 in their IETF Publication Limitation described in Section 5.3 in their IETF
Contribution. A working group can discuss the Internet-Draft with the Contribution. A working group can discuss the Internet-Draft with
aim to decide if it should become a working group document, even 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 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 as an RFC has not yet been granted. If the IETF
Contribution is accepted for development the Contributor must then Contribution is accepted for development the Contributor must then
resubmit the IETF Contribution without the limitation notices before resubmit the IETF Contribution without the limitation notices before
a working group can formally adopt the IETF Contribution as a working a working group can formally adopt the IETF Contribution as a working
group document. group document.
The IETF has historically encouraged organizations to publish details The IETF has historically encouraged organizations to publish details
of their technologies, even when the technologies are proprietary, of their technologies, even when the technologies are proprietary,
because understanding how existing technology is being used helps because understanding how existing technology is being used helps
when developing new technology. But organizations that publish when developing new technology. But organizations that publish
information about proprietary technologies are frequently not willing information about proprietary technologies are frequently not willing
to have the IETF produce revisions of the technologies and then claim to have the IETF produce revisions of the technologies and then claim
that the IETF version is the "new version" of the organization's that the IETF version is the "new version" of the organization's
technology. Organizations that feel this way can specify that an IETF technology. Organizations that feel this way can specify that an
Contribution can be published with the other rights granted under IETF Contribution can be published with the other rights granted
this document but may withhold the right to produce derivative works under this document but may withhold the right to produce derivative
other than translations. The right to produce translations is works other than translations. The right to produce translations is
required before any IETF Contribution can be published as an RFC to required before any IETF Contribution can be published as an RFC to
ensure the widest possible distribution of the material in RFCs. ensure the widest possible distribution of the material in RFCs.
In addition, IETF Documents frequently make normative references to In addition, IETF Documents frequently make normative references to
standards or recommendations developed by other standards standards or recommendations developed by other standards
organizations. Since the publications of some standards organizations. Since the publications of some standards
organizations are not public documents, it can be quite helpful to organizations are not public documents, it can be quite helpful to
the IETF to republish, with the permission of the other standards the IETF to republish, with the permission of the other standards
organization, some of these documents as RFCs so that the IETF organization, some of these documents as RFCs so that the IETF
community can have open access to them to better understand what they community can have open access to them to better understand what they
skipping to change at page 17, line 16 skipping to change at page 17, line 9
This memo relates to IETF process, not any particular technology. This memo relates to IETF process, not any particular technology.
There are security considerations when adopting any technology, but There are security considerations when adopting any technology, but
there are no known issues of security with IETF Contribution rights there are no known issues of security with IETF Contribution rights
policies. policies.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC 2026] Bradner, S., Ed, "The Internet Standards Process -- [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
Revision 3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[IETF IPR] Bradner, S., Ed, "Intellectual Property Rights in IETF [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in
Technology", BCP 79, RFC XXXY, date [Note to RFC Editor: replace the IETF Standards Process", BCP 11, RFC 2028, October
XXXY with the number of the RFC 3668 replacement] 1996.
[RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3979, March 2005.
10.2. Informative References 10.2. Informative References
[Berne] "Berne Convention for the Protection of Literary and Artistic [Berne] "Berne Convention for the Protection of Literary and
Work", http://www.wipo.int/treaties/ip/berne/index.html Artistic Work",
http://www.wipo.int/edocs/trtdocs/en/wo/wo001en.htm
11. Acknowledgements 11. Acknowledgements
The editor would like to acknowledge the help of the IETF IPR Working 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 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 for his careful legal reviews of this and other IETF IPR-related and
process documents. The editor would also like to acknowledge the process documents. The editor would also like to acknowledge the
extensive help John Klensin provided during the development of the extensive help John Klensin provided during the development of the
document. document.
12. Editor's Address Editor's Address
Scott Bradner Scott Bradner
Harvard University Harvard University
29 Oxford St. 29 Oxford St.
Cambridge MA, 02138 Cambridge MA, 02138
Phone: +1 617 495 3864 Phone: +1 617 495 3864
EMail: sob@harvard.edu EMail: sob@harvard.edu
13. Full copyright statement Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78 and Copyright (C) The Internet Society (2005).
except as set forth therein, the authors retain all their rights.
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.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
skipping to change at page 18, line 32 skipping to change at page 18, line 37
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. The IETF invites any interested party to http://www.ietf.org/ipr.
bring to its attention any copyrights, patents or patent
applications, or other proprietary rights that may cover technology The IETF invites any interested party to bring to its attention any
that may be required to implement this standard. Please address the copyrights, patents or patent applications, or other proprietary
information to the IETF at ietf-ipr@ietf.org. 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.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
change log - to be removed by the RFC Editor
RFC 3667 to version 00
correct wording on IPR disclaimer boilerplate
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/