Mozilla

stpeter@jabber.org

Internet Internet-Draft This document describes Version 3 of the RFC Editor model. As specified here, the model divides the responsibilities for the RFC Series into two high-level functions: policy definition governing the Series as a whole, and policy implementation through publication of documents in the Series. The policy definition function is the responsibility of the RFC Series Working Group (RSWG), which produces policy proposals that are subject to approval by the RFC Series Approval Board (RSAB). The policy implementation function is primarily the responsibility of the RFC Production Center (RPC), under the ultimate authority of the IETF Administration Limited Liability Company (LLC). This document reflects experience gained with version 1 of the RFC Editor Model as specified in RFC 5620 and with version 2 as specified in RFC 6635 and RFC 8728. This document obsoletes RFC 8728.

NOTE: This document is a work in progress. Although it is intended to describe consensus forged in the RFC Editor Future Development Program, many aspects are not yet settled; as a result, this document contains proposals and conjectures that do not yet have consensus in the Program. Where possible, open issues are identified herein to foster discussion. Documents in the Request for Comments (RFC) series have been continually published since 1969 . The RFC series is described in . RFC 8729 uses the term “RFC Editor function” or “RFC Editor” to identify the collective set of responsibilities for publishing documents in the RFC series. The processes and organizational models for publication of RFCs have changed significantly over the years. Most recently, in 2009 defined the RFC Editor Model (Version 1) and in 2012 defined the RFC Editor Model (Version 2), since modified slightly in 2020 by . In order to provide a sustainable basis for continued publication of the RFC series, this document describes Version 3 of the RFC Editor model, which divides the responsibilities for the RFC Series into two high-level functions: policy definition governing the Series as a whole, and policy implementation through publication of documents in the Series. The policy definition function is the responsibility of the RFC Series Working Group (RSWG), which produces policy proposals that are subject to approval by the RFC Series Approval Board (RSAB). The policy implementation function is primarily the responsibility of the RFC Production Center (RPC), under the ultimate authority of the IETF Administration Limited Liability Company (LLC) . This document obsoletes RFC 8728 by making a full update to the RFC Editor Model, changing the responsibilities of existing bodies and functions, and introducing new functions (see Section 7 of this document for a summary of the changes from Version 2).

Version 2 of the RFC Editor Model specified a structure consisting of the RFC Series Editor, the RFC Production Center, and the RFC Publisher, with oversight provided by the RFC Series Oversight Committee (RSOC) on behalf of the Internet Architecture Board (IAB). Discussion within the RFCED-Future Program has led in the direction of a more consensus-oriented structure (similar in some respects to the structure of technical work within the IETF or IRTF) that retains roles for specialized expertise in document editing and publication. The policy definition function is performed by the RFC Series Working Group (RSWG), which produces policy proposals that are subject to approval by the RFC Series Approval Board (RSAB), after which such policies are formally established. The RSWG is an open working group (as described below) that seeks input and participation from a wide range of persons who are have an interest in the RFC Series. The RSAB consists of appointed members who represent the various RFC streams as well as an expert in technical publishing, the RFC Series Editor/Advisor (RSEA). The policy implementation function is performed by the RFC Production Center (RPC), under the ultimate authority of the IETF Administration Limited Liability Company (IETF LLC). In short: The RSWG establishes policy, with input from the community, the RSAB, and the RSEA. The RSAB considers those proposals and approves or returns as appropriate. The RPC periodically reports to the RSAB on how it is implementing established policies. The RSEA provides expert advice to the RPC and RSAB on how to implement established policies on an ongoing and operational basis, which can include raising issues or initiating proposed policy changes within the RSWG. If issues arise with the implementation of particular policies, the RPC brings them to the RSAB who interprets the policy and provides interim guidance to the RPC, informing the RSWG of those interpretations. The remainder of this document describes the model in greater detail.

Policies governing the RFC series as a whole shall be defined in the open through proposals that are generated by and discussed within the RFC Series Working Group (RSWG) and then approved by the RFC Series Approval Board (RSAB). Policies under the purview of the RSWG and RSAB might include but are not necessarily limited to document formats, processes for publication and dissemination of RFCs, and overall management of the RFC series.

The RFC Series Working Group (RSWG) shall formulate proposals regarding policies that govern the RFC series. The intent is that the RSWG operate in a way similar to working groups in the IETF and research groups in the IRTF. Therefore, all RSWG meetings shall be open to any participant, subject to intellectual property policies which must be consistent with those of the IETF as specified in BCP 78 and BCP 79 . The RSWG shall operate by rough consensus, a mode of operation informationally described in . When the RSWG is formed, all discussions shall take place on an open email discussion list. Subsequently, the RSWG may decide by rough consensus to also use additional tooling (e.g., GitHub as specified in ), forms of communication (e.g., in-person or online meetings), and working methods (e.g., design teams) as long as they are consistent with . All interested persons are welcome to participate in the RSWG (subject to anti-harassment policies as described below). This includes participants in the IETF and IRTF, IAB and IESG members, RFC authors, individuals who use RFCs in procurement decisions, and the like. The IETF LLC Board members, staff, and the IETF Executive Director are invited to participate as community members in the RSWG to the extent permitted by any relevant IETF LLC policies. Members of the RSAB are also expected to participate actively. The RSWG shall have two chairs, one appointed by the IESG and the other appointed by the IAB. When the RSWG is formed, the chair appointed by the IESG shall serve for a term of one (1) year and the chair appointed by the IAB shall serve for a term of two (2) years; thereafter, chairs shall serve for a term of two (2) years, with no term limits on renewal. The appointing bodies shall determine their own processes for making these appointments, such as provision for an open nominations period. Community members who have concerns about the performance of an RSWG chair should direct their feedback to the relevant appointing body. Each appointing body shall have the power to remove its appointed chair at its discretion. It is the responsibility of the chairs to encourage rough consensus within the RSWG and to follow that consensus in their decision making, for instance regarding advancement of proposals to the RSAB. NOTE: This section is intended to address ISSUE #9, ISSUE #14, ISSUE #16, ISSUE #41, ISSUE #44, ISSUE #68, and ISSUE #72.

The RFC Series Approval Board (RSAB) shall act as the approving body for proposals generated within the RSWG. The sole function of RSAB is to review policy proposals generated by the RSWG; it shall have no independent authority to formulate policy on its own. It is expected that the RSAB will respect the rough consensus of the RSWG wherever possible, without ceding its review function. The voting members of the RSAB shall be as follows: One delegate representing the IETF stream, appointed by the IESG One delegate representing the IAB stream, appointed by the IAB The IRTF Chair, representing the IRTF stream The Independent Submissions Editor The RFC Series Editor/Advisor To ensure the smooth functioning of the RFC Series, the RSAB shall include the IETF Executive Director as a non-voting member since the IETF LLC is ultimately responsible for the operation of the policy implementation function. The RSAB may at its discretion include additional non-voting members, for instance a liaison from the RPC. The IAB and IESG delegates must be selected by the Nominating Committee to their respective bodies (i.e., they must not be liaison or ex-officio members). These delegates shall serve for one-year renewable terms. If it becomes necessary to replace such a delegate for any reason, then for the sake of continuity the IAB or IESG should name a new delegate to complete the term. Whenever a new stream is created (see below), the document that creates the stream shall specify if a voting member representing that stream shall also be added to the RSAB, along with any rules and processes related to that representative (e.g., whether the representative is a member of the body responsible for the stream or an appointed delegate thereof. The RSAB shall choose a chair from among its members using a method to be determined by the RSAB. The RSAB is expected to operate via email, in-person meetings, teleconferencing systems, and any additional tooling it deems necessary. The RSAB shall keep a public record of its proceedings, including minutes of all meetings and a record of all decisions. The RSAB shall announce plans and agendas for their meetings on the RFC Editor website and by email to the RSWG at least a week before such meetings. The meetings shall be open for public attendance and the RSAB may consider allowing open participation. If the RSAB needs to discuss a confidential matter in executive session, that part of the meeting shall be private to the RSAB, but must be noted on the agenda, and must be documented in the minutes with as much detail as the confidentiality requirements permit. NOTE: This section is intended to address ISSUE #9, ISSUE #38, ISSUE #50, and ISSUE #53.

The intent is to provide an open forum by which policies related to the RFC series are defined and evolved. The general expectation is that all interested parties will participate in the RSWG, and that only under extreme circumstances should RSAB members need to hold “CONCERN” positions as described below. Because policy issues can be difficult and contentious, RSWG participants and RSAB members are strongly encouraged to work together in a spirit of good faith and mutual understanding to achieve rough consensus (see ). In particular, RSWG members are encouraged to take RSAB concerns seriously, and RSAB members are encouraged to clearly express their concerns early in the process and to be responsive to the community. All parties are encouraged to respect the value of each stream and the long term health and viability of the RFC series. This process is intended to be one of continuous consultation. RSAB members should consult with their constituent stakeholders (e.g., authors, editors, tool developers, and consumers of RFCs) on an ongoing basis, so that when the time comes to consider a proposal, there should be no surprises. Appointing bodies are expected to establish whatever processes they deem appropriate to facilitate this goal.

The following process shall be used to formulate or modify processes related to the RFC series: An individual participant in the RSWG generates a proposal in the form of an Internet-Draft. If there is sufficient interest in the proposal, RSWG may adopt the proposal as a draft proposal of the RSWG, much the same way a working group of the IETF or IRTF would (see ). The RSWG shall then further develop the proposal. Members of the RSAB are expected to participate in discussion relating to such proposals so that they are fully aware of proposals early in the policy definition process and so that any issues or concerns that they have will be raised during the development of the proposals and will not be left until the RSAB review period. At some point, if the RSWG chairs believe there may be rough consensus for the proposal to advance, they will issue a working group last call. After a suitable period of time, the RSWG chairs will determine whether rough consensus for the proposal exists. If comments have been received and substantial changes have been made, it is expected that additional last calls may be necessary. Once consensus is established in the RSWG, the RSAB shall issue a community call for comments as further described below. Should substantial comments be received, the RSWG will again consider those comments and make revisions as they see fit. At this same time, the RSAB will consider the proposal. Should substantial changes be made, additional community calls for comment should be issued by the RSAB, and again comments considered by the RSWG. Once all comments have been been addressed, the RSWG chairs will submit the proposal to the RSAB for its consideration. Within a reasonable period of time, the RSAB will then poll on the proposal. Positions may be as follows: * “YES”: the proposal should be approved * “CONCERN”: the proposal raises substantial concerns that must be addressed. * “RECUSE”: the person holding the position has a conflict of interest. Anyone holding a “CONCERN” position must explain their concern to the community in detail. The explanation may or may not be actionable. A CONCERN may be made for two reasons: The proposal represents a serious problem for the group a particular member represents. The member believes that the proposal would cause serious harm to the overall series, including harm to the long term health and viability of the series. No CONCERN should ever come as a surprise to the RSWG. If a CONCERN exists, discussion will take place within the RSWG. Again, all RSAB members are expected to participate. A proposal without any CONCERN positions is approved. If substantial changes have been made in order to address CONCERN positions, an additional call for community input might be necessary. If, after a suitable period of time, any CONCERN positions remain, a formal vote of the RSAB is taken. If a majority of RSAB members vote to approve, the proposal is approved. Otherwise, it is returned to the RSWG. In the case of a tie, the proposal is approved. When a proposal is approved, a notification is sent to the community, and the document enters the queue for publication as an RFC. ISSUE #22: In which stream are these documents published? Is a new stream (e.g., the “Editorial Stream”) needed?

When a community call for comment is made, the RSAB sends a notice containing: A subject line beginning with ‘Call for Comment:’ A clear, concise summary of the proposal A URL for the proposal document Any commentary or questions for the community that the RSAB deems necessary (using their usual decision-making procedures) Clear instructions on how to provide public comments A deadline for comments Notices will always be sent to the rfc-interest mailing list. The RSAB and RSWG should also send notices to other communities that may be interested in or impacted by a proposal as they see fit, following policies for those fora as appropriate. Notices are also to be made available and archived on the rfc-editor.org web site, and other communication channels can be established for notices (e.g., using an RSS feed, social media). A comment period will not last less than two weeks. Comments will be publicly archived on the rfc-editor.org web site. NOTE: This section is intended to address ISSUE #67.

Appeals of RSWG decisions shall be made to the RSAB. Decisions of the RSWG can only be appealed on grounds of failure to follow the correct process. Appeals should be made within 30 days of any action, or in the case of failure to act, of notice having been given to the RSWG. The RSAB will then decide if the process was followed and will direct RSWG chairs as to what procedural actions are required. Appeals of RSAB decisions shall be made to the IAB and should be made within thirty (30) days of public notice of the relevant RSAB decision (typically, when minutes are posted). The appeals body shall decide whether a process failure occurred and what if any corrective action should take place. NOTE: This section is intended to address ISSUE #16 and ISSUE #36.

The IETF anti-harassment policy also applies to the RSWG and RSAB, which strive to create and maintain an environment in which people of many different backgrounds are treated with dignity, decency, and respect. Participants are expected to behave according to professional standards and demonstrate appropriate workplace behavior. See also , , and .

NOTE: Discussion continues within the RFCED-Future Program regarding the roles and responsibilities of an expert in technical publication processes. To retain flexibility (e.g., as to whether this individual plays more of an advisory role or more of a singular leadership role), this document temporarily refers to the individual as the “RFC Series Editor/Advisor” (“RSEA”). The RFC Series Editor/Advisor (RSEA) is a senior technical publishing professional who will apply their deep knowledge of technical publishing processes to the RFC series. The primary responsibilities of the RSEA are as follows: Serve as a voting member on the RSAB. Identify problems with the RFC publication process and opportunities for improvement. Provide expert advice regarding policy proposals within the RSWG. If requested, provide expert advice to the RPC and IETF LLC. Matters on which the RSEA might be consulted could include proposed changes to the RFC style guide , RFC formatting in general, web presence, copyright matters, archiving policy, and dissemination and cataloguing of RFCs. NOTE: This section is intended to address ISSUE #12 and ISSUE #24.

The RSEA will be selected by a search committee formed by the IETF Executive Director, taking into account the role definition as well as other information that the committee deems necessary or helpful in making its decision.

Periodically, the IETF Executive Director will send out to the community a call for input on the performance of the RSEA. The evaluation will be based on criteria specified in the role definition. Criteria could include matters such as the following: Was the RSEA an active participant in RSWG/RSAB discussions and meetings? Did the RSEA provide useful advice to the RSWG and RPC? Did the RSEA exercise good judgment in RSAB decision making? Was the RSEA effective in advising the community on policy direction? The IETF Executive Director will review the feedback, consulting with stream manager representatives, and then produce a recommendation to the IETF LLC Board. The LLC will then make a decision, taking into account the IETF Executive Director’s recommendation. Whether the RSEA role is structured as a contractual or employee relationship is a matter for the IETF LLC and the IETF Executive Director to determine.

Publication of RFCs shall be continue to be handled by the RFC Production Center (RPC) function in accordance with high-level policies currently in force or yet to be defined following the processes specified in the foregoing sections of this document. All matters of budget, timetable and impact on its performance targets, are between the RPC and IETF LLC. The RPC shall report regularly to the RSAB, RSWG, and broader community regarding the contents and progress of its work program and any key risks or issues affecting it. In the event that the RPC is required to make a decision without consultation that would normally deserve consultation, or makes a decision against the advice of the RSAB, then it must notify the RSAB. This document does not specify the exact relationship between the IETF LLC and the RPC function; for example, the RPC function could be provided by a separate corporate entity under contract to the IETF LLC, it could be performed by employees of the IETF LLC, or the IETF LLC could work with independent contractors for some or all aspects of the RPC function. The exact relationship is a matter for the IETF LLC and the IETF Executive Director to determine. The IETF LLC has authority over negotiating performance targets for the RPC and also has responsibility for ensuring that those targets are adhered to. The IETF LLC is empowered to appoint a manager or to convene a committee to complete these activities. Community members who have concerns about the performance of the RPC can request that the IETF LLC look into the matter. Even if the IETF LLC opts to delegate this activity, concerns should be raised with the IETF LLC. The IETF LLC is ultimately responsible to the community via the mechanisms outlined in its charter.

Under and consistent with the high-level policies defined for the RFC Series in general or particular streams, the RPC shall define more particular policies regarding matters related to the editorial preparation and final publication and dissemination of RFCs. Examples include: Maintenance of a styleguide that defines editorial standards to which RFCs must adhere (see and related updates). Policies regarding the file formats that are accepted as input to the editing and publication process. Policies regarding the final structure and layout of published documents; in the context of the XML vocabulary (), such policies could include matters such as the exact XML elements and attributes used to capture the semantic content of RFCs.

NOTE: This section is intended to address ISSUE #59 and ISSUE #6. During the process of editorial preparation and publication, disagreements can arise between the authors of an RFC-to-be and the RPC. Where an existing policy clearly applies, typically such disagreements are handled in a straightforward manner through direct consultation between the authors and the RPC, sometimes in collaboration with other individuals such as a document shepherd, IETF working group chair, IRSG research group chair, or IETF Area Director. However, if it is unclear whether an existing policy applies, or if the interpretation of an existing policy is unclear, the parties may need to consult with additional individuals or bodies (e.g., RSAB, IESG, IRSG, or stream manager) to help achieve a resolution. The following points are intended to provide more particular guidance. If there is a conflict with a policy for a particular stream, the RPC should consult with the relevant stream manager to help achieve a resolution, if needed also conferring with a per-stream body such as the IESG or IRSG. If there is a conflict with a cross-stream policy, the RPC should consult with the RSAB to achieve a resolution. If the disagreement raises a new issue that is not covered by an existing policy or that cannot be resolved through consultation between the RPC and other relevant individuals and bodies as described above), the issue should be brought to the RSWG in order to formulate a new policy. However, in the interest of time the disagreement may be resolved as the parties best see fit while the RSWG formulates a more general policy.

The exact implementation of the administrative and contractual activities described here are a responsibility of the IETF LLC.

Vendor selection is done in cooperation with the streams and under the final authority of the IETF LLC. The IETF LLC develops the work definition (the Statement of Work) for the RPC and manages the vendor selection process. The work definition is created within the IETF LLC budget and takes into account the stream managers and community input. The process to select and contract for an RFC Production Center and other RFC-related services, is as follows: The IETF LLC establishes the contract process, including the steps necessary to issue an RFP when necessary, the timing, and the contracting procedures. The IETF LLC establishes the Selection Committee, which will consist of the IETF Executive Director and other members selected by the IETF LLC in consultation with the stream managers. The Committee shall select a chair from among its members. The Selection Committee selects the vendor, subject to the successful negotiation of a contract approved by the IETF LLC. In the event that a contract cannot be reached, the matter shall be referred to the Selection Committee for further action.

The expenses discussed in this document are not new expenses. They have been and remain part of the IETF LLC budget. The RFC Series portion of the IETF LLC budget shall include funding to support the RSE/A, RFC Production Center, and the Independent Stream. The IETF LLC has the responsibility to approve the total RFC Editor budget (and the authority to deny it). All relevant parties must work within the IETF LLC budgetary process.

NOTE: This section is intended to address ISSUE #22.

This document creates the Editorial Stream. Any and all future documents produced by the RSWG and approved by the RSAB shall be published in the Editorial Stream.

Creation and deletion of streams within the RFC Series shall be accomplished within the Editorial Stream: proposals for such changes shall be made in the RSWG and, if approved by the RSAB, such changes shall be documented in RFCs published within the Editorial Stream.

This document defines several functions within the overall RFC Editor structure, and it places the responsibility for coordination of registry value assignments with the RFC Production Center. The IETF LLC will facilitate the establishment of the relationship between the RFC Production Center and IANA. This document does not create a new registry nor does it register any values in existing registries, and no IANA action is required.

The same security considerations as those in apply. The processes for the publication of documents must prevent the introduction of unapproved changes. Since the RFC Editor maintains the index of publications, sufficient security must be in place to prevent these published documents from being changed by external parties. The archive of RFC documents, any source documents needed to recreate the RFC documents, and any associated original documents (such as lists of errata, tools, and, for some early items, originals that are not machine readable) need to be secured against any kind of data storage failure. The IETF LLC should take these security considerations into account during the implementation and enforcement of the RFC Editor component contracts.

The RSWG and RSAB together provide a public process by which policies for the RFC series can be defined. It is expected that these bodies will therefore cover some of the responsibilities of the RFC Series Editor under Version 2.

In practice, the relationships and lines of authority and responsibility between the IAB, RSOC, and RSE have proved unwieldy and somewhat opaque. To overcome some of these issues, this document dispenses with the RSOC.

This document has no actions for IANA.

This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document is a self-consistent, organized compilation of the process as it was known at the time of publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The IETF policies about rights in Contributions to the IETF are designed to ensure that such Contributions can be made available to the IETF and Internet communities while permitting the authors to retain as many rights as possible. This memo details the IETF policies on rights in Contributions to the IETF. It also describes the objectives that the policies are designed to meet. This memo obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces Section 10 of RFC 2026. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. IAB The RFC Editor performs a number of functions that may be carried out by various persons or entities. The RFC Editor model presented in this document divides the responsibilities for the RFC Series into four functions: The RFC Series Editor, the Independent Submission Editor, the RFC Production Center, and the RFC Publisher. It also introduces the RFC Series Advisory Group and an (optional) Independent Submission Stream Editorial Board. The model outlined here is intended to increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC series, while maintaining RFC quality and timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. This memo provides information for the Internet community. IAB The RFC Editor model described in this document divides the responsibilities for the RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described, as is the relationship between the IETF Administrative Oversight Committee (IAOC) and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620, and obsoletes that document. This document is not an Internet Standards Track specification; it is published for informational purposes. This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force. The guidelines recognize the diversity of IETF participants, emphasize the value of mutual respect, and stress the broad applicability of our work.This document is an updated version of the guidelines for conduct originally published in RFC 3184. The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF participants and coming to (at least rough) consensus on technical matters. In particular, the IETF is supposed not to be run by a "majority rule" philosophy. This is why we engage in rituals like "humming" instead of voting. However, more and more of our actions are now indistinguishable from voting, and quite often we are letting the majority win the day without consideration of minority concerns. This document explains some features of rough consensus, what is not rough consensus, how we have gotten away from it, how we might think about it differently, and the things we can do in order to really achieve rough consensus.Note: This document is quite consciously being put forward as Informational. It does not propose to change any IETF processes and is therefore not a BCP. It is simply a collection of principles, hopefully around which the IETF can come to (at least rough) consensus. This document describes the fundamental and unique style conventions and editorial policies currently in use for the RFC Series. It captures the RFC Editor's basic requirements and offers guidance regarding the style and structure of an RFC. Additional guidance is captured on a website that reflects the experimental nature of that guidance and prepares it for future inclusion in the RFC Style Guide. This document obsoletes RFC 2223, "Instructions to RFC Authors". IETF Participants must not engage in harassment while at IETF meetings, virtual meetings, or social events or while participating in mailing lists. This document lays out procedures for managing and enforcing this policy.This document updates RFC 2418 by defining new working group guidelines and procedures. This document updates RFC 7437 by allowing the Ombudsteam to form a recall petition without further signatories. This document defines the "xml2rfc" version 3 vocabulary: an XML-based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the v2 grammar described in RFC 7749. The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process. The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This document sets out the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026. This document also obsoletes RFCs 3979 and 4879. This RFC marks the fiftieth anniversary for the RFC Series. It includes both retrospective material from individuals involved at key inflection points as well as a review of the current state of affairs. It concludes with thoughts on possibilities for the next fifty years for the Series. This document updates the perspectives offered in RFCs 2555 and 5540. The IETF Administrative Support Activity (IASA) was originally established in 2005. In the years since then, the needs of the IETF evolved in ways that required changes to its administrative structure. The purpose of this RFC is to document and describe the IETF Administrative Support Activity, version 2.0 (IASA 2.0). It defines the roles and responsibilities of the IETF Administration LLC Board (IETF LLC Board), the IETF Executive Director, and the Internet Society in the fiscal and administrative support of the IETF standards process. It also defines the membership and selection rules for the IETF LLC Board.This document obsoletes RFC 4071, RFC 4333, and RFC 7691. The IETF Anti-Harassment Procedures are described in RFC 7776.The IETF Administrative Oversight Committee (IAOC) has been replaced by the IETF Administration LLC, and the IETF Administrative Director has been replaced by the IETF LLC Executive Director. This document updates RFC 7776 to amend these terms.RFC 7776 contained updates to RFC 7437. RFC 8713 has incorporated those updates, so this document also updates RFC 7776 to remove those updates. The RFC Editor model described in this document divides the responsibilities for the RFC Series into three functions: the RFC Series Editor, the RFC Production Center, and the RFC Publisher. Internet Architecture Board (IAB) oversight via the RFC Series Oversight Committee (RSOC) is described, as is the relationship between the IETF Administration Limited Liability Company and the RSOC. This document reflects the experience gained with "RFC Editor Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to replace all references to the IETF Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 Model. This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This document obsoletes RFC 4844. This document describes the function and responsibilities of the RFC Independent Submission Editor (ISE). The Independent Submission stream is one of the stream producers that create draft RFCs, with the ISE as its stream approver. The ISE is overall responsible for activities within the Independent Submission stream, working with draft editors and reviewers, and interacts with the RFC Production Center and Publisher, and the RFC Series Editor (RSE). The ISE is appointed by the IAB, and also interacts with the IETF Administration Limited Liability Company (LLC).This version obsoletes RFC 6548 to replace all references to the Internet Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 structure. This document provides a set of guidelines for working groups that choose to use GitHub for their work.

Portions of this document were borrowed from , , , and earlier proposals within the RFCED-Future Program by Martin Thomson, Brian Carpenter, and Michael StJohns. Thanks to the chairs of the Program, Eliot Lear and Brian Rosen, for their leadership and assistance. Thanks also for feedback and proposed text and feedback to Jari Arkko, Sarah Banks, Scott Bradner, Carsten Bormann, Nevil Brownlee, Ben Campbell, Jay Daley, Martin Duerst, Lars Eggert, Adrian Farrel, Stephen Farrell, Sandy Ginoza, Bron Gondwana, Joel Halpern, Wes Hardaker, Bob Hinden, Russ Housley, Christian Huitema, John Klensin, Mirja Kuehlewind, Ted Lemon, John Levine, Lucy Lynch, Andrew Malis, Larry Masinter, S. Moonesamy, Mark Nottingham, Tommy Pauly, Colin Perkins, Julian Reschke, Eric Rescorla, Adam Roach, Alice Russo, Doug Royer, Rich Salz, Tim Wicinski, and Nico Williams.