Here is the IAB report for the period between IETF 105 and IETF 106. If you have topics or issues you want to discuss by email, feel free to send your comments to firstname.lastname@example.org (our public discussion list) or email@example.com (to reach just the IAB). Questions at the open mic at the IETF 106 plenary are, of course, also welcome.
The IAB has a few chartered roles. It confirms the appointments to the IESG, performs standards process oversight, and handles appeals. It also performs architectural oversight (including appointing the IRTF Chair), appoints the RFC series editor and oversight committee, manages the IETF’s relationship with IANA, and handles liaisons and appointments both to ISOC and to other organizations.
Here’s what the IAB has been doing since our last report; more detail on many of the topics is available at https://www.iab.org.
There were no appeals during this period.
The IAB made one public statement during this period, calling out the unintended consequences of policy and regulatory proposals.
As part of its appointments role, the IAB has filled a number of positions since our last report. Notable among them was Adrian Farrel being re-appointed as Independent Submissions Editor for a new two-year term, beginning in February of 2020. The IAB thanks Adrian for his continuing service.
The IAB also appointed Peter Koch to the ICANN NomCom.
In addition, the IAB has opened nominations for the Internet Society Board of Trustees selection. Sean Turner, the incumbent, has now served two terms in succession and is thus not eligible for another term. The IAB thanks him for service, and we encourage candidates to apply or to contact the IAB for more details.
You can always find the documents the IAB has adopted and is working on at https://datatracker.ietf.org/stream/iab.
One cluster of IAB documents are those that originally arose out of the IASA 2 effort. Of those, the following drafts are currently are currently in the queue for publication:
draft-ietf-iasa2-rfc4844-bis-05: The RFC Series and RFC Editor
draft-ietf-iasa2-rfc6220bis-04: Defining the Role and Function of IETF Protocol Parameter Registry Operators
draft-ietf-iasa2-rfc6548bis-02: Independent Submission Editor
draft-ietf-iasa2-rfc6635bis-04: RFC Editor Model (Version 2)
In addition, draft-iab-fiftyyears-01: Fifty Years of RFCs, the RSE’s review of the RFC Series first 50 years, is in queue.
A number of other drafts are in preparation or community review, and comments on these are welcome at firstname.lastname@example.org or in comments to the IAB:
draft-iab-escape-report-00: Report from the IAB Workshop on Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE)
draft-iab-for-the-users-00: The Internet is for End Users
draft-iab-protocol-maintenance-04: The Harmful Consequences of the Robustness Principle
draft-iab-rfc7500-bis-00: Principles for Operation of Internet Assigned Numbers Authority (IANA) Registries
draft-iab-use-it-or-lose-it-00: Long-term Viability of Protocol Extension Mechanisms
The IAB organizes its long term work, for the most part, into programs. There are basically two classes: management programs and architectural programs. The former are how we handle the oversight of various things, and the latter are where we do architectural work. The former are expected to last as long as the IAB continues to have that oversight function; the latter last until the IAB has come to a conclusion on the relevant group of topics or has decided that the topic needs to be reframed. Programs are listed at https://www.iab.org/activities/programs/. As a general rule, each architectural program has a public mailing list, as well as a member-specific list. For subscription instructions, see https://www.iab.org/iab-mailing-lists/.
Among the management programs, RSOC is no doubt top of mind for many folks because of the RSE transition. Among its activities were a consultation with the community on that transition and the preparation of an SOW for an interim RFC Series Project Manager. The IAB transmitted that to the IETF LLC on October 2nd and the IETF LLC subsequently issued an RFP.
There were no workshops during this period, but the workshop reports are in preparation for the Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE) workshop and the Design Expectations vs. Deployment Reality in Protocol Development (DEDR) workshop.
for the IAB