idnits 2.17.1 draft-ietf-ipr-3978-incoming-07.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 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 606. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 625. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 625. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 625. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The abstract seems to indicate that this document obsoletes RFC3978, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (4 February 2008) is 5916 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '-outbound' is mentioned on line 439, but not defined ** Obsolete normative reference: RFC 2028 (Obsoleted by RFC 9281) ** Obsolete normative reference: RFC 3979 (Obsoleted by RFC 8179) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) -- Obsolete informational reference (is this intentional?): RFC 3978 (Obsoleted by RFC 5378) -- Obsolete informational reference (is this intentional?): RFC 4748 (Obsoleted by RFC 5378) Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 10 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 Intended status: BCP Jorge Contreras 5 WilmerHale 6 Editors 7 4 February 2008 9 Rights Contributors provide to the IETF Trust 11 13 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on July 4, 2008. 37 Copyright (C) The IETF Trust (2008). 39 Abstract 40 The IETF policies about rights in Contributions to the IETF are 41 designed to ensure that such Contributions can be made available to 42 the IETF and Internet communities while permitting the authors to 43 retain as many rights as possible. This memo details the IETF 44 policies on rights in Contributions to the IETF. It also describes 45 the objectives that the policies are designed to meet. This memo 46 obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC xxx (rfc 47 editor - replace with the RFC # of -outgoing), replaces Section 10 of 48 RFC 2026. 50 Table of Contents 51 1. Definitions 52 2. Introduction 53 2.1 No Retroactive Effect 54 3. Exposition of why these procedures are the way they are 55 3.1. Rights Granted in Contributions 56 3.2. Rights to use Contributions 57 3.3. Right to Produce Derivative Works 58 3.4. Rights to use Trademarks 59 3.5. Contributions Not Subject to Copyright 60 3.6. Copyright in RFCs 61 4. RFC Editor Documents 62 5. Rights in Contributions 63 5.1. General Policy 64 5.2. Confidentiality Obligations 65 5.3. Rights Granted by Contributors to the IETF Trust 66 5.4. Sublicenses by IETF Trust 67 5.5. No Patent License 68 5.6. Representations and Warranties 69 5.7. No Duty to Publish 70 5.8. Trademarks 71 5.9. Copyright in RFCs 72 6. Legends, Notices and Other Standardized Text in IETF Documents 73 7. Security Considerations 74 8. References 75 8.1. Normative References 76 8.2. Informative References 77 9. Acknowledgements 78 10. Editors' Addresses 79 Full Copyright Statement 81 1. Definitions 82 The following definitions are for terms used in the context of this 83 document. Other terms, including "IESG," "ISOC," "IAB," and "RFC 84 Editor," are defined in [RFC2028]. 86 a. "Contribution": any submission to the IETF intended by the 87 Contributor for publication as all or part of an Internet-Draft or 88 RFC (except for RFC Editor Contributions described in Section 4 89 below) and any statement made within the context of an IETF 90 activity. Such statements include oral statements in IETF 91 sessions, as well as written and electronic communications made at 92 any time or place, which are addressed to: 93 o the IETF plenary session, 94 o any IETF working group or portion thereof, 95 o any Birds of a Feather (BOF) session, 96 o the IESG, or any member thereof on behalf of the IESG, 97 o the IAB or any member thereof on behalf of the IAB, 98 o any IETF mailing list, including the IETF list itself, any 99 working group or design team list, or any other list 100 functioning under IETF auspices, 101 o the RFC Editor or the Internet-Drafts function (except for RFC 102 Editor Contributions described in Section 4 below). 104 Statements made outside of an IETF session, mailing list or other 105 function, that are clearly not intended to be input to an IETF 106 activity, group or function, are not IETF Contributions in the 107 context of this document. 108 b. "Contributor": an individual submitting a Contribution. 109 c. "Indirect Contributor": any person who has materially or 110 substantially contributed to a Contribution without being 111 personally involved in its submission to the IETF. 112 d. "Copyright" means the legal right granted to an author in a 113 document or other work of authorship under applicable law. A 114 "copyright" is not equivalent to a "right to copy". Rather a 115 copyright encompasses all of the exclusive rights that an author 116 has in a work, such as the rights to copy, publish, distribute and 117 create derivative works of the work. An author often cedes these 118 rights to his or her employer or other parties as a condition of 119 employment or compensation. 120 e. "IETF": In the context of this document, the IETF includes all 121 individuals who participate in meetings, working groups, mailing 122 lists, functions and other activities which are organized or 123 initiated by ISOC, the IESG or the IAB under the general 124 designation of the Internet Engineering Task Force or IETF, but 125 solely to the extent of such participation. 126 f. "IETF Documents": RFCs and Internet-Drafts. 127 g. "IETF Standards Process": the activities undertaken by the IETF in 128 any of the settings described in 1(a) above. 129 h. "IETF Trust": A trust established under the laws of the 130 Commonwealth of Virginia, USA, in order to hold and administer 131 intellectual property rights for the benefit of the IETF. 132 i. "Internet-Draft": temporary documents used in the IETF Standards 133 Process. Internet-Drafts are posted on the IETF web site by the 134 IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet- 135 Drafts have a nominal maximum lifetime of six months in the IETF 136 Secretariat's public directory. 137 j. "Legend Instructions" means the standardized text that is 138 maintained by the IETF Trust and is included in IETF Documents and 139 the instructions and requirements for including that standardized 140 text in IETF Documents, each as posted from time to time at 141 http://www.ietf.org/legends. 142 k. "RFC": the basic publication series for the IETF. RFCs are 143 published by the RFC Editor. Although RFCs may be superseded in 144 whole or in part by subsequent RFCs, the text of an RFC is not 145 altered once published in RFC form. (See [RFC2026] Section 2.1) 147 l. "Reasonably and personally known": means something an individual 148 knows personally or, because of the job the individual holds, 149 would reasonably be expected to know. This wording is used to 150 indicate that an organization cannot purposely keep an individual 151 in the dark about certain information just to avoid the disclosure 152 requirement. 153 m. "RFC Editor Documents": means Internet-Drafts that are submitted 154 to the RFC Editor independently of the IETF Standards Process. 155 (See Section 4.) 157 2. Introduction 158 In all matters of copyright and document procedures, the intent is to 159 benefit the Internet community and the public at large, while 160 respecting the legitimate rights of others. 162 Under the laws of most countries and current international treaties 163 (for example the "Berne Convention for the Protection of Literary and 164 Artistic Work" [Berne Convention]), authors obtain numerous rights in 165 the works they produce automatically upon producing them. These 166 rights include copyrights, moral rights and other rights. In many 167 cases, if the author produces a work within the scope of his or her 168 employment, most of those rights are usually assigned to the 169 employer, either by operation of law or, in many cases, under 170 contract. (The Berne Convention names some rights as "inalienable", 171 which means that the author retains them in all cases.) 173 In order for Contributions to be used within the IETF Standards 174 Process, including when they are published as Internet-Drafts or 175 RFCs, certain limited rights must be granted to the IETF Trust, which 176 then grants the necessary rights to the IETF. In addition, 177 Contributors must make representations to the IETF Trust and the IETF 178 regarding their ability to grant these rights. 180 Section 1 provides definitions used in these policies. Sections 3 181 and 4 of this document explain the rationale for these provisions. 182 Sections 1, 2, 5 and 6 of this document are normative, the other 183 sections are informative. A companion document RFC 3979 [RFC3979] 184 deals with rights, including possible patent rights, in technologies 185 developed or specified as part of the IETF Standards Process. This 186 document is not intended to address those issues. This memo 187 obsoletes RFC 3978 [RFC3978] and 4748 [RFC4748] and, with RFC 3979 188 [RFC3979] and [-outgoing], replaces Section 10 of RFC 2026 [RFC2026]. 190 This document is not intended as legal advice. Readers are advised to 191 consult their own legal advisors if they would like a legal 192 interpretation of their rights or the rights of the IETF Trust 193 [RFC4371] in any Contributions they make. 195 2.1 No Retroactive Effect 196 This memo does not retroactively obtain additional rights from 197 Contributions that predate the date that the IETF Trust announces the 198 adoption of these procedures. 200 3. Exposition of Why These Procedures Are the Way They Are 202 3.1. Rights Granted in Contributions 203 The IETF Trust and IETF must obtain the right to publish an IETF 204 Contribution as an RFC or an Internet-Draft from the Contributors. 206 A primary objective of this policy is to obtain from the document 207 authors only the non-exclusive rights that are needed to develop and 208 publish IETF Documents and to use IETF Contributions in the IETF 209 Standards Process and potentially elsewhere. 211 The authors retain all other rights, but cannot withdraw the above 212 rights from the IETF Trust and IETF. 214 It is important to note that under this document Contributors are 215 required to grant certain rights to the IETF Trust, (See Section 216 5.3.) which holds all IETF-related intellectual property on behalf of 217 the IETF community. The IETF Trust will, in turn, grant a sublicense 218 of these rights to all IETF participants for use in the IETF 219 Standards Process. (See Section 5.4.) This sublicense is necessary 220 for the standards development work of the IETF to continue. In 221 addition, the IETF Trust may grant certain other sublicenses of the 222 rights that it is granted under this document. In granting such 223 other sublicenses, the IETF Trust will be guided and bound by 224 documents such as [-outgoing]. 226 3.2. Rights to use Contributions 227 It is important that the IETF receive assurances from all 228 Contributors that they have the authority to grant the IETF the 229 rights that they claim to grant because, under the laws of most 230 countries and applicable international treaties, copyright rights 231 come into existence when a work of authorship is created (but see 232 Section 3.5 below regarding public domain documents), and the IETF 233 cannot make use of IETF Contributions if it does not have sufficient 234 rights with respect to these copyright rights. IETF and its 235 participants would run a greater risk of liability to the owners of 236 these rights without this assurance. To this end, IETF asks 237 Contributors to give the assurances in Section 5.6 below. These 238 assurances are requested, however, only to the extent of the 239 Contributor's reasonable and personal knowledge. (See Section 1(k)) 241 3.3. Right to Produce Derivative Works 242 The IETF needs to be able to evolve IETF Documents in response to 243 experience gained in the deployment of the technologies described in 244 such IETF Documents, to incorporate developments in research and to 245 react to changing conditions on the Internet and other IP networks. 246 The IETF may also decide to permit others to develop derivative works 247 based on Contributions. In order to do this, the IETF must be able 248 to produce derivatives of its documents; thus the IETF must obtain 249 the right from Contributors to produce derivative works. Note that 250 the right to produce translations is required before any Contribution 251 can be published as an RFC to ensure the widest possible distribution 252 of the material in RFCs. The right to produce derivative works, in 253 addition to translations, is required for all IETF standards track 254 documents and for most IETF non-standards track documents. There are 255 two exceptions to this requirement: documents describing proprietary 256 technologies and documents that are republications of the work of 257 other standards organizations. 259 The right to produce derivative works must be granted in order for an 260 IETF working group to accept a Contribution as a working group 261 document or otherwise work on it. For non-working group Contributions 262 where the Contributor requests publication as a standards track RFC, 263 the right to produce derivative works must be granted before the IESG 264 will issue an IETF Last-Call and, for most non-standards track non- 265 working group Contributions, before the IESG will consider the 266 Internet-Draft for publication. Occasionally a Contributor may not 267 want to grant publication rights or the right to produce derivative 268 works before finding out if a Contribution has been accepted for 269 development in the IETF Standards Process. In these cases the 270 Contributor may include a limitation on the right to make derivative 271 works in the form specified in the Legend Instructions. A working 272 group can discuss the Contribution with the aim to decide if it 273 should become a working group document, even though the right to 274 produce derivative works or to publish the Contribution as an RFC has 275 not yet been granted. However, if the Contribution is accepted for 276 development, the Contributor must resubmit the Contribution without 277 the limitation notices before a working group can formally adopt the 278 Contribution as a working group document. The IETF Trust may 279 establish different policies for granting sublicenses with respect to 280 different types of Contributions and content within Contributions 281 (such as executable code versus descriptive text or references to 282 third party materials). The IETF Trust's policies concerning the 283 granting of sublicenses to make derivative works will be guided by 284 RFC [-outbound]. 286 The IETF has historically encouraged organizations to publish details 287 of their technologies, even when the technologies are proprietary, 288 because understanding how existing technology is being used helps 289 when developing new technology. But organizations that publish 290 information about proprietary technologies are frequently not willing 291 to have the IETF produce revisions of the technologies and then 292 possibly claim that the IETF version is the "new version" of the 293 organization's technology. Organizations that feel this way can 294 specify that a Contribution be published with the other rights 295 granted under this document but may withhold the right to produce 296 derivative works other than translations. 298 In addition, IETF Documents frequently make normative references to 299 standards or recommendations developed by other standards 300 organizations. Since the publications of some standards organizations 301 are not public documents, it can be quite helpful to the IETF to 302 republish, with the permission of the other standards organization, 303 some of these documents as RFCs so that the IETF community can have 304 open access to them to better understand what they are referring to. 305 In these cases the RFCs can be published without the right for the 306 IETF to produce derivative works. In both of the above cases in 307 which the production of derivative works is excluded, the Contributor 308 must include a special legend in the Contribution, as specified in 309 the Legend Instructions, in order to notify IETF participants about 310 this restriction. 312 3.4. Rights to Use Trademarks 313 Contributors may wish to seek trademark or service mark protection on 314 any terms that are coined or used in their Contributions. IETF makes 315 no judgment about the validity of any such trademark rights. 316 However, the IETF requires each Contributor, under the licenses 317 described in Section 5.3 below, to grant IETF Trust a perpetual 318 license to use any such trademarks or service marks solely in 319 exercising rights to reproduce, publish, discuss and modify the IETF 320 Contribution. This license does not authorize IETF or others to use 321 any trademark or service mark in connection with any product or 322 service offering. 324 3.5. Contributions Not Subject to Copyright 325 Certain documents, including those produced by the U.S. government 326 and those which are in the public domain, may not be protected by the 327 same copyright and other legal rights as other documents. 328 Nevertheless, we ask each Contributor to grant to the IETF the same 329 rights as he or she would grant, and to make the same 330 representations, as though the IETF Contribution were protected by 331 the same legal rights as other documents, and as though the 332 Contributor could be able to grant these rights. We ask for these 333 grants and representations only to the extent that the Contribution 334 may be protected. We believe they are necessary to protect the ISOC, 335 the IETF Trust, the IETF, the IETF Standards Process and all IETF 336 participants, and also because the IETF does not have the resources 337 or wherewithal to make any independent investigation as to the actual 338 proprietary status of any document submitted to it. 340 3.6. Copyright in RFCs. 341 As noted above, Contributors to the IETF (or their employers) retain 342 ownership of the copyright in their Contributions. This includes 343 Internet-Drafts and all other Contributions made within the IETF 344 Standards Process (e.g., via e-mail, oral comment and otherwise). 345 However, it is important that the IETF (through the IETF Trust) own 346 the copyright in documents that are published as RFCs (other than 347 Informational RFCs and RFCs that are submitted as RFC Editor 348 Contributions). Ownership of the copyright in an RFC does not 349 diminish the Contributors' rights in their underlying contributions, 350 but it does prevent anyone other than the IETF Trust (and its 351 licensees) from republishing or modifying an RFC in RFC format. In 352 this respect, Contributors are treated the same as anybody else: 353 though they may extract and republish their own Contributions without 354 limitation, they may not do so in the IETF's RFC format. And while 355 this principle (which is included in Section 5.9 below) may appear to 356 be new to IETF, it actually reflects historical practice and has been 357 observed for many years through the inclusion of an ISOC or IETF 358 Trust copyright notice on all RFC documents since the publication of 359 RFC 2026. 361 4. RFC Editor Documents 362 This document only relates to Contributions made as part of the IETF 363 Standards Process. Other documents that are referred to as Internet- 364 Drafts and RFCs may be submitted to and published by the RFC Editor 365 independently of the IETF Standards Process. Such "RFC Editor 366 Documents" are not covered by this document. RFC Editor 367 Contributions must be marked appropriately as described in the Legend 368 Instructions. See the RFC Editor web page for information about the 369 policies concerning rights in RFC Editor Documents. 371 5. Rights in Contributions 373 5.1. General Policy 374 By submission of a Contribution, each person actually submitting the 375 Contribution, and each named co-Contributor, is deemed to have read 376 and understood the rules and requirements set forth in this document. 377 Each Contributor is deemed, by the act of submitting a Contribution, 378 to enter into a legally-binding agreement to comply with the terms 379 and conditions set forth in this document. 381 The Contributor is further deemed to have agreed that he/she has 382 obtained the necessary permissions to enter into such an agreement 383 from any party that the Contributor reasonably and personally knows 384 may have rights in the Contribution, including, but not limited to, 385 the Contributor's sponsor or employer. 387 No further acknowledgement, signature or other action is required to 388 bind a Contributor to these terms and conditions. The operation of 389 the IETF and the work conducted by its many participants is dependent 390 on such agreement by each Contributor, and each IETF participant 391 expressly relies on the agreement of each Contributor to the terms 392 and conditions set forth in this document. 394 5.2. Confidentiality Obligations 395 No information or document that is subject to any requirement of 396 confidentiality or any restriction on its dissemination may be 397 submitted as a Contribution or otherwise considered in any part of 398 the IETF Standards Process, and there must be no assumption of any 399 confidentiality obligation with respect to any Contribution. Each 400 Contributor agrees that any statement in a Contribution, whether 401 generated automatically or otherwise, that states or implies that the 402 Contribution is confidential or subject to any privilege, can be 403 disregarded for all purposes, and will be of no force or effect. 405 5.3. Rights Granted by Contributors to the IETF Trust 406 To the extent that a Contribution or any portion thereof is protected 407 by copyright or other rights of authorship, the Contributor, and each 408 named co-Contributor grant a perpetual, irrevocable, non-exclusive, 409 royalty-free, world-wide, sublicensable right and license to the IETF 410 Trust under all such copyrights and other rights in the Contribution: 412 (A) to copy, publish, display, and distribute the Contribution, in 413 whole or in part, 414 (B) to prepare translations of the Contribution into languages other 415 than English, in whole or in part, and to copy, publish, display, 416 and distribute such translations or portions thereof, 417 (C) to modify or prepare derivative works (in addition to 418 translations) that are based on or incorporate all or part of the 419 Contribution, and to copy, publish, display, and distribute such 420 derivative works, or portions thereof unless explicitly disallowed 421 in the notices contained in a Contribution [in the form specified 422 by the Legend Instructions], and 423 (D) to reproduce any trademarks, service marks or trade names which 424 are included in the Contribution solely in connection with the 425 reproduction, distribution or publication of the Contribution and 426 derivative works thereof as permitted by this Section 5.3, 427 provided that when reproducing Contributions, trademark and 428 service mark identifiers used in the Contribution, including TM 429 and (R), will be preserved. 431 5.4. Sublicenses by IETF Trust 432 The IETF Trust will sublicense the rights granted to it under Section 433 5.3 to all IETF participants for use within the IETF Standards 434 Process. This license is expressly granted under [TRUST LICENSE 435 DOCUMENT]. 437 In addition, the IETF Trust may grant additional sublicenses of the 438 licenses granted to it hereunder. In doing so, the IETF Trust will 439 comply with the guidance provided under RFC xxx [-outbound]. 441 5.5. No Patent License 442 The licenses granted in Section 5.3 shall not be deemed to grant any 443 right under any patent, patent application or other similar 444 intellectual property right disclosed by the Contributor under BCP 79 445 or otherwise. 447 5.6. Representations and Warranties 448 With respect to each Contribution, each Contributor represents that 449 to the best of his or her knowledge and ability: 451 a. The Contribution properly acknowledges all Contributors including 452 Indirect Contributors. 453 b. No information in the Contribution is confidential and the IETF, 454 IETF Trust, ISOC, and its affiliated organizations may freely 455 disclose any information in the Contribution. 456 c. There are no limits to the Contributor's ability to make the 457 grants, acknowledgments and agreements herein that are reasonably 458 and personally known to the Contributor. 459 d. The Contributor has not intentionally included in the Contribution 460 any material which is defamatory or untrue or which is illegal 461 under the laws of the jurisdiction in which the Contributor has 462 his or her principal place of business or residence. 463 e. All trademarks, trade names, service marks and other proprietary 464 names used in the Contribution that are reasonably and personally 465 known to the Contributor are clearly designated as such where 466 reasonable. 468 5.7. No Duty to Publish 469 The Contributor, and each named co-Contributor, acknowledges that the 470 IETF has no duty to publish or otherwise use or disseminate any 471 Contribution. The IETF reserves the right to withdraw or cease using 472 any Contribution that does not comply with the requirements of this 473 Section 5. 475 5.8. Trademarks 476 Contributors who claim trademark rights in terms used in their IETF 477 Contributions are requested to state specifically what conditions 478 apply to implementers of the technology relative to the use of such 479 trademarks. Such statements should be submitted in the same way as is 480 done for other intellectual property claims. (See [RFC3979] Section 481 6.) 483 5.9. Copyright in RFCs 484 Subject to each Contributor's (or its sponsor's) ownership of its 485 underlying Contributions as described in Section 5.6(which ownership 486 is qualified by the irrevocable licenses granted under Section 5.3), 487 each Contributor hereby acknowledges that the copyright in any RFC in 488 which such Contribution is included, other than an RFC that is an RFC 489 Editor Contribution, shall be owned by the IETF Trust. Such 490 Contributor shall be deemed to assign to the IETF Trust such 491 Contributor's copyright interest in the collective work constituting 492 such RFC upon the submission of such RFC for publication, and 493 acknowledges that a copyright notice acknowledging the IETF Trust's 494 ownership of the copyright in such RFC will be included in the 495 published RFC. 497 5.10. Contributors retention of rights 498 Although Contributors provide specific rights to the IETF, it is not 499 intended that this should deprive them of their right to exploit 500 their Contributions. To underscore this principle, the IETF Trust is 501 directed to issue a license or assurance to Contributors which 502 confirms that they may each make use of their Contributions as 503 published in an RFC in any way they wish, subject only to the 504 restriction that no Contributor has the right to represent any 505 document as an RFC, or equivalent of an RFC, if it is not a full and 506 complete copy or translation of the published RFC. 508 6. Legends, Notices and Other Standardized Text in IETF Documents 509 The IETF requires that certain standardized text be reproduced 510 verbatim in certain IETF Documents (including copies, derivative 511 works and translations of IETF Documents). Some of this standardized 512 text may be mandatory (e.g., copyright notices and disclaimers that 513 must be included in all RFCs) and some may be optional (e.g., 514 limitations on the right to make derivative works). The text itself, 515 as well as the rules that explain when and how it must be used, are 516 contained in the Legend Instructions. The Legend Instructions may be 517 updated from time to time, and the version of the standardized text 518 that must be included in IETF Documents is that which was posted in 519 the Legend Instructions on the date of publication. 521 The IETF reserves the right to refuse to publish Contributions that 522 do not include the legends and notices required by the Legend 523 Instructions. 525 It is important to note that each Contributor grants the IETF Trust 526 rights pursuant to this document and the policies described herein. 527 The legends and notices included in certain written Contributions 528 such as Internet-Drafts do not themselves convey any rights. They 529 are simply included to inform the reader (whether or not part of the 530 IETF) about certain legal rights and limitations associated with such 531 documents. 533 It is also important to note that additional copyright notices are 534 not permitted in IETF Documents except in the case where such 535 document is the product of a joint development effort between the 536 IETF and another standards development organization or the document 537 is a republication of the work of another standards development 538 organization. Such exceptions must be approved on an individual 539 basis by the IAB. 541 IANA Considerations (RFC Editor - please remove this section when 542 publishing) 543 This document presents no issues that should be considered by the 544 IANA (this section is here to mollify the ID-nits checker) 546 7. Security Considerations 547 This memo relates to IETF process, not any particular technology. 548 There are security considerations when adopting any technology, but 549 there are no known issues of security with IETF Contribution rights 550 policies. 552 8. References 554 8.1. Normative References 555 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 556 3", BCP 9, RFC 2026, October 1996. 557 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 558 the IETF Standards Process", BCP 11, RFC 2028, October 1996. 559 [RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF 560 Technology", BCP 79, RFC 3979, March 2005. 561 [RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR Trust," 562 RFC 4371, January 2006 564 8.2. Informative References 565 [RFC3978] Bradner, S. Ed., "IETF Rights in Contributions", RFC 3978, 566 March 2005. 567 [RFC4748] Bradner, S., "RFC 3978 Update to Recognize the IETF Trust," 568 RFC 4748, October 2006 569 [-outgoing] Halpern, J., "Advice to the Trustees of the IETF Trust on 570 Rights to be Granted in IETF Documents," RFC XXXX, date 571 [Berne Convention] "Berne Convention for the Protection of Literary 572 and Artistic Work", 573 http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html 575 9. Acknowledgements 576 The editors would like to acknowledge the help of the IETF IPR 577 Working Group provided during the development of the document. 579 10. Editors' Addresses 580 Scott Bradner 581 Harvard University 582 29 Oxford St. 583 Cambridge MA, 02138 USA 584 Phone: +1 617 495 3864 585 EMail: sob@harvard.edu 587 Jorge L. Contreras 588 WilmerHale 589 1875 Pennsylvania Avenue NW 590 Washington, DC 20006 USA 591 Phone: +1 202 663 6872 592 Email: jorge.contreras@wilmerhale.com 594 Full Copyright Statement 595 Copyright (C) The IETF Trust (2008). 596 This document is subject to the rights, licenses and restrictions 597 contained in BCP 78, and except as set forth therein, the authors 598 retain all their rights. 600 This document and the information contained herein are provided on an 601 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 602 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 603 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 604 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 605 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 606 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 608 Intellectual Property 609 The IETF takes no position regarding the validity or scope of any 610 Intellectual Property Rights or other rights that might be claimed to 611 pertain to the implementation or use of the technology described in 612 this document or the extent to which any license under such rights 613 might or might not be available; nor does it represent that it has 614 made any independent effort to identify any such rights. Information 615 on the procedures with respect to rights in RFC documents can be 616 found in BCP 78 and BCP 79. Copies of IPR disclosures made to the 617 IETF Secretariat and any assurances of licenses to be made available, 618 or the result of an attempt made to obtain a general license or 619 permission for the use of such proprietary rights by implementers or 620 users of this specification can be obtained from the IETF on-line IPR 621 repository at http://www.ietf.org/ipr. The IETF invites any 622 interested party to bring to its attention any copyrights, patents or 623 patent applications, or other proprietary rights that may cover 624 technology that may be required to implement this standard. Please 625 address the information to the IETF at ietf-ipr@ietf.org. 627 Acknowledgement 628 Funding for the RFC Editor function is currently provided by the 629 Internet Society. 631 changes 632 version 01 ->02 633 misc grammar fixes 634 added BOF to sec 1(a) 635 added 1(l) 636 reorder 3.2 637 moved sentence about translations within sec 3.3 638 reorder 5.3 (C) 639 added section 5.10 640 removed "an Informational RFC" from section 5.9 641 added text about assigning rights and acknowledging that a 642 copyright notice will be added to section 5.9 643 added 2nd pp to section 3.6 from RFC 3978 644 added pp on multiple copyright notices to sec 6 646 version 02 ->03 647 replaced the text in section 5.10 649 version 03 -> 04 650 change "requested" to "directed" in section 5.10 651 add sections 1 & 2 to the list of normative sections in section 2 652 sec 5.7 - replace last sentence 653 sec 5.3 preface - add "sublicensable" 654 sec 1 i - add that the IETF Trust maintains the Legend Instructions 655 open issues 656 a/ the use of the terms Contribution and Contributors - 657 for example in section 5.6 658 b/ do we need specific mention of work for hire in sec 3.2 660 version 04 -> 05 661 replaced section 5.1 & the 1st pp of section 5.3 662 replaced section 5.6 a 664 version 05 -> 06 - input from Jorge 665 fix various typos in document 666 add definition of "Indirect Contributor" 667 fix definition of "Reasonably and personally known" to be copyright- 668 related rather than patent-related 669 reword sec 5.6 a and remove definition of "Indirect Contributor" 670 add pointer to section 5.6 to section 5.9 671 tweak the wording on section 5.10 672 add "development" to the next to last sentence of section 6 674 version 06 -> 07 675 fix references etc to mollify the ID nits checker