idnits 2.17.1 draft-ietf-ipr-template-09.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 3667, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 373. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 357. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 379), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) 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 (April 2004) is 7316 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) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPR WG 3 Internet-Draft V. See (editor) 4 Document: draft-ietf-ipr-template-09.txt Microsoft 5 Expires: October 28, 2004 April 2004 7 A Template for IETF Patent Disclosures and Licensing Declarations 9 Status of this Memo 11 By submitting this Internet-Draft, I certify that any applicable 12 patent or other IPR claims of which I am aware have been disclosed, 13 and any of which I become aware will be disclosed, in accordance with 14 RFC 3668. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on October 2, 2004 34 Copyright Notice 36 Copyright (C) The Internet Society 2004. All Rights Reserved. 38 Abstract 40 This document describes a proposal for one form of a template for 41 IETF patent disclosures and licensing declarations. The optional use 42 of this template is meant to simplify the process of such disclosures 43 and licensing declarations and to assist disclosers in providing the 44 necessary information to meet the obligations documented in RFC 3668. 46 Table of Contents 48 1. Introduction...................................................2 49 2. The Patent Disclosure and Licensing Declaration Template.......2 50 3. Commentary on Terms Used in the Template.......................6 51 Security Considerations...........................................7 52 Normative References..............................................7 53 Acknowledgments...................................................8 54 Authors' Addresses................................................8 55 Intellectual Property Statement...................................8 56 Disclaimer of Validity............................................9 57 Copyright Statement...............................................9 59 1. Introduction 61 RFC 3668 [i] documents the current IETF policies and obligations with 62 respect to disclosure of patents and patent applications. It also 63 documents the information requested in licensing declarations for 64 IETF specifications. In the interest of making these patent 65 disclosure and licensing declaration processes simpler, this document 66 proposes a patent disclosure and licensing declaration template that 67 may be optionally used as one method for IETF participants and patent 68 holders to comply with patent disclosure requirements and licensing 69 declaration provisions under RFC 3668. This proposal also may be 70 optionally used as a model by the IETF Secretariat for Web-based 71 disclosure and licensing declaration tools; however, the intent of 72 this document is informational and is not meant to suggest that this 73 is the only method that could be used by IETF participants for 74 disclosure of patents or for licensing declarations. For the latest 75 information on how to submit a patent disclosure or licensing 76 declaration, please see http://www.ietf.org/ipr-instructions. 78 2. The Patent Disclosure and Licensing Declaration Template 80 START OF TEMPLATE 82 This document is an IETF Patent Disclosure and Licensing Declaration 83 Template and is submitted to inform the IETF of a) patent information 84 regarding the IETF document or contribution listed in Section IV, and 85 b) a Patent Holder's intention with respect to the licensing of its 86 necessary patent claims. No actual license is implied by submission 87 of this template. Please complete and submit a separate template for 88 each IETF document or contribution to which the disclosed patent 89 information relates. 91 I. Patent Holder/Applicant ("Patent Holder") 93 Legal Name: 95 II. Patent Holder's Contact for License Application 97 Name: 99 Title: 101 Department: 103 Address: 105 Telephone: 107 Fax: 109 Email: 111 III. Contact Information for the IETF Participant Whose Personal 112 Belief Triggered the Disclosure in this Template (Optional) 114 Name: 116 Title: 118 Department: 120 Address: 122 Telephone: 124 Fax: 126 Email: 128 IV. IETF Document or Contribution to Which Patent Disclosure Relates 130 Title: 132 RFC Number or I-D Tag: 134 Other Designations: 136 V. Disclosure of Patent Information (i.e., patents or patent 137 applications required to be disclosed by Section 6 of RFC 3668) 139 A. For granted patents or published pending patent applications, 140 please provide the following information: 142 Patent, Serial, Publication, Registration, or Application/File 143 number(s): 145 Date(s) granted or applied for (YYYY-MM-DD): 147 Country(ies): 149 B. Does your disclosure relate to an unpublished pending patent 150 application? 152 Select one: Yes ______ No ______ 154 C. If an Internet-Draft or RFC includes multiple parts and it is not 155 reasonably apparent which part of such Internet-Draft or RFC is 156 alleged to be covered by the patent information disclosed in Section 157 V(A) or V(B), it is helpful if the discloser identifies here the 158 sections of the Internet-Draft or RFC that are alleged to be so 159 covered. 161 VI. Licensing Declaration 163 The Patent Holder states that its position with respect to licensing 164 any patent claims contained in the patent(s) or patent application(s) 165 disclosed above that would necessarily be infringed by implementation 166 of the technology required by the relevant IETF specification 167 ("Necessary Patent Claims"), for the purpose of implementing such 168 specification, is as follows (select one licensing declaration option 169 only): 171 a) ___ No License Required for Implementers 172 Check here if commitment to forgo a license is limited 173 solely to standards-track RFCs ___ 175 b) ___ Royalty-Free, Reasonable and Non-Discriminatory License to 176 All Implementers 177 Check here if this commitment to license is limited solely 178 to standards-track RFCs ___ 180 c) ___ Reasonable and Non-Discriminatory License to All 181 Implementers with Possible Royalty/Fee 182 Check here if this commitment to license is limited solely 183 to standards-track RFCs ___ 185 d) ___ Licensing Declaration to be Provided Later (implies a 186 willingness to commit to the provisions of a), b), or c) 187 above; otherwise, the next option - "Unwilling to Commit to 188 the Provisions of a), b), or c) Above" - must be selected) 190 e) ___ Unwilling to Commit to the Provisions of a), b), or c) 191 Above 193 NOTE: The individual submitting this template represents and warrants 194 that he or she is authorized by the Patent Holder to agree to the 195 above-selected licensing declaration. 197 VII. Contact Information of Submitter of this Form (if different from 198 IETF Participant in Section III above) 200 Name: 202 Title: 204 Department: 206 Address: 208 Telephone: 210 Fax: 212 Email: 214 VIII. Other Notes: 216 END OF TEMPLATE 218 3. Commentary on Terms Used in the Template 220 Section III requests contact information for the Patent Holder's IETF 221 participant whose personal belief that necessary patent claims are 222 implicated by an IETF document or contribution caused this template 223 to be filed. This is an optional section. However, if Section III is 224 not completed, then Section VII must be completed. Even if Section 225 III is completed, Section VII must still be completed if the 226 submitter of this template is different from the IETF participant 227 identified in Section III. 229 The "Other Designations" field in Section IV may be used to identify 230 an IETF contribution (oral or written) other than an Internet-Draft 231 or RFC to which a disclosure is related. 233 Here is an explanation of the licensing declaration options in 234 Section VI of the template: 236 a) No License Required for Implementers: The Patent Holder does not 237 require parties to acquire any license to its Necessary Patent Claims 238 in order to make, have made, use, import, offer to sell, sell, or 239 distribute technology that implements such IETF specification. 241 b) Royalty-Free, Reasonable and Non-Discriminatory License to All 242 Implementers: The Patent Holder is willing, upon request, to grant a 243 license to its Necessary Patent Claims to all persons on a royalty- 244 free basis (i.e., no royalty or other fee) and under other reasonable 245 and non-discriminatory terms and conditions, to make, have made, use, 246 import, offer to sell, sell, and distribute technology that 247 implements such IETF specification. 249 c) Reasonable and Non-Discriminatory License to All Implementers with 250 Possible Royalty/Fee: The Patent Holder is willing, upon request, to 251 grant a license to its Necessary Patent Claims to all persons under 252 reasonable and non-discriminatory terms and conditions (which may 253 include a royalty/fee), to make, have made, use, import, offer to 254 sell, sell, and distribute technology that implements such IETF 255 specification. 257 d) Licensing Declaration to be Provided Later: The Patent Holder is 258 willing to commit to the provisions of a), b), or c) above, but wants 259 to defer its specific selection of one of these licensing declaration 260 options until a later point in time (or when asked for this 261 information by the IESG). This option may not be selected if the 262 Patent Holder is unwilling to commit to the provisions of a), b), or 263 c) above. In that case, the Patent Holder must select licensing 264 declaration option e) - "Unwilling to Commit to the Provisions of a), 265 b), or c) Above." 266 e) Unwilling to Commit to the Provisions of a), b), or c) Above: The 267 Patent Holder indicates an unwillingness to commit to the provisions 268 of any of options a), b), or c) described above. 270 Options a), b), and c) above also allow the Patent Holder to indicate 271 (with a check) whether its licensing declaration is limited solely to 272 standards-track RFCs. If left unchecked, the Patent Holder's 273 licensing declaration will be deemed to apply to any implementation 274 of the relevant IETF specification, including non-standards-track 275 documents and Internet-Drafts. However, the Patent Holder may list 276 other conditions or restrictions on its commitment to forego a 277 license (option a)) or on its commitment to license (options b) and 278 c)) in Section VIII - "Other Notes." This standards-track qualifier 279 is not relevant to licensing declaration options d) and e), because 280 under d) the Patent Holder has not yet indicated its specific 281 licensing intention and under e) the Patent Holder has indicated a 282 general refusal to commit to the provisions of any of options a), b), 283 or c) above. 285 Section VIII in the template, "Other Notes," may be used for any 286 additional information a discloser or Patent Holder wishes to 287 provide. For example, a Patent Holder may use the "Other Notes" 288 Section to indicate any other conditions or restrictions on the 289 licensing declaration option selected in Section VI (e.g., 1) 290 reciprocity, or 2) that a license will only be made available for 291 implementations of any RFC (standards-track or non-standards-track), 292 but not for implementations of Internet-Drafts or other documents). 294 Security Considerations 296 This document relates to IETF process, not any particular technology. 297 There are security considerations when adopting any particular 298 technology, regardless of whether patent or patent application 299 disclosures or licensing declarations are implicated by such 300 technology. A working group should take those security considerations 301 into account as one part of evaluating the technology, but there are 302 no security considerations per se with these IETF processes. 304 Normative References 306 i Bradner, S., "Intellectual Property Rights in IETF Technology," 307 RFC 3668, February 2004. 309 Acknowledgments 311 The authors acknowledge the thoughtful contributions of Harald 312 Alvestrand and Scott Bradner to this document. 314 Authors' Addresses 316 Valerie See 317 Microsoft Corporation 318 One Microsoft Way, Redmond, WA 98052 USA 319 Email: vsee@microsoft.com 321 Robert Barr 322 Cisco Systems, Inc. 323 170 West Tasman Drive, San Jose, CA 95134 USA 324 Email: rbarr@cisco.com 326 Scott Brim 327 Cisco Systems, Inc. 328 146 Honess Lane, Ithaca, NY 14850 USA 329 Email: sbrim@cisco.com 331 Paul Gleichauf 332 Cisco Systems, Inc. 333 170 West Tasman Drive, San Jose, CA 95134 USA 334 Email: phg@cisco.com 336 Allen Lo 337 Juniper Networks 338 1194 North Mathilda Ave., Sunnyvale, CA 94089 USA 339 Email: alo@juniper.net 341 Intellectual Property Statement 343 The IETF takes no position regarding the validity or scope of any 344 intellectual property or other rights that might be claimed to 345 pertain to the implementation or use of the technology described in 346 this document or the extent to which any license under such rights 347 might or might not be available; neither does it represent that it 348 has made any effort to identify any such rights. Information on the 349 IETF's procedures with respect to rights in IETF Documents can be 350 found in BCP 78 and 79. 352 Copies of IPR disclosures made to the IETF Secretariat and any 353 assurances of licenses to be made available, or the result of an 354 attempt made to obtain a general license or permission for the use of 355 such proprietary rights by implementers or users of this 356 specification can be obtained from the IETF on-line IPR repository at 357 http://www.ietf.org/ipr. 359 The IETF invites any interested party to bring to its attention any 360 copyrights, patents or patent applications, or other proprietary 361 rights which may cover technology that may be required to implement 362 this standard. Please address the information to the IETF at ietf- 363 ipr.org. 365 Disclaimer of Validity 367 This document and the information contained herein are provided on an 368 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 369 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 370 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 371 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 372 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 373 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 375 Copyright Statement 377 Copyright (C) The Internet Society (2004). This document is subject 378 to the rights, licenses and restrictions contained in BCP 78, and 379 except as set forth therein, the authors retain all their rights.