draft-ietf-cdni-triggers-extensions-00.txt   draft-ietf-cdni-triggers-extensions-01.txt 
Network Working Group O. Finkelman Network Working Group O. Finkelman
Internet-Draft Qwilt Internet-Draft Qwilt
Updates: 8007 (if approved) S. Mishra Updates: 8007 (if approved) S. Mishra
Intended status: Standards Track Verizon Intended status: Standards Track Verizon
Expires: June 2, 2019 November 29, 2018 Expires: June 5, 2019 December 2, 2018
CDNI Control Triggers Interface Extensions CDNI Control Triggers Interface Extensions
draft-ietf-cdni-triggers-extensions-00 draft-ietf-cdni-triggers-extensions-01
Abstract Abstract
This document updates RFC 8007 to include generic extensions and more This document updates RFC 8007 to include generic extensions and more
granular content matching options, required by the Open Caching granular content matching options, required by the Open Caching
architecture. The Open Caching working group of the Streaming Video architecture. The Open Caching working group of the Streaming Video
Alliance is focused on the delegation of video delivery request from Alliance is focused on the delegation of video delivery request from
commercial CDNs to a caching layer at the ISP. In that aspect, Open commercial CDNs to a caching layer at the ISP. In that aspect, Open
Caching is a specific use case of CDNI, where the commercial CDN is Caching is a specific use case of CDNI, where the commercial CDN is
the upstream CDN (uCDN) and the ISP caching layer is the downstream the upstream CDN (uCDN) and the ISP caching layer is the downstream
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 June 2, 2019. This Internet-Draft will expire on June 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 29, line 21 skipping to change at page 29, line 21
execution time per region. execution time per region.
o Local Time schedule: We introduce a "local time" version for o Local Time schedule: We introduce a "local time" version for
Internet timestamps that follows the notation for local time as Internet timestamps that follows the notation for local time as
defined in Section 4.2.2 of [ISO8601]. When local time is used, defined in Section 4.2.2 of [ISO8601]. When local time is used,
that dCDN SHOULD execute the triggers at different absolute times, that dCDN SHOULD execute the triggers at different absolute times,
according the local time of each execution location. according the local time of each execution location.
Object specification Object specification
Property: unixEpochWindow Property: unix-time-window
Description: A UNIX epoch time window in which the trigger Description: A UNIX epoch time window in which the trigger
SHOULD be executed. SHOULD be executed.
Type: TimeWindow object using UNIX epoch timestamps (see Type: TimeWindow object using UNIX epoch timestamps (see
Section 4.2.3.2 of [RFC8006]) Section 4.2.3.2 of [RFC8006])
Mandatory-to-Specify: No, but exactly one of "unixEpochWindow", Mandatory-to-Specify: No, but exactly one of "unix-time-
"utcWindow" or "localTimeWindow" MUST be present. window", "utc-window" or "local-time-window" MUST be present.
Property: utcWindow Property: utc-window
Description: A UTC time window in which the trigger SHOULD be Description: A UTC time window in which the trigger SHOULD be
executed. executed.
Type: UTCWindow object as defined in Section 4.2.1. Type: UTCWindow object as defined in Section 4.2.1.
Mandatory-to-Specify: No, but exactly one of "unixEpochWindow", Mandatory-to-Specify: No, but exactly one of "unix-time-
"utcWindow" or "localTimeWindow" MUST be present. window", "utc-window" or "local-time-window" MUST be present.
Property: localTimeWindow Property: local-time-window
Description: A local time window. The dCDN SHOULD execute the Description: A local time window. The dCDN SHOULD execute the
trigger at the defined time frame, interpreted as the the local trigger at the defined time frame, interpreted as the the local
time per location. time per location.
Type: LocalTimeWindow object as defined in Section 4.2.2. Type: LocalTimeWindow object as defined in Section 4.2.2.
Mandatory-to-Specify: No, but exactly one of "unixEpochWindow", Mandatory-to-Specify: No, but exactly one of "unix-time-
"utcWindow" or "localTimeWindow" MUST be present. window", "utc-window" or "local-time-window" MUST be present.
If a time policy object is not listed within the trigger command, the 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 default behavior is to execute the trigger in a time frame most
suitable to the dCDN taking under consideration other constrains and suitable to the dCDN taking under consideration other constrains and
/ or obligations. / or obligations.
Example of a generic trigger extension object containing a time Example of a generic trigger extension object containing a time
policy object that schedules the trigger execution to a window 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 between 09:00 01/01/2000 UTC and 17:00 01/01/2000 UTC, using the
"unixEpochWindow" property: "unix-time-window" property:
{ {
"generic-trigger-extension-type": "CIT.TimePolicy", "generic-trigger-extension-type": "CIT.TimePolicy",
"generic-trigger-extension-value": "generic-trigger-extension-value":
{ {
"unixEpochWindow": { "unix-time-window": {
"start": 946717200, "start": 946717200,
"end": 946746000 "end": 946746000
} }
} }
"mandatory-to-enforce": true, "mandatory-to-enforce": true,
"safe-to-redistribute": true, "safe-to-redistribute": true,
"incomprehensible": false "incomprehensible": false
} }
4.2.1. UTCWindow 4.2.1. UTCWindow
 End of changes. 11 change blocks. 
14 lines changed or deleted 14 lines changed or added

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