The CP code used can be changed

Change this if you'd like to use a different CP code to collect usage and billing data for this specific Edge IP Binding configuration.

The property hostname can be upgraded from non-secure to secure

Upgrade if you need to change delivery security for Edge IP Binding from HTTP to HTTPS. Upgrading incorporates Enhanced TLS security and after it's complete, you need to provision an SNI-Only, Enhanced TLS certificate and apply it to the corresponding property hostname in Property Manager, similar to what's covered in Use enhanced TLS (HTTPS).

📘

Downgrading from HTTPS to HTTP is not supported.

Slot/Serial settings can be changed

This varies, depending on the level of delivery security set along with EIPB:

• HTTP. The Slot value does not apply to HTTP delivery. When Edge IP Binding is enabled, a unique Serial is generated for HTTP. We use this Serial along with various maprule settings to generate the forward-host header. You can have this value changed, if necessary.

• HTTPS. The following points apply for these values for secure delivery:

  • The Slot. The active slot is associated with an Enhanced/Standard TLS certificate that's "SNI-Only," or the shared certificate that's been grand-fathered in for use. When enhanced TLS, standard TLS, or a shared cert hostname secure delivery is set up with Edge IP Binding, this value is pulled from the certificate. If your account representative is changing this value, it must be associated with another SNI-Only certificate, or the shared certificate hostname.

  • The Serial. The Edge IP Binding tool sets the Serial using {Slot}%2000 and uses it, along with various maprule settings to generate the forward-host header.

The IP version can be upgraded

If you're currently using IPv4 Only, you can have this upgraded to Dual Stack (IPv4 + IPv6).

📘

Downgrading from Dual Stack to IPv4 Only is not supported.

Hostnames can be modified or added via Host Headers

When Edge IP Binding is enabled in Property Manager, you include one or more of your hostnames in a property hostname to edge hostname association, to field requests from end users. Host Headers in the Edge IP Binding configuration can be edited to add or remove hostnames. You can also determine if the exact hostname should be considered for requests. For example, with "myvideos.com" only requests sent to http://www.myvideos.com use Edge IP Binding addresses. Or, the suffix of the hostname is to be used. For example, any requests for myvideos.com that end in this hostname—https://www.baseball.myvideos.com, https://www.football.myvideos.com—use the Edge IP Binding addresses. There is no limit on the number of host headers you can include.

Maprule settings can be changed

Maprules are fixed settings that are tied to your selected product (Adaptive Media Delivery, for example). They consist of a specific ID and name that are both used along with the Serial to generate the forward hostname. Requests to your Edge IP Binding network IP addresses are forwarded to this hostname on the Edge IP Binding edge to obtain content. In very rare circumstances, Edge IP Binding may determine that your environment requires different Maprule ID or Maprule Name values (or both) to best distribute your content.

Edge IP Binding IP assignments can be changed

By default, Edge IP Binding grants you a quantity of Anycast IP addresses for use. You may, however, have IP addresses you've configured with a third party (ISP) that you want to use for zero-rated billing. You can have these addresses applied to your Edge IP Binding configuration, instead.