draft-ietf-ipr-rules-update-02.txt   draft-ietf-ipr-rules-update-03.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Editor Editor
December 2005 January 2006
RFC 3978 Update RFC 3978 Update
<draft-ietf-ipr-rules-update-02.txt> <draft-ietf-ipr-rules-update-03.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 1, line 35 skipping to change at page 1, line 35
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 May 19, 2005. This Internet-Draft will expire on June 25, 2006.
Abstract Abstract
This document modifies "IETF Rights in Contributions" so that the This document modifies "IETF Rights in Contributions" so that the
IETF gets the right to permit extraction of material from RFCs, and IETF gets the right to permit extraction of material from RFCs, and
the right to permit others to create derivative works outside the the right to permit others to create derivative works outside the
IETF process. IETF process.
It does not constrain how the IETF exercises those rights. It does not constrain how the IETF exercises those rights.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society. (2005) Copyright (C) The Internet Society. (2006)
1. Introduction 1. Introduction
Currently the IETF requires that authors of contributions to the IETF Currently the IETF requires that authors of contributions to the IETF
grant to the IETF a limited set of non-exclusive rights and grant to the IETF a limited set of non-exclusive rights and
permissions to a document as part of the process of submitting the permissions to a document as part of the process of submitting the
contribution. These rights and permissions are detailed in Section contribution. These rights and permissions are detailed in Section
3.3 of "IETF Rights in Contributions" (RFC 3978 - BCP 78) [RFC3978]. 3.3 of "IETF Rights in Contributions" (RFC 3978 - BCP 78) [RFC3978].
This memo updates this section of RFC 3978 to add the rights for the This memo updates this section of RFC 3978 to add the rights for the
IETF to 1/ permit the extraction of material from RFCs for a wide IETF to 1/ permit the extraction of material from RFCs for a wide
skipping to change at page 2, line 38 skipping to change at page 2, line 38
changes such as changes to fonts, and translations into languages changes such as changes to fonts, and translations into languages
other than English would be permitted. other than English would be permitted.
2.1 New paragraph 3.3 (c) 2.1 New paragraph 3.3 (c)
This memo replaces paragraph 3.3(a)(E) of RFC 3978 with the This memo replaces paragraph 3.3(a)(E) of RFC 3978 with the
following: following:
(E) to extract, copy, publish, display, distribute and incorporate (E) to extract, copy, publish, display, distribute and incorporate
into other works, for any purpose (and not limited to use within into other works, for any purpose (and not limited to use within
the IETF Standards Process), and to grant third parties the IETF Standards Process), and to grant third parties perpetual
sublicenses to do the same, any portion of the Contribution and non-revocable sublicenses to do the same, any portion of the
without modification (other than non-substantive modifications Contribution without modification (other than non-substantive
such as translation into languages other than English or modifications such as translation into languages other than
compilation of source code statements into executable code), and English or compilation of source code statements into executable
further provided that the notices required by Sections 5.4 or 5.6 code), and further provided that the notices required by Sections
below, as applicable, are included. 5.4 or 5.6 below, as applicable, are included.
2.2 Reformat a section of the old paragraph 3.3(a)(E) 2.2 Reformat a section of the old paragraph 3.3(a)(E)
The patent disclaimer text at the end of 3.3(a)(E) really should The patent disclaimer text at the end of 3.3(a)(E) really should
apply to the entire license grant in 3.3(a), and not just the grant apply to the entire license grant in 3.3(a), and not just the grant
in subparagraph 3.3(a)(E). the following free-standing sentence is in subparagraph 3.3(a)(E). the following free-standing sentence is
placed at the end of 3.3(a), separated by a carriage return and placed at the end of 3.3(a), separated by a carriage return and
space from (E): space from (E):
The licenses granted in this Section 3.3(a) shall not be deemed to The licenses granted in this Section 3.3(a) shall not be deemed to
skipping to change at page 3, line 24 skipping to change at page 3, line 24
reproduce RFCs as-is or as translations. The permission to do so was reproduce RFCs as-is or as translations. The permission to do so was
not specifically noted in early RFCs (other than a note to say that not specifically noted in early RFCs (other than a note to say that
the distribution of the RFC was unlimited). The copyright notice the distribution of the RFC was unlimited). The copyright notice
introduced with RFC 1602 specifically granted these permissions. But introduced with RFC 1602 specifically granted these permissions. But
an unintended byproduct of the attempt in BCP 78 to simplify the an unintended byproduct of the attempt in BCP 78 to simplify the
copyright statement in published RFCs was the lack of of any specific copyright statement in published RFCs was the lack of of any specific
statement of these permissions in the RFC copyright notice or in BCP statement of these permissions in the RFC copyright notice or in BCP
78. This memo adds the following paragraph to RFC 3978 Section 3.3. 78. This memo adds the following paragraph to RFC 3978 Section 3.3.
(F) to permit third parties to copy, publish, display and distribute (F) to permit third parties to copy, publish, display and distribute
the Contribution without modification (except for translation into the Contribution without modification, as part of a full,
languages other than English) as part of a full, unmodified RFC unmodified RFC and to permit third parties to translate the
(which may be translated into the same language as such Contribution as part of a full, unmodified RFC into languages
Contribution), for any purpose, whether or not within the IETF other than English, for any purpose, whether or not within the
Standards Process. IETF Standards Process.
Note, of course, that this language itself is not a grant FROM the Note, of course, that this language itself is not a grant FROM the
IETF to any third party. Rather, it is a grant from the author TO IETF to any third party. Rather, it is a grant from the author to
the IETF. The permission granted by IETF to the world is encapsulated the IETF.
in the legend that accompanies the RFC series documents:
"Distribution of this memo is unlimited".
To make the permission unambiguous this memo changes the existing
legend to:
Permission is granted to translate this document or portions of
this document into languages other than English. Permission is
also hereby granted to copy, publish, display and distribute this
document or portions of this document, or their translations,
without additional modification.
3. Right to authorize the development of derivative works 3. Right to authorize the development of derivative works
Currently the IETF obtains from Contributors the right to prepare Currently the IETF obtains from Contributors the right to prepare
derivative within the IETF Standards Process. This is done in RFC derivative within the IETF Standards Process. This is done in RFC
3978 Section 3.3 (a) (C). This memo proposes to modify that 3978 Section 3.3 (a) (C). This memo proposes to modify that
paragraph to grant the IETF the ability to authorize the preparation paragraph to grant the IETF the ability to authorize the preparation
of derivative works without limiting such development to being done of derivative works without limiting such development to being done
within the IETF Standards Process. This paragraph does not, by within the IETF Standards Process. This paragraph does not, by
itself, grant any additional permissions outside of the IETF, but itself, grant any additional permissions outside of the IETF, but
does empower the IETF, on a case by case basis, to authorize the does empower the IETF to authorize the development of derivative
development of derivative works, outside of the IETF Standards works, outside of the IETF Standards Process. One example of where
Process. One example of where the IETF might grant such a right is the IETF might grant such a right is the case where another standards
the case where another standards development organization (SDO) wants development organization (SDO) wants to update or extend an IETF
to update or extend an IETF technology (which would normally be done technology (which would normally be done by the SDO sending their
by the SDO sending their requirements to the IETF) but the IETF no requirements to the IETF) but the IETF no longer has a working group
longer has a working group focused on the particular technology and focused on the particular technology and the IETF does not have the
the IETF does not have the interest to create a new working group. interest to create a new working group.
3.1 Revised Section 3.3 (a) (C) 3.1 Revised Section 3.3 (a) (C)
This memo replaces RFC 3978 Section 3.3 (a) (C) with the following This memo replaces RFC 3978 Section 3.3 (a) (C) with the following
paragraph: paragraph:
(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], Contribution [as per Section 5.2 below],
(1) to prepare derivative works (in addition to translations) that (1) to prepare derivative works (in addition to translations) that
skipping to change at page 5, line 7 skipping to change at page 4, line 45
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
6. Full copyright statement 6. Full copyright statement
Copyright (C) The Internet Society (2005). 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,
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.
 End of changes. 9 change blocks. 
38 lines changed or deleted 27 lines changed or added

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