IETF IPR Policy

IETF IPR Policy
Name	IETF IPR Policy
Established	1994
Type	Standards policy
Parent organization	Internet Engineering Task Force
Related	Internet Engineering Steering Group, RFC 2026, RFC 8179

IETF IPR Policy The IETF IPR Policy governs disclosure and licensing of intellectual property in Internet Engineering Task Force standards development, balancing contributions from stakeholders such as Cisco Systems, Microsoft, Google, Apple Inc., IBM, and Intel. It evolved through interactions among IETF Working Group participants, the Internet Architecture Board, and legal counsel from entities like Mozilla Foundation and Juniper Networks, reflecting tensions seen in cases involving Qualcomm, Nokia, Ericsson, Samsung Electronics, and standards debates tied to 3GPP, IEEE Standards Association, and ETSI.

Overview

The policy requires participants to disclose known patents and licensing intentions to the IETF Working Group and the IETF Secretariat, directing editors and chairs to record statements in a standardized manner. Its origins lie in early Internet history debates among Vint Cerf, Bob Kahn, and institutions including DARPA, NSF, MIT, and Stanford University over openness and proprietary claims. Over time it has intersected with legal frameworks such as United States patent law, European Patent Convention, and controversies involving Microsoft v. Motorola and Apple v. Samsung.

Scope and Definitions

The policy defines key terms like "essential patent" and "infringement" with operational links to standards activities, distinguishing contributors such as IETF Trust, ISOC, IAB, and corporate participants including Huawei, ZTE Corporation, Broadcom Inc., and ARM Holdings. It clarifies whether disclosures cover pending applications, granted claims, and expired rights, referencing procedural norms from RFC 2026 and later clarifications from RFC 8179. Definitions connect to broader intellectual property regimes involving World Intellectual Property Organization, Patent Cooperation Treaty, and national offices like the United States Patent and Trademark Office and the European Patent Office.

Disclosure and Licensing Procedures

Contributors must submit statements to working group mailing lists and editors, with templates that reflect licensing commitments such as royalty-free, RAND, RAND-Like, or non-assertion covenants. Practitioners from Cisco Systems, Ericsson, Siemens, Oracle Corporation, Red Hat, Facebook, and Amazon.com have submitted varied declarations, sometimes involving legal teams from firms like Skadden, Arps, Slate, Meagher & Flom, Latham & Watkins, and Morrison & Foerster. Disclosure practice also interacts with institutional policies at University of California, Carnegie Mellon University, Harvard University, Caltech, and corporate IP management strategies at Intel and IBM.

Implementation in IETF Process

Operationally, disclosure influences whether a document advances to Proposed Standard, Draft Standard, or Internet Standard, affecting streams like the Standards Track and Individual submissions. Chairs and area directors such as those appointed by the IETF Administrative Oversight Committee and the Internet Engineering Steering Group assess disclosures alongside technical reviews from groups including TLS WG, HTTPbis WG, QUIC WG, and Routing Area. Implementation decisions have been shaped by precedent in RFCs and by cases where stakeholders like Cisco, Microsoft, Google, and Apple Inc. negotiated licensing or withdrew claims.

Patent Ambiguity and RAND/FRAND Issues

Ambiguities around RAND (Reasonable and Non-Discriminatory) and FRAND (Fair, Reasonable, and Non-Discriminatory) commitments have provoked litigation and academic critique involving Unwired Planet, Huawei v. ZTE, Microsoft v. Motorola, and enforcement strategies deployed by firms including Qualcomm and Nokia. Courts in jurisdictions such as United States Court of Appeals for the Federal Circuit, European Court of Justice, and national courts have shaped interpretations of RAND/FRAND, influencing how IETF participants frame declarations. Tensions mirror debates within ETSI and ITU-T standardization contexts.

Criticisms and Revisions

Critics from civil society and industry, including advocates at Electronic Frontier Foundation, academics at Stanford Law School and Harvard Law School, and corporate rivals, have argued the policy can be opaque or insufficiently protective of implementers. Revisions over time were informed by episodes involving Motorola Mobility, Microsoft, Samsung Electronics, and strategic actors such as Google and Amazon Web Services, resulting in updates and clarifications published as RFCs and interpreted by the IAB and the IETF Administrative Oversight Committee.

Impact on Standards Adoption and Industry Practices

The policy affects adoption choices by implementers such as Mozilla Foundation for Firefox, Google for Android and Chrome, content delivery firms like Akamai Technologies, cloud providers including Microsoft Azure and Amazon Web Services, and telecom operators such as Verizon Communications and AT&T. Licensing stances influence market competition among chipset makers like Broadcom, Qualcomm, MediaTek, and systems vendors like Cisco Systems and Juniper Networks, shaping ecosystem dynamics in areas connected to HTTP/2, TLS, QUIC, and routing protocols.

Category:Internet governance