idnits 2.17.1 draft-ietf-ipr-ietf-trust-update-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 179. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 190. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 201. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 201. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year (Using the creation date from RFC3978, updated by this document, for RFC5378 checks: 2004-06-23) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 2006) is 6431 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3978 (Obsoleted by RFC 5378) ** Obsolete normative reference: RFC 4071 (ref. 'BCP101') (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Bradner 3 Internet-Draft Harvard University 4 Updates: RFC 3978 Editor 5 September 2006 7 RFC 3978 Update to recognize the IETF Trust 9 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 This Internet-Draft will expire on February 5, 2007. 36 Abstract 37 This document updates RFC 3978 "IETF Rights in Contributions" to 38 recognize that the IETF Trust is now the proper custodian of all 39 IETF-related intellectual property rights. 41 This document does not constrain how the IETF Trust exercises those 42 rights. 44 Copyright Notice 45 Copyright (C) The Internet Society. (2006) 47 1. Introduction 48 1.1 IETF Trust 50 Currently the IETF requires that authors of Contributions to the IETF 51 grant to the IETF (meaning the full set of participants in the IETF 52 Standards Process) a limited set of non-exclusive rights and 53 permissions as part of the process of submitting such Contribution. 54 These rights and permissions are detailed in "IETF Rights in 55 Contributions" (RFC 3978 - BCP 78) [RFC3978]. 57 The IETF Trust was recently formed to act as the administrative 58 custodian of all copyrights and other intellectual property rights 59 relating to the IETF Standards Process that had previously been held 60 by ISOC and CNRI (See [IETF Trust Agreement]). 62 The IETF is supported by an IETF Administrative Support Activity 63 (IASA) defined in BCP 101 [BCP101]. BCP 101 was updated by [RFC4371] 64 to recognize the creation of the IETF Trust. 66 This document updates RFC 3978 in order to recognize the IETF Trust 67 and to implement the structure needed to support it. Most 68 importantly, it alters the license-grant path as follows: whereas 69 previously authors of Contributions to the IETF would grant a license 70 ISOC, such authors will grant a license to the IETF Trust (in Section 71 3.3). This document concerns itself only with changes to RFC 3978 72 needed to recognize the creation of the IETF Trust. 74 This introductory section is to provide context for the reader. 75 Section 2 of this document is intended to be normative. 77 2. Updates to RFC 3978 79 The text of RFC 3978 is hereby updated as set forth below to reflect 80 the creation of the IETF Trust. 82 2.1. Update introduction 84 In the third paragraph of Section 2 replace "IETF and Internet 85 Society (ISOC)" with "IETF Trust and the IETF" and replace "IETF and 86 ISOC" with "IETF Trust and the IETF." 88 2.2. Update Section 3.3 90 In section 3.3 replace two instances of "ISOC and the IETF" and one 91 instance of "IETF and ISOC" with "IETF Trust and the IETF." 93 2.3. Update Section 3.4 94 In Section 3.4(b) add "IETF Trust, " after "IETF,". 96 2.4. Update Section 4.2 98 In section 4.2 replace two instances of "ISOC and the IETF" and one 99 instance of "IETF and ISOC" with "IETF Trust and the IETF." 101 2.5. Update Section 5 103 In Section 5 change two instances of "ISOC" to "IETF Trust." 105 2.6. Update copyright statement 107 Replace "Internet Society" with "IETF Trust" in the copyright 108 statement in Section 5.4. 110 2.7. Update Section 5.5 112 In Section 5.5 insert ", THE IETF TRUST" after "INTERNET SOCIETY". 114 2.8. Update Section 5.6 116 In Section 5.6, replace all occurrences of "Internet Society" with 117 "IETF Trust". 119 2.9. Update Section 7.1 121 In Section 7.1, replace two instances of "IETF/ISOC" with "IETF Trust 122 and IETF". 124 2.10. Update Section 8 126 In Section 8, insert ", the IETF Trust" after "ISOC". 128 3. References 130 3.1. Normative References 132 [RFC3978] Bradner, S., Ed., "IETF Rights in Contributions", BCP 78, 133 RFC 3978, March 2005. 135 [BCP101] Austein, R., and B. Wijnen, "Structure of the IETF 136 Administrative Support Activity (IASA)," BCP 101, RFC 4071, April 137 2005. 139 [RFC4371] Carpenter, B., and L. Lynch Ed., " BCP 101 Update for IPR 140 Trust," RFC 4371, January 2006 142 [IETF Trust Agreement] 143 www.ietf.org/trust/IETFtrustAgreement20051208.pdf 145 4. Security Considerations 147 This type of process document does not have a direct impact on the 148 security of the Internet or Internet protocols. 150 5. IANA Considerations 152 (Note to RFC Editor - this section to be removed before publication 153 as a RFC) 155 There are no IANA actions required by this document. 157 6. Editor's Address 159 Scott Bradner 160 Harvard University 161 29 Oxford St. 162 Cambridge MA, 02138 164 Phone: +1 617 495 3864 165 EMail: sob@harvard.edu 167 7. Full copyright statement 169 Copyright (C) The Internet Society (2006). This document is subject 170 to the rights, licenses and restrictions contained in BCP 78, and 171 except as set forth therein, the authors retain all their rights. 173 This document and the information contained herein are provided on an 174 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 175 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 176 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 177 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 178 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 179 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 181 Intellectual Property 183 The IETF takes no position regarding the validity or scope of any 184 Intellectual Property Rights or other rights that might be claimed to 185 pertain to the implementation or use of the technology described in 186 this document or the extent to which any license under such rights 187 might or might not be available; nor does it represent that it has 188 made any independent effort to identify any such rights. Information 189 on the procedures with respect to rights in RFC documents can be 190 found in BCP 78 and BCP 79. 192 Copies of IPR disclosures made to the IETF Secretariat and any 193 assurances of licenses to be made available, or the result of an 194 attempt made to obtain a general license or permission for the use of 195 such proprietary rights by implementers or users of this 196 specification can be obtained from the IETF on-line IPR repository at 197 http://www.ietf.org/ipr. The IETF invites any interested party to 198 bring to its attention any copyrights, patents or patent 199 applications, or other proprietary rights that may cover technology 200 that may be required to implement this standard. Please address the 201 information to the IETF at ietf-ipr@ietf.org. 203 Acknowledgement 205 Funding for the RFC Editor function is currently provided by the 206 Internet Society.