draft-ietf-cdni-triggers-extensions-07.txt   draft-ietf-cdni-triggers-extensions-08.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 26, 2021 N. Sopher Expires: June 26, 2021 N. Sopher
Qwilt Qwilt
December 23, 2020 December 23, 2020
CDNI Control Triggers Interface Extensions CDNI Control Triggers Interface Extensions
draft-ietf-cdni-triggers-extensions-07 draft-ietf-cdni-triggers-extensions-08
Abstract Abstract
Open Caching architecture is a use case of Content Delivery Network Open Caching architecture is a use case of Content Delivery Network
Interconnection (CDNI) in which the commercial Content Delivery Interconnection (CDNI) in which the commercial Content Delivery
Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer
serves as the downstream CDN (dCDN). This document defines serves as the downstream CDN (dCDN). This document defines
extensions to the Content Delivery Network Interconnection (CDNI) extensions to the Content Delivery Network Interconnection (CDNI)
Control Interface/Triggers defined in RFC 8007. These extensions are Control Interface/Triggers defined in RFC 8007. These extensions are
derived from requirements raised by Open Caching architecture but are derived from requirements raised by Open Caching architecture but are
skipping to change at page 3, line 33 skipping to change at page 3, line 33
6.1.2. CDNI ci-trigger-status.v2 Payload Type . . . . . . . 40 6.1.2. CDNI ci-trigger-status.v2 Payload Type . . . . . . . 40
6.1.3. CDNI CI/T LocationPolicy Trigger Extension Type . . . 40 6.1.3. CDNI CI/T LocationPolicy Trigger Extension Type . . . 40
6.1.4. CDNI CI/T TimePolicy Trigger Extension Type . . . . . 40 6.1.4. CDNI CI/T TimePolicy Trigger Extension Type . . . . . 40
6.1.5. CDNI FCI CI/T Versions Payload Type . . . . . . . . . 40 6.1.5. CDNI FCI CI/T Versions Payload Type . . . . . . . . . 40
6.1.6. CDNI FCI CI/T Playlist Protocol Payload Type . . . . 40 6.1.6. CDNI FCI CI/T Playlist Protocol Payload Type . . . . 40
6.1.7. CDNI FCI CI/T Extension Objects Payload Type . . . . 41 6.1.7. CDNI FCI CI/T Extension Objects Payload Type . . . . 41
6.2. CDNI CI/T Trigger Error Codes types . . . . . . . . . . . 41 6.2. CDNI CI/T Trigger Error Codes types . . . . . . . . . . . 41
6.3. CDNI Media protocol types . . . . . . . . . . . . . . . . 41 6.3. CDNI Media protocol types . . . . . . . . . . . . . . . . 41
7. Security Considerations . . . . . . . . . . . . . . . . . . . 42 7. Security Considerations . . . . . . . . . . . . . . . . . . . 42
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 42 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 42
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 9.1. Normative References . . . . . . . . . . . . . . . . . . 42
10.1. Normative References . . . . . . . . . . . . . . . . . . 43 9.2. Informative References . . . . . . . . . . . . . . . . . 44
10.2. Informative References . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction 1. Introduction
The Streaming Video Alliance [SVA] is a global association that works The Streaming Video Alliance [SVA] is a global association that works
to solve streaming video challenges in an effort to improve end-user to solve streaming video challenges in an effort to improve end-user
experience and adoption. The Open Caching Working Group [OCWG] of experience and adoption. The Open Caching Working Group [OCWG] of
the Streaming Video Alliance [SVA] is focused on the delegation of the Streaming Video Alliance [SVA] is focused on the delegation of
video delivery requests from commerical CDNs to a caching layer at video delivery requests from commerical CDNs to a caching layer at
the ISP's network. Open Caching architecture is a specific use case the ISP's network. Open Caching architecture is a specific use case
of CDNI where the commercial CDN is the upstream CDN (uCDN) and the of CDNI where the commercial CDN is the upstream CDN (uCDN) and the
skipping to change at page 42, line 41 skipping to change at page 42, line 41
the worst case. An implementation MUST protect itself at a minimum the worst case. An implementation MUST protect itself at a minimum
by accepting triggers only from an authenticated party over a secured by accepting triggers only from an authenticated party over a secured
connection. An implementation SHOULD also protect itself by using connection. An implementation SHOULD also protect itself by using
secure programing techniques and decline trigger commands that use secure programing techniques and decline trigger commands that use
potentially risky regex, such techniques are readily available in potentially risky regex, such techniques are readily available in
secure programming literature and are beyond the scope of this secure programming literature and are beyond the scope of this
document. document.
8. Acknowledgments 8. Acknowledgments
TBD The authors thank Kevin J. Ma for his guidance as well as careful
and methodical reviews and feedback.
9. Contributors
The authors thank all members of the "Streaming Video Alliance" (SVA)
and specifically contributions by members of Open Caching Working
Group in support of this document. The authors also thank Kevin Ma
for his guidance and careful and methodical reviews.
10. References 9. References
10.1. Normative References 9.1. Normative References
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 44, line 15 skipping to change at page 44, line 5
[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>.
[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 9.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,
<https://www.iso.org/standard/40874.html>. <https://www.iso.org/standard/40874.html>.
[MPEG-DASH] [MPEG-DASH]
ISO, "Information technology -- Dynamic adaptive streaming ISO, "Information technology -- Dynamic adaptive streaming
over HTTP (DASH) -- Part 1: Media presentation description over HTTP (DASH) -- Part 1: Media presentation description
and segment format", ISO/IEC 23009-1:2014, Edition 2, 05 and segment format", ISO/IEC 23009-1:2014, Edition 2, 05
 End of changes. 6 change blocks. 
17 lines changed or deleted 10 lines changed or added

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