CDNI Control Interface / Triggers
draft-ietf-cdni-control-triggers-12
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (cdni WG) | |
Last updated | 2016-03-18 | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | François Le Faucheur | ||
Shepherd write-up | Show (last changed 2015-10-27) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs 5 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Alexey Melnikov | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed |
Network Working Group R. Murray Internet-Draft B. Niven-Jenkins Intended status: Standards Track Nokia Expires: September 19, 2016 March 18, 2016 CDNI Control Interface / Triggers draft-ietf-cdni-control-triggers-12 Abstract This document describes the part of the CDN Interconnection Control Interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-positions metadata or content, or that it invalidates or purges metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 19, 2016. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. Murray & Niven-Jenkins Expires September 19, 2016 [Page 1] Internet-Draft CDN Interconnect Triggers March 2016 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2. Model for CDNI Triggers . . . . . . . . . . . . . . . . . . . 4 2.1. Timing of Triggered Activity . . . . . . . . . . . . . . 6 2.2. Scope of Triggered Activity . . . . . . . . . . . . . . . 6 2.2.1. Multiple Interconnected CDNs . . . . . . . . . . . . 6 2.3. Trigger Results . . . . . . . . . . . . . . . . . . . . . 8 3. Collections of Trigger Status Resources . . . . . . . . . . . 8 4. CDNI Trigger Interface . . . . . . . . . . . . . . . . . . . 9 4.1. Creating Triggers . . . . . . . . . . . . . . . . . . . . 10 4.2. Checking Status . . . . . . . . . . . . . . . . . . . . . 11 4.2.1. Polling Trigger Status Resource collections . . . . . 11 4.2.2. Polling Trigger Status Resources . . . . . . . . . . 12 4.3. Cancelling Triggers . . . . . . . . . . . . . . . . . . . 12 4.4. Deleting Triggers . . . . . . . . . . . . . . . . . . . . 13 4.5. Expiry of Trigger Status Resources . . . . . . . . . . . 13 4.6. Loop Detection and Prevention . . . . . . . . . . . . . . 14 4.7. Error Handling . . . . . . . . . . . . . . . . . . . . . 14 4.8. Content URLs . . . . . . . . . . . . . . . . . . . . . . 15 5. CI/T Object Properties and Encoding . . . . . . . . . . . . . 16 5.1. CI/T Objects . . . . . . . . . . . . . . . . . . . . . . 16 5.1.1. CI/T Commands . . . . . . . . . . . . . . . . . . . . 16 5.1.2. Trigger Status Resource . . . . . . . . . . . . . . . 17 5.1.3. Trigger Collection . . . . . . . . . . . . . . . . . 18 5.2. Properties of CI/T Objects . . . . . . . . . . . . . . . 20 5.2.1. Trigger Specification . . . . . . . . . . . . . . . . 20 5.2.2. Trigger Type . . . . . . . . . . . . . . . . . . . . 21 5.2.3. Trigger Status . . . . . . . . . . . . . . . . . . . 22 5.2.4. PatternMatch . . . . . . . . . . . . . . . . . . . . 22 5.2.5. Absolute Time . . . . . . . . . . . . . . . . . . . . 23 5.2.6. Error Description . . . . . . . . . . . . . . . . . . 24 5.2.7. Error Code . . . . . . . . . . . . . . . . . . . . . 24Show full document text