| 1 |
<pre>Network Working Group R. Hovey |
| 2 |
Request for Comments: 2028 Digital Equipment Corporation |
| 3 |
BCP: 11 S. Bradner |
| 4 |
Category: Best Current Practice Harvard University |
| 5 |
October 1996 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">The Organizations Involved in the IETF Standards Process</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This document specifies an Internet Best Current Practices for the |
| 13 |
Internet Community, and requests discussion and suggestions for |
| 14 |
improvements. Distribution of this memo is unlimited. |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
This document describes the individuals and organizations involved in |
| 19 |
the IETF. This includes descriptions of the IESG, the IETF Working |
| 20 |
Groups and the relationship between the IETF and the Internet |
| 21 |
Society. |
| 22 |
|
| 23 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Documents controlling the process</span> |
| 24 |
|
| 25 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> The IETF Standards Process</span> |
| 26 |
|
| 27 |
The process used by the Internet community for the standardization of |
| 28 |
protocols and procedures is described in [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>]. That document defines |
| 29 |
the stages in the standardization process, the requirements for |
| 30 |
moving a document between stages and the types of documents used |
| 31 |
during this process. It also addresses the intellectual property |
| 32 |
rights and copyright issues associated with the standards process. |
| 33 |
|
| 34 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Key individuals in the Process</span> |
| 35 |
|
| 36 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> The Request for Comments Editor</span> |
| 37 |
|
| 38 |
The RFC publication series [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>] is managed by an Editor (which may in |
| 39 |
practice be one or more individuals) responsible both for the |
| 40 |
mechanics of RFC publication and for upholding the traditionally high |
| 41 |
technical and editorial standards of the RFC series. |
| 42 |
|
| 43 |
The functions of the RFC Editor are performed by one or more |
| 44 |
individuals or organizations selected in accordance with the |
| 45 |
procedures defined by the RFC Editor charter [<a href="#ref-G">G</a>]. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> The Working Group Chair</span> |
| 58 |
|
| 59 |
Each IETF Working Group is headed by a chair (or by co-chairs) with |
| 60 |
the responsibility for directing the group's activities, presiding |
| 61 |
over the group's meetings, and ensuring that the commitments of the |
| 62 |
group with respect to its role in the Internet standards process are |
| 63 |
met. In particular, the WG chair is the formal point of contact |
| 64 |
between the WG and the IESG, via the Area Director of the area to |
| 65 |
which the WG is assigned. |
| 66 |
|
| 67 |
The details on the selection and responsibilites of an IETF Working |
| 68 |
Group chair can be found in [<a href="#ref-A" title=""IETF Working Group Guidelines and Procedures"">A</a>]. |
| 69 |
|
| 70 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> The Document Editor</span> |
| 71 |
|
| 72 |
Most IETF Working Groups focus their efforts on a document, or set of |
| 73 |
documents, that capture the results of the group's work. A Working |
| 74 |
Group generally designates a person or persons to serve as the Editor |
| 75 |
for a particular document. The Document Editor is responsible for |
| 76 |
ensuring that the contents of the document accurately reflect the |
| 77 |
decisions that have been made by the working group. |
| 78 |
|
| 79 |
As a general practice, the Working Group Chair and Document Editor |
| 80 |
positions are filled by different individuals to help ensure that the |
| 81 |
resulting documents accurately reflect the consensus of the Working |
| 82 |
Group and that all processes are followed. |
| 83 |
|
| 84 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Key organizations in the Process</span> |
| 85 |
|
| 86 |
The following organizations and organizational roles are involved in |
| 87 |
the Internet standards process. Contact information is contained in |
| 88 |
<a href="#appendix-A">Appendix A</a>. |
| 89 |
|
| 90 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Internet Engineering Task Force</span> |
| 91 |
|
| 92 |
The Internet Engineering Task Force (IETF) is an open international |
| 93 |
community of network designers, operators, vendors and researchers |
| 94 |
concerned with the evolution of the Internet architecture and the |
| 95 |
smooth operation of the Internet. It is the principal body engaged |
| 96 |
in the development of new Internet Standard specifications. |
| 97 |
|
| 98 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> IETF Working Groups</span> |
| 99 |
|
| 100 |
The technical work of the IETF is done in its Working Groups, which |
| 101 |
are organized by topics into several Areas (e.g., routing, network |
| 102 |
management, security, etc.) under the coordination of Area Directors. |
| 103 |
Working Groups typically have a narrow focus and a lifetime bounded |
| 104 |
by completion of a specific task. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 111 |
|
| 112 |
|
| 113 |
For all purposes relevant to the Internet Standards development |
| 114 |
process, membership in the IETF and its Working Groups is defined to |
| 115 |
be established solely and entirely by individual participation in |
| 116 |
IETF and Working Group activities. Participation in the IETF and its |
| 117 |
Working Groups is by individual technical contributors rather than by |
| 118 |
formal representatives of organizations. |
| 119 |
|
| 120 |
Anyone with the time and interest to do so is entitled and urged to |
| 121 |
participate actively in one or more IETF Working Groups and to attend |
| 122 |
IETF meetings which are held three times a year. In most cases |
| 123 |
active Working Group participation is possible through electronic |
| 124 |
mail alone. Internet video conferencing is also being used to allow |
| 125 |
for remote participation. |
| 126 |
|
| 127 |
To ensure a fair and open process, participants in the IETF and its |
| 128 |
Working Groups must be able to disclose, and must disclose to the |
| 129 |
Working Group chairs any relevant current or pending intellectual |
| 130 |
property rights that are reasonably and personally known to the |
| 131 |
participant if they participate in discussions about a specific |
| 132 |
technology. |
| 133 |
|
| 134 |
New Working Groups are established within the IETF by explicit |
| 135 |
charter. The guidelines and procedures for the formation and |
| 136 |
operation of IETF working groups are described in detail in [<a href="#ref-A" title=""IETF Working Group Guidelines and Procedures"">A</a>]. |
| 137 |
|
| 138 |
A Working Group is managed by one or more Working Group chairs (see |
| 139 |
<a href="#section-2.2">section 2.2</a>). It may also include editors of documents that record |
| 140 |
the group's work (see <a href="#section-2.3">section 2.3</a>). Further details of Working Group |
| 141 |
operation are contained in [<a href="#ref-A" title=""IETF Working Group Guidelines and Procedures"">A</a>] |
| 142 |
|
| 143 |
IETF Working Groups display a spirit of cooperation as well as a high |
| 144 |
degree of technical maturity; IETF participants recognize that the |
| 145 |
greatest benefit for all members of the Internet community results |
| 146 |
from cooperative development of technically superior protocols and |
| 147 |
services. |
| 148 |
|
| 149 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> IETF Secretariat</span> |
| 150 |
|
| 151 |
The administrative functions necessary to support the activities of |
| 152 |
the IETF are performed by a Secretariat consisting of the IETF |
| 153 |
Executive Director and his or her staff. The IETF Executive Director |
| 154 |
is the formal point of contact for matters concerning any and all |
| 155 |
aspects of the Internet standards process, and is responsible for |
| 156 |
maintaining the formal public record of the Internet standards |
| 157 |
process [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>]. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Internet Society</span> |
| 170 |
|
| 171 |
The Internet Society (ISOC) is an international organization |
| 172 |
concerned with the growth and evolution of the worldwide Internet and |
| 173 |
with the social, political, and technical issues that arise from its |
| 174 |
use. The ISOC is an organization with individual and organizational |
| 175 |
members. The ISOC is managed by a Board of Trustees elected by the |
| 176 |
worldwide individual membership. |
| 177 |
|
| 178 |
Internet standardization is an organized activity of the ISOC, with |
| 179 |
the Board of Trustees being responsible for ratifying the procedures |
| 180 |
and rules of the Internet standards process [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>]. |
| 181 |
|
| 182 |
The way in which the members of the ISOC Board of Trustees are |
| 183 |
selected, and other matters concerning the operation of the Internet |
| 184 |
Society, are described in the ISOC By Laws [<a href="#ref-C">C</a>]. |
| 185 |
|
| 186 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Internet Engineering Steering Group</span> |
| 187 |
|
| 188 |
|
| 189 |
The Internet Engineering Steering Group (IESG) is the part of the |
| 190 |
Internet Society responsible for the management of the IETF technical |
| 191 |
activities. It administers the Internet Standards process according |
| 192 |
to the rules and procedures defined in [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>]. The IESG is responsible |
| 193 |
for the actions associated with the progression of technical |
| 194 |
specification along the "standards track" including the initial |
| 195 |
approval of new Working Groups and the final approval of |
| 196 |
specifications as Internet Standards. The IESG is composed of the |
| 197 |
IETF Area Directors and the chair of the IETF, who also serves as the |
| 198 |
chair of the IESG. |
| 199 |
|
| 200 |
The members of the IESG are nominated by a nominations committee (the |
| 201 |
Nomcom), and are approved by the IAB. See [<a href="#ref-E" title=""IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"">E</a>] for a detailed |
| 202 |
description of the Nomcom procedures. Other matters concerning its |
| 203 |
organization and operation, are described in the IESG charter [does |
| 204 |
not yet exist]. |
| 205 |
|
| 206 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> Internet Architecture Board</span> |
| 207 |
|
| 208 |
The Internet Architecture Board (IAB) is chartered by the Internet |
| 209 |
Society Trustees to provide oversight of the architecture of the |
| 210 |
Internet and its protocols. The IAB appoints the IETF chair and is |
| 211 |
responsible for approving other IESG candidates put forward by the |
| 212 |
IETF nominating committee. The IAB is also responsible for reviewing |
| 213 |
and approving the charters of new Working Groups that are proposed |
| 214 |
for the IETF. |
| 215 |
|
| 216 |
The IAB provides oversight of the process used to create Internet |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 223 |
|
| 224 |
|
| 225 |
Standards and serves as an appeal board for complaints of improper |
| 226 |
execution of the standards process [<a href="#ref-B" title=""The Internet Standards Process -- Revision 3"">B</a>]. In general it acts as source |
| 227 |
of advice to the IETF, the ISOC and the ISOC Board of Trustees |
| 228 |
concerning technical, architectural, procedural, and policy matters |
| 229 |
pertaining to the Internet and its enabling technologies. |
| 230 |
|
| 231 |
The members of the IAB are nominated by a nominations committee (the |
| 232 |
Nomcom), and are approved by the ISOC board. See [<a href="#ref-E" title=""IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"">E</a>] for a detailed |
| 233 |
description of the Nomcom procedures. The membership of the IAB |
| 234 |
consists of members selected by the Nomcom process and the IETF chair |
| 235 |
sitting as a ex-officio member. Other matters concerning its |
| 236 |
organization and operation, are described in the IAB charter [<a href="#ref-D" title=""Charter of the Internet Architecture Board (IAB)"">D</a>]. |
| 237 |
|
| 238 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a> Internet Assigned Numbers Authority</span> |
| 239 |
|
| 240 |
Many protocol specifications include numbers, keywords, and other |
| 241 |
parameters that must be uniquely assigned. Examples include version |
| 242 |
numbers, protocol numbers, port numbers, and MIB numbers. The |
| 243 |
Internet Assigned Numbers Authority (IANA) is responsible for |
| 244 |
assigning the values of these protocol parameters for the Internet. |
| 245 |
The IANA publishes tables of all currently assigned numbers and |
| 246 |
parameters in RFCs entitled "Assigned Numbers" [<a href="#ref-E" title=""IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees"">E</a>]. The IANA |
| 247 |
functions as the "top of the pyramid" for DNS and Internet Address |
| 248 |
assignment establishing policies for these functions. |
| 249 |
|
| 250 |
The functions of the IANA are performed by one or more individuals or |
| 251 |
organizations selected in accordance with the procedures defined by |
| 252 |
the IANA charter [<a href="#ref-F">F</a>]. |
| 253 |
|
| 254 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a> Internet Research Task Force</span> |
| 255 |
|
| 256 |
The Internet Research Task Force (IRTF) is not directly involved in |
| 257 |
the Internet standards process. It investigates topics considered to |
| 258 |
be too uncertain, too advanced, or insufficiently well-understood to |
| 259 |
be the subject of Internet standardization. When an IRTF activity |
| 260 |
generates a specification that is sufficiently stable to be |
| 261 |
considered for Internet standardization, the specification is |
| 262 |
processed through the IETF using the rules in this document. |
| 263 |
|
| 264 |
The IRTF is composed of individual Working Groups, but its structure |
| 265 |
and mode of operation is much less formal than that of the IETF, due |
| 266 |
in part to the fact that it does not participate directly in the |
| 267 |
Internet standards process. The organization and program of work of |
| 268 |
the IRTF is overseen by the Internet Research Steering Group (IRSG), |
| 269 |
which consists of the chairs of the IRTF Working Groups. Details of |
| 270 |
the organization and operation of the IRTF and its Working Groups may |
| 271 |
be found in [<a href="#ref-H" title="RFC 2014">H</a>]. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 282 |
|
| 283 |
Security is not addressed in this memo. |
| 284 |
|
| 285 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span> |
| 286 |
|
| 287 |
[<a id="ref-A">A</a>] Huizer,E. and D. Crocker, "IETF Working Group Guidelines and |
| 288 |
Procedures", <a href="./rfc1603">RFC 1603</a>, March 1994. |
| 289 |
|
| 290 |
[<a id="ref-B">B</a>] Bradner, S., Editor, "The Internet Standards Process -- Revision |
| 291 |
3", <a href="./rfc2026">RFC 2026</a>, October 1996. |
| 292 |
|
| 293 |
[<a id="ref-C">C</a>] By - Laws for the Internet Society, as amended: |
| 294 |
gopher://info.isoc.org/00/isoc/basic_docs/bylaws.txt |
| 295 |
|
| 296 |
[<a id="ref-D">D</a>] Huitema, C. and the IAB, "Charter of the Internet Architecture |
| 297 |
Board (IAB)", <a href="./rfc1601">RFC 1601</a>, March 1994. |
| 298 |
|
| 299 |
[<a id="ref-E">E</a>] Galvin, J (Ed.), "IAB and IESG Selection, Confirmation, and |
| 300 |
Recall Process: Operation of the Nominating and Recall Committees", |
| 301 |
<a href="./rfc2027">RFC 2027</a>, October 1996. |
| 302 |
|
| 303 |
[<a id="ref-F">F</a>] IANA Charter, Work in Progress. |
| 304 |
|
| 305 |
[<a id="ref-G">G</a>] RFC Editor Charter, Work in Progress. |
| 306 |
|
| 307 |
[<a id="ref-H">H</a>] IRTF Charter, <a href="./rfc2014">RFC 2014</a>, October 1996. |
| 308 |
|
| 309 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Authors' Addresses:</span> |
| 310 |
|
| 311 |
Richard Hovey |
| 312 |
Digital Equipment Corporation |
| 313 |
1401 H Street NW |
| 314 |
Washington DC 20005 |
| 315 |
|
| 316 |
Phone: +1 202 383 5615 |
| 317 |
EMail: [email protected] |
| 318 |
|
| 319 |
Scott Bradner |
| 320 |
Harvard University |
| 321 |
1350 Mass Ave. Rm 813 |
| 322 |
Cambridge MA 02138 |
| 323 |
|
| 324 |
Phone: +1 617 495 3864 |
| 325 |
EMail: [email protected] |
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Hovey & Bradner Best Current Practice [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2028">RFC 2028</a> IETF Organizations October 1996</span> |
| 335 |
|
| 336 |
|
| 337 |
Appendix A - Contact Information |
| 338 |
|
| 339 |
IETF - [email protected], <a href="http://www.ietf.org">http://www.ietf.org</a> |
| 340 |
|
| 341 |
IESG - [email protected], <a href="http://www.ietf.org/iesg.html">http://www.ietf.org/iesg.html</a> |
| 342 |
|
| 343 |
IAB - [email protected], <a href="http://www.iab.org/iab">http://www.iab.org/iab</a> |
| 344 |
|
| 345 |
RFC Editor - [email protected], <a href="http://www.isi.edu/rfc-editor">http://www.isi.edu/rfc-editor</a> |
| 346 |
|
| 347 |
IANA - [email protected], <a href="http://www.iana.org/iana/">http://www.iana.org/iana/</a> |
| 348 |
|
| 349 |
|
| 350 |
|
| 351 |
|
| 352 |
|
| 353 |
|
| 354 |
|
| 355 |
|
| 356 |
|
| 357 |
|
| 358 |
|
| 359 |
|
| 360 |
|
| 361 |
|
| 362 |
|
| 363 |
|
| 364 |
|
| 365 |
|
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
Hovey & Bradner Best Current Practice [Page 7] |
| 389 |
</pre> |