<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>

<!--
     ASCII to XML transformation by Invisible Worlds, Inc.
     http://invisible.net/
     Last transformation: 03-Feb-1999, 02:08:20

     Cannonical version of this document is at:
     http://info.internet.isi.edu/in-notes/rfc/files/rfc2028.txt

     Implementors should verify all content with
     cannonical version.  Failure to do so may result in
     protocol failures.
-->

<rfc number="2028"
     category="bcp"
     seriesNo="11">
<front>
<title abbrev="IETF Organizations">The Organizations Involved in the IETF Standards Process</title>
<author initials="R." surname="Hovey" fullname="Richard Hovey">
<organization>Digital Equipment Corporation</organization>
<address>
<postal>
<street>1401 H Street NW</street>
<street>Washington DC 20005</street>
</postal>
<phone>+1 202 383 5615</phone>
<email>hovey@wnpv01.enet.dec.com</email>
</address>
</author>
<author initials="S." surname="Bradner" fullname="Scott Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass Ave. Rm 813</street>
<street>Cambridge MA 02138</street>
</postal>
<phone>+1 617 495 3864</phone>
<email>sob@harvard.edu</email>
</address>
</author>
<date month="October" year="1996"/>
<area>General</area>
<keyword>Internet Engineering Task Force</keyword>
<keyword>standards process</keyword>
<abstract>
<t>
   This document describes the individuals and organizations involved in
   the IETF.  This includes descriptions of the IESG, the IETF Working
   Groups and the relationship between the IETF and the Internet
   Society.
</t>
</abstract>
</front>
<middle>
<!-- RFC original section: (1.) -->
<section title="Documents controlling the process">
<t>
</t>
<!-- RFC original section: (1.1) -->
<section title="The IETF Standards Process">
<t>
   The process used by the Internet community for the standardization of
   protocols and procedures is described in <xref target="_XREF_B"/>.  That document defines
   the stages in the standardization process, the requirements for
   moving a document between stages and the types of documents used
   during this process.  It also addresses the intellectual property
   rights and copyright issues associated with the standards process.
</t>
</section>
</section>
<!-- RFC original section: (2.) -->
<section title="Key individuals in the Process">
<t>
</t>
<!-- RFC original section: (2.1) -->
<section title="The Request for Comments Editor">
<t>
   The RFC publication series <xref target="_XREF_B"/> is managed by an Editor (which may in
   practice be one or more individuals) responsible both for the
   mechanics of RFC publication and for upholding the traditionally high
   technical and editorial standards of the RFC series.
</t>
<t>
   The functions of the RFC Editor are performed by one or more
   individuals or organizations selected in accordance with the
   procedures defined by the RFC Editor charter <xref target="_XREF_G"/>.
</t>
</section>
<!-- RFC original section: (2.2) -->
<section title="The Working Group Chair">
<t>
   Each IETF Working Group is headed by a chair (or by co-chairs) with
   the responsibility for directing the group&apos;s activities, presiding
   over the group&apos;s meetings, and ensuring that the commitments of the
   group with respect to its role in the Internet standards process are
   met. In particular, the WG chair is the formal point of contact
   between the WG and the IESG, via the Area Director of the area to
   which the WG is assigned.
</t>
<t>
   The details on the selection and responsibilites of an IETF Working
   Group chair can be found in <xref target="_XREF_A"/>.
</t>
</section>
<!-- RFC original section: (2.3) -->
<section title="The Document Editor">
<t>
   Most IETF Working Groups focus their efforts on a document, or set of
   documents, that capture the results of the group&apos;s work.  A Working
   Group generally designates a person or persons to serve as the Editor
   for a particular document.  The Document Editor is responsible for
   ensuring that the contents of the document accurately reflect the
   decisions that have been made by the working group.
</t>
<t>
   As a general practice, the Working Group Chair and Document Editor
   positions are filled by different individuals to help ensure that the
   resulting documents accurately reflect the consensus of the Working
   Group and that all processes are followed.
</t>
</section>
</section>
<!-- RFC original section: (3.) -->
<section title="Key organizations in the Process">
<t>
   The following organizations and organizational roles are involved in
   the Internet standards process.  Contact information is contained in
   Appendix A.
</t>
<!-- RFC original section: (3.1) -->
<section title="Internet Engineering Task Force">
<t>
   The Internet Engineering Task Force (IETF) is an open international
   community of network designers, operators, vendors and researchers
   concerned with the evolution of the Internet architecture and the
   smooth operation of the Internet.  It is the principal body engaged
   in the development of new Internet Standard specifications.
</t>
</section>
<!-- RFC original section: (3.2) -->
<section title="IETF Working Groups">
<t>
   The technical work of the IETF is done in its Working Groups, which
   are organized by topics into several Areas (e.g., routing, network
   management, security, etc.) under the coordination of Area Directors.
   Working Groups typically have a narrow focus and a lifetime bounded
   by completion of a specific task.
</t>
<t>
   For all purposes relevant to the Internet Standards development
   process, membership in the IETF and its Working Groups is defined to
   be established solely and entirely by individual participation in
   IETF and Working Group activities. Participation in the IETF and its
   Working Groups is by individual technical contributors rather than by
   formal representatives of organizations.
</t>
<t>
   Anyone with the time and interest to do so is entitled and urged to
   participate actively in one or more IETF Working Groups and to attend
   IETF meetings which are held three times a year.  In most cases
   active Working Group participation is possible through electronic
   mail alone.  Internet video conferencing is also being used to allow
   for remote participation.
</t>
<t>
   To ensure a fair and open process, participants in the IETF and its
   Working Groups must be able to disclose, and must disclose to the
   Working Group chairs any relevant current or pending intellectual
   property rights that are reasonably and personally known to the
   participant if they participate in discussions about a specific
   technology.
</t>
<t>
   New Working Groups are established within the IETF by explicit
   charter.  The guidelines and procedures for the formation and
   operation of IETF working groups are described in detail in <xref target="_XREF_A"/>.
</t>
<t>
   A Working Group is managed by one or more Working Group chairs (see
   section 2.2).  It may also include editors of documents that record
   the group&apos;s work (see section 2.3). Further details of Working Group
   operation are contained in <xref target="_XREF_A"/>
</t>
<t>
   IETF Working Groups display a spirit of cooperation as well as a high
   degree of technical maturity;  IETF participants recognize that the
   greatest benefit for all members of the Internet community results
   from cooperative development of technically superior protocols and
   services.
</t>
</section>
<!-- RFC original section: (3.3) -->
<section title="IETF Secretariat">
<t>
   The administrative functions necessary to support the activities of
   the IETF are performed by a Secretariat consisting of the IETF
   Executive Director and his or her staff. The IETF Executive Director
   is the formal point of contact for matters concerning any and all
   aspects of the Internet standards process, and is responsible for
   maintaining the formal public record of the Internet standards
   process <xref target="_XREF_B"/>.
</t>
</section>
<!-- RFC original section: (3.4) -->
<section title="Internet Society">
<t>
   The Internet Society (ISOC) is an international organization
   concerned with the growth and evolution of the worldwide Internet and
   with the social, political, and technical issues that arise from its
   use.  The ISOC is an organization with individual and organizational
   members.  The ISOC is managed by a Board of Trustees elected by the
   worldwide individual membership.
</t>
<t>
   Internet standardization is an organized activity of the ISOC, with
   the Board of Trustees being responsible for ratifying the procedures
   and rules of the Internet standards process <xref target="_XREF_B"/>.
</t>
<t>
   The way in which the members of the ISOC Board of Trustees are
   selected, and other matters concerning the operation of the Internet
   Society, are described in the ISOC By Laws <xref target="_XREF_C"/>.
</t>
</section>
<!-- RFC original section: (3.5) -->
<section title="Internet Engineering Steering Group">
<t>
   The Internet Engineering Steering Group (IESG) is the part of the
   Internet Society responsible for the management of the IETF technical
   activities.  It administers the Internet Standards process according
   to the rules and procedures defined in <xref target="_XREF_B"/>.  The IESG is responsible
   for the actions associated with the progression of technical
   specification along the &quot;standards track&quot; including the initial
   approval of new Working Groups and the final approval of
   specifications as Internet Standards.  The IESG is composed of the
   IETF Area Directors and the chair of the IETF, who also serves as the
   chair of the IESG.
</t>
<t>
   The members of the IESG are nominated by a nominations committee (the
   Nomcom), and are approved by the IAB.  See <xref target="_XREF_E"/> for a detailed
   description of the Nomcom procedures. Other matters concerning its
   organization and operation, are described in the IESG charter [does
   not yet exist].
</t>
</section>
<!-- RFC original section: (3.6) -->
<section title="Internet Architecture Board">
<t>
   The Internet Architecture Board (IAB) is chartered by the Internet
   Society Trustees to provide oversight of the architecture of the
   Internet and its protocols.  The IAB appoints the IETF chair and is
   responsible for approving other IESG candidates put forward by the
   IETF nominating committee. The IAB is also responsible for reviewing
   and approving the charters of new Working Groups that are proposed
   for the IETF.
</t>
<t>
   The IAB provides oversight of the process used to create Internet
   Standards and serves as an appeal board for complaints of improper
   execution of the standards process <xref target="_XREF_B"/>. In general it acts as source
   of advice to the IETF, the ISOC and the ISOC Board of Trustees
   concerning technical, architectural, procedural, and policy matters
   pertaining to the Internet and its enabling technologies.
</t>
<t>
   The members of the IAB are nominated by a nominations committee (the
   Nomcom), and are approved by the ISOC board.  See <xref target="_XREF_E"/> for a detailed
   description of the Nomcom procedures.  The membership of the IAB
   consists of members selected by the Nomcom process and the IETF chair
   sitting as a ex-officio member.  Other matters concerning its
   organization and operation, are described in the IAB charter <xref target="_XREF_D"/>.
</t>
</section>
<!-- RFC original section: (3.7) -->
<section title="Internet Assigned Numbers Authority">
<t>
   Many protocol specifications include numbers, keywords, and other
   parameters that must be uniquely assigned.  Examples include version
   numbers, protocol numbers, port numbers, and MIB numbers. The
   Internet Assigned Numbers Authority (IANA) is responsible for
   assigning the values of these protocol parameters for the Internet.
   The IANA publishes tables of all currently assigned numbers and
   parameters in RFCs entitled &quot;Assigned Numbers&quot; <xref target="_XREF_E"/>. The IANA
   functions as the &quot;top of the pyramid&quot; for DNS and Internet Address
   assignment establishing policies for these functions.
</t>
<t>
   The functions of the IANA are performed by one or more individuals or
   organizations selected in accordance with the procedures defined by
   the IANA charter <xref target="_XREF_F"/>.
</t>
</section>
<!-- RFC original section: (3.8) -->
<section title="Internet Research Task Force">
<t>
   The Internet Research Task Force (IRTF) is not directly involved in
   the Internet standards process.  It investigates topics considered to
   be too uncertain, too advanced, or insufficiently well-understood to
   be the subject of Internet standardization.  When an IRTF activity
   generates a specification that is sufficiently stable to be
   considered for Internet standardization, the specification is
   processed through the IETF using the rules in this document.
</t>
<t>
   The IRTF is composed of individual Working Groups, but its structure
   and mode of operation is much less formal than that of the IETF, due
   in part to the fact that it does not participate directly in the
   Internet standards process.  The organization and program of work of
   the IRTF is overseen by the Internet Research Steering Group (IRSG),
   which consists of the chairs of the IRTF Working Groups.  Details of
   the organization and operation of the IRTF and its Working Groups may
   be found in [H].
</t>
</section>
</section>
<!-- RFC original section: (4.) -->
<section title="Security Considerations">
<t>
   Security is not addressed in this memo.
</t>
</section>
<!-- RFC original section: (5.) -->
<section title="References (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;References.&quot;
</t>
</section>
<!-- RFC original section: (5.) -->
<section title="Authors&apos; Addresses: (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;Author&apos;s Address.&quot;
</t>
</section>
</middle>
<back>
<!-- BEGIN INCLUDE REFERENCES ** DO NOT REMOVE -->
<references>
<reference anchor="_XREF_A">
<front>
<title abbrev="IETF Working Group Guidelines">IETF Working Group Guidelines and Procedures</title>
<author initials="E." surname="Huizer" fullname="E. Huizer">
<organization/>
</author>
<author initials="D." surname="Crocker" fullname="D. Crocker">
<organization/>
</author>
<date month="March" year="1994"/>
</front>
<seriesInfo>RFC 1603</seriesInfo>
</reference>
<reference anchor="_XREF_B">
<front>
<title abbrev="The Internet Standards Process">The Internet Standards Process -- Revision 3</title>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization/>
</author>
<date month="October" year="1996"/>
</front>
<seriesInfo>RFC 2026</seriesInfo>
</reference>
<reference anchor="_XREF_C">
<front>
<title abbrev="By - Laws for the Internet Society">By - Laws for the Internet Society, as amended: gopher://info.isoc.org/00/isoc/basic_docs/bylaws.txt</title>
<author>
<organization/>
</author>
<date month="" year=""/>
</front>
</reference>
<reference anchor="_XREF_D">
<front>
<title abbrev="the IAB">the IAB, Charter of the Internet  Architecture Board (IAB)</title>
<author initials="C." surname="Huitema" fullname="C. Huitema">
<organization/>
</author>
<date month="March" year="1994"/>
</front>
<seriesInfo>RFC 1601</seriesInfo>
</reference>
<reference anchor="_XREF_E">
<front>
<title abbrev="Galvin">Galvin, J (Ed.), IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees</title>
<author>
<organization/>
</author>
<date month="October" year="1996"/>
</front>
<seriesInfo>RFC 2027</seriesInfo>
</reference>
<reference anchor="_XREF_F">
<front>
<title>IANA Charter, Work in Progress</title>
<author>
<organization/>
</author>
<date month="" year=""/>
</front>
</reference>
<reference anchor="_XREF_G">
<front>
<title>RFC Editor Charter, Work in Progress</title>
<author>
<organization/>
</author>
<date month="" year=""/>
</front>
</reference>
</references>
<!-- END INCLUDE REFERENCES ** DO NOT REMOVE -->
<!-- RFC original section: (Appendix A) -->
<section title="Contact Information">
<t>
   IETF - <eref target="mailto:ietf@ietf.org"/>, <eref target="http://www.ietf.org"/>
</t>
<t>
   IESG - <eref target="mailto:iesg@ietf.org"/>, <eref target="http://www.ietf.org/iesg.html"/>
</t>
<t>
   IAB - <eref target="mailto:iab@ietf.org"/>, <eref target="http://www.iab.org/iab"/>
</t>
<t>
   RFC Editor - <eref target="mailto:rfc-ed@isi.edu"/>, <eref target="http://www.isi.edu/rfc-editor"/>
</t>
<t>
   IANA - <eref target="mailto:iana@iana.org"/>, <eref target="http://www.iana.org/iana/"/>
</t>
</section>
</back>
</rfc>
