idnits 2.17.1 draft-ietf-ipr-submission-rights-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by 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 : ---------------------------------------------------------------------------- ** 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.) -- The abstract seems to indicate that this document updates RFC2026, but the header doesn't have an 'Updates:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 241 has weird spacing: '...for the purpo...' == Line 594 has weird spacing: '...for the purpo...' -- 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 (March 2003) is 7713 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 information found for draft-iprwg-technology - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'IETF IPR' Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 5 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 Editor 5 March 2003 7 IETF Rights in Submissions 9 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 10 of RFC 2026. 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 Abstract 33 The IETF policies about rights in submissions to the IETF are 34 designed to ensure that IETF contributions can be made available to 35 the IETF and Internet communities while permitting the authors to 36 retain as many rights in the document as possible. This memo details 37 the IETF policies on rights in submissions to the IETF. It also 38 describes the objectives that the policies are designed to meet. This 39 memo updates RFC 2026, and with RFC XXXY, replaces Section 10 of RFC 40 2026. [note to RFC editor: replace XXXY with number of IETF IPR] 42 Copyright (C) The Internet Society. (2003) 44 1. Introduction 45 Under the laws of most countries and current international treaties 46 (for example the "Berne Convention for the Protection of Literary and 47 Artistic Work" [Berne]), authors obtain numerous rights in the works 48 they produce automatically upon producing them. These rights include 49 copyrights, moral rights and other rights. In many cases, if the 50 author produces a work within the scope of his or her employment, 51 most of those rights are usually assigned to the employer, either by 52 operation of law or, in many cases, under contract. (The Berne 53 Convention names some rights as "inalienable", which means that the 54 author retains them in all cases.) 56 In order for works to be used within the IETF process, certain 57 limited rights in all Contributions must be granted to the IETF and 58 Internet Society (ISOC). In addition, Contributors must make 59 representations to IETF and ISOC regarding their ability to grant 60 these rights. These necessary rights and representations have until 61 now been laid out in Section 10 of [RFC 2026]. In the years since 62 [RFC 2026] was published there have been a number of times when the 63 exact intent of Section 10 has been the subject of vigorous debate 64 within the IETF community. The aim of this document is to clarify 65 various ambiguities in Section 10 of [RFC 2026] that led to these 66 debates and to amplify the policy in order to clarify what the IETF 67 is currently doing. 69 Sections 2 and 3 of this document address the rights in submissions 70 to the IETF previously covered by Section 10 of [RFC 2026] and the 71 "Note Well" explanatory text presented at many IETF activities. 72 Section 4 gives definitions used in describing these policies. 73 Sections 5, 6 and 7 then explain the rationale for these provisions, 74 including some of the clarifications that have become understood 75 since the adoption of [RFC 2026]. The rules and procedures set out 76 in this document are not intended to substantially modify or alter 77 the IETF's current policy toward Contributions made to the IETF. 79 A companion document [IETF IPR] will deal with rights in technologies 80 developed or specified as part of the IETF process. This document is 81 not intended to address those issues. 83 The rights addressed in this document fall into the following 84 categories: 86 o rights to make use of contributed material 87 o copyrights in IETF documents 88 o rights to produce derivative works 89 o rights to use trademarks 91 This document is not intended as legal advice. Readers are advised 92 to consult their own legal advisors if they would like a legal 93 interpretation of their rights or the rights of the IETF in any 94 Contributions they make. 96 2. Rights in IETF Submissions 98 2.1. General Policy 100 In all matters of copyright and document procedures, the intent is to 101 benefit the Internet community and the public at large, while 102 respecting the legitimate rights of others. 104 2.2 Confidentiality Obligations 106 No Contribution that is subject to any requirement of confidentiality 107 or any restriction on its dissemination may be considered in any part 108 of the IETF Standards Process, and there must be no assumption of any 109 confidentiality obligation with respect to any such Contribution. 110 Each Contributor agrees that any statement in a Contribution, whether 111 generated automatically or otherwise, that states or implies that the 112 Contribution is confidential or subject to any privilege, can be 113 disregarded for all purposes, and will be of no force or effect. 115 2.3. Granting of Rights and Permissions 117 By submission of a Contribution, each person actually submitting the 118 Contribution, and each named co-contributor, is deemed to agree to 119 the following terms and conditions, and to grant the following 120 rights, on his or her own behalf and on behalf of the organization 121 the contributor represents or is sponsored by (if any) when 122 submitting the Contribution. 124 a. To the extent that the Contribution or any portion thereof is 125 protected by copyright and other rights of authorship, the 126 Contributor, and each named co-contributor, and the organization 127 he or she represents or is sponsored by (if any) grant a 128 perpetual, irrevocable, non-exclusive, royalty-free, world-wide 129 right and license to the ISOC and the IETF under all intellectual 130 property rights in the Contribution: 132 (A) to copy, publish, display and distribute the contribution as 133 part of the IETF standards process, 135 (B) unless explicitly disallowed in the written terms of the 136 Contribution [pursuant to one of the notices contained in 137 Section 3.3 below], to prepare derivative works that are based 138 on or incorporate all or part of the Contribution within the 139 IETF standards process, the license to such derivative works to 140 be of a scope no wider than the license to the original 141 Contribution, and 143 (C) to reproduce any trademarks, service marks or trade names 144 which are included in the Contribution solely in connection 145 with the reproduction, distribution or publication of the 146 Contribution and derivative works thereof as permitted by this 147 paragraph. When reproducing Contributions, the IETF will 148 preserve trademark and service mark identifiers in the format 149 used by the Contributor of the contribution, including (tm) and 150 (r) where appropriate. 152 b. The Contributor grants the IETF and ISOC permission to reference 153 the name(s) and address(es) of the contributor(s) and of the 154 organization(s) s/he represents or is sponsored by (if any). 156 c. Every copy of an IETF document made pursuant to the licenses 157 granted under paragraph (a)(A) above, and all derivative works 158 made pursuant to the licenses granted under paragraph (a)(B) 159 above, must include, in unaltered form, the notices included in 160 such Contribution pursuant to Section 3 below. 162 2.4 Representations and Warranties. With respect to each Contribution, 163 each Contributor represents that to the best of his or her knowledge 164 and ability: 166 a. The contribution properly acknowledges all major Contributors. A 167 major Contributor is any person who has materially or 168 substantially contributed to the Contribution. 170 b. No information in the Contribution is confidential and the IETF, 171 ISOC, and its affiliated organizations may freely disclose any 172 information in the Contribution. 174 c. There are no limits to the Contributor's ability to make the 175 grants, acknowledgments and agreements herein that are reasonably 176 and personally known to the Contributor. 178 d. The Contributor has not intentionally included in the 179 Contribution any material which is defamatory or untrue or which 180 is illegal under the laws of the jurisdiction in which the 181 Contributor has his or her principal place of business or 182 residence. 184 e. All trademarks, trade names, service marks and other proprietary 185 names used in the Contribution and personally and reasonably known 186 to the Contributor are clearly designated as such where 187 reasonable. 189 2.5 The Contributor, and each named co-contributor, acknowledges that 190 the IETF has no duty to publish or otherwise use or disseminate any 191 Contribution. The IETF reserves the right to withdraw or cease using 192 any Contribution that does not comply with the requirements of 193 Sections 2.3 and 2.4 above. 195 2.6 Contributors, and each named co-contributor, who claim trademark 196 rights to terms in their contributions are requested to specifically 197 state what conditions apply to implementers of the technology 198 relative to the use of any claimed trademarks. Such statements 199 should be submitted in the same way as is done for other intellectual 200 property claims. (See [IETF IPR] sec 6.) 202 3. Copyright notice required in IETF Documents 204 The IETF requires that a copyright notice and disclaimer be 205 reproduced verbatim in all IETF Documents. This requirement protects 206 IETF and its participants from liabilities connected with these 207 documents. The copyright notice also alerts readers that the 208 document is an IETF document, and that ISOC claims copyright rights 209 in certain aspects of the document, such as its layout, the RFC 210 numbering convention and the prefatory language of the document. 211 This legend is not intended to imply that ISOC has obtained ownership 212 of the contribution itself, which is retained by the author(s) or 213 remains in the public domain, as applicable. 215 Additional copyright notices are not permitted in IETF documents 216 except in the case where the document is the product of a joint 217 development effort between the IETF and another standards development 218 organization. Such exceptions must be approved on an individual 219 basis by the IAB. 221 3.1 Copyright notice and disclaimer 223 One of the following two copyright notice and disclaimers shall be 224 included at the end of all IETF documents. 226 3.1.1 Notice for documents where the right to produce derivative works 227 has not been withheld. (See sec 5.3 for a discussion on derivative 228 works.) 230 "Copyright (C) The Internet Society (year). Except as set forth 231 below, authors retain all their rights. 233 This document and translations of it may be copied and furnished to 234 others, and derivative works that comment on or otherwise explain it 235 or assist in its implementation may be prepared, copied, published 236 and distributed, in whole or in part, without restriction of any 237 kind, provided that the above copyright notice and this paragraph are 238 included on all such copies and derivative works. However, this 239 document itself may not be modified in any way, such as by removing 240 the copyright notice or references to the Internet Society or other 241 Internet organizations, except as needed for the purpose of 242 developing Internet standards in which case the procedures for rights 243 in submissions defined in the IETF Standards Process must be 244 followed, or as required to translate it into languages other than 245 English. 247 The limited permissions granted above are perpetual and will not be 248 revoked by the Internet Society or its successors or assigns. 250 This document and the information contained herein is provided on an 251 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE 252 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 253 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 254 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 255 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 256 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 258 3.1.2 Notice for documents where the right to produce derivative works 259 has been withheld. (See sec 5.3 for a discussion on derivative 260 works.) 262 "Copyright (C) The Internet Society (year). Except as set forth 263 below, authors retain all their rights. 265 This document and translations of it may be copied and furnished to 266 others provided that the above copyright notice and this paragraph 267 are included on all such copies. However, this document itself may 268 not be modified in any way, such as by removing the copyright notice 269 or references to the Internet Society or other Internet 270 organizations, except as required to translate it into languages 271 other than English. 273 The limited permissions granted above are perpetual and will not be 274 revoked by the Internet Society or its successors or assigns. 276 This document and the information contained herein is provided on an 277 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE 278 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 279 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 280 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 281 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 282 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 284 3.2 Notices re. Derivative Works and publication rights. 286 In addition to the foregoing, each IETF Internet-Draft must contain 287 one of the following three notices regarding derivative works and 288 publication rights on it's first page: (See sec 5.3 for a discussion 289 on derivative works.) 291 a. This document is an Internet-Draft and is subject to all 292 provisions of section 2 of RFC XXXX. By submitting this Internet- 293 Draft, I certify that any applicable patent or other IPR claims of 294 which I am aware have been disclosed in accordance with RFC XXXY. 296 b. This document is an Internet-Draft and is subject to all 297 provisions of Section 2 of RFC XXXX except that the right to 298 prepare revised versions of this specification is not granted. By 299 submitting this Internet-Draft, I certify that any applicable 300 patent or other IPR claims of which I am aware have been disclosed 301 in accordance with RFC XXXY. 303 c. This document is an Internet-Draft and is subject to all 304 provisions of Section 2 RFC XXXX, but the author does not provide 305 the IETF with any rights other than to publish as an Internet- 306 Draft. By submitting this Internet-Draft, I certify that any 307 applicable patent or other IPR claims of which I am aware have 308 been disclosed in accordance with RFC XXXY. 310 [note to the RFC Editor - XXXX above to be replaced with the number 311 of this document and XXXY to be replaced the number of [IETF-IPR]] 313 The first statement is required for all documents that are submitted 314 for Standards Track publication. The primary motivation is that the 315 IETF retains change control, thus permitting augmenting the original 316 document to clarify or enhance the protocol defined by the document. 318 The second statement is used when "republishing" standards produced 319 by other (non-IETF) standards organizations, industry consortia or 320 individual companies. These are typically published as Informational 321 RFCs, and do not require that change control be ceded to the IETF. 322 Basically, these documents convey information for the Internet 323 community. 325 The third statement is used when the document's purpose is to provide 326 background information to educate and to facilitate discussions 327 within IETF groups and the document is not intended to be published 328 as an RFC. 330 4. Definitions 332 "Contribution": in the context of this memo, a contribution to the IETF 333 is any submission intended by the contributor for publication as an 334 Internet-Draft or RFC and any statements made within the context of 335 an IETF process. Such statements include oral statements in IETF 336 meetings, as well as written and electronic communications made at 337 any time or place, which are addressed to 338 o the IETF plenary session, 339 o any IETF working group or portion thereof, 340 o the IESG, or any member thereof on behalf of the IESG, 341 o the IAB or any member thereof on behalf of the IAB, 342 o any IETF mailing list, including the IETF list itself, any working 343 group or design team list, or any other list functioning under 344 IETF auspices, 345 o the RFC Editor or the Internet-Drafts function 347 Statements made outside of an IETF meeting, mailing list or other 348 function, that are clearly not intended to be input to an IETF 349 activity, group or function, are not contributions in the context of 350 this memo. 352 "IETF Standards Process": the activities undertaken by the IETF in any 353 of the settings described in 4 above. 355 "Contributors": individuals submitting Contributions 357 "IETF Documents": RFCs and Internet-Drafts. 359 "RFC": the basic publication series for the IETF. RFCs are published by 360 the RFC Editor and once published are never modified. (See [RFC 361 2026] sec 2.1) 363 "Internet-Draft": temporary documents used in the IETF process. 364 Internet-Drafts are published by the IETF Secretariat and have a 365 nominal maximum lifetime in the Secretariat's public directory of 6 366 months, after which they are removed. Since Internet-Drafts are 367 archived many places on the Internet there is no effective limit on 368 their actual lifetime. Internet-Drafts that are under active 369 consideration by the IESG are not removed from the Secretariat's 370 public directory until that consideration is complete. In addition, 371 the author of an Internet-Draft can request that the lifetime in the 372 Secretariat's public directory be extended before the expiration. 373 (See [RFC 2026] sections 2.2 and 8) 375 "IETF": In the context of this document, the IETF includes all 376 individuals who participate in meetings, working groups, mailing 377 lists, functions and other activities which are organized or 378 initiated by ISOC, the IESG or the IAB under the general designation 379 of the Internet Engineering Task Force or IETF, but solely to the 380 extent of such participation. 382 "Reasonably and personally known": should be read to refer to something 383 the individual knows personally or, because of the job the individual 384 holds, would reasonably be expected to know. 386 5. Exposition of why these procedures are the way they are 388 5.1 Rights Granted in Contributions 390 The IETF/ISOC must obtain the right to publish a Contribution as an 391 RFC or an Internet-Draft from the Contributors. 393 A primary objective of this policy is to obtain from the document 394 authors only the non-exclusive rights that are needed to develop and 395 publish IETF documents and to use the Contributions in the IETF 396 standards process while leaving all other rights with the authors. 398 The non-exclusive rights that the IETF needs are: 400 a. the right to publish the document 401 b. the right to let the document be freely reproduced in the formats 402 that the IETF publishes it in 403 c. the right to let third parties translate it into languages other 404 than English 405 d. except where explicitly excluded (see sec 3.2), the right to make 406 derivative works within the IETF process. 408 The authors retain all other rights, but cannot withdraw the above 409 rights from the IETF/ISOC. 411 5.2 Rights to use Contributed Material 413 Because, under the laws of most countries and applicable 414 international treaties, copyright rights come into existence whenever 415 a work of authorship is created (but see Section 6 below regarding 416 public domain documents), and IETF cannot make use of Contributions 417 if it does not have sufficient rights with respect to these copyright 418 rights, it is important that the IETF receive assurances from all 419 Contributors that they have the authority to grant the IETF the 420 rights that they claim to grant. Without this assurance, IETF and 421 its participants would run a greater risk of liability to the owners 422 of these rights. 424 To this end, IETF asks Contributors to give the assurances in Section 425 2.4 above. These assurances are requested, however, only to the 426 extent of the Contributor's reasonable and personal knowledge. (See 427 Section 4.) 429 5.3 Right to produce derivative works 431 The IETF needs to be able to evolve its documents in response to 432 experience gained in the deployment of the technologies described in 433 the documents, to incorporate developments in research and to react 434 to changing conditions on the Internet and other IP networks. In 435 order to do this the IETF must be able to produce derivatives of its 436 documents; thus the IETF must obtain the right from Contributors to 437 produce derivative works. Note though that the IETF only requires 438 this right for the production of derivative works within the IETF 439 standards process. The IETF does not need, nor does it obtain, the 440 right to let derivative works be created outside of the IETF process. 442 The right to produce derivative works is required for all IETF 443 standards track documents and for most non-standards track documents. 444 There are two exceptions to this requirement: documents describing 445 proprietary technologies and documents that are republications of the 446 work of other standards organizations. 448 The right to produce derivative works must be granted (i.e., an 449 Internet-Draft must be published with boilerplate "a" from sec 3.2) 450 before an IETF working group can accept a document as a working group 451 document or otherwise work on it. Note: a working group can discuss 452 any Internet-Draft with the aim to decide if it should become a 453 working group document, whether or not the right to produce 454 derivative works has been yet granted. For independent submissions, 455 the right to produce derivative works must be granted for all 456 standards track documents before the IESG will issue an IETF Last- 457 Call and, for most non-standards track documents, before the IESG 458 will consider the Internet-Draft for publication. 460 The IETF has historically encouraged organizations to publish details 461 of their technologies, even where the technologies are proprietary 462 ones, because understanding how existing technology is being used 463 helps when developing new technology. But organizations that publish 464 information about proprietary technologies are frequently not willing 465 to have the IETF produce revisions of the technologies and then claim 466 that the IETF version is the "new version" of the organization's 467 technology. Organizations which feel this way can specify that the 468 document can be published following the other provisions of this 469 section but withhold the right to produce derivative works. 471 In addition, IETF documents frequently make normative references to 472 standards or recommendations developed by other standards 473 organizations. Since the publications of some standards 474 organizations are not public documents it can be quite helpful to the 475 IETF to republish, with the permission of the other standards 476 organization, some of these documents as IETF documents so that the 477 IETF community can have open access to them to better understand what 478 they are referring to. In these cases the IETF documents can be 479 published without the right for the IETF to produce derivative works. 481 In both of the above cases in which the production of derivative 482 works is excluded, the Contributor must include a special legend in 483 the Contribution, as specified in section 3.2, in order to notify 484 IETF participants about this restriction. 486 5.4 Rights to use trademarks 488 Contributors may wish to seek trademark or service mark protection on 489 any terms that are coined or used in their Contributions. IETF makes 490 no judgment about the validity of any such trademark rights. 491 However, the IETF requires each Contributor, under the licenses 492 described in Section 2.3.a above, to grant IETF a perpetual license 493 to use any such trademarks or service marks solely in exercising its 494 rights to reproduce, publish and modify the Contribution. This 495 license does not authorize any IETF participant to use any trademark 496 or service mark in connection with any product or service offering, 497 but only in the context of IETF documents and discussions. 499 5.5 Who does this apply to? 501 Rights and licenses granted to the IETF are granted to all 502 individuals noted in section 4, irrespective of their employment or 503 institutional affiliation. However, these licenses do not extend 504 broadly to the employers, sponsors or institutions of such 505 individuals, nor do they authorize the individuals to exercise any 506 rights outside the specific context of the IETF standards process. 508 6. Contributions Not Subject to Copyright 510 Certain documents, including those produced by the U.S. government 511 and those which are in the public domain, may not be protected by the 512 same copyright and other legal rights as other documents. 513 Nevertheless, we ask each Contributor to grant to the IETF the same 514 rights as he or she would grant, and to make the same 515 representations, as though the Contribution were a proprietary 516 document. We ask for these grants and representations only to the 517 extent that the Contribution may be protected. We believe they are 518 necessary to protect the IETF, the standards process and all IETF 519 participants, and also because the IETF does not have the resources 520 or wherewithal to make any independent investigation as to the actual 521 proprietary status of any document submitted to it. 523 7. Inclusion of legal notice 525 Section three above defines a copyright notice to be included on IETF 526 documents and in derivative works. The full copyright notice does 527 not need to be included in some specific types of derivative works. 529 a/ in MIBs, PIBs and similar material commonly extracted from IETF 530 documents, the following copyright notice should be included in 531 the body of the material that will be extracted "Copyright (C) 532 The Internet Society. This version of this MIB module is 533 part of RFC xxxx; see the RFC itself for the full legal notices." 534 (Substitute "PIB" for "MIB" in the statement for PIBs.) In the 535 case of MIBs and PIBs this statement should be placed in the 536 DESCRIPTION clause of the MODULE-IDENTITY macro. 538 b/ short excerpts of IETF documents presented in electronic help 539 systems, for example, the DESCRIPTION clauses for MIB variables, 540 do not need to include a copyright notice. 542 8 Security Considerations 544 This memo relates to IETF process, not any particular technology. 545 There are security considerations when adopting any technology, 546 whether IPR-protected or not. A working group should take those 547 security considerations into account as one part of evaluating the 548 technology, just as IPR is one part, but they are not issues of 549 security with IPR procedures. 551 9. References 553 9.1 Normative references 555 [RFC 2026] Bradner, S.[ed], "The Internet Standards Process -- 556 Revision 3", RFC 2026, October 1996 557 [IETF IPR] Bradner, S.[ed] "Intellectual Property Rights in IETF 558 Technology", work in progress: draft-iprwg-technology-00.txt 560 9.2 Informative references 561 [Berne] "Berne Convention for the Protection of Literary and Artistic 562 Work", http://www.wipo.int/treaties/ip/berne/index.html 564 10. Acknowledgements 566 The editor would like to acknowledge the help of the IETF ipr Working 567 Group and, in particular the help of Jorge Contreras of Hale and Dorr 568 for his careful legal reviews of this and other IETF IPR-related and 569 process documents. 571 11. Editor's Address 573 Scott Bradner 574 Harvard University 575 29 Oxford St. 576 Cambridge MA, 02138 578 sob@harvard.edu 579 +1 617 495 3864 581 12. Full copyright statement 583 Copyright (C) The Internet Society (2003). Except as set forth 584 below, authors retain all their rights. 586 This document and translations of it may be copied and furnished to 587 others, and derivative works that comment on or otherwise explain it 588 or assist in its implementation may be prepared, copied, published 589 and distributed, in whole or in part, without restriction of any 590 kind, provided that the above copyright notice and this paragraph are 591 included on all such copies and derivative works. However, this 592 document itself may not be modified in any way, such as by removing 593 the copyright notice or references to the Internet Society or other 594 Internet organizations, except as needed for the purpose of 595 developing Internet standards in which case the procedures for rights 596 in submissions defined in the IETF Standards process must be 597 followed, or as required to translate it into languages other than 598 English. 600 The limited permissions granted above are perpetual and will not be 601 revoked by the Internet Society or its successors or assigns. 603 This document and the information contained herein is provided on an 604 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/S HE 605 REPRESENTS (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 606 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 607 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 608 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 609 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 611 12. change log 613 note to RFC Editor - remove this section before publication 615 ver 00 to ver 01 616 misc grammar changes throughout text 617 sec 2.2 - add note about automatic disclaimers 618 sec 2.3a - add "or is sponsored by" remove "unlimited" 619 sec 2.3 B - reword to 'of a scope no wider than the license" 620 sec 2.4a - add deff of major contributor 621 sec 2.6 - 2nd paragraph from sec 5.4 moved here 622 sec 3 - truncate heading 623 sec 3.1 5th pp - add OR IS SPONSORED BY 624 sec 3.1.2 - new section with copyright notice for use where 625 derivative works right are withheld 626 sec 3.2 - added usage guidelines for boilerplates 627 sec 4.1 - add "intended by the contributor" 628 sec 4.6 - add "actual" before lifetime 629 sec 4.8 - reword 630 sec 5.3 - insert "standards" in front of "process" last pp - add 631 "with permission" phrase after "republish" 632 sec 5.4 - change "we require" to "the IETF requires" 633 sec 7/a - add PIBs 634 sec 8 - redo security considerations 635 sec 9.1 - remove IPR ID as normative reference 636 sec 9.2 - add IPR ID as informative reference 637 sec 12 - add changes section 639 ver 01 to 02 640 abstract - add note about updating 2026 641 sec 3.2 - add patent pledge 643 ver 02 to 03 644 misc copy edits throughout document 645 sec 4 - "personally and reasonably known" - remove detail