| RFC 9281 | Entities in IETF Standards Process | June 2022 |
| Salz | Best Current Practice | [Page] |
This document describes the individuals and organizations involved inthe IETF standards process, as described in BCP 9.It includes brief descriptions of the entities involvedand the role they play in the standards process.¶
The IETF and its structure have undergone many changes since RFC2028 was published in 1996. This document reflects the changed organizationalstructure of the IETF and obsoletes RFC 2028.¶
This memo documents an Internet Best Current Practice.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9281.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The process used by the IETF community for the standardization ofprotocols and procedures is described in BCP 9[IETFPROCS].BCP 9 definesthe stages in the standardization process, the requirements formoving a document between stages, and the types of documents usedduring this process.This document identifies some of the key individual roles and organizationsin that process.¶
This document refers to individual roles in the singular,such as "a document editor."In reality, many roles are filled by more than one person at the sametime.For clarity, this document does not use phrases like "chair (or co-chair)."¶
The following changes have been made, in no particular order:¶
This section describes the individual roles involved in the process.It attempts to list the roles in the order in which they are involvedin the process, without otherwise expressing significance.¶
Most working groups (WGs) focus their efforts on one or more documentsthat capture their work results. The WG chair designates one or more peopleto serve as the editor(s)for a particular document. The editor is responsible forensuring that the contents of the document accurately reflect thedecisions that have been made by the WG.¶
When a document is composed and edited mainly by one or more individuals,they may be referred to as "document authors". The distinction isnot significant for the standards process.This document uses the term "document editor".¶
When a document editor is a chair of the same WG, anotherchair should manage the process around the document. If another chair is notavailable, the WG and AD must monitor the process especially carefully to ensure that theresulting documents accurately reflect the consensus of the WG andthat all processes are followed. This is the collective obligationof all parties involved in the document.¶
Each WG is headed by a chair who hasthe responsibility for facilitating the group's activities, presidingover the group's meetings, and ensuring that the commitments of thegroup with respect to its role in the Internet standards process aremet. In particular, the WG chair is the formal point of contactbetween the WG and the Internet Engineering Steering Group (IESG), via the AD of the area towhich the WG belongs.¶
The details on the selection and responsibilities of a WGchair can be found in[WGPROCS].¶
Each WG is assigned a single responsible area director (AD).The AD canassist the WG chair in assessing consensus and executing process.The AD also reviews documents after the WG has approved them, andwhen satisfied, the ADcoordinates the IESG review and IETF Last Call ofthe document.¶
An AD can also sponsor an Internet-Draft directly, but this is not very common.When this is done, a WG is not involved.¶
Except for the General Area,IETF areas traditionally have multiple ADs.¶
The following organizations and organizational roles are involved inthe Internet standards process.¶
The IETF is an open internationalcommunity of network designers, operators, implementors, researchers,and other interested parties who areconcerned with the evolution of the Internet architecture and thesmooth operation of the Internet. It is the principal body engagedin the development of new Internet Standard specifications and related documents.¶
The technical work of the IETF is done in its WGs, whichare organized by topics into severalareas,each under the coordination of an AD.WGs typically have a narrow focus and a lifetime boundedby completion of specific tasks as defined in their charterand milestones. Some WGs are long-lived and intended to conductongoing maintenance on IETF protocol(s). There are also "dispatch" WGsthat assess where new work in the IETF should be done but donot directly produce standards.¶
For all purposes relevant to the Internet Standards developmentprocess, membership in the IETF and its WGs is defined tobe established solely and entirely by individuals whoparticipate inIETF and WG activities.These individuals do not formally represent any organizations they may be affiliated with,although affiliations are often used for identification.¶
Anyone with the time and interest to do so is entitled and urged toparticipate actively in one or more WGs and to attendIETF meetings, which are usually heldthree times a year[MEETINGS].A WG may also schedule interim meetings (virtual, in-person, or hybrid).These are scheduled and announced to the entire WG.Active WG participation is possible without attendingany in-person meetings.¶
Participants in the IETF and its WGs must discloseany relevant current or pending intellectualproperty rights that are reasonably and personally known to theparticipant if they participate in discussions about a specifictechnology.The full intellectual property policy is defined in[IPRRIGHTS1] and[IPRRIGHTS2].¶
New WGs are established by the IESGand almost always have a specific and explicit charter.The charter can be modified as the WG progresses.The guidelines and procedures for the formation andoperation of WGs are described in detail in[WGPROCS].¶
A WG is managed by a WG chair, as described inSection 2.2. Documents produced by the group have an editor, asdescribed inSection 2.1. Further details of WG operation canbe found in[WGPROCS].¶
WGs ideally display a spirit of cooperation as well as a highdegree of technical maturity; IETF participants recognize that thegreatest benefit for all members of the Internet community resultsfrom cooperative development of technically excellent protocols andservices.¶
The IESG isresponsible for the management of the IETF technicalactivities. It administers the Internet Standards process accordingto the rules and procedures defined in[IETFPROCS]. The IESG is responsiblefor the actions associated with the progression of documentsalong the IETF Stream, including the initialapproval of new WGs, any subsequentrechartering, and the final approval ofdocuments. The IESG is composed of theADs and the IETF Chair. The IETF Chair also chairs the IESG andis the AD for the General Area.The Chair of the Internet Architecture Board (IAB) is an ex officio member of the IESG. Various other bodies have liaisons with the IESG; the full list can be found at<https://www.ietf.org/about/groups/iesg/members/>.¶
All members of the IESG are nominated by a Nominations Committee(colloquially, "NomCom")and are confirmed by the IAB. See[NOMCOM] for a detaileddescription of the NomCom procedures. Other matters concerning theorganization and operation of the NomCom are described in the IESG Charter[IESG].¶
The IAB provides oversight of the architecture of the Internet and itsprotocols. The IAB approves IESG candidates put forward by theNomCom. It also reviews all proposed IETF WG charters.¶
The IAB provides oversight of the standards processand serves as an appeal board for related complaints about improperexecution[IETFPROCS]. In general, it acts as a sourceof advice abouttechnical, architectural, procedural, and policy matterspertaining to the Internet and its enabling technologies.¶
The members of the IAB are nominated by the NomComand are confirmed by the Board of the Internet Society (ISOC).The IETF Chair is also a member of the IAB, and theChair of the Internet Research Task Force (IRTF) is an ex officio member.Othermatters concerning the IAB's organization and operation are described in the IABCharter[IAB].¶
Editorial preparation and publication of RFCs are handled by the RFC Production Center (RPC).RFC policy is defined by the RFCSeries Working Group (RSWG), an open group (similar to IETF WGs),and approved by the RFC Series AdvisoryBoard (RSAB), which has appointed members. The RFC Series Consulting Editor (RSCE) is a position funded by the IETF Administration LLC, with responsibilities defined in[RFCEDMODEL].¶
Full details on the roles and responsibilities of the RPC are specified in[RFCEDMODEL], in particular Section4.¶
Many protocol specifications include parameters that must be uniquely assigned. Examples of this include port numbers, option identifiers within a protocol, and so on. The Internet Assigned Numbers Authority (IANA) is responsible for assigning values to these protocol parameters and maintaining parameter registries online (https://www.iana.org/protocols). Assignments are coordinated by writing an "IANA Considerations" section for a given document, as described in[IANADOCS]. The IETF's relationship with IANA is defined by formal agreements, including[IANAMOU].¶
IANA is also responsible for operating and maintainingseveral aspects of the DNS andcoordinating of IP address assignments.¶
The IRTF focuses on longer-term research issues related to the Internet as aparallel organization to the IETF, whichfocuses on the shorter-term issues of engineering, operations, andspecification of standards.¶
The IRTF consists of a number of research groups (RGs) chartered to researchvarious aspects related to the broader Internet.The products of these RGs are typically research results that areoften published in scholarly conferences and journals, but they can also be publishedas RFCs on the IRTF Stream. RGs alsosometimes develop experimental protocols or technologies, some of which may be suitablefor possible standardization in IETF. Similarly, IETF WGssometimes ask RGs for advice or other input. However, contributions fromRGs generallycarry no more weight in the IETF than other community inputand go through the same standards-setting process as any other proposal.¶
The IRTF is managed by the IRTF Chair in consultation with the InternetResearch Steering Group (IRSG). The IRSG membership includes the IRTF Chair,the chairs of the various RGs, and possibly other individuals("members at large") from the community. Details of the organizationand operation of the IRTF, the ISRG, and its RGs may be found in[IRTF],[IABIRTF],[IRTFPRIMER], and[IRTFCHAIR].¶
The IETF Trust is the legal owner of intellectualproperty for the IETF, IRTF, and IAB.This includes their trademarks, the copyrights to RFCs and to worksof the IETF such as the IETF website, andcopyright licenses for IETF contributions including Internet-Drafts.The principles for the copyright licenses granted to and from theTrust are described in[IPRRIGHTS1]and[COPYRIGHT], and the licenses themselves are in theTrust Legal Provisions.¶
The Trust also currently owns IANA's domain names and trademarks through anagreement with IANA.¶
The Trustees that govern the Trust are selected from the IETF community, asdescribed in[TRUSTEES] and the rationale given in[TRUSTRAT].¶
The IETF Administration Limited Liability Company(colloquially, the "IETF LLC") providesthe corporate legal home for the IETF, the IAB, and the IRTF.¶
The IETF LLC is responsible for supporting the ongoing operationsof the IETF, managing its finances and budget, and raising money.It regularly reports to the community.The IETF LLC is the legal entity that signs contracts for the IETFSecretariat, meeting hotels, tools development contractors, among many others.The IETF LLC also responds to legal requests; these are often subpoenasin patent lawsuits.¶
Selection of the IETF LLC Board of Directors is defined in[NOMCOM].¶
The IETF Executive Director handles the IETF's daily tasks and managementand is overseen by the IETF LLC Board of Directors.¶
Section 6 of [ISOCIETF] describes the legal relationship between the IETFLLC and the Internet Society.¶
The administrative functions necessary to support the activities ofthe IETF and its various related boards and organizationsare performed by a Secretariat contracted by the IETF LLC.The IETF Secretariat handles much of the logistics of running the in-personmeetings and is responsible formaintaining the formal public record of the Internet standardsprocess[IETFPROCS].¶
ISOC plays an important role in the standards process.In addition to being the legal entity that hosts the IETF LLC,ISOC appoints the NomCom Chair, confirms IAB candidates selected by the NomCom,and acts as the final authority in the appeals process.This is described in[ISOCIETF].¶
The way in which the ISOC leadership isselected and other matters concerning the operation of the InternetSociety are described in[ISOC].¶
This document introduces no new security considerations.¶
This document has no IANA actions.¶
We are grateful to the authors of[RFC2028] --Richard Hovey andScott Bradner.¶
Barry Leiba,Colin Perkins,Eric Auerswald,John Levine, andLars Eggertprovided useful feedback and corrections to this document.¶