Skip to content

Fix normative language issues #690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 6, 2023
Merged

Fix normative language issues #690

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a3db9af
Remaining normative language issues
aboba Jun 22, 2023
0f12a6c
Merge pull request #1 from aboba/aboba-patch-1
aboba Jun 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions index.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5575,6 +5575,9 @@
Security Considerations{#security-considerations}
=================================================

<div class=non-normative>
This section is non-normative.

The primary security impact is that features of this API make it easier for an
attacker to exploit vulnerabilities in the underlying platform codecs.
Additionally, new abilities to configure and control the codecs can allow for
Expand Down Expand Up @@ -5603,14 +5606,16 @@
exploits being able to read user data.

An additional concern is exposing the underlying codecs to input mutation race
conditions. Specifically, it <em class="rfc2119">SHOULD</em> not be possible for
a site to mutate a codec input or output while the underlying codec is still
operating on that data. This concern is mitigated by ensuring that input and
output interfaces are immutable.
conditions, such as allowing a site to mutate a codec input or output while
the underlying codec is still operating on that data. This concern is mitigated
by ensuring that input and output interfaces are immutable.

Privacy Considerations{#privacy-considerations}
===============================================

<div class=non-normative>
This section is non-normative.

The primary privacy impact is an increased ability to fingerprint users by
querying for different codec capabilities to establish a codec feature profile.
Much of this profile is already exposed by existing APIs. Such profiles are very
Expand Down