Originally posted on 2017-07-16.
Continuing the tradition started by Andrew Sullivan, here is the IAB report to the community about our activities. We hope that this information allows you to prepare topics you might want to discuss during the upcoming open mic time. Of course, if you have issues you want to discuss by email, feel free to send your comments to email@example.com (our public discussion list) or firstname.lastname@example.org (to reach just the IAB).
The IAB has a few chartered roles. We confirm the appointments to the IESG and perform standards process oversight and handle appeals. We also perform architectural oversight (including appointing the IRTF Chair), we manage the RFC series and the IETF’s relationship with IANA, and we handle liaisons and appointments both to ISOC and to other organizations. We try to ensure that anything we do is part of one of these areas of responsibility, and we try to make sure these are all covered.
Here’s what we’ve been doing since our last report at IETF 98. You can find mention of each of these on the IAB pages at https://www.iab.org (where there’s more background, too).
First, I’m happy to note that there were no appeals during this period. (Appeals and standards process oversight)
In late March, the IAB published a statement on the registration of special use names in the ARPA domain. This comment focused on the distinction between creating an entry in the Special Use Names registry and requesting a delegation within the DNS, and it reminded the community that .arpa was an appropriate choice for delegations that met the conditions in RFC 3172. (Architecture)
In early May, the IAB provided comments on ICANN’s draft IDN implementation guidelines. (Architecture)
In mid-May, the IAB formed a search committee to seek a successor for Nevil Brownlee as Independent Series Editor, as documented in RFC 6548. The committee gathered suggestions and comments from the community and will be conducting interviews at the Prague IETF. Additional comments may be provided to the committee at email@example.com. (RFC Series)
Also in mid-May, the IAB held its annual retreat, including some joint time with the IESG. Among the topics the IAB discussed was the upcoming set of work on 5g. Jari Arkko and Jeff Tantsura have written a blog post on 5g that captures some of the related topics. The IAB is also a host of a lunch meeting on Tuesday of this IETF, where 3GPP colleagues will be available to discuss “3GPP & IETF collaboration on 5g”. Interested folks should join us in Congress Hall III or via the remote streams. Another topic from the retreat was a look back at RFC 4084, captured in a blog post on the meaning of “Internet Access”. As that post notes, we’d be happy for any comments on that topic to be sent to firstname.lastname@example.org .(Architecture)
Later in May, the IAB sent a Liaison Statement to the Unicode technical committee on the relationship of Unicode Technical Standard #39 to IETF work. There have since been several informal meetings with Unicode leaders on how to encourage increased cooperation between the two groups, and we expect to continue to work toward that end over the next year. (Liaisons and appointments)
During June, the IAB made three appointments to the Community Coordination Group as required by RFC 8090. Russ Housley and Barry Leiba were appointed for two years and Andrew Sullivan for one year. The IETF representatives then selected Russ as CCG Co-chair, and the IAB confirmed him in that post. We thank each of them for their service. (Liaisons and appointments)
A bit later in June, the IAB reappointed Jim Reid to the ICANN Root Zone Evolution Review Committee, the appointment being required by RFC 8128. We appreciate Jim’s willingness to serve again. (Liaisons and appointments).
During early July the RSOC program developed a draft Statement of Work for the RFC Series Editor, which will go out for public comment this week. Under the current timeline, the RSOC will make a recommendation to the IAB in late September, with the RSE term to begin January 1, 2018 (RFC Series)
You can always find the documents the IAB has adopted and is working
on at https://datatracker.ietf.org/stream/iab.
RFCs published since the last report are:
- Coordinating Attack Response at Internet Scale (CARIS) Workshop Report
- Appointment Procedures for the IETF Representatives to the Community Coordination Group (CCG)
- IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
- Digital Preservation Considerations for the RFC Series
- Planning for Protocol Adoption and Subsequent Transitions
There are some workshop reports still in process:
Report from the Internet of Things (IoT) Software Update (IoTSU)
Workshop 2016 (with the RFC Editor now)
IAB Workshop on Managing Radio Networks in an Encrypted World
(MaRNEW) Report (undergoing community review)
The IAB organizes its 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/.
We review these programs periodically. In the period since our last report, the IAB made several personnel changes to recognize the change in the composition of the IAB, as well as charter updates to the Stack Evolution and Privacy and Security programs. The IAB also chose to close down the Internationalization program. This was not because of a lack of focus on that topic; rather, the IAB felt the need to reframe some of the issues related to Internationalization and identifiers in Internet contexts. For more on that, see the Workshop section below.
The Plenary Planning Program works to arrange a tech plenary topic for each meeting that is currently topical, broadly interesting to the IETF community as a whole, and for which we can engage interesting speakers. When it can’t have all three, the IAB does not schedule a tech plenary. Unfortunately, this time we didn’t get to all three in time for Prague, but the program is already working on an IETF 100 technical plenary.
In June, the IAB sent out a call for participation in a workshop on Internet naming systems that explicitly called out their resolution method or context. We invite position papers on this topic to be submitted by July 28, 2017 to email@example.com. Decisions on accepted submissions will be made by August 11, 2017. The final logistics for the workshop will be announced as soon as possible; some late information on conflicts mean that the original date announced will likely change.
for the IAB