rfc9281.original | rfc9281.txt | |||
---|---|---|---|---|
??? R. Salz | Internet Engineering Task Force (IETF) R. Salz | |||
Internet-Draft Akamai Technologies | Request for Comments: 9281 Akamai Technologies | |||
Obsoletes: 2028 (if approved) 14 March 2022 | BCP: 11 June 2022 | |||
Intended status: Best Current Practice | Obsoletes: 2028 | |||
Expires: 15 September 2022 | Category: Best Current Practice | |||
ISSN: 2070-1721 | ||||
Entities Involved in the IETF Standards Process | Entities Involved in the IETF Standards Process | |||
draft-rsalz-2028bis-07 | ||||
Abstract | Abstract | |||
This document describes the individuals and organizations involved in | This document describes the individuals and organizations involved in | |||
the IETF standards process, as described in IETF BCP 9. It includes | the IETF standards process, as described in BCP 9. It includes brief | |||
brief descriptions of the entities involved, and the role they play | descriptions of the entities involved and the role they play in the | |||
in the standards process. | standards process. | |||
The IETF and its structure have undergone many changes since 1996, | The IETF and its structure have undergone many changes since RFC 2028 | |||
when RFC 2028 was published. This document reflects the changed | was published in 1996. This document reflects the changed | |||
organizational structure of the IETF and obsoletes RFC 2028. | organizational structure of the IETF and obsoletes RFC 2028. | |||
Discussion Venues | ||||
This note is to be removed before publishing as an RFC. | ||||
Discussion of this document takes place on the GENDISPATCH mailing | ||||
list (gendispatch@ietf.org)], which is archived at | ||||
https://mailarchive.ietf.org/arch/browse/gendispatch/. | ||||
Source for this draft and an issue tracker can be found at | ||||
https://github.com/richsalz/draft-ietf-rfc2028bis. | ||||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This memo documents an Internet Best Current Practice. | |||
provisions of BCP 78 and BCP 79. | ||||
Internet-Drafts are working documents of the Internet Engineering | ||||
Task Force (IETF). Note that other groups may also distribute | ||||
working documents as Internet-Drafts. The list of current Internet- | ||||
Drafts is at https://datatracker.ietf.org/drafts/current/. | ||||
Internet-Drafts are draft documents valid for a maximum of six months | This document is a product of the Internet Engineering Task Force | |||
and may be updated, replaced, or obsoleted by other documents at any | (IETF). It represents the consensus of the IETF community. It has | |||
time. It is inappropriate to use Internet-Drafts as reference | received public review and has been approved for publication by the | |||
material or to cite them other than as "work in progress." | Internet Engineering Steering Group (IESG). Further information on | |||
BCPs is available in Section 2 of RFC 7841. | ||||
This Internet-Draft will expire on 15 September 2022. | Information about the current status of this document, any errata, | |||
and how to provide feedback on it may be obtained at | ||||
https://www.rfc-editor.org/info/rfc9281. | ||||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2022 IETF Trust and the persons identified as the | Copyright (c) 2022 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents | |||
license-info) in effect on the date of publication of this document. | (https://trustee.ietf.org/license-info) in effect on the date of | |||
Please review these documents carefully, as they describe your rights | publication of this document. Please review these documents | |||
and restrictions with respect to this document. Code Components | carefully, as they describe your rights and restrictions with respect | |||
extracted from this document must include Revised BSD License text as | to this document. Code Components extracted from this document must | |||
described in Section 4.e of the Trust Legal Provisions and are | include Revised BSD License text as described in Section 4.e of the | |||
provided without warranty as described in the Revised BSD License. | Trust Legal Provisions and are provided without warranty as described | |||
in the Revised BSD License. | ||||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction | |||
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 | 1.1. Terminology | |||
1.2. Changes since RFC 2028 . . . . . . . . . . . . . . . . . 3 | 1.2. Changes since RFC 2028 | |||
2. Key Individuals in the Process . . . . . . . . . . . . . . . 3 | 2. Key Individuals in the Process | |||
2.1. The Document Editor or Author . . . . . . . . . . . . . . 3 | 2.1. Document Editor or Author | |||
2.2. The Working Group Chair . . . . . . . . . . . . . . . . . 4 | 2.2. Working Group Chair | |||
2.3. The Area Director . . . . . . . . . . . . . . . . . . . . 4 | 2.3. Area Director | |||
3. Key Organizations in the Process . . . . . . . . . . . . . . 4 | 3. Key Organizations in the Process | |||
3.1. Internet Engineering Task Force (IETF) . . . . . . . . . 5 | 3.1. Internet Engineering Task Force (IETF) | |||
3.2. Working Groups (WGs) . . . . . . . . . . . . . . . . . . 5 | 3.2. Working Groups (WGs) | |||
3.3. Internet Engineering Steering Group (IESG) . . . . . . . 6 | 3.3. Internet Engineering Steering Group (IESG) | |||
3.4. Internet Architecture Board (IAB) . . . . . . . . . . . . 6 | 3.4. Internet Architecture Board (IAB) | |||
3.5. The RFC Production Center (RPC) . . . . . . . . . . . . . 7 | 3.5. RFC Production Center (RPC) | |||
3.6. Internet Assigned Numbers Authority (IANA) . . . . . . . 7 | 3.6. Internet Assigned Numbers Authority (IANA) | |||
3.7. Internet Research Task Force (IRTF) . . . . . . . . . . . 7 | 3.7. Internet Research Task Force (IRTF) | |||
3.8. The IETF Trust . . . . . . . . . . . . . . . . . . . . . 8 | 3.8. IETF Trust | |||
3.9. IETF Administration LLC (IETF LLC) . . . . . . . . . . . 8 | 3.9. IETF Administration LLC (IETF LLC) | |||
3.10. IETF Secretariat . . . . . . . . . . . . . . . . . . . . 9 | 3.10. IETF Secretariat | |||
3.11. Internet Society (ISOC) . . . . . . . . . . . . . . . . . 9 | 3.11. Internet Society (ISOC) | |||
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 | 4. Security Considerations | |||
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 | 5. IANA Considerations | |||
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 | 6. Informative References | |||
7. Informative References . . . . . . . . . . . . . . . . . . . 9 | Acknowledgements | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 | Author's Address | |||
1. Introduction | 1. Introduction | |||
The process used by the IETF community for the standardization of | The process used by the IETF community for the standardization of | |||
protocols and procedures is described in [IETFPROCS]. That document | protocols and procedures is described in BCP 9 [IETFPROCS]. BCP 9 | |||
defines the stages in the standardization process, the requirements | defines the stages in the standardization process, the requirements | |||
for moving a document between stages, and the types of documents used | for moving a document between stages, and the types of documents used | |||
during this process. This document identifies some of the key | during this process. This document identifies some of the key | |||
individual roles and organizations in that process. | individual roles and organizations in that process. | |||
1.1. Terminology | 1.1. Terminology | |||
This document refers to individual roles in the singular, such as "a | This document refers to individual roles in the singular, such as "a | |||
Document Editor." In reality, many roles are filled by more than one | document editor." In reality, many roles are filled by more than one | |||
person at the same time. For clarity, this document does not use | person at the same time. For clarity, this document does not use | |||
phrases like "Chair (or co-chair)." | phrases like "chair (or co-chair)." | |||
1.2. Changes since RFC 2028 | 1.2. Changes since RFC 2028 | |||
The following changes have been made, in no particular order: | The following changes have been made, in no particular order: | |||
* Added the role of Responsible Area Director (AD) and re-ordered | * Added the role of responsible area director (AD) and reordered | |||
Section 2 to follow the typical workflow. | Section 2 to follow the typical workflow. | |||
* Added the IETF Administration LLC and the IETF Trust to Section 3. | * Added the IETF Administration LLC and the IETF Trust to Section 3. | |||
* Changed RFC Editor to RFC Production Center, to reflect the | * Changed "RFC Editor" to "RFC Production Center" to reflect the | |||
changes made by [RFCEDMODEL]. | changes made by [RFCEDMODEL]. | |||
* Added Section 6 and Section 1.1 and cleaned up some wording | * Added the Terminology and Acknowledgements sections. | |||
throughout the document. | ||||
* Cleaned up some wording throughout the document. | ||||
2. Key Individuals in the Process | 2. Key Individuals in the Process | |||
This section describes the individual roles involved in the process. | This section describes the individual roles involved in the process. | |||
It attempts to list the roles in the order in which they are involved | It attempts to list the roles in the order in which they are involved | |||
in the process, without otherwise expressing significance. | in the process, without otherwise expressing significance. | |||
2.1. The Document Editor or Author | 2.1. Document Editor or Author | |||
Most Working Groups (WGs) focus their efforts on one or more | Most working groups (WGs) focus their efforts on one or more | |||
documents that capture their work results. The Working Group Chair | documents that capture their work results. The WG chair designates | |||
designates one or more people to serve as the Editor(s) for a | one or more people to serve as the editor(s) for a particular | |||
particular document. They are responsible for ensuring that the | document. The editor is responsible for ensuring that the contents | |||
contents of the document accurately reflect the decisions that have | of the document accurately reflect the decisions that have been made | |||
been made by the Working Group. | by the WG. | |||
When a document is composed and edited mainly by one or more | When a document is composed and edited mainly by one or more | |||
individuals, they may be referred to as Document Authors. The | individuals, they may be referred to as "document authors". The | |||
distinction is not significant for the standards process. This | distinction is not significant for the standards process. This | |||
document uses the term Document Editor. | document uses the term "document editor". | |||
When a Document Editor is a Chair of the same Working Group, another | When a document editor is a chair of the same WG, another chair | |||
Chair should manage the process around the document. If another | should manage the process around the document. If another chair is | |||
Chair is not available, the WG and AD must monitor the process | not available, the WG and AD must monitor the process especially | |||
especially carefully to ensure that the resulting documents | carefully to ensure that the resulting documents accurately reflect | |||
accurately reflect the consensus of the Working Group and that all | the consensus of the WG and that all processes are followed. This is | |||
processes are followed. This is the collective obligation of all | the collective obligation of all parties involved in the document. | |||
parties involved in the document. | ||||
2.2. The Working Group Chair | 2.2. Working Group Chair | |||
Each Working Group is headed by a Chair who has the responsibility | Each WG is headed by a chair who has the responsibility for | |||
for facilitating the group's activities, presiding over the group's | facilitating the group's activities, presiding over the group's | |||
meetings, and ensuring that the commitments of the group with respect | meetings, and ensuring that the commitments of the group with respect | |||
to its role in the Internet standards process are met. In | to its role in the Internet standards process are met. In | |||
particular, the WG Chair is the formal point of contact between the | particular, the WG chair is the formal point of contact between the | |||
WG and the Internet Engineering Steering Group (IESG), via the AD of | WG and the Internet Engineering Steering Group (IESG), via the AD of | |||
the area to which the WG belongs. | the area to which the WG belongs. | |||
The details on the selection and responsibilities of a Working Group | The details on the selection and responsibilities of a WG chair can | |||
Chair can be found in [WGPROCS]. | be found in [WGPROCS]. | |||
2.3. The Area Director | 2.3. Area Director | |||
Each Working Group is assigned a single responsible Area Director | Each WG is assigned a single responsible area director (AD). The AD | |||
(AD). The AD can assist the WG chair in assessing consensus and | can assist the WG chair in assessing consensus and executing process. | |||
executing process. The AD also reviews documents after the WG has | The AD also reviews documents after the WG has approved them, and | |||
approved them and, when satisfied, the AD coordinates the IESG review | when satisfied, the AD coordinates the IESG review and IETF Last Call | |||
and IETF last call of of the document. | of the document. | |||
An AD can also sponsor a draft directly, but this is not very common. | An AD can also sponsor an Internet-Draft directly, but this is not | |||
When this is done, a Working Group is not involved. | very common. When this is done, a WG is not involved. | |||
Except for the General Area, IETF Areas traditionally have multiple | Except for the General Area, IETF areas traditionally have multiple | |||
Area Directors. | ADs. | |||
3. Key Organizations in the Process | 3. Key Organizations in the Process | |||
The following organizations and organizational roles are involved in | The following organizations and organizational roles are involved in | |||
the Internet standards process. | the Internet standards process. | |||
3.1. Internet Engineering Task Force (IETF) | 3.1. Internet Engineering Task Force (IETF) | |||
The IETF is an open international community of network designers, | The IETF is an open international community of network designers, | |||
operators, implementors, researchers, and other interested parties | operators, implementors, researchers, and other interested parties | |||
who are concerned with the evolution of the Internet architecture and | who are concerned with the evolution of the Internet architecture and | |||
the smooth operation of the Internet. It is the principal body | the smooth operation of the Internet. It is the principal body | |||
engaged in the development of new Internet Standard specifications | engaged in the development of new Internet Standard specifications | |||
and related documents. | and related documents. | |||
3.2. Working Groups (WGs) | 3.2. Working Groups (WGs) | |||
The technical work of the IETF is done in its Working Groups, which | The technical work of the IETF is done in its WGs, which are | |||
are organized by topics into several Areas | organized by topics into several areas (https://www.ietf.org/topics/ | |||
(https://www.ietf.org/topics/areas/), each one under the coordination | areas/), each under the coordination of an AD. WGs typically have a | |||
of an Area Director. Working Groups typically have a narrow focus | narrow focus and a lifetime bounded by completion of specific tasks | |||
and a lifetime bounded by completion of specific tasks as defined in | as defined in their charter and milestones. Some WGs are long-lived | |||
their charter and milestones. Some Working Groups are long-lived | and intended to conduct ongoing maintenance on IETF protocol(s). | |||
intended to conduct ongoing maintenance on IETF protocol(s). There | There are also "dispatch" WGs that assess where new work in the IETF | |||
are also "dispatch" Working Groups whose role is to assess where new | should be done but do not directly produce standards. | |||
work in the IETF should be done, not directly produce standards. | ||||
For all purposes relevant to the Internet Standards development | For all purposes relevant to the Internet Standards development | |||
process, membership in the IETF and its Working Groups is defined to | process, membership in the IETF and its WGs is defined to be | |||
be established solely and entirely by individuals who participate in | established solely and entirely by individuals who participate in | |||
IETF and Working Group activities. These individuals do not formally | IETF and WG activities. These individuals do not formally represent | |||
represent any organizations they may be affiliated with, although | any organizations they may be affiliated with, although affiliations | |||
affiliations are often used for identification. | are often used for identification. | |||
Anyone with the time and interest to do so is entitled and urged to | Anyone with the time and interest to do so is entitled and urged to | |||
participate actively in one or more Working Groups and to attend IETF | participate actively in one or more WGs and to attend IETF meetings, | |||
meetings, which are usually held three times a year [MEETINGS]. A WG | which are usually held three times a year [MEETINGS]. A WG may also | |||
may also schedule interim meetings (virtual, in-person, or hybrid). | schedule interim meetings (virtual, in-person, or hybrid). These are | |||
These are scheduled and announced to the entire WG. Active Working | scheduled and announced to the entire WG. Active WG participation is | |||
Group participation is possible without attending any in-person | possible without attending any in-person meetings. | |||
meetings. | ||||
Participants in the IETF and its Working Groups must disclose any | Participants in the IETF and its WGs must disclose any relevant | |||
relevant current or pending intellectual property rights that are | current or pending intellectual property rights that are reasonably | |||
reasonably and personally known to the participant if they | and personally known to the participant if they participate in | |||
participate in discussions about a specific technology. The full | discussions about a specific technology. The full intellectual | |||
intellectual property policy is defined in [IPRRIGHTS1] and | property policy is defined in [IPRRIGHTS1] and [IPRRIGHTS2]. | |||
[IPRRIGHTS2]. | ||||
New Working Groups are established by the IESG and almost always have | New WGs are established by the IESG and almost always have a specific | |||
a specific and explicit charter. The charter can be modified as the | and explicit charter. The charter can be modified as the WG | |||
Working Group progresses. The guidelines and procedures for the | progresses. The guidelines and procedures for the formation and | |||
formation and operation of Working Groups are described in detail in | operation of WGs are described in detail in [WGPROCS]. | |||
[WGPROCS]. | ||||
A Working Group is managed by a Working Group Chair, as described in | A WG is managed by a WG chair, as described in Section 2.2. | |||
Section 2.2. Documents produced by the group have an Editor, as | Documents produced by the group have an editor, as described in | |||
described in Section 2.1. Further details of Working Group operation | Section 2.1. Further details of WG operation can be found in | |||
can be found in [WGPROCS]. | [WGPROCS]. | |||
Working Groups ideally display a spirit of cooperation as well as a | WGs ideally display a spirit of cooperation as well as a high degree | |||
high degree of technical maturity; IETF participants recognize that | of technical maturity; IETF participants recognize that the greatest | |||
the greatest benefit for all members of the Internet community | benefit for all members of the Internet community results from | |||
results from cooperative development of technically excellent | cooperative development of technically excellent protocols and | |||
protocols and services. | services. | |||
3.3. Internet Engineering Steering Group (IESG) | 3.3. Internet Engineering Steering Group (IESG) | |||
The IESG is responsible for the management of the IETF technical | The IESG is responsible for the management of the IETF technical | |||
activities. It administers the Internet Standards process according | activities. It administers the Internet Standards process according | |||
to the rules and procedures defined in [IETFPROCS]. The IESG is | to the rules and procedures defined in [IETFPROCS]. The IESG is | |||
responsible for the actions associated with the progression of | responsible for the actions associated with the progression of | |||
documents along the "IETF stream," including the initial approval of | documents along the IETF Stream, including the initial approval of | |||
new Working Groups, any subsequent rechartering, and the final | new WGs, any subsequent rechartering, and the final approval of | |||
approval of documents. The IESG is composed of the Area Directors | documents. The IESG is composed of the ADs and the IETF Chair. The | |||
and the IETF Chair, who also chairs the IESG and is the Area Director | IETF Chair also chairs the IESG and is the AD for the General Area. | |||
for the General Area. The Chair of the Internet Architecture Board | The Chair of the Internet Architecture Board (IAB) is an ex officio | |||
(IAB) is an ex-officio member of the IESG. Various other bodies have | member of the IESG. Various other bodies have liaisons with the | |||
liaisons with the IESG. | 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 | All members of the IESG are nominated by a Nominations Committee | |||
(colloquially, NomCom), and are confirmed by the IAB. See [NOMCOM] | (colloquially, "NomCom") and are confirmed by the IAB. See [NOMCOM] | |||
for a detailed description of the NomCom procedures. Other matters | for a detailed description of the NomCom procedures. Other matters | |||
concerning its organization and operation are described in the IESG | concerning the organization and operation of the NomCom are described | |||
charter [IESG]. | in the IESG Charter [IESG]. | |||
3.4. Internet Architecture Board (IAB) | 3.4. Internet Architecture Board (IAB) | |||
The IAB provides oversight of the architecture of the Internet and | The IAB provides oversight of the architecture of the Internet and | |||
its protocols. The IAB approves IESG candidates put forward by the | its protocols. The IAB approves IESG candidates put forward by the | |||
NomCom. It also reviews all proposed WG charters. | NomCom. It also reviews all proposed IETF WG charters. | |||
The IAB provides oversight of the standards process and serves as an | The IAB provides oversight of the standards process and serves as an | |||
appeal board for related complaints about improper execution | appeal board for related complaints about improper execution | |||
[IETFPROCS]. In general, it acts as a source of advice about | [IETFPROCS]. In general, it acts as a source of advice about | |||
technical, architectural, procedural, and policy matters pertaining | technical, architectural, procedural, and policy matters pertaining | |||
to the Internet and its enabling technologies. | to the Internet and its enabling technologies. | |||
The members of the IAB are nominated by the NomCom, and are confirmed | The members of the IAB are nominated by the NomCom and are confirmed | |||
by the Board of the Internet Society (ISOC). The IETF Chair is also | by the Board of the Internet Society (ISOC). The IETF Chair is also | |||
a member of the IAB, and the Chair of the Internet Research Task | a member of the IAB, and the Chair of the Internet Research Task | |||
Force (IRTF) is an ex-officio member. Other matters concerning the | Force (IRTF) is an ex officio member. Other matters concerning the | |||
IAB's organization and operation are described in the IAB charter | IAB's organization and operation are described in the IAB Charter | |||
[IAB]. | [IAB]. | |||
3.5. The RFC Production Center (RPC) | 3.5. RFC Production Center (RPC) | |||
Publication of RFCs is handled by the RFC Production Center (RPC), | Editorial preparation and publication of RFCs are handled by the RFC | |||
including editorial preparation and publication. RFC policy is | Production Center (RPC). RFC policy is defined by the RFC Series | |||
defined by the RFC Series Working Group (RSWG), an open group | Working Group (RSWG), an open group (similar to IETF WGs), and | |||
(similar to IETF Working Groups), and approved by the RFC Advisory | approved by the RFC Series Advisory Board (RSAB), which has appointed | |||
Board (RSAB), which has appointed members. The RFC Series Consulting | members. The RFC Series Consulting Editor (RSCE) is a position | |||
Editor (RSCE) is a position funded by the IETF LLC, with | funded by the IETF Administration LLC, with responsibilities defined | |||
responsibilities to consult with all parties, and be a member of the | in [RFCEDMODEL]. | |||
RSAB. | ||||
Full details on the roles and responsibilities of the RPC are | Full details on the roles and responsibilities of the RPC are | |||
specified in [RFCEDMODEL], in particular Section 4. | specified in [RFCEDMODEL], in particular Section 4. | |||
3.6. Internet Assigned Numbers Authority (IANA) | 3.6. Internet Assigned Numbers Authority (IANA) | |||
Many protocol specifications include parameters that must be uniquely | Many protocol specifications include parameters that must be uniquely | |||
assigned. Examples of this include port numbers, option identifiers | assigned. Examples of this include port numbers, option identifiers | |||
within a protocol, and so on. The Internet Assigned Numbers | within a protocol, and so on. The Internet Assigned Numbers | |||
Authority (IANA) is responsible for assigning values to these | Authority (IANA) is responsible for assigning values to these | |||
protocol parameters, maintained in parameter registries. These | protocol parameters and maintaining parameter registries online | |||
registries are maintained online (https://www.iana.org/protocols). | (https://www.iana.org/protocols). Assignments are coordinated by | |||
Assignments are coordinated by writing an "IANA Considerations" | writing an "IANA Considerations" section for a given document, as | |||
section for a given document, as descrribed in [IANADOCS]. The | described in [IANADOCS]. The IETF's relationship with IANA is | |||
IETF's relationship with IANA is defined by formal agreements, | defined by formal agreements, including [IANAMOU]. | |||
including [IANAMOU]. | ||||
IANA also is responsible for operating and maintaining several | IANA is also responsible for operating and maintaining several | |||
aspects of the DNS (https://www.iana.org/domains) and coordinating of | aspects of the DNS (https://www.iana.org/domains) and coordinating of | |||
IP address assignments (https://www.iana.org/numbers). | IP address assignments (https://www.iana.org/numbers). | |||
3.7. Internet Research Task Force (IRTF) | 3.7. Internet Research Task Force (IRTF) | |||
The IRTF focuses on longer-term research issues related to the | The IRTF focuses on longer-term research issues related to the | |||
Internet as a parallel organization to the IETF, which focuses on the | Internet as a parallel organization to the IETF, which focuses on the | |||
shorter-term issues of engineering, operations, and specification of | shorter-term issues of engineering, operations, and specification of | |||
standards. | standards. | |||
The IRTF consists of a number of Research Groups (RGs) chartered to | The IRTF consists of a number of research groups (RGs) chartered to | |||
research various aspects related to the broader Internet. The | research various aspects related to the broader Internet. The | |||
products of these RGs are typically research results that are often | products of these RGs are typically research results that are often | |||
published in scholarly conferences and journals, but can also be | published in scholarly conferences and journals, but they can also be | |||
published as RFCs on the IRTF's RFC stream. RGs also sometimes | published as RFCs on the IRTF Stream. RGs also sometimes develop | |||
develop experimental protocols or technologies, some of which may be | experimental protocols or technologies, some of which may be suitable | |||
suitable for possible standardization in IETF. Similarly, IETF | for possible standardization in IETF. Similarly, IETF WGs sometimes | |||
working groups sometimes ask RGs for advice or other input. | ask RGs for advice or other input. However, contributions from RGs | |||
Contributions from RGs, however, in general carry no more weight in | generally carry no more weight in the IETF than other community input | |||
the IETF than other community input, and go through the same | and go through the same standards-setting process as any other | |||
standards setting process as any other proposal. | proposal. | |||
The IRTF is managed by the IRTF Chair in consultation with the | The IRTF is managed by the IRTF Chair in consultation with the | |||
Internet Research Steering Group (IRSG). The IRSG membership | Internet Research Steering Group (IRSG). The IRSG membership | |||
includes the IRTF Chair, the Chairs of the various RG and possibly | includes the IRTF Chair, the chairs of the various RGs, and possibly | |||
other individuals ("members at large") from the community. Details | other individuals ("members at large") from the community. Details | |||
of the organization and operation of the IRTF, the ISRG, and its RGs | of the organization and operation of the IRTF, the ISRG, and its RGs | |||
may be found in [IRTF], [IABIRTF], [IRTFPRIMER], and [IRTFCHAIR]. | may be found in [IRTF], [IABIRTF], [IRTFPRIMER], and [IRTFCHAIR]. | |||
3.8. The IETF Trust | 3.8. IETF Trust | |||
The IETF Trust is the legal owner of intellectual property for the | The IETF Trust is the legal owner of intellectual property for the | |||
IETF, IRTF, and IAB. This includes their trademarks, the copyrights | IETF, IRTF, and IAB. This includes their trademarks, the copyrights | |||
to RFCs and to works of the IETF such as the IETF web site, and | to RFCs and to works of the IETF such as the IETF website, and | |||
copyright licenses for IETF contributions including Internet Drafts. | copyright licenses for IETF contributions including Internet-Drafts. | |||
The principles for the copyright licenses granted to and from the | The principles for the copyright licenses granted to and from the | |||
Trust are described in [IPRRIGHTS1] and [COPYRIGHT], and the licenses | Trust are described in [IPRRIGHTS1] and [COPYRIGHT], and the licenses | |||
themselves are in the Trust Legal Provisions | themselves are in the Trust Legal Provisions | |||
(https://trustee.ietf.org/documents/trust-legal-provisions/). | (https://trustee.ietf.org/documents/trust-legal-provisions/). | |||
The Trust also currently owns IANA's domain names and trademarks | The Trust also currently owns IANA's domain names and trademarks | |||
through an agreement with the IANA clients. | through an agreement with IANA. | |||
The Trustees that govern the Trust are selected from the IETF | The Trustees that govern the Trust are selected from the IETF | |||
community, as described in [TRUSTEES] and the rationale given in | community, as described in [TRUSTEES] and the rationale given in | |||
[TRUSTRAT]. | [TRUSTRAT]. | |||
3.9. IETF Administration LLC (IETF LLC) | 3.9. IETF Administration LLC (IETF LLC) | |||
The IETF Administration Limited Liability Corporation (colloquially, | The IETF Administration Limited Liability Company (colloquially, the | |||
the IETF LLC) provides the corporate legal home for the IETF, the | "IETF LLC") provides the corporate legal home for the IETF, the IAB, | |||
IAB, and the IRTF. | and the IRTF. | |||
The IETF LLC is responsible for supporting the ongoing operations of | The IETF LLC is responsible for supporting the ongoing operations of | |||
the IETF, managing its finances and budget, and raising money. It | the IETF, managing its finances and budget, and raising money. It | |||
regularly reports to the community. The LLC is the legal entity that | regularly reports to the community. The IETF LLC is the legal entity | |||
signs contracts for the IETF Secretariat, meeting hotels, tools | that signs contracts for the IETF Secretariat, meeting hotels, tools | |||
development contractors, among many others. The LLC also responds to | development contractors, among many others. The IETF LLC also | |||
legal requests; these are often subpoenas in patent lawsuits. | responds to legal requests; these are often subpoenas in patent | |||
lawsuits. | ||||
Selection of the LLC Board of Directors is defined in [NOMCOM]. | Selection of the IETF LLC Board of Directors is defined in [NOMCOM]. | |||
The IETF Executive Director handles the IETF's daily tasks and | The IETF Executive Director handles the IETF's daily tasks and | |||
management, and is overseen by the LLC Board of Directors. | management and is overseen by the IETF LLC Board of Directors. | |||
[ISOCIETF], Section 6 describes the legal relationship between the | Section 6 of [ISOCIETF] describes the legal relationship between the | |||
IETF LLC and the Internet Society. | IETF LLC and the Internet Society. | |||
3.10. IETF Secretariat | 3.10. IETF Secretariat | |||
The administrative functions necessary to support the activities of | The administrative functions necessary to support the activities of | |||
the IETF and its various related boards and organizations are | the IETF and its various related boards and organizations are | |||
performed by a Secretariat contracted by the IETF LLC. The IETF | performed by a Secretariat contracted by the IETF LLC. The IETF | |||
Secretariat handles much of the logistics of running the in-person | Secretariat handles much of the logistics of running the in-person | |||
meetings, and is responsible for maintaining the formal public record | meetings and is responsible for maintaining the formal public record | |||
of the Internet standards process [IETFPROCS]. | of the Internet standards process [IETFPROCS]. | |||
3.11. Internet Society (ISOC) | 3.11. Internet Society (ISOC) | |||
ISOC plays an important role in the standards process. In addition | ISOC plays an important role in the standards process. In addition | |||
to being the legal entity that hosts the IETF LLC, ISOC appoints the | to being the legal entity that hosts the IETF LLC, ISOC appoints the | |||
NomCom Chair, confirms IAB candidates selected by the NomCom, and | NomCom Chair, confirms IAB candidates selected by the NomCom, and | |||
acts as the final authority in the appeals process. This is | acts as the final authority in the appeals process. This is | |||
described in [ISOCIETF]. | described in [ISOCIETF]. | |||
The way in which the the ISOC leadership is selected, and other | The way in which the ISOC leadership is selected and other matters | |||
matters concerning the operation of the Internet Society, are | concerning the operation of the Internet Society are described in | |||
described in [ISOC]. | [ISOC]. | |||
4. Security Considerations | 4. Security Considerations | |||
This document introduces no new security considerations. | This document introduces no new security considerations. | |||
5. IANA Considerations | 5. IANA Considerations | |||
This document has no IANA actions. | This document has no IANA actions. | |||
6. Acknowledgements | 6. Informative References | |||
We are grateful to the authors of [RFC2028], Richard Hovey and Scott | ||||
Bradner. | ||||
Barry Lieba, Colin Perkins, Eric Auerswald, John Levine, and Lars | ||||
Eggert provided useful feedback and corrections to this document. | ||||
7. Informative References | ||||
[COPYRIGHT] | [COPYRIGHT] | |||
Halpern, J., Ed., "Advice to the Trustees of the IETF | Halpern, J., Ed., "Advice to the Trustees of the IETF | |||
Trust on Rights to Be Granted in IETF Documents", | Trust on Rights to Be Granted in IETF Documents", | |||
RFC 8721, DOI 10.17487/RFC8721, February 2020, | RFC 8721, DOI 10.17487/RFC8721, February 2020, | |||
<https://doi.org/10.17487/RFC8721>. | <https://www.rfc-editor.org/info/rfc8721>. | |||
[IAB] Internet Architecture Board and B. Carpenter, Ed., | [IAB] Internet Architecture Board and B. Carpenter, Ed., | |||
"Charter of the Internet Architecture Board (IAB)", | "Charter of the Internet Architecture Board (IAB)", | |||
BCP 39, RFC 2850, May 2000. | BCP 39, RFC 2850, May 2000. | |||
<https://www.rfc-editor.org/info/bcp39> | <https://www.rfc-editor.org/info/bcp39> | |||
[IABIRTF] Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB, | [IABIRTF] Floyd, S., Ed., Paxson, V., Ed., Falk, A., Ed., and IAB, | |||
"IAB Thoughts on the Role of the Internet Research Task | "IAB Thoughts on the Role of the Internet Research Task | |||
Force (IRTF)", RFC 4440, DOI 10.17487/RFC4440, March 2006, | Force (IRTF)", RFC 4440, DOI 10.17487/RFC4440, March 2006, | |||
<https://doi.org/10.17487/RFC4440>. | <https://www.rfc-editor.org/info/rfc4440>. | |||
[IANADOCS] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | [IANADOCS] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | |||
Writing an IANA Considerations Section in RFCs", BCP 26, | Writing an IANA Considerations Section in RFCs", BCP 26, | |||
RFC 8126, June 2017. | RFC 8126, June 2017. | |||
<https://www.rfc-editor.org/info/bcp26> | <https://www.rfc-editor.org/info/bcp26> | |||
[IANAMOU] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of | [IANAMOU] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of | |||
Understanding Concerning the Technical Work of the | Understanding Concerning the Technical Work of the | |||
Internet Assigned Numbers Authority", RFC 2860, | Internet Assigned Numbers Authority", RFC 2860, | |||
DOI 10.17487/RFC2860, June 2000, | DOI 10.17487/RFC2860, June 2000, | |||
<https://doi.org/10.17487/RFC2860>. | <https://www.rfc-editor.org/info/rfc2860>. | |||
[IESG] Alvestrand, H., "An IESG charter", RFC 3710, | [IESG] Alvestrand, H., "An IESG charter", RFC 3710, | |||
DOI 10.17487/RFC3710, February 2004, | DOI 10.17487/RFC3710, February 2004, | |||
<https://doi.org/10.17487/RFC3710>. | <https://www.rfc-editor.org/info/rfc3710>. | |||
[IETFPROCS] | [IETFPROCS] | |||
Bradner, S., "The Internet Standards Process -- Revision | Bradner, S., "The Internet Standards Process -- Revision | |||
3", BCP 9, RFC 2026, October 1996. | 3", BCP 9, RFC 2026, October 1996. | |||
Dusseault, L. and R. Sparks, "Guidance on Interoperation | Dusseault, L. and R. Sparks, "Guidance on Interoperation | |||
and Implementation Reports for Advancement to Draft | and Implementation Reports for Advancement to Draft | |||
Standard", BCP 9, RFC 5657, September 2009. | Standard", BCP 9, RFC 5657, September 2009. | |||
Housley, R., Crocker, D., and E. Burger, "Reducing the | Housley, R., Crocker, D., and E. Burger, "Reducing the | |||
skipping to change at page 11, line 32 ¶ | skipping to change at line 467 ¶ | |||
<https://www.rfc-editor.org/info/bcp78> | <https://www.rfc-editor.org/info/bcp78> | |||
[IPRRIGHTS2] | [IPRRIGHTS2] | |||
Bradner, S. and J. Contreras, "Intellectual Property | Bradner, S. and J. Contreras, "Intellectual Property | |||
Rights in IETF Technology", BCP 79, RFC 8179, May 2017. | Rights in IETF Technology", BCP 79, RFC 8179, May 2017. | |||
<https://www.rfc-editor.org/info/bcp79> | <https://www.rfc-editor.org/info/bcp79> | |||
[IRTF] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines | [IRTF] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines | |||
and Procedures", BCP 8, RFC 2014, DOI 10.17487/RFC2014, | and Procedures", BCP 8, RFC 2014, DOI 10.17487/RFC2014, | |||
October 1996, <https://doi.org/10.17487/RFC2014>. | October 1996, <https://www.rfc-editor.org/info/rfc2014>. | |||
[IRTFCHAIR] | [IRTFCHAIR] | |||
Eggert, L., "The Role of the IRTF Chair", RFC 7827, | Eggert, L., "The Role of the IRTF Chair", RFC 7827, | |||
DOI 10.17487/RFC7827, March 2016, | DOI 10.17487/RFC7827, March 2016, | |||
<https://doi.org/10.17487/RFC7827>. | <https://www.rfc-editor.org/info/rfc7827>. | |||
[IRTFPRIMER] | [IRTFPRIMER] | |||
Dawkins, S., Ed., "An IRTF Primer for IETF Participants", | Dawkins, S., Ed., "An IRTF Primer for IETF Participants", | |||
RFC 7418, DOI 10.17487/RFC7418, December 2014, | RFC 7418, DOI 10.17487/RFC7418, December 2014, | |||
<https://doi.org/10.17487/RFC7418>. | <https://www.rfc-editor.org/info/rfc7418>. | |||
[ISOC] "Amended and restated By-Laws of the Internet Society", | [ISOC] Internet Society, "Amended and restated By-Laws of the | |||
March 2021, <https://www.internetsociety.org/about- | Internet Society", May 2021, | |||
internet-society/governance-policies/by-laws/>. | <https://www.internetsociety.org/about-internet-society/ | |||
governance-policies/by-laws/>. | ||||
[ISOCIETF] Camarillo, G. and J. Livingood, "The IETF-ISOC | [ISOCIETF] Camarillo, G. and J. Livingood, "The IETF-ISOC | |||
Relationship", RFC 8712, DOI 10.17487/RFC8712, February | Relationship", RFC 8712, DOI 10.17487/RFC8712, February | |||
2020, <https://doi.org/10.17487/RFC8712>. | 2020, <https://www.rfc-editor.org/info/rfc8712>. | |||
[MEETINGS] Krishnan, S., "High-Level Guidance for the Meeting Policy | [MEETINGS] Krishnan, S., "High-Level Guidance for the Meeting Policy | |||
of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719, | of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719, | |||
February 2020, <https://doi.org/10.17487/RFC8719>. | February 2020, <https://www.rfc-editor.org/info/rfc8719>. | |||
[NOMCOM] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, | [NOMCOM] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, | |||
Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection, | Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection, | |||
Confirmation, and Recall Process: Operation of the IETF | Confirmation, and Recall Process: Operation of the IETF | |||
Nominating and Recall Committees", BCP 10, RFC 8713, | Nominating and Recall Committees", BCP 10, RFC 8713, | |||
February 2020. | February 2020. | |||
Leiba, B., "Eligibility for the 2020-2021 Nominating | Leiba, B., "Eligibility for the 2020-2021 Nominating | |||
Committee", BCP 10, RFC 8788, May 2020. | Committee", BCP 10, RFC 8788, May 2020. | |||
<https://www.rfc-editor.org/info/bcp10> | <https://www.rfc-editor.org/info/bcp10> | |||
[RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in | [RFC2028] Hovey, R. and S. Bradner, "The Organizations Involved in | |||
the IETF Standards Process", BCP 11, RFC 2028, | the IETF Standards Process", BCP 11, RFC 2028, | |||
DOI 10.17487/RFC2028, October 1996, | DOI 10.17487/RFC2028, October 1996, | |||
<https://doi.org/10.17487/RFC2028>. | <https://www.rfc-editor.org/info/rfc2028>. | |||
[RFCEDMODEL] | [RFCEDMODEL] | |||
"RFC Editor Model (Version 3)", n.d., | Saint-Andre, P., Ed., "RFC Editor Model (Version 3)", | |||
<https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced- | RFC 9280, DOI 10.17487/RFC9280, June 2022, | |||
model/>. | <https://www.rfc-editor.org/info/rfc9280>. | |||
[TRUSTEES] Arkko, J. and T. Hardie, "Update to the Process for | [TRUSTEES] Arkko, J. and T. Hardie, "Update to the Process for | |||
Selection of Trustees for the IETF Trust", BCP 101, | Selection of Trustees for the IETF Trust", BCP 101, | |||
RFC 8714, DOI 10.17487/RFC8714, February 2020, | RFC 8714, DOI 10.17487/RFC8714, February 2020, | |||
<https://doi.org/10.17487/RFC8714>. | <https://www.rfc-editor.org/info/rfc8714>. | |||
[TRUSTRAT] Arkko, J., "IETF Administrative Support Activity 2.0: | [TRUSTRAT] Arkko, J., "IETF Administrative Support Activity 2.0: | |||
Update to the Process for Selection of Trustees for the | Update to the Process for Selection of Trustees for the | |||
IETF Trust", RFC 8715, DOI 10.17487/RFC8715, February | IETF Trust", RFC 8715, DOI 10.17487/RFC8715, February | |||
2020, <https://doi.org/10.17487/RFC8715>. | 2020, <https://www.rfc-editor.org/info/rfc8715>. | |||
[WGPROCS] Bradner, S., "IETF Working Group Guidelines and | [WGPROCS] Bradner, S., "IETF Working Group Guidelines and | |||
Procedures", BCP 25, RFC 2418, September 1998. | Procedures", BCP 25, RFC 2418, September 1998. | |||
Wasserman, M., "Updates to RFC 2418 Regarding the | Wasserman, M., "Updates to RFC 2418 Regarding the | |||
Management of IETF Mailing Lists", BCP 25, RFC 3934, | Management of IETF Mailing Lists", BCP 25, RFC 3934, | |||
October 2004. | October 2004. | |||
Resnick, P. and A. Farrel, "IETF Anti-Harassment | Resnick, P. and A. Farrel, "IETF Anti-Harassment | |||
Procedures", BCP 25, RFC 7776, March 2016. | Procedures", BCP 25, RFC 7776, March 2016. | |||
Resnick, P. and A. Farrel, "Update to the IETF Anti- | Resnick, P. and A. Farrel, "Update to the IETF Anti- | |||
Harassment Procedures for the Replacement of the IETF | Harassment Procedures for the Replacement of the IETF | |||
Administrative Oversight Committee (IAOC) with the IETF | Administrative Oversight Committee (IAOC) with the IETF | |||
Administration LLC", BCP 25, RFC 8716, February 2020. | Administration LLC", BCP 25, RFC 8716, February 2020. | |||
<https://www.rfc-editor.org/info/bcp25> | <https://www.rfc-editor.org/info/bcp25> | |||
Acknowledgements | ||||
We are grateful to the authors of [RFC2028] -- Richard Hovey and | ||||
Scott Bradner. | ||||
Barry Leiba, Colin Perkins, Eric Auerswald, John Levine, and Lars | ||||
Eggert provided useful feedback and corrections to this document. | ||||
Author's Address | Author's Address | |||
Rich Salz | Rich Salz | |||
Akamai Technologies | Akamai Technologies | |||
Email: rsalz@akamai.com | Email: rsalz@akamai.com | |||
End of changes. 75 change blocks. | ||||
229 lines changed or deleted | 213 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |