idnits 2.17.1 draft-ietf-ipr-3978-incoming-01.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 3979, Section 5, paragraph 1 on line 577. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 577. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 577. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) -- 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 (26 June 2007) is 6149 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) == Missing Reference: '-outbound' is mentioned on line 427, but not defined == Unused Reference: 'Trust' is defined on line 519, but no explicit reference was found in the text == Unused Reference: 'RFC3978' is defined on line 523, but no explicit reference was found in the text == Unused Reference: 'Berne' is defined on line 525, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2028 (Obsoleted by RFC 9281) ** Obsolete normative reference: RFC 3979 (Obsoleted by RFC 8179) -- Possible downref: Non-RFC (?) normative reference: ref. 'Trust' -- Obsolete informational reference (is this intentional?): RFC 3978 (Obsoleted by RFC 5378) Summary: 5 errors (**), 0 flaws (~~), 6 warnings (==), 9 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 Jorge Contreras 5 WilmerHale 6 Editors 7 26 June 2007 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 December 26, 2007. 37 Copyright (C) IETF Trust (2007). 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 47 (-outgoing), replaces Section 10 of RFC 2026. 49 Table of Contents 50 1. Definitions 51 2. Introduction 52 2.1 No Retroactive Effect 53 3. Exposition of why these procedures are the way they are 54 3.1. Rights Granted in Contributions 55 3.2. Rights to use Contributions 56 3.3. Right to Produce Derivative Works 57 3.4. Rights to use Trademarks 58 3.5. Contributions Not Subject to Copyright 59 3.6. Copyright in RFCs 60 4. RFC Editor Documents 61 5. Rights in Contributions 62 5.1. General Policy 63 5.2. Confidentiality Obligations 64 5.3. Rights Granted by Contributors to the IETF Trust 65 5.4. Sublicenses by IETF Trust 66 5.5. No Patent License 67 5.6. Representations and Warranties 68 5.7. No Duty to Publish 69 5.8. Trademarks 70 5.9. Copyright in RFCs 71 6. Legends, Notices and Other Standardized Text in IETF Documents 72 7. Security Considerations 73 8. References 74 8.1. Normative References 75 8.2. Informative References 76 9. Acknowledgements 77 10. Editors' Addresses 78 Full Copyright Statement 80 1. Definitions 81 The following definitions are for terms used in the context of 82 thisdocument. Other terms, including "IESG," "ISOC," "IAB," and 83 "RFCEditor," are defined in [RFC2028]. 85 a. "Contribution": any submission to the IETF intended by the 86 Contributor for publication as all or part of an Internet-Draft or 87 RFC (except for RFC Editor Contributions described in Section 4 88 below) and any statement made within the context of an IETF 89 activity. Such statements include oral statements in IETF 90 sessions, as well as written and electronic communications made at 91 any time or place, which are addressed to: 92 o the IETF plenary session, 93 o any IETF working group or portion thereof, 94 o the IESG, or any member thereof on behalf of the IESG, 95 o the IAB or any member thereof on behalf of the IAB, 96 o any IETF mailing list, including the IETF list itself, any 97 working group or design team list, or any other list 98 functioning under IETF auspices, 99 o the RFC Editor or the Internet-Drafts function (except for RFC 100 Editor Contributions described in Section 4 below). 102 Statements made outside of an IETF session, mailing list or other 103 function, that are clearly not intended to be input to an IETF 104 activity, group or function, are not IETF Contributions in the 105 context of this document. 106 b. "Contributor": an individual submitting a Contribution. 107 c. "Copyright" means the legal right granted to an author in a 108 document or other work of authorship under applicable law. A 109 "copyright" is not equivalent to a "right to copy". Rather a 110 copyright encompasses all of the exclusive rights that an author 111 has in a work, such as the rights to copy, publish, distribute and 112 create derivative works of the work. An author often cedes these 113 rights to his or her employer or other parties as a condition of 114 employment or compensation. 115 d. "IETF": In the context of this document, the IETF includes all 116 individuals who participate in meetings, working groups, mailing 117 lists, functions and other activities which are organized or 118 initiated by ISOC, the IESG or the IAB under the general 119 designation of the Internet Engineering Task Force or IETF, but 120 solely to the extent of such participation. 121 e. "IETF Documents": RFCs and Internet-Drafts. 122 f. "IETF Standards Process": the activities undertaken by the IETF in 123 any of the settings described in 1(c) below. 124 g. "IETF Trust": A trust established under the laws of the 125 Commonwealth of Virginia, USA, in order to hold and administer 126 intellectual property rights for the benefit of the IETF. 127 h. "Internet-Draft": temporary documents used in the IETF Standards 128 Process. Internet-Drafts are posted on the IETF web site by the 129 IETF Secretariat. As noted in Section 2.2 of RFC 2026, Internet- 130 Drafts have a nominal maximum lifetime of six months in the IETF 131 Secretariat's public directory. 132 i. "Legend Instructions" means the standardized text that is 133 included in IETF Documents and the instructions and requirements 134 for including that standardized text in IETF Documents, each as 135 posted from time to time at www.ietf.org/legends. 136 j. "RFC": the basic publication series for the IETF. RFCs are 137 published by the RFC Editor. Although RFCs may be superseded in 138 whole or in part by subsequent RFCs, the text of an RFC is not 139 altered once published in RFC form. (See [RFC2026] Section 2.1) 140 k. "Reasonably and personally known": means something an individual 141 knows personally or, because of the job the individual holds, 142 would reasonably be expected to know. This wording is used to 143 indicate that an organization cannot purposely keep an individual 144 in the dark about patents or patent applications just to avoid the 145 disclosure requirement. But this requirement should not be 146 interpreted as requiring the IETF Contributor or participant (or 147 his or her represented organization, if any) to perform a patent 148 search in an attempt to find applicable IPR. 150 2. Introduction 151 In all matters of copyright and document procedures, the intent is to 152 benefit the Internet community and the public at large, while 153 respecting the legitimate rights of others. 155 Under the laws of most countries and current international treaties 156 (for example the "Berne Convention for the Protection of Literary and 157 Artistic Work" [Berne Convention]), authors obtain numerous rights in 158 the works they produce automatically upon producing them. These 159 rights include copyrights, moral rights and other rights. In many 160 cases, if the author produces a work within the scope of his or her 161 employment, most of those rights are usually assigned to the 162 employer, either by operation of law or, in many cases, under 163 contract. (The Berne Convention names some rights as "inalienable", 164 which means that the author retains them in all cases.) 166 In order for Contributions to be used within the IETF Standards 167 Process, including when they are published as Internet-Drafts or 168 RFCs, certain limited rights must be granted to the IETF Trust, which 169 then grants the necessary rights to the IETF. In addition, 170 Contributors must make representations to IETF Trust and the IETF 171 regarding their ability to grant these rights. 173 Section 1 provides definitions used in these policies. Sections 3 174 and 4 of this document explain the rationale for these provisions. 175 Only sections 5 and 6 of this document are normative, the other 176 sections are informative. A companion document RFC 3979 [RFC3979] 177 deals with rights, including possible patent rights, in technologies 178 developed or specified as part of the IETF Standards Process. This 179 document is not intended to address those issues. This memo 180 obsoletes RFC 3978 and 4748 and, with RFC 3979 and RFC 181 xxx(-outgoing), replaces Section 10 of RFC 2026. 183 This document is not intended as legal advice. Readers are advised to 184 consult their own legal advisors if they would like a legal 185 interpretation of their rights or the rights of the IETF Trust in any 186 Contributions they make. 188 2.1 No Retroactive Effect 189 This memo does not retroactively obtain additional rights from 190 Contributions that predate the date that the IETF Trust announces the 191 adoption of these procedures. 193 3. Exposition of Why These Procedures Are the Way They Are 195 3.1. Rights Granted in Contributions 196 The IETF Trust and IETF must obtain the right to publish an IETF 197 Contribution as an RFC or an Internet-Draft from the Contributors. 199 A primary objective of this policy is to obtain from the document 200 authors only the non-exclusive rights that are needed to develop and 201 publish IETF Documents and to use IETF Contributions in the IETF 202 Standards Process and potentially elsewhere. 204 The authors retain all other rights, but cannot withdraw the above 205 rights from the IETF Trust and IETF. 207 It is important to note that under this document Contributors are 208 required to grant certain rights to the IETF Trust, which holds all 209 IETF-related intellectual property on behalf of the IETF community. 210 The IETF Trust will, in turn, grant a sublicense of these rights to 211 all IETF participants for use in the IETF Standards Process. This 212 sublicense is necessary for the standards development work of the 213 IETF to continue. In addition, the IETF Trust may grant certain 214 other sublicenses of the rights that it is granted under this 215 document. In granting such other sublicenses, the IETF Trust will be 216 guided [and bound] by documents such as [-outbound]. 218 3.2. Rights to use Contributions 219 Because, under the laws of most countries and applicable 220 international treaties, copyright rights come into existence when a 221 work of authorship is created (but see Section 3.5 below regarding 222 public domain documents), and IETF cannot make use of IETF 223 Contributions if it does not have sufficient rights with respect to 224 these copyright rights, it is important that the IETF receive 225 assurances from all Contributors that they have the authority to 226 grant the IETF the rights that they claim to grant. Without this 227 assurance, IETF and its participants would run a greater risk of 228 liability to the owners of these rights. To this end, IETF asks 229 Contributors to give the assurances in Section5.6 below. These 230 assurances are requested, however, only to the extent of the 231 Contributor's reasonable and personal knowledge. (See Section 1(l)) 233 3.3. Right to Produce Derivative Works 234 The IETF needs to be able to evolve IETF Documents in response to 235 experience gained in the deployment of the technologies described in 236 such IETF Documents, to incorporate developments in research and to 237 react to changing conditions on the Internet and other IP networks. 238 The IETF may also decide to permit others to develop derivative works 239 based on Contributions. In order to do this, the IETF must be able 240 to produce derivatives of its documents; thus the IETF must obtain 241 the right from Contributors to produce derivative works. The right 242 to produce derivative works is required for all IETF standards track 243 documents and for most IETF non-standards track documents. There are 244 two exceptions to this requirement: documents describing proprietary 245 technologies and documents that are republications of the work of 246 other standards organizations. 248 The right to produce derivative works must be granted in order for an 249 IETF working group to accept a Contribution as a working group 250 document or otherwise work on it. For non-working group Contributions 251 where the Contributor requests publication as a standards track RFC, 252 the right to produce derivative works must be granted before the IESG 253 will issue an IETF Last-Call and, for most non-standards track non- 254 working group Contributions, before the IESG will consider the 255 Internet-Draft for publication. Occasionally a Contributor may not 256 want to grant publication rights or the right to produce derivative 257 works before finding out if a Contribution has been accepted for 258 development in the IETF Standards Process. In these cases the 259 Contributor may include a limitation on the right to make derivative 260 works in the form specified in the Legend Instructions. A working 261 group can discuss the Contribution with the aim to decide if it 262 should become a working group document, even though the right to 263 produce derivative works or to publish the Contribution as an RFC has 264 not yet been granted. However, if the Contribution is accepted for 265 development, the Contributor must resubmit the Contribution without 266 the limitation notices before a working group can formally adopt the 267 Contribution as a working group document. The IETF Trust may 268 establish different policies for granting sublicenses with respect to 269 different types of Contributions and content within Contributions 270 (such as executable code versus descriptive text or references to 271 third party materials). The IETF Trust's policies concerning the 272 granting of sublicenses to make derivative works will be guided by 273 RFC [-outbound. 275 The IETF has historically encouraged organizations to publish details 276 of their technologies, even when the technologies are proprietary, 277 because understanding how existing technology is being used helps 278 when developing new technology. But organizations that publish 279 information about proprietary technologies are frequently not willing 280 to have the IETF produce revisions of the technologies and then 281 possibly claim that the IETF version is the "new version" of the 282 organization's technology. Organizations that feel this way can 283 specify that a Contribution be published with the other rights 284 granted under this document but may withhold the right to produce 285 derivative works other than translations. The right to produce 286 translations is required before any Contribution can be published as 287 an RFC to ensure the widest possible distribution of the material in 288 RFCs. 290 In addition, IETF Documents frequently make normative references to 291 standards or recommendations developed by other standards 292 organizations. Since the publications of some standards organizations 293 are not public documents, it can be quite helpful to the IETF to 294 republish, with the permission of the other standards organization, 295 some of these documents as RFCs so that the IETF community can have 296 open access to them to better understand what they are referring to. 297 In these cases the RFCs can be published without the right for the 298 IETF to produce derivative works. In both of the above cases in 299 which the production of derivative works is excluded, the Contributor 300 must include a special legend in the Contribution, as specified in 301 the Legend Instructions, in order to notify IETF participants about 302 this restriction. 304 3.4. Rights to Use Trademarks 305 Contributors may wish to seek trademark or service mark protection on 306 any terms that are coined or used in their Contributions. IETF makes 307 no judgment about the validity of any such trademark rights. 308 However, the IETF requires each Contributor, under the licenses 309 described in Section 5.3 below, to grant IETF Trust a perpetual 310 license to use any such trademarks or service marks solely in 311 exercising rights to reproduce, publish, discuss and modify the IETF 312 Contribution. This license does not authorize IETF or others to use 313 any trademark or service mark in connection with any product or 314 service offering. 316 3.5. Contributions Not Subject to Copyright 317 Certain documents, including those produced by the U.S. government 318 and those which are in the public domain, may not be protected by the 319 same copyright and other legal rights as other documents. 320 Nevertheless, we ask each Contributor to grant to the IETF the same 321 rights as he or she would grant, and to make the same 322 representations, as though the IETF Contribution were protected by 323 the same legal rights as other documents, and as though the 324 Contributor could be able to grant these rights. We ask for these 325 grants and representations only to the extent that the Contribution 326 may be protected. We believe they are necessary to protect the ISOC, 327 the IETF Trust, the IETF, the IETF Standards Process and all IETF 328 participants, and also because the IETF does not have the resources 329 or wherewithal to make any independent investigation as to the actual 330 proprietary status of any document submitted to it. 332 3.6 Copyright in RFCs. 333 As noted above, Contributors to the IETF (or their employers) retain 334 ownership of the copyright in their Contributions. This includes 335 Internet-Drafts and all other Contributions made within the IETF 336 Standards Process (e.g., via e-mail, oral comment and otherwise). 337 However, it is important that the IETF (through the IETF Trust) own 338 the copyright in documents that are published as RFCs (other than 339 Informational RFCs and RFCs that are submitted as RFC Editor 340 Contributions). Ownership of the copyright in an RFC does not 341 diminish the Contributors' rights in their underlying contributions, 342 but it does prevent anyone other than the IETF Trust (and its 343 licensees) from republishing or modifying an RFC in RFC format. In 344 this respect, Contributors are treated the same as anybody else: 345 though they may extract and republish their own Contributions without 346 limitation, they may not do so in the IETF's RFC format. And while 347 this principle (which is included in Section 5.9 below) may appear to 348 be new to IETF, it actually reflects historical practice and has been 349 observed for many years through the inclusion of an ISOC or IETF 350 Trust copyright notice on all RFC documents since the publication of 351 RFC 2026. 353 4. RFC Editor Documents 354 This document only relates to Contributions made as part of the IETF 355 Standards Process. Other documents that are referred to as Internet- 356 Drafts and RFCs may be submitted to and published by the RFC Editor 357 independently of the IETF Standards Process. Such "RFC Editor 358 Documents" are not covered by this document. RFC Editor 359 Contributions must be marked appropriately as described in the Legend 360 Instructions. See the RFC Editor web page for information about the 361 policies concerning rights in RFC Editor Documents. 363 5. Rights in Contributions 365 5.1. General Policy 366 By submission of a Contribution, each person actually submitting the 367 Contribution, and each named co-Contributor, is deemed to have read 368 and understood the rules and requirements set forth in this document. 369 Each Contributor is deemed, by the act of submitting a Contribution, 370 to enter into a legally-binding agreement to comply with the terms 371 and conditions set forth in this document, on his or her own behalf 372 and on behalf of the organization the Contributor represents or is 373 sponsored by (if any), when submitting the Contribution. No further 374 acknowledgement, signature or other action is required to bind a 375 Contributor to these terms and conditions. The operation of the IETF 376 and the work conducted by its many participants is dependent on such 377 agreement by each Contributor, and each IETF participant expressly 378 relies on the agreement of each Contributor to the terms and 379 conditions set forth in this document. 381 5.2. Confidentiality Obligations 382 No information or document that is subject to any requirement of 383 confidentiality or any restriction on its dissemination may be 384 submitted as a Contribution or otherwise considered in any part of 385 the IETF Standards Process, and there must be no assumption of any 386 confidentiality obligation with respect to any Contribution. Each 387 Contributor agrees that any statement in a Contribution, whether 388 generated automatically or otherwise, that states or implies that the 389 Contribution is confidential or subject to any privilege, can be 390 disregarded for all purposes, and will be of no force or effect. 392 5.3. Rights Granted by Contributors to the IETF Trust 393 To the extent that a Contribution or any portion thereof is protected 394 by copyright or other rights of authorship, the Contributor, and each 395 named co-Contributor, and the organization he or she represents or is 396 sponsored by (if any) grant a perpetual, irrevocable, non-exclusive, 397 royalty-free, world-wide right and license to the IETF Trust under 398 all such copyrights and other rights in the Contribution. 400 (A) to copy, publish, display, and distribute the Contribution, in 401 whole or in part, 402 (B) to prepare translations of the Contribution into languages other 403 than English, in whole or in part, and to copy, publish, display, 404 and distribute such translations or portions thereof, 405 (C) unless explicitly disallowed in the notices contained in a 406 Contribution [in the form specified by the Legend Instructions], 407 to modify or prepare derivative works (in addition to 408 translations) that are based on or incorporate all or part of the 409 Contribution, and to copy, publish, display, and distribute such 410 derivative works, or portions thereof, and 411 (D) to reproduce any trademarks, service marks or trade names which 412 are included in the Contribution solely in connection with the 413 reproduction, distribution or publication of the Contribution and 414 derivative works thereof as permitted by this Section 5.3, 415 provided that when reproducing Contributions, trademark and 416 service mark identifiers used in the Contribution, including TM 417 and (R) will be preserved. 419 5.4 Sublicenses by IETF Trust 420 The IETF Trust will sublicense the rights granted to it under Section 421 5.3 to all IETF participants for use within the IETF Standards 422 Process. This license is expressly granted under [TRUST LICENSE 423 DOCUMENT]. 425 In addition, the IETF Trust may grant additional sublicenses of the 426 licenses granted to it hereunder. In doing so, the IETF Trust will 427 comply with the guidance provided under RFC xxx [-outbound]. 429 5.5 No Patent License 430 The licenses granted in Section 5.3 shall not be deemed to grant any 431 right under any patent, patent application or other similar 432 intellectual property right disclosed by the Contributor under BCP 79 433 or otherwise. 435 5.6. Representations and Warranties 436 With respect to each Contribution, each Contributor represents that 437 to the best of his or her knowledge and ability: 439 a. The Contribution properly acknowledges all major Contributors. A 440 major Contributor is any person who has materially or 441 substantially contributed to the Contribution. 442 b. No information in the Contribution is confidential and the IETF, 443 IETF Trust, ISOC, and its affiliated organizations may freely 444 disclose any information in the Contribution. 445 c. There are no limits to the Contributor's ability to make the 446 grants, acknowledgments and agreements herein that are reasonably 447 and personally known to the Contributor. 448 d. The Contributor has not intentionally included in the Contribution 449 any material which is defamatory or untrue or which is illegal 450 under the laws of the jurisdiction in which the Contributor has 451 his or her principal place of business or residence. 452 e. All trademarks, trade names, service marks and other proprietary 453 names used in the Contribution that are reasonably and personally 454 known to the Contributor are clearly designated as such where 455 reasonable. 457 5.7. No Duty to Publish 458 The Contributor, and each named co-Contributor, acknowledges that the 459 IETF has no duty to publish or otherwise use or disseminate any 460 Contribution. The IETF reserves the right to withdraw or cease using 461 any Contribution that does not comply with the requirements of 462 Section 5.3 and Section 5.4 or 5.6. 464 5.8. Trademarks 465 Contributors who claim trademark rights in terms used in their IETF 466 Contributions are requested to state specifically what conditions 467 apply to implementers of the technology relative to the use of such 468 trademarks. Such statements should be submitted in the same way as is 469 done for other intellectual property claims. (See [RFC3979] Section 470 6.) 472 5.9 Copyright in RFCs 473 Subject to each Contributor's (or its sponsor's) ownership of its 474 underlying Contributions (which ownership is qualified by the 475 irrevocable licenses granted under Section 5.3), each Contributor 476 hereby acknowledges that the copyright in any RFC in which such 477 Contribution is included, other than an Informational RFC or an RFC 478 that is an RFC Editor Contribution, shall be owned by the IETF Trust. 480 6. Legends, Notices and Other Standardized Text in IETF Documents 481 The IETF requires that certain standardized text be reproduced 482 verbatim in certain IETF Documents (including copies, derivative 483 works and translations of IETF Documents). Some of this standardized 484 text may be mandatory (e.g., copyright notices and disclaimers that 485 must be included in all RFCs) and some may be optional (e.g., 486 limitations on the right to make derivative works). The text itself, 487 as well as the rules that explain when and how it must be used, are 488 contained in the Legend Instructions. The Legend Instructions may be 489 updated from time to time, and the version of the standardized text 490 that must be included in IETF Documents is that which was posted in 491 the Legend Instructions on the date of publication. 493 The IETF reserves the right to refuse to publish Contributions that 494 do not include the legends required by the Legend Instructions. 496 It is important to note that each Contributor grants the IETF Trust 497 rights pursuant to this document and the policies described herein. 498 The legends and notices included in certain written Contributions 499 such as Internet-Drafts do not themselves convey any rights. They 500 are simply included to inform the reader (whether or not part of the 501 IETF) about certain legal rights and limitations associated with such 502 documents. 504 7. Security Considerations 505 This memo relates to IETF process, not any particular technology. 506 There are security considerations when adopting any technology, but 507 there are no known issues of security with IETF Contribution rights 508 policies. 510 8. References 512 8.1. Normative References 513 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 514 3", BCP 9, RFC 2026, October 1996. 515 [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in 516 the IETF Standards Process", BCP 11, RFC 2028, October 1996. 517 [RFC3979] Bradner, S., Ed, "Intellectual Property Rights in IETF 518 Technology", BCP 79, RFC 3979, March 2005. 519 [Trust] IETF Trust Agreement - http://iaoc.ietf.org/docs/IETF-Trust- 520 Agreement-Executed-12-15-05.pdf 522 8.2. Informative References 523 [RFC3978] Bradner, S. Ed., "IETF Rights in Contributions", RFC 3978, 524 March 2005. 525 [Berne] "Berne Convention for the Protection of Literary and Artistic 526 Work", http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html 528 9. Acknowledgements 529 The editors would like to acknowledge the help of the IETF IPR 530 Working Group provided during the development of the document. 532 10. Editors' Addresses 533 Scott Bradner 534 Harvard University 535 29 Oxford St. 536 Cambridge MA, 02138 USA 537 Phone: +1 617 495 3864 538 EMail: sob@harvard.edu 540 Jorge L. Contreras 541 WilmerHale 542 1875 Pennsylvania Avenue NW 543 Washington, DC 20006 USA 544 Phone: +1 202 663 6872 545 Email: jorge.contreras@wilmerhale.com 547 Full Copyright Statement 548 Copyright (C) The IETF Trust (2007). This document is subject to the 549 rights, licenses and restrictions contained in BCP 78, and except as 550 set forth therein, the authors retain all their rights. This 551 document and the information contained herein are provided on an "AS 552 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTSOR 553 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 554 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 555 EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 556 USE OFTHE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 557 IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 558 PURPOSE. 560 Intellectual Property 561 The IETF takes no position regarding the validity or scope of any 562 Intellectual Property Rights or other rights that might be claimed to 563 pertain to the implementation or use of the technology described in 564 this document or the extent to which any license under such rights 565 might or might not be available; nor does it represent that it has 566 made any independent effort to identify any such rights. Information 567 on the procedures with respect to rights in RFC documents can be 568 found in BCP 78 and BCP 79. Copies of IPR disclosures made to the 569 IETF Secretariat and any assurances of licenses to be made available, 570 or the result of an attempt made to obtain a general license or 571 permission for the use of such proprietary rights by implementers or 572 users of this specification can be obtained from the IETF on-line IPR 573 repository at http://www.ietf.org/ipr. The IETF invites any 574 interested party to bring to its attention any copyrights, patents or 575 patent applications, or other proprietary rights that may cover 576 technology that may be required to implement this standard. Please 577 address the information to the IETF at ietf-ipr@ietf.org. 579 Acknowledgement 580 Funding for the RFC Editor function is currently provided by the 581 Internet Society. ?? 583 ?? 585 ?? 587 ?? 589 US1DOCS 6241323v2