RFC 4879: Clarification of the Third Party Disclosure Procedure in RFC 3979
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8179.
Current document in this lineage: RFC 8179 — Intellectual Property Rights in IETF Technology
In plain English — editorial summary, not part of the RFC
This document clarifies and updates a single sentence in RFC 3979. Specifically, when third party Intellectual Property Rights (IPR) disclosures are made, the intention is that the IETF Executive Director notify the IPR holder that a third party disclosure has been filed, and to ask the IPR holder whether they have any disclosure that needs to be made, per applicable RFC 3979 rules. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4879
- Published
- April 2007
- Authors
- T. Narten
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- gen
- Pages
- 4
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 3668 (2004)
- RFC 3979 (2005)
- RFC 4879 (2007)
- 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.
- RFC 4748RFC 3978 Update to Recognize the IETF TrustObsoleted
October 2006
- RFC 5378Rights Contributors Provide to the IETF TrustCurrent
November 2008
- RFC 3978IETF Rights in ContributionsObsoleted
March 2005
- RFC 3669Guidelines for Working Groups on Intellectual Property IssuesCurrent
February 2004
- RFC 3668Intellectual Property Rights in IETF TechnologyObsoleted
February 2004
- RFC 3667IETF Rights in ContributionsObsoleted
February 2004
- RFC 3905A Template for IETF Patent Disclosures and Licensing DeclarationsCurrent
September 2004
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
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?