Hubbry Logo
search
logo
Internet Architecture Board avatar
Internet Architecture Board
Internet Architecture Board
current hub
I

Internet Architecture Board

logo
Community Hub0 Subscribers
Read side by side
Internet Architecture Board
View on Wikipedia
from Wikipedia

The Internet Architecture Board (IAB) is a committee of the Internet Engineering Task Force (IETF) and an advisory body of the Internet Society (ISOC). Its responsibilities include architectural oversight of IETF activities, Internet Standards Process oversight and appeal, and the appointment of the Request for Comments (RFC) Editor. The IAB is also responsible for the management of the IETF protocol parameter registries.[1]

History

[edit]

The body which eventually became the IAB was originally the Internet Configuration Control Board (ICCB). It was created by Vint Cerf in 1979 while he was working at the Defense Advanced Research Projects Agency (DARPA) of the United States Department of Defense. In 1983, the ICCB was reorganized by Barry Leiner, Cerf's successor at DARPA, around a series of task forces considering different technical aspects of internetting. The re-organized group was named the Internet Activities Board (IAB).[2][3][4]

The IAB set for itself seven principal foci for the period of 1989 to 1990. These were namely:[5]

  • Operational Stability
  • User Services
  • OSI Coexistence
  • Testbed Facilities
  • Security
  • Getting Big
  • Getting Fast

It finally became the Internet Architecture Board, under ISOC, in January 1992, as part of the Internet's transition from a U.S.-government entity to an international, public entity.

Responsibilities

[edit]

The IAB is responsible for:

  • Providing architectural oversight of Internet protocols and procedures
  • Liaising with other organizations on behalf of the Internet Engineering Task Force (IETF)
  • Reviewing appeals of the Internet standards process
  • Managing Internet standards documents (the RFC series) and protocol parameter value assignment
  • Confirming the Chair of the IETF and the IETF Area Directors
  • Selecting the Internet Research Task Force (IRTF) Chair
  • Acting as a source of advice and guidance to the Internet Society.

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 that hinder trust in the network.

Activities

[edit]

Activities of the IAB include:

Workshops

  • COVID-19 Network Impacts Workshop, 2020
  • Exploring Synergy between Content Aggregation and the Publisher Ecosystem Workshop 2019
  • Design Expectations vs. Deployment Reality in Protocol Development Workshop 2019
    • Position Papers: DEDR Workshop
  • Explicit Internet Naming Systems (EName) Workshop 2017
  • Internet of Things Software Update Workshop (IoTSU) 2016
  • Managing Radio Networks in an Encrypted World (MaRNEW) Workshop 2015
  • Coordinating Attack Response at Internet Scale (CARIS) Workshop 2015
    • Call For Papers
    • Agenda: Coordinating Attack Response at Internet Scale (CARIS) Workshop
  • IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI) 2015
  • W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT) 2014
  • IAB Workshop on Internet Technology Adoption and Transition (ITAT) 2013
  • IAB / IRTF Workshop on Congestion Control for Interactive Real-Time Communication 2012
    • Workshop on Congestion Control: Position Papers
    • Congestion Control Workshop Agenda and Materials
  • Interconnecting Smart Objects with the Internet Workshop 2011
    • Tutorial on Interconnecting Smart Objects with the Internet
    • Position Papers
    • Agenda
  • Internet Privacy Workshop 2010
    • Slides Presentations
    • Minutes of the IAB/W3C/ISOC/MIT Internet Privacy Workshop
    • Meeting Minutes
    • Accepted Position Papers
  • Routing and Addressing Workshop 2006
  • Unwanted Traffic Workshop 2006
  • IAB Wireless Internetworking Workshop 2000

Technical programs and administrative support groups

  • RFC Editor Program: The RFC Series Oversight Committee (RSOC)
  • RFC Editor Future Development Program
  • Plenary Planning Program
  • Internet Threat Model (model-t) Program
  • IETF-IANA Group
    • Evolvability, Deployability, & Maintainability (EDM) Program
  • Concluded Programs
    • Security Program
    • Privacy Program
    • Privacy Reviews
    • IPv6 Privacy Survey
    • Privacy and Security Program
    • Names and Identifiers Program
    • Liaison Oversight Program
    • ITU-T Coordination Program
    • IP Stack Evolution Program
    • IP Evolution
    • Internationalization Program
    • IETF Protocol Registries Oversight Committee (IPROC)
    • IAB Tools and Processes Program
    • Emergency Services

IAB appointments and confirmations

  • Community Coordination Group (CCG): Russ Housley (2017–2021), Barry Leiba (2017–2021), Tim Wicinski (2018–2022)
  • IANA Stewardship Transition Coordination Group (ICG): Russ Housley, Lynn St Amour
  • ICANN Board of Directors Liaison: Harald Alvestrand: (2018–present)
  • ICANN Root Zone Evolution Review Committee (RZERC): Tim (April, 2020–2021)
  • ICANN NomCom: Peter Koch, 2020
  • ICANN Technical Liaison Group (TLG) : Warren Kumari (2019–2021), Petr Špaček (2020–2022)

Responsibilities

[edit]

The IAB's current responsibilities include:[6]

  • Architectural Oversight: The IAB provides oversight of, and occasional commentary on, aspects of the architecture for the network protocols and procedures used by the Internet.
  • Standards Process Oversight and Appeal: The IAB provides oversight of the process used to create Internet Standards. The IAB serves as an appeal board for complaints of improper execution of the standards process, through acting as an appeal body in respect of an Internet Engineering Steering Group (IESG) standards decision.
  • Request for Comments series: The IAB is responsible for editorial management and publication of the Request for Comments (RFC) document series.
  • Internet Assigned Numbers Authority: In conjunction with the Internet Corporation for Assigned Names and Numbers (ICANN), the IAB is responsible for the administration of the assignment of IETF protocol parameter values by the Internet Assigned Numbers Authority (IANA).
  • External Liaison: The IAB acts as representative of the interests of the IETF in liaison relationships with other organizations concerned with standards and other technical and organizational issues relevant to the worldwide Internet.
  • Advice to the Internet Society: The IAB acts as a source of advice and guidance to the board of trustees and Officers of ISOC concerning technical, architectural, procedural, and (where appropriate) policy matters pertaining to the Internet and its enabling technologies.
  • Internet Engineering Steering Group Confirmation: The IAB confirms the IETF Chair and IESG Area Directors, from nominations provided by the IETF Nominating Committee.
  • Internet Research Task Force Chair: The IAB selects a chair of the IRTF for a renewable two-year term.

RFC1087 – Ethics and the Internet and a rise to modernity

[edit]

The IAB takes a formal stance on what constitutes proper use of the Internet in their 1989 memo, RFC 1087: “Ethics and the Internet.”[7] They introduce their contemporary version of the Internet, which at the time was in its nascent stages, serving primarily as a tool for communication of research in the scientific community, and identify the use of this internet as a “privilege.”

The IAB then proclaims as unethical any activity which:

  • seeks to gain unauthorized access to the resources of the Internet,
  • disrupts the intended use of the Internet,
  • wastes resources (people, capacity, computer) through such actions,
  • destroys the integrity of computer-based information
  • compromises the privacy of users.

This memo was written at a time during which the Internet existed in the general research milieu, but since that time the Internet has evolved greatly and expanded its user base. The IAB has accordingly taken new stances on ethical and secure Internet use, such as in RFC 8890, where the IAB identifies protecting end users as the first priority in their maintenance of the Internet.[8]

As such, though their core principles are the same, the IAB's priority for protection has shifted from the technical and scientific community to the community of day-to-day users. In another memo RFC7624, the IAB takes a firm stance against pervasive mass surveillance through the use of the Internet on the part of national intelligence agencies, saying that it is necessary that the Internet technical community, including itself, “address the vulnerabilities exploited [by mass surveillance campaigns]...to ensure that the Internet can be trusted by [its] users.”[9]

RFC 2850 - Charter of the Internet Architecture Board

[edit]

RFC 2850 establishes the structure and purpose of the IAB. The RFC specifies the following:[10]

  • IAB membership: the IAB has 13 members, 1 being the chair of the Internet Engineering Task Force (IETF). These members are appointed to 2-year terms.[10]
  • The Role of the IAB: The IAB serves to provide Architectural Oversight for Internet procedures, and to provide oversight in the process of creating Internet standards, including appeals. Furthermore, the IAB acts as a liaison to the Internet Society (ISOC) to advise regarding architectural and technical issues.[10]
  • IAB Organization: The 13 members of the IAB choose 1 member to serve as the chair of the IAB for a 1-year term. There is no limit to the number of terms that the chair can serve. The executive director of the IAB is chosen by the chair. The IAB also has the power to designate the chair of the Internet Research Task Force (IRTF) for a 2-year term.[10]
  • Decision-making: in most situations, the IAB aims to come to unanimous decisions on matters. When this is not possible, the IAB must come to a consensus of at least 7 members before taking action.[10]
  • Openness and confidentiality: The IAB makes all meetings open to the public by making it available online, and also publishes RFCs regularly to make its conclusions generally available. In some situations, however, confidential information is excluded for privacy reasons.[10]

RFC 2026 - The Internet Standards Process

[edit]

The Internet Standards process is an activity of the Internet Society that is organized and managed on behalf of the Internet community by the Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG). The Internet Standards Process is concerned with all protocols, procedures, and conventions that are used in or by the Internet. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body (either the IAB or the IESG), and is published. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications of the IESG, IAB, and Internet community. The complete Internet Standards Process is itself specified by an RFC, namely RFC 2026.[11]

RFC 8980 - Workshop on Design Expectations vs. Deployment Reality in Protocol Development

[edit]

The RFC 8980 workshop was held in February 2021, where the IAB discussed several topics around security protocols, including:[12]

  • Email standards, which presumed many providers running in a largely uncoordinated fashion but have seen both significant market consolidation and a need for coordination to defend against spam and other attacks. The coordination and centralized defense mechanisms scale better for large entities; these have fueled additional consolidation.
  • The Domain Name System (DNS), which presumed deep hierarchies but has often been deployed in large, flat zones, leading to the nameservers for those zones becoming critical infrastructure. Future developments in DNS may see concentration through the use of globally available common resolver services, which evolve rapidly and can offer better security. Paradoxically, the concentration of these queries into a few services creates new security and privacy concerns.
  • The Web, which is built on a fundamentally decentralized design but is now often delivered with the aid of Content Delivery Networks (CDNs). Their services provide scaling, distribution, and prevention of denial of service in ways that new entrants and smaller systems operators would find difficult to replicate. While truly small services and truly large services may each operate using only their own infrastructure, many others are left with the only practical choice being the use of a globally available commercial service.

The workshop resulted in the following recommendations by the IAB:

  • Develop and document a modern threat model.
  • Continue discussion of consolidation/centralization issues.
  • Document architectural principles, e.g., (re)application of the end-to-end principle.

Chairs

[edit]

The following people have served as chair of the IAB:[13]

Current members

[edit]
Members[14] Background
Deborah Brungard Deborah Brungard is a Lead Member of Technical Staff in Wireless and Access Technology at AT&T, where she has worked since 1984. She's been very active in the IETF's routing sector and has made many meaningful contributions there. She received a master's degree in electrical engineering from Stevens Institute of Technology. When off the clock, she can often be found escaping in her Silver Bullet.
Ben Campbell Ben Campbell is an independent consultant and an IAB liaison to the Internet Engineering Steering Group. He's spent time at many different companies and organizations, most notably Oracle Communication, Tekelec, and Estacado Systems. He received his bachelor's degree and His MBA from Texas A&M University and now resides in Irving, Texas. In his free time, he sails as much as he can and also enjoys listening to middle eastern percussion.
Jari Arkko Jari Arkko is originally from Kauniainen, Finland, but now resides in Jorvas, Finland, where he is employed at Ericsson Research, a Swedish mobile equipment manufacturer. He has also served at the IETF as one of the Internet Area Directors in the Internet Engineering Steering Group. He is also an avid family man and enjoys skiing, climbing, and photography.
Jiankang Yao Jiankang Yao is a senior research engineer leading the team in charge of technology standardization at the China Internet Network Information Center. He received his master's degree in computer science from the University of Singapore and went on to receive a Ph.D. in Computer Software and Theory from the Chinese Academy of Sciences.
Lars Eggert Lars Eggert is currently based in Helsinki, Finland, where he works as the Technical Director for Networking at NetApp. He has served on the Internet Engineering Task Force (IETF) for over two decades, including a stint as the chair of its research arm, the IRTF. He currently serves as the chair of the IETF. He received a Ph.D. in computer science from the University of Southern California and has previously served as the CTO at Nokia.
Wes Hardaker Wes Hardaker is a computer scientist at USC's Information Sciences Institute (USC/ISI). He primarily researches Internet security and is currently leading two NSF-funded projects on DNS and DDoS attacks. He is also active within the IETF and ICANN.
Cullen Jennings Cullen Jennings is a software development manager at Cisco Systems, where he builds collaboration systems used on the Internet. Cullen is also involved with discussions surrounding open source and internet standards.
Mirja Kühlewind Mirja Kühlewind received her PhD in 2015 on Transmission Control Protocol (TCP) from the University of Stuttgart and now researches transport protocol evolution. Mirja also was selected as IETF Transport Area Director in 2016.
Zhenbin Li Zhenbin Li received his bachelor's degree in Information and Communication Engineering from Xi’an Jiaotong University and his Master of Electronic Engineering from Tsinghua University. Now Zhenbin works as a network engineer and system architect for Huawei.
Jared Mauch Jared was appointed to the IAB as a 2020-2021 candidate. He currently works for Akamai Technologies as a Network Architect. Past work includes founding White Box Optical Inc. and Washtenaw Fiber Properties LLC.
Tommy Pauly Tommy was appointed to the IAB as a 2020-2021 candidate. He currently works for Apple on their networking stack for client operating systems, focusing on areas including secure transport protocols and APIs, VPNs, IPv6, and DNS. He currently co-chairs the HTTP and IPPM Working Groups. He received a BS in Computer Science and a BA in music, both from Stanford University.
David Schinazi David Schinazi is an engineer at Google. He currently works primarily as the Chrome Tech Lead for QUIC and helps out with various standardization efforts at the IETF and W3C. Previously, David worked at Apple on many networking technologies at the heart of iOS, macOS, tvOS, and watchOS, including networking APIs, TCP, IPv6, IKEv2/IPsec, and routing protocols.
Russ White Russ White began working with computers in the mid-1980s, and computer networks in 1990. He has experience in designing, deploying, breaking, and troubleshooting large-scale networks, and is a strong communicator from the whiteboard to the board room. He has co-authored more than forty software patents, participated in the development of several Internet standards, helped develop the CCDE and the CCAr, and worked in Internet governance with the Internet Society. Russ has a background covering a broad spectrum of topics, including radio frequency engineering and graphic design, and is an active student of philosophy and culture.
[edit]

References

[edit]

Further reading

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Internet Architecture Board

View on Grokipedia
from Grokipedia
The Internet Architecture Board (IAB) is a committee of the Internet Engineering Task Force (IETF) and an advisory body to the Internet Society (ISOC), composed of volunteer technical experts who provide long-range architectural guidance to ensure the Internet's ongoing evolution as a robust, interoperable network.[1][2] Originating from the Internet Configuration Control Board established in 1979 under Vint Cerf's DARPA program management, it evolved into the Internet Advisory Board in 1984 before adopting its current name and charter, as documented in RFC 2850, which outlines its composition, selection processes, and oversight roles independent of direct protocol development.[3][4] The IAB's core functions include confirming appointments to the IETF's Internet Engineering Steering Group (IESG), appointing the RFC Editor to manage Request for Comments publications, reviewing appeals on standards processes, and initiating workshops or programs on critical areas such as network security, IPv6 deployment, and emerging technologies like smart objects.[5][6][7] Comprising 13 seated members selected by the IETF Nominating Committee for two-year terms, the IAB maintains a focus on first-principles technical analysis rather than policy or governance, having produced influential statements opposing built-in surveillance mechanisms and advocating default encryption to preserve end-to-end principles amid growing threats.[8][9] Its programs have addressed long-term challenges, including Internet sustainability and barriers to access in underserved regions, contributing to the architecture's resilience without direct involvement in commercial or political disputes.[10][11]

History

Origins in Early Internet Governance (1979-1985)

The Internet Configuration Control Board (ICCB) was established in 1979 by Vinton Cerf, then serving as the DARPA program manager responsible for Internet protocols, to coordinate the growing technical efforts surrounding the transition from ARPANET to a broader TCP/IP-based network.[3][12] The ICCB functioned as an invitational advisory group, comprising experts selected to address configuration control, protocol interoperability, and software development challenges amid the proliferation of interconnected networks funded by DARPA.[13] Chaired by David Clark of MIT, the board met periodically to review proposals, resolve architectural disputes, and guide implementation standards without formal authority, relying instead on consensus among ARPA contractors and researchers.[3] During the early 1980s, the ICCB played a pivotal role in stabilizing Internet governance by overseeing the deployment of TCP/IP across diverse host systems and gateways, including efforts to standardize addressing schemes and error-handling mechanisms that prevented fragmentation in the nascent network.[12] Jon Postel, as the RFC editor at the University of Southern California's Information Sciences Institute (ISI), contributed informally through his management of protocol documentation and assigned numbers, emerging as a de facto "protocol czar" whose notes influenced ICCB deliberations on document reviews and updates.[3] By 1983, with Barry Leiner assuming DARPA's Internet program management, the ICCB's scope expanded to accommodate increasing research demands, though it remained a small, technical body focused on pragmatic problem-solving rather than policy-making.[14] In September 1984, following an ICCB meeting at the Royal Signals and Radar Establishment (RSRE) in Malvern, UK, the board was disbanded and restructured into the Internet Advisory Board (IAB), marking a shift toward a more organized framework with defined task forces for specialized areas such as gateway algorithms (chaired by Dave Mills) and end-to-end services.[3] This transition, initiated by Clark and Leiner, integrated the chairs of ten newly formed research task forces alongside Postel, with Clark retaining the chairmanship to provide continuity in architectural oversight.[3] Through 1985, the nascent IAB continued the ICCB's mandate by advising DARPA on protocol evolution, fostering interoperability testing, and laying the groundwork for open standards processes that emphasized technical merit over institutional directives.[12]

Formalization as Internet Activities Board (1986-1990s)

In May 1986, the Internet Activities Board (IAB) was formally documented in RFC 985, which outlined an executive summary of the proposed Internet standards process and affirmed its role in coordinating the evolution of Internet protocols and architecture. This formalization built on the 1983 reorganization from the Internet Configuration Control Board (ICCB), expanding the IAB's scope to include structured subsidiaries for engineering and research activities.[3] That year, the IAB divided the earlier Gateway Algorithms and Data Structures (GADS) group into the Internet Engineering Task Force (IETF), focused on short- to mid-term protocol development and operational standards, and the Internet Research Task Force (IRTF), dedicated to long-term networking research and innovation.[15] The IETF held its first meeting in 1986 under initial chair Mike Corrigan, transitioning to Phill Gross as chair from October 1, while the IRTF was chaired by David Clark.[3] The IAB's structure during this period consisted of an independent committee of approximately 10-15 researchers and professionals, appointed by the chair with member approval, serving two-year terms to address evolving Internet needs.[15] Chaired by Vinton Cerf from the late 1980s, the board met quarterly—often via video teleconferencing—and oversaw subsidiaries through steering groups: the Internet Engineering Steering Group (IESG) for the IETF and the Internet Research Steering Group (IRSG) for the IRTF.[15] [16] Responsibilities included strategic planning for TCP/IP evolution, resolving technical disputes, managing the Request for Comments (RFC) publication process, and liaising with sponsors such as DARPA, NSF, DOE, and NASA.[15] In August 1986, the IAB sponsored the first TCP/IP Vendors Workshop in Monterey, California, which laid groundwork for ongoing interoperability testing and evolved into the Interop events.[3] By 1989, further formalization occurred through RFC 1120, which detailed the IAB's oversight of standards progression—from Proposed Standard to Draft Standard to full Standard—via Internet-Drafts with a three-month review cycle, and emphasized multi-protocol architecture support.[15] That July, at the 14th IETF meeting in Stanford, the IAB restructured by formalizing the IESG and IRSG, while establishing IRTF research groups such as End-to-End (E2E) and Packet Switching (PSRG).[3] RFC 1120 listed 1989 IAB members including Cerf (chair), David Clark, Jonathan Postel, and Barry Leiner, reflecting a blend of DARPA origins and academic expertise.[15] In 1990, RFC 1160 provided an updated description of the IAB, its subsidiaries, and the broader ecosystem, including the transition of the Federal Research Internet Coordinating Committee (FRICC) to the Federal Networking Council (FNC).[16] Throughout the early 1990s, the IAB continued refining its processes amid Internet growth, focusing on architectural integrity and protocol scalability, though major charter changes under the newly formed Internet Society occurred by 1992.[3] This era solidified the IAB's role as the technical oversight body, distinct from operational implementation, ensuring consensus-driven evolution without centralized control.[15]

Transition to Modern IAB and Ongoing Evolution (2000-present)

In May 2000, the Internet Architecture Board (IAB) adopted RFC 2850, which formalized its contemporary charter and marked a pivotal transition toward a more structured oversight role within the Internet Engineering Task Force (IETF). This document delineated the IAB's primary responsibilities, including providing long-term architectural guidance to the IETF, reviewing proposed standards for consistency with overarching Internet principles, appointing the RFC Editor, establishing liaison relationships with external bodies, and offering technical advice to the Internet Society (ISOC). The charter affirmed the IAB's composition as thirteen members: twelve selected through the IETF Nominations Committee process for two-year terms, with the IETF Chair serving ex officio, emphasizing expertise in Internet architecture over administrative duties. This framework reinforced the IAB's independence while aligning it closely with IETF operations, shifting emphasis from broad activities coordination—prevalent in its earlier incarnation as the Internet Activities Board—to focused architectural stewardship amid the Internet's commercialization and global expansion.[17] Leadership transitioned smoothly under this charter, with John Klensin serving as Chair from March 2000 to March 2002, followed by Leslie Daigle's extended tenure from March 2002 to March 2007, the longest in IAB history, during which the board navigated post-dot-com challenges like IPv6 deployment and security protocol maturation. Subsequent Chairs included Olaf Kolkman (2007–2011), Bernard Aboba (2011–2013), Russ Housley (2013–2015), Andrew Sullivan (2015–2017), Ted Hardie (2017–2020), Mirja Kühlewind (2020–2024), and the current Chair Tommy Pauly (2024–present). These leaders, drawn from industry and research sectors, maintained the IAB's volunteer, expert-driven model, with terms typically aligned to March cycles to synchronize with IETF elections.[18] The IAB's ongoing evolution has centered on adaptive responses to technological shifts without major structural overhauls, prioritizing workshops, programs, and reports to address emergent issues. In the mid-2000s, it collaborated on refining the RFC Series governance to handle increasing publication volumes, introducing independent streams for non-IETF documents while preserving the series' archival integrity. By the 2010s, the IAB formalized long-term programs in areas like privacy, security, and network management, enabling sustained focus on challenges such as encryption at transport layers and IoT scalability. Workshops exemplified this proactive stance, including the 2000 Wireless Internetworking Workshop evaluating TCP/IP adaptations for mobile environments and recent efforts on AI-driven controls (2023) and access barriers (2024), fostering interdisciplinary input to guide protocol evolution. Through these mechanisms, the IAB has upheld causal principles of end-to-end connectivity and layered modularity, critiquing deviations that risk fragmenting the network's unified architecture, while advising ISOC on policy implications of technical trends.[19][10][20][21]
ChairTermAffiliation (at appointment)
John KlensinMarch 2000–March 2002AT&T
Leslie DaigleMarch 2002–March 2007Verisign, Cisco
Olaf KolkmanMarch 2007–March 2011NLNet Labs
Bernard AbobaMarch 2011–March 2013Microsoft
Russ HousleyMarch 2013–March 2015Vigil Security
Andrew SullivanMarch 2015–March 2017Dyn, Inc.
Ted HardieMarch 2017–March 2020Google
Mirja KühlewindMarch 2020–March 2024Ericsson
Tommy PaulyMarch 2024–presentApple

Organizational Structure and Governance

Membership Composition and Selection

The Internet Architecture Board (IAB) comprises 13 full voting members, consisting of the Chair of the Internet Engineering Task Force (IETF), who serves ex officio, and 12 sitting members selected for their technical expertise in Internet architecture.[22] In addition to these voting members, the IAB includes non-voting ex-officio participants, such as the IRTF Chair and the IETF Executive Director, as well as liaisons from entities like the Internet Society, the RFC Editor, and the Internet Assigned Numbers Authority (IANA).[22] These liaisons provide input but do not participate in votes on architectural decisions.[23] Sitting IAB members are nominated annually by the IETF Nominating Committee (NomCom), a rotating body drawn from the broader IETF community, which solicits input through public calls and evaluates candidates based on demonstrated expertise, community consensus, and the need for balanced representation of technical perspectives.[24] Approximately six positions—half of the sitting membership—are reviewed and potentially refilled each year to maintain continuity while refreshing expertise; nominees must consent to serve, and sitting members are eligible for re-nomination without term limits, provided they meet ongoing performance expectations.[23] Nominations are forwarded for confirmation, historically by the Internet Society Board of Trustees, ensuring alignment with IETF processes outlined in Best Current Practice 10 (BCP 10).[24] Mid-term vacancies, if any, follow the same NomCom procedures.[22] Terms for sitting members and the IETF Chair last two years, commencing at the first IETF meeting of the year, with staggered appointments to avoid full turnover.[22] This structure promotes stability in oversight while allowing periodic infusion of new insights; reappointments are common for high-performing members, as there is no cap on consecutive terms subject to NomCom review.[24] A recall mechanism exists for underperformance, initiated by a petition from at least 20 qualified IETF participants and requiring a three-quarters majority vote by a dedicated recall committee, though it has rarely been invoked.[24] The IAB itself elects its Chair from among the sitting members, typically for a renewable one- to two-year term, to lead internal deliberations.[22]

Core Responsibilities in Architectural Oversight

The Internet Architecture Board (IAB) holds primary responsibility for providing architectural oversight of Internet protocols and procedures, ensuring that developments align with the long-term evolution and stability of the Internet as a cohesive system. This involves reviewing proposed IETF working group charters and other initiatives to assess their consistency with the overall Internet architecture, preventing fragmented or incompatible advancements that could undermine interoperability or scalability.[4] As outlined in its charter, the IAB engages in long-range planning by identifying and addressing emerging architectural challenges, such as coordination across diverse protocol areas, to maintain the Internet's foundational design principles focused on modular building blocks and their interactions rather than imposing a rigid overarching blueprint.[4][1] In practice, this oversight manifests through periodic commentary on protocol designs and procedural evolutions, offering guidance to the Internet Engineering Steering Group (IESG) and working groups when architectural implications warrant intervention. The IAB does not micromanage day-to-day standards development but intervenes to safeguard core capabilities, including robust security, privacy foundations, and support for expanding connectivity demands like the Internet of Things and mobile networks.[5][1] For instance, it evaluates how new proposals interact with existing layers of the protocol stack, drawing on interdisciplinary insights to anticipate systemic risks, such as those arising from policy-technology intersections that could erode trust or openness.[4] This role extends to fostering an environment where the Internet remains a platform for global innovation without centralized controls that compromise its decentralized ethos.[1] The IAB's architectural mandate also includes serving as an appellate body for decisions related to standards that raise significant architectural concerns, providing a check against short-term expediency overriding long-term viability. By May 2000, when RFC 2850 formalized these duties, the emphasis was placed on proactive coordination to evolve the Internet responsibly amid rapid growth, a principle that continues to guide its activities in reviewing protocol parameter assignments and liaising externally to refine specifications.[4][5] This oversight ensures empirical grounding in protocol evolution, prioritizing causal mechanisms like end-to-end principles over unsubstantiated assumptions, thereby sustaining the Internet's resilience against foreseeable disruptions.[4]

Role in Standards Process, Appeals, and Appointments

The Internet Architecture Board (IAB) provides oversight of the process used to create Internet Standards, as documented in Best Current Practice 9 (BCP 9).[4] This role ensures architectural consistency and long-term coherence in protocol development, though the IAB does not directly manage working group activities, which fall under the Internet Engineering Steering Group (IESG).[4] The IAB functions as the final appeals body for complaints alleging improper execution of the standards process, with authority to review procedural adherence and enforce remedies as specified in BCP 9.[4] Appeals to the IAB typically follow exhaustion of lower-level reviews, such as those to working group chairs or the IESG, and must be filed within two months of the decision becoming publicly known, accompanied by a detailed dispute description and proposed remedy per RFC 2026.[25][26] The IAB may annul an IESG decision to revert to the pre-decision state, issue non-binding recommendations to the IESG, or affirm the original ruling, but it cannot override substantive technical judgments reserved for the IESG; it holds ultimate authority on procedural compliance in standards track advancement.[25] In appointments, the IAB reviews candidates nominated by the IETF Nominating Committee for IESG positions and the IETF Chair, consenting to some, all, or none based on architectural fit and expertise.[4] It appoints the RFC Editor to manage publication of Request for Comments (RFCs), selects the Internet Research Task Force (IRTF) Chair for renewable two-year terms, and confirms other key roles such as the Independent Submissions Editor.[4] Additionally, the IAB makes targeted appointments to external coordination bodies, including three members to the IETF Community Coordination Group (CCG) for two-year terms, one non-voting liaison to the ICANN Board of Directors, one member to the ICANN Root Zone Evolution Review Committee (renewable up to four years), and one voting delegate to the ICANN Nominating Committee (maximum two non-consecutive two-year terms), with calls for nominations issued openly for each vacancy.[27] These processes, grounded in the IAB's charter, emphasize community input while prioritizing technical oversight to sustain Internet protocol evolution.[4]

Activities and Technical Programs

Workshops, Reports, and Research Initiatives

The Internet Architecture Board (IAB) organizes workshops to convene experts on long-term Internet architecture challenges, emerging technologies, and strategic directions, often resulting in detailed reports that inform IETF and IRTF activities.[28] These gatherings solicit position papers from participants and emphasize discussion over consensus, with outputs including published reports—frequently as RFCs—and recommendations for standards development or further research.[29] Workshops address topics such as network management, security, and protocol evolution, typically held online or in hybrid formats when needed.[21] Notable examples include the 2024 AI-CONTROL Workshop held on September 19-20, which examined mechanisms for controlling AI systems' Internet interactions, producing a report highlighting risks like unauthorized data access and potential mitigations through protocol design.[30] The 2024 Barriers to Internet Access of Services (BIAS) Workshop, conducted January 15-17, documented filtering, blocking, and connectivity issues, with its report identifying technical barriers and calling for improved transparency in service access.[31] Earlier efforts encompass the 2021 Measuring Network Quality for End-Users Workshop, documented in RFC 9318 (October 2022), which analyzed metrics for user-perceived performance and spurred operator collaborations.[32] The COVID-19 Network Impacts Workshop in November 2020, reported in RFC 9075 (July 2021), assessed pandemic-driven traffic shifts and resilience gaps.[33] These activities have stimulated research initiatives by launching IRTF research groups and IETF working groups; for instance, the 2021 Analyzing IETF Data (AID) Workshop led to the Research and Analysis of Standards-Process Research Group (RASPRG) for data mining IETF contributions, while the 2016 IoT Software Updates (IoTSU) Workshop initiated the SUIT Working Group for secure update protocols.[29] The 2014 STRINT Workshop on pervasive monitoring influenced encryption protocol enhancements across multiple standards.[29] Over the 2014-2024 period, such workshops have consistently driven tangible outcomes, including new standards tracks and cross-community collaborations, underscoring their role in adaptive Internet evolution.[29]

Liaison Functions and External Engagements

The Internet Architecture Board (IAB) oversees the establishment and management of formal liaison relationships between the Internet Engineering Task Force (IETF) and other standards development organizations (SDOs), as mandated by its charter in Best Current Practice 39 (BCP 39).[34] This responsibility ensures coordinated technical input on Internet-related standards, with the IAB appointing liaison managers and representatives to convey IETF positions and gather relevant information from external bodies.[35] Procedures for these liaisons, including initiation, maintenance, and termination, are detailed in RFC 4052, which emphasizes transparency through public documentation and periodic reviews to align with IETF architectural principles.[36] IAB-appointed liaisons operate under guidelines in RFC 4691, requiring active participation in the external organization's meetings, conference calls, and mailing lists to monitor developments impacting IETF work, while accurately representing IETF consensus without binding commitments.[37] The IAB maintains liaison coordinators as primary contact points for management, facilitating efficient handling of inquiries and statements.[2] These functions extend to issuing formal liaison statements to other organizations, archived in the IETF datatracker, which address specific technical overlaps such as protocol interoperability or architectural concerns.[38] In external engagements, the IAB represents IETF interests in technical and organizational matters with bodies involved in standards development, providing oversight to prevent fragmentation of Internet protocols.[5] It also serves as an advisory liaison to the Internet Society (ISOC), offering guidance on architectural and procedural issues to support long-term Internet evolution.[2] These interactions prioritize empirical alignment with Internet scalability, drawing on first-hand technical expertise rather than external policy impositions, and have been instrumental in harmonizing efforts across global SDOs since the formalization of liaison processes in the early 2000s.[36]

Key Publications Including Foundational RFCs

The Internet Architecture Board (IAB) contributes to the RFC series through its dedicated stream, focusing on documents that address high-level architectural concerns rather than protocol specifications. These publications often establish guiding principles for Internet evolution, oversight of standards processes, and responses to emerging technical challenges. Foundational RFCs from the IAB emphasize enduring design tenets, such as modularity and decentralization, derived from empirical observations of network growth since the ARPANET era.[39][40] A cornerstone publication is RFC 1958, "Architectural Principles of the Internet," issued in May 1996 by IAB member Brian Carpenter. This document codifies principles like the end-to-end argument—positing that application-specific functions should reside in hosts rather than the network core to foster robustness and innovation—and the preference for simple, layered protocols over complex, monolithic designs. It draws on historical protocol deployments, such as IP's datagram model, to argue against over-reliance on network-level reliability mechanisms, which could hinder scalability as evidenced by early congestion collapses in the 1980s.[39] RFC 2850, "Charter of the Internet Architecture Board," published in May 2000, formalizes the IAB's structure, responsibilities, and relationship to the IETF. It defines the IAB as a 13-member body (including the IESG chair ex officio) tasked with architectural oversight, appointing the RFC Editor, and handling appeals on technical matters, replacing earlier charters like RFC 1601 from 1994. This RFC underscores the IAB's role in maintaining coherence across IETF work without micromanaging protocols, supported by its veto power over standards-track documents that deviate from core architecture.[4] Other significant IAB-stream RFCs include RFC 4845 from July 2007, which outlines the process for reviewing and publishing IAB documents to ensure editorial consistency and technical soundness prior to RFC issuance. Additionally, periodic updates like RFC 8729 (January 2020) refine the broader RFC series model, incorporating IAB input on document streams to adapt to evolving publication needs without altering foundational Internet principles. These works collectively sustain architectural integrity amid protocol proliferation, with the IAB's output tracked via the IETF datatracker for transparency.[41]

Leadership and Personnel

Historical and Current Chairs

The chair of the Internet Architecture Board (IAB) is elected by its members from among the IETF-nominated members and serves a term typically aligned with the board's two-year nomination cycles, providing leadership in guiding long-term Internet architecture, overseeing technical direction, and liaising with related bodies like the IETF and ISOC.[42] The position has been held by a series of experts in networking and computer science, reflecting the IAB's evolution from its origins in the early 1980s as a successor to the Internet Configuration Control Board (ICCB).[3] The following table enumerates the historical and current IAB chairs, including their primary affiliations during service and exact terms where documented:[18]
NameAffiliationTerm
Dave ClarkMIT1981–July 1989
Vint CerfCNRIJuly 1989–July 1991
Lyman ChapinData General, BBNJuly 1991–March 1993
Christian HuitemaINRIAMarch 1993–July 1995
Brian CarpenterIBMJuly 1995–March 2000
John KlensinAT&TMarch 2000–March 2002
Leslie DaigleVerisign, CiscoMarch 2002–March 2007
Olaf KolkmanNLNetlabsMarch 2007–March 2011
Bernard AbobaMicrosoftMarch 2011–March 2013
Russ HousleyVigil SecurityMarch 2013–March 2015
Andrew SullivanDyn, Inc.March 2015–March 2017
Ted HardieGoogleMarch 2017–March 2020
Mirja KühlewindEricssonMarch 2020–March 2024
Tommy PaulyAppleMarch 2024–present
As of October 2025, Tommy Pauly continues to serve as IAB chair, focusing on areas such as privacy-enhancing technologies and protocol evolution amid growing Internet scale challenges.[23] Prior chairs have influenced key architectural decisions, including transitions in domain name systems under Huitema and scalability oversight during Carpenter's tenure, though specific contributions are detailed in IAB workshops and RFCs rather than chair-specific mandates. The election process, outlined in RFC 8713, ensures continuity while allowing refresh of perspectives every few years.[42]

Membership Rosters and Tenure Patterns

The Internet Architecture Board (IAB) comprises 13 members: 12 selected through the annual IETF Nominating Committee process for two-year staggered terms (typically six seats per cycle), plus the IETF Chair serving ex officio.[43] This structure, detailed in RFC 8713, facilitates partial turnover each year to preserve accumulated expertise while incorporating fresh contributions, with no fixed limits on reappointments.[43] One member may occasionally receive a shorter term for transitional purposes, as seen in recent selections.[44] As of the seating at IETF 122 in March 2025, the IAB members are:
MemberAffiliation
Matthew BocciNokia
Cullen JenningsCisco
Dhruv DhodyHuawei
Jana IyengarFastly
Jason LivingoodComcast (1-year term)
Mark NottinghamCloudflare
Alvaro RetanaFuturewei
Roman DanyliwCarnegie Mellon University (IETF Chair)
Suresh KrishnanCisco
Mirja KühlewindEricsson
Warren KumariGoogle
Tommy PaulyApple (Chair)
Qin WuHuawei
Historical rosters, tracked via IETF announcements and IAB records, exhibit consistent patterns of staggered renewal, with approximately half the non-ex-officio membership rotating biennially to sustain oversight continuity amid evolving technical challenges.[18] Reappointments are common, enabling extended service for key contributors; for example, chairs have averaged about 3.5 years in role, with outliers like Dave Clark (1981–1989) demonstrating up to eight years of influence through successive terms.[18] This flexibility, absent formal term caps, has supported long-term architectural stability, though it risks entrenchment without the counterbalance of regular infusions.[43] Empirical data from post-2011 rosters show 40–60% annual retention rates among the appointed seats, aligning with the intent for balanced expertise retention.[18]

Relationships and Broader Context

Ties to IETF, IESG, and Protocol Development

The Internet Architecture Board (IAB) operates as a committee of the Internet Engineering Task Force (IETF), tasked with providing long-term architectural oversight rather than direct involvement in day-to-day protocol engineering or standards ratification.[5][4] This distinction ensures that while the IETF's working groups focus on developing and refining protocols through consensus-driven processes, the IAB evaluates broader architectural implications, such as consistency across protocols and alignment with Internet-scale principles like end-to-end connectivity and modularity.[4] For instance, the IAB reviews proposed IETF working group charters to assess their architectural fit, advising the Internet Engineering Steering Group (IESG) on potential issues before groups form and begin protocol work.[4] The IAB maintains structured ties to the IESG, which manages the IETF's technical direction and approves documents for advancement on the standards track. The IAB Chair serves as an ex officio, non-voting member of the IESG, facilitating coordination on overarching policy without influencing operational decisions like protocol actions.[45] Mutual appointments reinforce this linkage: the IAB nominates two liaisons to the IESG, while the IESG appoints one to the IAB, enabling cross-pollination of expertise on emerging technical challenges.[4] Additionally, the IAB confirms IESG Area Directors and the IETF Chair based on nominations from the IETF Nominating Committee, ensuring alignment between architectural vision and standards execution; these confirmations occur every two years for the Chair and annually for Area Directors.[5] The IAB also acts as the final appeal body for disputes arising from IESG decisions in the standards process, reviewing claims of procedural impropriety or architectural misalignment per Best Current Practice 9.[45][4] In protocol development, the IAB's influence is advisory and prospective, focusing on preventing architectural fragmentation rather than endorsing specific implementations. It assists the IESG in classifying new initiatives—directing suitable efforts to IETF working groups for standardization or to the Internet Research Task Force (IRTF) for exploratory research—and provides commentary on protocol parameters managed via the Internet Assigned Numbers Authority (IANA), often in response to IESG queries.[4][5] This role has historically shaped developments by highlighting risks, such as in early reviews of transport layer evolutions or naming system architectures, though the IAB avoids micromanaging working group outputs, leaving ratification to the IESG after IETF-wide last calls and expert reviews.[4] Through workshops and reports, the IAB further informs protocol trajectories by synthesizing community input on scalability and interoperability, ensuring developments sustain the Internet's decentralized ethos without centralizing control.[5]

Connections to ISOC, IANA, and Global Standards Bodies

The Internet Architecture Board (IAB) functions as a technical advisory committee to the Internet Society (ISOC), providing guidance on Internet architecture, protocol standards, and long-term technical direction. This relationship originated in 1992, when the IAB—formerly the Internet Activities Board—aligned with ISOC to establish a nonprofit structure supporting open Internet development, with the IAB renaming itself in 1995 to reflect its architectural focus.[46][3] The IAB chair serves ex officio on the ISOC Board of Trustees, and the IAB contributes to ISOC trustee nominations, ensuring technical expertise informs ISOC's governance and policy initiatives, as outlined in the IETF-ISOC relationship documented in RFC 8712.[47] Regarding the Internet Assigned Numbers Authority (IANA), the IAB holds direct oversight of protocol parameter assignments for IETF standards, including the administration of registries for numbers, names, and other identifiers to maintain interoperability and prevent duplication. This includes appointing managers for the IETF protocol parameters namespace, handling appeals on assignment decisions, and enforcing principles for registry operation as specified in RFC 8720.[5][48] Post-2016 IANA stewardship transition from U.S. government oversight to ICANN under a contract with the IETF Trust, the IAB retained authority over IETF-specific functions, such as protocol parameter stewardship, while ICANN manages domain names and IP addresses.[49] The IAB coordinates with global standards bodies through formal liaison mechanisms, acting as the IETF's representative to organizations including the International Telecommunication Union (ITU), Institute of Electrical and Electronics Engineers (IEEE), World Wide Web Consortium (W3C), and International Organization for Standardization (ISO). These relationships, governed by processes in RFC 4052, involve appointing liaison managers to exchange technical information, align on interoperable specifications, and address cross-organizational issues like spectrum allocation or web protocols.[36] Notable collaborations include joint endorsement of the 2012 OpenStand principles with IEEE, W3C, IETF, and ISOC, emphasizing open access, consensus-driven standards, and voluntary adoption over proprietary or mandated approaches.[50] This framework supports the IAB's role in advocating decentralized, bottom-up standards development amid potential tensions with more centralized bodies like the ITU.[51]

Influence on Internet Ecosystem and Decentralized Design Principles

The Internet Architecture Board (IAB) has profoundly shaped the Internet's ecosystem by championing architectural principles that prioritize scalability, openness, and resilience against centralization, thereby fostering a decentralized structure where intelligence resides primarily at network edges rather than in core infrastructure.[1] This influence stems from the IAB's oversight role in providing long-range technical direction to the Internet Engineering Task Force (IETF), ensuring protocol developments align with foundational tenets like the end-to-end arguments, which argue for implementing complex functions in end systems to maintain network simplicity and adaptability. By embedding these principles into IETF standards, the IAB has enabled the Internet's evolution into a permissionless, globally interoperable platform capable of supporting diverse applications without reliance on centralized gatekeepers.[52] A cornerstone of the IAB's advocacy for decentralization is its reinforcement of the end-to-end principle, originally articulated in early Internet design but continually defended in IAB outputs to counter pressures from intermediaries and regulatory interventions that could impose middlebox controls or erode user autonomy.[53] For instance, RFC 8890, an IAB informational document published in 2020, explicitly states that "the Internet is for end users" and urges protocol designers to prioritize user empowerment over intermediary interests, warning that deviations from end-to-end transparency undermine the network's openness and innovation potential. This stance has influenced ecosystem dynamics by discouraging designs that embed surveillance or filtering in the core, as seen in IAB critiques of proposals favoring centralized routing or content controls, which risk creating single points of failure and stifling peer-to-peer innovations. The IAB's workshops and reports further extend this influence by systematically addressing threats to decentralization, such as routing scalability challenges that could incentivize consolidation among a few providers.[54] In responses to policy consultations, like the 2023 reply to the European Commission's sender-pays model, the IAB emphasized the Internet's layered, decentralized architecture as essential for agility and global reach, arguing that alterations favoring centralization would fragment connectivity and reduce resilience.[55] These efforts have indirectly shaped market behaviors, promoting protocols that distribute control—such as those enabling federated systems over monolithic platforms—and sustaining an ecosystem where no single entity dominates addressing, routing, or application layers.[52] Empirical outcomes include the Internet's sustained growth to over 5 billion users by 2023 without architectural collapse, attributable in part to IAB-guided avoidance of over-centralized dependencies.[1] Critically, the IAB's focus on causal mechanisms of decentralization—such as modular protocol stacks that allow independent evolution of layers—has mitigated risks of vendor lock-in and state-imposed chokepoints, though debates persist on whether standards alone suffice against economic incentives for centralization in cloud services. Through these principles, the IAB has preserved the Internet's capacity for emergent, bottom-up innovation, distinguishing it from more hierarchical networks and enabling resilience to disruptions like the 2021 Colonial Pipeline attack, where decentralized routing alternatives prevented total outage.[56]

Evaluations and Debates

Achievements in Sustaining Internet Scalability and Innovation

The Internet Architecture Board (IAB) has sustained Internet scalability by codifying foundational architectural principles that prioritize simplicity in the network core, as outlined in RFC 1958 published in June 1996. This document emphasizes the end-to-end argument, asserting that functions like reliability and security should primarily be implemented at endpoints rather than in the network itself, thereby avoiding bloat in core infrastructure and enabling the network to handle diverse, unforeseen applications without frequent redesigns.[57] This approach has proven scalable, supporting the Internet's growth from millions to billions of users by distributing complexity to edges, where innovation can occur independently of central protocol changes.[57] Extending these guidelines in RFC 3439 (December 2002), the IAB reinforced philosophical tenets against over-reliance on network-level interventions, preserving a layered model that accommodates modular evolution. In confronting specific scalability challenges, the IAB has guided transitions critical to the Internet's expansion, particularly through advocacy for IPv6 to resolve IPv4 address exhaustion. In November 2016, the IAB issued a statement mandating full IPv6 support in all future networking standards, recognizing its 128-bit addressing as essential for accommodating the proliferation of devices in IoT and mobile ecosystems, projected to exceed 20 billion connections by 2025.[58] This position, echoed in drafts like "The Case for IPv6," underscores the IAB's role in steering protocol evolution toward sustainable addressing hierarchies that mitigate routing table inflation.[59] By prioritizing IPv6's built-in extensibility over short-term workarounds like NAT, which complicate end-to-end connectivity, the IAB has fostered an architecture resilient to exponential device growth while enabling seamless innovation in services like cloud computing and edge processing.[58] The IAB has also driven innovation through targeted workshops addressing emergent bottlenecks, such as the 2006 Routing and Addressing Workshop, which analyzed inter-domain routing scalability issues amid BGP table sizes approaching 200,000 entries and proposed strategies like identifier separation to curb explosive growth. This effort informed subsequent IETF work on secure routing protocols, enhancing the Internet's capacity to scale without compromising decentralization. Similarly, the 2011 workshop on interconnecting smart objects explored lightweight protocols for massive-scale IoT deployments, balancing constrained devices with Internet-wide interoperability to spur innovations in sensor networks and real-time data analytics.[60] These initiatives demonstrate the IAB's proactive oversight in maintaining an evolvable architecture, where scalability supports rather than stifles novel applications, from autonomous systems to global content delivery.[21]

Criticisms Regarding Adaptability, Centralization Risks, and Decision-Making

The Internet Architecture Board (IAB) has faced scrutiny within technical communities for the perceived limitations of internet architecture in adapting to evolving demands, such as the protracted transition to IPv6, where adoption remains below 50% globally as of 2024 despite standards finalized in 1998, attributed in part to architectural complexities like middlebox interference and a proliferation of incompatible transition mechanisms that overwhelm operators.[61] IAB-organized workshops, including the 2013 Internet Technology Adoption and Transition (ITAT) event, have acknowledged that protocol designs often fail to account for real-world externalities, leading to stalled deployments of security enhancements like DNSSEC and transport protocols like SCTP, with participants noting the IETF's tendency to prioritize solutions over comprehensive problem elucidation.[61] Regarding centralization risks, critics in IETF discussions argue that foundational IAB-endorsed principles, such as those in RFC 1958 emphasizing decentralization, have been undermined by deployment realities favoring concentrated services—for instance, the dominance of a few global DNS resolvers (e.g., Google Public DNS and Cloudflare's 1.1.1.1) which enhance efficiency but introduce single points of failure, privacy erosion, and coercion vulnerabilities, as highlighted in IAB analyses of market consolidation.[62] The 2019 Design Expectations vs. Deployment Reality (DEDR) workshop report underscores how economic incentives drive centralization in email and content delivery, contradicting architectural ideals and risking reduced user choice and protocol innovation, with IAB documents questioning whether current standards sufficiently counter these trends.[63] Such concentrations are seen as partly stemming from architectural decisions that did not anticipate proprietary escalations or spam-mitigation necessities pushing toward fewer, larger providers.[62] Decision-making processes within the IAB have drawn internal critique for potential insularity, as evidenced by community feedback on the opacity of workshop purposes and outcomes, which some IETF participants view as disconnected from broader deployment incentives, contributing to mismatches between theoretical designs and practical scalability.[29] The robustness principle (Postel's Law), long upheld in IAB oversight, has been reevaluated in recent drafts as fostering maintenance burdens and interoperability issues that hinder timely adaptations, with arguments that it encourages overly permissive implementations exacerbating centralization by favoring dominant players able to absorb compatibility costs. These concerns, while often raised in self-reflective IAB streams rather than adversarial external sources, reflect ongoing debates about whether the Board's small, expert-driven model adequately incorporates diverse economic and operational inputs to mitigate risks of architectural ossification.[61]

References

  1. About the IAB - Internet Architecture Board
  2. The Role of the IAB - Internet Architecture Board
  3. A Brief History of the Internet Advisory / Activities / Architecture ... - IAB
  4. RFC 2850 - Charter of the Internet Architecture Board (IAB)
  5. Internet Architecture Board - IETF
  6. Internet Engineering Task Force and Internet Architecture Board ...
  7. Internet Architecture Board (iab) - IETF Datatracker
  8. New Internet Architecture Board, IETF Trust, IETF LLC and Internet ...
  9. IAB Statement on Encryption and Mandatory Client-side Scanning of ...
  10. History of IAB Programs - Internet Architecture Board
  11. RFC 9707: Report from the IAB Workshop on Barriers to Internet ...
  12. RFC 1160: Internet Activities Board
  13. A Brief History of the Internet - Internet Society
  14. A Brief History of the Internet - UCSB Computer Science
  15. RFC 1120 - Internet Activities Board - IETF Datatracker
  16. RFC 1160: Internet Activities Board
  17. RFC 2850 - Charter of the Internet Architecture Board (IAB)
  18. Past IAB Members and Chairs - Internet Architecture Board
  19. draft-iab-fiftyyears-01 - Fifty Years of RFCs - IETF Datatracker
  20. RFC 3002: Overview of 2000 IAB Wireless Internetworking Workshop
  21. Past IAB Workshops - Internet Architecture Board
  22. RFC 2850: Charter of the Internet Architecture Board (IAB)
  23. IAB Members - Internet Architecture Board
  24. RFC 3777: IAB and IESG Selection, Confirmation, and Recall Process
  25. Appeals to the IAB - Internet Architecture Board
  26. https://www.rfc-editor.org/info/rfc2026
  27. IAB Appointments & Confirmations - Internet Architecture Board
  28. IAB Workshops - Internet Architecture Board
  29. A review of a decade of Internet Architecture Board workshops - IETF
  30. IAB AI-CONTROL Workshop Report - IETF Datatracker
  31. IAB Barriers to Internet Access of Services (BIAS) Workshop Report
  32. RFC 9318 - IAB Workshop Report: Measuring Network Quality for ...
  33. RFC 9075 - Report from the IAB COVID-19 Network Impacts ...
  34. IAB Processes for Management of IETF Liaison Relationships
  35. Liaisons - IETF
  36. RFC 4052: IAB Processes for Management of IETF Liaison ...
  37. Guidelines for Acting as an IETF Liaison to Another Organization
  38. IAB Statements & Correspondence - Internet Architecture Board
  39. RFC 1958 - Architectural Principles of the Internet - IETF Datatracker
  40. Documents & Publications
  41. IAB stream documents - IETF Datatracker
  42. https://www.rfc-editor.org/rfc/rfc8713
  43. RFC 8713 - IAB, IESG, IETF Trust, and IETF LLC Selection ...
  44. New IAB, IETF Trust, IETF LLC and IETF Leadership Announced
  45. RFC 9281 - Entities Involved in the IETF Standards Process
  46. IETF and the Internet Society
  47. RFC 8712: The IETF-ISOC Relationship
  48. RFC 8720: Principles for Operation of Internet Assigned Numbers ...
  49. IANA Transition - Internet Society
  50. IEEE, IAB, IETF, Internet Society and W3C Endorse OpenStand ...
  51. The Internet and Standards - Internet Society
  52. Centralization, Decentralization, and Internet Standards - IETF
  53. The Internet is for the Empowerment of End Users - RIPE Labs
  54. Report from the IAB Workshop on Routing and Addressing
  55. [PDF] IAB Response to EC sender-pays
  56. RFC 9518 - What Can Internet Standards Do About Centralisation?
  57. RFC 1958: Architectural Principles of the Internet
  58. IAB encourages IPv6 - APNIC Blog
  59. draft-iab-case-for-ipv6-06 - IETF Datatracker
  60. IAB Workshop on Interconnecting Smart Objects with the Internet ...
  61. RFC 7305: Report from the IAB Workshop on Internet Technology Adoption and Transition (ITAT)
  62. draft-arkko-iab-internet-consolidation-02 - IETF Datatracker
  63. RFC 8980: Report from the IAB Workshop on Design Expectations ...
User Avatar
No comments yet.