ObsoletedBEST CURRENT PRACTICEIETF stream

RFC 3668: Intellectual Property Rights in IETF Technology

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3979.

Current document in this lineage: RFC 8179Intellectual Property Rights in IETF Technology

In plain English — editorial summary, not part of the RFC

The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information about any IPR constraints on a technical proposal as possible. The policies are also intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders. This memo details the IETF policies concerning IPR related to technology worked on within the IETF. It also describes the objectives that the policies are designed to meet. This memo updates RFC 2026 and, with RFC 3667, replaces Section 10 of RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC 2028, for all purposes, including reference [2] in RFC 2418. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC3668
Published
February 2004
Authors
S. Bradner
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
gen
Pages
17
Also known as
Obsoleted by:
RFC 3979

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 3668 (2004)
  2. RFC 3979 (2005)
  3. RFC 4879 (2007)
  4. RFC 8179 (2017)

Read the full history of Intellectual Property Rights in IETF Technology

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3668-intellectual-property-rights-in-ietf-technology