Data compression patents often sit directly on top of technical standards. Compression formats, transport protocols, image codecs, media containers and interoperability specifications may be developed and publicly documented years before a patent owner asserts a corresponding patent.
That makes IETF RFCs and ISO/IEC standards potentially important prior-art sources in patent validity analysis.
But the mere fact that a standard describes similar technology does not automatically invalidate a patent. For an anticipation theory, the critical questions are whether the standard was publicly available before the relevant date and whether a single qualifying reference discloses every limitation of the challenged claim, arranged as claimed.
Under U.S. law, the USPTO explains that anticipation requires every claim element to be found, expressly or inherently, in a single prior-art reference. The public-accessibility issue is equally important: an electronic document can qualify as a printed publication when it was sufficiently accessible to interested members of the public.
For European practice, the EPO similarly defines the state of the art broadly as information made available to the public before the relevant filing date, regardless of geography or language.
For compression patents, therefore, standards research should be treated as a structured invalidity exercise – not simply a search for documents containing the same technical vocabulary.
Why Standards Matter in Compression Patent Litigation
Compression technology is unusually standards-driven.
A patented technique may appear in:
- an Internet protocol;
- a codec specification;
- an image or video compression standard;
- a file-format specification;
- a transport protocol;
- an interoperability requirement;
- an implementation guideline; or
- a technical standard adopted by an industry consortium.
An IETF RFC, for example, may describe a protocol or technical method and become part of the permanent RFC publication record. The RFC Editor explains that published RFCs are official publications whose contents do not change after publication, although later RFCs may update or obsolete them.
ISO and ISO/IEC standards likewise have identifiable publication records. ISO’s standards database provides publication dates and lifecycle information for individual standards, while ISO maintains metadata concerning published and developing deliverables.
These characteristics can make standards particularly useful when reconstructing what technical information was publicly available before a patent’s critical date.
The Basic Anticipation Test
The starting point for a U.S. anticipation analysis is straightforward:
Can one qualifying prior-art reference disclose every limitation of the claim?
The USPTO states that a claim is anticipated only when each and every element is found, expressly or inherently, in a single reference. The elements must also be arranged as required by the claim, although the reference does not have to use identical terminology.
Consider a hypothetical compression claim requiring:
- receiving an input data stream;
- identifying repeated data patterns;
- generating a dictionary;
- encoding repeated patterns using dictionary references;
- transmitting the encoded stream; and
- reconstructing the original data using the dictionary.
If an earlier IETF RFC discloses all six elements in the required arrangement, that RFC could potentially anticipate the claim.
But suppose the RFC discloses elements 1–4 while an earlier ISO standard discloses elements 5–6.
That may create a strong obviousness/inventive-step theory, but it does not ordinarily establish anticipation of the entire claim because anticipation generally requires a single reference.
This distinction is fundamental.
A Standard Does Not Need to Be Called a “Patent Reference”
Patent practitioners sometimes overlook standards because they are not conventional patent documents.
That is a mistake.
For U.S. purposes, the relevant question is whether the document qualifies as prior art under the applicable statutory framework and whether it discloses the claimed subject matter. A document’s status as an RFC, ISO standard, technical paper, or other industry publication does not by itself prevent it from serving as prior art.
The USPTO specifically recognizes electronic publications as potential printed publications when they were sufficiently accessible to persons concerned with the relevant art.
Thus, the search should not be limited to:
patents + patent applications + scientific journals.
For compression technologies, it should also include:
standards + RFCs + drafts + implementation specifications + archived technical documentation.
Public Availability Is Often the First Battleground
Finding a standards document is only the beginning.
The invalidity analysis must establish when the relevant disclosure became publicly available.
For an IETF document, distinguish among:
- an Internet-Draft;
- a working-group version;
- a Last Call version;
- an approved RFC;
- a revised RFC; and
- an RFC that later became obsolete.
The RFC Editor explains that RFCs begin as Internet-Drafts and that, after approval and publication, the official RFC is published on rfc-editor.org.
That means the relevant question may not simply be:
“When was RFC 1234 published?”
Instead, counsel should ask:
When was the particular disclosure relied upon publicly accessible?
An earlier Internet-Draft may matter if it was publicly available before the critical date and contains the necessary disclosure. But the evidence establishing its public accessibility should be preserved.
Internet-Drafts Can Be Especially Important
IETF standards development is iterative.
A final RFC may have been published after the patent’s critical date even though substantially identical technical material appeared in earlier Internet-Drafts.
That creates a potentially important prior-art trail.
The investigation should therefore compare:
Internet-Draft version → later draft → approved RFC
rather than searching only for the final RFC.
But there is a critical evidentiary distinction:
Later publication does not automatically prove earlier public availability of identical technical content.
The attorney should identify the earliest version containing the relied-upon disclosure and establish its public availability independently.
RFC Status Is Not the Same as Publication
Another common mistake is treating “Internet Standard” status as the decisive factor.
It is not.
The RFC Editor explains that the RFC series is a publication mechanism and that publication does not itself determine whether a document is an Internet Standard. RFCs can have different statuses, including Proposed Standard, Internet Standard, Informational, Experimental, Best Current Practice and Historic.
For patent prior-art purposes, the key inquiry is generally not:
Was this an official Internet Standard?
It is:
Was the relevant disclosure publicly available before the applicable critical date?
An Informational RFC can therefore be worth investigating even if it never became a standards-track document.
ISO Standards Require Similar Date Analysis
ISO standards should receive the same treatment.
An ISO document may have a detailed lifecycle involving:
- proposal;
- committee draft;
- enquiry;
- draft international standard;
- approval;
- publication;
- confirmation;
- revision; and
- withdrawal.
The final publication date is easy to identify from an ISO catalog entry. ISO’s records, for example, provide publication dates and lifecycle information for individual standards.
But an invalidity investigation should also consider whether earlier draft or committee materials were publicly available.
The key is to separate:
date of technical development
from
date of public accessibility.
A technology can have existed internally for years without becoming prior art through public disclosure.
The Claim Chart Is the Core Tool
For standards-based anticipation analysis, a detailed claim chart is indispensable.
A useful chart should identify:
| Claim limitation | IETF/ISO disclosure | Exact location | Express/inherent | Public-availability evidence |
| Receive compressed stream | RFC section X | § 3.1 | Express | Publication record |
| Identify repeated patterns | RFC section Y | § 4.2 | Express | Publication record |
| Generate dictionary | RFC section Z | § 4.3 | Express | Publication record |
| Encode references | RFC section Z | § 4.4 | Express | Publication record |
| Reconstruct data | RFC section A | § 5 | Express | Publication record |
This structure separates two questions that are often improperly combined:
- Does the document disclose the limitation?
- Was that disclosure publicly available in time?
Both must be established.
Technical Vocabulary Is Not Enough
Compression patents frequently use highly specialized terminology.
A standard may use a different term for the same technical concept.
For example, a patent may claim:
“constructing a codebook based on previously encountered symbols”
while an RFC might describe:
“building a dictionary from previously observed tokens.”
The lack of identical terminology does not necessarily defeat anticipation.
The USPTO expressly states that anticipation does not require an identity of terminology; the elements must be present and arranged as claimed.
The claim chart should therefore map technical concepts, not merely matching words.
Express Disclosure Versus Inherent Disclosure
A standards document may anticipate a claim either through express disclosure or, in appropriate circumstances, inherent disclosure.
For example, an RFC may explicitly describe a decompression procedure but omit a statement that the reconstructed output is identical to the original input.
If that result necessarily follows from the disclosed process, inherency may become relevant.
But inherency should not be confused with possibility.
The question is not:
“Could an implementation perform this step?”
It is closer to:
“Does the disclosed technology necessarily possess the claimed characteristic?”
A feature that is merely optional or one possible implementation generally presents a much weaker anticipation theory.
Standards Often Contain Alternatives
This is particularly important for compression specifications.
A standard may define:
- multiple encoding modes;
- optional headers;
- alternative dictionaries;
- several block types;
- optional prediction mechanisms;
- different entropy coders; or
- implementation-dependent features.
A claim may be anticipated if one disclosed embodiment within the scope of the reference contains every limitation.
But the attorney should identify the exact embodiment rather than treating the entire standard as one undifferentiated disclosure.
The USPTO recognizes that a claim covering alternatives can be anticipated when an applicable alternative is disclosed in the prior art.
Mandatory Versus Optional Features
For standards-based invalidity analysis, the words used by the standard can be crucial.
Look carefully for:
- MUST;
- SHALL;
- SHOULD;
- MAY;
- OPTIONAL;
- RECOMMENDED;
- REQUIRED; and
- IMPLEMENTATION-DEPENDENT.
An optional feature can still be relevant, but the legal analysis may differ depending on the claim and the nature of the disclosure.
For example, if a claim requires a particular compression operation and an RFC merely states that an implementation may use that operation, counsel should not automatically treat the feature as necessarily present in every implementation.
The claim chart should identify the normative status of each relied-upon feature.
One Standard Versus Multiple Standards
This is where standards research often becomes especially powerful – and legally nuanced.
Suppose:
- an IETF RFC discloses the compression algorithm;
- an ISO standard discloses the file format; and
- a separate technical specification discloses the transmission mechanism.
Together, they may provide a compelling story about the technology’s development.
But if no single reference contains every limitation of the challenged claim, the combination is generally not an anticipation case under the conventional single-reference rule.
Instead, the references may support an obviousness or inventive-step analysis.
The distinction should be preserved in litigation work product:
Anticipation: one reference, all limitations.
Obviousness/inventive step: potentially multiple references, subject to the applicable legal standard.
The Critical Date Controls the Search
Before analyzing any standard, establish the patent’s relevant date.
Depending on the jurisdiction and statutory framework, this may involve:
- filing date;
- earliest valid priority date;
- effective filing date;
- publication date;
- or another statutory date.
The attorney should not simply assume that the earliest claimed priority date controls every aspect of the analysis.
Priority must itself be valid for the particular subject matter being relied upon.
For international practice, the EPO’s guidance likewise emphasizes the relevant filing or priority date when determining what constitutes prior art.
Preserve Evidence of the Standard’s Historical Version
A current standards webpage is not necessarily sufficient evidence of what the standard disclosed ten or twenty years ago.
Standards evolve.
A current RFC may update or obsolete an earlier RFC. The RFC Editor specifically notes that RFCs may be updated or obsoleted while the published RFC itself remains unchanged.
Similarly, ISO standards can be revised, confirmed, or withdrawn.
For an invalidity investigation, preserve:
- the exact document version;
- publication date;
- version number;
- revision history;
- archive location;
- bibliographic metadata;
- relevant sections;
- referenced documents; and
- evidence establishing public availability.
This is much stronger than citing a current webpage that happens to contain similar technology.
Standards References Can Help Establish Technical Meaning
Even when a standard does not anticipate a claim by itself, it can still be valuable.
For example, an RFC might explain how a technical term was understood by skilled practitioners at the relevant time.
An ISO standard may demonstrate that a particular compression technique was conventional or widely implemented.
Such material may therefore be relevant to:
- claim construction;
- obviousness;
- motivation to combine;
- reasonable expectations;
- technical background;
- enablement;
- indefiniteness; or
- the understanding of a person skilled in the art.
But those uses should not be confused with anticipation.
Beware of Post-Critical-Date Standards
A common invalidity mistake is finding a perfect standards disclosure published after the patent’s critical date and treating it as anticipatory prior art.
That does not work merely because the later document describes exactly what the patent claims.
A later standard can be useful for other purposes – for example, demonstrating how an earlier technology operated if there is independent evidence that the relevant feature existed earlier – but the attorney must establish a legally appropriate basis for using it.
The date of the document and the date of the underlying disclosure should therefore always be recorded separately.
Search the References Cited by the Standard
Standards often contain extensive references to earlier technical materials.
This can turn a single promising RFC into a much larger prior-art trail.
For each important standard, examine:
- normative references;
- informative references;
- predecessor standards;
- earlier RFCs;
- cited academic papers;
- implementation specifications;
- earlier versions;
- working-group drafts; and
- referenced patents.
This is particularly effective in compression technology because standards frequently build incrementally on earlier algorithms and formats.
The goal is to identify the earliest public disclosure of the claimed combination, not merely the first document found in a modern standards archive.
A Practical Standards-Based Invalidity Workflow
A disciplined workflow can be organized into eight steps.
1. Identify the Critical Date
Determine the relevant date for the challenged claim.
2. Break the Claim Into Limitations
Do not search the claim as one paragraph. Separate structural, functional, data-format and algorithmic limitations.
3. Identify Standards Families
Search relevant:
- IETF working groups;
- RFCs;
- Internet-Drafts;
- ISO/IEC committees;
- predecessor standards;
- codec specifications; and
- industry implementation documents.
4. Find the Earliest Candidate Disclosure
For each candidate, determine the earliest version containing the relevant technical feature.
5. Establish Public Accessibility
Collect evidence showing when that version became available to the public.
For electronic publications, public accessibility is the central inquiry under U.S. printed-publication doctrine.
6. Build a Single-Reference Claim Chart
Test whether one qualifying reference discloses every limitation.
7. Separate Anticipation From Combination Theories
If multiple standards are necessary, move the analysis into the appropriate obviousness/inventive-step framework rather than calling the combination anticipation.
8. Preserve the Evidence
Archive the exact standards documents, metadata, publication records, historical versions and relevant technical passages.
A Useful Red-Flag Checklist
When evaluating an IETF or ISO document against a compression patent, ask:
- Was the document publicly available before the critical date?
- Is this the correct historical version?
- Does the document disclose every claim limitation?
- Are the limitations disclosed in the required combination?
- Is any missing limitation necessarily present?
- Is a relied-upon feature mandatory or optional?
- Does the document define the technical term differently?
- Are there incorporated or referenced documents that are being improperly used to fill a gap?
- Are multiple references being combined for an anticipation theory?
- Is the document being used for anticipation or merely as evidence of technical knowledge?
- Can the public-accessibility date be independently proven?
- Has the exact historical copy been preserved?
The Special Value of Standards in Compression Cases
Standards can be particularly persuasive because they often represent a detailed technical description of how systems actually operate.
A compression patent may use broad patent terminology, while the corresponding standard may specify:
- bitstream syntax;
- coding tables;
- dictionary construction;
- transform operations;
- prediction modes;
- entropy coding;
- block structures;
- decoding steps; and
- interoperability requirements.
That level of technical detail can make standards unusually useful for limitation-by-limitation analysis.
But the same specificity creates a trap: a standard may disclose nearly everything in a claim without disclosing one critical limitation.
That single missing limitation can defeat an anticipation theory.
Final Takeaway
IETF RFCs and ISO/IEC standards can be powerful sources of prior art in data-compression patent invalidity work. Their value comes not merely from technical similarity, but from the combination of detailed technical disclosure, identifiable publication histories and evidence of public accessibility.
For anticipation, however, the standard remains demanding: under U.S. practice, a single qualifying reference generally must disclose every claim element, expressly or inherently, in the arrangement required by the claim.
The most effective analysis therefore follows a disciplined sequence:
identify the critical date → locate the earliest public standards disclosure → verify public accessibility → map every claim limitation → test the single-reference requirement → preserve the historical evidence.
In compression patent disputes, the winning prior-art document may not be another patent at all. It may be an old RFC, an earlier version of an ISO/IEC standard, an Internet-Draft, or a standards document that quietly described the claimed compression technique years before the patent was filed.
The key is to prove not simply that the technology was known, but that the claimed invention was disclosed in a qualifying prior-art reference before the relevant date.