Fixes/Changes:

Files using the extension “m4i” are now recognized as DASH “init” segments, and their Content-Type is set as “video/mp4.” Prior to this change, files using the “m4i” extension were treated as an “unknown” stream format.

Introducing the “Time Interval” match type

This match allows you to invoke certain property behaviors in a scheduled manner. (You configure them within a specified time range under this match.) Currently, this match type is not supported for use with the following behaviors:

• Cache Key Query Parameters
• Client Characteristics
• Content Characteristics
• Content Provider Code
• HTTPS Cache Key Sharing
• Ignore Case In Cache Key
• Origin Characteristics
• Origin Server
• Segmented Media Delivery Mode

Introducing the Edge IP Binding application

This application provides a unified view of all your Edge IP Binding configurations, as well as access to advanced settings. It is open to Edge IP Binding customers, and can be accessed via the Luna Control Center under CONFIGURE > Edge IP Binding.

Contact your Account Representative for more information and to add Edge IP Binding to your contract.

New Features:

• Manifest Personalization: This new feature for Adaptive Media Delivery (AMD) allows you to improve the viewing experience at scale by modifying the HLS Master Manifests that are served to your end users. You can filter in bitrates based on end user request, as well as set a preferred bitrate at the top of the manifest. We also provide a ‘Best Practice’ mode that allows you to use Apple recommended settings for iOS and TvOS devices. Please contact your account representative for more information on Manifest Personalization. The feature is currently in the Beta phase.

Fixes:

• Media Encryption-related fix:  With this update, if you have Media Encryption enabled, a valid session ID should be present in the query string for the init segment request. This is applicable to HLS Live and VOD streams that use CMAF segments.

New Features:

• Protocol Downgrade (HTTPS Downgrade to Origin): This has been added as a self-serviceable behavior in the Property Editor in Luna, and it does not requiring additional entitlement. It lets you downgrade HTTPS requests for Standard TLS and Shared Cert options. Complete details on use can be found in the Adaptive Media Delivery - Implementation Guide.
• New headers in the Default CORS Policy rule: The Access-Control-Expose-Headers response header in the Modify Outgoing Response Header behavior in Property Editor now contains two additional header names: “Akamai-Mon-Iucid-Ing” and “Akamai-Mon-Iucid-Del.”  These both support client-side analytics. If you create a new AMD property configuration (or update an existing one), these two headers are automatically added to the Access-Control-Expose-Headers list.

Fixes/Changes:

• The Proxy Protection option has been removed: This feature is no longer available in the Content Targeting - Protection behavior, for Adaptive Media Delivery property configurations in Property Editor in Luna.

New Feature:

• Content Targeting: Protection for Adaptive Media Delivery is available as a self-serviceable behavior for customers with it added to their contract.  It can be applied to an AMD configuration via the Property Manager in Luna. 

Fixes:

• Authentication request failure issue: Requests to the Google Cloud Platform and Amazon Web Services were failing if either Token Auth or Media Encryption were enabled.

This option can be enabled by using the “Segmented Content Protection” Behavior in Property Manager. If Media Encryption is not present on your contract, enabling this option will show an error.

Please see the documentation for this feature for more information.

As part of self-serviceability enhancements, the following changes have been added:

• There are three new mandatory behaviors called Origin Characteristics, Content Characteristics and Client Characteristics.

• Segmented Media Delivery Mode behavior is now mandatory. Using these behaviors, appropriate optimizations for the property are automatically applied, including settings for Caching and Tiered Distribution.

These behaviors will automatically be part of new configurations. If you update an existing configuration, you will need to add these behaviors (by clicking ‘Add Behavior’ in the Behaviors section of Property Manager). If you aren’t sure which options to select in a new behavior’s drop-down lists, you may leave them set to the default settings of ‘Unknown,’ in which case the behavior will not take effect. It is a best practice to test configuration changes in staging before deploying to production.