Internet Engineering Task Force

The Internet Engineering Task Force (IETF) is an open, international standards organization whose technical work underpins much of the modern Internet. It develops, reviews, and publishes specifications for the Internet protocol suite and related technologies, including networking, routing, transport, security, naming, web services, real-time communications, operations, and emerging connected-device systems. Its standards are published primarily as Requests for Comments, or RFCs, and are freely available for implementation and reuse. The IETF is distinctive in that it has no conventional membership roster, corporate membership system, or formal entrance requirements. Participation is individual and open to anyone with relevant interest or expertise. Contributors commonly join working-group mailing lists, attend meetings, review drafts, write specifications, test implementations, or take part in interim discussions. Participants may be supported by employers, universities, governments, nonprofits, or other sponsors, but the IETF's technical process is designed around individual participation rather than organizational voting rights. The organization evolved from the Gateway Algorithms and Data Structures Task Force. In January 1986, the Internet Activities Board divided that earlier work between a research-oriented Internet Architecture Task Force and the IETF, which focused on nearer-term engineering and technology-transfer issues. The first meeting involved 21 federally funded researchers. Participation broadened to nongovernmental organizations at the fourth meeting later in 1986, and subsequent meetings became open to the public. During its early years, the IETF received support from the United States government and administrative assistance from the Corporation for National Research Initiatives. In the early 1990s, the Internet Society was formed with support from institutions and figures involved in the development of the Internet, and the IETF became an activity associated with that nonprofit organization. Since 1993, the Internet Society has provided the IETF's broader institutional setting while the technical standards process has remained distinct from the society's administrative role. In 2018, the Internet Society established the IETF Administration LLC as the IETF's corporate, legal, and financial home. The IETF Trust, established in 2005, manages intellectual-property assets and materials produced through the IETF process. IETF work is organized into subject areas and working groups. Working groups normally operate under a public charter, use open mailing-list discussions, and are guided by one or more chairs. Area directors and the IETF chair form the Internet Engineering Steering Group, which oversees the standards process, conducts final technical reviews, and handles appeals. The Internet Architecture Board provides architectural guidance and manages external relationships, while the Internet Research Task Force pursues longer-term research topics. A nominating committee selects members of key leadership bodies, including the IETF chair, the IESG, the IAB, the IETF Trust, and the IETF Administration LLC. The IETF's decision-making culture is commonly summarized as “rough consensus and running code.” It does not use formal voting as its primary method. Technical proposals are debated publicly, revised through review and implementation experience, and advanced when working-group consensus and sufficient evidence of interoperability have been established. This process favors practical, modular protocols that can be reused across different architectures. It can also be slow, particularly when backward compatibility, complex technical trade-offs, or a large and divided contributor community make agreement difficult. The organization normally holds three major meetings each year, rotating among North America, Europe, and Asia, with remote participation and interim virtual or hybrid work supplementing the in-p…

The IETF emerged from the early Internet research and engineering community that worked on connecting disparate computer networks. Its direct precursor was the Gateway Algorithms and Data Structures Task Force, chaired by David L. Mills. In January 1986, the Internet Activities Board divided that activity into two streams: an Internet Architecture Task Force for research-oriented goals and the Internet Engineering Task Force for nearer-term engineering issues and technology transfer. Mike Corrigan became the first IETF chair, and Phill Gross succeeded him in 1987. The first IETF meeting took place on 16 January 1986 and was attended by 21 United States government-funded researchers. The early meetings were small and initially centered on government-supported research networks. By the fourth meeting, in October 1986, representatives from nongovernmental organizations, including gateway vendors, were invited. The meetings subsequently became open to the public, establishing the inclusive participation model that remains central to the organization. Administrative support was initially connected to the United States government and later to the Corporation for National Research Initiatives. A cooperative agreement between CNRI and the National Science Foundation, effective in 1989, provided for a secretariat supporting the Internet Activities Board, its task forces, and especially the IETF. CNRI also supported the formation and early financing of the Internet Society in 1992. The Internet Society then became the IETF's principal institutional setting, while the IETF retained responsibility for its technical standards process. The relationship between the IETF and the Internet Society was clarified in standards-process documents during the 1990s. The Internet Society provided administrative and organizational support but was not intended to dictate the technical substance of Internet standards. In 1998, CNRI established Foretec Seminars to provide secretariat services; that arrangement continued for several years. In 2005, the IETF Trust was created to administer copyrights and other intellectual-property interests associated with IETF output. As the Internet expanded, the IETF's scope grew from a relatively small engineering forum into a major global standards community. It moved from quarterly meetings to three meetings per year in 1991. Attendance increased dramatically during the commercial expansion of the Internet, reaching a reported peak of 2,810 participants at the December 2000 meeting in San Diego. Attendance later declined from that peak, but the organization continued to operate through a combination of in-person meetings, mailing lists, interim sessions, remote participation, and implementation-focused hackathons. In 2018, the Internet Society created the IETF Administration LLC to serve as the IETF's corporate, legal, and financial home. IETF activities are supported through meeting fees, sponsorships, Internet Society support, and related institutional funding. In 2019, the LLC sought proposals for secretariat services, reflecting the continuing evolution of the organization's administrative model. The IETF's technical method has remained more stable than its administration. Working groups publish proposals for public discussion, revise them through review and implementation experience, and submit mature documents through the standards-track process. The Internet Engineering Steering Group provides final technical review and manages day-to-day standards operations. The Internet Architecture Board offers architectural oversight and external liaison, while the Internet Research Task Force addresses longer-horizon research. The process is based on rough consensus rather than formal votes, with running, interoperable code serving as an important practical test. This model has produced protocols that are embedded in email, web services, routing, transport, security, naming, and many other Internet systems. It also creates challenges: consensus can take time, backward compatibility can make protocol change difficult, and volunteer availability can vary across subjects. The IETF continues to work with other standards organizations and to address new requirements involving mobility, cloud systems, automated management, connected devices, privacy, security, and evolving transport technologies.

• 2019

  Secretariat-services procurement begins

  [1]Internet Engineering Task Forceen.wikipedia.org

  The IETF Administration LLC issued a call for proposals for secretariat services.

• 2018

  IETF Administration LLC established

  [1]Internet Engineering Task Forceen.wikipedia.org

  The Internet Society created a dedicated LLC to serve as the IETF's corporate, legal, and financial administrative home.

• 2005

  IETF Trust established

  [1]Internet Engineering Task Forceen.wikipedia.org

  The IETF Trust was established to manage copyrighted materials and related intellectual-property interests produced through IETF work.

• 2000

  Record reported meeting attendance

  [1]Internet Engineering Task Forceen.wikipedia.org

  The December meeting in San Diego reportedly reached 2,810 attendees, illustrating the scale of the IETF during the Internet industry's expansion.

• 1993

  Institutional association with the Internet Society

  [1]Internet Engineering Task Forceen.wikipedia.org

  The IETF became an independent international activity associated with the Internet Society after its earlier federal-government support period.

• 1991

  Meeting schedule expands to three times yearly

  [1]Internet Engineering Task Forceen.wikipedia.org

  The IETF moved from quarterly meetings to a schedule of three major meetings per year.

• 1989

  CNRI and NSF secretariat agreement

  [1]Internet Engineering Task Forceen.wikipedia.org

  A cooperative agreement provided administrative support for the IETF and related Internet coordination bodies.

• 1986

  First IETF meeting

  [1]Internet Engineering Task Forceen.wikipedia.org

  The first meeting was held on 16 January 1986 with 21 federally funded researchers, following the division of the earlier GADS activity.

• 1986

  Participation opens beyond government researchers

  [1]Internet Engineering Task Forceen.wikipedia.org

  Representatives from nongovernmental organizations were invited to the fourth meeting, helping establish the IETF's open participation model.

An open, technically led, volunteer-driven standards forum for interoperable Internet protocols. The IETF emphasizes individual participation, public review, rough consensus, and demonstrated implementations rather than membership voting or commercial ownership.

• Technical publications · 1969

  Requests for Comments (RFCs)

  RFCs are the IETF's principal document series. They contain protocol specifications, standards-track documents, informational papers, experimental work, and other technical records. RFCs are published online and are generally available for unrestricted reading and implementation, making the series a durable reference layer for Internet engineering.

• Standards-development forums · 1986

  IETF working groups

  Working groups are temporary or continuing technical communities organized around a defined charter. They conduct discussions on public mailing lists, develop and review drafts, coordinate interoperability work, and seek rough consensus before documents advance through the standards process.

• Standards process · 1986

  IETF standards-track process

  The standards-track process takes proposals through public technical discussion, revision, review, implementation experience, and approval stages. The Internet Engineering Steering Group provides final technical review. Formal voting is not the normal basis for decisions; consensus and evidence of useful, interoperable implementations are central.

• Professional forums · 1986

  IETF meetings and hackathons

  The IETF holds three major meetings each year, supplemented by remote and interim sessions. Meetings provide working-group discussions and informal Birds of a Feather sessions. Hackathons focus on code, testing, and interoperability improvements that support standards development.

• 2025

  Concerns about intelligence-agency influence

  Reference material describes intensified criticism concerning possible intelligence-agency influence and insufficient transparency in IETF decision-making. It does not establish a confirmed finding, legal judgment, or specific responsible party.

  Source

Read more

• 2018

  Create a dedicated administrative legal entityStrategy

  Background

  The IETF needed a separate structure for corporate, legal, financial, and administrative responsibilities.

  Action taken

  The Internet Society established the IETF Administration LLC.

  Aftermath

  The LLC became the IETF's administrative home and later managed procurement of secretariat services.

  Source

• 1993

  Transition to an international Internet Society-associated structureStrategy

  Background

  The IETF had outgrown its original federal-government-supported research setting and required a durable international institutional framework.

  Action taken

  The IETF became associated with the Internet Society while retaining an independent technical standards process.

  Aftermath

  The Internet Society provided administrative context and support without being intended to control the technical content of IETF standards.

  Source

• 1986

  Separate research and near-term engineering workStrategy

  Background

  The Internet Activities Board needed to distinguish longer-term architectural research from practical engineering and technology-transfer work.

  Action taken

  It divided the GADS precursor into the research-oriented Internet Architecture Task Force and the IETF.

  Aftermath

  The IETF became the principal open forum for near-term development of Internet protocol standards.

  Source

1. 1Internet Engineering Task Forceen.wikipedia.org
2. 2IETF official websiteietf.org