draft-ietf-ipr-rules-update-05.txt   draft-ietf-ipr-rules-update-06.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Editor Editor
RFC 3978 Update RFC 3978 Update
<draft-ietf-ipr-rules-update-05.txt> <draft-ietf-ipr-rules-update-06.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 4, line 12 skipping to change at page 4, line 12
Contributor represents or is sponsored by (if any), when Contributor represents or is sponsored by (if any), when
submitting the Contribution." submitting the Contribution."
2.2 Because it is necessary in this document to refer to individual 2.2 Because it is necessary in this document to refer to individual
IETF participants, the following sentence is added at the end of the IETF participants, the following sentence is added at the end of the
definition of "IETF" in Section 1(a) of RFC 3978: definition of "IETF" in Section 1(a) of RFC 3978:
"An "IETF Participant" shall mean any such individual "An "IETF Participant" shall mean any such individual
participant." participant."
2.3 To make it easier to change the ID boilerplate when needed Sections
5.1 to 5.6 are replaced with the following:
"5.1. IPR Disclosure Acknowledgement (required in all Internet-
Drafts but not in RFCs)
All I-Ds MUST include the exact text for an IPR Disclosure
Acknowledgement from http://www.ietf.org/ipr-boilerplate-
derivworks
5.2. Derivative Works Limitation
If the Contributor desires to eliminate the IETF's right to make
modifications and derivative works of an IETF Contribution (other
than translations), one of the two Derivative Works Limitation
notices from http://www.ietf.org/ipr-boilerplate-derivworks may be
included in the Status of Memo section of an Internet-Draft and
included in a published RFC.
In the cases of MIB or PIB modules and in other cases where the
Contribution includes material that is meant to be extracted in
order to be used, the text of the MIB extraction notice from
http://www.ietf.org/ipr-boilerplate-derivworks should be appended
to the Derivative Works Limitation.
These notices may not be used with any standards-track document or
with most working group documents, except as discussed in Section
7.3 below, since the IETF must retain change control over its
documents and the ability to augment, clarify and enhance the
original IETF Contribution in accordance with the IETF Standards
Process. A fuller discussion of the rationale behind these
requirements is contained in Section 7.3 below.
5.3. Publication Limitation
If the Contributor only wants the IETF Contribution to be made
available in an Internet-Draft (i.e., does not want the IETF
Contribution to be published as an RFC) then the Contributor may
include the Publication Limitation notice from
http://www.ietf.org/ipr-boilerplate-derivworks in the Status of
Memo section of the Internet-Draft.
This notice can be used on IETF Contributions that are intended to
provide background information to educate and to facilitate
discussions within IETF working groups but are not intended to be
published as an RFCs.
5.4. Copyright Notice (required for all IETF Documents)
(Normally placed at the end of the IETF Document.)
The Copyright notice from http://www.ietf.org/ipr-boilerplate-
derivworks must be included in all Internet-Drafts.
Additional copyright notices are not permitted in IETF Documents
except in the case where such document is the product of a joint
development effort between the IETF and another standards
development organization or the document is a republication of the
work of another standards organization. Such exceptions must be
approved on an individual basis by the IAB.
5.5. Disclaimer (required in all IETF Documents)
(Normally placed at the end of the IETF Document after the
copyright notice.)
The Disclaimer notice from http://www.ietf.org/ipr-boilerplate-
derivworks must be included in all Internet-Drafts.
5.6. Exceptions
Notwithstanding the provisions of this Section 5, in certain
limited cases an abbreviated notice may be placed on certain types
of derivative works of IETF Documents in accordance with this
Section 5.6.
a. in MIB modules, PIB modules and similar material commonly
extracted from IETF Documents, except for material that is
being placed under IANA maintenance, the abbreviated MIB notice
from http://www.ietf.org/ipr-boilerplate-derivworks shall be
included in the body of the material that will be extracted in
lieu of the notices otherwise required by Section 5.
When the MIB or PIB module is the initial version of a module
that is to be maintained by the IANA, the abbreviated MIB
Copyright Notice from http://www.ietf.org/ipr-boilerplate-
derivworks notice shall be included:
Variations of these abbreviated notices are not permitted
except in cases where the material to be extracted is the
product of a joint development effort between the IETF and
another standards development organization or is a
republication of the work of another standards organization.
Such variations must be approved on an individual basis by the
IAB.
b. short excerpts of IETF Documents presented in electronic help
systems, for example, the DESCRIPTION clauses for MIB
variables, do not need to include a copyright notice.
3. Rights Granted By Contributors to IETF Trust - New Section 3.3 3. Rights Granted By Contributors to IETF Trust - New Section 3.3
The following text describes the rights that are granted by each The following text describes the rights that are granted by each
Contributor to the IETF Trust and replaces Section 3.3 of RFC 3978 in Contributor to the IETF Trust and replaces Section 3.3 of RFC 3978 in
full: full:
"3.3. Rights Granted by Contributors to IETF Trust "3.3. Rights Granted by Contributors to IETF Trust
To the extent that a Contribution or any portion thereof is To the extent that a Contribution or any portion thereof is
protected by copyright or other rights of authorship, the protected by copyright or other rights of authorship, the
skipping to change at page 5, line 40 skipping to change at page 7, line 46
(G) to permit the IETF Trust to sublicense these rights to the (G) to permit the IETF Trust to sublicense these rights to the
extent of the original grant of right and license, including extent of the original grant of right and license, including
its use in a working collection or collective work. its use in a working collection or collective work.
The licenses granted in this Section 3.3 shall not be deemed to The licenses granted in this Section 3.3 shall not be deemed to
grant any right under any patent, patent application or other grant any right under any patent, patent application or other
similar intellectual property right disclosed by the similar intellectual property right disclosed by the
Contributor under BCP 79." Contributor under BCP 79."
4. Legends and Notifications 4. Instruct IETF Trust to grant rights to IETF participants
[ NOTE: this section has been added at the request of the General
Area AD. This direction may be better placed in another document.]
The following to be inserted between sections 8 and 9 of RFC 3978.
"The IETF Trust is hereby instructed to grant the rights granted
in section 3.3 above to all participants in the IETF process as
needed for the operation of the IETF standards process."
5. Legends and Notifications
The legends and notifications required by RFC 3978 are hereby updated The legends and notifications required by RFC 3978 are hereby updated
as set forth below to reflect the other provisions of this document. as set forth below to reflect the other provisions of this document.
4.1 The first paragraph of Section 5 of RFC 3978 explains the 5.1 The first paragraph of Section 5 of RFC 3978 explains the
requirement for applying certain notices and legends to IETF requirement for applying certain notices and legends to IETF
documents. There has been considerable confusion in the past documents. There has been considerable confusion in the past
regarding the meaning of the copyright notice on these documents. regarding the meaning of the copyright notice on these documents.
Accordingly, the first paragraph of Section 5 is hereby amended as Accordingly, the first paragraph of Section 5 is hereby amended as
follows to explain the purpose and meaning of this copyright notice follows to explain the purpose and meaning of this copyright notice
requirement, as well as to substitute "IETF Trust" for "ISOC": requirement, as well as to substitute "IETF Trust" for "ISOC":
"The IETF requires that certain notices and disclaimers described "The IETF requires that certain notices and disclaimers described
in this Section 5 be reproduced verbatim in all IETF Documents in this Section 5 be reproduced verbatim in all IETF Documents
(including copies, derivative works and translations of IETF (including copies, derivative works and translations of IETF
skipping to change at page 6, line 23 skipping to change at page 8, line 39
The copyright notice also alerts readers that the document is an The copyright notice also alerts readers that the document is an
IETF Document, and that the IETF Trust owns certain aspects of the IETF Document, and that the IETF Trust owns certain aspects of the
document, such as its layout, the RFC numbering convention and the document, such as its layout, the RFC numbering convention and the
prefatory language of the document. This legend is not, however, prefatory language of the document. This legend is not, however,
intended to imply that IETF or the IETF Trust owns the text of any intended to imply that IETF or the IETF Trust owns the text of any
Contribution included in an IETF Document. Rather, ownership of Contribution included in an IETF Document. Rather, ownership of
such Contributions is retained by the author(s) or remains in the such Contributions is retained by the author(s) or remains in the
public domain, as applicable, subject only to the licenses granted public domain, as applicable, subject only to the licenses granted
to IETF and the IETF Trust under Section 3.3 above." to IETF and the IETF Trust under Section 3.3 above."
4.2 Update copyright statement and clarify text about additional 5.2 Update copyright statement and clarify text about additional
copyright statements copyright statements
The creation of the IETF Trust to hold IETF-related IPR requires that The creation of the IETF Trust to hold IETF-related IPR requires that
the copyright statement in Section 5.4 be changed. Since it has been the copyright statement in Section 5.4 be changed. Since it has been
established practice to include a one-line copyright statement near established practice to include a one-line copyright statement near
the beginning of IETF Documents this should be mentioned. the beginning of IETF Documents this should be mentioned.
The text in Section 5.4 about multiple copyright statements has The text in Section 5.4 about multiple copyright statements has
occasionally been misinterpreted so should be clarified. occasionally been misinterpreted so should be clarified.
4.2.1 Revised Section 5.4 5.2.1 Revised Section 5.4
5.4. Copyright Notices (required for all IETF Documents) 5.4. Copyright Notices (required for all IETF Documents)
(Normally placed at the end of the IETF Document.) (Normally placed at the end of the IETF Document.)
"Portions Copyright (C) The IETF Trust (year). "Portions Copyright (C) The IETF Trust (year).
This document is subject to the rights, licenses and This document is subject to the rights, licenses and
restrictions contained in BCP 78, and except as set forth restrictions contained in BCP 78, and except as set forth
therein, the authors retain all their rights." therein, the authors retain all their rights."
Only copyright notices for the IETF Trust are permitted in IETF Only copyright notices for the IETF Trust are permitted in IETF
Documents except in the case where such a document is the product Documents except in the case where such a document is the product
of a joint development effort between the IETF and another of a joint development effort between the IETF and another
standards development organization or the document is a standards development organization or the document is a
republication of the work of another standards organization. Such republication of the work of another standards organization. Such
exceptions must be approved on an individual basis by the IAB. exceptions must be approved on an individual basis by the IAB.
4.3 In Section 5.6 of RFC 3978, all occurrences of "Internet Society" 5.3 In Section 5.6 of RFC 3978, all occurrences of "Internet Society"
or "ISOC" are replaced by "IETF Trust". or "ISOC" are replaced by "IETF Trust".
to reduce confusion the note about multiple copyright notices to reduce confusion the note about multiple copyright notices
4.4 In Section 5.5 of RFC 3978, ", THE IETF TRUST" is inserted after 5.4 In Section 5.5 of RFC 3978, ", THE IETF TRUST" is inserted after
"INTERNET SOCIETY". "INTERNET SOCIETY".
5. Errata 6. Errata
5.1 The two sentences of Section 4.2(a)(C) are combined into a single 6.1 The two sentences of Section 4.2(a)(C) are combined into a single
sentence separated by a comma. sentence separated by a comma.
5.2 In Section 7.1, all occurrences of "Internet Society" or "ISOC" are 6.2 In Section 7.1, all occurrences of "Internet Society" or "ISOC" are
replaced by "IETF Trust". replaced by "IETF Trust".
5.3 The section reference at the end of the first paragraph of Section 6.3 The section reference at the end of the first paragraph of Section
7.3 is changed from 3.3(E) to 3.3(C). 7.3 is changed from 3.3(E) to 3.3(C).
5.4. In Section 8, ", the IETF Trust" is inserted after "ISOC". 6.4. In Section 8, ", the IETF Trust" is inserted after "ISOC".
6. References 7. References
6.1. Normative References 7.1. Normative References
[RFC 3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78, [RFC 3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78,
RFC 3978, March 2005. RFC 3978, March 2005.
[BCP 101] Austein, R., and B. Wijnen, "Structure of the IETF [BCP 101] Austein, R., and B. Wijnen, "Structure of the IETF
Administrative Support Activity (IASA)," BCP 101, RFC 4071, April Administrative Support Activity (IASA)," BCP 101, RFC 4071, April
2005. 2005.
[IETF Trust Agreement?] [IETF Trust Agreement?]
7. Acknowledgements 8. Acknowledgements
Thanks to Jorge Contreras from Wilmer, Cutler, Pickering, Hale and Thanks to Jorge Contreras from Wilmer, Cutler, Pickering, Hale and
Dorr LLP who provided a significant rewrite of my material. Dorr LLP who provided a significant rewrite of my material.
8. Editor's Address 9. 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
9. Full copyright statement 10. Full copyright statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. 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,
skipping to change at line 375 skipping to change at page 11, line 15
http://www.ietf.org/ipr. The IETF invites any interested party to http://www.ietf.org/ipr. The IETF invites any interested party to
bring to its attention any copyrights, patents or patent bring to its attention any copyrights, patents or patent
applications, or other proprietary rights that may cover technology applications, or other proprietary rights that may cover technology
that may be required to implement this standard. Please address the that may be required to implement this standard. Please address the
information to the IETF at ietf-ipr@ietf.org. 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.
Changes
Note to RFC Editor - remove this section if this document is
published as an RFC
version 3 to version 4
major rewrite based on input from Jorge
version 4 to version 5
various places cleaned up removal of outbound rights
version 5 to version 6
added section 2.3
added a new section 4 and renumbered the old section 4 and the
sections following
 End of changes. 19 change blocks. 
18 lines changed or deleted 128 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/