draft-ietf-cdni-triggers-extensions-02.txt   draft-ietf-cdni-triggers-extensions-03.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: October 2, 2019 March 31, 2019 Expires: March 26, 2020 September 23, 2019
CDNI Control Triggers Interface Extensions CDNI Control Triggers Interface Extensions
draft-ietf-cdni-triggers-extensions-02 draft-ietf-cdni-triggers-extensions-03
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
CDN (dCDN). The extensions specified in this document to the CDNI CDN (dCDN). The extensions specified in this document to the CDNI
Control Interface / Triggers are derived from requirements of Open Control Interface / Triggers are derived from requirements of Open
Caching but are applicable to CDNI use cases in general. Caching but are applicable to CDNI use cases in general.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "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.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 October 2, 2019. This Internet-Draft will expire on March 26, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 36, line 24 skipping to change at page 36, line 24
] ]
} }
] ]
} }
6. IANA Considerations 6. IANA Considerations
6.1. CDNI Payload Types 6.1. CDNI Payload Types
This document requests the registration of the following CDNI Payload This document requests the registration of the following CDNI Payload
Types under the IANA CDNI Payload Type registry defined in [RFC7736]: Types under the IANA "CDNI Payload Types" registry defined in
[RFC7736]:
+-----------------------------+---------------+ +-----------------------------+---------------+
| Payload Type | Specification | | Payload Type | Specification |
+-----------------------------+---------------+ +-----------------------------+---------------+
| ci-trigger-command.v2 | RFCthis | | ci-trigger-command.v2 | RFCthis |
| ci-trigger-status.v2 | RFCthis | | ci-trigger-status.v2 | RFCthis |
| CIT.LocationPolicy | RFCthis | | CIT.LocationPolicy | RFCthis |
| CIT.TimePolicy | RFCthis | | CIT.TimePolicy | RFCthis |
| FCI.TriggerVersion | RFCthis | | FCI.TriggerVersion | RFCthis |
| FCI.TriggerPlaylistProtocol | RFCthis | | FCI.TriggerPlaylistProtocol | RFCthis |
skipping to change at page 38, line 33 skipping to change at page 38, line 33
+------------+-----------------------------------+------------------+ +------------+-----------------------------------+------------------+
| eextension | The dCDN failed to parse a | Section Section | | eextension | The dCDN failed to parse a | Section Section |
| | generic extension object, or does | 3.3.7 of this | | | generic extension object, or does | 3.3.7 of this |
| | not support this extension. | document. | | | not support this extension. | document. |
+------------+-----------------------------------+------------------+ +------------+-----------------------------------+------------------+
6.3. CDNI Media protocol types 6.3. CDNI Media protocol types
The IANA is requested to create a new "CDNI MediaProtocol Types" The IANA is requested to create a new "CDNI MediaProtocol Types"
subregistry in the "Content Delivery Networks Interconnection (CDNI) subregistry in the "Content Delivery Networks Interconnection (CDNI)
Parameters" registry. The "CDNI Media Protocol Types" namespace Parameters" registry. The "CDNI MediaProtocol Types" namespace
defines the valid Media Protocol object values in defines the valid MediaProtocol object values in
Section Section 3.3.4, used by the Playlist object. Additions to the Section Section 3.3.4, used by the Playlist object. Additions to the
MediaProtocol namespace conform to the "Specification Required" MediaProtocol namespace conform to the "Specification Required"
policy as defined in Section 4.6 of [RFC8126], where the policy as defined in Section 4.6 of [RFC8126], where the
specification defines the MediaProtocol Type and the protocol to specification defines the MediaProtocol Type and the protocol to
which it is associated. The designated expert will verify that new which it is associated. The designated expert will verify that new
protocol definitions do not duplicate existing protocol definitions protocol definitions do not duplicate existing protocol definitions
and prevent gratuitous additions to the namespace. and prevent gratuitous additions to the namespace.
The following table defines the initial MediaProtocol values The following table defines the initial MediaProtocol values
corresponding to the HLS, MSS, and DASH protocols: corresponding to the HLS, MSS, and DASH protocols:
skipping to change at page 40, line 49 skipping to change at page 40, line 49
R., and K. Ma, "Content Delivery Network Interconnection R., and K. Ma, "Content Delivery Network Interconnection
(CDNI) Request Routing: Footprint and Capabilities (CDNI) Request Routing: Footprint and Capabilities
Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016, Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016,
<https://www.rfc-editor.org/info/rfc8008>. <https://www.rfc-editor.org/info/rfc8008>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", STD 90, RFC 8259, Interchange Format", STD 90, RFC 8259,
DOI 10.17487/RFC8259, December 2017, DOI 10.17487/RFC8259, December 2017,
<https://www.rfc-editor.org/info/rfc8259>. <https://www.rfc-editor.org/info/rfc8259>.
10.2. Informative References 10.2. Informative References
[ISO8601] ISO, "Data elements and interchange formats -- Information [ISO8601] ISO, "Data elements and interchange formats -- Information
interchange -- Representation of dates and times", interchange -- Representation of dates and times",
ISO 8601:2004, Edition 3, 12 2004, ISO 8601:2004, Edition 3, 12 2004,
 End of changes. 7 change blocks. 
8 lines changed or deleted 15 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/