IETF Working Group

IETF Working Group
Name	IETF Working Group
Formation	1986
Type	Working group
Parent organization	Internet Engineering Task Force

IETF Working Group

IETF Working Group units are temporary technical committees created within the Internet Engineering Task Force to develop standards, best current practices, protocols, and informational documents. These groups interact with standards bodies and institutions such as the Internet Society, IAB, RFC Editor, IETF Trust and coordinate with regional organizations like IETF Administrative Oversight Committee and technical consortia including the W3C, IEEE 802, and IETF Hackathons. They operate alongside protocols and efforts exemplified by TCP/IP, HTTP, DNS, BGP, and TLS.

Overview

Working groups serve as the principal mechanism for producing specifications such as RFC 2119, RFC 2026, and standards that influence projects like QUIC, IPv6, and SNMP. Participants come from companies, universities, and research labs including Google, Cisco Systems, Apple Inc., Microsoft, Mozilla Foundation, Stanford University, and MIT. Interactions and decisions are shaped by mailing lists, plenary sessions at conferences such as the IETF Meeting, IETF Working Group Last Call, and close coordination with bodies like IANA, ICANN, RIPE NCC, and regional registries. Historical collaborations have involved projects connected to NSFNET, Arpanet, DARPA, and standards influenced by published work from Jon Postel, Vint Cerf, and Van Jacobson.

Formation and Chartering

Formation begins when proposers file a charter that enumerates scope, milestones, chairs, and deliverables; charters are reviewed by the IETF Area Directors and approved by the IETF Chair and IESG. Chartering references procedural texts such as RFC 3933 and coordination practices used by groups like IESG Nominations Committee and processes in IESG Appeals. Proposals often cite existing standards from RFC 793, RFC 791, or practices developed at consortia like OpenSSL Project and Apache Software Foundation. Consensus on charter scope is reached via mailing list discussion and area director guidance, with historical precedents set during the evolution of working groups that produced SMTP, IMAP, and MIME.

Organizational Structure and Roles

A working group typically designates one or more chairs, an appointed document shepherd, and active contributors drawn from organizations such as Juniper Networks, Nokia, Ericsson, Red Hat, and academic labs like Berkeley Computer Science Division. Chairs coordinate with the Area Director and liaise with working groups in other areas including the Routing Area, Transport Area, and Security Area. Roles mirror governance practices found in institutions such as IEEE Standards Association and the World Wide Web Consortium with community positions analogous to editors of publications like the RFC Series. Contributors may serve as editors, authors, reviewers, and implementers, interacting with maintainers of projects like BIND, OpenSSH, and iproute2.

Work Process and Procedures

Work proceeds through iterative drafts on the IETF Datatracker, discussion on mailing lists, and consensus assessment methods derived from documented practices like rough consensus and running code exemplified by W3C Process Document and IAB Recommendations. Milestones include initial drafts, working group last calls, IETF last calls, and IESG review; artifacts transition to the RFC Editor and may receive designations such as Proposed Standard, Draft Standard, or Internet Standard. Implementation experience from software linked to Linux Kernel, FreeBSD, nginx, and Open vSwitch frequently informs consensus. Interoperability testing, protocol fuzzing techniques pioneered in research at CERT Coordination Center and Lodgepole-style testbeds, and coordination with events like IETF Hackathon are standard practices.

Deliverables and Standards Track

Deliverables include Internet Standards, Proposed Standards, Experimental RFCs, Informational RFCs, and Best Current Practice documents that have guided technology such as HTTP/2, OAuth, SIP, and RADIUS. Some working groups produce code, reference implementations, test suites, and interoperability reports that feed into ecosystems maintained by IETF Tools and the RFC Editor. Standards-track documents follow the path from IETF consensus to IESG approval, potential independent review by bodies like IANA and registry updates in coordination with IANA Protocol Registries, and eventual archiving in the RFC Series.

Lifespan, Closure, and Historical Impact

Working groups are charter-limited and close upon completion, charter expiration, or due to lack of activity; closure actions are recorded by the IETF Datatracker, with dissolved groups often spawning successor groups or influencing ongoing work at organizations like IETF Research Group initiatives, and standards adopted by vendors such as Cisco Systems and Juniper Networks. Historically, working groups have driven major Internet transformations, contributing to protocols linked to SMTP, BGP, DNSSEC, and TLS 1.3, and shaping deployments in large-scale infrastructures like CDN operators and cloud providers including Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Their legacy is reflected in the corpus of RFC documents, the institutional practices of the IETF, and the operational fabric of the global Internet.

Category:Internet standards