Skip to content

Expand and restructure Privacy Considerations section - #985

Open
Djuffin wants to merge 1 commit into
w3c:mainfrom
Djuffin:privacy
Open

Djuffin wants to merge 1 commit into
w3c:mainfrom
Djuffin:privacy

Conversation

@Djuffin

@Djuffin Djuffin commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor
  • Add an informative note to Check Configuration Support clarifying that User Agents can limit provided configurations to a common baseline subset (including Codec Registry extensions) to reduce fingerprinting entropy across both isConfigSupported() and configure().
  • Restructure Privacy Considerations into topical non-normative subsections: Codec Capability Fingerprinting, Codec Output Fingerprinting, and Timing and Resource Side-Channels.
  • Cite Section 7.9 (Hardware Acceleration) anti-fingerprinting rules.
  • Replace the obsolete "privacy budget" reference and stray RFC 2119 markup with concrete mitigations (common capability baselines, ignoring HardwareAcceleration hints, silent software fallback on hardware exhaustion, probe throttling, bundled software codecs in heightened privacy modes, timing coarsening, pacing/throttling, and normalized buffer pool limits).
  • Clarify differences between bundled software codecs and OS/hardware codecs, distinguish encoding vs. decoding bit-exactness, and note capturing-context restrictions on hardware stats in WebRTC-Stats.

Addresses #231, #233, #234, #238, #429


Preview | Diff

- Add an informative note to Check Configuration Support clarifying that
  User Agents can limit provided configurations to a common baseline
  subset (including Codec Registry extensions) to reduce fingerprinting
  entropy across both isConfigSupported() and configure().
- Restructure Privacy Considerations into topical non-normative
  subsections: Codec Capability Fingerprinting, Codec Output
  Fingerprinting, and Timing and Resource Side-Channels.
- Cite Section 7.9 (Hardware Acceleration) anti-fingerprinting rules.
- Replace the obsolete "privacy budget" reference and stray RFC 2119
  markup with concrete mitigations (common capability baselines, ignoring
  HardwareAcceleration hints, silent software fallback on hardware
  exhaustion, probe throttling, bundled software codecs in heightened
  privacy modes, timing coarsening, pacing/throttling, and normalized
  buffer pool limits).
- Clarify differences between bundled software codecs and OS/hardware
  codecs, distinguish encoding vs. decoding bit-exactness, and note
  capturing-context restrictions on hardware stats in WebRTC-Stats.

Addresses w3c#231, w3c#233, w3c#234, w3c#238, w3c#429

@padenot padenot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty comprehensive, not much to add, thanks.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants