draft-ietf-ipr-rules-update-00.txt   draft-ietf-ipr-rules-update-01.txt 
Network Working Group S. Bradner Network Working Group S. Bradner
Internet-Draft Harvard University Internet-Draft Harvard University
Editor Editor
October 2005 October 2005
RFC 3978 Update RFC 3978 Update
<draft-ietf-ipr-rules-update-00.txt> <draft-ietf-ipr-rules-update-01.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 March 3, 2005. This Internet-Draft will expire on March 10, 2005.
Abstract Abstract
This Internet Draft proposes two additions to "IETF Rights in This Internet Draft proposes two additions to "IETF Rights in
Contributions" (RFC3978). The first addition permits the extraction Contributions" (RFC3978). The first addition permits the extraction
of material from IETF RFCs for a wide range of uses. The second of material from IETF RFCs for a wide range of uses. The second
addition obtains from contributors the right, but not the addition obtains from contributors the right, but not the
requirement, to grant permission to create derivative outside of the requirement, to grant permission to create derivative outside of the
IETF Standards Process. IETF Standards Process.
Copyright Notice Copyright Notice
skipping to change at page 3, line 10 skipping to change at page 3, line 10
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
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 Contributor similar intellectual property right disclosed by the Contributor
under BCP 79. under BCP 79.
2.3 Make clear the right to reprint RFCs
Since the start of the RFC series third parties have been free to
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
the distribution of the RFC was unlimited). The copyright notice
introduced with RFC 1602 specifically granted these permissions. But
an unintended byproduct of the attempt in BCP 78 to simplify the
copyright statement in published RFCs was the lack of of any specific
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.
(F) to permit third parties to copy, publish, display and distribute
the Contribution without modification (except for translation into
languages other than English) as part of a full, unmodified RFC
(which may be translated into the same language as such
Contribution), for any purpose, whether or not within the IETF
Standards Process.
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
the IETF. The permission granted by IETF to the world is encapsulated
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, on a case by case basis, to authorize the
 End of changes. 3 change blocks. 
2 lines changed or deleted 36 lines changed or added

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