draft-ietf-ipr-3978-incoming-07.txt   draft-ietf-ipr-3978-incoming-08.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Intended status: BCP Jorge Contreras Intended status: BCP Jorge Contreras
WilmerHale WilmerHale
Editors Editors
4 February 2008
Rights Contributors provide to the IETF Trust Rights Contributors provide to the IETF Trust
<draft-ietf-ipr-3978-incoming-07.txt> <draft-ietf-ipr-3978-incoming-08.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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
skipping to change at page 1, line 36 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 4, 2008. This Internet-Draft will expire on September 24, 2008.
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
5.6. Representations and Warranties 5.6. Representations and Warranties
5.7. No Duty to Publish 5.7. No Duty to Publish
5.8. Trademarks 5.8. Trademarks
5.9. Copyright in RFCs 5.9. Copyright in RFCs
6. Legends, Notices and Other Standardized Text in IETF Documents 6. Legends, Notices and Other Standardized Text in IETF Documents
7. Security Considerations 7. Security Considerations
8. References 8. References
8.1. Normative References 8.1. Normative References
8.2. Informative References 8.2. Informative References
9. Acknowledgements 9. Acknowledgements
10. Editors' Addresses 10. Changes since RFC 3978
11. Editors' Addresses
Full Copyright Statement Full Copyright Statement
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 [RFC2028]. Editor," are defined in [RFC2028].
a. "Contribution": any submission to the IETF intended by the a. "Contribution": any submission to the IETF intended by the
Contributor for publication as all or part of an Internet-Draft or Contributor for publication as all or part of an Internet-Draft or
RFC (except for RFC Editor Contributions described in Section 4 RFC (except for RFC Editor Contributions described in Section 4
skipping to change at page 3, line 32 skipping to change at page 3, line 33
has in a work, such as the rights to copy, publish, distribute and has in a work, such as the rights to copy, publish, distribute and
create derivative works of the work. An author often cedes these create derivative works of the work. An author often cedes these
rights to his or her employer or other parties as a condition of rights to his or her employer or other parties as a condition of
employment or compensation. employment or compensation.
e. "IETF": In the context of this document, the IETF includes all e. "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.
f. "IETF Documents": RFCs and Internet-Drafts. f. "IETF Documents": RFCs and Internet-Drafts that are used in the
IETF Standards Process as defined in 1(g).
g. "IETF Standards Process": the activities undertaken by the IETF in g. "IETF Standards Process": the activities undertaken by the IETF in
any of the settings described in 1(a) above. any of the settings described in 1(a) above.
h. "IETF Trust": A trust established under the laws of the h. "IETF Trust": A trust established under the laws of the
Commonwealth of Virginia, USA, in order to hold and administer Commonwealth of Virginia, USA, in order to hold and administer
intellectual property rights for the benefit of the IETF. intellectual property rights for the benefit of the IETF.
i. "Internet-Draft": temporary documents used in the IETF Standards i. "Internet-Draft": temporary documents used in the IETF Standards
Process. Internet-Drafts are posted on the IETF web site by the Process. Internet-Drafts are posted on the IETF web site by the
IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet- IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet-
Drafts have a nominal maximum lifetime of six months in the IETF Drafts have a nominal maximum lifetime of six months in the IETF
Secretariat's public directory. Secretariat's public directory.
skipping to change at page 8, line 19 skipping to change at page 8, line 21
Standards Process (e.g., via e-mail, oral comment and otherwise). Standards Process (e.g., via e-mail, oral comment and otherwise).
However, it is important that the IETF (through the IETF Trust) own However, it is important that the IETF (through the IETF Trust) own
the copyright in documents that are published as RFCs (other than the copyright in documents that are published as RFCs (other than
Informational RFCs and RFCs that are submitted as RFC Editor Informational RFCs and RFCs that are submitted as RFC Editor
Contributions). Ownership of the copyright in an RFC does not Contributions). Ownership of the copyright in an RFC does not
diminish the Contributors' rights in their underlying contributions, diminish the Contributors' rights in their underlying contributions,
but it does prevent anyone other than the IETF Trust (and its but it does prevent anyone other than the IETF Trust (and its
licensees) from republishing or modifying an RFC in RFC format. In licensees) from republishing or modifying an RFC in RFC format. In
this respect, Contributors are treated the same as anybody else: this respect, Contributors are treated the same as anybody else:
though they may extract and republish their own Contributions without though they may extract and republish their own Contributions without
limitation, they may not do so in the IETF's RFC format. And while limitation, they may not do so in the RFC format used by the IETF.
this principle (which is included in Section 5.9 below) may appear to And while this principle (which is included in Section 5.9 below) may
be new to IETF, it actually reflects historical practice and has been appear to be new to IETF, it actually reflects historical practice
observed for many years through the inclusion of an ISOC or IETF and has been observed for many years through the inclusion of an ISOC
Trust copyright notice on all RFC documents since the publication of or IETF Trust copyright notice on all RFC documents since the
RFC 2026. publication of RFC 2026.
4. RFC Editor Documents 4. RFC Editor Documents
This document only relates to Contributions made as part of the IETF This document only relates to Contributions made as part of the IETF
Standards Process. Other documents that are referred to as Internet- Standards Process. Other documents that are referred to as Internet-
Drafts and RFCs may be submitted to and published by the RFC Editor Drafts and RFCs may be submitted to and published by the RFC Editor
independently of the IETF Standards Process. Such "RFC Editor independently of the IETF Standards Process. Such "RFC Editor
Documents" are not covered by this document. RFC Editor Documents" are not covered by this document. RFC Editor
Contributions must be marked appropriately as described in the Legend Contributions must be marked appropriately as described in the Legend
Instructions. See the RFC Editor web page for information about the Instructions. See the RFC Editor web page for information about the
policies concerning rights in RFC Editor Documents. policies concerning rights in RFC Editor Documents.
skipping to change at page 9, line 50 skipping to change at page 10, line 5
are included in the Contribution solely in connection with the are included in the Contribution solely in connection with the
reproduction, distribution or publication of the Contribution and reproduction, distribution or publication of the Contribution and
derivative works thereof as permitted by this Section 5.3, derivative works thereof as permitted by this Section 5.3,
provided that when reproducing Contributions, trademark and provided that when reproducing Contributions, trademark and
service mark identifiers used in the Contribution, including TM service mark identifiers used in the Contribution, including TM
and (R), will be preserved. and (R), will be preserved.
5.4. Sublicenses by IETF Trust 5.4. Sublicenses by IETF Trust
The IETF Trust will sublicense the rights granted to it under Section The IETF Trust will sublicense the rights granted to it under Section
5.3 to all IETF participants for use within the IETF Standards 5.3 to all IETF participants for use within the IETF Standards
Process. This license is expressly granted under [TRUST LICENSE Process. This license is expressly granted under a license agreement
DOCUMENT]. issued by the IETF Trust and must contain a pointer to the full IETF
Trust agreement.
In addition, the IETF Trust may grant additional sublicenses of the In addition, the IETF Trust may grant additional sublicenses of the
licenses granted to it hereunder. In doing so, the IETF Trust will licenses granted to it hereunder. In doing so, the IETF Trust will
comply with the guidance provided under RFC xxx [-outbound]. comply with the guidance provided under RFC xxx [-outbound].
5.5. No Patent License 5.5. No Patent License
The licenses granted in Section 5.3 shall not be deemed to grant any The licenses granted in Section 5.3 shall not be deemed to grant any
right under any patent, patent application or other similar right under any patent, patent application or other similar
intellectual property right disclosed by the Contributor under BCP 79 intellectual property right disclosed by the Contributor under BCP 79
or otherwise. or otherwise.
skipping to change at page 12, line 51 skipping to change at page 13, line 7
[-outgoing] Halpern, J., "Advice to the Trustees of the IETF Trust on [-outgoing] Halpern, J., "Advice to the Trustees of the IETF Trust on
Rights to be Granted in IETF Documents," RFC XXXX, date Rights to be Granted in IETF Documents," RFC XXXX, date
[Berne Convention] "Berne Convention for the Protection of Literary [Berne Convention] "Berne Convention for the Protection of Literary
and Artistic Work", and Artistic Work",
http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html
9. Acknowledgements 9. Acknowledgements
The editors would like to acknowledge the help of the IETF IPR The editors would like to acknowledge the help of the IETF IPR
Working Group provided during the development of the document. Working Group provided during the development of the document.
10. Editors' Addresses 10. Changes since RFF 3978
This document represents a significant reorganization and rewording
of RFC 3978 along with a number of substantive changes.
The most basic change is to limit this document to the rights that a
Contributor grants to the IETF Trust when making a Contribution. All
sublicenses of rights for the use of IETF Documents must be provided
by the IETF Trust. (See Section 5.4.)
Material added from RFC 4748 that recognized the IETF Trust.
Most of the material relating to RFC-Editor documents has been
removed since the RFC-Editor maintains their own rules and processes
for RFC-Editor documents.
Changes in the definitions section include defining the terms
"Contribution," "Indirect Contributor," "Copyright," "IETF Trust,"
and "Legend Instructions" as well as minor tweaks to some of the
other definitions.
The responsibility for the text of notices has been given to the IETF
Trust and removed from this document. (See Section 6.)
Clarified that Contributors enter into a legally binding contract
when they submit a Contribution. (See Section 5.1.)
The right to produce derivative works provided by the Contributor to
the IETF Trust is not limited to being within the IETF Standards
Process.
Made it clear that this document does not deal with patent licenses.
(See Section 5.5.)
Clarified the ownership of the Copyrights to IETF Documents. (See
Section 5.9.)
Clarified the rights retained by authors of IETF Contributions. (See
Section 5.10.)
11. Editors' Addresses
Scott Bradner Scott Bradner
Harvard University Harvard University
29 Oxford St. 29 Oxford St.
Cambridge MA, 02138 USA Cambridge MA, 02138 USA
Phone: +1 617 495 3864 Phone: +1 617 495 3864
EMail: sob@harvard.edu EMail: sob@harvard.edu
Jorge L. Contreras Jorge L. Contreras
WilmerHale WilmerHale
1875 Pennsylvania Avenue NW 1875 Pennsylvania Avenue NW
skipping to change at page 14, line 30 skipping to change at page 15, line 28
added pp on multiple copyright notices to sec 6 added pp on multiple copyright notices to sec 6
version 02 ->03 version 02 ->03
replaced the text in section 5.10 replaced the text in section 5.10
version 03 -> 04 version 03 -> 04
change "requested" to "directed" in section 5.10 change "requested" to "directed" in section 5.10
add sections 1 & 2 to the list of normative sections in section 2 add sections 1 & 2 to the list of normative sections in section 2
sec 5.7 - replace last sentence sec 5.7 - replace last sentence
sec 5.3 preface - add "sublicensable" sec 5.3 preface - add "sublicensable"
sec 1 i - add that the IETF Trust maintains the Legend Instructions sec 1 i - add that the IETF Trust maintains the Legend
Instructions
open issues open issues
a/ the use of the terms Contribution and Contributors - a/ the use of the terms Contribution and Contributors -
for example in section 5.6 for example in section 5.6
b/ do we need specific mention of work for hire in sec 3.2 b/ do we need specific mention of work for hire in sec 3.2
version 04 -> 05 version 04 -> 05
replaced section 5.1 & the 1st pp of section 5.3 replaced section 5.1 & the 1st pp of section 5.3
replaced section 5.6 a replaced section 5.6 a
version 05 -> 06 - input from Jorge version 05 -> 06 - input from Jorge
fix various typos in document fix various typos in document
add definition of "Indirect Contributor" add definition of "Indirect Contributor"
fix definition of "Reasonably and personally known" to be copyright- fix definition of "Reasonably and personally known" to be
related rather than patent-related copyright-related rather than patent-related
reword sec 5.6 a and remove definition of "Indirect Contributor" reword sec 5.6 a and remove definition of "Indirect Contributor"
add pointer to section 5.6 to section 5.9 add pointer to section 5.6 to section 5.9
tweak the wording on section 5.10 tweak the wording on section 5.10
add "development" to the next to last sentence of section 6 add "development" to the next to last sentence of section 6
version 06 -> 07 version 06 -> 07
fix references etc to mollify the ID nits checker fix references etc to mollify the ID nits checker
version 07 -> 08
change "the IETF's RFC format" to "the RFC format used by the
IETF" in section 3.6
tweak definition of IETF Documents
change "[TRUST LICENSE AGREEMENT]" to "a license agreement issued
by the IETF Trust" and add a requirement that licenses must point
to the full trust agreement in section 5.4
added "changes from 3987" section 10
 End of changes. 11 change blocks. 
18 lines changed or deleted 59 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/