draft-ietf-cdni-control-triggers-09.txt   draft-ietf-cdni-control-triggers-10.txt 
Network Working Group R. Murray Network Working Group R. Murray
Internet-Draft B. Niven-Jenkins Internet-Draft B. Niven-Jenkins
Intended status: Standards Track Velocix (Alcatel-Lucent) Intended status: Standards Track Velocix (Alcatel-Lucent)
Expires: April 18, 2016 October 16, 2015 Expires: June 8, 2016 December 6, 2015
CDNI Control Interface / Triggers CDNI Control Interface / Triggers
draft-ietf-cdni-control-triggers-09 draft-ietf-cdni-control-triggers-10
Abstract Abstract
This document describes the part of the CDN Interconnection Control This document describes the part of the CDN Interconnection Control
Interface that allows a CDN to trigger activity in an interconnected Interface that allows a CDN to trigger activity in an interconnected
CDN that is configured to deliver content on its behalf. The CDN that is configured to deliver content on its behalf. The
upstream CDN can use this mechanism to request that the downstream upstream CDN can use this mechanism to request that the downstream
CDN pre-positions metadata or content, or that it invalidates or CDN pre-positions metadata or content, or that it invalidates or
purges metadata or content. The upstream CDN can monitor the status purges metadata or content. The upstream CDN can monitor the status
of activity that it has triggered in the downstream CDN. of activity that it has triggered in the downstream CDN.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 18, 2016. This Internet-Draft will expire on June 8, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 48 skipping to change at page 2, line 48
5.1.2. Trigger Status Resource . . . . . . . . . . . . . . . 16 5.1.2. Trigger Status Resource . . . . . . . . . . . . . . . 16
5.1.3. Trigger Collection . . . . . . . . . . . . . . . . . 17 5.1.3. Trigger Collection . . . . . . . . . . . . . . . . . 17
5.2. Properties of CI/T Objects . . . . . . . . . . . . . . . 18 5.2. Properties of CI/T Objects . . . . . . . . . . . . . . . 18
5.2.1. Trigger Specification . . . . . . . . . . . . . . . . 19 5.2.1. Trigger Specification . . . . . . . . . . . . . . . . 19
5.2.2. Trigger Type . . . . . . . . . . . . . . . . . . . . 20 5.2.2. Trigger Type . . . . . . . . . . . . . . . . . . . . 20
5.2.3. Trigger Status . . . . . . . . . . . . . . . . . . . 21 5.2.3. Trigger Status . . . . . . . . . . . . . . . . . . . 21
5.2.4. PatternMatch . . . . . . . . . . . . . . . . . . . . 21 5.2.4. PatternMatch . . . . . . . . . . . . . . . . . . . . 21
5.2.5. Absolute Time . . . . . . . . . . . . . . . . . . . . 22 5.2.5. Absolute Time . . . . . . . . . . . . . . . . . . . . 22
5.2.6. Error Description . . . . . . . . . . . . . . . . . . 22 5.2.6. Error Description . . . . . . . . . . . . . . . . . . 22
5.2.7. Error Code . . . . . . . . . . . . . . . . . . . . . 23 5.2.7. Error Code . . . . . . . . . . . . . . . . . . . . . 23
5.3. Formalization of the JSON Data . . . . . . . . . . . . . 23 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.1. Creating Triggers . . . . . . . . . . . . . . . . . . . . 24
6.1. Creating Triggers . . . . . . . . . . . . . . . . . . . . 25 6.1.1. Preposition . . . . . . . . . . . . . . . . . . . . . 24
6.1.1. Preposition . . . . . . . . . . . . . . . . . . . . . 25 6.1.2. Invalidate . . . . . . . . . . . . . . . . . . . . . 25
6.1.2. Invalidate . . . . . . . . . . . . . . . . . . . . . 27 6.2. Examining Trigger Status . . . . . . . . . . . . . . . . 27
6.2.1. Collection of All Triggers . . . . . . . . . . . . . 27
6.2. Examining Trigger Status . . . . . . . . . . . . . . . . 28 6.2.2. Filtered Collections of Trigger Status Resources . . 28
6.2.1. Collection of All Triggers . . . . . . . . . . . . . 28 6.2.3. Individual Trigger Status Resources . . . . . . . . . 29
6.2.2. Filtered Collections of Trigger Status Resources . . 29 6.2.4. Polling for Change . . . . . . . . . . . . . . . . . 31
6.2.3. Individual Trigger Status Resources . . . . . . . . . 31 6.2.5. Deleting Trigger Status Resources . . . . . . . . . . 34
6.2.4. Polling for Change . . . . . . . . . . . . . . . . . 33 6.2.6. Error Reporting . . . . . . . . . . . . . . . . . . . 35
6.2.5. Deleting Trigger Status Resources . . . . . . . . . . 36 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
6.2.6. Error Reporting . . . . . . . . . . . . . . . . . . . 38 7.1. CDNI Payload Type Parameter Registrations . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 8. Security Considerations . . . . . . . . . . . . . . . . . . . 37
7.1. CDNI Payload Type Parameter Registrations . . . . . . . . 39
8. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8.1. Authentication, Authorization, Confidentiality, Integrity 8.1. Authentication, Authorization, Confidentiality, Integrity
Protection . . . . . . . . . . . . . . . . . . . . . . . 40 Protection . . . . . . . . . . . . . . . . . . . . . . . 37
8.2. Denial of Service . . . . . . . . . . . . . . . . . . . . 40 8.2. Denial of Service . . . . . . . . . . . . . . . . . . . . 38
8.3. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 41 8.3. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 39
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
10.1. Normative References . . . . . . . . . . . . . . . . . . 41 10.1. Normative References . . . . . . . . . . . . . . . . . . 39
10.2. Informative References . . . . . . . . . . . . . . . . . 42 10.2. Informative References . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Appendix A. Formalization of the JSON Data . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
[RFC6707] introduces the problem scope for CDN Interconnection (CDNI) [RFC6707] introduces the problem scope for CDN Interconnection (CDNI)
and lists the four categories of interfaces that may be used to and lists the four categories of interfaces that may be used to
compose a CDNI solution (Control, Metadata, Request Routing, compose a CDNI solution (Control, Metadata, Request Routing,
Logging). Logging).
[RFC7336] expands on the information provided in [RFC6707] and [RFC7336] expands on the information provided in [RFC6707] and
describes each of the interfaces and the relationships between them describes each of the interfaces and the relationships between them
skipping to change at page 4, line 7 skipping to change at page 4, line 7
o Section 3 describes collections of Trigger Status Resources. o Section 3 describes collections of Trigger Status Resources.
o Section 4 defines the web service provided by the dCDN. o Section 4 defines the web service provided by the dCDN.
o Section 5 lists properties of CI/T Commands and Status Resources. o Section 5 lists properties of CI/T Commands and Status Resources.
o Section 6 contains example messages. o Section 6 contains example messages.
1.1. Terminology 1.1. Terminology
This document reuses the terminology defined in [RFC6707]. This document reuses the terminology defined in [RFC6707] and uses
"uCDN" and "dCDN" as shorthand for "Upstream CDN" and "Downstream
CDN", respectively.
2. Model for CDNI Triggers 2. Model for CDNI Triggers
A CI/T Command, sent from the uCDN to the dCDN, is a request for the A CI/T Command, sent from the uCDN to the dCDN, is a request for the
dCDN to do some work relating to data associated with content dCDN to do some work relating to data associated with content
requests originating from the uCDN. requests originating from the uCDN.
There are two types of CI/T Command, CI/T Trigger Commands and CI/T There are two types of CI/T Command: CI/T Trigger Commands, and CI/T
Cancel Commands. The CI/T Cancel Command can be used to request Cancel Commands. The CI/T Cancel Command can be used to request
cancellation of an earlier CI/T Trigger Command. A CI/T Trigger cancellation of an earlier CI/T Trigger Command. A CI/T Trigger
Command is of one of the following types: Command is of one of the following types:
o preposition - used to instruct the dCDN to fetch metadata from the o preposition - used to instruct the dCDN to fetch metadata from the
uCDN, or content from any origin including the uCDN. uCDN, or content from any origin including the uCDN.
o invalidate - used to instruct the dCDN to revalidate specific o invalidate - used to instruct the dCDN to revalidate specific
metadata or content before re-using it. metadata or content before re-using it.
skipping to change at page 9, line 17 skipping to change at page 9, line 17
are purely illustrative and are not intended to impose a definitive are purely illustrative and are not intended to impose a definitive
structure on CI/T interface implementations. structure on CI/T interface implementations.
4.1. Creating Triggers 4.1. Creating Triggers
To issue a CI/T Command, the uCDN makes an HTTP POST to the dCDN's 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 collection of all of the uCDN's Trigger Status Resources. The
request body of that POST is a CI/T Command, as described in request body of that POST is a CI/T Command, as described in
Section 5.1.1. Section 5.1.1.
The dCDN validates the CI/T Command, if it is malformed or the uCDN The dCDN validates the CI/T Command. If the command is malformed or
does not have sufficient access rights it MUST either respond with an the uCDN does not have sufficient access rights, the dCDN MUST either
appropriate 4xx HTTP error code and a Trigger Status Resource MUST respond with an appropriate 4xx HTTP error code and not create a
NOT be created on the dCDN, or create a 'failed' Trigger Status Trigger Status Resource, or create a 'failed' Trigger Status Resource
Resource containing an appropriate error description. containing an appropriate error description.
When a CI/T Trigger Command is accepted, the uCDN MUST create a new When a CI/T Trigger Command is accepted, the uCDN MUST create a new
Trigger Status Resource which will convey a specification of the CI/T Trigger Status Resource which will convey a specification of the CI/T
Command and its current status. The HTTP response to the dCDN MUST Command and its current status. The HTTP response to the dCDN MUST
have status code 201 and MUST convey the URI of the Trigger Status have status code 201 and MUST convey the URI of the Trigger Status
Resource in the Location header field. The HTTP response SHOULD Resource in the Location header field. The HTTP response SHOULD
include the content of the newly created Trigger Status Resource, include the content of the newly created Trigger Status Resource.
this is recommended particularly in cases where the CI/T Trigger This is particularly important in cases where the CI/T Trigger
Command has completed immediately. Command has completed immediately.
Once a Trigger Status Resource has been created the dCDN MUST NOT re- Once a Trigger Status Resource has been created the dCDN MUST NOT re-
use its URI, even after that Trigger Status Resource has been use its URI, even after that Trigger Status Resource has been
removed. removed.
The dCDN SHOULD track and report on progress of CI/T Trigger The dCDN SHOULD track and report on progress of CI/T Trigger
Commands. If the dCDN is not able to do that, it MUST indicate that Commands. 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 it has accepted the request but will not be providing further status
updates. To do this, it sets the "status" of the Trigger Status updates. To do this, it sets the "status" of the Trigger Status
skipping to change at page 10, line 27 skipping to change at page 10, line 27
requests from the uCDN to Trigger Status Resources by responding with requests from the uCDN to Trigger Status Resources by responding with
an appropriate HTTP status code, for example 405 "Method Not an appropriate HTTP status code, for example 405 "Method Not
Allowed". Allowed".
4.2. Checking Status 4.2. Checking Status
The uCDN has two ways to check progress of CI/T Commands it has The uCDN has two ways to check progress of CI/T Commands it has
issued to the dCDN, described in sections Section 4.2.1 and issued to the dCDN, described in sections Section 4.2.1 and
Section 4.2.2. Section 4.2.2.
To check for change in status of a Trigger Status Resource or To allow the uCDN to check for change in status of a Trigger Status
collection of Trigger Status Resources without re-fetching the whole Resource or collection of Trigger Status Resources without re-
Resource or Collection, Entity Tags SHOULD be included by the dCDN fetching the whole Resource or Collection, the dCDN SHOULD include
for the uCDN to use as cache validators, as defined in [RFC7232]. Entity Tags for the uCDN to use as cache validators, as defined in
[RFC7232].
The dCDN SHOULD use the cache control headers for responses to GETs The dCDN SHOULD use the cache control headers for responses to GETs
for Trigger Status Resources and Collections to indicate the for Trigger Status Resources and Collections to indicate the
frequency at which it recommends the uCDN should poll for change. frequency at which it recommends the uCDN should poll for change.
4.2.1. Polling Trigger Status Resource collections 4.2.1. Polling Trigger Status Resource collections
The uCDN can fetch the collection of its Trigger Status Resources, or The uCDN can fetch the collection of its Trigger Status Resources, or
filtered views of that collection. filtered views of that collection.
skipping to change at page 11, line 24 skipping to change at page 11, line 24
When polling in this way, the uCDN SHOULD use HTTP Entity Tags to When polling in this way, the uCDN SHOULD use HTTP Entity Tags to
monitor for change, rather than repeatedly fetching the Trigger monitor for change, rather than repeatedly fetching the Trigger
Status Resource. Status Resource.
4.3. Cancelling Triggers 4.3. Cancelling Triggers
The uCDN can request cancellation of a CI/T Trigger Command by 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 POSTing a CI/T Cancel Command to the collection of all Trigger Status
Resources. Resources.
Cancellation of a CI/T Trigger Command is optional-to-implement in The dCDN is required to accept and respond to the CI/T Cancel
the dCDN. 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 The dCDN MUST respond to the CI/T Cancel Command appropriately, for
example with HTTP status code 200 "OK" if the cancellation has been example with HTTP status code 200 "OK" if the cancellation has been
processed and the CI/T Command is inactive, 202 "Accepted" if the 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 command has been accepted but the CI/T Command remains active, or 501
"Not Implemented" if cancellation is not supported by the dCDN. "Not Implemented" if cancellation is not supported by the dCDN.
If cancellation of a "pending" Trigger Status Resource is accepted by If cancellation of a "pending" Trigger Status Resource is accepted by
the dCDN, the dCDN SHOULD NOT start processing of that activity. the dCDN, the dCDN SHOULD NOT start processing of that activity.
Issuing a CT/T cancel command for a "pending" Trigger Status Resource Issuing a CT/T Cancel Command for a "pending" Trigger Status Resource
does not however guarantee that the corresponding activity will not does not however guarantee that the corresponding activity will not
be started, because the uCDN cannot control the timing of that be started, because the uCDN cannot control the timing of that
activity. Processing could, for example, start after the POST is activity. Processing could, for example, start after the POST is
sent by the uCDN but before that request is processed by the dCDN. sent by the uCDN but before that request is processed by the dCDN.
If cancellation of an "active" or "processed" Trigger Status Resource If cancellation of an "active" or "processed" Trigger Status Resource
is accepted by the dCDN, the dCDN SHOULD stop processing the CI/T is accepted by the dCDN, the dCDN SHOULD stop processing the CI/T
Command. However, as with cancellation of a "pending" CI/T Command, Command. However, as with cancellation of a "pending" CI/T Command,
the dCDN does not guarantee this. the dCDN does not guarantee this.
skipping to change at page 14, line 35 skipping to change at page 14, line 35
o CI/T "preposition" and "purge" commands can be reported as o CI/T "preposition" and "purge" commands can be reported as
"processed" if affected caches are offline and the activity will "processed" if affected caches are offline and the activity will
complete when they return to service. complete when they return to service.
o Otherwise, the dCDN SHOULD keep the Trigger Status Resource in o Otherwise, the dCDN SHOULD keep the Trigger Status Resource in
state "pending" or "active" until the CI/T Command is acted upon, state "pending" or "active" until the CI/T Command is acted upon,
or the uCDN chooses to cancel it. or the uCDN chooses to cancel it.
4.8. Content URLs 4.8. Content URLs
Therefore, if content URLs are transformed by an intermediate CDN in If content URLs are transformed by an intermediate CDN in a cascade,
a cascade, that intermediate CDN MUST transform URLs in CI/T Commands that intermediate CDN MUST transform URLs in CI/T Commands it passes
it passes to its dCDN. to its dCDN.
When processing Trigger Specifications, CDNs MUST ignore the URL When processing Trigger Specifications, CDNs MUST ignore the URL
scheme (http or https) in comparing URLs. For example, for a CI/T scheme (http or https) in comparing URLs. For example, for a CI/T
invalidate or purge command, content MUST be invalidated or purged invalidate or purge command, content MUST be invalidated or purged
regardless of the protocol clients use to request it. regardless of the protocol clients use to request it.
5. CI/T Object Properties and Encoding 5. CI/T Object Properties and Encoding
CI/T Commands, Trigger Status Resources and Trigger Collections and CI/T Commands, Trigger Status Resources and Trigger Collections and
their properties are encoded using JSON, as defined in sections their properties are encoded using JSON, as defined in sections
skipping to change at page 21, line 31 skipping to change at page 21, line 31
| | cases where completion cannot be confirmed). | | | cases where completion cannot be confirmed). |
| failed | The CI/T Trigger Command could not be completed. | | failed | The CI/T Trigger Command could not be completed. |
| cancelling | Processing of the CI/T Trigger Command is still in | | cancelling | Processing of the CI/T Trigger Command is still in |
| | progress, but the CI/T Trigger Command has been | | | progress, but the CI/T Trigger Command has been |
| | cancelled by the uCDN. | | | cancelled by the uCDN. |
| cancelled | The CI/T Trigger Command was cancelled by the uCDN. | | cancelled | The CI/T Trigger Command was cancelled by the uCDN. |
+------------+------------------------------------------------------+ +------------+------------------------------------------------------+
5.2.4. PatternMatch 5.2.4. PatternMatch
A Pattern Match consists of a string pattern to match, and flags A Pattern Match consists of a string pattern to match against a URI,
describing the type of match. and flags describing the type of match.
It is encoded as a JSON object with the following name/value pairs: It is encoded as a JSON object with the following name/value pairs:
Name: pattern Name: pattern
Description: A pattern for string matching. Description: A pattern for URI matching.
Value: A JSON string representing the pattern. The pattern may Value: A JSON string representing the pattern. The pattern may
contain the wildcards * and ?, where * matches any sequence of contain the wildcards * and ?, where * matches any sequence of
characters (including the empty string) and ? matches exactly characters (including the empty string) and ? matches exactly
one character. The three literals "\" , "*" and "?" MUST be one character. The three literals "\" , "*" and "?" MUST be
escaped as "\\", "\*" and "\?". escaped as "\\", "\*" and "\?".
Mandatory: Yes. Mandatory: Yes.
Name: case-sensitive Name: case-sensitive
Description: Flag indicating whether or not case-sensitive Description: Flag indicating whether or not case-sensitive
matching should be used. matching should be used.
Value: One of the JSON values 'true' or 'false'. Value: One of the JSON values 'true' (the matching is case-
sensitive) or 'false' (the matching is case-insensitive).
Mandatory: No, default is case-insensitive match. Mandatory: No, default is case-insensitive match.
Name: match-query-string Name: match-query-string
Description: Flag indicating whether or not the query string Description: Flag indicating whether or not the query part of
should be included in the pattern match. the URI should be included in the pattern match.
Value: One of the JSON values 'true' or 'false'. 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 not to include the query string in Mandatory: No, default is 'false', the query part of the URI
the pattern match. should be dropped before comparison with the given pattern.
Example of case-sensitive prefix match against Example of case-sensitive prefix match against
"http://www.example.com/trailers/": "http://www.example.com/trailers/":
{ {
"pattern": "http://www.example.com/trailers/*", "pattern": "http://www.example.com/trailers/*",
"case-sensitive": true "case-sensitive": true
} }
5.2.5. Absolute Time 5.2.5. Absolute Time
A JSON number, seconds since the UNIX epoch. A JSON number, seconds since the UNIX epoch, 00:00:00 UTC on 1
January 1970.
5.2.6. Error Description 5.2.6. Error Description
An Error Description is used to report failure of a CI/T Command, or An Error Description is used to report failure of a CI/T Command, or
in the activity it triggered. It is encoded as a JSON object with in the activity it triggered. It is encoded as a JSON object with
the following name/value pairs: the following name/value pairs:
Name: error Name: error
Value: Error Code, as defined in Section 5.2.7. Value: Error Code, as defined in Section 5.2.7.
skipping to change at page 23, line 46 skipping to change at page 24, line 5
| | CDN). | | | CDN). |
| ereject | The dCDN is not willing to fulfil the CI/T Command | | ereject | The dCDN is not willing to fulfil the CI/T Command |
| | (for example, a preposition request for content at a | | | (for example, a preposition request for content at a |
| | time when the dCDN would not accept Request Routing | | | time when the dCDN would not accept Request Routing |
| | requests from the uCDN). | | | requests from the uCDN). |
| ecdn | An internal error in the dCDN or one of its | | ecdn | An internal error in the dCDN or one of its |
| | downstream CDNs. | | | downstream CDNs. |
| ecancelled | The uCDN cancelled the request. | | ecancelled | The uCDN cancelled the request. |
+------------+------------------------------------------------------+ +------------+------------------------------------------------------+
5.3. Formalization of the JSON Data
The JSON data described in this document has been formalised using
CDDL [I-D.greevenbosch-appsawg-cbor-cddl] as follows:
CIT-object = CIT-command / Trigger-Status-Resource / Trigger-Collection
CIT-command ; use media type application/cdni; ptype=ci-trigger-command
= {
? trigger: Triggerspec
? cancel: [* URI]
cdn-path: [* Cdn-PID]
}
Trigger-Status-Resource ; application/cdni; ptype=ci-trigger-status
= {
trigger: Triggerspec
ctime: Absolute-Time
mtime: Absolute-Time
? etime: Absolute-Time
status: Trigger-Status
? errors: [* Error-Description]
}
Trigger-Collection ; application/cdni; ptype=ci-trigger-collection
= {
triggers: [* URI]
? staleresourcetime: int ; time in seconds
? coll-all: URI
? coll-pending: URI
? coll-active: URI
? coll-complete: URI
? coll-failed: URI
? cdn-id: Cdn-PID
}
Triggerspec = { ; 5.2.1
type: Trigger-Type
? metadata.urls: [* URI]
? content.urls: [* URI]
? content.ccid: [* Ccid]
? metadata.patterns: [* Pattern-Match]
? content.patterns: [* Pattern-Match]
}
Trigger-Type = "preposition" / "invalidate" / "purge" ; 5.2.2
Trigger-Status = "pending" / "active" / "complete" / "processed"
/ "failed" / "cancelling" / "cancelled" ; 5.2.3
Pattern-Match = { ; 5.2.4
pattern: tstr
? case-sensitive: bool
? match-query-string: bool
}
Absolute-Time = number ; seconds since UNIX epoch, 5.2.5
Error-Description = { ; 5.2.6
error: Error-Code
? metadata.urls: [* URI]
? content.urls: [* URI]
? metadata.patterns: [* Pattern-Match]
? content.patterns: [* Pattern-Match]
? description: tstr
}
Error-Code = "emeta" / "econtent" / "eperm" / "ereject"
/ "ecdn" / "ecancelled" ; 5.2.7
Ccid = tstr ; see I-D.ietf-cdni-metadata
Cdn-PID = tstr .regexp "AS[0-9]+:[0-9]+"
URI = tstr
6. Examples 6. Examples
The following sections provide examples of different CI/T objects The following sections provide examples of different CI/T objects
encoded as JSON. encoded as JSON.
Discovery of the triggers interface is out of scope of this document. Discovery of the triggers interface is out of scope of this document.
In an implementation, all CI/T URLs are under the control of the In an implementation, all CI/T URLs are under the control of the
dCDN. The uCDN MUST NOT attempt to ascribe any meaning to individual dCDN. The uCDN MUST NOT attempt to ascribe any meaning to individual
elements of the path. elements of the path.
skipping to change at page 26, line 25 skipping to change at page 25, line 4
"metadata.urls" : [ "http://metadata.example.com/a/b/c" ], "metadata.urls" : [ "http://metadata.example.com/a/b/c" ],
"content.urls" : [ "content.urls" : [
"http://www.example.com/a/b/c/1", "http://www.example.com/a/b/c/1",
"http://www.example.com/a/b/c/2", "http://www.example.com/a/b/c/2",
"http://www.example.com/a/b/c/3", "http://www.example.com/a/b/c/3",
"http://www.example.com/a/b/c/4" "http://www.example.com/a/b/c/4"
] ]
}, },
"cdn-path" : [ "AS64496:1" ] "cdn-path" : [ "AS64496:1" ]
} }
RESPONSE: RESPONSE:
HTTP/1.1 201 Created HTTP/1.1 201 Created
Date: Sun, 31 Aug 2014 09:53:18 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Length: 472 Content-Length: 462
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
Location: http://dcdn.example.com/triggers/0 Location: http://dcdn.example.com/triggers/0
Server: example-server/0.1 Server: example-server/0.1
{ {
"ctime": 1409478798, "ctime": 1449422326,
"etime": 1409478806, "etime": 1449422334,
"mtime": 1409478798, "mtime": 1449422326,
"status": "pending", "status": "pending",
"trigger": { "trigger": {
"content.urls": [ "content.urls": [
"http://www.example.com/a/b/c/1", "http://www.example.com/a/b/c/1",
"http://www.example.com/a/b/c/2", "http://www.example.com/a/b/c/2",
"http://www.example.com/a/b/c/3", "http://www.example.com/a/b/c/3",
"http://www.example.com/a/b/c/4" "http://www.example.com/a/b/c/4"
], ],
"metadata.urls": [ "metadata.urls": [
"http://metadata.example.com/a/b/c" "http://metadata.example.com/a/b/c"
skipping to change at page 27, line 47 skipping to change at page 26, line 25
"case-sensitive" : true "case-sensitive" : true
} }
] ]
}, },
"cdn-path" : [ "AS64496:1" ] "cdn-path" : [ "AS64496:1" ]
} }
RESPONSE: RESPONSE:
HTTP/1.1 201 Created HTTP/1.1 201 Created
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Length: 551 Content-Length: 542
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
Location: http://dcdn.example.com/triggers/1 Location: http://dcdn.example.com/triggers/1
Server: example-server/0.1 Server: example-server/0.1
{ {
"ctime": 1409478799, "ctime": 1449422326,
"etime": 1409478807, "etime": 1449422334,
"mtime": 1409478799, "mtime": 1449422326,
"status": "pending", "status": "pending",
"trigger": { "trigger": {
"content.patterns": [ "content.patterns": [
{ {
"case-sensitive": true, "case-sensitive": true,
"pattern": "http://www.example.com/a/b/*" "pattern": "http://www.example.com/a/b/*"
} }
], ],
"content.urls": [ "content.urls": [
"http://www.example.com/a/index.html" "http://www.example.com/a/index.html"
skipping to change at page 29, line 15 skipping to change at page 27, line 30
REQUEST: REQUEST:
GET /triggers HTTP/1.1 GET /triggers HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 347 Content-Length: 339
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-6516741166528256414" ETag: "-8770885545613447380"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"cdn-id": "AS64496:0", "cdn-id": "AS64496:0",
"coll-active": "/triggers/active", "coll-active": "/triggers/active",
"coll-complete": "/triggers/complete", "coll-complete": "/triggers/complete",
"coll-failed": "/triggers/failed", "coll-failed": "/triggers/failed",
"coll-pending": "/triggers/pending", "coll-pending": "/triggers/pending",
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [ "triggers": [
skipping to change at page 30, line 15 skipping to change at page 28, line 21
REQUEST: REQUEST:
GET /triggers/pending HTTP/1.1 GET /triggers/pending HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 153 Content-Length: 150
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "5012053611544832286" ETag: "-1475121655268178613"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [ "triggers": [
"http://dcdn.example.com/triggers/0", "http://dcdn.example.com/triggers/0",
"http://dcdn.example.com/triggers/1" "http://dcdn.example.com/triggers/1"
] ]
} }
skipping to change at page 31, line 15 skipping to change at page 29, line 15
REQUEST: REQUEST:
GET /triggers/complete HTTP/1.1 GET /triggers/complete HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 56 Content-Length: 54
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "2986340333785000363" ETag: "7958041393922269003"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [] "triggers": []
} }
6.2.3. Individual Trigger Status Resources 6.2.3. Individual Trigger Status Resources
The Trigger Status Resources can also be examined for detail about The Trigger Status Resources can also be examined for detail about
skipping to change at page 32, line 15 skipping to change at page 30, line 15
REQUEST: REQUEST:
GET /triggers/0 HTTP/1.1 GET /triggers/0 HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 472 Content-Length: 462
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-4765587034697674779" ETag: "-256278637448610056"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
{ {
"ctime": 1409478798, "ctime": 1449422326,
"etime": 1409478806, "etime": 1449422334,
"mtime": 1409478798, "mtime": 1449422326,
"status": "pending", "status": "pending",
"trigger": { "trigger": {
"content.urls": [ "content.urls": [
"http://www.example.com/a/b/c/1", "http://www.example.com/a/b/c/1",
"http://www.example.com/a/b/c/2", "http://www.example.com/a/b/c/2",
"http://www.example.com/a/b/c/3", "http://www.example.com/a/b/c/3",
"http://www.example.com/a/b/c/4" "http://www.example.com/a/b/c/4"
], ],
"metadata.urls": [ "metadata.urls": [
"http://metadata.example.com/a/b/c" "http://metadata.example.com/a/b/c"
skipping to change at page 33, line 15 skipping to change at page 31, line 15
REQUEST: REQUEST:
GET /triggers/1 HTTP/1.1 GET /triggers/1 HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 551 Content-Length: 542
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:47 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-7657333837290433420" ETag: "-1202970338696035175"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:47 GMT
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
{ {
"ctime": 1409478799, "ctime": 1449422326,
"etime": 1409478807, "etime": 1449422334,
"mtime": 1409478799, "mtime": 1449422326,
"status": "pending", "status": "pending",
"trigger": { "trigger": {
"content.patterns": [ "content.patterns": [
{ {
"case-sensitive": true, "case-sensitive": true,
"pattern": "http://www.example.com/a/b/*" "pattern": "http://www.example.com/a/b/*"
} }
], ],
"content.urls": [ "content.urls": [
"http://www.example.com/a/index.html" "http://www.example.com/a/index.html"
skipping to change at page 34, line 11 skipping to change at page 32, line 11
The uCDN SHOULD use the Entity Tags of collections or Trigger Status The uCDN SHOULD use the Entity Tags of collections or Trigger Status
Resources when polling for change in status, as shown in the Resources when polling for change in status, as shown in the
following examples: following examples:
REQUEST: REQUEST:
GET /triggers/pending HTTP/1.1 GET /triggers/pending HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
If-None-Match: "5012053611544832286" If-None-Match: "-1475121655268178613"
RESPONSE: RESPONSE:
HTTP/1.1 304 Not Modified HTTP/1.1 304 Not Modified
Content-Length: 0 Content-Length: 0
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "5012053611544832286" ETag: "-1475121655268178613"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
REQUEST: REQUEST:
GET /triggers/0 HTTP/1.1 GET /triggers/0 HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
If-None-Match: "-4765587034697674779" If-None-Match: "-256278637448610056"
RESPONSE: RESPONSE:
HTTP/1.1 304 Not Modified HTTP/1.1 304 Not Modified
Content-Length: 0 Content-Length: 0
Expires: Sun, 31 Aug 2014 09:54:19 GMT Expires: Sun, 06 Dec 2015 17:19:46 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-4765587034697674779" ETag: "-256278637448610056"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:19 GMT Date: Sun, 06 Dec 2015 17:18:46 GMT
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
When the CI/T Trigger Command is complete, the contents of the When the CI/T Trigger Command is complete, the contents of the
filtered collections will be updated along with their Entity Tags. filtered collections will be updated along with their Entity Tags.
For example, when the two example CI/T Trigger Commands are complete, For example, when the two example CI/T Trigger Commands are complete,
the collections of pending and complete Trigger Status Resources the collections of pending and complete Trigger Status Resources
might look like: might look like:
REQUEST: REQUEST:
GET /triggers/pending HTTP/1.1 GET /triggers/pending HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
If-None-Match: "5012053611544832286"
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 56 Content-Length: 54
Expires: Sun, 31 Aug 2014 09:54:29 GMT Expires: Sun, 06 Dec 2015 17:19:51 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-4471185573414616962" ETag: "1337503181677633762"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:29 GMT Date: Sun, 06 Dec 2015 17:18:51 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [] "triggers": []
} }
REQUEST: REQUEST:
GET /triggers/complete HTTP/1.1 GET /triggers/complete HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
If-None-Match: "2986340333785000363"
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 153 Content-Length: 150
Expires: Sun, 31 Aug 2014 09:54:30 GMT Expires: Sun, 06 Dec 2015 17:19:58 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-1508172875796647067" ETag: "-2588648306194498266"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:30 GMT Date: Sun, 06 Dec 2015 17:18:58 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [ "triggers": [
"http://dcdn.example.com/triggers/0", "http://dcdn.example.com/triggers/0",
"http://dcdn.example.com/triggers/1" "http://dcdn.example.com/triggers/1"
] ]
} }
skipping to change at page 37, line 15 skipping to change at page 34, line 47
REQUEST: REQUEST:
DELETE /triggers/0 HTTP/1.1 DELETE /triggers/0 HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 204 No Content HTTP/1.1 204 No Content
Date: Sun, 31 Aug 2014 09:53:30 GMT Date: Sun, 06 Dec 2015 17:18:59 GMT
Content-Length: 0 Content-Length: 0
Content-Type: text/html; charset=UTF-8 Content-Type: text/html; charset=UTF-8
Server: example-server/0.1 Server: example-server/0.1
This would, for example, cause the collection of completed Trigger This would, for example, cause the collection of completed Trigger
Status Resources shown in the example above to be updated to: Status Resources shown in the example above to be updated to:
REQUEST: REQUEST:
GET /triggers/complete HTTP/1.1 GET /triggers/complete HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 106 Content-Length: 104
Expires: Sun, 31 Aug 2014 09:54:30 GMT Expires: Sun, 06 Dec 2015 17:19:59 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-1842390246836476263" ETag: "6647924643429037709"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:30 GMT Date: Sun, 06 Dec 2015 17:18:59 GMT
Content-Type: application/cdni; ptype=ci-trigger-collection Content-Type: application/cdni; ptype=ci-trigger-collection
{ {
"staleresourcetime": 86400, "staleresourcetime": 86400,
"triggers": [ "triggers": [
"http://dcdn.example.com/triggers/1" "http://dcdn.example.com/triggers/1"
] ]
} }
6.2.6. Error Reporting 6.2.6. Error Reporting
skipping to change at page 38, line 21 skipping to change at page 36, line 15
REQUEST: REQUEST:
GET /triggers/2 HTTP/1.1 GET /triggers/2 HTTP/1.1
User-Agent: example-user-agent/0.1 User-Agent: example-user-agent/0.1
Host: dcdn.example.com Host: dcdn.example.com
Accept: */* Accept: */*
RESPONSE: RESPONSE:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Length: 505 Content-Length: 484
Expires: Sun, 31 Aug 2014 09:54:38 GMT Expires: Sun, 06 Dec 2015 17:20:08 GMT
Server: example-server/0.1 Server: example-server/0.1
Etag: "-3893590191073700822" ETag: "8302815253703938792"
Cache-Control: max-age=60 Cache-Control: max-age=60
Date: Sun, 31 Aug 2014 09:53:38 GMT Date: Sun, 06 Dec 2015 17:19:08 GMT
Content-Type: application/cdni; ptype=ci-trigger-status Content-Type: application/cdni; ptype=ci-trigger-status
{ {
"ctime": 1409478810, "ctime": 1449422340,
"errors": [ "errors": [
{ {
"content.urls": [ "content.urls": [
"http://newsite.example.com/index.html" "http://newsite.example.com/index.html"
], ],
"description": "description": "newsite.example.com not in HostIndex",
"No HostIndex entry found for newsite.example.com",
"error": "emeta" "error": "emeta"
} }
], ],
"etime": 1409478818, "etime": 1449422348,
"mtime": 1409478814, "mtime": 1449422344,
"status": "active", "status": "active",
"trigger": { "trigger": {
"content.urls": [ "content.urls": [
"http://newsite.example.com/index.html" "http://newsite.example.com/index.html"
], ],
"type": "preposition" "type": "preposition"
} }
} }
7. IANA Considerations 7. IANA Considerations
skipping to change at page 41, line 39 skipping to change at page 39, line 32
9. Acknowledgements 9. Acknowledgements
The authors thank Kevin Ma for his input, and Carsten Bormann for his The authors thank Kevin Ma for his input, and Carsten Bormann for his
review and formalization of the JSON data. review and formalization of the JSON data.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, March 1997.
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March Interchange Format", RFC 7159, March 2014.
2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
Protocol (HTTP/1.1): Message Syntax and Routing", RFC (HTTP/1.1): Message Syntax and Routing", RFC 7230, June
7230, DOI 10.17487/RFC7230, June 2014, 2014.
<http://www.rfc-editor.org/info/rfc7230>.
[RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
Protocol (HTTP/1.1): Semantics and Content", RFC 7231, DOI (HTTP/1.1): Semantics and Content", RFC 7231, June 2014.
10.17487/RFC7231, June 2014,
<http://www.rfc-editor.org/info/rfc7231>.
[RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7232] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol
Protocol (HTTP/1.1): Conditional Requests", RFC 7232, DOI (HTTP/1.1): Conditional Requests", RFC 7232, June 2014.
10.17487/RFC7232, June 2014,
<http://www.rfc-editor.org/info/rfc7232>.
[RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May (DTLS)", BCP 195, RFC 7525, May 2015.
2015, <http://www.rfc-editor.org/info/rfc7525>.
10.2. Informative References 10.2. Informative References
[I-D.greevenbosch-appsawg-cbor-cddl] [I-D.greevenbosch-appsawg-cbor-cddl]
Vigano, C. and H. Birkholz, "CBOR data definition Vigano, C. and H. Birkholz, "CBOR data definition language
language: a notational convention to express CBOR data (CDDL): a notational convention to express CBOR data
structures.", draft-greevenbosch-appsawg-cbor-cddl-06 structures", draft-greevenbosch-appsawg-cbor-cddl-07 (work
(work in progress), July 2015. in progress), October 2015.
[I-D.ietf-cdni-media-type] [I-D.ietf-cdni-media-type]
Ma, K., "CDNI Media Type Registration", draft-ietf-cdni- Ma, K., "CDNI Media Type Registration", draft-ietf-cdni-
media-type-06 (work in progress), October 2015. media-type-06 (work in progress), October 2015.
[I-D.ietf-cdni-metadata] [I-D.ietf-cdni-metadata]
Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma,
"CDN Interconnection Metadata", draft-ietf-cdni- "CDN Interconnection Metadata", draft-ietf-cdni-
metadata-11 (work in progress), July 2015. metadata-12 (work in progress), October 2015.
[I-D.ietf-cdni-redirection] [I-D.ietf-cdni-redirection]
Niven-Jenkins, B. and R. Brandenburg, "Request Routing Niven-Jenkins, B. and R. Brandenburg, "Request Routing
Redirection Interface for CDN Interconnection", draft- Redirection Interface for CDN Interconnection", draft-
ietf-cdni-redirection-13 (work in progress), October 2015. ietf-cdni-redirection-13 (work in progress), October 2015.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/ [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
RFC2818, May 2000,
<http://www.rfc-editor.org/info/rfc2818>.
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", RFC 6707, DOI 10.17487/RFC6707, September Statement", RFC 6707, September 2012.
2012, <http://www.rfc-editor.org/info/rfc6707>.
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg,
"Framework for Content Distribution Network "Framework for Content Distribution Network
Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, Interconnection (CDNI)", RFC 7336, August 2014.
August 2014, <http://www.rfc-editor.org/info/rfc7336>.
[RFC7337] Leung, K., Ed. and Y. Lee, Ed., "Content Distribution [RFC7337] Leung, K. and Y. Lee, "Content Distribution Network
Network Interconnection (CDNI) Requirements", RFC 7337, Interconnection (CDNI) Requirements", RFC 7337, August
DOI 10.17487/RFC7337, August 2014, 2014.
<http://www.rfc-editor.org/info/rfc7337>.
Appendix A. Formalization of the JSON Data
This appendix is non-normative.
The JSON data described in this document has been formalised using
CDDL [I-D.greevenbosch-appsawg-cbor-cddl] as follows:
CIT-object = CIT-command / Trigger-Status-Resource / Trigger-Collection
CIT-command ; use media type application/cdni; ptype=ci-trigger-command
= {
? trigger: Triggerspec
? cancel: [* URI]
cdn-path: [* Cdn-PID]
}
Trigger-Status-Resource ; application/cdni; ptype=ci-trigger-status
= {
trigger: Triggerspec
ctime: Absolute-Time
mtime: Absolute-Time
? etime: Absolute-Time
status: Trigger-Status
? errors: [* Error-Description]
}
Trigger-Collection ; application/cdni; ptype=ci-trigger-collection
= {
triggers: [* URI]
? staleresourcetime: int ; time in seconds
? coll-all: URI
? coll-pending: URI
? coll-active: URI
? coll-complete: URI
? coll-failed: URI
? cdn-id: Cdn-PID
}
Triggerspec = { ; 5.2.1
type: Trigger-Type
? metadata.urls: [* URI]
? content.urls: [* URI]
? content.ccid: [* Ccid]
? metadata.patterns: [* Pattern-Match]
? content.patterns: [* Pattern-Match]
}
Trigger-Type = "preposition" / "invalidate" / "purge" ; 5.2.2
Trigger-Status = "pending" / "active" / "complete" / "processed"
/ "failed" / "cancelling" / "cancelled" ; 5.2.3
Pattern-Match = { ; 5.2.4
pattern: tstr
? case-sensitive: bool
? match-query-string: bool
}
Absolute-Time = number ; seconds since UNIX epoch, 5.2.5
Error-Description = { ; 5.2.6
error: Error-Code
? metadata.urls: [* URI]
? content.urls: [* URI]
? metadata.patterns: [* Pattern-Match]
? content.patterns: [* Pattern-Match]
? description: tstr
}
Error-Code = "emeta" / "econtent" / "eperm" / "ereject"
/ "ecdn" / "ecancelled" ; 5.2.7
Ccid = tstr ; see I-D.ietf-cdni-metadata
Cdn-PID = tstr .regexp "AS[0-9]+:[0-9]+"
URI = tstr
Authors' Addresses Authors' Addresses
Rob Murray Rob Murray
Velocix (Alcatel-Lucent) Velocix (Alcatel-Lucent)
3 Ely Road 3 Ely Road
Milton, Cambridge CB24 6DD Milton, Cambridge CB24 6DD
UK UK
Email: rob.murray@alcatel-lucent.com Email: rob.murray@alcatel-lucent.com
 End of changes. 83 change blocks. 
235 lines changed or deleted 231 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/