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