idnits 2.17.1 draft-iab-publication-00.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 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 197. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 208. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 215. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 221. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing revision: the document name given in the document, 'draft-iab-publication', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-iab-publication', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-iab-publication', but the file name used is 'draft-iab-publication-00' == 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 (December 21, 2006) is 6333 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) ** Downref: Normative reference to an Informational draft: draft-iab-rfc-editor (ref. '1') ** Downref: Normative reference to an Informational draft: draft-iesg-sponsoring-guidelines (ref. '2') Summary: 5 errors (**), 1 flaw (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Daigle 3 Internet-Draft Ed. 4 Expires: June 24, 2007 Internet Architecture Board 5 (IAB) 6 December 21, 2006 8 Process for Publication of IAB RFCs 9 draft-iab-publication 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on June 24, 2007. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2006). 40 Abstract 42 From time to time, the Internet Architecture Board (IAB) publishes 43 documents as Requests for Comments (RFCs). This document defines the 44 process by which those documents are produced, reviewed, and 45 published in the RFC series. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Review and Approval . . . . . . . . . . . . . . . . . . . . . 4 51 3. IAB RFC Publication Process . . . . . . . . . . . . . . . . . 5 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 54 6. IAB members at the time of approval . . . . . . . . . . . . . 8 55 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 56 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 57 Intellectual Property and Copyright Statements . . . . . . . . . . 11 59 1. Introduction 61 From time to time, the IAB has cause to publish documents as Requests 62 for Comments (RFCs). These occasions include: 64 o documents that arise from consideration of an issue by the IAB and 65 are authored by the IAB through a nominated editor. 67 o documents that report on IAB activities, such as workshop reports 68 and are authored by a nominated editor, generally from among the 69 activity participants. 71 o documents that are not the outcome of an IETF Working Group 72 effort, but which the IAB has determined would be of benefit to 73 the IETF community to publish. Such document need not necessarily 74 be authored or revised by the IAB. 76 The majority of documents published by the IAB will be classified as 77 Informational RFCs (see [3]). Generally-speaking, the IAB does not 78 publish Standards-track or Experimental RFCs. If the IAB has cause 79 to publish a document as a BCP, it would fall under the approval 80 process of the IETF Standards stream of RFCs (see [1]). 82 2. Review and Approval 84 In many cases, the IAB publishes documents to provide a permanent 85 record of an IAB statement or position. In such cases, the IAB uses 86 its internal discussion processes to refine the expression and 87 technical content of the document, and the document is approved for 88 publication if, and only if, the IAB is in agreement on its 89 substantive content. 91 For certain documents, it may not be appropriate for the IAB to take 92 responsibility for technical correctness. For example, where the IAB 93 has sponsored a workshop where not all the participants were members 94 of the IAB and/or not all the members of the IAB were present, 95 approval by the IAB of a report of the workshop is used only to 96 assert that the report is a faithful report of the proceedings of the 97 workshop and that the matter is of interest to the community. 99 Documents for which the IAB takes responsibility for technical 100 correctness (the most usual case) will be indicated by noting the IAB 101 as an author of the document, with individuals noted as editors or 102 text authors. Other documents, such as workshop reports, will not 103 specify the IAB as an author (although this does not preclude 104 individual IAB members from being authors or editors). 106 In general, the document (introductory) text should make plain the 107 role of the IAB in publishing and supporting the text. Should the 108 IAB have significant issues with any individual item in the document, 109 a note may be included in the document explaining the issue. 111 3. IAB RFC Publication Process 113 The following is a description of the process used by the IAB to 114 publish IAB documents as RFCs. 116 1. The document is determined to be an IAB document by the IAB, as 117 described in Section 1. 119 2. The IAB publishes an IAB draft (draft-iab-*). Comments on the 120 draft are reviewed and may be integrated into successive 121 iterations of the draft. In addition to considering comments 122 received on the draft, the IAB may elect to refer the document to 123 individuals or groups and explicitly solicit comments as 124 appropriate. 126 3. For documents intended to be published as BCPs, the document is 127 passed to the IESG with a sponsoring Area Director (AD), and 128 follows the process outlined in [2]. 130 4. For documents intended to be Informational RFCs, the remainder of 131 this process is followed. 133 5. The chair of the IAB issues an IETF-wide Call For Comment on the 134 IETF Announce mailing list. The comment period is normally no 135 shorter than four weeks. 137 6. Comments received are considered for integration into the draft. 138 The IAB shall determine whether the document is ready for 139 publication based on the comments received, or whether another 140 round of document editing and, optionally, a further call for 141 input is required. 143 7. The document is passed to the RFC editor for publication as an 144 IAB document Informational RFC. 146 4. Security Considerations 148 This document does not discuss matters with any particular security 149 implications. 151 5. IANA Considerations 153 This document requires no action on IANA's part. 155 6. IAB members at the time of approval 157 To be filled in. 159 7. References 161 [1] Daigle, L., "The RFC Series and RFC Editor", 162 draft-iab-rfc-editor (work in progress), December 2006. 164 [2] Arkko, J., "Guidance on Area Director Sponsoring of Documents", 165 draft-iesg-sponsoring-guidelines (work in progress), 166 October 2006. 168 [3] Bradner, S., "The Internet Standards Process -- Revision 3", 169 RFC 2026, October 1996. 171 Authors' Addresses 173 Leslie L. Daigle 174 Ed. 176 Email: ledaigle@cisco.com, leslie@thinkingcat.com 178 (IAB) 180 Email: iab@iab.org 181 URI: http://www.iab.org/ 183 Full Copyright Statement 185 Copyright (C) The IETF Trust (2006). 187 This document is subject to the rights, licenses and restrictions 188 contained in BCP 78, and except as set forth therein, the authors 189 retain all their rights. 191 This document and the information contained herein are provided on an 192 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 193 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 194 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 195 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 196 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 197 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 199 Intellectual Property 201 The IETF takes no position regarding the validity or scope of any 202 Intellectual Property Rights or other rights that might be claimed to 203 pertain to the implementation or use of the technology described in 204 this document or the extent to which any license under such rights 205 might or might not be available; nor does it represent that it has 206 made any independent effort to identify any such rights. Information 207 on the procedures with respect to rights in RFC documents can be 208 found in BCP 78 and BCP 79. 210 Copies of IPR disclosures made to the IETF Secretariat and any 211 assurances of licenses to be made available, or the result of an 212 attempt made to obtain a general license or permission for the use of 213 such proprietary rights by implementers or users of this 214 specification can be obtained from the IETF on-line IPR repository at 215 http://www.ietf.org/ipr. 217 The IETF invites any interested party to bring to its attention any 218 copyrights, patents or patent applications, or other proprietary 219 rights that may cover technology that may be required to implement 220 this standard. Please address the information to the IETF at 221 ietf-ipr@ietf.org. 223 Acknowledgment 225 Funding for the RFC Editor function is provided by the IETF 226 Administrative Support Activity (IASA).