diff --git a/encrypted-media-respec.html b/encrypted-media-respec.html index 6af9b2d..6295c4f 100644 --- a/encrypted-media-respec.html +++ b/encrypted-media-respec.html @@ -63,7 +63,7 @@ }, }, - xref: ["dom", "html", "infra", "webaudio"] + xref: ["dom", "html", "infra", "mimesniff", "webaudio"] }; @@ -1021,22 +1021,6 @@
- A valid media MIME type is a media MIME type that is - also a [=valid MIME type string=] [[mimesniff]]. When a MIME type includes parameters, - such as `"codecs"` [[RFC6381]], such parameters MUST also be valid per the relevant - specification. -
-- When used with the features defined in this specification, MIME type strings SHOULD - explicitly specify codecs and codec constraints (e.g., per [[RFC6381]]) unless these - are normatively implied by the container. -
-- If content type is not a [=valid media MIME type=] or is - unrecognized, continue to the next iteration. + Let mimeType be the result of running parse a MIME type + with content type.
- Let container be the container type specified by content
- type.
+ If mimeType is failure
or is unrecognized,
+ continue to the next iteration.
+
+ Let container be the container type specified by + mimeType.
- Let parameters be the RFC 6381 [[RFC6381]] parameters, if any, - specified by content type. + Let parameters be the "codecs" and "profiles" RFC 6381 [[RFC6381]] + parameters, if any, of mimeType.
If the user agent does not recognize one or more parameters, + or if any parameters are not valid per the relevant specification, continue to the next iteration.
- If content type is not strictly a audio/video type, + If mimeType is not strictly an audio/video type, continue to the next iteration.
- For example, if audio/video type is Video and the top-level type + For example, if audio/video type is Video and mimeType's + [=MIME type/type=] is not "video" or media types contains non-video codecs.
- The type of the media resource. Its value - must be a [=valid media MIME type=]. The empty string is invalid. + The MIME type of the + media resource. +
++ Applications SHOULD ensure that the MIME type explicitly specifies codecs + and codec constraints (e.g., per [[RFC6381]]) unless these are normatively + implied by the container.