Skip to main content

NomCom 2015 Concluded

Desired expertise

These pages contain the current summaries of desired expertise for open positions, provided to the NomCom by the IESG, IAB, and IAOC. As the NomCom proceeds, per BCP 10, we receive input from the community on the qualifications required for the positions. The NomCom bases selections on all of this information. These pages may be updated periodically.

The IAB is chartered both as a committee of the IETF and as an advisory body of the Internet Society. The IAB acts as a source of advice and guidance concerning technical, architectural and procedural matters pertaining to the Internet and its enabling technologies; this includes both reviewing proposed new work and providing input to the IESG as well as providing perspective to the broader community on important issues. The IAB develops and documents architectural insight and guidance for the Internet. It provides architectural input into IETF technical activities as well as sponsoring and organizing work in the IRTF. The IAB also has several procedural roles to support the operation of the IETF including being the formal channel for liaisons with other organizations.

Architectural role

The IAB oversees various aspects of the architecture for the protocols and technical specifications as developed by the IETF, as well as overseeing activities in the IRTF. While the IAB does draw on specific expertise as required, it is expected that the sum of the expertise of IAB members encompasses a broad range of technologies under IETF and IRTF study, and also encompasses a broad range of perspectives on these specifications, from research and academic study through development, deployment and operational experience.

A major role of the IAB is to take a broad and long range perspective to offer input into the planning and coordination among different areas of Internet activities, including those of the IETF and IRTF. The IAB, both collectively and on an individual basis, is expected to pay attention to important long-term issues in the Internet, and to make sure that these issues are brought to the attention of the groups that are in a position to address them. The IAB maintains open communications channels with other bodies engaged in Internet governance, including ICANN, the Regional Internet Registries, and ISOC, and provides technical and architectural input as appropriate. As needed, the IAB works with ISOC to provide advice and guidance to the Internet community on technical, architectural, procedural, and policy matters pertaining to the Internet and its enabling technologies. That advice and guidance are provided to the public, to the Board of Trustees and Officers of the Internet Society, and to the larger community as circumstances dictate.

Organizational role

The IAB has a number roles within the organizational functioning of the IETF. While these roles require administrative rather than technical work, they form a large and important part of the IABs activities. All IAB members need to be prepared to participate (to varying degrees) in these activities.

The IAB serves as an appeal board for complaints of improper execution of the standards process, acting on appeals in respect of IESG standards decisions. In addition, the IAB appoints ISOC BoT members as well as a member of the IAOC, and hears appeals on matters related to the IAOC and IAD.

The IAB is responsible for the RFC Editor function, including appointing and overseeing the RFC Series Editor. The IAB provides direction for the administration of the IETF's protocol parameters registries (the IANA function). The IAB selects a chair of the Internet Research Task Force (IRTF) for a renewable two year term, and oversees the IRTF's activities.

The IAB has a role in the IETF Nominations Committee process: the IAB confirms the IETF Chair and the Area Directors (IESG).

The IAB is responsible for liaisons between the IETF and other organizations that undertake activities that overlap or intersect with the IETF's activities including other standards development organizations. The IAB appoints liaison managers to manage these relationships, and deals with liaison matters of an architectural or general procedural nature. The IAB becomes actively involved when these liaison relationships have difficulties, for example, in determining clear boundaries of responsibility. The IAB also appoints a member to the ICANN Nomcom and a liaison to the ICANN board to represent the IETF's interests within ICANN. IAB members fulfill the role of liaison "shepherds" to advise the liaison managers and to act as review point for assessing the efficacy of liaison activities and the liaison manager's duties.

IAB Organization

In order to enhance institutional memory and enable the development of medium and long term activities, the IAB has organized its work in several areas in the form of programs. A program is a high priority, long term activity scoped and managed by the IAB, which can be thought of as an IAB directorate, small task force, or an ad-hoc body of (independent) technical experts (see RFC 2850 Section 2.1). Program outputs include IAB documents and positions. All IAB members are expected to review and comment on program outputs that represent the consensus of the IAB. In order to ensure that all IAB activities have IAB participation, members of the IAB are expected to actively participate in one or more programs.

The program leads, who will usually be IAB members, communicate the program plan to the community, solicit feedback, facilitate activities within the program, provide oversight and ensure continuity. The program lead will typically nominate non-IAB members to the program, subject to IAB approval, will develop the program plan, will organize regular program conference calls, and will develop consensus within the program for recommendations to be made to the IAB. The lead doesn’t need to have specific expertise in the area, but must have good general understanding of the issues from technical, business, and or policy perspective. The IAB as a whole will periodically review the state of the programs and their progress, and make necessary adjustments and prioritization. This includes a review of the program membership, activity plan and progress against deliverables. Current IAB programs include:

o Emergency Services Program
o IANA Evolution Program
o Internationalization Program
o IP Stack Evolution Program
o Liaison Oversight Program
o Privacy and Security Program
o RFC Editor Program
o Names and Identifiers Program
o IETF Protocol Registries Oversight Committee

IAB Member Qualities

IAB members are expected to act at the "Board" level.

The IAB is most effective when it is composed of a diverse set of individuals with a broad range of technical skills, architectural perspectives and backgrounds. For example, it is desirable for IAB members to have technical leadership experience, operational management backgrounds, research or academic backgrounds, implementation experience, and experience in other bodies involved in Internet governance. Likewise it is desirable for IAB members to have had experiences with differing technical challenges and requirements, including those that vary by geographic region. It is critical that IAB members be willing and able to work with each other to develop a shared viewpoint.

Some IAB activities are very specialized - for example, managing liaison relationships with other SDOs on behalf of the IETF. It is advantageous for the IAB when NomCom ensures that at least some IAB members have sufficient managerial skills to understand the issues that need to come to the IAB by managing and documenting inter-SDO liaison relationships on a strategic basis.

While it is advantageous for at least some IAB membership to have expertise in the IAB's current program topics, it is more important for the IAB to have membership who are experienced in managing volunteer teams, and who can build teams, motivate program work, and direct one or more programs even in the absence of in-depth knowledge about specific program topics. The IAB needs at least some members with program management skills that will facilitate interfacing between programs and the IAB.

IAB members

* are normally highly regarded in one or more domains of technical subject matter. They may be recognized in a particular area as being a domain expert, but must also exhibit advanced architectural and technical competence.
* should be willing and able to apply those technical skills and analytic thinking to understand and usefully contribute to discussions in other areas and to have interests broad enough that they are willing and able to contribute to discussions on new areas as appropriate.
* should be willing and able to apply their managerial skills to new areas.
* should be constructive in framing new approaches, technically or in terms of communication.
* should be willing and able to work well with others.
* should be willing and able to constructively contribute to consensus-based processes.
* should have substantial experience within the IETF, and an understanding of its processes and workings.
* should be willing and able to commit the time to follow the IAB, IRTF and IETF discussions on a regular basis. This commitment should extend to regular attendance at IAB teleconferences and attendance in person at IETF meetings, IAB workshops, an annual IAB retreat, as well as the commitment to review material and generate and edit documentation. It may also extend to leading open discussion forums and active participation in IETF WG and IRTF RG activity.

The time commitment in "normal weeks" (i.e., those not containing IETF meetings, retreats, or workshops) is typically one to three days a week or more for IAB members that are fully engaged; simply tracking the various mailing list and documents often takes up to a day a week. IAB members are likely to be tapped by ADs to do reviews of specialized documents and other tasks, potentially adding to those numbers. About a quarter to half of the time is spent on the organizational activities. The time commitment at IETF meetings includes time on Sunday (at the latest, IAB members need to plan to arrive at IETF meetings on the preceeding Saturday), early mornings, Friday afternoon meetings, as well as coverage of BOFs for technical review. An annual retreat will be scheduled for up to three days in late April or early May.

The incumbents are:

* Mary Barnes
* Joe Hildebrand
* Ted Hardie
* Erik Nordmark
* Brian Trammell
* Marc Blanchet

Continuing IAB members are:

* Ralph Droms
* Russ Housley
* Robert Sparks
* Andrew Sullivan
* Dave Thaler
* Suzanne Woolf

Generic expertise is documented at

Specific expertise is documented at

We are recruiting 2 people for this position (out of 3 responsible ADs).

The incumbents are Alissa Cooper and Barry Leiba.

The continuing AD is Ben Campbell.

Generic expertise is documented at

Specific expertise is documented at

The incumbent, Brian Haberman, has indicated that he will decline nominations for another term.

The continuing AD is Terry Manderson.

Generic requirements are at

Specific requirements are at

The sitting Operations AD is Benoit Claise.

The continuing AD is Joel Jaeggli.

Generic requirements are at

Specific requirements are at

The sitting Routing AD is Alia Atlas.

The continuing Routing ADs are Deborah Brungard and Alvaro Retana.

Generic requirements are at

Specific requirements are at

The sitting Security AD is Kathleen Moriarty.

The continuing AD is Stephen Farrell.

Genercic requirements are at

Specific requirements are at

The sitting AD, Martin Stiemerling, has indicated that he will not accept nominations for a new term.

The continuing AD is Spencer Dawkins.