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

1.1. Terminology

This document reuses the terminology defined in [RFC6707] and uses "uCDN" and "dCDN" as shorthand for "upstream CDN" and "downstream CDN", respectively.¶

Additionally, the following terms are used throughout this document and are defined as follows:¶

• HLS - HTTP Live Streaming¶
• DASH - Dynamic Adaptive Streaming Over HTTP¶
• MSS - Microsoft Smooth Streaming¶

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

2.1. Timing of Triggered Activity

Timing of the execution of CI/T Commands is under the dCDN's control, including its start time and pacing of the activity in the network. Instructions regarding this timing may be included in the trigger using one of the Trigger Extension Objects defined in Section 8¶

CI/T "invalidate" and "purge" commands MUST be applied to all data acquired before the command was accepted by the dCDN. The dCDN SHOULD NOT apply CI/T "invalidate" and "purge" commands to data acquired after the CI/T Command was accepted, but this may not always be achievable, so the uCDN cannot count on that.¶

If the uCDN wishes to invalidate or purge content and then immediately pre-position replacement content at the same URLs, it SHOULD ensure that the dCDN has completed the invalidate/purge before initiating the pre-positioning. Otherwise, there is a risk that the dCDN pre-positions the new content, then immediately invalidates or purges it (as a result of the two uCDN requests running in parallel).¶

Because the CI/T Command timing is under the dCDN's control, the dCDN implementation can choose whether to apply CI/T "invalidate" and "purge" commands to content acquisition that has already started when the command is received.¶

2.2. Scope of Triggered Activity

Each CI/T Command can operate on multiple metadata and content elements, usually referred to by their URLs. These elements are targeted by specifying both their subject (i.e. "metadata" or "content") as well as specification method (e.g. URL Regexes) and value.¶

Multiple representations of an HTTP resource may share the same URL. CI/T Trigger Commands that invalidate or purge metadata or content apply to all resource representations with matching URLs.¶

2.3. Trigger Results

Possible states for a Trigger Status Resource are defined in Section 6.2.6.¶

The CI/T Trigger Command MUST NOT be reported as "complete" until all operations have been completed successfully. The reasons for failure, and URLs or patterns affected, SHOULD be enumerated in the Trigger Status Resource. For more details, see Section 5.7.¶

If a dCDN is also acting as a uCDN in a cascade, it MUST forward CI/T Commands to any dCDNs that may be affected. The CI/T Trigger Command MUST NOT be reported as "complete" in a CDN until it is "complete" in all of its dCDNs. If a CI/T Trigger Command is reported as "processed" in any dCDN, intermediate CDNs MUST NOT report "complete"; instead, they MUST also report "processed". A CI/T Command MAY be reported as "failed" as soon as it fails in a CDN or in any of its dCDNs. A canceled CI/T Trigger Command MUST be reported as "cancelling" until it has been reported as "cancelled", "complete", or "failed" by all dCDNs in a cascade.¶

3.1. Trigger Action

Trigger Action Type is used in a Trigger Specification to describe trigger action. It was initially referred to (at [RFC8007]) as "Trigger Type".¶

All trigger actions MUST be registered in the IANA "CDNI CI/T Trigger Types" registry (see Section 11.2).¶

A dCDN receiving a request containing a trigger action 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 "eunsupported".¶

The following trigger actions are defined by this document:¶

3.2. Trigger Spec

The CDNI Control Interface / Triggers 1st edition [RFC8007] defines a set of properties and objects used by the trigger commands in order to specify the targets the trigger is applied on. This document modifies the trigger interface so it has a list of trigger specs. Such structure improves the interface's extensibility and flexibility. Furthermore, the document defines a generic trigger spec object that act as a wrapper for managing individual CDNI trigger spec in an opaque manner, allowing future extension of the interface.¶

All trigger specs MUST be registered in the IANA "CDNI CI/T Trigger Specs" registry (see Section 11.3).¶

A dCDN receiving a request containing a trigger spec 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 "espec".¶

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

3.3. Trigger Extensibility

The CDNI Control Interface / Triggers 1st edition [RFC8007] defines a set of properties and objects used by the trigger commands. In this 2nd edition we define an extension mechanism to the triggers interface that enables applications to add instructions for finer control over the trigger execution, for example indicating a time window for the trigger to be executed. This document specifies a generic trigger extension object wrapper for managing individual CDNI trigger extensions in an opaque manner.¶

All trigger extensions are optional, and it is thus the responsibility of the extension specification to define a consistent default behavior for the case the extension is not present.¶

All trigger extensions MUST be registered in the IANA "CDNI CI/T Trigger Extensions" registry (see Section 11.6).¶

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

Example use cases¶

• Pre-position with cache location policy¶
• Purge content with cache location policy¶
• Pre-position at a specific time¶
• Purge by content acquisition time (e.g. purge all content acquired in the past X hours)¶

5.1. Creating Triggers

To issue a CI/T Command, the uCDN makes an HTTP POST to the dCDN's collection of all of the uCDN's Trigger Status Resources. The request body of that POST is a CI/T Command, as described in Section 6.1.1.¶

The dCDN validates the CI/T Command. If the command is malformed or the uCDN does not have sufficient access rights, the dCDN MUST either respond with an appropriate 4xx HTTP error code and not create a Trigger Status Resource or create a "failed" Trigger Status Resource containing an appropriate Error.v2 Description.¶

When a CI/T Trigger Command is accepted, the dCDN MUST create a new Trigger Status Resource that will convey a specification of the CI/T Command and its current status. The HTTP response to the uCDN MUST have status code 201 and MUST convey the URI of the Trigger Status Resource in the Location header field [RFC7231]. The HTTP response SHOULD include the content of the newly created Trigger Status Resource. This is particularly important in cases where the CI/T Trigger Command has completed immediately.¶

Once a Trigger Status Resource has been created, the dCDN MUST NOT reuse its URI, even after that Trigger Status Resource has been removed.¶

The dCDN SHOULD track and report on the progress of CI/T Trigger Commands using a Trigger Status Resource (Section 6.1.2). If the dCDN is not able to do that, it MUST indicate that it has accepted the request but will not be providing further status updates. To do this, it sets the status of the Trigger Status Resource to "processed". In this case, CI/T processing should continue as for a "complete" request, so the Trigger Status Resource MUST be added to the dCDN's collection of complete Trigger Status Resources. The dCDN SHOULD also provide an estimated completion time for the request by using the "etime" property of the Trigger Status Resource. This will allow the uCDN to schedule pre-positioning after an earlier delete of the same URLs is expected to have finished.¶

If the dCDN is able to track the execution of CI/T Commands and a CI/T Command is queued by the dCDN for later action, the "status" property of the Trigger Status Resource MUST be "pending". Once processing has started, the status MUST be "active". Finally, once the CI/T Command is complete, the status MUST be set to "complete" or "failed".¶

A CI/T Trigger Command may result in no activity in the dCDN if, for example, it is an "invalidate" or "purge" request for data the dCDN has not yet acquired, or a "preposition" request for data that it has already acquired and that is still valid. In this case, the status of the Trigger Status Resource MUST be "processed" or "complete", and the Trigger Status Resource MUST be added to the dCDN's collection of complete Trigger Status Resources.¶

Once created, Trigger Status Resources can be canceled or deleted by the uCDN, but not modified. The dCDN MUST reject PUT and POST requests from the uCDN to Trigger Status Resources by responding with an appropriate HTTP status code -- for example, 405 ("Method Not Allowed").¶

5.2. Checking Status

The uCDN has two ways to check the progress of CI/T Commands it has issued to the dCDN, as described in Sections Section 5.2.1 and Section 5.2.2.¶

To allow the uCDN to check for changes in the status of a Trigger Status Resource or collection of Trigger Status Resources without refetching the whole resource or collection, the dCDN SHOULD include entity-tags (ETags) for the uCDN to use as cache validators, as defined in [RFC7232].¶

The dCDN SHOULD use the cache control headers for responses to GETs for Trigger Status Resources and Collections to indicate the frequency at which it recommends that the uCDN should poll for change.¶

5.3. Canceling Triggers

The uCDN can request cancellation of a CI/T Trigger Command by POSTing a CI/T Cancel Command to the collection of all Trigger Status Resources.¶

The dCDN is required to accept and respond to the CI/T Cancel Command, but the actual cancellation of a CI/T Trigger Command is optional-to-implement.¶

The dCDN MUST respond to the CI/T Cancel Command appropriately -- for example, with HTTP status code 200 ("OK") if the cancellation has been processed and the CI/T Command is inactive, 202 ("Accepted") if the command has been accepted but the CI/T Command remains active, or 501 ("Not Implemented") if cancellation is not supported by the dCDN.¶

If cancellation of a "pending" Trigger Status Resource is accepted by the dCDN, the dCDN SHOULD NOT start the processing of that activity. Issuing a CI/T Cancel Command for a "pending" Trigger Status Resource does not, however, guarantee that the corresponding activity will not be started, because the uCDN cannot control the timing of that activity. Processing could, for example, start after the POST is sent by the uCDN but before that request is processed by the dCDN.¶

If cancellation of an "active" or "processed" Trigger Status Resource is accepted by the dCDN, the dCDN SHOULD stop processing the CI/T Command. However, as with cancellation of a "pending" CI/T Command, the dCDN does not guarantee this.¶

If the CI/T Command cannot be stopped immediately, the status in the corresponding Trigger Status Resource MUST be set to "cancelling", and the Trigger Status Resource MUST remain in the collection of Trigger Status Resources for active CI/T Commands. If processing is stopped before normal completion, the status value in the Trigger Status Resource MUST be set to "cancelled", and the Trigger Status Resource MUST be included in the collection of failed CI/T Trigger Commands.¶

Cancellation of a "complete" or "failed" Trigger Status Resource requires no processing in the dCDN. Its status MUST NOT be changed to "cancelled".¶

5.4. Deleting Triggers

The uCDN can delete Trigger Status Resources at any time, using the HTTP DELETE method. The effect is similar to cancellation, but no Trigger Status Resource remains afterwards.¶

Once deleted, the references to a Trigger Status Resource MUST be removed from all Trigger Status Resource collections. Subsequent requests to GET the deleted Trigger Status Resource SHOULD be rejected by the dCDN with an HTTP error.¶

If a "pending" Trigger Status Resource is deleted, the dCDN SHOULD NOT start the processing of that activity. Deleting a "pending" Trigger Status Resource does not, however, guarantee that it has not started, because the uCDN cannot control the timing of that activity. Processing may, for example, start after the DELETE is sent by the uCDN but before that request is processed by the dCDN.¶

If an "active" or "processed" Trigger Status Resource is deleted, the dCDN SHOULD stop processing the CI/T Command. However, as with deletion of a "pending" Trigger Status Resource, the dCDN does not guarantee this.¶

Deletion of a "complete" or "failed" Trigger Status Resource requires no processing in the dCDN other than deletion of the Trigger Status Resource.¶

5.5. Expiry of Trigger Status Resources

The dCDN can choose to automatically delete Trigger Status Resources some time after they become "complete", "processed", "failed", or "cancelled". In this case, the dCDN will remove the Trigger Status Resource and respond to subsequent requests for it with an HTTP error.¶

If the dCDN does remove Trigger Status Resources automatically, it MUST report the length of time after which it will do so, using a property of the collection of all Trigger Status Resources. It is¶

RECOMMENDED that Trigger Status Resources are not automatically deleted by the dCDN for at least 24 hours after they become "complete", "processed", "failed", or "cancelled".¶

To ensure that it is able to get the status of its Trigger Status Resources for completed and failed CI/T Commands, it is RECOMMENDED that the uCDN polling interval is less than the time after which records for completed activity will be deleted.¶

5.6. Loop Detection and Prevention

Given three CDNs, A, B, and C, if CDNs B and C delegate delivery of CDN A's content to each other, CDN A's CI/T Commands could be passed between CDNs B and C in a loop. More complex networks of CDNs could contain similar loops involving more hops.¶

In order to prevent and detect such CI/T loops, each CDN uses a CDN Provider ID (PID) to uniquely identify itself. In every CI/T Command it originates or cascades, each CDN MUST append an array element containing its CDN PID to a JSON array under an entry named "cdn-path". When receiving CI/T Commands, a dCDN MUST check the cdn-path and reject any CI/T Command that already contains its own CDN PID in the cdn-path. Transit CDNs MUST check the cdn-path and not cascade the CI/T Command to dCDNs that are already listed in the cdn-path.¶

The CDN PID consists of the two characters "AS" followed by the CDN provider's Autonomous System number [RFC1930], then a colon (":") and an additional qualifier that is used to guarantee uniqueness in case a particular AS has multiple independent CDNs deployed -- for example, "AS64496:0".¶

If the CDN provider has multiple ASes, the same AS number SHOULD be used in all messages from that CDN provider, unless there are multiple distinct CDNs.¶

If the CDNI Request Routing Redirection interface (RI) described in [RFC7975] is implemented by the dCDN, the CI/T interface and the RI SHOULD use the same CDN PID.¶

5.7. Error Handling

A dCDN can signal rejection of a CI/T Command using HTTP status codes -- for example, 400 ("Bad Request") if the request is malformed, or 403 ("Forbidden") or 404 ("Not Found") if the uCDN does not have permission to issue CI/T Commands or it is trying to act on another CDN's data.¶

If any part of the CI/T Trigger Command fails, the trigger SHOULD be reported as "failed" once its activity is complete or if no further errors will be reported. The "errors" property in the Trigger Status Resource will be used to enumerate which actions failed and the reasons for failure, and can be present while the Trigger Status Resource is still "pending" or "active", if the CI/T Trigger Command is still running for some URLs or patterns in the Trigger Specification.¶

Once a request has been accepted, processing errors are reported in the Trigger Status Resource using a list of Error.v2 Descriptions. Each Error.v2 Description is used to report errors against one or more of the URLs or patterns in the Trigger Specification.¶

If a Surrogate affected by a CI/T Trigger Command is offline in the dCDN or the dCDN is unable to pass a CI/T Command on to any of its cascaded dCDNs:¶

• If the CI/T Command is abandoned by the dCDN, the dCDN SHOULD report an error.¶
• A CI/T "invalidate" command may be reported as "complete" when Surrogates that may have the data are offline. In this case, Surrogates MUST NOT use the affected data without first revalidating it when they are back online.¶
• CI/T "preposition" and "purge" commands can be reported as "processed" if affected caches are offline and the activity will complete when they return to service.¶
• Otherwise, the dCDN SHOULD keep the Trigger Status Resource in state "pending" or "active" until either the CI/T Command is acted upon or the uCDN chooses to cancel it.¶

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/uCDN-A            | (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     [ ]                             |
[ ]<---------------------------[ ]                             |

6.1. CI/T Objects

The top-level objects defined by the CI/T interface are described in this section.¶

The encoding of values used by these objects is described in Section 6.2.¶

6.2. Properties of CI/T Objects

This section defines the values that can appear in the top-level objects described in Section 6.1, and their encodings.¶

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

}

{
  "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>
}

{
   "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"
},

{
  "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"
   },
  ]
}

7.1. URLs Spec

The urls spec type allows the uCDN to manage uCDN content or metadata objects held by the dCDN based on the objects' URLs.¶

Spec object specification¶

• Property: urls¶

  • Description: An array of URLs over which the trigger MUST be executed.¶
  • Value: A JSON array of URLs represented as JSON strings.¶
  • Mandatory: Yes.¶

Below is an example of a JSON serialized generic trigger spec object, matching the metadata at metadata.example.com/a/b/c.¶

{
   "trigger-subject": "metadata",
   "generic-trigger-spec-type": "urls",
   "generic-trigger-spec-value": {
      "urls": [
         "https://metadata.example.com/a/b/c"
      ]
   }
}

7.2. CCIDs Spec

The content-ccids spec type allows to specify the Content Collection IDentifier of content the trigger applies to. The "ccid" is a grouping of content, as defined at [RFC8006]. The ccid spec type is valid only for content spec subject.¶

Spec object specification¶

• Property: ccids¶

  • Description: An array of Content Collection IDentifiers over which the trigger MUST be executed.¶
  • Value: A JSON array of strings, where each string is a Content Collection IDentifier.¶
  • Mandatory: Yes.¶

7.3. URI Pattern Match Spec

The uri-pattern match spec type allows the uCDN to manage uCDN content or metadata objects held by the dCDN based on the objects' URI pattern. The value is a UriPatternMatch object, as defined in Section 7.3.1.¶

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

7.4. URI Regex Match Spec

The content-uri-regexes spec type allows the uCDN to manage content or metadata objects held by the dCDN based on the objects' URI regex.¶

"^(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
}

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

7.5. Content Playlist Spec

The content-playlist spec type allows the uCDN to manage content held by the dCDN based on the content's playlist. The content-playlist spec type is valid only for the content spec subject.¶

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

8.1. LocationPolicy extension

A content operation may be relevant for a specific geographical region, or need to be excluded from a specific region. In this case, the trigger should be applied only to parts of the network that are either "included" or "not excluded" by the location policy. Note that the restrictions here are on the cache location rather than the client location.¶

The LocationPolicy object defines which CDN or cache locations for which the trigger command is relevant.¶

Example use cases:¶

• Pre-position: Certain contracts allow for pre-positioning or availability of contract in all regions except for certain excluded regions in the world, including caches. For example, some content cannot ever knowingly touch servers in a specific country, including cached content. Therefore, these regions MUST be excluded from a pre-positioning operation.¶
• Purge: In certain cases, content may have been located on servers in regions where the content must not reside. In such cases, a purge operation to remove content specifically from that region is required.¶

Object specification¶

• Property: locations¶

  • Description: An Access List that allows or denies (blocks) the trigger execution per cache location.¶
  • Type: Array of LocationRule objects (see Section 4.2.2.1 of [RFC8006])¶
  • Mandatory: Yes.¶

If a location policy object is not listed within the trigger command, the default behavior is to execute the trigger in all available caches and locations of the dCDN.¶

The trigger command is allowed, or denied, for a specific cache location according to the action of the first location whose footprint matches against that cache's location. If two or more footprints overlap, the first footprint that matches against the cache's location determines the action a CDN MUST take. If the "locations" property is an empty list or if none of the listed footprints match the location of a specific cache location, then the result is equivalent to a "deny" action.¶

Following is an example of a JSON serialized generic trigger extension object containing a location policy object that allows the trigger execution in the US but blocks its execution in Canada:¶

{
   "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,
   "incomprehensible": false
}

8.2. TimePolicy Extension

A uCDN may wish to perform content management operations on the dCDN in a specific schedule. The TimePolicy extensions allows the uCDN to instruct the dCDN to execute the trigger command in a desired time window. For example, a content provider that wishes to pre-populate a new episode at off-peak time so that it would be ready on caches at prime time when the episode is released for viewing. A scheduled operation enables the uCDN to direct the dCDN in what time frame to execute the trigger.¶

A uCDN may wish to to schedule a trigger such that the dCDN will execute it in local time, as it is measured in each region. For example, a uCDN may wish the dCDN to pull the content at off-peak hours, between 2AM-4AM, however, as a CDN is distributed across multiple time zones, the UTC definition of 2AM depends on the actual location.¶

We define two alternatives for localized scheduling:¶

• Regional schedule: When used in conjunction with the Location Policy defined in Section 8.1, the uCDN can trigger separate commands for different geographical regions, for each region using a different schedule. This allows the uCDN to control the execution time per region.¶
• Local Time schedule: We introduce a "local time" version for Internet timestamps that follows the notation for local time as defined in Section 4.2.2 of [ISO8601]. When local time is used, that dCDN SHOULD execute the triggers at different absolute times, according the local time of each execution location.¶

Object specification¶

• Property: unix-time-window¶

  • Description: A UNIX epoch time window in which the trigger SHOULD be executed.¶
  • Type: TimeWindow object using UNIX epoch timestamps (see Section 4.2.3.2 of [RFC8006])¶
  • Mandatory: No, but exactly one of "unixEpochWindow", "utcWindow" or "localTimeWindow" MUST be present.¶

• Property: utc-window¶

  • Description: A UTC time window in which the trigger SHOULD be executed.¶
  • Type: UTCWindow object as defined in Section 8.2.1.¶
  • Mandatory: No, but exactly one of "unixEpochWindow", "utcWindow" or "localTimeWindow" MUST be present.¶

• Property: local-time-window¶

  • Description: A local time window. The dCDN SHOULD execute the trigger at the defined time frame, interpreted as the the local time per location.¶
  • Type: LocalTimeWindow object as defined in Section 8.2.2.¶
  • Mandatory: No, but exactly one of "unixEpochWindow", "utcWindow" or "localTimeWindow" MUST be present.¶

If a time policy object is not listed within the trigger command, the default behavior is to execute the trigger in a time frame most suitable to the dCDN taking under consideration other constrains and / or obligations.¶

Example of a JSON serialized generic trigger extension object containing a time policy object that schedules the trigger execution to a window between 09:00 01/01/2000 UTC and 17:00 01/01/2000 UTC, using the "unix-time-window" property:¶

{
   "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,
   "incomprehensible": false
}

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

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

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

date-fullyear   = 4DIGIT
date-month      = 2DIGIT  ; 01-12
date-mday       = 2DIGIT  ; 01-28, 01-29, 01-30, 01-31 based on
                          ; month/year
time-hour       = 2DIGIT  ; 00-23
time-minute     = 2DIGIT  ; 00-59
time-second     = 2DIGIT  ; 00-59 leap seconds are not supported

local-time      = time-hour ":" time-minute ":" time-second
full-date       = date-fullyear "-" date-month "-" date-mday
date-local-time = full-date "T" local-time

Month Number  Month/Year           Maximum value of date-mday
------------  ----------           --------------------------
01            January              31
02            February, normal     28
02            February, leap year  29
03            March                31
04            April                30
05            May                  31
06            June                 30
07            July                 31
08            August               31
09            September            30
10            October              31
11            November             30
12            December             31

10.1. Creating Triggers

Examples of the uCDN triggering activity in the dCDN:¶

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.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"
                  ]
               }
            }
         ]
      }
  }

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.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
               }
            }
         ]
      }
  }

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.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/0
  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> }
  }

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.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/0
  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. Examining Trigger Status

Once Trigger Status Resources have been created, the uCDN can check their status as shown in the following examples.¶

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.v2

  {
      "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"
      ]
  }

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.v2

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

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.v2

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

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
               }
            }
         ]
      }
  }

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.v2

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

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.v2

  {
      "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.v2

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

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

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.v2

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

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.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. CDNI Payload Type Parameter Registrations

The IANA is requested to register the following new Payload Types in the "CDNI Payload Types" registry defined by [RFC7736], for use with the "application/cdni" MIME media type.¶

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

11.2. "CDNI CI/T Trigger Types" Registry For Trigger Actions

In [RFC8007] the IANA was requested to create a new "CDNI CI/T Trigger Types" subregistry under the "Content Delivery Network Interconnection (CDNI) Parameters" registry.¶

Additions to the "CDNI CI/T Trigger Types" registry are made via the RFC Required policy as defined in [RFC8126].¶

The initial contents of the "CDNI CI/T Trigger Types" registry comprise the names and descriptions listed in section 5.2.2 of [RFC8007], with [RFC8007] acting as the specification.¶

In this second edition of the interface, trigger types are referred to as "trigger actions". The "Trigger Types" registery is used for further actions definitions. Furthermore, this document, and specifically Section 3.1, repeats the definitions of the trigger types from [RFC8007] as trigger actions, with no modification in the entities specification.¶

11.3. "CDNI CI/T Trigger Specs" Registry

The IANA is requested to create a new "CDNI CI/T Trigger Specs" subregistry in the "Content Delivery Networks Interconnection (CDNI) Parameters" registry. The "CDNI CI/T Trigger Specs" namespace defines the valid trigger targets' spec values in Section 3.2, used by the Trigger Spec object.¶

Additions to the "CDNI CI/T Trigger Specs" registry are made via the RFC Required policy as defined in [RFC8126].¶

The initial contents of the "CDNI CI/T Trigger Specs" registry comprise the names and descriptions listed in Section 3.2, with this document acting as the specification.¶

11.4. "CDNI CI/T Trigger Subjects" Registry

The IANA is requested to create a new "CDNI CI/T Trigger Subjects" subregistry in the "Content Delivery Networks Interconnection (CDNI) Parameters" registry. The "CDNI CI/T Trigger Subjects" namespace defines the valid trigger targets' subject values in Section 3.2.1, used by the Trigger Spec object.¶

Additions to the "CDNI CI/T Trigger Subjects" registry are made via the RFC Required policy as defined in [RFC8126].¶

The initial contents of the "CDNI CI/T Trigger Subjects" registry comprise the names and descriptions listed in Section 3.2.1, with this document acting as the specification.¶

11.5. CDNI CI/T Playlist Spec MediaProtocols

The IANA is requested to create a new "CDNI CI/T Playlist Spec MediaProtocols" subregistry in the "Content Delivery Networks Interconnection (CDNI) Parameters" registry. The "CDNI CI/T Playlist Spec MediaProtocols" namespace defines the valid trigger targets' extension values in Section 7.5.2, used by the Trigger Spec object.¶

Additions to the "CDNI Playlist Spec MediaProtocols" registry are made via the RFC Required policy as defined in [RFC8126].¶

The initial contents of the "CDNI CI/T Trigger Extensions" registry comprise the names and descriptions listed in Section 7.5.2, with this document acting as the specification.¶

11.6. "CDNI CI/T Trigger Extensions" Registry

The IANA is requested to create a new "CDNI CI/T Trigger Extensions" subregistry in the "Content Delivery Networks Interconnection (CDNI) Parameters" registry. The "CDNI CI/T Trigger Extensions" namespace defines the valid trigger targets' extension values in Section 3.3, used by the Trigger Spec object.¶

Additions to the "CDNI CI/T Trigger Extensions" registry are made via the RFC Required policy as defined in [RFC8126].¶

The initial contents of the "CDNI CI/T Trigger Extensions" registry comprise the names and descriptions listed in Section 3.3, with this document acting as the specification.¶

11.7. "CDNI CI/T Error Codes" Registry

In [RFC8007] the IANA was requested to create a new "CDNI CI/T Error Codes" subregistry under the "Content Delivery Network Interconnection (CDNI) Parameters" registry.¶

Additions to the "CDNI CI/T Error Codes" registry are made via the Specification Required policy as defined in [RFC8126]. The Designated Expert will verify that new Error Code registrations do not duplicate existing Error Code definitions (in name or functionality), prevent gratuitous additions to the namespace, and prevent any additions to the namespace that would impair the interoperability of CDNI implementations.¶

The initial contents of the "CDNI CI/T Error Codes" registry comprise the names and descriptions of the Error Codes listed in Section 5.2.7 of [RFC8007], with [RFC8007] acting as the specification.¶

In this second edition of the interface, we repeat the definion of the defined errors, with no modification of the entities specification. Additionally, the IANA is requested to register three additional error codes, "espec", "esubject" and "eextension", with specification as defined at Section 6.2.6.1.¶

12.1. Authentication, Authorization, Confidentiality, Integrity Protection

A CI/T implementation MUST support Transport Layer Security (TLS) transport for HTTP (HTTPS) as per [RFC2818] and [RFC7230].¶

TLS MUST be used by the server side (dCDN) and the client side (uCDN) of the CI/T interface, including authentication of the remote end, unless alternate methods are used for ensuring the security of the information in the CI/T interface requests and responses (such as setting up an IPsec tunnel between the two CDNs or using a physically secured internal network between two CDNs that are owned by the same corporate entity).¶

The use of TLS for transport of the CI/T interface allows the dCDN and the uCDN to authenticate each other using TLS client authentication and TLS server authentication.¶

Once the dCDN and the uCDN have mutually authenticated each other, TLS allows:¶

• The dCDN and the uCDN to authorize each other (to ensure that they are receiving CI/T Commands from, or reporting status to, an authorized CDN).¶
• CDNI commands and responses to be transmitted with confidentiality.¶
• Protection of the integrity of CDNI commands and responses.¶

When TLS is used, the general TLS usage guidance in [RFC7525] MUST be followed.¶

The mechanisms for access control are dCDN-specific and are not standardized as part of this CI/T specification.¶

HTTP requests that attempt to access or operate on CI/T data belonging to another CDN MUST be rejected using, for example, HTTP 403 ("Forbidden") or 404 ("Not Found"). This is intended to prevent unauthorized users from generating unnecessary load in dCDNs or uCDNs due to revalidation, reacquisition, or unnecessary acquisition.¶

When deploying a network of interconnected CDNs, the possible inefficiencies related to the diamond configuration discussed in Section 2.2.1 should be considered.¶

12.2. Denial of Service

This document does not define a specific mechanism to protect against Denial-of-Service (DoS) attacks on the CI/T interface. However, CI/T endpoints can be protected against DoS attacks through the use of TLS transport and/or via mechanisms outside the scope of the CI/T interface, such as firewalling or the use of Virtual Private Networks (VPNs).¶

Depending on the implementation, triggered activity may consume significant processing and bandwidth in the dCDN. A malicious or faulty uCDN could use this to generate unnecessary load in the dCDN. The dCDN should consider mechanisms to avoid overload -- for example, by rate-limiting acceptance or processing of CI/T Commands, or by performing batch processing.¶

12.3. Privacy

The CI/T protocol does not carry any information about individual end users of a CDN; there are no privacy concerns for end users.¶

The CI/T protocol does carry information that could be considered commercially sensitive by CDN operators and content owners. The use of mutually authenticated TLS to establish a secure session for the transport of CI/T data, as discussed in Section 12.1, provides confidentiality while the CI/T data is in transit and prevents parties other than the authorized dCDN from gaining access to that data. The dCDN MUST ensure that it only exposes CI/T data related to a uCDN to clients it has authenticated as belonging to that uCDN.¶