Internet Architecture Board


About the Internet Architecture Board

The Internet Architecture Board provides long-range technical direction for Internet development, ensuring the Internet continues to grow and evolve as a platform for global communication and innovation.

In its work, the IAB strives to:

  • Ensure that the Internet is a trusted medium of communication that provides a solid technical foundation for privacy and security, especially in light of pervasive surveillance,
  • Establish the technical direction for an Internet that will enable billions more people to connect, support the vision for an Internet of Things, and allow mobile networks to flourish, while keeping the core capabilities that have been a foundation of the Internet’s success, and
  • Promote the technical evolution of an open Internet without special controls, especially those which hinder trust in the network.

IAB Seeks Feedback on Appointment to ICANN Technical Liaison Group

The IAB names two technical experts to the ICANN Technical Liaison Group (TLG). The TLG is tasked with connecting the ICANN Board with appropriate sources of technical advice on specific matters pertinent to ICANN’s activities.

Warren Kumari and Paul Wouters are the current experts. Paul’s current term ends in early 2017; he has indicated that he is willing to serve for an additional two-year term.

The IAB would like to solicit comments from the community on the performance of Paul Wouters on the ICANN TLG. Please send comments to iab-chair at and execd at

We would appreciate receiving comments by Wednesday, October 26.

Call for IAOC Nominations and Volunteers 2017

This is a call for nominations for the IAB appointment to the IETF Administrative Oversight Committee (IAOC). The nomination period will close on 2 November 2016.

IAOC membership is described in BCP 101 (RFC 4071) Section 4, with selection guidelines and process documented in BCP 113 (RFC 4333). In alternate years, the IESG and the IAB each select one person for a two-year IAOC term. This year, the IAB will select one person for a term beginning in March 2017. Note that the NomCom is also selecting an IAOC member.

Candidates for these IAOC positions should have knowledge of the IETF, knowledge of contracts and financial procedures, and familiarity with the administrative support needs of the IAB, the IESG, and the IETF standards process. Candidates are also expected to be able to understand the respective roles and responsibilities of the IETF and ISOC in this activity, and be able to articulate these roles within the IETF community.

Acceptable candidates must be prepared to exercise all the duties of an IAOC member. These responsibilities include, but are not limited to, the setting (in consultation with the community and after carefully considering their input) of administrative support policies, oversight of the administrative operations of the IETF, and representing the interests of the IETF to the IAOC. The IAOC meets for a couple of hours at each IETF meeting, holds two conference calls each month, and meets for two days in a separate meeting, usually in May. Acceptable candidates must be able to undertake full participation in all IAOC meetings and activities.

IAOC members also serve as the trustees of the IETF Trust. Please note that the role of the IETF Trust is expanding as part of the IANA stewardship transition.

The IAB-selected member of the IAOC does not directly represent the IAB. The IAB and IESG selected members are accountable directly to the IETF community. As such, candidates do not need to be current members of the IAB or the IESG and, in fact, we prefer nominations and volunteers from the rest of the community.

If you are interested in serving on the IAOC, or know of someone who may be a good fit for this position, please send the name and email address to <> and <>.

The IAB will respond with a questionnaire, asking for the candidates’ qualifications and willingness to serve.

The names of all people who declare themselves willing to serve will be made public on the list after the end of the solicitation period. The plan is to post the list of candidates by 4 November 2016.

The IAB expects to make a decision in December 2016.

IAB Seeks Feedback on IETF Appointment to the ICANN NomCom

The IAB (on behalf of the IETF) has been asked to supply a member to the 2017 ICANN Nominating Committee (NomCom). Last year, Tim Wicinski did the job for the IETF community, and he is willing to serve again.

The IAB would like to solicit comments from the community on the performance of Tim Wicinski on the ICANN NomCom. We are interested in comments on what has gone well or badly over the past year.

Please send comments to iab-chair at and execd at

We would appreciate receiving comments by Wednesday, September 28, as the IAB will begin the next steps in this appointment process shortly so that the ICANN NomCom member can attend the first formal meeting of the 2017 NomCom in Hyderabad, India in November 2016.

Allison Mankin to be next IRTF Chair

After having served as IRTF chair since 2011, Lars Eggert will step down as Internet Research Task Force (IRTF) chair during IETF 98 in March 2017.

The IAB has appointed Allison Mankin as his successor, and in the months to come Allison will be working with Lars in transitioning responsibilities.

Allison Mankin is an Internet protocol lead and researcher based in the Washington DC area, and holds the position of Senior Director, Public DNS, at Salesforce.  She has a long history in and around the IETF and IRTF, including serving as Nomcom Chair, Transport AD (most recently stepping down in 2006), and IPng AD.  In the IRTF, she chaired the Reliable Multicast RG and then moved it to the IETF as the RMT WG.  She has worked in a diverse set of industry, academic and government settings.  Some of her positions prior to Salesforce were at Verisign, JHU Applied Physics Lab, the US National Science Foundation (NSF), Bell Labs, and USC/ISI.  As a program director at the US NSF, Allison was a leader of the Future Internet Design (FIND) program, which initiated the funding of info-centric networking and also played an early role in software-defined networking.

The IAB would like to thank Lars for serving the community by fulfilling the role with zeal and thank Allison for taking up the responsibility.  The IAB would also like to thank the other volunteers for this position; with so many good candidates, it was a difficult choice for the IAB.

For more information about the IRTF, please see

IAB approves RFC format-related drafts for publication

On 3 August 2016, the IAB approved the drafts [1] documenting the requirements for the new RFC format for publication. The RFC Format project goals include:

  • Supporting XML as the unchanging, underlying format
  • Creating TXT, PDF/A-3, and HTML as the outputs
  • Allowing SVG line art (black and white) as per a limited SVG profile
  • Allowing Non-ASCII characters in a controlled fashion

An FAQ about the new RFC Format is available online: Continue reading

Report from the IAB before IETF 96

Dear colleagues,

This is the usual IAB report to the community about our activities since the previous meeting (in this case, since IETF 95 in Buenos Aires). As ever, we hope that this form allows you to prepare topics you might want to discuss during the open mic. But of course, if you have views you want to make known by email, we’re easy to reach: send mail to to reach our public discussion list, and 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, we manage the RFC series and the IETF’s relationship with IANA, and we handle liaisons 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 IETF 95. You can find mention of each of these on the IAB pages at (where there’s more background, too). Continue reading