Presentation is loading. Please wait.

Presentation is loading. Please wait.

Derivative Works Authors Rights in RFCs authors retain almost all copy rights in the material in their RFCs IETF/ISOC gets rights needed.

Similar presentations


Presentation on theme: "Derivative Works Authors Rights in RFCs authors retain almost all copy rights in the material in their RFCs IETF/ISOC gets rights needed."— Presentation transcript:

1 Derivative Works sob@harvard.edu

2 Authors Rights in RFCs authors retain almost all copy rights in the material in their RFCs IETF/ISOC gets rights needed to publish ID/RFC and to operate the IETF Standards process author can deny right to make derivative works author(s) retain all other rights can publish as an op-ed column or a novel, give to another SDO etc

3 IETF RFCs Dealing with RFCs RFC 1310 - March 1992 RFC 1602 - March 1994 RFC 2026 - October 1996 RFC 3667 - February 2004 RFC 3978 - March 2005 all deal with inbound rights rights granted to IETF by authors

4 Rights Grants by RFC Authors pre RFC 1602 (including RFC 1310) copyright & derivative works not mentioned assumption was that RFCs could be modified & republished by anyone still the case for non-IETF RFCs RFC 1602 right to make derivative works given to IETF section 5.4.1 (1) & agreement in section 5.6

5 Author Rights Grants, contd. RFC 2026 right to make derivative works given to ISOC & IETF section 10.3.1 (1) note in copyright notice (sec 10.4 (C)

6 RFC 2026 Copyright Notice This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

7 Author Rights Grants, contd. RFC 3667 right to make derivative works within IETF standards process given to ISOC & IETF Section 3.3 (a) (C) note translation text (Section 3.3 (a) (B) (B) to prepare or allow the preparation of translations of the Contribution into languages other than English

8 Author Rights Grants, contd. RFC 3667 Section 3.3 (a) (C) (C) unless explicitly disallowed in the notices contained in a Contribution [as per Section 5.2 below], to prepare derivative works (other than translations) that are based on or incorporate all or part of the Contribution, or comment upon it, within the IETF Standards Process. The license to such derivative works not granting the ISOC and the IETF any more rights than the license to the original Contribution,

9 Author Rights Grants, contd. RFC 3978 - same as RFC 3667

10 draft-ietf-ipr-rules-update-01.txt proposes getting the right for the IETF to allow the creation of derivative works outside of standards process (2) on a case by case basis, to grant third parties the right to prepare derivative works of the Contribution outside of the IETF Standards Process and to copy, publish, display and distribute such derivative works outside the IETF Standards Process, subject to a requirement to properly acknowledge the IETF,

11 Questions should the IETF get the right to grant the right to make derivative works outside of IETF Standards Process if yes, what should the criteria be? should the IETF granting of this right be on a case-by-case basis or a blanket permission? if yes, should there be criteria?


Download ppt "Derivative Works Authors Rights in RFCs authors retain almost all copy rights in the material in their RFCs IETF/ISOC gets rights needed."

Similar presentations


Ads by Google