AWS mediapackage documentation change
Summary
Restructured DASH manifest creation steps, added DVB-DASH compliance requirements, expanded configuration options for manifest compactness, UTC timing, subtitle profiles, program information, base URLs, and DVB-DASH-specific settings including font downloads and error reporting.
Security assessment
The changes focus on feature enhancements, compliance requirements (DVB-DASH), and manifest configuration options. While they include error reporting URLs and synchronization settings, there is no explicit mention of addressing vulnerabilities, patching weaknesses, or mitigating security incidents. The UTC timing and DVB-DASH requirements relate to playback compliance rather than security controls.
Diff
diff --git a/mediapackage/latest/userguide/endpoints-create.md b/mediapackage/latest/userguide/endpoints-create.md index a040bb3c3..52f0e2d19 100644 --- a//mediapackage/latest/userguide/endpoints-create.md +++ b//mediapackage/latest/userguide/endpoints-create.md @@ -212,11 +211,0 @@ Choose the type of manifest to use. You can choose an HLS manifest, LL-HLS manif -###### Topics - - * Create an HLS or LL-HLS manifest - - * Create a DASH manifest - - - - -### Create an HLS or LL-HLS manifest - @@ -300 +289,12 @@ If you're using this setting to limit content playback for contractual reasons, -### Create a DASH manifest +Use the following steps to configure the endpoint to create manifests that are compliant with DASH. + +###### DVB-DASH requirements + +If the outputs from this endpoint will be compliant with DVB-DASH, you must adhere to the following requirements: + + * The channel must use CMAF input + + * The endpoint must not use **UTC Direct** for UTC timing mode + + + @@ -318 +318,9 @@ If you're using this setting to limit content playback for contractual reasons, - 7. For **UTC timing** , select the method that the player uses to synchronize to coordinated universal time (UTC) wall clock time. This enables the player and MediaPackage to run on the same UTC wall clock time. This is a requirement, otherwise playback timing or synchronization issues can occur. Choose from the following options: + 7. For **Manifest compactness** , indicate if you want MediaPackage to serve a standard (compacted) or full manifest (no compacting) in response to playback requests. + + * If you choose **None** , MediaPackage presents the `SegmentTemplate` and `SegmentTimeline` tags for every `Representation` in the manifest. + + * **Standard** is the default selection. It indicates that MediaPackage combines duplicate `SegmentTemplate` tags and presents them at the start of the manifest. This shortens the manifest and makes it easier for some devices to process it. + +For more information about the manifest layout options, see [DASH manifest compactness](./compacted.html). + + 8. For **Profiles** , optionally choose if the output is compliant with DVB-DASH. Review the DVB-DASH requirements to ensure the endpoint is compliant with this profile: @@ -320 +328 @@ If you're using this setting to limit content playback for contractual reasons, - * UTC Direct + * The channel must use CMAF input @@ -322 +330 @@ If you're using this setting to limit content playback for contractual reasons, - * HTTP Head + * The endpoint must not use **UTC Direct** for UTC timing mode @@ -324 +332 @@ If you're using this setting to limit content playback for contractual reasons, - * HTTP Iso + 9. For **UTC timing** , select the method that the player uses to synchronize to coordinated universal time (UTC) wall clock time. This enables the player and MediaPackage to run on the same UTC wall clock time. This is a requirement, otherwise playback timing or synchronization issues can occur. Choose from the following options: @@ -326 +334 @@ If you're using this setting to limit content playback for contractual reasons, - * HTTP Xsdate + * `UTC Direct` @@ -328 +336 @@ If you're using this setting to limit content playback for contractual reasons, - 8. For **UTC timing source** , specify a URI to use for UTC synchronization. This is the URI used to fetch the timing data according to the scheme defined by **UTC timing**. This value is only valid if **UTC timing** is not `NONE` or `UTC DIRECT`. This value will be set as the `@value` attribute for the `UTCTiming` element. For information about `@value`, see [DASH clock synchronization](https://dashif.org/dash.js/pages/usage/clock-sync.html). + * `HTTP Head` @@ -330 +338,7 @@ If you're using this setting to limit content playback for contractual reasons, - 9. For **DASH period triggers** , choose how MediaPackage creates media presentation description (MPD) periods in the DASH output manifest. For more information, see [Multi-period DASH in AWS Elemental MediaPackage](./multi-period.html). Choose from the following options: + * `HTTP Iso` + + * `HTTP Xsdate` + + 10. For **UTC timing source** , specify a URI to use for UTC synchronization. This is the URI used to fetch the timing data according to the scheme defined by **UTC timing**. This value is only valid if **UTC timing** is not `NONE` or `UTC DIRECT`. This value will be set as the `@value` attribute for the `UTCTiming` element. For information about `@value`, see [DASH clock synchronization](https://dashif.org/dash.js/pages/usage/clock-sync.html). + + 11. For **DASH period triggers** , choose how MediaPackage creates media presentation description (MPD) periods in the DASH output manifest. For more information, see [Multi-period DASH in AWS Elemental MediaPackage](./multi-period.html). Choose from the following options: @@ -342 +356,82 @@ If you're using this setting to limit content playback for contractual reasons, -###### Note + 12. Select **Configure subtitle TTML profile** to optionally configure the profile that TTML subtitles use. + +**Subtitle TTML profile** + + +The profile that MediaPackage uses when signaling subtitles in the manifest. **IMSC** is the default profile. **EBU-TT-D** produces subtitles that are compliant with the EBU-TT-D TTML profile. MediaPackage passes through subtitle styles to the manifest. For more information about EBU-TT-D subtitles, see [EBU-TT-D Subtitling Distribution Format](https://tech.ebu.ch/publications/tech3380). + + 13. Select **Configure program information** to optionally provide details about the content that you want MediaPackage to pass through in the manifest to the playback device. To read more about program information, see the _Program information_ section of the [ISO 23009-1 DASH standards](https://dashif.org/news/5th-edition/). + +**Title** + + +The title for the manifest. + +**Source** + + +Information about the content provider. + +**Copyright** + + +A copyright statement about the content. + +**Language code** + + +The language code for this manifest. + +**More information URL** + + +An absolute URL that contains more information about this content. + + 14. Select **Configure DASH base URLs** to optionally specify one or more locations for the segments. For more information, see the _Base URL section_ of the [ISO 23009-1 DASH standards](https://dashif.org/news/5th-edition/) and _Handling of BaseURLs by players_ in the DVB.org [MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks document](https://dvb.org/wp-content/uploads/2021/06/A168r4_MPEG-DASH-Profile-for-Transport-of-ISO-BMFF-Based-DVB-Services_Draft-ts_103-285-v140_November_2021.pdf). + +**URL** + + +The Base URL. + +**Service location** + + +The name of the Base URL location. + +**DVB priority** + + +For endpoints that use the DVB-DASH profile only. The priority that the playback device should use this Base URL. Lower values are higher priority. + +**DVB weight** + + +For endpoints that use the DVB-DASH profile only. The weighting for Base URLs with the same priority. + + 15. For endpoints that use the DVB-DASH profile, select **Configure DVB-DASH settings** to optionally pass to the player information for downloading subtitle fonts and sending error reports to pass through in the manifest to the playback device. For more information about these settings, see _DVB font download scheme_ and _DVB metrics reporting_ in the DVB.org [MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks document](https://dvb.org/wp-content/uploads/2021/06/A168r4_MPEG-DASH-Profile-for-Transport-of-ISO-BMFF-Based-DVB-Services_Draft-ts_103-285-v140_November_2021.pdf). + +These settings are compatible only with the DASH-DVB profile. **Profiles** must be set to **DVB-DASH** to set these fields. + +**Font download URL** + + +The URL of the font to download for subtitles. + +**Font family** + + +The `fontFamily` name for subtitles, as described in [EBU-TT-D Subtitling Distribution Format](https://tech.ebu.ch/publications/tech3380). + +**MIME type** + + +The `mimeType` of the resource that's at the indicated **Font download URL**. Options are **application/font-sfnt** and **application/font-woff** , as described in the [DVB.org DASH document](https://dvb.org/wp-content/uploads/2021/06/A168r4_MPEG-DASH-Profile-for-Transport-of-ISO-BMFF-Based-DVB-Services_Draft-ts_103-285-v140_November_2021.pdf) linked above. + +**Error metrics reporting URL** + + +The URL to which a reporting player will send error reports. + +**Probability** + @@ -344 +439 @@ If you're using this setting to limit content playback for contractual reasons, -New periods will always be created on DRM settings changes, independently of the DASH period triggers that you configure. +The number of playback devices per 1000 that will send error reports to the reporting URL. This integer represents the probability that the playback device will be a reporting player for this session. @@ -346 +441 @@ New periods will always be created on DRM settings changes, independently of the - 10. For **Ad markers** , choose how ad markers are signaled in the output manifests. All the non-ad markers that you include in the content stream in your upstream encoders will also be present in the output manifests. Choose from the following options: + 16. For **Ad markers** , choose how ad markers are signaled in the output manifests. All the non-ad markers that you include in the content stream in your upstream encoders will also be present in the output manifests. Choose from the following options: @@ -352 +447 @@ New periods will always be created on DRM settings changes, independently of the - 11. Select **Enable filter configuration** if you want to optionally add filters and settings to modify manifests. These filters apply to all manifests that originate from this endpoint. + 17. Select **Enable filter configuration** if you want to optionally add filters and settings to modify manifests. These filters apply to all manifests that originate from this endpoint.