draft-ietf-cdni-request-routing-extensions-03.txt   draft-ietf-cdni-request-routing-extensions-04.txt 
Network Working Group O. Finkelman Network Working Group O. Finkelman
Internet-Draft Qwilt Internet-Draft Qwilt
Intended status: Standards Track S. Mishra Intended status: Standards Track S. Mishra
Expires: November 22, 2019 Verizon Expires: January 29, 2020 Verizon
May 21, 2019 July 28, 2019
CDNI Request Routing Extensions CDNI Request Routing Extensions
draft-ietf-cdni-request-routing-extensions-03 draft-ietf-cdni-request-routing-extensions-04
Abstract Abstract
The Open Caching working group of the Streaming Video Alliance is The Open Caching working group of the Streaming Video Alliance is
focused on the delegation of video delivery requests from commercial focused on the delegation of video delivery requests from commercial
CDNs to a caching layer at the ISP. In that aspect, Open Caching is 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 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). CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN).
The extensions specified in this document to the CDNI Metadata and The extensions specified in this document to the CDNI Metadata and
FCI interfaces are derived from requirements raised by Open Caching FCI interfaces are derived from requirements raised by Open Caching
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 November 22, 2019. This Internet-Draft will expire on January 29, 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 2, line 37 skipping to change at page 2, line 37
2.3. HttpTarget . . . . . . . . . . . . . . . . . . . . . . . 6 2.3. HttpTarget . . . . . . . . . . . . . . . . . . . . . . . 6
3. Fallback Target Address Metadata . . . . . . . . . . . . . . 8 3. Fallback Target Address Metadata . . . . . . . . . . . . . . 8
3.1. Properties Fallback Target Address Metadata Object . . . 9 3.1. Properties Fallback Target Address Metadata Object . . . 9
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4.1. CDNI Payload Types . . . . . . . . . . . . . . . . . . . 9 4.1. CDNI Payload Types . . . . . . . . . . . . . . . . . . . 9
4.1.1. CDNI FCI RedirectTarget Payload Type . . . . . . . . 10 4.1.1. CDNI FCI RedirectTarget Payload Type . . . . . . . . 10
4.1.2. CDNI MI FallbackTarget Payload Type . . . . . . . . . 10 4.1.2. CDNI MI FallbackTarget Payload Type . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5.1. Confidentiality and Privacy . . . . . . . . . . . . . . . 10 5.1. Confidentiality and Privacy . . . . . . . . . . . . . . . 10
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
This document defines objects needed for Open Caching request This document defines objects needed for Open Caching request
routing. For that purpose it extends CDNI metadata [RFC8006] and routing. For that purpose it extends CDNI metadata [RFC8006] and
CDNI Footprint and Capabilities [RFC8008]. For consistency, this CDNI Footprint and Capabilities [RFC8008]. For consistency, this
document follows the CDNI notation of uCDN (the commercial CDN) and document follows the CDNI notation of uCDN (the commercial CDN) and
dCDN (the ISP caching layer). dCDN (the ISP caching layer).
skipping to change at page 5, line 8 skipping to change at page 5, line 8
Mandatory-to-Specify: No. If not present, or empty, the Mandatory-to-Specify: No. If not present, or empty, the
redirect target applies to all hosts of the redirecting uCDN. redirect target applies to all hosts of the redirecting uCDN.
Property: dns-target Property: dns-target
Description: Target address for a DNS A record or CNAME record. Description: Target address for a DNS A record or CNAME record.
Type: DnsTarget object (see Section 2.2) Type: DnsTarget object (see Section 2.2)
Mandatory-to-Specify: No. but at least one of "dns-target" or 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 Property: http-target
Description: Target URI for a HTTP redirect. Description: Target URI for a HTTP redirect.
Type: HttpTarget object (see Section 2.3) Type: HttpTarget object (see Section 2.3)
Mandatory-to-Specify: No, but at least one of "dns-target" or 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 The following is an example of a Redirect Target capability object
serialization that advertises a dCDN target address that is attached serialization that advertises a dCDN target address that is attached
to a specific list of uCDN "redirecting-hosts". A uCDN host that is to a specific list of uCDN "redirecting-hosts". A uCDN host that is
included in that list can redirect to the advertised dCDN redirect included in that list can redirect to the advertised dCDN redirect
target. target.
{ {
"capabilities": [ "capabilities": [
{ {
skipping to change at page 10, line 47 skipping to change at page 10, line 47
The redirect Target FCI object potentially exposes information about The redirect Target FCI object potentially exposes information about
the internal strcture of the dCDN network. A third party could the internal strcture of the dCDN network. A third party could
intercept the FCI transactions and use the information to attack the intercept the FCI transactions and use the information to attack the
dCDN. An implemenation of the FCI MUST therefore use strong dCDN. An implemenation of the FCI MUST therefore use strong
authentication and encryption and strictly follow the directions for authentication and encryption and strictly follow the directions for
securing the interface as defined for the Metadata Interface in securing the interface as defined for the Metadata Interface in
Section 8.3 of [RFC8006]. Section 8.3 of [RFC8006].
6. Acknowledgements 6. Acknowledgements
TBD. The authors thank Nir B. Sopher for reality checks against
production use cases, his contribution is significant to this
7. Contributors document. The authors also thank Ben Niven-Jenkins for his review
and feedback and Kevin J. Ma for his guidance throughout the
TBD. 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", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987,
<https://www.rfc-editor.org/info/rfc1034>. <https://www.rfc-editor.org/info/rfc1034>.
[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 11, line 48 skipping to change at page 11, line 44
Interconnection (CDNI) Control Interface / Triggers", Interconnection (CDNI) Control Interface / Triggers",
RFC 8007, DOI 10.17487/RFC8007, December 2016, RFC 8007, DOI 10.17487/RFC8007, December 2016,
<https://www.rfc-editor.org/info/rfc8007>. <https://www.rfc-editor.org/info/rfc8007>.
[RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg, [RFC8008] Seedorf, J., Peterson, J., Previdi, S., van Brandenburg,
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>.
8.2. Informative References 7.2. Informative References
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", RFC 6707, DOI 10.17487/RFC6707, September Statement", RFC 6707, DOI 10.17487/RFC6707, September
2012, <https://www.rfc-editor.org/info/rfc6707>. 2012, <https://www.rfc-editor.org/info/rfc6707>.
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed.,
"Framework for Content Distribution Network "Framework for Content Distribution Network
Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336,
August 2014, <https://www.rfc-editor.org/info/rfc7336>. August 2014, <https://www.rfc-editor.org/info/rfc7336>.
skipping to change at page 12, line 32 skipping to change at page 12, line 27
<https://www.rfc-editor.org/info/rfc7871>. <https://www.rfc-editor.org/info/rfc7871>.
Authors' Addresses Authors' Addresses
Ori Finkelman Ori Finkelman
Qwilt Qwilt
6, Ha'harash 6, Ha'harash
Hod HaSharon 4524079 Hod HaSharon 4524079
Israel Israel
Phone: +972-72-2221647
Email: ori.finkelman.ietf@gmail.com Email: ori.finkelman.ietf@gmail.com
Sanjay Mishra Sanjay Mishra
Verizon Verizon
13100 Columbia Pike 13100 Columbia Pike
Silver Spring, MD 20904 Silver Spring, MD 20904
USA USA
Email: sanjay.mishra@verizon.com Email: sanjay.mishra@verizon.com
 End of changes. 11 change blocks. 
19 lines changed or deleted 17 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/