Content Delivery Network Interconnection (CDNI) Control Interface / Triggers 2nd Edition

2.2.1. Multiple Interconnected CDNs

In a network of interconnected CDNs, a single uCDN will originate a given item of metadata and associated content. It would possibly distribute that metadata and content to more than one dCDN, which in turn distribute that metadata and content to additional CDNs located further downstream.¶

An intermediate CDN is a dCDN that passes on CDNI Metadata and content to dCDNs located further downstream.¶

A "diamond" configuration is one where a dCDN can acquire metadata and content originated in one uCDN from that uCDN itself and an intermediate CDN, or via more than one intermediate CDN.¶

CI/T Commands originating in the single source uCDN affect metadata and content in all dCDNs; however, in a diamond configuration, it may not be possible for the dCDN to determine from which uCDN it acquired content. In this case, a dCDN MUST allow each uCDN from which it may have acquired the content to act upon that content using CI/T Commands.¶

In all other cases, a dCDN MUST reject CI/T Commands from a uCDN that attempts to act on another uCDN's content by using, for example, responding with an HTTP 403 ("Forbidden").¶

Security considerations are discussed further in Section 12.¶

The diamond configuration may lead to inefficient interactions, but the interactions are otherwise harmless. For example:¶

• When the uCDN issues an "invalidate" CI/T Command, a dCDN will receive that command from multiple directly connected uCDNs. The dCDN may schedule multiple such commands separately, and the last scheduled command may affect content already revalidated following execution of the "invalidate" command that was scheduled first.¶

• If one of a dCDN's directly connected uCDNs loses its rights to distribute content, it may issue a CI/T "purge" command. That purge may affect content the dCDN could retain because it's distributed by another directly connected uCDN. But, that content can be reacquired by the dCDN from the remaining uCDN.¶

• When the uCDN originating an item of content issues a CI/T purge followed by a pre-position, two directly connected uCDNs will pass those commands to a dCDN. That dCDN implementation need not merge those operations or notice the repetition, in which case the purge issued by one uCDN will complete before the other. The first uCDN to finish its purge may then forward the "preposition" trigger, and content pre-positioned as a result might be affected by the still-running purge issued by the other uCDN. However, the dCDN will reacquire that content as needed, or when it's asked to pre-position the content by the second uCDN. A dCDN implementation could avoid this interaction by knowing which uCDN it acquired the content from, or it could minimize the consequences by recording the time at which the "invalidate"/"purge" command was received and not applying it to content acquired after that time.¶

3.2.1. Trigger Subject

As the scope of the trigger may relate to either metadata as well as content, the "trigger spec object" also specifies the trigger's target subject (i.e., metadata or content) against which to match.¶

All trigger subjects MUST be registered in the IANA "CDNI CI/T Trigger Subjects" registry (see Section 11.4).¶

A dCDN receiving a request containing a trigger subject it does not recognize or does not support MUST reject the request by creating a Trigger Status Resource with a status of "failed" and the "errors" array containing an Error.v2 Description with error "esubject" (see Section 6.2.7).¶

This document also defines an initial set of trigger subject values and registers them in the IANA "CDNI CI/T Trigger Subjects" registry:¶

3.2.2. Content URLs

Each CI/T Command usually refers to the targets by the target URLs, using a "urls" trigger spec object or some aggregating spec such as the "url-regex-match". If content URLs are transformed by an intermediate CDN in a cascade, that intermediate CDN MUST similarly transform URLs in CI/T Commands it passes to its dCDN.¶

When processing Trigger Specifications, CDNs MUST ignore the URL scheme (HTTP or HTTPS) in comparing URLs. For example, for a CI/T "invalidate" or "purge" command, content MUST be invalidated or purged regardless of the protocol clients used to request it.¶

5.2.1. Polling Trigger Status Resource Collections

The uCDN can fetch the collection of its Trigger Status Resources or filtered views of that collection.¶

This makes it possible to poll the status of all CI/T Trigger Commands in a single request. If the dCDN moves a Trigger Status Resource from the active to the completed collection, the uCDN can fetch the result of that activity.¶

When polling in this way, the uCDN SHOULD use HTTP ETags to monitor for change, rather than repeatedly fetching the whole collection. An example of this is given in Section 10.2.4.¶

5.2.2. Polling Trigger Status Resources

The uCDN has a URI provided by the dCDN for each Trigger Status Resource it has created. It may fetch that Trigger Status Resource at any time.¶

This can be used to retrieve progress information and to fetch the result of the CI/T Command.¶

When polling in this way, the uCDN SHOULD use HTTP ETags to monitor for change, rather than repeatedly fetching the Trigger Status Resource.¶

5.7.1. Error propagation

This subsection explains the mechanism for enabling the uCDN to trace an error back to the dCDN in which it occurred. CDNI triggers may be propagated over a chain of downstream CDNs. For example, an upstream CDN A (uCDN-A) that is delegating to a downstream CDN B (dCDN-B) and dCDN-B is delegating to a downstream CDN C (dCDN-C). Triggers sent from uCDN-A to dCDN-B may be redistributed from dCDN-B to dCDN-C, and errors can occur anywhere along the path. Therefore, it might be essential for uCDN-A that sets the trigger, be able to trace back an error to the downstream CDN where it occurred. This document adds a mechanism to propagate the PID of the dCDN where the fault occurred, back to the uCDN by adding the PID to the error.v2 description. When dCDN-B propagates a trigger further to the downstream dCDN-C, it MUST also propagate back the errors received in the trigger status resource from dCDN-C by adding them to the errors array in its own status resource to be sent back to the originating uCDN-A. While propagating back the errors dCDN-B MAY also specify the dCDN-C PID, indicating to which CDN the error specifically relates. The trigger originating upstream CDN then receives an array built of the errors that occurred in all the CDNs along the execution path, where each error MAY be carrying its own CDN identifier.¶

Figure 2 below is an example showing the message flow used by uCDN-A to trigger activity in the dCDN-B, followed by dCDN-C, as well as the discovery of the status of that activity, including the Error Propagation.¶

uCDN-A                         dCDN-B                         dCDN-C
 |                              |                              |
 | (1) POST                     |                              |
 | https://dcdn-b.example.com   |                              |
 | /triggers/uCDN-A             |                              |
[ ]--------------------------->[ ]--+                          |
 |                             [ ]  | (2)                      |
 |                             [ ]<-+                          |
 | (3) HTTP 201 Response.      [ ]                             |
 |<----------------------------[ ]                             |
 | Loc:                        [ ]                             |
 | https://dcdn-b.example.com  [ ] (4) POST                    |
 | /triggers/uCDN-A/123        [ ] https://dcdn-c.example.com  |
 |                             [ ] /triggers/dCDN-B            | (5)
 |                             [ ]--------------------------->[ ]--+
 |                              |                             [ ]  |
 |                              |                             [ ]<-+
 |                              | (6) HTTP 201 Response.      [ ]
 |                             [ ]<---------------------------[ ]
 |                              |  Loc:                        |
 |                              |  https://dcdn-c.example.com  |
 |                              |  /triggers/dCDN-B/456        |
 |                              |                              |
 |                             [ ]--+                          |
 |                             [ ]  | (7.1)                    |
 |                             [ ]<-+                         [ ]--+
 |                              |                       (7.2) [ ]  |
 |                              |                             [ ]<-+
 |                              |                              |
 .                              .                              .
 .                              .                              .
 .                              .                              .
 |                              | (8) GET                      |
 |                              | https://dcdn-c.example.com   |
 |                              | /triggers/dCDN-B/456         |
 |                             [ ]--------------------------->[ ]
 |                              |                             [ ]
 |                              | (9) HTTP 200                [ ]
 |                              | Trigger Status Resource     [ ]
 |                             [ ]<---------------------------[ ]
 |                              |                              |
 .                              .                              .
 .                              .                              .
 .                              .                              .
 | (10) GET                     |                              |
 | https://dcdn-b.example.com   |                              |
 | /triggers/uCDN-A/123         |                              |
[ ]--------------------------->[ ]                             |
 |                             [ ]                             |
 | (11) HTTP 200               [ ]                             |
 | Trigger Status Resource     [ ]                             |
[ ]<---------------------------[ ]                             |

The steps in Figure 2 are as follows:¶

1. The uCDN-A triggers action in the dCDN-B by POSTing a CI/T Command to a collection of Trigger Status Resources "https://dcdn-b.example.com/triggers/uCDN-A". This URL was given to the uCDN-A when the CI/T interface was established.¶

2. The dCDN-B authenticates the request, validates the CI/T Command, and, if it accepts the request, creates a new Trigger Status Resource.¶

3. The dCDN-B responds to the uCDN-A with an HTTP 201 response status and the location of the Trigger Status Resource.¶

4. The dCDN-B triggers the action in the dCDN-C by POSTing a CI/T Command to a collection of Trigger Status Resources "https://dcdn-c.example.com/triggers/dCDN-B". This URL was given to the dCDN-B when the CI/T interface was established.¶

5. The dCDN-C authenticates the request, validates the CI/T Command, and, if it accepts the request, creates a new Trigger Status Resource.¶

6. The dCDN-C responds to the dCDN-B with an HTTP 201 response status and the location of the Trigger Status Resource.¶

7. The dCDN-C acts upon the CI/T Command. However, the command fails at dCDN-C as, for example, the Trigger Specification contains an "action type" that is not supported by dCDN-C. dCDN-C's action is depicted by 7.2 in the diagram, while 7.1 shows dCDN-B acting on its own command.¶

8. The dCDN-B queries, possibly repeatedly, the Trigger Status Resource in dCDN-C.¶

9. The dCDN-C responds with the Trigger Status Resource, describing the progress or results of the CI/T Trigger Command. In the described flow, the returned Status is "failed", with an Error.v2 Description Object holding an "eunsupported" Error Code reflecting the status response.¶

10. The uCDN-A queries, possibly repeatedly, the Trigger Status Resource in dCDN-B.¶

11. The dCDN-B responds with the Trigger Status Resource, describing the progress or results of the CI/T Trigger Command. In the flow described above, the returned Status is "failed", and the "eunsupported" error received in the trigger status resource from dCDN-C is propagated along with dCDN-C PID by adding it to the errors array in dCDN-B's own status resource to be sent back to the originating uCDN-A.¶

6.1.1. CI/T Trigger Command

CI/T Trigger Command, which is used to create a new trigger, MUST use a MIME media type of "application/cdni; ptype=ci-trigger-command.trigger.v2".¶

A CI/T Trigger Command is encoded as a JSON object containing the following name/value pairs.¶

• Name: trigger

  Description: A specification of the trigger action and a set of targets upon which to act.¶

  Value: A Trigger.v2 Specification, as defined in Section 6.2.1.¶

  Mandatory: Yes.¶

  Name: cdn-path

  Description: The CDN PIDs of CDNs that have already issued the CI/T Command to their dCDNs.¶

  Value: A non-empty JSON array of JSON strings, where each string is a CDN PID as defined in Section 5.6.¶

  Mandatory: Yes.¶

6.1.2. CI/T Cancel Command

CI/T Cancel Command, which is used to cancel an existing trigger, MUST use a MIME media type of "application/cdni; ptype=ci-trigger-command.cancel".¶

A CI/T Cancel Command is encoded as an empty JSON object.¶

6.1.3. Trigger Status Resources

Trigger Status Resources MUST use a MIME media type of "application/cdni; ptype=ci-trigger-status.v2".¶

A Trigger Status Resource is encoded as a JSON object containing the following name/value pairs.¶

• Name: trigger

  Description: The Trigger Specification POSTed in the body of the CI/T Command. Note that this need not be a byte-for-byte copy. For example, in the JSON representation the dCDN may re-serialize the information differently.¶

  Value: A Trigger.v2 Specification, as defined in Section 6.2.1.¶

  Mandatory: Yes.¶

  Name: ctime

  Description: Time at which the CI/T Command was received by the dCDN. Time is determined by the dCDN; there is no requirement to synchronize clocks between interconnected CDNs.¶

  Value: Absolute Time, as defined in Section 6.2.4.¶

  Mandatory: Yes.¶

  Name: mtime

  Description: Time at which the Trigger Status Resource was last modified. Time is determined by the dCDN; there is no requirement to synchronize clocks between interconnected CDNs.¶

  Value: Absolute Time, as defined in Section 6.2.4.¶

  Mandatory: Yes.¶

  Name: etime

  Description: Estimate of the time at which the dCDN expects to complete the activity. Time is determined by the dCDN; there is no requirement to synchronize clocks between interconnected CDNs.¶

  Value: Absolute Time, as defined in Section 6.2.4.¶

  Mandatory: No.¶

  Name: status

  Description: Current status of the triggered activity.¶

  Value: Trigger Status, as defined in Section 6.2.6.¶

  Mandatory: Yes.¶

  Name: status-reason

  Description: A human-readable explanation for the object status.¶

  Value: A JSON string, the human-readable status reason.¶

  Mandatory: No.¶

  Name: errors

  Description: Descriptions of errors that have occurred while processing a Trigger Command.¶

  Value: An array of Error.v2 Descriptions, as defined in Section 6.2.5. An empty array is allowed and is equivalent to omitting "errors" from the object.¶

  Mandatory: No.¶

6.1.4. Trigger Collections

Trigger Collections MUST use a MIME media type of "application/cdni; ptype=ci-trigger-collection".¶

A Trigger Collection is encoded as a JSON object containing the following name/value pairs.¶

• Name: triggers

  Description: Links to Trigger Status Resources in the collection.¶

  Value: A JSON array of zero or more URLs, represented as JSON strings.¶

  Mandatory: Yes.¶

  Name: staleresourcetime

  Description: The length of time for which the dCDN guarantees to keep a completed Trigger Status Resource. After this time, the dCDN SHOULD delete the Trigger Status Resource and all references to it from collections.¶

  Value: A JSON number, which must be a positive integer, representing time in seconds.¶

  Mandatory: Yes, in the collection of all Trigger Status Resources if the dCDN deletes stale entries. If the property is present in the filtered collections, it MUST have the same value as in the collection of all Trigger Status Resources.¶

  Name: coll-all

  Description: Link to a Trigger Collection representing all Trigger Status Resources.¶

  Value: A URL represented as a JSON string.¶

  Mandatory: Links to all of the filtered collections are mandatory in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Otherwise, optional.¶

  Name: coll-pending

  Description: Link to a Trigger Collection representing Trigger Status Resources that have been accepted but not yet acted upon.¶

  Value: A URL represented as a JSON string.¶

  Mandatory: Links to all of the filtered collections are mandatory in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Otherwise, optional.¶

  Name: coll-active

  Description: Link to a Trigger Collection representing Trigger Status Resources that are currently being processed in the dCDN.¶

  Value: A URL represented as a JSON string.¶

  Mandatory: Links to all of the filtered collections are mandatory in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Otherwise, optional.¶

  Name: coll-complete

  Description: Link to a Trigger Collection representing Trigger Status Resources that completed successfully.¶

  Value: A URL represented as a JSON string.¶

  Mandatory: Links to all of the filtered collections are mandatory in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Otherwise, optional.¶

  Name: coll-failed

  Description: Link to a Trigger Collection representing Trigger Status Resources that failed or were cancelled by the uCDN.¶

  Value: A URL represented as a JSON string.¶

  Mandatory: Links to all of the filtered collections are mandatory in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Otherwise, optional.¶

  Name: cdn-id

  Description: The CDN PID of the dCDN.¶

  Value: A JSON string, the dCDN's CDN PID, as defined in Section 5.6.¶

  Mandatory: Only in the collection of all Trigger Status Resources, if the dCDN implements the filtered collections. Optional in the filtered collections (the uCDN can always find the dCDN's cdn-id in the collection of all Trigger Status Resources, but the dCDN can choose to repeat that information in its implementation of filtered collections).¶

6.2.1. Trigger.v2 Specification

A Trigger.v2 Specification is encoded as a JSON object containing the following name/value pairs.¶

An unrecognized name/value pair in the Trigger Specification object contained in a CI/T Command SHOULD be preserved in the Trigger Specification of any Trigger Status Resource it creates. Note that the preferred method for extending the CI/T capabilities is by defining new related trigger specs and/or trigger extensions, rather than adding new properties to the Trigger.v2 object.¶

• Name: action

  Description: Defines the type of the CI/T Trigger Action.¶

  Value: Trigger Action Type, as defined in Section 3.1.¶

  Mandatory: Yes.¶

  Name: specs

  Description: Array of trigger specs representing trigger's targets.¶

  Value: Array of GenericTriggerSpec objects (see Section 6.2.2.1).¶

  Mandatory: Yes. Furthermore, the list MUST NOT be empty.¶

  Name: extensions

  Description: Array of trigger extensions.¶

  Value:Array of GenericTriggerExtension objects (see Section 6.2.3.2).¶

  Mandatory: No. The default is no extensions.¶

6.2.2. Generic Trigger Specs

A "trigger.v2" object, as defined in Section 6.2.1, includes an array of trigger spec objects. Each trigger spec object contains properties that are used as trigger target selection directives for the dCDN when executing the trigger command, e.g., content URLs or metadata URI patterns. Each such CDNI Trigger Spec is a specialization of a CDNI GenericTriggerSpec object. The GenericTriggerSpec object abstracts the basic information required for trigger distribution from the specifics of any given property (i.e., property semantics, enforcement options, etc.).¶

The semantics of the Trigger Specs list is additive, i.e., the trigger applies to any object matching one of the listed specs.¶

{
  "generic-trigger-spec-type":
     <Type of this trigger spec>,
  "generic-trigger-spec-value":
      {
        <properties of this trigger spec object>
      },
   "generic-trigger-spec-subject":
     <Category of this trigger spec subject>

}

6.2.3. CI/T Trigger Extensions

A "trigger.v2" object, as defined in Section 6.2.1 includes an optional array of trigger extension objects. A trigger extension contains properties that are used as directives for the dCDN when executing the trigger command, e.g., location policies, time policies, and so on. Each such CDNI Trigger extension is a specialization of a CDNI GenericTriggerExtension object. The GenericTriggerExtension object abstracts the basic information required for trigger distribution from the specifics of any given property (i.e., property semantics, enforcement options, etc.). All trigger extensions are optional, and it is thus the responsibility of the extension specification to define a consistent default behavior for extensions supported by a dCDN when not specified by the uCDN.¶

{
  "generic-trigger-extension-type":
     <Type of this trigger extension object>,
  "generic-trigger-extension-value":
      {
        <properties of this trigger extension object>
      },
  "mandatory-to-enforce": <bool>,
  "safe-to-redistribute": <bool>,
  "incomprehensible": <bool>
}

6.2.4. Absolute Time

A JSON number, seconds since the UNIX epoch (00:00:00 UTC on 1 January 1970).¶

6.2.5. Error.v2 Description

An Error.v2 Description is used to report the failure of a CI/T Command or failure in the activity it triggered. It is encoded as a JSON object with the following name/value pairs:¶

• Name: error

  Value: Error Code, as defined in Section 6.2.7.¶

  Mandatory: Yes.¶

• Name: description

  Description: A human-readable description of the error.¶

  Value: A JSON string, the human-readable description.¶

  Mandatory: No.¶

• Name: specs

  Description: Array of trigger spec objects from the corresponding "specs" array at the Trigger Specification. Only those spec to which the error applies are listed.¶

  Value: Array Trigger Specifications, as defined in Section 6.2.1, where each spec object MUST be exactly as they appear in the request.¶

  Mandatory: Yes.¶

• Name: extensions

  Description: Array of trigger extension objects copied from the corresponding "extensions" array from the Trigger Specification. Only those extensions to which the error applies are included, but those extensions MUST be exactly as they appear in the request.¶

  Value: Array of GenericTriggerExtension objects, where each extension object is copied from the "extensions" array values in the Trigger Specification.¶

  Mandatory: No. The "extensions" array SHOULD be used only if the error relates to extension objects. Property omission should be interpreted as "the error is not related to any extension".¶

• Name: cdn-id

  Description: The CDN PID of the CDN where the error occurred. The "cdn-id" property is used by the originating uCDN or by the propagating dCDN in order to distinguish in which CDN the error occurred.¶

  Value: A non-empty JSON string, where the string is a CDN PID as defined in Section Section 5.6¶

  Mandatory: Yes. The dCDN may use its own CDN PID if it does not want to expose the CDN PIDs of dCDNs.¶

Example of a JSON serialized Error.v2 Description object reporting a malformed Playlist:¶

{
  "error": "econtent",
  "description": "Failed to parse HLS playlist",
  "specs": [
    {
      "trigger-subject": "content",
      "generic-trigger-spec-type": "content-playlist",
      "generic-trigger-spec-value": {
        "playlist": "https://www.example.com/hls/title/index.m3u8",
        "media-protocol": "hls"
      }
    }
  ],
  "cdn": "AS64500:0"
}

Example of a JSON serialized Error.v2 Description object reporting an unsupported extension object:¶

{
  "errors": [
    {
      "error": "eextension",
      "description": "unrecognized extension <type>",
      "specs": [
        {
          "trigger-subject": "content",
          "generic-trigger-spec-type": "urls",
          "generic-trigger-spec-value": {
            "urls": [
              "https://www.example.com/a/b/c/1",
              "https://www.example.com/a/b/c/2"
            ]
          }
        }
      ],
      "extensions": [
        {
          "generic-trigger-extension-type":
            <type of this erroneous trigger extension object>,
          "generic-trigger-extension-value": {
            <properties of this erroneous trigger extension object>
          }
        }
      ],
      "cdn": "AS64500:0"
    }
  ]
}

6.2.6. Trigger Status

Trigger Status describes the current status of the triggered activity. It MUST be one of the JSON strings in the following table:¶

Along with the Trigger Status, the Trigger Status Resource object includes a Status Reason property, allowing the dCDN to provide additional information for the trigger status. For example, the dCDN may indicate that the trigger status is "pending" due to one of the execution prerequisites not being fulfilled. Such a prerequisite may possibly be specified via one of the extensions.¶

6.2.7. Error Code

This type is used by the dCDN to report failures in trigger processing. All Error Codes MUST be registered in the IANA "CDNI CI/T Error Codes" registry (see Section 11.7). Unknown Error Codes MUST be treated as fatal errors, and the request MUST NOT be automatically retried without modification.¶

The following Error Codes are defined by this document and MUST be supported by an implementation of the CI/T interface utilizing the ci-trigger-command.trigger.v2 and the ci-trigger-status.v2 objects.¶

7.3.1. UriPatternMatch

A UriPatternMatch consists of a string pattern to match against a URI, and flags describing the type of match.¶

It is encoded as a JSON object with the following name/value pairs:

Name: pattern¶

Description: A pattern for URI matching.¶

Value: A JSON string representing the pattern. The pattern can contain the wildcards * and ?, where * matches any sequence of [RFC3986] pchar or "/" characters (including the empty string) and ? matches exactly one [RFC3986] pchar character. The three literals $, * and ? MUST be escaped as $$, $* and $? (where $ is the designated escape character). All other characters are treated as literals.¶

Mandatory: Yes.¶

Name: case-sensitive

Description: Flag indicating whether or not case-sensitive matching should be used.¶

Value: One of the JSON values "true" (the matching is case sensitive) or "false" (the matching is case insensitive).¶

Mandatory: No; default is "false", i.e., a case-insensitive match.¶

Name: match-query-string

Description: Flag indicating whether to include the query part of the URI when comparing against the pattern.¶

Value: One of the JSON values "true" (the full URI, including the query part, should be compared against the given pattern) or "false" (the query part of the URI should be dropped before comparison with the given pattern).¶

Mandatory: No; default is "false". The query part of the URI should be dropped before comparison with the given pattern.¶

Example of case-sensitive prefix match against "https://www.example.com/trailers/":¶

{
    "pattern": "https://www.example.com/trailers/*",
    "case-sensitive": true
}

7.4.1. RegexMatch

A RegexMatch consists of a regular expression string a URI is matched against, and flags describing the type of match. It is encoded as a JSON object with following properties:¶

• Property: regex¶

  • Description: A regular expression for URI matching.¶

  • Type: A regular expression to match against the URI, i.e., against the path-absolute and the query string parameters [RFC3986]. The regular expression string MUST be compatible with POSIX [POSIX.1] Section 9 Extended Regular Expressions. This regular expression MUST be evaluated in the POSIX locale (POSIX [POSIX.1] Section 7.2).¶

  • Note: Because '\' has a special meaning in JSON [RFC8259] as the escape character within JSON strings, the regular expression character '\' MUST be escaped as '\\'.¶

  • Mandatory: Yes.¶

• Property: case-sensitive¶

  • Description: Flag indicating whether or not case-sensitive matching should be used.¶

  • Type: JSON boolean. Either "true" (the matching is case sensitive) or "false" (the matching is case insensitive).¶

  • Mandatory: No; default is "false", i.e., a case-insensitive match.¶

• Property: match-query-string¶

  • Description: Flag indicating whether to include the query part of the URI when comparing against the regex.¶

  • Type: JSON boolean. Either "true" (the full URI, including the query part, should be compared against the regex) or "false" (the query part of the URI should be dropped before comparison with the given regex).¶

  • Mandatory: No; default is "false". The query part of the URI MUST be dropped before comparison with the given regex. This makes the regular expression simpler and safer for cases in which the query parameters are not relevant for the match.¶

Example of a case sensitive, no query parameters, regex match against:¶

"^(https:\/\/video\.example\.com)\/([a-z])\/
 movie1\/([1-7])\/*(index.m3u8|\d{3}.ts)$"

{
  "regex": "^(https:\\/\\/video\\.example\\.com)\\/([a-z])\\/movie1\
           \/([1-7])\\/*(index.m3u8|\\d{3}.ts)$",
  "case-sensitive": true,
  "match-query-string": false
}

This regex matches URLs of domain video.example.com where the path structure is /(single lower case letter)/(name-of-title)/(single digit between 1 to 7)/(index.m3u8 or a 3 digit number with ts extension). For example:¶

https://video.example.com/d/movie1/5/index.m3u8
or
https://video.example.com/k/movie1/4/013.ts

7.5.1. Playlist

A Playlist consists of a full URL and a media protocol identifier. An implementation that supports a specific playlist media protocol MUST be able to parse playlist files of that protocol type and extract, possibly recursively, the URLs to all media objects and/or sub playlist files, and apply the trigger to each one of them separately.¶

Playlist is encoded as a JSON object with following properties:¶

• Property: playlist¶

  • Description: A URL to the playlist file.¶

  • Type: A URL represented as a JSON string.¶

  • Mandatory: Yes.¶

• Property: media-protocol¶

  • Description: Media protocol to be used when parsing and interpreting this playlist.¶

  • Type: MediaProtocol (see Section 7.5.2).¶

  • Mandatory: Yes.¶

Example of a JSON serialized HLS playlist object:¶

{
  "playlist": "https://www.example.com/hls/title/index.m3u8",
  "media-protocol": "hls"
}

7.5.2. MediaProtocol

Media Protocol objects are used to specify registered type of media protocol (see Section 11.5) used for protocol related operations like pre-position according to playlist.¶

The following table defines the initial MediaProtocol JSON string values corresponding to the HLS, MSS, and DASH protocols:¶

[RFC Editor: Please replace RFCthis with the published RFC number for this document.]¶

8.2.1. UTCWindow

A UTCWindow object describes a time range in UTC or UTC and a zone offset that can be applied by a TimePolicy.¶

• Property: start¶

  • Description: The start time of the window.¶

  • Type: Internet date and time as defined in [RFC3339].¶

  • Mandatory: No, but at least one of "start" or "end" MUST be present and non-empty.¶

• Property: end¶

  • Description: The end time of the window.¶

  • Type: Internet date and time as defined in [RFC3339].¶

  • Mandatory: No, but at least one of "start" or "end" MUST be present and non-empty.¶

Example JSON serialized UTCWindow object that describes a time window from 02:30 01/01/2000 UTC to 04:30 01/01/2000 UTC:¶

{
  "start": "2000-01-01T02:30:00.00Z",
  "end": "2000-01-01T04:30:00.00Z"
}

Example JSON serialized UTCWindow object that describes a time window in New York time zone offset UTC-05:00 from 02:30 01/01/2000 to 04:30 01/01/2000:¶

{
  "start": "2000-01-01T02:30:00.00-05:00",
  "end": "2000-01-01T04:30:00.00-05:00"
}

10.1.1. Preposition

Below is an example of a CI/T "preposition" command -- a POST to the collection of all Trigger Status Resources.¶

Note that pattern based specs like "UriPatternMatch" and "UrisRegexMatch", are not allowed in a pre-position Trigger Specification, where the dCDN has to have a clear list of objects to obtain.¶

REQUEST:

  POST /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*
  Content-Type: application/cdni; ptype=ci-trigger-command.trigger.v2
  Content-Length: 352

  {
      "trigger": {
         "action": "preposition",
         "specs": [
            {
               "trigger-subject": "metadata",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://metadata.example.com/a/b/c"
                  ]
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://www.example.com/a/b/c/1",
                     "https://www.example.com/a/b/c/2",
                     "https://www.example.com/a/b/c/3",
                     "https://www.example.com/a/b/c/4"
                  ]
               }
            }
         ],
      },
      "cdn-path": [ "AS64496:1" ]
  }

RESPONSE:

  HTTP/1.1 201 Created
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Length: 467
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  Location: https://dcdn.example.com/triggers/0
  Server: example-server/0.1

  {
      "ctime": 1462351690,
      "etime": 1462351698,
      "mtime": 1462351690,
      "status": "pending",
      "trigger": {
         "action": "preposition"
         "specs": [
            {
               "trigger-subject": "metadata",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://metadata.example.com/a/b/c"
                  ]
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://www.example.com/a/b/c/1",
                     "https://www.example.com/a/b/c/2",
                     "https://www.example.com/a/b/c/3",
                     "https://www.example.com/a/b/c/4"
                  ]
               }
            }
         ]
      }
  }

10.1.2. Invalidate

Below is an example of a CI/T "invalidate" command -- another POST to the collection of all Trigger Status Resources. This instructs the dCDN to revalidate the content at "https://www.example.com/a/index.html", as well as any metadata and content whose URLs are prefixed by "https://metadata.example.com/a/b/" using case-insensitive matching, and "https://www.example.com/a/b/" using case-sensitive matching, respectively.¶

REQUEST:

  POST /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*
  Content-Type: application/cdni; ptype=ci-trigger-command.trigger.v2
  Content-Length: 387

  {
    "trigger": {
      "action": "invalidate",
      "specs": [
         {
            "trigger-subject": "metadata",
            "generic-trigger-spec-type": "uri-pattern-match",
            "generic-trigger-spec-value": {
               "pattern": "https://metadata.example.com/a/b/*"
            }
         },
         {
            "trigger-subject": "content",
            "generic-trigger-spec-type": "urls",
            "generic-trigger-spec-value": {
               "urls": [
                  "https://www.example.com/a/index.html"
               ]
            }
         },
         {
            "trigger-subject": "content",
            "generic-trigger-spec-type": "uri-pattern-match",
            "generic-trigger-spec-value": {
               "pattern": "https://www.example.com/a/b/*",
               "case-sensitive": true
            }
         }
      ]
    },
    "cdn-path": [ "AS64496:1" ]
  }

RESPONSE:

  HTTP/1.1 201 Created
  Date: Wed, 04 May 2016 08:48:11 GMT
  Content-Length: 545
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  Location: https://dcdn.example.com/triggers/1
  Server: example-server/0.1

  {
      "ctime": 1462351691,
      "etime": 1462351699,
      "mtime": 1462351691,
      "status": "pending",
      "trigger": {
         "action": "invalidate",
         "specs": [
            {
               "trigger-subject": "metadata",
               "generic-trigger-spec-type": "uri-pattern-match",
               "generic-trigger-spec-value": {
                  "pattern": "https://metadata.example.com/a/b/*"
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://www.example.com/a/index.html"
                  ]
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "uri-pattern-match",
               "generic-trigger-spec-value": {
                  "pattern": "https://www.example.com/a/b/*",
                  "case-sensitive": true
               }
            }
         ]
      }
  }

10.1.3. Invalidation with Regex

In the following example a CI/T "invalidate" command uses the Regex property to specify the range of content objects for invalidation, the command is rejected by the dCDN due to regex complexity, and an appropriate error is reflected in the status response.¶

REQUEST:

  POST /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: triggers.dcdn.example.com
  Accept: */*
  Content-Type: application/cdni; ptype=ci-trigger-command.trigger.v2
  {
    "trigger": {
      "action": "invalidate",
      "specs": [
        {
          "trigger-subject": "content",
          "generic-trigger-spec-type": "uri-regex-match",
          "generic-trigger-spec-value": {
            "regex": "^(https:\\/\\/video\\.example\\.com)\\/
              ([a-z])\\/movie1\\/([1-7])\\/*(index.m3u8|\\d{3}.ts)$",
            "case-sensitive": true,
            "match-query-string": false
          }
        }
      ]
    },
    "cdn-path": [ "AS64496:0" ]
  }

RESPONSE:

  HTTP/1.1 201 Created
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Length: 467
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  Location: https://triggers.dcdn.example.com/triggers/2
  Server: example-server/0.1

  {
    "errors": [
      {
        "specs": [
          {
            "trigger-subject": "content",
            "generic-trigger-spec-type": "uri-regex-match",
            "generic-trigger-spec-value": {
              "regex": "^(https:\\/\\/video\\.example\\.com)\\/
                ([a-z])\\/movie1\\/
                ([1-7])\\/*(index.m3u8|\\d{3}.ts)$",
              "case-sensitive": true,
              "match-query-string": false
            }
          }
        ],
        "description": "The dCDN rejected a regex due to complexity",
        "error": "ereject",
        "cdn": "AS64500:0"
      }
    ],
    "ctime": 1462351690,
    "etime": 1462351698,
    "mtime": 1462351690,
    "status": "failed",
    "trigger": { <content of trigger.v2 object from the command> }
  }

10.1.4. Preposition with Playlists

In the following example a CI/T "preposition" command uses the Playlist property to specify the full media library of a specific content. The command fails due to playlist parse error and an appropriate error is reflected in the status response.¶

REQUEST:

  POST /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: triggers.dcdn.example.com
  Accept: */*
  Content-Type: application/cdni; ptype=ci-trigger-command.trigger.v2
  {
    "trigger": {
      "action": "preposition",
      "specs": [
        {
          "trigger-subject": "content",
          "generic-trigger-spec-type": "contentPlaylist",
          "generic-trigger-spec-value": {
            "playlist":
              "https://www.example.com/hls/title/index.m3u8",
            "media-protocol": "hls"
          }
        }
      ]
    },
    "cdn-path": [ "AS64496:0" ]
  }

RESPONSE:

  HTTP/1.1 201 Created
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Length: 467
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  Location: https://triggers.dcdn.example.com/triggers/3
  Server: example-server/0.1

  {
    "errors": [
      {
        "specs": [
          {
            "trigger-subject": "content",
            "generic-trigger-spec-type": "contentPlaylist",
            "generic-trigger-spec-value": {
              "playlist":
                "https://www.example.com/hls/title/index.m3u8",
              "media-protocol": "hls"
            }
          }
        ],
        "description": "The dCDN was not able to parse the playlist",
        "error": "econtent",
        "cdn": "AS64500:0"
      }
    ],
    "ctime": 1462351690,
    "etime": 1462351698,
    "mtime": 1462351690,
    "status": "failed",
    "trigger": { <content of trigger.v2 object from the command> }
  }

10.2.1. Collection of All Triggers

The uCDN can fetch the collection of all Trigger Status Resources it has created that have not yet been deleted or removed or expired. After creation of the "preposition" and "invalidate" triggers shown above, this collection might look as follows:¶

REQUEST:

  GET /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 341
  Expires: Wed, 04 May 2016 08:49:11 GMT
  Server: example-server/0.1
  ETag: "-936094426920308378"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:11 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "cdn-id": "AS64496:0",
      "coll-active": "/triggers/active",
      "coll-complete": "/triggers/complete",
      "coll-failed": "/triggers/failed",
      "coll-pending": "/triggers/pending",
      "staleresourcetime": 86400,
      "triggers": [
          "https://dcdn.example.com/triggers/0",
          "https://dcdn.example.com/triggers/1"
      ]
  }

10.2.2. Filtered Collections of Trigger Status Resources

The filtered collections are also available to the uCDN. Before the dCDN starts processing the two CI/T Trigger Commands shown above, both will appear in the collection of pending triggers. For example:¶

REQUEST:

  GET /triggers/pending HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 152
  Expires: Wed, 04 May 2016 08:49:11 GMT
  Server: example-server/0.1
  ETag: "4331492443626270781"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:11 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "staleresourcetime": 86400,
      "triggers": [
          "https://dcdn.example.com/triggers/0",
          "https://dcdn.example.com/triggers/1"
      ]
  }

At this point, if no other Trigger Status Resources had been created, the other filtered views would be empty. For example:¶

REQUEST:

  GET /triggers/complete HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 54
  Expires: Wed, 04 May 2016 08:49:11 GMT
  Server: example-server/0.1
  ETag: "7958041393922269003"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:11 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "staleresourcetime": 86400,
      "triggers": []
  }

10.2.3. Individual Trigger Status Resources

The Trigger Status Resources can also be examined for details about individual CI/T Trigger Commands. For example, for the CI/T "preposition" and "invalidate" commands from previous examples:¶

REQUEST:

  GET /triggers/0 HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 467
  Expires: Wed, 04 May 2016 08:49:10 GMT
  Server: example-server/0.1
  ETag: "6990548174277557683"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Type: application/cdni; ptype=ci-trigger-status.v2

  {
      "ctime": 1462351690,
      "etime": 1462351698,
      "mtime": 1462351690,
      "status": "pending",
      "trigger": {
          "action": "preposition",
          "specs": [
            {
               "trigger-subject": "metadata",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://metadata.example.com/a/b/c"
                  ]
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://www.example.com/a/b/c/1",
                     "https://www.example.com/a/b/c/2",
                     "https://www.example.com/a/b/c/3",
                     "https://www.example.com/a/b/c/4"
                  ]
               }
            }
         ]
      }
  }

REQUEST:

  GET /triggers/1 HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 545
  Expires: Wed, 04 May 2016 08:49:11 GMT
  Server: example-server/0.1
  ETag: "-554385204989405469"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:11 GMT
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  {
      "ctime": 1462351691,
      "etime": 1462351699,
      "mtime": 1462351691,
      "status": "pending",
      "trigger": {
          "action": "invalidate",
          "specs": [
            {
               "trigger-subject": "metadata",
               "generic-trigger-spec-type": "uri-pattern-match",
               "generic-trigger-spec-value": {
                  "pattern": "https://metadata.example.com/a/b/*"
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "urls",
               "generic-trigger-spec-value": {
                  "urls": [
                     "https://www.example.com/a/index.html"
                  ]
               }
            },
            {
               "trigger-subject": "content",
               "generic-trigger-spec-type": "uri-pattern-match",
               "generic-trigger-spec-value": {
                   "pattern": "https://www.example.com/a/b/*",
                   "case-sensitive": true
               }
            }
         ]
      }
  }

10.2.4. Polling for Changes in Status

The uCDN SHOULD use the ETags of collections or Trigger Status Resources when polling for changes in status, as shown in the following examples:¶

REQUEST:

  GET /triggers/pending HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*
  If-None-Match: "4331492443626270781"

RESPONSE:
   HTTP/1.1 304 Not Modified
   Content-Length: 0
   Expires: Wed, 04 May 2016 08:49:11 GMT
   Server: example-server/0.1
   ETag: "4331492443626270781"
   Cache-Control: max-age=60
   Date: Wed, 04 May 2016 08:48:11 GMT
   Content-Type: application/cdni; ptype=ci-trigger-collection

REQUEST:

  GET /triggers/0 HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*
  If-None-Match: "6990548174277557683"

RESPONSE:

  HTTP/1.1 304 Not Modified
  Content-Length: 0
  Expires: Wed, 04 May 2016 08:49:10 GMT
  Server: example-server/0.1
  ETag: "6990548174277557683"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Type: application/cdni; ptype=ci-trigger-status.v2

When the CI/T Trigger Command is complete, the contents of the filtered collections will be updated along with their ETags. For example, when the two example CI/T Trigger Commands are complete, the collections of pending and complete Trigger Status Resources might look like:¶

REQUEST:

  GET /triggers/pending HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 54
  Expires: Wed, 04 May 2016 08:49:15 GMT
  Server: example-server/0.1
  ETag: "1337503181677633762"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:15 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "staleresourcetime": 86400,
      "triggers": []
  }

REQUEST:

  GET /triggers/complete HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 152
  Expires: Wed, 04 May 2016 08:49:22 GMT
  Server: example-server/0.1
  ETag: "4481489539378529796"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:22 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "staleresourcetime": 86400,
      "triggers": [
          "https://dcdn.example.com/triggers/0",
          "https://dcdn.example.com/triggers/1"
      ]
  }

10.2.5. Deleting Trigger Status Resources

The uCDN can delete completed and failed Trigger Status Resources to reduce the size of the collections, as described in Section 5.4. For example, to delete the "preposition" request from earlier examples:¶

REQUEST:

  DELETE /triggers/0 HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 204 No Content
  Date: Wed, 04 May 2016 08:48:22 GMT
  Content-Length: 0
  Content-Type: text/html; charset=UTF-8
  Server: example-server/0.1

This would, for example, cause the collection of completed Trigger Status Resources shown in the example above to be updated to:¶

REQUEST:

  GET /triggers/complete HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: dcdn.example.com
  Accept: */*

RESPONSE:

  HTTP/1.1 200 OK
  Content-Length: 105
  Expires: Wed, 04 May 2016 08:49:22 GMT
  Server: example-server/0.1
  ETag: "-6938620031669085677"
  Cache-Control: max-age=60
  Date: Wed, 04 May 2016 08:48:22 GMT
  Content-Type: application/cdni; ptype=ci-trigger-collection

  {
      "staleresourcetime": 86400,
      "triggers": [
          "https://dcdn.example.com/triggers/1"
      ]
  }

10.2.6. Extensions with Error Propagation

In the following example a CI/T "preposition" command is using two extensions to control the way the trigger is executed. In this example the receiving dCDN, identified as "AS64500:0", does not support the first extension in the extensions array. dCDN "AS64500:0" further distributes this trigger to another downstream CDN that is identified as "AS64501:0", which does not support the second extension in the extensions array. The error is propagated from "AS64501:0" to "AS64500:0" and the errors.v2 array reflects both errors.¶

REQUEST:

  POST /triggers HTTP/1.1
  User-Agent: example-user-agent/0.1
  Host: triggers.dcdn.example.com
  Accept: */*
  Content-Type: application/cdni; ptype=ci-trigger-command.trigger.v2
  {
    "trigger": {
      "action": "preposition",
      "specs": [
        {
          "trigger-subject": "content",
          "generic-trigger-spec-type": "contentPlaylist",
          "generic-trigger-spec-value": {
            "playlist":
              "https://www.example.com/hls/title/index.m3u8",
            "media-protocol": "hls"
          }
        }
      ],
      "extensions": [
        {
          "generic-trigger-extension-type": "location-policy",
          "generic-trigger-extension-value": {
            "locations": [
              {
                "action": "allow",
                "footprints": [
                  {
                    "footprint-type": "countrycode",
                    "footprint-value": [
                      "us"
                    ]
                  }
                ]
              },
              {
                "action": "deny",
                "footprints": [
                  {
                    "footprint-type": "countrycode",
                    "footprint-value": [
                      "ca"
                    ]
                  }
                ]
              }
            ]
          },
          "mandatory-to-enforce": true,
          "safe-to-redistribute": true
        },
        {
          "generic-trigger-extension-type": "time-policy",
          "generic-trigger-extension-value": {
            "unix-time-window": {
              "start": 946717200,
              "end": 946746000
            }
          },
          "mandatory-to-enforce": true,
          "safe-to-redistribute": true
        }
      ]
    },
    "cdn-path": [ "AS64496:0" ]
  }

RESPONSE:

  HTTP/1.1 201 Created
  Date: Wed, 04 May 2016 08:48:10 GMT
  Content-Length: 467
  Content-Type: application/cdni; ptype=ci-trigger-status.v2
  Location: https://triggers.dcdn.example.com/triggers/0
  Server: example-server/0.1

  {
    "errors": [
      {
        "extensions": [
          {
            "generic-trigger-extension-type": "location-policy",
            "generic-trigger-extension-value": {
              "locations": [
                {
                  "action": "allow",
                  "footprints": [
                    {
                      "footprint-type": "countrycode",
                      "footprint-value": [
                        "us"
                      ]
                    }
                  ]
                },
                {
                  "action": "deny",
                  "footprints": [
                    {
                      "footprint-type": "countrycode",
                      "footprint-value": [
                        "ca"
                      ]
                    }
                  ]
                }
              ]
            },
            "mandatory-to-enforce": true,
            "safe-to-redistribute": true
          }
        ],
        "description": "unrecognized extension <type>",
        "error": "eextension",
        "cdn": "AS64500:0"
      },
      {
        "extensions": [
          {
            "generic-trigger-extension-type": "time-policy",
            "generic-trigger-extension-value": {
              "unix-time-window": {
                "start": 946717200,
                "end": 946746000
              }
            },
            "mandatory-to-enforce": true,
            "safe-to-redistribute": true
          }
        ],
        "description": "unrecognized extension <type>",
        "error": "eextension",
        "cdn": "AS64501:0"
      }
    ],
    "ctime": 1462351690,
    "etime": 1462351698,
    "mtime": 1462351690,
    "status": "failed",
    "trigger": { <content of trigger.v2 object from the command> }
  }

11.1.1. CDNI ci-trigger-command.trigger.v2 Payload Type

Purpose: The purpose of this payload type is to distinguish version 2 of the CI/T trigger command object (and any associated capability advertisement)¶

Interface: CI/T¶

Encoding: see Section 6.1.1¶

11.1.2. CDNI ci-trigger-command.cancel Payload Type

Purpose: The purpose of this payload type is to distinguish the CI/T cancel command object (and any associated capability advertisement)¶

Interface: CI/T¶

Encoding: see Section 6.1.2¶

11.1.3. CDNI ci-trigger-status.v2 Payload Type

Purpose: The purpose of this payload type is to distinguish version 2 of the CI/T status resource response object (and any associated capability advertisement)¶

Interface: CI/T¶

Encoding: see Section 6.1.3¶

11.1.4. CDNI FCI CI/T Payload Types