Skip to content

Fix normative notes and clarify/simplify robustness rules #549

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix normative notes and clarify/simplify robustness rules #549

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 8 additions & 9 deletions encrypted-media-respec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2544,20 +2544,19 @@ <h2>
<p>
The robustness level associated with the content type. The empty string indicates
that any ability to decrypt and decode the content type is acceptable.
Implementations MUST configure the [=CDM=] to support at least the robustness
levels specified in the configuration of the {{MediaKeySystemAccess}} object used
to create the {{MediaKeys}} object.
Comment on lines +2548 to +2549
Copy link
Member

@marcoscaceres marcoscaceres Jul 24, 2024

Choose a reason for hiding this comment

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

Suggested change
levels specified in the configuration of the {{MediaKeySystemAccess}} object used
to create the {{MediaKeys}} object.
levels specified in the configuration of the {{MediaKeySystemAccess}} dictionary used
to create the {{MediaKeys}} instance.

Copy link
Member

@chrisn chrisn Oct 27, 2025

Choose a reason for hiding this comment

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

I think "MediaKeySystemAccess object" is right here - it's an interface, whereas MediaKeySystemConfiguration is a dictionary.

</p>
<div class="note">
<p>
Implementations MUST configure the [=CDM=] to support at least the robustness
levels specified in the configuration of the {{MediaKeySystemAccess}} object used
to create the {{MediaKeys}} object. Exact configuration of the [=CDM=] is
implementation-specific, and implementations MAY configure the [=CDM=] to use the
highest robustness level in the configuration even if a higher robustness level
is available. If only the empty string is specified, implementations MAY be
configured to use the lowest robustness level the implementation supports.
Exact configuration of the [=CDM=] is implementation-specific.
Copy link
Member

@chrisn chrisn Aug 21, 2025

Choose a reason for hiding this comment

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

We may want to remove the note entirely, and keep the "implementations MAY configure" language.

If only the empty string is specified, implementations have the option to
use the lowest robustness level the implementation supports.
</p>
<p>
Applications SHOULD specify the robustness level(s) they require to avoid
unexpected client incompatibilities.
Applications are recommended to specify the robustness level(s) they require,
if any, to avoid unexpected client incompatibilities.
Comment on lines +2558 to +2559
Copy link
Member

@marcoscaceres marcoscaceres Jul 24, 2024

Choose a reason for hiding this comment

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

Suggested change
Applications are recommended to specify the robustness level(s) they require,
if any, to avoid unexpected client incompatibilities.
To avoid unexpected interoperability issues, developers are encouraged to provide the robustness level(s)
(if any).

</p>
</div>
</dd>
Expand Down