--- 1/draft-ietf-cdni-request-routing-extensions-03.txt 2019-07-29 01:13:13.406892939 -0700 +++ 2/draft-ietf-cdni-request-routing-extensions-04.txt 2019-07-29 01:13:13.434893645 -0700 @@ -1,19 +1,19 @@ Network Working Group O. Finkelman Internet-Draft Qwilt Intended status: Standards Track S. Mishra -Expires: November 22, 2019 Verizon - May 21, 2019 +Expires: January 29, 2020 Verizon + July 28, 2019 CDNI Request Routing Extensions - draft-ietf-cdni-request-routing-extensions-03 + draft-ietf-cdni-request-routing-extensions-04 Abstract The Open Caching working group of the Streaming Video Alliance is focused on the delegation of video delivery requests from 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 the upstream CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN). The extensions specified in this document to the CDNI Metadata and FCI interfaces are derived from requirements raised by Open Caching @@ -33,21 +33,21 @@ 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 https://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 November 22, 2019. + This Internet-Draft will expire on January 29, 2020. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -67,24 +67,23 @@ 2.3. HttpTarget . . . . . . . . . . . . . . . . . . . . . . . 6 3. Fallback Target Address Metadata . . . . . . . . . . . . . . 8 3.1. Properties Fallback Target Address Metadata Object . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4.1. CDNI Payload Types . . . . . . . . . . . . . . . . . . . 9 4.1.1. CDNI FCI RedirectTarget Payload Type . . . . . . . . 10 4.1.2. CDNI MI FallbackTarget Payload Type . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5.1. Confidentiality and Privacy . . . . . . . . . . . . . . . 10 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 - 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 11 - 8.2. Informative References . . . . . . . . . . . . . . . . . 11 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 + 7.1. Normative References . . . . . . . . . . . . . . . . . . 11 + 7.2. Informative References . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction This document defines objects needed for Open Caching request routing. For that purpose it extends CDNI metadata [RFC8006] and CDNI Footprint and Capabilities [RFC8008]. For consistency, this document follows the CDNI notation of uCDN (the commercial CDN) and dCDN (the ISP caching layer). @@ -182,30 +181,30 @@ Mandatory-to-Specify: No. If not present, or empty, the redirect target applies to all hosts of the redirecting uCDN. Property: dns-target Description: Target address for a DNS A record or CNAME record. Type: DnsTarget object (see Section 2.2) Mandatory-to-Specify: No. but at least one of "dns-target" or - "http-target" MUST be present and non empty. + "http-target" MUST be present and non-empty. Property: http-target Description: Target URI for a HTTP redirect. Type: HttpTarget object (see Section 2.3) Mandatory-to-Specify: No, but at least one of "dns-target" or - "http-target" MUST be present and non empty. + "http-target" MUST be present and non-empty. The following is an example of a Redirect Target capability object serialization that advertises a dCDN target address that is attached to a specific list of uCDN "redirecting-hosts". A uCDN host that is included in that list can redirect to the advertised dCDN redirect target. { "capabilities": [ { @@ -455,29 +454,29 @@ The redirect Target FCI object potentially exposes information about the internal strcture of the dCDN network. A third party could intercept the FCI transactions and use the information to attack the dCDN. An implemenation of the FCI MUST therefore use strong authentication and encryption and strictly follow the directions for securing the interface as defined for the Metadata Interface in Section 8.3 of [RFC8006]. 6. Acknowledgements - TBD. - -7. Contributors - - TBD. + The authors thank Nir B. Sopher for reality checks against + production use cases, his contribution is significant to this + document. The authors also thank Ben Niven-Jenkins for his review + and feedback and Kevin J. Ma for his guidance throughout the + development of this document including his regular reviews. -8. References +7. References -8.1. Normative References +7.1. Normative References [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . @@ -500,21 +499,21 @@ Interconnection (CDNI) Control Interface / Triggers", RFC 8007, DOI 10.17487/RFC8007, December 2016, . [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg, R., and K. Ma, "Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics", RFC 8008, DOI 10.17487/RFC8008, December 2016, . -8.2. Informative References +7.2. Informative References [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content Distribution Network Interconnection (CDNI) Problem Statement", RFC 6707, DOI 10.17487/RFC6707, September 2012, . [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., "Framework for Content Distribution Network Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, August 2014, . @@ -529,20 +528,19 @@ . Authors' Addresses Ori Finkelman Qwilt 6, Ha'harash Hod HaSharon 4524079 Israel - Phone: +972-72-2221647 Email: ori.finkelman.ietf@gmail.com Sanjay Mishra Verizon 13100 Columbia Pike Silver Spring, MD 20904 USA Email: sanjay.mishra@verizon.com