Developer docs
API playgroundTry for free, no card

Search company profiles

Internet Engineering Task Force (IETF)

Full company profile

uuid000boy8

Namestring
Internet Engineering Task Force (IETF)
Legal namestring
Internet Engineering Task Force
Websiteurl
ietf.org
Company typeenum
Private
Founded yearint
1986
Descriptiontext

The Internet Engineering Task Force (IETF), founded in 1986, is the premier open international standards development organization for the Internet. Its core output is the RFC (Request for Comments) series, with thousands of published documents specifying the technical foundations of the Internet including TCP/IP, DNS, TLS 1.3, QUIC, HTTP, and WebRTC, used daily by billions of people. The IETF is volunteer-driven, with more than 7,000 active participants annually working through mailing lists and working groups organized by Areas, supplemented by three week-long in-person meetings per year averaging 1,000-1,500 onsite and 600+ remote participants each. Supporting technical infrastructure includes the IETF Datatracker (document and meeting management), the RFC Production Center (editorial services), and coordination with IANA via ICANN/PTI for protocol parameter assignment.

The IETF's products and services consist of standards documents (RFCs), preliminary Internet-Drafts, the Datatracker platform, Hackathons and Code Sprints, and IETF Meetings; these outputs are freely available to the public. The organization operates through the IETF Administration LLC, a Delaware single-member LLC and 501(c)(3) under the Internet Society (ISOC), which provides the corporate and legal home for the IETF, IAB, and IRTF. The IETF maintains formal liaison relationships with ITU-T, 3GPP, IEEE, W3C, ISO/IEC, CableLabs, Broadband Forum, and others, plus a coordination function with the IETF Trust (est. 2005) that holds standards-related intellectual property.

The IETF is funded by annual contributions funneled through ISOC, meeting registration fees (the only direct charge to participants, with fee waivers available), and corporate sponsorships from Global Hosts and donors including Cisco, Ericsson, Verisign, Nokia, Huawei, Comcast NBCUniversal, and Juniper Networks. It employs approximately 51-100 paid staff supporting a global volunteer community; pricing is entirely freemium for the standards themselves, with monetization restricted to meeting registration.

Short descriptiontext

The Internet Engineering Task Force (IETF) is the premier open international standards development organization for the Internet, producing voluntary RFC protocol specifications used daily by billions of people across network operators, equipment vendors, software developers, and hardware manufacturers worldwide.

Operating statusenum
Operating
Ownership categoryenum
Headcount rangeband
51–100
akta.pro rankint
HeadquartersFremont, United States
HQ citystring
Fremont
HQ countrystring
United States
HQ regionstring
North America
Markets served

Serves global market

Offices1 record

Each record includes

City, Country, Type, Description, Source

Keyword5 values
Internet standards development, open protocol specifications, RFC publications, Internet engineering, voluntary technical standards
Industry3 codes
PRIMARYMPAJACAB
Standards Development & Publishing (SDOs, Technical Standards)
Media, Entertainment & Sports/Publishing (Books, News, Magazines)/Professional & Legal Publishing (Standards, Compliance, Reference)
SECONDARYBPADANAA
International Standards Development & Standardization Bodies
Business & Public Services/International Organizations & Development/International Standards, Policy & Regulatory Cooperation
SECONDARYBPADAAAJ
International Standards, Norms & Technical Regulatory Bodies
Business & Public Services/International Organizations & Development/Multilateral & Intergovernmental Organizations
NAICS code2 codes
  • Religious, Grantmaking, Civic, Professional, and Similar Organizations813
  • Labor Unions and Similar Labor Organizations813930
SIC code2 codes
  • Miscellaneous Publishing2741
  • Services-Membership Organizations8600
Product category
Internet Standards Development
Social media profiles3 records
GTM motion1 record

Each record includes

Type, Description, Source

Revenue model3 records
1Internet Society Funding
TypeSubscription Recurring
Description

Primary ongoing financial support from the Internet Society, a 501(c)(3) organization. The IETF LLC is a single member LLC of ISOC.

ietf.org
2Meeting Registration Fees
TypeOne Time License
Description

The only fee the IETF charges is for registering for IETF meetings, with options in place to prevent that fee from becoming a barrier to participation.

ietf.org
3Corporate Sponsorship and Donations
TypeOthers
Description

Funding from corporate sponsors and individual donors. Companies like Cisco, Ericsson, Verisign, Nokia, Huawei, and Comcast NBCUniversal provide financial support as hosts and sponsors.

ietf.org
Marketing channels6 records

Each record includes

Title, Type, Stage, Description, Source

Distribution channels3 records

Each record includes

Title, Type, Scope, Target buyer, Description, Source

Cost components6 values
Personnel, Operations, Technology or R&D, Infrastructure, Marketing or Sales, Others
Pricing details2 tiers
1Free access to all standards and documentation
ModelFreemiumBilling cadenceOther
Notes

All RFCs and IETF technical documents are freely available to the public. No licensing fees are required to implement IETF standards.

ietf.org
2Meeting Registration Fee
ModelSubscriptionBilling cadenceAnnual
Notes

Registration fees for IETF meetings are charged to cover venue and administrative costs. Fee waivers are available to prevent cost from being a barrier to participation.

ietf.org
GTM typeB2B
B2B
Offering typeServices
Services
Core offering1 text field

The IETF develops voluntary, open Internet technical standards known as RFCs (Requests for Comments), covering protocols such as TCP/IP, DNS, TLS 1.3, QUIC, HTTP, and WebRTC. Its core operational products are the standards documents themselves, the IETF Datatracker system that provides transparency on the development process, Internet-Drafts as preliminary work products, three annual week-long meetings that convene working groups, and supporting services such as the RFC Production Center and IANA protocol parameter registry. All standards are published royalty-free and are freely accessible to the global community.

Differentiator
Functional benefit
Problem solved
Quantifiable outcome1 of 3 values shown
  • Protocols specified by IETF are used by billions of people every day for services such as real-time collaboration, email, and the domain name system
+2 more records
Product overview1 text field

The Internet Engineering Task Force (IETF) is the premier standards development organization for the Internet, founded in 1986. Rather than a traditional product company, IETF produces voluntary technical standards that are adopted by Internet users, network operators, and equipment vendors. The core offerings include RFCs (Requests for Comments) as the primary standards documents, the Datatracker system for tracking documents and working groups, Internet-Drafts as preliminary work products, and IETF Meetings/Hackathons for in-person collaboration. Supporting functions include the RFC Production Center for editorial services and IANA for protocol parameter administration. IETF standards cover protocols like TLS 1.3, QUIC, WebRTC, and define foundational Internet technologies including DNS, routing, and transport systems used by billions of people daily.

Product and service7 records
1RFCs (Requests for Comments)
CategoryInternet Standards Documents
Description

The IETF's primary technical documentation published as RFCs (Requests for Comments) describing the Internet's technical foundations, including addressing, routing, transport technologies, and protocols such as TLS 1.3, QUIC, and WebRTC. Used by network operators, equipment vendors, software developers, and hardware manufacturers worldwide.

2IETF Datatracker
CategoryProcess Tracking and Transparency System
Description

An online system containing data about IETF documents, working groups, meetings, agendas, minutes, presentations, and standards process information; provides transparency on the process that results in each RFC publication. Used by IETF participants, implementers, and the broader Internet community.

3Internet-Drafts
CategoryWorking Documents
Description

Discussion documents produced by IETF participants that serve as the starting point for new work; reviewed and developed in Working Groups and through mailing lists before potentially being adopted and progressed toward RFC status. Used by IETF participants as the input to the standards process.

4IETF Meetings
CategoryStandards Collaboration Events
Description

Three week-long in-person meetings per year where IETF Working Groups convene to advance technical work, with multiple simultaneous Working Group sessions. Meetings register on-site and remote participants and serve as the primary in-person venue for standards collaboration.

5IETF Hackathons
CategoryImplementation Events
Description

Hands-on collaborative events held during IETF meetings where developers and subject-matter experts validate, implement, and improve IETF standards and develop proof-of-concept implementations of new protocol work.

6RFC Production Center (RPC)
CategoryStandards Publication Service
Description

The professional editorial team responsible for the production, editing, and publication of RFCs, ensuring technical accuracy and proper formatting of all IETF standards documents. The RPC operates within the IETF Administration LLC.

7IANA Protocol Parameter Registry
CategoryProtocol Parameter Administration
Description

The Internet Assigned Numbers Authority (IANA) administers protocol parameter registries for IETF protocols, including port numbers, MIME types, and other critical Internet identifiers. Administered by ICANN through Public Technical Identifiers (PTI) under arrangement with the IETF.

Scale indicator7 records

Each record includes

Type, Value, Description, Source

Partnership13 partners
1TIP Mantra Subgroup
Strategic tierMinorTypeStrategic or Co-development PartnerAnnounced on2025-08-27
Description

The Telecom Infra Project's Mantra subgroup backed the IETF 126 hackathon event in Vienna targeting network inventory YANG model validation and harmonization. This partnership provides hands-on setting to prove up emerging network inventory concepts.

tomshardware.com
Strategic tierCoreTypeStrategic or Co-development Partner
Description

Liaison relationship between IETF and 3GPP for coordination on mobile telecommunications standards. Liaison manager: Charles Eckel. RFC 3113 documents the relationship.

Strategic tierCoreTypeStrategic or Co-development Partner
Description

Formal liaison relationship for coordination on broadband standards. Liaison manager: Xueyan Song.

Strategic tierCoreTypeStrategic or Co-development Partner
Description

Liaison relationship for cable technology standards coordination. Liaison manager: Greg White. RFC 4965 documents the relationship.

5ITU-T
Strategic tierCoreTypeStrategic or Co-development Partner
Description

Important liaison relationship with ITU-T for international telecommunications standards coordination. Liaison manager: Scott Mansfield. RFC 6756 documents the relationship.

ietf.org
Strategic tierCoreTypeStrategic or Co-development Partner
Description

Liaison relationships with IEEE 802.1 and IEEE Standards Association for networking standards coordination. Liaison managers: János Farkas (802.1) and Russ Housley (IEEE-SA).

Strategic tierCoreTypeStrategic or Co-development Partner
Description

Liaison relationship with W3C for web standards coordination. Liaison manager: Martin Thomson.

8ISO/IEC
Strategic tierCoreTypeStrategic or Co-development Partner
Description

Multiple liaison relationships with ISO/IEC JTC1 subcommittees (SC2, SC6, SC29) and technical committees (TC46, TC154, TC204) for international standards coordination.

ietf.org
Strategic tierMinorTypeStrategic or Co-development Partner
Description

Liaison relationship with ECMA TC39 for coordination on scripting and programming language standards. Liaison manager: Matt Miller.

Strategic tierMinorTypeStrategic or Co-development Partner
Description

Liaison relationship with Messaging, Malware and Mobile Anti-Abuse Working Group. Liaison manager: Bron Gondwana.

Strategic tierMinorTypeStrategic or Co-development Partner
Description

Liaison relationship with Unicode Consortium for character encoding standards coordination. Liaison manager: Patrik Fältström.

Strategic tierCoreTypeStrategic or Co-development Partner
Description

The Internet Assigned Numbers Authority (IANA) administers many parameters of IETF protocols through arrangement with ICANN and Public Technical Identifiers (PTI). Multiple MoU supplements govern the relationship.

13IETF Trust
Strategic tierCoreTypeStrategic or Co-development Partner
Description

The IETF Trust was created to acquire, hold, and maintain intellectual property and other property used in connection with Internet standards. Created by ISOC and CNRI as settlors in 2005.

ietf.org
Recent move9 records

Each record includes

Date, Type, Title, Description, Source

Expansion highlight6 records

Each record includes

Type, Description

Peers10 records
TypeDirect peer
Description

3GPP coordinates mobile telecommunications standards (4G, 5G, NR) and maintains a formal liaison with the IETF (RFC 3113). It is the most direct peer in scope: producing global, voluntary, royalty-free telecom standards through a multi-organization partnership.

TypeRegional player
Description

ETSI is the European regional SDO for telecommunications, producing standards such as DECT and 5G specifications alongside 3GPP. It is comparable in mission — open, consensus-based telecom standards — but is regionally anchored, while the IETF's remit is explicitly global.

3Ecma International
TypeEmerging player
Description

Ecma International develops standards for scripting languages (notably ECMAScript/JavaScript via TC39) and has a formal liaison to the IETF. It is comparable as an open, industry-driven SDO but operates at a smaller scale and in adjacent (programming language) rather than networking territory.

TypeEmerging player
Description

OASIS is an open-standards consortium producing specifications in security, IoT, and cloud (e.g., SAML, AMQP, MQTT). It is comparable to the IETF as an open, royalty-free SDO with member-driven working groups, but focuses on adjacent technology areas rather than core Internet protocols.

TypeDirect peer
Description

IEEE-SA (and IEEE 802) is a peer SDO responsible for Ethernet, Wi-Fi (802.11), and the 802.1 bridging suite, all of which interoperate with IETF protocols. The two organizations share the open, consensus-based standards model and coordinate via formal IETF–IEEE 802 liaison.

TypeDirect peer
Description

W3C is the principal global SDO for web standards, with a formal liaison relationship to the IETF. Both organizations produce royalty-free specifications that underpin the Internet and rely on open, member-driven processes — making W3C the closest analogue in mission and operating model.

TypeBroad incumbent
Description

ANSI is the US national standards body and the US member of ISO and IEC. It is comparable to the IETF as a coordinator of consensus-based standards development, but operates as an umbrella/coordination body rather than a direct technical SDO.

TypeBroad incumbent
Description

ITU is the UN-affiliated international body for telecom standards (ITU-T, ITU-R), with a long-standing IETF liaison (RFC 6756). It is a comparable SDO in mission — global, treaty-rooted telecom standardization — but operates at government and operator level rather than the IETF's individual-contributor model.

9ISO / IEC JTC 1
TypeBroad incumbent
Description

ISO/IEC JTC 1 is the joint technical committee for information technology standards. It maintains multiple liaison relationships with the IETF (SC6, SC29, TC46, etc.) and is comparable as a global, consensus-based standards body, though its scope is far broader than networking.

TypeOthers
Description

ISOC is the single-member parent of the IETF Administration LLC and the IETF's primary ongoing financial backer. It is not a peer in the competitive sense, but is the closest governance and funding analogue — a 501(c)(3) that supports the open Internet and Internet standards globally.

Market position
Strengths5 records

Each record includes

Headline, Details, Source

Weaknesses5 records

Each record includes

Headline, Details, Source

Competitive moat6 records

Each record includes

Type, Details

Key risks6 records

Each record includes

Headline, Details, Source

Key highlights7 records

Each record includes

Headline, Details, Source

Customer concentration

Classification, Details

Named customers4 records

Each record includes

Name, Industry, Type, Use case, Source, UUID

Segment3 records

Each record includes

Title, Type, Primary, Description, Pain point addressed, Use case, Source

Ideal customer profile3 records

Each record includes

Profile, Firmographic size, Sales motion, Sales cycle length, Buying structure, Purchase trigger, Buyer persona, Geography, Industry vertical, Primary use case, Description, Pain points, Evidence proof points, Target buyer

Technology focused
Yes
API detail
Has APIbool
Yes

Docs URL, Description

AI maturity
App detail

Has app

Feature3 records

Each record includes

Title, Differentiator, Description, Source

Core technology
Revenue estimate
Valuation estimate
Number of profiles
Profiles13 records

Each record includes

Name, Designation, Designation category, Overview, Profile commentary, Source

No data
No data
Funding overview

Funding stage, Last funding date, Total funding USD

Funding rounds

Each record includes

Round, Amount USD, Date, Pre money valuation, Total investors, Investors, News

Investors

Each record includes

Name, Type, Date of entry, Rounds participated, Website

Funding detail is available on the Subscription and Enterprise plan.Contact sales →

M&A

Each record includes

Name, Acquisition type, Announced date, Completed date, Status, Website, News

Investment

Each record includes

Name, Round, Announced date, Lead investor, Website, News

M&A and investment is available on the Subscription and Enterprise plan.Contact sales →

Internet Engineering Task Force (IETF)

Internet Standards Developmentietf.org

The Internet Engineering Task Force (IETF) is the premier open international standards development organization for the Internet, producing voluntary RFC protocol specifications used daily by billions of people across network operators, equipment vendors, software developers, and hardware manufacturers worldwide.

What Internet Engineering Task Force (IETF) does

The Internet Engineering Task Force (IETF), founded in 1986, is the premier open international standards development organization for the Internet. Its core output is the RFC (Request for Comments) series, with thousands of published documents specifying the technical foundations of the Internet including TCP/IP, DNS, TLS 1.3, QUIC, HTTP, and WebRTC, used daily by billions of people. The IETF is volunteer-driven, with more than 7,000 active participants annually working through mailing lists and working groups organized by Areas, supplemented by three week-long in-person meetings per year averaging 1,000-1,500 onsite and 600+ remote participants each. Supporting technical infrastructure includes the IETF Datatracker (document and meeting management), the RFC Production Center (editorial services), and coordination with IANA via ICANN/PTI for protocol parameter assignment.

The IETF's products and services consist of standards documents (RFCs), preliminary Internet-Drafts, the Datatracker platform, Hackathons and Code Sprints, and IETF Meetings; these outputs are freely available to the public. The organization operates through the IETF Administration LLC, a Delaware single-member LLC and 501(c)(3) under the Internet Society (ISOC), which provides the corporate and legal home for the IETF, IAB, and IRTF. The IETF maintains formal liaison relationships with ITU-T, 3GPP, IEEE, W3C, ISO/IEC, CableLabs, Broadband Forum, and others, plus a coordination function with the IETF Trust (est. 2005) that holds standards-related intellectual property.

The IETF is funded by annual contributions funneled through ISOC, meeting registration fees (the only direct charge to participants, with fee waivers available), and corporate sponsorships from Global Hosts and donors including Cisco, Ericsson, Verisign, Nokia, Huawei, Comcast NBCUniversal, and Juniper Networks. It employs approximately 51-100 paid staff supporting a global volunteer community; pricing is entirely freemium for the standards themselves, with monetization restricted to meeting registration.

Internet Engineering Task Force (IETF) firmographics

Firmographics
Name
Internet Engineering Task Force (IETF)
Legal name
Internet Engineering Task Force
Website
https://ietf.org
Company type
Private
Founded year
1986
Operating status
Operating
Headcount range
51–100 employees
Short description
The Internet Engineering Task Force (IETF) is the premier open international standards development organization for the Internet, producing voluntary RFC protocol specifications used daily by billions of people across network operators, equipment vendors, software developers, and hardware manufacturers worldwide.
Ownership category
akta.pro rank

Internet Engineering Task Force (IETF) industry classification

Industry
Product category
Internet Standards Development
NAICS
Religious, Grantmaking, Civic, Professional, and Similar Organizations (813), Labor Unions and Similar Labor Organizations (813930)
SIC
Miscellaneous Publishing (2741), Services-Membership Organizations (8600)
akta.pro industry
PRIMARYMPAJACAB
Standards Development & Publishing (SDOs, Technical Standards)
Media, Entertainment & Sports/Publishing (Books, News, Magazines)/Professional & Legal Publishing (Standards, Compliance, Reference)
SECONDARYBPADANAA
International Standards Development & Standardization Bodies
Business & Public Services/International Organizations & Development/International Standards, Policy & Regulatory Cooperation
SECONDARYBPADAAAJ
International Standards, Norms & Technical Regulatory Bodies
Business & Public Services/International Organizations & Development/Multilateral & Intergovernmental Organizations

Keywords

  • Internet standards development
  • Open protocol specifications
  • RFC publications
  • Internet engineering
  • Voluntary technical standards

Where Internet Engineering Task Force (IETF) is headquartered

Location

Headquarters

HQ city
Fremont
HQ country
United States
HQ region
North America

Offices1 record

Markets served

Internet Engineering Task Force (IETF) business model

Business model
GTM type
B2B
Offering type
Services
Cost components
Personnel, Operations, Technology or R&D, Infrastructure, Marketing or Sales, Others

Revenue model

  1. Internet Society Funding: Primary ongoing financial support from the Internet Society, a 501(c)(3) organization. The IETF LLC is a single member LLC of ISOC.
  2. Meeting Registration Fees: The only fee the IETF charges is for registering for IETF meetings, with options in place to prevent that fee from becoming a barrier to participation.
  3. Corporate Sponsorship and Donations: Funding from corporate sponsors and individual donors. Companies like Cisco, Ericsson, Verisign, Nokia, Huawei, and Comcast NBCUniversal provide financial support as hosts and sponsors.

Pricing tiers

ModelBillingPrice
FreemiumOtherFree access to all standards and documentation
SubscriptionAnnualMeeting Registration Fee

Go-to-market motion1 record

Distribution channels3 records

Marketing channels6 records

Internet Engineering Task Force (IETF) product offering

Product offering

Core offering

The IETF develops voluntary, open Internet technical standards known as RFCs (Requests for Comments), covering protocols such as TCP/IP, DNS, TLS 1.3, QUIC, HTTP, and WebRTC. Its core operational products are the standards documents themselves, the IETF Datatracker system that provides transparency on the development process, Internet-Drafts as preliminary work products, three annual week-long meetings that convene working groups, and supporting services such as the RFC Production Center and IANA protocol parameter registry. All standards are published royalty-free and are freely accessible to the global community.

Product overview

The Internet Engineering Task Force (IETF) is the premier standards development organization for the Internet, founded in 1986. Rather than a traditional product company, IETF produces voluntary technical standards that are adopted by Internet users, network operators, and equipment vendors. The core offerings include RFCs (Requests for Comments) as the primary standards documents, the Datatracker system for tracking documents and working groups, Internet-Drafts as preliminary work products, and IETF Meetings/Hackathons for in-person collaboration. Supporting functions include the RFC Production Center for editorial services and IANA for protocol parameter administration. IETF standards cover protocols like TLS 1.3, QUIC, WebRTC, and define foundational Internet technologies including DNS, routing, and transport systems used by billions of people daily.

Differentiator

Problem solved

Functional benefit

Products and services

  • RFCs (Requests for Comments) The IETF's primary technical documentation published as RFCs (Requests for Comments) describing the Internet's technical foundations, including addressing, routing, transport technologies, and protocols such as TLS 1.3, QUIC, and WebRTC. Used by network operators, equipment vendors, software developers, and hardware manufacturers worldwide.
  • IETF Datatracker An online system containing data about IETF documents, working groups, meetings, agendas, minutes, presentations, and standards process information; provides transparency on the process that results in each RFC publication. Used by IETF participants, implementers, and the broader Internet community.
  • Internet-Drafts Discussion documents produced by IETF participants that serve as the starting point for new work; reviewed and developed in Working Groups and through mailing lists before potentially being adopted and progressed toward RFC status. Used by IETF participants as the input to the standards process.
  • IETF Meetings Three week-long in-person meetings per year where IETF Working Groups convene to advance technical work, with multiple simultaneous Working Group sessions. Meetings register on-site and remote participants and serve as the primary in-person venue for standards collaboration.
  • IETF Hackathons Hands-on collaborative events held during IETF meetings where developers and subject-matter experts validate, implement, and improve IETF standards and develop proof-of-concept implementations of new protocol work.
  • RFC Production Center (RPC) The professional editorial team responsible for the production, editing, and publication of RFCs, ensuring technical accuracy and proper formatting of all IETF standards documents. The RPC operates within the IETF Administration LLC.
  • IANA Protocol Parameter Registry The Internet Assigned Numbers Authority (IANA) administers protocol parameter registries for IETF protocols, including port numbers, MIME types, and other critical Internet identifiers. Administered by ICANN through Public Technical Identifiers (PTI) under arrangement with the IETF.

Quantifiable outcome

  • Protocols specified by IETF are used by billions of people every day for services such as real-time collaboration, email, and the domain name system
  • +2 more outcomes

Companies that use Internet Engineering Task Force (IETF)

Customer profile

Named customers4 records

Segments3 records

Ideal customer profiles3 records

Internet Engineering Task Force (IETF) technology and API

Technology

Technology focussed Yes

API detail

Has API
Yes
API docs
API detail

Core technology

AI maturity

App detail

Feature3 records

Internet Engineering Task Force (IETF) partnerships and signals

Strategic signal

Partnerships

13 partnerships are on record, tiered minor and core.

  • TIP Mantra SubgroupminorStrategic or Co-development Partner · 27 August 2025The Telecom Infra Project's Mantra subgroup backed the IETF 126 hackathon event in Vienna targeting network inventory YANG model validation and harmonization. This partnership provides hands-on setting to prove up emerging network inventory concepts.
  • 3GPPcoreStrategic or Co-development PartnerLiaison relationship between IETF and 3GPP for coordination on mobile telecommunications standards. Liaison manager: Charles Eckel. RFC 3113 documents the relationship.
  • Broadband ForumcoreStrategic or Co-development PartnerFormal liaison relationship for coordination on broadband standards. Liaison manager: Xueyan Song.
  • CableLabscoreStrategic or Co-development PartnerLiaison relationship for cable technology standards coordination. Liaison manager: Greg White. RFC 4965 documents the relationship.
  • ITU-TcoreStrategic or Co-development PartnerImportant liaison relationship with ITU-T for international telecommunications standards coordination. Liaison manager: Scott Mansfield. RFC 6756 documents the relationship.
  • IEEE/ IEEE-SAcoreStrategic or Co-development PartnerLiaison relationships with IEEE 802.1 and IEEE Standards Association for networking standards coordination. Liaison managers: János Farkas (802.1) and Russ Housley (IEEE-SA).
  • W3CcoreStrategic or Co-development PartnerLiaison relationship with W3C for web standards coordination. Liaison manager: Martin Thomson.
  • ISO/IECcoreStrategic or Co-development PartnerMultiple liaison relationships with ISO/IEC JTC1 subcommittees (SC2, SC6, SC29) and technical committees (TC46, TC154, TC204) for international standards coordination.
  • ECMA TC39minorStrategic or Co-development PartnerLiaison relationship with ECMA TC39 for coordination on scripting and programming language standards. Liaison manager: Matt Miller.
  • M3AAWGminorStrategic or Co-development PartnerLiaison relationship with Messaging, Malware and Mobile Anti-Abuse Working Group. Liaison manager: Bron Gondwana.
  • Unicode ConsortiumminorStrategic or Co-development PartnerLiaison relationship with Unicode Consortium for character encoding standards coordination. Liaison manager: Patrik Fältström.
  • ICANN/ IANAcoreStrategic or Co-development PartnerThe Internet Assigned Numbers Authority (IANA) administers many parameters of IETF protocols through arrangement with ICANN and Public Technical Identifiers (PTI). Multiple MoU supplements govern the relationship.
  • IETF TrustcoreStrategic or Co-development PartnerThe IETF Trust was created to acquire, hold, and maintain intellectual property and other property used in connection with Internet standards. Created by ISOC and CNRI as settlors in 2005.

Scale indicators7 records

Recent moves9 records

Expansion highlights6 records

Internet Engineering Task Force (IETF) competitors and assessment

Company assessment

Direct peers

  • 3GPP: 3GPP coordinates mobile telecommunications standards (4G, 5G, NR) and maintains a formal liaison with the IETF (RFC 3113). It is the most direct peer in scope: producing global, voluntary, royalty-free telecom standards through a multi-organization partnership.
  • IEEE Standards Association: IEEE-SA (and IEEE 802) is a peer SDO responsible for Ethernet, Wi-Fi (802.11), and the 802.1 bridging suite, all of which interoperate with IETF protocols. The two organizations share the open, consensus-based standards model and coordinate via formal IETF–IEEE 802 liaison.
  • World Wide Web Consortium (W3C): W3C is the principal global SDO for web standards, with a formal liaison relationship to the IETF. Both organizations produce royalty-free specifications that underpin the Internet and rely on open, member-driven processes — making W3C the closest analogue in mission and operating model.

Regional players

  • ETSI (European Telecommunications Standards Institute): ETSI is the European regional SDO for telecommunications, producing standards such as DECT and 5G specifications alongside 3GPP. It is comparable in mission — open, consensus-based telecom standards — but is regionally anchored, while the IETF's remit is explicitly global.

Emerging players

  • Ecma International: Ecma International develops standards for scripting languages (notably ECMAScript/JavaScript via TC39) and has a formal liaison to the IETF. It is comparable as an open, industry-driven SDO but operates at a smaller scale and in adjacent (programming language) rather than networking territory.
  • OASIS Open: OASIS is an open-standards consortium producing specifications in security, IoT, and cloud (e.g., SAML, AMQP, MQTT). It is comparable to the IETF as an open, royalty-free SDO with member-driven working groups, but focuses on adjacent technology areas rather than core Internet protocols.

Broad incumbents

  • ANSI (American National Standards Institute): ANSI is the US national standards body and the US member of ISO and IEC. It is comparable to the IETF as a coordinator of consensus-based standards development, but operates as an umbrella/coordination body rather than a direct technical SDO.
  • ITU (International Telecommunication Union): ITU is the UN-affiliated international body for telecom standards (ITU-T, ITU-R), with a long-standing IETF liaison (RFC 6756). It is a comparable SDO in mission — global, treaty-rooted telecom standardization — but operates at government and operator level rather than the IETF's individual-contributor model.
  • ISO / IEC JTC 1: ISO/IEC JTC 1 is the joint technical committee for information technology standards. It maintains multiple liaison relationships with the IETF (SC6, SC29, TC46, etc.) and is comparable as a global, consensus-based standards body, though its scope is far broader than networking.

Others

  • Internet Society (ISOC): ISOC is the single-member parent of the IETF Administration LLC and the IETF's primary ongoing financial backer. It is not a peer in the competitive sense, but is the closest governance and funding analogue — a 501(c)(3) that supports the open Internet and Internet standards globally.

Market position

Strengths5 records

Weaknesses5 records

Competitive moat6 records

Key risks6 records

Key highlights7 records

Customer concentration

Internet Engineering Task Force (IETF) social profiles

Digital presence

Internet Engineering Task Force (IETF) financial estimates

Financial estimate

Revenue estimate

Valuation estimate

Internet Engineering Task Force (IETF) leadership team

Management profile

Number of profiles

Profiles13 records

Internet Engineering Task Force (IETF) funding detail

Funding detail

Funding overview

Funding rounds

Investors

Funding detail is available on the Subscription and Enterprise plan.Contact sales →

Internet Engineering Task Force (IETF) M&A and investment

M&A and investment

M&A

Investments

M&A and investment is available on the Subscription and Enterprise plan.Contact sales →

Frequently asked questions about Internet Engineering Task Force (IETF)

What does Internet Engineering Task Force (IETF) do?

The IETF develops voluntary, open Internet technical standards known as RFCs (Requests for Comments), covering protocols such as TCP/IP, DNS, TLS 1.3, QUIC, HTTP, and WebRTC. Its core operational products are the standards documents themselves, the IETF Datatracker system that provides transparency on the development process, Internet-Drafts as preliminary work products, three annual week-long meetings that convene working groups, and supporting services such as the RFC Production Center and IANA protocol parameter registry. All standards are published royalty-free and are freely accessible to the global community.

Is Internet Engineering Task Force (IETF) a public or private company?

Internet Engineering Task Force (IETF) is a private company. It is classified as nonprofit foundation owned and is currently operating.

When was Internet Engineering Task Force (IETF) founded?

Internet Engineering Task Force (IETF) was founded in 1986. It employs 51 to 100 people.

Where is Internet Engineering Task Force (IETF) based?

Internet Engineering Task Force (IETF) is headquartered in Fremont, United States, in the North America region.

How does Internet Engineering Task Force (IETF) make money?

Three revenue lines are on record. Internet Society Funding is the primary driver. The others are meeting Registration Fees and corporate Sponsorship and Donations.

Who are Internet Engineering Task Force (IETF)'s main competitors?

Direct peers on record are 3GPP, IEEE Standards Association and World Wide Web Consortium (W3C). ETSI (European Telecommunications Standards Institute) is listed as a regional player. Emerging players are Ecma International and OASIS Open. Broad incumbents are ANSI (American National Standards Institute), ITU (International Telecommunication Union) and ISO / IEC JTC 1. Internet Society (ISOC) is listed as an others.

Does Internet Engineering Task Force (IETF) have an API?

Yes. The IETF provides the Datatracker system as a public-facing tool containing data about IETF documents, working groups, meetings, agendas, minutes, presentations, and more. The Datatracker API enables access to this organizational data. Developer documentation is at datatracker.ietf.org.

What industry is Internet Engineering Task Force (IETF) in?

Internet Engineering Task Force (IETF)'s product category is Internet Standards Development. Its primary akta.pro industry code is MPAJACAB, Standards Development & Publishing (SDOs, Technical Standards), with a secondary code of BPADANAA, International Standards Development & Standardization Bodies. Its NAICS code is 813 and its SIC code is 2741.

Unlock the full company data

50 free credits on sign-up, no credit card required.

Contact sales
Live signals
Wikipedia.localhostIn 1999, the Internet Engineering Task Force reserved the DNS labels localhost, example, invalid, and test so they could not be installed into the root zone. The reservation reduces the likelihood of conflict and confusion, allowing these names for documentation or local testing.NateAI 업계, 학습용 웹 자료 수집 거부 지원…무분별한 크롤링에 제동 : 네이트 뉴스AI companies including OpenAI, Google, and Microsoft are supporting a common standard to let website operators block AI learning data collection. The standard, developed with IETF, will be adopted by Google and Microsoft next year, with OpenAI following within months. It aims to give operators control over content use, allowing them to block AI learning while permitting search indexing.Quantum ZeitgeistML-DSA certificates use X.509, but aren’t yet for public TLS.The IETF finalized RFC 9881 in October 2025 to encode ML-DSA signatures in X.509 certificates, but the CA/Browser Forum has not approved their use in publicly trusted TLS certificates as of October 2026. NIST's FIPS 204/205 standards define ML-DSA and SLH-DSA, with ML-DSA-65 offering smaller signatures than SLH-DSA. Organizations can build private post-quantum PKIs now, but public adoption remains pending.Business StandardWhy AI agents need an identity layer to act safely on web built for humansAmazon blocked Meta's Muse agent from its marketplace, citing unauthorized access and credential handling. NPCI paused its Unified Agentic Protocol for UPI, citing safety concerns. IETF drafts and Cloudflare's agent traffic controls aim to establish identity and authorization layers for AI agents.Quantum ZeitgeistIETF workshop to speed up post-quantum authentication rolloutThe Internet Architecture Board is holding a workshop in Prague on October 11-12, 2026, to gather real-world deployment data on post-quantum authentication, which lags behind post-quantum key establishment. The IETF is soliciting position papers by September 4, 2026, on constraints such as certificate chain size, latency, and hardware compatibility.Tech TimesIETF Formally Bans RSA and DHE from TLS 1.2: Over 175 Cipher Suites Off-LimitsThe IETF published RFC 10015 in July 2026, formally prohibiting RSA key exchange and finite-field Diffie-Hellman cipher suites in TLS 1.2 and DTLS 1.2 by changing the compliance status of over 175 cipher suites from "not recommended" to "explicitly impermissible" under IETF standards. The key shift is from advisory language ("SHOULD NOT") to mandatory prohibition ("MUST NOT"), eliminating any exception mechanism for implementations claiming compliance. Organizations running TLS 1.2 with legacy RSA or DHE cipher suites must audit and remediate their configurations, as these now represent IETF non-compliance even where PCI-DSS v4.0 requirements may appear satisfied.InfoWorldIETF publishes QUERY method to allow safe and idempotent HTTP requestsThe Internet Engineering Task Force (IETF) has published RFC 10008, introducing QUERY as a proposed standard HTTP request method that combines the body-passing capability of POST with the safety and idempotence of GET. The new method addresses a long-standing workaround where developers used POST for complex requests that exceed URI length limits, but lacked the ability to safely cache or retry them. Adoption remains limited—major browsers do not yet support QUERY, though server-side environments like Node.js and Go already support it—and broader implementation will require updates to related standards and infrastructure.Electronic Frontier FoundationThe Free and Open Web Is Under Attack at the IETFEFF and allies are fighting IETF proposals that would let websites block automated crawling, including AI preference signals and bot authentication. These changes could require licensing payments and give operators veto power over research, archival, and accessibility tools. EFF has resisted some proposals and will continue opposing them.Dark ReadingPost-Quantum Web Could be Safer, FasterThe Internet Engineering Task Force (IETF) has developed Merkle Tree Certificates (MTCs), a draft specification designed to protect against post-quantum computing attacks, with Google and Cloudflare actively testing the technology. Unlike current post-quantum encryption algorithms such as ML-DSA, which would increase certificate size from 3.1 KB to 14.7 KB per connection and slow down Web performance, MTCs require only approximately 840 bytes per page load while providing quantum-safe security. Google has announced plans to support MTCs in Chrome, with Chrome security teams concluding that adding more than 7 KB to Web communications would overburden the Internet infrastructure.DEV CommunityAI Agents Authentication: How to secure agentic LoginsThe article outlines a security framework for AI agents that utilizes passkeys for human authentication combined with OAuth 2.1 to grant scoped, delegated access to software systems. It cites GitHub's implementation of this model as a practical example and notes that industry bodies like the W3C and IETF are developing standardized protocols for agent identity and secure delegation.