The Internet Engineering Task Force is the body responsible for the technical standards that make the internet work. It grew out of the informal Network Working Group of the ARPANET era and was organized under that name in the mid-1980s. Its work product is the long-running Request for Comments series: protocols such as TCP/IP, DNS, HTTP, BGP, and IPv6 are all defined in RFCs produced through the IETF process.
The IETF’s own mission statement, RFC 3935 by Harald Alvestrand, published in October 2004, states the aim plainly: “The goal of the IETF is to make the Internet work better.” It defines the mission as producing “high quality, relevant technical and engineering documents that influence the way people design, use, and manage the Internet.” Those documents include protocol standards, best current practices, and informational and experimental notes.
What distinguishes the IETF from older standards organizations is how open it is. There is no formal membership; anyone may join a mailing list, attend a meeting, or submit an Internet-Draft. Decisions are reached by what the organization calls rough consensus and running code, a working ethos that values demonstrated, interoperable implementation over formal voting. RFC 3935 lists this among the IETF’s cardinal principles, alongside an open process, technical competence, and volunteer participation.
The IETF works through working groups, each focused on a specific area, organized under broader areas overseen by the Internet Engineering Steering Group, with architectural guidance from the Internet Architecture Board. Much of the day-to-day work happens on public mailing lists between the three in-person meetings held each year. The registries of protocol numbers and parameters that IETF standards depend on are maintained by the Internet Assigned Numbers Authority on the IETF’s behalf, an arrangement formalized in RFC 2860.
Because its standards are published openly and implemented by competing vendors, the IETF has had outsized influence relative to its informal structure. The protocols it stewards carry essentially all internet traffic, and its consensus-driven, implementation-first culture has become a model for how open technical standards can be developed.