idnits 2.17.1 draft-malis-iab-stream-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 draft header indicates that this document updates RFC4846, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4846, updated by this document, for RFC5378 checks: 2007-03-08) -- 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 (November 24, 2009) is 5266 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3979 (Obsoleted by RFC 8179) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) ** Obsolete normative reference: RFC 4844 (Obsoleted by RFC 8729) ** Obsolete normative reference: RFC 4879 (Obsoleted by RFC 8179) -- Obsolete informational reference (is this intentional?): RFC 5377 (Obsoleted by RFC 8721) Summary: 5 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Architecture Board A. Malis 3 Internet-Draft For the IAB 4 Updates: 4846 (if approved) 5 Intended status: Informational 6 Expires: May 23, 2010 November 24, 2009 8 Procedures for Rights Handling in the RFC IAB Stream 9 draft-malis-iab-stream-00.txt 11 Abstract 13 This document specifies the procedures by which authors of RFC 14 IAB Stream documents grant the community "incoming" rights 15 for copying and using the text. It also specifies the "outgoing" 16 rights the community grants to readers and users of those documents, 17 and it requests that the IETF Trust manage the outgoing rights to 18 effect this result. 20 Status of this Memo 22 This Internet-Draft is submitted to IETF in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on May 23, 2010. 43 Copyright Notice 45 Copyright (c) 2009 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 4. Rules for Submission and Use of Material . . . . . . . . . . . 4 64 5. Procedures requested of the IETF Trust . . . . . . . . . . . . 5 65 6. Patent and Trademark Rules for the IAB Stream . . . . . . . . . 5 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 67 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 68 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 7 71 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7 72 11. IAB Members at the Time of This Writing . . . . . . . . . . . . 7 73 12. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 75 1. Introduction 77 As the IETF has grown, the process and the community have become more 78 careful about defining the rights relating to copying documents that 79 are granted by authors to the community, and the corresponding rights 80 that are granted by the community to readers and users of these 81 documents. The creation of the IETF Trust [RFC4371], with its special 82 role in managing intellectual property rights (IPR), has also 83 increased the need to be explicit about these rights and decisions. 85 This document defines the copyright procedures for RFC IAB Stream 86 documents. It parallels the procedures for IETF- produced documents, 87 defined in RFC 5377 [RFC5377] and RFC 5378 [RFC5378]. 89 In summary, submissions in the IAB Stream use the same submission 90 procedures and mechanisms that are defined in RFC 5378, and hence 91 require the same "incoming rights" as IETF-stream documents. This 92 document provides advice to the Trustees of the IETF Trust on 93 "outgoing" rights to be granted to readers and users of 94 IAB Stream documents, and it explicitly requests the IETF 95 Trust to manage the rights in accordance with this advice. 97 This document also specifies the policies with regard to the 98 disclosure of Patents and Trademarks that may be relevant to a 99 submission intended for the IAB Stream. 101 2. Background 103 The concept of RFC streams in general, and the IAB RFC Stream in 104 particular, is described in Section 5 of RFC 4844 [RFC4844]. 106 Section 8 of RFC 4846 [RFC4846] presented the copyright rules for the 107 Independent Submission stream. The present document is intended to 108 be fully consistent with that section, and to update it by clarifying 109 the formal procedures that the IETF Trust will use to effect those 110 rules. In particular, it is the intention of this document to make 111 the copyright rules for IAB stream documents identical to those for 112 Independent Stream documents. 114 3. Goals 116 The goal of the IAB Stream of RFCs is to publish information from the 117 IAB to the Internet community. Consistent with the principle stated 118 for the Independent Submission stream in Section 8 of RFC 4846, this 119 objective will best be met with a liberal copyright policy on IAB 120 Stream documents. Therefore, the IAB Stream policy is to allow any 121 individual reading such documents to use the content thereof in any 122 manner. The only restriction is that proper credit ("attribution") 123 must be given. Lawyers describe this liberal policy by saying that 124 this stream normally permits "unlimited derivative works". The only 125 additional restriction for the use of IAB documents is that proper 126 credit ("attribution") must be given. 128 However, for a small subset of documents published as IAB Stream 129 documents, such as output from other standards bodies, it is not 130 reasonable to permit unlimited derivative works. In such cases, 131 authors are permitted to request that the published IAB Stream 132 documents permit no derivative works. 134 Note also that this unlimited derivative works policy applies to all 135 parts of an IAB Stream document, including any code. Therefore, no 136 separate licensing procedure is required for extracting and adapting 137 code that is contained in an IAB Stream document submitted under the 138 (preferred) unlimited derivative works terms. On the other hand, code 139 may not be extracted and adapted from IAB Stream documents submitted 140 under the "no derivative works" terms. 142 4. Rules for Submission and Use of Material 144 IAB Stream authors will submit their material as Internet-Drafts. 145 These drafts will be submitted to, and stored in, the IETF 146 Internet-Drafts repository in the same fashion as IETF Internet- 147 Drafts. 149 During Internet-Draft submission, authors who intend to submit their 150 document for publication in the IAB Stream will grant rights as 151 described in RFC 5378 [RFC5378]. To request that the contribution be 152 published as an RFC that permits no derivative works, an author may 153 use the form specified for use with RFC 5378. 155 The IETF Trust will publish rules that provide that the Trust grants 156 to readers and users of material from IAB Stream RFCs the right to 157 make unlimited derivative works, unless the RFC specifies that no 158 derivative works are permitted. This will permit anyone to copy, 159 extract, modify, or otherwise use material from IAB Stream RFCs as 160 long as suitable attribution is given. 162 Contributors of Internet-Drafts intended for the IAB Stream will 163 include the appropriate boilerplate defined by the IETF Trust. This 164 boilerplate shall indicate compliance with RFC 5378 and shall 165 explicitly indicate either that no derivative works can be based on 166 the contribution, or, as is preferred, that unlimited derivative 167 works may be crafted from the contribution. 169 5. Procedures requested of the IETF Trust 171 The IAB requests that the IETF Trust and its Trustees assist in 172 meeting the goals and procedures set forth in this document. 174 The Trustees are requested to publicly confirm their willingness and 175 ability to accept responsibility for the Intellectual Property Rights 176 for the IAB Stream. 178 Specifically, the Trustees are asked to develop the necessary 179 boilerplate to enable the suitable marking of documents so that the 180 IETF Trust receives the rights as specified in RFC 5378. These 181 procedures need to also allow authors to indicate either no rights to 182 make derivative works, or preferentially, the right to make unlimited 183 derivative works from the documents. It is left to the Trust to 184 specify exactly how this shall be clearly indicated in each document. 186 6. Patent and Trademark Rules for the IAB Stream 188 As specified above, contributors of documents for the IAB stream are 189 expected to use the IETF Internet-Draft process, complying therein 190 with the rules specified in the latest version of BCP 9, whose 191 version at the time of writing was RFC 2026 [RFC2026]. This includes 192 the disclosure of Patent and Trademark issues that are known, or can 193 be reasonably expected to be known, to the contributor. 195 Disclosure of license terms for patents is also requested, as 196 specified in the most recent version of BCP 79. The version of BCP 79 197 at the time of this writing was RFC 3979 [RFC3979] updated by RFC 198 4879 [RFC4879]. The IAB Stream has chosen to use the IETF's IPR 199 disclosure mechanism, www.ietf.org/ipr/, for this purpose. The IAB 200 would prefer the most liberal terms possible be made available for 201 IAB Stream documents. Terms which do not require fees or licensing 202 are preferable. Non-discriminatory terms are strongly preferred over 203 those which discriminate among users. However, although disclosure is 204 required and the IAB may consider disclosures and terms in making a 205 decision as to whether to submit a document for publication, there 206 are no specific requirements on the licensing terms for intellectual 207 property related to IAB Stream publication. 209 7. IANA Considerations 211 There are no IANA Considerations in this document, as no computer 212 protocols are discussed, and no code points assigned. This section 213 may be removed by the RFC Editor. 215 This document does make a specific request of the IASA, as described 216 in preceding sections. 218 8. Security Considerations 220 The integrity and quality of the IAB Stream are the responsibility of 221 the IAB. This document does not change those responsibilities. 223 9. References 225 9.1. Normative References 227 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 228 3", BCP 9, RFC 2026, October 1996. 230 [RFC3979] Bradner, S., "Intellectual Property Rights in IETF 231 Technology", BCP 79, RFC 3979, March 2005. 233 [RFC4371] Carpenter, B. and L. Lynch, "BCP 101 Update for IPR 234 Trust", RFC 4371, BCP 101, January 2006. 236 [RFC4844] Daigle, L. and Internet Architecture Board, "The RFC 237 Series and RFC Editor", RFC 4844, July 2007. 239 [RFC4846] Klensin, J. and D. Thaler, "Independent Submissions to the 240 RFC Editor", RFC 4846, July 2007. 242 [RFC4879] Narten, T., "Clarification of the Third Party Disclosure 243 Procedure in RFC 3979", BCP 79, RFC 4879, April 2007. 245 [RFC5378] Bradner, S. and J. Contreras, "Rights Contributors Provide 246 to the IETF Trust", BCP 78, RFC 5378, November 2008. 248 9.2. Informative References 250 [RFC5377] Halpern, J., "Advice to the Trustees of the IETF Trust on 251 Rights to Be Granted in IETF Documents", RFC 5377, 252 November 2008. 254 [Braden] Braden, R. and J. Halpern, "Procedures for Rights Handling 255 in the RFC Independent Stream", draft-braden-independent- 256 submission-02.txt, November 2009, work in progress 258 10. Acknowledgements 260 The author wishes to acknowledge that the majority of text of this 261 document was derived from [Braden], and wishes to thank the authors 262 of that document. 264 11. IAB Members at the Time of This Writing 266 Marcelo Bagnulo 267 Gonzalo Camarillo 268 Stuart Cheshire 269 Vijay Gill 270 Russ Housley 271 John Klensin 272 Olaf Kolkman 273 Gregory Lebovitz 274 Andrew Malis 275 Danny McPherson 276 David Oran 277 Jon Peterson 278 Dave Thaler 280 12. Author's Address 282 Andrew G. Malis 283 Verizon Communications 284 117 West St. 285 Waltham, MA 02451 286 USA 288 Email: andrew.g.malis@verizon.com