By Jorge Cano, Senior Software Architect at LACNIC
The Internet Engineering Task Force (IETF) is a global community that brings together people from around the world to develop the standards that allow the Internet to work. It’s structured into different working groups, each of which focuses on a particular topic.
Within these groups, participants propose solutions to specific technical problems. Someone may bring forward a proposal or the need to solve a problem. A draft is then submitted, and if the group believes it’s relevant, the work begins. The goal is not to create a product, but to define a standard, one that any individual, organization, or company can implement. Because these are open standards, it’s important that they function consistently regardless of who implements them.
The IETF is structured into different areas (applications, security, transport, etc.), each of which includes several working groups. If an issue arises that doesn’t fall into any of the existing groups, there’s always the possibility of creating a new group to address it.
(Free access, no subscription required)
Participating in the IETF
Work at the IETF is completely open and free. Most discussions take place on mailing lists, where the level of debate is highly technical and attracts people with extensive experience in specific areas of the Internet. In recent years, efforts have been made to diversify participation, seeking to include people from all regions, not just Europe and the United States.
My first experience with the IETF goes back to their 61st meeting. Today, we’re attending IETF 123. At first, it can be quite a challenge: you arrive eager to follow all the discussions but soon realize that it’s better to focus on a single group and then gradually include others. Participants tend to have extensive experience, so overcoming the initial barrier to contributing isn’t always easy. I began attending simply to listen and learn; over time, I became an active participant and proposed solutions that are now part of the standards.
Co-Chairing an IETF Working Group
The IETF operates through small units known as working groups, each led by one or more chairs. Serving as a chair means coordinating discussions, managing timelines, and, most importantly, identifying when there is consensus. At the IETF, deciding is not about voting. Instead, it’s about making sure that as many people as possible agree and that no technical objections go unaddressed.
Participating in the IETF
Work at the IETF is completely open and free. Most discussions take place on mailing lists, where the level of debate is highly technical and attracts people with extensive experience in specific areas of the Internet. In recent years, efforts have been made to diversify participation, seeking to include people from all regions, not just Europe and the United States.
My first experience with the IETF goes back to their 61st meeting. Today, we’re attending IETF 123. At first, it can be quite a challenge: you arrive eager to follow all the discussions but soon realize that it’s better to focus on a single group and then gradually include others. Participants tend to have extensive experience, so overcoming the initial barrier to contributing isn’t always easy. I began attending simply to listen and learn; over time, I became an active participant and proposed solutions that are now part of the standards.
Co-Chairing an IETF Working Group
The IETF operates through small units known as working groups, each led by one or more chairs. Serving as a chair means coordinating discussions, managing timelines, and, most importantly, identifying when there is consensus. At the IETF, deciding is not about voting. Instead, it’s about making sure that as many people as possible agree and that no technical objections go unaddressed.
In my case, I currently serve as co-chair of REGEXT, a group that works on extensions to two key protocols:
Extensible Provisioning Protocol (EPP), used primarily to register objects in registries (today, mostly domain names), and
Registration Data Access Protocol (RDAP), which replaces Whois and offers more secure, standardized, and uniform responses.
At REGEXT, we work on extensions and enhancements to these protocols, as well as on developing new standards (currently between five and seven).
In the beginning, I participated in other groups such as DNSOPS (DNS Operations), SIDROPS (routing and RPKI), and DELEG (a new form of DNS zone delegation). There’s even a new group exploring how the Internet will operate in space, considering connectivity between space stations, satellites, and Earth.
What I Value about the IETF
Over the years, much has changed at the IETF. Today, the community is more open and welcoming to newcomers, with a clear effort to make the process less intimidating and more inclusive.
For me, the IETF’s main value is its collaborative spirit. Regardless of where they are or who they work for, people from all over the world can come together to define how the Internet works and ensure that those decisions are accessible to anyone who wishes to implement them.
If you’re interested in these topics, don’t miss the panel on “Technical Trends and the Role of the IETF,” which will take place on 7 October as part of LACNIC 44 – LACNOG 2025. This panel will explore key issues such as routing, security, IPv6, and network efficiency. People who have participated in the IETF will share specific experiences and discuss how the regional community can actively engage in developing global standards. Click here to register
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of LACNIC.
