Format for RFCs in the IAB Stream ---------------------------------- Below is general guidance about the format for IAB stream documents, based on IAB discussion that took place May 2012 in response to questions from the RFC Editor. - Regarding use of "Ed.", the header of the I-D determines the header of the RFC. The IAB is determining author listings on a case-by-case basis. For example, the following are both possible: Internet Architecture Board (IAB) D. Thaler, Ed. Request for Comments: 5902 L. Zhang, Ed. Category: Informational G. Lebovitz, Ed. ISSN: 2070-1721 July 2010 Internet Architecture Board (IAB) D. Thaler Request for Comments: 5902 L. Zhang Category: Informational G. Lebovitz ISSN: 2070-1721 July 2010 Each author's name SHOULD be listed without an organization. - The IAB is no longer to be listed in the Authors' Addresses Section. The document is identified as an IAB stream document via the header as indicated above. - Per RFC 5741, Section 3.2.2, the following boilerplate appears in the second paragraph of the "Status of This Memo" section: This document is a product of the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. - There are two types of IAB documents: IAB consensus documents, and workshop reports. IAB consensus documents ----------------------- The following boilerplate is to appear at the end of the second paragraph of the Status of this Memo section, following the boilerplate quoted above: It represents the consensus of the Internet Architecture Board (IAB). IAB consensus documents also include a list of IAB members that were part of the IAB when the document was approved, in a section entitled "IAB Members at the Time of Approval". Workshop Reports ---------------- The following boilerplate paragraph is to appear at the end of the abstract: Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB views and positions. The following boilerplate paragraph SHOULD appear in the introduction: The Internet Architecture Board (IAB) holds occasional workshops designed to consider long-term issues and strategies for the Internet, and to suggest future directions for the Internet architecture. This long-term planning function of the IAB is complementary to the ongoing engineering efforts performed by working groups of the Internet Engineering Task Force (IETF), under the leadership of the Internet Engineering Steering Group (IESG) and area directorates. Workshop reports are to contain an appendix listing the workshop participants. ---------------------------------- Last edited 13 June 2012.