idnits 2.17.1 draft-iab-rfc1601bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 8 longer pages, the longest (page 1) being 64 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. -- The abstract seems to indicate that this document obsoletes RFC1601, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (January 2000) is 8858 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) ** Obsolete normative reference: RFC 1601 (Obsoleted by RFC 2850) ** Obsolete normative reference: RFC 2282 (ref. 'BCP 10') (Obsoleted by RFC 2727) Summary: 10 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IAB B. Carpenter 2 Internet Draft 3 January 2000 5 Charter of the Internet Architecture Board (IAB) 7 Copyright Notice 9 Placeholder for ISOC copyright 11 Abstract 13 draft-iab-rfc1601bis-02.txt 15 This memo documents the composition, selection, roles, and 16 organization of the Internet Architecture Board. It replaces 17 RFC 1601. 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Table of Contents: 42 Status of this Memo.............................................1 43 1. IAB Membership...............................................3 44 1.1 Selection of voting IAB members............................3 45 1.2 Ex-Officio and Liaison members..............................3 46 2. The Role of the IAB.........................................3 47 2.1 Architectural oversight in more detail......................5 48 3. IAB Organization.............................................5 49 3.1 IAB chair...................................................5 50 3.2 Executive Director..........................................6 51 3.3 Selection of the IRTF chair.................................6 52 3.4 Liaisons within the IETF....................................6 53 3.5 Voting rule.................................................6 54 3.6 Openness and confidentiality................................7 55 Security Considerations.........................................7 56 Summary of Changes from RFC 1601................................7 57 References......................................................7 58 Full Copyright Statement........................................7 59 Author's Address................................................8 61 1. IAB Membership 63 The Internet Architecture Board (IAB) shall consist of thirteen 64 voting members, composed of the chair of the Internet Engineering 65 Task Force (IETF), and of twelve full members. The IETF chair, who 66 is also the chair of the Internet Engineering Steering Group (IESG), 67 may vote on all official IAB actions except the approval of IESG 68 members and appeals against IESG decisions. Ex-officio and liaison 69 members of the IAB may also attend IAB meetings but shall have no 70 vote on official actions. 72 In the event that the number of voting members temporarily falls 73 below thirteen for any reason, the IAB may function as normal subject 74 to the voting rule of Section 3.5. 76 Members of the IAB shall serve as individuals, and not as 77 representatives of any company, agency, or other organization. 78 Members of the IAB shall owe no fiduciary duty of loyalty or care to 79 IAB, IETF, IRTF or IESG. 81 1.1 Selection of voting IAB members 83 Voting IAB members, including the IETF chair, are selected and 84 appointed according to the procedures defined in [BCP 10] . Normally, 85 six full members are appointed each year to sit for two years, and 86 the IETF chair is appointed every two years. 88 There is no limit to the number of terms that a member of the IAB may 89 serve, subject to the process defined by [BCP 10]. 91 1.2 Ex-Officio and Liaison members 93 Ex-officio and liaison members of the IAB have no vote but 94 participate in IAB discussions. However, an ex-officio position 95 may be held by a voting member, who does not thereby lose his or her 96 vote. Liaison positions may not be held by a voting member. 98 The chair of the Internet Research Task Force (IRTF) is an ex-officio 99 member of the IAB. The IAB has an Executive Director who is an ex- 100 officio member of the IAB. 102 The Internet Society, the RFC Editor, the IANA and the IESG each 103 appoints a liaison member to the IAB. 105 2. The Role of the IAB 107 The IAB is chartered both as a committee of the IETF and as an 108 advisory body of the Internet Society. Its responsibilities include: 110 (a) IESG Appointment 112 The IAB appoints a new IETF chair and all other IESG candidates, from 113 a list provided by the IETF nominating committee established under 114 [BCP 10]. 116 (b) Architectural Oversight 118 The IAB provides oversight of the architecture for the protocols and 119 procedures used by the Internet. This point is expanded in Section 120 2.1 below. 122 (c) Standards Process Oversight and Appeal 124 The IAB provides oversight of the process used to create Internet 125 Standards [BCP 9]. 127 The IAB serves as an appeal board for complaints of improper 128 execution of the standards process, with powers defined in [BCP 9]. 130 (d) RFC Series and IANA 132 The RFC Editor executes editorial management and publication of the 133 IETF "Request for Comment" (RFC) document series, which is the 134 permanent document repository of the IETF. The RFC series 135 constitutes the archival publication channel for Internet Standards 136 and for other contributions by the Internet research and engineering 137 community. RFCs are available free of charge to anyone via the 138 Internet. The RFC Editor operates under the responsibility of the 139 IAB. 141 The Internet Assigned Numbers Authority (IANA) administers various 142 protocol parameters used by IETF protocols, delegating this 143 administration as appropriate. The IANA operates with the advice and 144 consent of the IAB on IETF technical matters, taking technical direction 145 from the IESG. 147 (e) ISOC Liaison 149 The IAB acts as a source of advice and guidance to the Board of 150 Trustees and Officers of the Internet Society concerning technical, 151 architectural, procedural, and (where appropriate) policy matters 152 pertaining to the Internet and its enabling technologies. If 153 necessary the IAB may convene panels of knowledgeable people, hold 154 hearings, and otherwise pursue the investigation of specific 155 questions or topics presented to it by the Internet Society. 157 (f) External Liaison 159 The IAB acts as representative of the interests of the IETF and the 160 Internet Society in technical liaison relationships with other 161 organizations concerned with standards and other technical and 162 organizational issues relevant to the world-wide Internet. Liaisons 163 are kept as informal as possible and must be of demonstrable value in 164 improving the quality of IETF specifications. Individual members of 165 the IETF are appointed as liaisons to other organizations by the IAB 166 or IESG as appropriate. 168 2.1 Architectural oversight in more detail 170 A major role of the IAB is long range planning and coordination 171 between different areas of IETF activity. The IAB, both collectively 172 and on an individual basis, is expected to pay attention to important 173 long-term issues in the Internet, and to make sure that these issues 174 are brought to the attention of the group(s) that are in a position 175 to address them. It is also expected to play a role in assuring that 176 the people responsible for evolving the Internet and its technology 177 are aware of the essential elements of the Internet architecture. 179 IAB members pay special attention to emerging activities in the IETF 180 and to "Birds of a Feather" sessions at IETF meetings. The IAB 181 assists the IESG in evaluating such activities and in determining 182 whether an IETF or an IRTF group is more appropriate. When a new 183 IETF working group is proposed, the IESG will forward a preliminary 184 version of the charter to the IAB for review of architectural 185 consistency and integrity. The IAB shall review these proposed 186 charters and give feedback to the IESG as appropriate. 188 Pursuant to the architectural oversight function, the IAB sponsors 189 and organizes the Internet Research Task Force (IRTF) [BCP 8]. The 190 IAB reviews proposed IRTF groups. 192 The IAB will convene invitational workshops to perform in-depth 193 reviews of particular architectural issues. Such reviews may include 194 consideration of relevant IETF and IRTF activities, and of work in 195 other organizations, and for this purpose the workshop may invite 196 presentations by qualified parties on the design goals and decisions, 197 technology choices, and other pertinent aspects of these activities. 198 The results of such a review will be a report which may give advice 199 to the IETF community and the IESG. 201 The IAB may organize ad hoc bodies of independent technical experts 202 to adjudicate technical disputes. 204 3. IAB Organization 206 3.1 IAB chair 208 The members of the IAB shall select one of its full members to serve 209 as the chair of the IAB, with all of the duties and responsibilities 210 normally associated with such a position. The term of the IAB chair 211 shall be one year, with no restriction on renewal. The chair of the 212 IAB may be removed at any time by the affirmative vote of two-thirds 213 of the members of the IAB, or as a result of his or her departure 214 from the IAB. 216 The chair of the IAB shall have the authority to manage the 217 activities and meetings of the IAB. 219 3.2 Executive Director 221 The chair of the IAB shall have the authority to appoint an honorary 222 Executive Director (ExecD) for a one-year renewable term, and to 223 remove him or her. The ExecD shall administer the internal operation 224 of the IAB, e.g., organization of meetings and reporting of their 225 results. 227 The ExecD is an ex-officio member as defined in Section 1.2. 229 3.3 Selection of the IRTF chair 231 The IAB shall have the authority to appoint the chair of the Internet 232 Research Task Force (IRTF) for a two-year renewable term, and to 233 remove him or her. The IRTF chair shall be responsible for the 234 management and organization of the IRTF according to [BCP 8]. 236 The IRTF chair is an ex-officio member as defined in Section 1.2. 238 3.4 Liaisons within the IETF 240 The chair of the IAB and another voting IAB member (other than the 241 IETF chair), to be selected by the IAB, shall serve as liaisons to 242 the IESG. In addition, the IESG will appoint one of its members 243 (other than the IETF chair) to serve as a liaison to the IAB. The 244 IESG liaison may attend IAB meetings but shall have no vote. 246 3.5 Voting rule 248 The IAB attempts to reach all decisions by unanimous consensus. In 249 the event that a vote is required, a motion passes if there are not 250 fewer than seven votes in favour and not more than two against. 252 IAB votes may be taken by face to face meeting, teleconference, 253 Internet communication, or any combination of the above. 255 3.6 Openness and confidentiality 257 The IAB publishes minutes of all its meetings on the Internet, and 258 conducts an open meeting at every IETF meeting. It publishes all its 259 findings as RFCs, Internet Drafts or messages to the IETF mailing 260 list. However, discussion of personnel matters and possibly legal and 261 financial matters may sometimes be required to be kept confidential. 263 Specifically, the IAB makes use of the second level domain iab.org 264 and the URL http://www.iab.org to publish information. 266 Security Considerations 268 This memo does not raise any known security threats. 270 Summary of Changes from RFC 1601 272 This document replaces [RFC 1601]. The principal change is the 273 removal of material now covered in [BCP 8], [BCP 9] and [BCP 10], 274 with many consequent editorial changes. Additional changes are: 276 - description of a voting rule 277 - note on openness and confidentiality 278 - addition of liaison seats for the Internet Society and the IANA 279 - revised text concerning the IANA and the RFC Editor 280 - clarifications following legal review 282 References 284 [RFC 1601] 286 [BCP 8] RFC 2014 or its replacement 288 [BCP 9] RFC 2026 or its replacement 290 [BCP 10] RFC 2282 or its replacement 292 Full Copyright Statement 294 PLACEHOLDER for full ISOC Copyright Statement if needed. 296 Author's Address 298 Brian E. Carpenter 299 IBM 300 c/o iCAIR 301 Suite 150 302 1890 Maple Avenue 303 Evanston IL 60201 304 USA 306 email: brian@icair.org