As previously discussed, the IAB is seeking an additional chair or chairs for the RFC Editor Future Development Program.
This program is modeled on an IETF working group, and will use its mailing list (email@example.com) to develop and validate consensus among the participants.
The program currently has one chair, Eliot Lear. The current IAB has received significant feedback from the community that a second chair needs to be selected, and the IAB is eager to fill that position with a great candidate as soon as is practical. The IAB is now seeking at least one additional chair from outside the IAB to join Eliot. Together, these chairs will set the detailed agenda, manage the program, and call consensus among the participants. The program also has two liaisons from the IAB to assist with logistical matters, Wes Hardaker and Jared Mauch.
If you are interested in serving in this role, please send a short email message to firstname.lastname@example.org and email@example.com with your motivation and information concerning your familiarity with IETF working groups or similar processes. The deadline for volunteering is Tuesday, 2020-05-12 at 2359 UTC. The IAB will then solicit public comments on the candidates before making a decision.
The IAB has selected Eliot Lear to serve as chair of the RFC Editor Future Development Program.
The IAB thanks all of the candidates who were willing to serve. This was a difficult decision with many strong candidates.
Like an IETF working group, this program will have completely open participation. The program will use the mailing list firstname.lastname@example.org. To subscribe, please go to <https://www.iab.org/mailman/listinfo/rfced-future>.
Future details about the operation of the program will be coming shortly.
Here is the IAB report for the period between IETF 106 and IETF 107. If you have issues you want to discuss by email, feel free to send your comments to the IAB as whole at email@example.com; more detail on many of the topics is also available at https://www.iab.org. Continue reading
The IAB has published RFC 8752: Report from the IAB Workshop on Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE).
Abstract: The Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE) Workshop was convened by the Internet Architecture Board (IAB) in July 2019. This report summarizes its significant points of discussion and identifies topics that may warrant further consideration.
Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB views and positions.
On 2020-03-04, the IAB approved a new conflict of interest policy for the Internet Architecture Board.
The IAB has published RFC 8730: Independent Submission Editor Model.
Abstract: 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).
The IAB has published RFC 8729: The RFC Series and RFC Editor.
Abstract: 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.
The IAB has published RFC 8728: RFC Editor Model (Version 2).
Abstract: 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.
The IAB has published RFC 8722: Defining the Role and Function of IETF Protocol Parameter Registry Operators.
Abstract: Many Internet Engineering Task Force (IETF) protocols make use of commonly defined values that are passed in messages or packets. To ensure consistent interpretation of these values between independent implementations, there is a need to ensure that the values and associated semantic intent are uniquely defined. The IETF uses registry functions to record assigned protocol parameter values and their associated semantic intentions. For each IETF protocol parameter, it is current practice for the IETF to delegate the role of Protocol Parameter Registry Operator to a nominated entity. This document provides a description of, and the requirements for, these delegated functions. This document obsoletes RFC 6220 to replace all references to the IETF Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 Model.