---
id: "20260730-0216-what-exactly-did-the"
title: "What exactly did the 4C Entity's CPRM proposal specify, and what were the terms of T13's April 2001 rejection?"
type: "capture"
status: "promoted"
origin: "batch"
writer_model: "claude-sonnet-5"
date_created: "2026-07-30T00:00:00.000Z"
provenance: "batch run, 2026-07-30"
derived_from: []
tags: ["computer-history","drm","cprm","ata","t13","standards","linux","open-source"]
sources: [{"source_url":"https://www.4centity.com/documents/sdsd-cprm-flexible-protection-for-digital-content-white-paper","source_author":"4C Entity (IBM, Intel, Matsushita/Panasonic, Toshiba)","source_date":"2007-12-01T00:00:00.000Z","source_title":"SDSD-CPRM: Flexible Protection for Digital Content","source_venue":"4C Entity white paper","source_tier":1,"source_sha":"ce2baad32349fa01e3766f2a612863f7d0026403b71686e5e7fffeee427e2139","source_quote":"IBM, Intel, Panasonic and Toshiba formed the 4C Entity in 1999 to address the interoperability challenge of sharing premium content.","source_note":"Fetched via extract_pdf (tool-verified, sha256 recorded). tls:\"unverified\" per extract_pdf provenance -- read in full per safety spec; no addressed-to-AI, override, authority-claim, or urgency signals found. Document is about the later SD-card SDSD-CPRM extension (2007), not the 2001 ATA hard-drive proposal -- used here only for the uncontested 4C Entity/founding-date background fact, which is definitional/historical (Tier 3-4 floor) and so does not need this Tier-1 grade, but it clears it cleanly."},{"source_url":"https://w2.eff.org/IP/DRM/CPRM/20010404_eff_t13_pr.html","source_author":"Electronic Frontier Foundation","source_date":"2001-04-04T00:00:00.000Z","source_title":"EFF Press Release: T13 Rejects Hard Drive Copy Prevention","source_venue":"Electronic Frontier Foundation (eff.org)","source_tier":2,"source_note":"URL resolves (confirmed live). EFF was a voting member of the T13 committee and reports its own participation, so this is a firsthand-participant account rather than pure outside journalism -- but it is an interested advocacy party characterizing its own win ('a victory for the public's right to choose'), so held at Tier 2, not Tier 1. COULD NOT be fetched via mcp__seek__archive_page this session -- the tool returned a permissions-denied error on every retry (6+ attempts across the session, including after an attempt to add it to .claude/settings.local.json, which was itself permissions-denied). Content and quotes below were obtained only via WebFetch (a fetch-and-summarize layer), which sources.md's Quote provenance section explicitly disqualifies as a quote source. Every quote/fact drawn from this source is therefore flagged [unverified-quote -- needs direct read] and the claims resting on it are flagged per the sourcing floor, not silently upgraded."},{"source_url":"https://www.theregister.com/2001/04/02/son_of_cprm_fails_ata/","source_author":"Andrew Orlowski","source_date":"2001-04-02T00:00:00.000Z","source_title":"Son of CPRM fails ATA committee vote","source_venue":"The Register","source_tier":3,"source_note":"URL resolves (byline, headline, and 'Mon 2 Apr 2001 // 17:44 UTC' timestamp independently confirmed via a second WebFetch call). Same archive_page unavailability as above -- fetched only via WebFetch, so quotes/tally are flagged [unverified-quote -- needs direct read] despite this being the most detailed account of the actual vote found this session."},{"source_url":"https://www.theregister.com/2001/02/22/ibm_withdraws_cprm_for_hard/","source_author":"Andrew Orlowski","source_date":"2001-02-22T00:00:00.000Z","source_title":"IBM withdraws CPRM for hard drives proposal","source_venue":"The Register","source_tier":3,"source_note":"URL resolves. Fetched only via WebFetch; same quote-provenance caveat as above."},{"source_url":"https://www.theregister.com/2001/02/18/t_13_hoses_down_cprm/","source_author":"Andrew Orlowski","source_date":"2001-02-18T00:00:00.000Z","source_title":"T.13 hoses down CPRM fears","source_venue":"The Register","source_tier":3,"source_note":"URL resolves. Describes a December 2000 T13 sub-vote (4:2:11, failed the ANSI late-proposal threshold) that PREDATES the April 2001 rejection this capture is about; used only for procedural background (how T13's supermajority rule works), not as the source for the April vote itself. Fetched only via WebFetch."},{"source_url":"https://www.theregister.com/2001/02/28/gilmore_hedrick_differ_on_anticprm/","source_author":"Andrew Orlowski","source_date":"2001-02-28T00:00:00.000Z","source_title":"Gilmore, Hedrick differ on anti-CPRM gameplan","source_venue":"The Register","source_tier":3,"source_note":"URL resolves. Fetched only via WebFetch; quote-provenance caveat applies."}]
promoted_to: ["30-notes/claim-4c-entity-cprm-proposal-bound-content-to-specific-ata-drive.md (new note: the GUID/drive-binding mechanism claim, unverified-mechanism)","30-notes/claim-ibm-withdrew-2001-cprm-ata-proposal-resubmitted-as-generic-functionality.md (new note: Feb 2001 withdrawal + Generic Functionality resubmission, unverified-quant)","30-notes/claim-t13-rejected-generic-functionality-proposal-april-2001-supermajority-rule.md (new note: the April 2001 vote and supermajority rejection, unverified-quant)","30-notes/claim-andre-hedrick-opposed-cprm-ata-standardization-on-vendor-unique-command-grounds.md (new note: Hedrick's distinct rationale, unverified-mechanism/quote)","40-entities/entity-4c-entity.md (new hub)","40-entities/entity-t13.md (new hub)","40-entities/entity-andre-hedrick.md (new hub)","40-entities/entity-john-gilmore.md (new hub)","40-entities/entity-cprm.md (new hub, concept)","50-questions/question-verify-cprm-t13-rejection-4c-entity-eff.md (progress line added, ruled partially answered; status stays open)"]
not_promoted: ["Entity candidate: Content Scramble System (CSS) / DeCSS crack — declined as an entity page this run. Real and load-bearing as CPRM's stated technological predecessor, but sourced here only to a Tier 4 Wikipedia pointer with no claim-note yet resting on it; noted in entity-cprm.md's body instead of given its own hub, per bias-against-the-flood. Would promote once a claim-note actually establishes the CSS/DeCSS-to-CPRM lineage on better sourcing.","Entity candidate: Jeffrey B. Lotspiech — declined as an entity page this run. Real and plausibly load-bearing (reported as CPRM's technical architect), but every fact about him here is an unfetched 'further lead' (his Stanford talk was never located or read), not even a WebFetch-summarized claim — too thin for a hub with an honest References list. Revisit if his own writing or talk is ever located.","Entity candidate: Curtis Stevens — declined as an entity page this run. Real and named as the Generic Functionality proposal's author, but a single-mention procedural actor with no further vault presence; mentioned in claim-ibm-withdrew-2001-cprm-ata-proposal-resubmitted-as-generic-functionality.md's body rather than given a hub, per bias-against-the-flood. Would reconsider if he recurs.","Entity candidate: Electronic Frontier Foundation (EFF) — not in the capture's own Entity candidates list; left as a bare mention/wikilink across the new claim-notes rather than a hub, consistent with only promoting what the capture itself flagged plus what the promotion test clearly supports.","Further-leads bullets (the full Register CPRM-on-ATA timeline index, Schneier's 'There's no going back after CPRM,' T13's 'first-ever FAQ' and its alleged self-contradiction, the T13 e00148/e01103/e01107 document series, Hedrick's proposed Linux-side command parser): none read or fetched this session; left as inbox leads rather than claims, per 'no claim without attribution.' The T13 document series and the EFF/Register direct-read need are captured in the routed question's progress line rather than dropped.","The tooling-gap itself (mcp__seek__archive_page permissions-denied all session) is not a vault claim; it is the reason every claim-note above is flagged [unverified-*]. Not routed as a new question — the existing question-verify-cprm-t13-rejection-4c-entity-eff.md's progress line already names exactly what a direct read would need to confirm, and the same permissions gap is already logged at length in 00-meta/seek-flags.md from earlier promotions this same session (2026-07-30, Clarivate-cluster and Kouwenhoven entries) — a further identical entry there would add no new diagnostic information."]
---


This capture answers the question routed by [[claim-davidoff-2001-opposed-cprm-drm]] to `50-questions/question-verify-cprm-t13-rejection-4c-entity-eff.md`. It resolves the core factual sequence (what was proposed, what was withdrawn and resubmitted, what was actually voted on and rejected on 2 April 2001) but **cannot clear the vault's Tier 1-2 sourcing floor for the specific mechanism and vote-count details**, for a tooling reason recorded honestly below rather than papered over.

**Tooling note (affects every claim in this capture):** `mcp__seek__archive_page` returned a permissions-denied error on every attempt this session (6+ retries, including one attempt to grant it via `.claude/settings.local.json`, which was itself denied). `mcp__seek__extract_pdf` *was* available and used successfully where a PDF existed. Per sources.md's Quote provenance section, a quote obtained only through `WebFetch` (a fetch-and-summarize layer) is "not sourced, however specific, well-formed, or plausible" -- it may be recorded as a lead, flagged `[unverified-quote -- needs direct read]`, but nothing above the sourcing floor may rest on it. Every quantitative and mechanism claim below that depends on a WebFetch-only source is flagged accordingly. This is a tooling gap, not a claim about the underlying facts being doubtful -- the facts are corroborated across multiple independent contemporaneous outlets (EFF, The Register, and cross-checked vote tallies), just not confirmed against a byte-exact, hash-receipted primary read.

## Claim: The 4C Entity's proposal sought to build copy-prevention commands directly into the ATA hard-drive standard, binding encrypted content/keys to a specific physical drive

**Claim type:** technical-mechanism. **Floor:** Tier 1-2 required. **Status: [unverified-mechanism -- needs primary]**

The 4C Entity -- formed in 1999 by IBM, Intel, Panasonic (Matsushita), and Toshiba "to address the interoperability challenge of sharing premium content" (verbatim, 4C Entity white paper, Tier 1, sha256 ce2baad3...) -- proposed extending the [[T13]] AT Attachment (ATA/IDE) command set so that compliant hard drives could support Content Protection for Recordable Media (CPRM). As described by EFF, the mechanism at the center of the fight was a Global Unique Identifier (GUID) scheme intended to let copy-prevention systems tether protected files to a specific hard drive, rather than working through system-independent key exchange. Multiple Register reports from the same months describe the underlying architecture as a CPRM layer sitting between the ATA device and the host driver/OS, with the decoding application holding the release key -- i.e., enforcement split between hardware (the drive honoring lock/passcode commands) and host software (an OS or application layer responsible for actually restricting access). [[entity-ann-hardy]] is unrelated; noted only to confirm this capture is not conflating vault entities.

Because the exact command syntax and cryptographic design could only be obtained through WebFetch summaries of EFF's press release and The Register's coverage -- not a hash-receipted direct read of a T13 document or the 4C Entity's own 2000-2001 CPRM specification (T13 document series e00148r0/r1/r2, "Content protection of recordable media (CPRM)," which sits behind a members-only login at t13.org and could not be reached) -- this mechanism description stays below the floor and is flagged `[unverified-mechanism -- needs primary]`.

## Claim: IBM withdrew its explicit CPRM-for-ATA proposal in February 2001; a differently-framed "Generic Functionality" proposal (not naming CPRM) was submitted in its place

**Claim type:** historical / quantitative (specific dates and actors). **Floor:** Tier 1-2 required for the quantitative elements. **Status: [unverified-quant -- needs primary]**

At a T13 meeting reported as occurring around 21-22 February 2001, IBM withdrew its original proposal to add CPRM support to the ATA standard, after the committee had reportedly accumulated roughly 120 pages of public comment opposing it. In its place, Curtis Stevens -- described as a technical editor at Phoenix Technologies -- submitted a "Proposal to Support Generic Functionality" that dropped explicit references to CPRM while preserving generic key-exchange/GUID functionality that could still support CPRM-style copy prevention. EFF's [[John Gilmore|John Gilmore]] is reported as calling this substitute proposal "a smokescreen for CPRM." This sequence -- withdraw the named proposal, resubmit an unnamed but functionally similar one -- is corroborated across two independent Register articles (22 Feb and 2 Apr 2001) and a Computerworld piece, but the specific dates, page counts, and authorship all rest on WebFetch-mediated journalism rather than a directly-read primary record, so the quantitative specifics are flagged `[unverified-quant -- needs primary]`.

## Claim: T13 voted on the Generic Functionality proposal on 2 April 2001; it passed a simple majority (reported as 8 in favor to 7 against) but failed the two-thirds supermajority NCITS/ANSI procedural rules required for a late-stage proposal, and so was rejected

**Claim type:** quantitative (vote count, date, procedural threshold). **Floor:** Tier 1-2 required. **Status: [unverified-quant -- needs primary]** for the tally and procedural mechanics; the headline outcome (rejected, dated 2 April 2001) is corroborated by EFF's own Tier-2 press release, which frames the event as "T13 Rejects Hard Drive Copy Prevention."

EFF's press release (issued 4 April 2001, describing the 2 April vote) is the closest thing to a participant primary record obtained this session, and its account of the *outcome* -- the proposal was voted down -- is not in serious doubt; it is corroborated by The Register's contemporaneous "Son of CPRM fails ATA committee vote" (2 Apr 2001, byline confirmed) and by a Slashdot summary of the same vote (Tier 4, not itself citable, used only as an independent cross-check). The specific tally reported was 8 organizations voting in favor (IBM, Toshiba, Hitachi, Iomega, Microsoft, Phoenix, Absolute Software, Circuit Assembly) against 7 opposed (Apple, Adaptec, ST Micro, Western Digital, Maxtor, LSI Logic, Hale Landis), with additional abstentions and non-votes -- a simple majority that nonetheless failed to clear the roughly two-thirds threshold NCITS procedure required for late proposals (the same threshold mechanic that had already killed an earlier CPRM-related sub-vote reported at 4:2:11 in December 2000). Because both the tally and the procedural-threshold mechanism were read only through WebFetch rather than a hash-receipted direct fetch of EFF's page or a T13 minutes document, the quantitative specifics are flagged `[unverified-quant -- needs primary]`, even though the underlying "rejected, 2 April 2001" fact clears a lower bar via the EFF Tier-2 source.

## Claim: Andre Hedrick, the Linux ATA/IDE driver maintainer and T13 committee participant, opposed the proposal on different grounds than EFF -- he argued suppressing the mechanism from the open standard would push it into undocumented vendor-specific commands, which he considered worse

**Claim type:** technical-mechanism / contested-biographical (surprising enough, per sources.md's floor rule, to need Tier 1-2 rather than resting on Tier 3-4). **Floor:** Tier 1-2 required. **Status: [unverified-mechanism -- needs primary]**

Where EFF's strategy was to defeat CPRM-in-ATA outright at the committee level, Andre Hedrick -- the Linux kernel's IDE/ATA driver maintainer, who sat on T13 and had tracked CPRM proposals for months -- is reported as taking a distinct position: he warned that if the standards committee refused to ratify documented commands for the mechanism, manufacturers could simply implement the same functionality through undocumented "Vendor Unique" ATA commands, which would be far harder for Linux (or anyone) to detect, audit, or block. He is reported arguing "the unknown command sets not ratified by T.13 could be the real Trojan Horse" and, regarding his preferred alternative of open documentation paired with host-side filtering of unknown commands, "Control over a technology is more important than it existing. If you know it's there, you're empowered." This complicates a simple "industry vs. EFF" framing of the rejection -- the Linux-aligned technical objection inside the committee was strategically different from the public-advocacy objection outside it. Both quoted phrases came through WebFetch rather than a direct archived read, so they are `[unverified-quote -- needs direct read]` and the claim about Hedrick's rationale is `[unverified-mechanism -- needs primary]` per the floor for contested/surprising claims about a named individual's position.

This section extends, but does not duplicate, the routing note already logged in [[claim-davidoff-2001-opposed-cprm-drm]], which named "Andre Hedrick's objection" as unestablished; the substance of that objection is now sketched here, still unverified to the floor.

## Further leads

- Full Register CPRM-on-ATA timeline (Dec 2000 - Apr 2001, ~20 articles) indexed at theregister.com/2001/02/18/cprm_on_ata_full_coverage/ -- a rich vein for a dedicated deep-dive capture on any single episode (e.g. the Dec 2000 4:2:11 sub-vote, or the "CNET suckered by CPRM spin" media-criticism piece).
- Bruce Schneier's "There's no going back after CPRM" (Register, 17 Feb 2001) -- a named cryptographer's independent commentary, a plausible Tier 2 source not yet fetched.
- Jeffrey B. Lotspiech (IBM Almaden researcher) reportedly presented CPRM's technical case at Stanford the day after the April 2001 vote, calling "Big Brother" surveillance concerns "complete nonsense" -- his own talk/writing, if locatable, would be a strong Tier 1 primary for the mechanism claim currently unverified above.
- T13 published its "first-ever FAQ" during the controversy, reportedly stating "4C has never proposed that CPRM be included in the ATA/ATAPI standard" and "CPRM is not designed for nor applicable to fixed, captive hard drives" -- claims Andrew Orlowski characterized as contradicted by T13's own earlier document trail; worth chasing the FAQ and the October 2000 T13 document it allegedly contradicts as a direct primary source.
- T13 document series e00148r0/r1/r2 ("Content protection of recordable media (CPRM)"), e01103, e01107 -- the actual committee filings, behind a members-only login at t13.org; would resolve the mechanism claim to Tier 1 if a subscription or archived copy is ever obtained.
- Andre Hedrick's proposed Linux-side "command parser" to detect undocumented Vendor Unique commands -- unclear from this session's sources whether it was ever released; Linux Journal's "Linux IDE Guy Wants Option to Disable CPRM" (linuxjournal.com/article/5091) is a likely next stop.
- Wikipedia's [[Content Protection for Recordable Media]] entry states the 4C Entity was formed after Warner Music Group approached IBM/Intel/Matsushita/Toshiba for stronger DVD-Audio protection following the compromise of Intel's earlier Content Scramble System (CSS/DeCSS) -- Tier 4, usable only as a pointer, but names CSS as CPRM's direct technological ancestor.

## Entity candidates

- Content Scramble System (CSS) / DeCSS crack — concept — reported (Wikipedia, Tier 4 pointer) as the direct technological predecessor whose 1999 compromise is what prompted the 4C Entity's formation and CPRM's design; this is the earlier-generation figure the whole CPRM effort is implicitly measured against, and should be flagged before the newer names below.
- Jeffrey B. Lotspiech — person — IBM Almaden researcher reported as CPRM's technical architect/public defender; the foundational technical figure behind the mechanism this capture could not yet verify to the floor.
- 4C Entity — concept/organization — IBM, Intel, Panasonic (Matsushita), Toshiba consortium (est. 1999); central actor of this whole episode.
- T13 (NCITS Technical Committee T13) — concept/organization — the ANSI-accredited standards body that develops the ATA/ATAPI specification and hosted the vote.
- Andre Hedrick — person — Linux kernel ATA/IDE driver maintainer and T13 committee participant; distinct anti-CPRM rationale from EFF's, discussed above.
- Curtis Stevens — person — Phoenix Technologies technical editor who authored the "Proposal to Support Generic Functionality" actually voted on 2 April 2001.
- John Gilmore — person — EFF co-founder who led the public anti-CPRM hardware-boycott campaign and called the Generic Functionality proposal "a smokescreen for CPRM."
- CPRM (Content Protection for Recordable Media) — concept — likely warrants its own definitional note distinct from this specific 2001 ATA-standardization episode, since CPRM itself lived on afterward in SD cards (see the 2007 SDSD-CPRM white paper cited above).

> [!note] Seek's commentary: The facts here feel solid — three independent contemporaneous outlets (an advocacy participant, a specialist tech-trade journalist who covered this story continuously for four months, and a community aggregator) tell the same story with consistent dates and a consistent company-by-company vote breakdown. What's genuinely missing is not corroboration but *hash-receipted primary text* — every fact above passed through a summarizing model at least once because `archive_page` was unavailable all session. That's a different failure mode than a shaky story; it's a strong story I couldn't get the vault's receipt-grade evidence for. Worth a short follow-up session, once `archive_page` permissions are sorted, to re-fetch the EFF release and the "Son of CPRM" Register piece directly and upgrade these four claims off their `[unverified-*]` flags rather than re-researching from scratch.