Network Working Group S. Bradner Internet-Draft Harvard University July 2005 Obtaining Additional Permissions from Contributors Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Abstract This is a proposed update to "IETF Rights in Contributions" (RFC 3978 - BCP 78). It proposes a change in the rights required from authors of contributors to the IETF. Copyright Notice Copyright (C) The Internet Society. (2005) 1. Introduction Currently the IETF requires that authors of contributions to the IETF grant to the IETF a limited set of non-exclusive rights and permissions to a document as part of the process of submitting the contribution. These rights and permissions are detailed in Section Bradner [Page 1] Internet-Draft IETF Permissions from Contributors July 2005 3.3 of "IETF Rights in Contributions" (RFC 3978 - BCP 78) [RFC3978]. This current memo proposes a replacement for a paragraph in this section to add the right for the IETF to permit the creation of derivative works in any venue, not limited to within the IETF Standards Process. This proposal is a result of the discussion in the IPR Working Group session during IETF 62 in Minneapolis, MN. 2. Current 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, 3. Revised 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 (in addition to translations) that are based on or incorporate all or part of the Contribution, or comment upon it, within the IETF Standards Process or to authorize preparation of such derivative works outside of the IETF Standards Process. The license to such derivative works not granting any more rights than the license to the original Contribution, 4. Security Considerations This proposed revision of RFC 39978 has no direct security implications. 5. References 5.1 Normative References [RFC3978] "IETF Rights in Contributions," S. Bradner, RFC 3978 also BCP 78, March 2005 6. Editor's Address Scott Bradner Harvard University 29 Oxford St. Cambridge MA, 02138 Phone: +1 617 495 3864 EMail: sob@harvard.edu Bradner [Page 2] Internet-Draft IETF Permissions from Contributors July 2005 7. Full copyright statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Bradner [Page 3]