Internet Engineering Task Force: What It Builds and How It Works
The Internet Engineering Task Force (IETF) develops and publishes open technical standards and guidance that help the internet work across different networks and devices. It does this through a public, largely volunteer-driven process: participants discuss proposals, refine them in working groups, and publish approved documents called RFCs.
What the IETF Builds
The IETF builds specifications for internet protocols and related technologies—not websites, internet connections, or physical network equipment. A protocol describes how systems communicate, including the formats, rules, and procedures they must follow. When implementations follow compatible specifications, equipment and software made by different organizations can exchange data.
Its work covers many layers and functions of internet communication. Familiar examples include:
- IP (Internet Protocol): carries packets between networks. IPv4 and IPv6 are distinct versions of IP.
- TCP (Transmission Control Protocol): provides a reliable, ordered stream of data between endpoints.
- DNS-related standards: specify parts of the system used to look up information associated with domain names.
- TLS (Transport Layer Security): defines a protocol commonly used to protect communications, including web connections.
- HTTP specifications: define the application protocol used to transfer web resources.
These examples do not mean the IETF operates the services that use the protocols. It specifies technical behavior; companies, public institutions, researchers, and open-source communities build and run implementations.
How the IETF Works
The IETF is an open standards-development organization. Participation is not limited to employees of member companies: individuals can join discussions, contribute drafts, and attend meetings. The organization describes its approach with the phrase “rough consensus and running code.” This means that decisions seek broad agreement, informed by practical implementation and testing, rather than being settled simply by a majority vote.
A typical standards effort moves through stages such as these:
- Identify a problem. Participants describe an interoperability or operational need and discuss whether the IETF is an appropriate place to address it.
- Form or use a working group. If the work is accepted into the IETF process, a working group with a defined charter develops the proposal. Working groups are organized under areas such as routing, security, or applications.
- Write and revise Internet-Drafts. Authors publish drafts for discussion. These are working documents, not final standards, and can be revised, replaced, or allowed to expire.
- Review the technical details. Participants examine whether the proposal is clear, feasible, secure, and compatible with related protocols. Implementations and operational experience can reveal problems that text alone does not.
- Advance the document through review and approval. The working group and relevant IETF leadership review documents according to the applicable process. An approved document is published as an RFC.
Not every proposal becomes a standard, and publication does not by itself guarantee that a technology will be widely adopted. The process aims to produce technically useful, openly available specifications.
RFCs and Internet Standards
RFC stands for Request for Comments, the name of a long-running series of technical documents. RFCs include IETF standards, but the terms are not interchangeable: an RFC can also be informational, experimental, or describe another kind of technical publication. An RFC number identifies a document in the series; it does not indicate its age, quality, or status as a standard.
When an IETF specification is revised, the newer document may update or obsolete an earlier RFC. Readers should check the document’s status and its relationship to other RFCs rather than relying only on its number. Some IETF standards are designated as Internet Standards, while others are published with a different standards-track status or as non-standards documents.
RFCs are published publicly, allowing implementers and readers to consult the same technical text. Their availability is important to interoperability: engineers can build compatible systems without needing to obtain a private specification from a single vendor.
Who Participates and How Decisions Are Made
IETF work is conducted by people who contribute expertise and time, including network operators, software developers, researchers, security specialists, and representatives of organizations. The Internet Society provides organizational support, while the Internet Architecture Board and the Internet Engineering Steering Group have defined roles in the IETF’s structure and processes. These bodies do not replace the technical discussion of working groups.
Consensus is assessed through discussion and the judgment of the relevant chairs, following IETF procedures. It is not the same as unanimity: a technical objection should be considered, but one person does not automatically have a veto. Conversely, a quick show of hands is not necessarily enough to establish that a proposal has addressed important concerns.
Meetings provide a place for discussion, but much of the work happens through mailing lists and online document review. This allows people to contribute even if they cannot attend a meeting in person. The process is public, though following a technical discussion can require familiarity with networking concepts and the documents under review.
What the IETF Does Not Do
A common misconception is that the IETF controls the internet or requires every network to use its standards. It does neither. The IETF does not own the global network, assign every IP address, register domain names, police websites, or decide what content people may publish. Those functions, where applicable, belong to other organizations, service providers, governments, or network operators.
IETF standards can become influential because broad adoption makes communication easier, not because the IETF can compel every product or network to implement them. A vendor may implement a standard, extend it, or choose a different approach; the practical consequences depend on compatibility and user needs. Standards can also evolve as operational requirements and security knowledge change.
Why Its Work Matters
Without shared protocol specifications, each network or software maker could define incompatible ways to address, route, secure, or exchange data. Common standards let independently built systems communicate and give implementers a public reference for expected behavior.
The IETF’s work is especially useful when a technology must function across organizational boundaries. For example, a web browser and a web server may come from unrelated developers and run on different operating systems, yet they can exchange information because they implement common protocols. Interoperability does not mean every implementation is identical; it means they follow enough shared rules to work together.
Frequently Asked Questions
What does IETF stand for?
IETF stands for Internet Engineering Task Force. It is an open organization that develops technical specifications and guidance for internet operation and interoperability.
Is the IETF a government agency?
No. It is not a government regulator. It develops standards through an open technical process; it does not have authority to compel networks or companies to adopt them.
What is the difference between an RFC and an IETF standard?
RFC is the name of a document series. Many RFCs are IETF standards or standards-track documents, but others are informational, experimental, or otherwise not standards.
Can anyone participate in the IETF?
Yes. Individuals can take part in public discussions and contribute technical work. Participation is open, although effective contributions often require time and relevant technical knowledge.
Does the IETF run the internet?
No. The IETF develops specifications; networks, service providers, device makers, and software developers operate systems and decide whether to implement them.
How do I find an IETF standard?
Search the IETF’s public RFC and document resources by protocol name, subject, or RFC number, then check the document’s status and any later updates or replacements.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.