The Internet Engineering Task Force (IETF) stands as the cornerstone of Internet protocol development, crafting the technical foundations that power global connectivity. Yet, a persistent challenge looms: the underrepresentation of network operators in these processes. Operators, who manage the physical and operational realities of Internet infrastructure, bring invaluable perspectives on scalability, reliability, and real-world deployment hurdles. This article delves into historical efforts to amplify their voices, drawing from pivotal discussions like those at IETF 91 in 2014, while connecting to the evolving landscape of standards creation today.
The Critical Need for Operator Perspectives
Internet standards emerge from collaborative debates among diverse stakeholders, including developers, vendors, academics, and operators. However, operators often lag in participation. According to RFC 9281, the IETF comprises ‘an open international community of network designers, operators, implementors, researchers, and other interested parties’ focused on Internet evolution.1 Despite this inclusive ethos, surveys reveal imbalances. A key 2016 analysis by Netnod highlighted that many mid-sized and smaller operators rarely engage with IETF mailing lists or meetings, allowing vendors and academics to dominate decisions.
This gap risks standards that overlook operational pain points, such as complex configurations or unforeseen scaling issues in live networks. Enhanced operator input ensures protocols are not just theoretically sound but practically deployable, fostering a more resilient Internet.
Insights from Operator Surveys
To quantify this issue, initiatives like the Internet Society’s operator survey gathered over 350 responses by mid-2016. Respondents identified core problems: inconsistent operator awareness of relevant discussions, insufficient engagement relative to other groups, and protocols that sometimes falter in production environments. The survey proposed solutions like formalizing ‘best current operational practices’ (BCOP) documents, akin to those from NANOG and IPB COP communities.
Key findings included:
- Operators desire protocols addressing deployment and management concerns from the outset.
- A need for mechanisms requiring operator validation before standards advancement.
- Calls for dedicated tracks mandating input from at least two operators per document class.
These insights fueled Internet-Drafts, such as draft-opsawg-operators-ietf, synthesizing feedback into actionable recommendations.
IETF 91: A Turning Point for Collaboration
IETF 91, held in Honolulu from November 9-14, 2014, marked a milestone. Pre-meeting buzz centered on operator involvement, with the Internet Engineering and Planning Group (IEPG) dedicating Sunday sessions to the topic. The highlight was a Wednesday morning session in ‘Coral 1’ (0900-1130 HST), featuring detailed agendas and draft discussions.
Participants explored barriers like time constraints for mid-sized operators and proposed bridges, such as regional engagement events and simplified contribution tools. Outcomes emphasized phased approaches: surveying the community, analyzing results via drafts, and implementing systemic changes for sustained participation.
Structural Pillars of the IETF
Understanding operator integration requires grasping IETF’s architecture, as outlined in RFC 9281.1 The Internet Engineering Steering Group (IESG) oversees technical activities, approving working groups and documents. The Internet Architecture Board (IAB) provides architectural oversight and reviews charters. Operators can influence via working groups (WGs) like OPSAWG, focusing on operational management.
| Entity | Role | Operator Opportunities |
|---|---|---|
| IETF Community | Develops standards | Mailing lists, meetings |
| IESG | Manages WG charters, document approval | Review participation, appeals |
| IAB | Architectural advice, oversight | Expert commentary on designs |
| Working Groups (e.g., OPSAWG) | Protocol-specific work | Direct contributions, reviews |
This structure offers multiple entry points, yet operator utilization remains low outside mega-providers like Google or large telcos.
Challenges Facing Operator Engagement
Several hurdles persist. Large operators from tech giants often prioritize niche needs, sidelining broader concerns, as noted in industry analyses.4 Smaller entities face resource shortages—time, travel, and expertise. Vendor dominance in funding and attendance further skews dynamics. Moreover, operators may lack awareness of when their input is crucial, missing early design phases.
A 2014 OPSAWG slide deck echoed these, questioning if ‘operators always know when their input is needed’ and if engagement levels match other stakeholders.9
Strategic Pathways Forward
Addressing these requires multifaceted strategies:
- Surveys and Feedback Loops: Regular polls to gauge needs and track progress.
- Operational Requirements: Introduce document classes needing operator sign-off, ensuring diverse buy-in.
- BCOP Integration: Formalize operational best practices within IETF streams, drawing from NANOG models.
- Accessibility Improvements: Virtual participation, regional hubs, and streamlined tools for non-experts.
- Partnerships: Collaborate with forums like IEPG and Internet Society for outreach.
Post-IETF 91 updates from the Internet Society reported productive exchanges, with drafts advancing to refine these ideas.6
Modern Relevance and Evolution
Though rooted in 2014 events, these discussions remain pertinent amid rising complexities like 5G, edge computing, and IPv6 scaling. Recent IETF meetings continue OPSAWG efforts on autonomic networks, reducing OpEx for managed infrastructures.3 Operator voices are increasingly vital for standards tackling security, privacy, and sustainability.
The IETF’s open model endures, but balanced input is key to its success. As RFC 9281 affirms, operators are integral to ‘the smooth operation of the Internet.’1
Practical Steps for Operators
Aspiring contributors can start small:
- Subscribe to relevant WG mailing lists via ietf.org.
- Attend meetings (in-person or remote) and review agendas on datatracker.ietf.org.
- Contribute to drafts via tools.ietf.org.
- Join operator forums like NANOG for peer support.
Organizations should allocate resources, fostering a culture of standards participation.
FAQs on IETF Operator Involvement
What is the IETF?
The IETF develops open Internet standards through working groups and community consensus.
Why do operators matter in standards?
They ensure protocols work in real networks, addressing deployment realities often missed by theorists.
How can small operators participate?
Via mailing lists, remote meeting attendance, and commenting on drafts—no travel required.
What came of IETF 91 discussions?
They spurred surveys, drafts, and calls for operator-mandated document tracks.
Is progress being made?
Yes, with ongoing WG work and initiatives like BCOP integration.
In summary, elevating operator roles in the IETF promises standards that better serve the Internet’s operational demands. From IETF 91’s foundational talks to today’s imperatives, the path forward lies in inclusive collaboration.
References
- Entities Involved in the IETF Standards Process — Internet Engineering Task Force (IETF). 2022-06-22. https://www.rfc-editor.org/rfc/rfc9281.html
- Operators and the IETF – Netnod — Netnod. 2016-11. https://www.netnod.se/sites/default/files/2016-11/Jan_Zorz_Operators-IETF_NETNOD.pdf
- IETF Working Group 91 High Level Summary — IETF Wiki. 2014-11. https://wiki.ietf.org/group/ops/IETF91summary
- Understanding How The IETF Works — Packet Pushers. Accessed 2026. https://packetpushers.net/blog/understanding-ietf-works/
- Operators and the IETF – the survey — IETF Proceedings. 2014. https://www.ietf.org/proceedings/90/slides/slides-90-opsawg-8.pdf
- Operators and the IETF: Update from IETF 91 — Internet Society. 2014-12. https://www.internetsociety.org/blog/2014/11/operators-and-the-ietf-update-from-ietf-91/

