idnits 2.17.1 draft-narten-ipr-3979-3rd-party-fix-00.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 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 182. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 143. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 150. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 156. ** 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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 13, 2006) is 6398 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 3979 (Obsoleted by RFC 8179) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Thomas Narten 3 IBM 4 October 13, 2006 6 Clarification of the 3rd Party Disclosure procedure in RFC 3979 8 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/1id-abstracts.html 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 This Internet-Draft expires in six months. 35 Abstract 37 This document clarifies and updates a single sentence in RFC 3979. 38 Specifically, when 3rd party IPR disclosures are made, the intention 39 is that the IETF Executive Director notify the IPR holder that a 3rd 40 party disclosure has been filed, and to ask the IPR holder whether 41 they have any disclosure that needs to be made, per applicable 42 RFC3979 rules. 44 Contents 46 Status of this Memo.......................................... 1 48 1. Introduction............................................. 2 50 2. The Fix.................................................. 2 52 3. Security Considerations.................................. 3 54 4. IANA Considerations...................................... 3 56 5. Acknowledgments.......................................... 3 58 6. Notes (To be removed upon RFC Publication)............... 3 60 7. Normative References..................................... 3 62 8. Author's Address......................................... 3 64 1. Introduction 66 This document clarifies and updates a single sentence in RFC 3979 67 [RFC3979]. Specifically, when 3rd party IPR disclosures are made, the 68 intention is that the IETF Executive Director notify the IPR holder 69 that a 3rd party disclosure has been filed, and to ask the IPR holder 70 whether they have any disclosure that needs to be made, per 71 applicable RFC3979 rules. 73 This document updates RFC 3979. 75 2. The Fix 77 RFC3979, Section 4 (C), states: 79 (C) Where Intellectual Property Rights have been disclosed for IETF 80 Documents as provided in Section 6 of this document, the IETF 81 Executive Director shall request from the discloser of such IPR, 82 a written assurance that upon approval by the IESG for 83 publication as RFCs of the relevant IETF specification(s), all 84 persons will be able to obtain the right to implement, use, 85 distribute and exercise other rights with respect to 86 Implementing Technology under one of the licensing options 87 specified in Section 6.5 below unless such a statement has 88 already been submitted. 90 In the case of third party disclosures, it makes no sense to ask the 91 discloser about potential licensing terms, since they do not own the 92 IPR. Instead, it only makes sense to ask the IPR holder. 94 This document updates RFC3979 by changing the word "discloser" to 95 "IPR holder" in the above text. 97 3. Security Considerations 99 This document has no known security implications. 101 4. IANA Considerations 103 This document makes no requests to IANA. 105 5. Acknowledgments 107 6. Notes (To be removed upon RFC Publication) 109 This topic was discussed during the March, 2006 IPR WG meeting in 110 Dallas. See the minutes under the section "3rd Party Disclosure 111 Verification" at 112 http://www3.ietf.org/proceedings/06mar/minutes/ipr.txt. 114 The topic was also discussed on the mailing list after the Dallas 115 meeting. 117 7. Normative References 119 [RFC3979] "Intellectual Property Rights in IETF Technology," S. 120 Bradner, Ed., 121 RFC 3979, March 2005. 123 8. Author's Address 125 Thomas Narten 126 IBM Corporation 127 3039 Cornwallis Ave. 128 PO Box 12195 - BRQA/502 129 Research Triangle Park, NC 27709-2195 131 Phone: 919-254-7798 132 EMail: narten@us.ibm.com 134 Intellectual Property Statement 136 The IETF takes no position regarding the validity or scope of any 137 Intellectual Property Rights or other rights that might be claimed to 138 pertain to the implementation or use of the technology described in 139 this document or the extent to which any license under such rights 140 might or might not be available; nor does it represent that it has 141 made any independent effort to identify any such rights. Information 142 on the procedures with respect to rights in RFC documents can be 143 found in BCP 78 and BCP 79. 145 Copies of IPR disclosures made to the IETF Secretariat and any 146 assurances of licenses to be made available, or the result of an 147 attempt made to obtain a general license or permission for the use of 148 such proprietary rights by implementers or users of this 149 specification can be obtained from the IETF on-line IPR repository at 150 http://www.ietf.org/ipr. 152 The IETF invites any interested party to bring to its attention any 153 copyrights, patents or patent applications, or other proprietary 154 rights that may cover technology that may be required to implement 155 this standard. Please address the information to the IETF at ietf- 156 ipr@ietf.org. 158 Disclaimer of Validity 160 This document and the information contained herein are provided on an 161 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 162 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 163 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 164 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 165 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 166 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 168 Copyright Statement 170 Copyright (C) The Internet Society (2006). 172 This document is subject to the rights, licenses and restrictions 173 contained in BCP 78, and except as set forth therein, the authors 174 retain all their rights. 176 This document and the information contained herein are provided on an 177 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 178 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 179 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 180 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 181 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 182 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.