History
The body which eventually became the IAB was originally the Internet Configuration Control Board (ICCB). It was created byResponsibilities
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 anActivities
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 ** IoT Semantic Interoperability Workshop 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
The IAB's current responsibilities include: *Architectural Oversight: The IAB provides oversight of, and occasional commentary on, aspects of the architecture for theRFC1087 – Ethics and the Internet and a rise to modernity
The IAB takes a formal stance on what constitutes proper use of the Internet in their 1989 memo, RFC 1087: “Ethics and the Internet.” 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. 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 y mass surveillance campaigns..to ensure that the Internet can be trusted by tsusers.”RFC 2850 - Charter of the Internet Architecture Board
RFC 2850 establishes the structure and purpose of the IAB. The RFC specifies the following: * IAB membership: the IAB has 13 members, 1 being the chair of theRFC 2026 - The Internet Standards Process
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.RFC 8980 - Workshop on Design Expectations vs. Deployment Reality in Protocol Development
The RFC 8980 workshop was held in February 2021, where the IAB discussed several topics around security protocols, including: *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
The following people have served as chair of the IAB: * David D. Clark – 1981 to July 1989 *Current members
Related organizations
* IETF Administration LLC - This organization provides legal advice for the IAB * Request for Comments (RFC) Editor - The RFC series contains documents released by 4 organizations: The Internet Architecture Board (IAB), the Internet Engineering Task Force (IETF), the Internet Research Task Force (IRTF), and Independent Submissions * Internet Assigned Numbers Authority (IANA) * Internet Research Task Force (IRTF) - The IRTF works on long-term projects related to the Internet * The IETF Trust - The IETF Trust holds intellectual property licensing and other licensing related to the Internet * The Internet Society (ISOC)References
Further reading
* Carpenter, Brian (editor), ''Charter of the Internet Architecture Board'' (RFC 2850, May 2000) * Kozierok, Charles,External links
* *