From nobody Mon Nov 4 06:47:15 2019 Return-Path: X-Original-To: cdni@ietf.org Delivered-To: cdni@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4CA1200F4; Mon, 4 Nov 2019 06:47:05 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: cdni@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.108.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: cdni@ietf.org Message-ID: <157287882542.16597.2117028609653765193@ietfa.amsl.com> Date: Mon, 04 Nov 2019 06:47:05 -0800 Archived-At: Subject: [CDNi] I-D Action: draft-ietf-cdni-interfaces-https-delegation-02.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.29 List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2019 14:47:06 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Content Delivery Networks Interconnection WG of the IETF. Title : CDNI extensions for HTTPS delegation Authors : Frederic Fieau Emile Stephan Sanjay Mishra Filename : draft-ietf-cdni-interfaces-https-delegation-02.txt Pages : 11 Date : 2019-11-04 Abstract: The delivery of content over HTTPS involving multiple CDNs raises credential management issues. This document proposes extensions in CDNI Control and Metadata interfaces to setup HTTPS delegation from an Upstream CDN (uCDN) to a Downstream CDN (dCDN). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-interfaces-https-delegation/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-cdni-interfaces-https-delegation-02 https://datatracker.ietf.org/doc/html/draft-ietf-cdni-interfaces-https-delegation-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-interfaces-https-delegation-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 20 13:29:33 2019 Return-Path: X-Original-To: cdni@ietf.org Delivered-To: cdni@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22BCB1201EA; Wed, 20 Nov 2019 13:29:32 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: cdni@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.110.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: cdni@ietf.org Message-ID: <157428537207.30532.619903290739952848@ietfa.amsl.com> Date: Wed, 20 Nov 2019 13:29:32 -0800 Archived-At: Subject: [CDNi] I-D Action: draft-ietf-cdni-request-routing-extensions-08.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.29 List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2019 21:29:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Content Delivery Networks Interconnection WG of the IETF. Title : CDNI Request Routing Extensions Authors : Ori Finkelman Sanjay Mishra Filename : draft-ietf-cdni-request-routing-extensions-08.txt Pages : 19 Date : 2019-11-20 Abstract: Open Caching architecture is a use case of Content Delivery Networks Interconnection (CDNI) in which the commercial Content Delivery Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer serves as the downstream CDN (dCDN). The extensions specified in this document to the CDNI Metadata Interface (MI) and the Footprint and Capabilities Interface (FCI) are derived from requirements raised by Open Caching but are also applicable to CDNI use cases in general. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-request-routing-extensions/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-cdni-request-routing-extensions-08 https://datatracker.ietf.org/doc/html/draft-ietf-cdni-request-routing-extensions-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-request-routing-extensions-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 20 14:22:17 2019 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAAA12024E; Wed, 20 Nov 2019 14:21:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8SHVRTxQIglI; Wed, 20 Nov 2019 14:21:35 -0800 (PST) Received: from mail-vs1-xe44.google.com (mail-vs1-xe44.google.com [IPv6:2607:f8b0:4864:20::e44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 388EE1200CE; Wed, 20 Nov 2019 14:21:32 -0800 (PST) Received: by mail-vs1-xe44.google.com with SMTP id u6so843320vsp.4; Wed, 20 Nov 2019 14:21:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=TwnQzoxE6pmTrai5oZGBuLWiJ9zGXyWueYdn4kiYZZM=; b=F6nx6vX+ukaRHfn/xTZVxwnBso3gPAId/BdqigtD77sK37WcM4EiUDFCSc5JkCo1IQ 9EUXYSK/TKmOsL0ASJDZA15h3kvXNmQPnupZPMWbnnEvB5tXaaI7zPRz/SPVGEbVbvXF 7sZjn7RKoqm+r0RnO1fepGT3PVl0ZAK5nZcB6Qa/rerDLy6k3tGbKRkZyBTm/Z6cUqey d8cc+NMmCYVQSEE5mO2AyJF2TE/uhOuupCkDK52gsrEiv7yriq3MpyJlllr2jTz+LECj u9pqpSNMnpzw0Oe1FiYWFmX2PhwxFbPe41BpnNsrosJBTIt0HKbVkCpR0DNVHuErd3oC 7WOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=TwnQzoxE6pmTrai5oZGBuLWiJ9zGXyWueYdn4kiYZZM=; b=r4VVtQT4uxf6K+u7wQ8+sMFlHLNHbO14jhbcQ68XLGoWbWNb0WmO+iTRz72jZFiStL nqByGrMBvJTdTJ496BNLWvmuZaGkTkwE3azDFlVj2HNZrjPxpTSOuFK0GScztLfwWQx5 pgpxgOKk1DHecfRBwWL4zTS1fgTLKg34LiikGNlaMTxJTJMMcqp71iV4ntQDIqNLJyW8 ymyRfuEMspgeUFTah+F2dQWLWmd7Pb2CuCvgUN/dKtIGYNxpw8HLCGJgBewvNJjiwaR8 DoHXQ4GULIVBcYxf/b//wssI0FKW+wPnDxQIOeQIXEyDpHrCkwnT9nQ17e1XyChnQuCC /Tgg== X-Gm-Message-State: APjAAAUM+tuT4GuoAgo6bIMqlb2I4rgEja1PF6Zx+b2XoOU3G3yftzD2 jKj2V6Eak6oP20Km/FxprvqSCWMfhadeNubKOQhEYQqfQwg= X-Google-Smtp-Source: APXvYqzhYhe344yws+6ai+Wmkru769vW3ogJrfY+BxB6pl7mq6s0a5DCN32Unc3MUAQ+USJf330vdFIcey8zpsmdQ0s= X-Received: by 2002:a67:e8c3:: with SMTP id y3mr3830813vsn.140.1574288490529; Wed, 20 Nov 2019 14:21:30 -0800 (PST) MIME-Version: 1.0 References: <157428537207.30532.619903290739952848@ietfa.amsl.com> In-Reply-To: <157428537207.30532.619903290739952848@ietfa.amsl.com> From: Ori Finkelman Date: Thu, 21 Nov 2019 00:21:08 +0200 Message-ID: To: The IESG , draft-ietf-cdni-request-routing-extensions@ietf.org, Kevin Ma , cdni-chairs@ietf.org, "" , Alissa Cooper Content-Type: multipart/alternative; boundary="0000000000004089a30597ce9aa8" Archived-At: Subject: [CDNi] Fwd: I-D Action: draft-ietf-cdni-request-routing-extensions-08.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2019 22:21:38 -0000 --0000000000004089a30597ce9aa8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear all, Draf 08 was just submitted. Thanks goes to all the reviewers and commenters. As a general note, we have removed the option to advertise an IPv4 / IPv6 address in both redirect target and fallback target and left only the CNAME option. The reason is that in the CDNI docs there is only reference to CNAME option for DNS routing, not AAAA/A records, and this is also aligned with Open Caching specification. Fixes list by commenter: *Alissa Cooper* + EDNS0 client-subnet - a note was added to new section 2.1 regarding the privacy drawbacks and reference to guidance in RFC 7871. *Roman Danyliw* + EDNS0 client-subnet - see comment above. + Add references to SVA and Open Caching - added to the introduction + Typos - all fixed. *Alvaro Retana* + Add references to SVA and Open Caching - added to the introduction *=C3=89ric Vyncke*+ Router definition - Request Router definition added to section 1.1 + Switching / preserving of URI scheme - we have added a "scheme" property to the redirect target object, to determine if the scheme is preset or to be the same as the original request (if the property is absent) + Expand FCI in Abstract - done + Requirement Langague - moved to the introduction + Typos - all fixed *Benjamin Kaduk* + Geo DNS reference - there is no RFC or other official standard, instead we have added a short explanation of that we mean by "Geo DNS" + The dCDN's advertisements interaction with the uCDN's DNS redirection decision - we have elaborated more about how uCDN is expected to use the dCDN advertisement + Change reference from section 5 of RFC8008 to sections 5.1 and 5.2 of the same - accepted and done + IP address examples - see first comment in this email, we have removed the options to route to IP addresses and left only CNAME + Redirection to TLS - we have added "scheme" property to the Http redirect target. Regarding SNI, an implemenation should avoid using an IP address for hostname if it is using HTTPS, that makes certificates more complex and creates SNI problems, but that is a general issue, not specific to CDNI. + swapping of redirecting and target host in the figures - correct, I have fixed it. Thanks for catching it. + nits - all fixed + Attacks on the fallback - we have added an explanation on how the fallback should be designed to have the same level of load balancing and redundancy as the original uCDN nodes, so that the fallback would be not expose a new attack surface (beyond the original uCDN architecture) + Scheme in fallback address - the same as in the redirect target, we have added a "scheme" property. The default is to use the same scheme as the received request. One can set a specific scheme if needed using this property. Best regards, Ori ---------- Forwarded message --------- From: Date: Wed, Nov 20, 2019 at 11:29 PM Subject: [CDNi] I-D Action: draft-ietf-cdni-request-routing-extensions-08.txt To: Cc: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Content Delivery Networks Interconnection WG of the IETF. Title : CDNI Request Routing Extensions Authors : Ori Finkelman Sanjay Mishra Filename : draft-ietf-cdni-request-routing-extensions-08.txt Pages : 19 Date : 2019-11-20 Abstract: Open Caching architecture is a use case of Content Delivery Networks Interconnection (CDNI) in which the commercial Content Delivery Network (CDN) is the upstream CDN (uCDN) and the ISP caching layer serves as the downstream CDN (dCDN). The extensions specified in this document to the CDNI Metadata Interface (MI) and the Footprint and Capabilities Interface (FCI) are derived from requirements raised by Open Caching but are also applicable to CDNI use cases in general. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-request-routing-extensions= / There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-cdni-request-routing-extensions-08 https://datatracker.ietf.org/doc/html/draft-ietf-cdni-request-routing-exten= sions-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-request-routing-extensi= ons-08 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ CDNi mailing list CDNi@ietf.org https://www.ietf.org/mailman/listinfo/cdni --0000000000004089a30597ce9aa8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,
Draf 08 was just submitted.
Thanks= goes to all the reviewers and commenters.

As a ge= neral=C2=A0note, we have removed the option to advertise an IPv4 / IPv6 add= ress in both redirect target and fallback target and left only the CNAME op= tion. The reason is that in the CDNI docs there is only reference to CNAME = option for DNS routing, not AAAA/A records, and this is also aligned with O= pen Caching specification.=C2=A0

Fixes list by com= menter:

Alissa Cooper
+ EDNS0= client-subnet - a note was added to new section 2.1 regarding the privacy = drawbacks and reference to guidance in RFC 7871.

<= b>Roman Danyliw
+ EDNS0 client-subnet - see comment ab= ove.
+ Add references to SVA and Open Caching - added to the intr= oduction
+ Typos - all fixed.

Alvaro Retana
+ Add references to SVA and Open Ca= ching - added to the introduction

=C3=89ric Vyncke
+ Router definition=C2=A0- Request Rout= er definition added to section 1.1
+ Switching / preserving of UR= I scheme - we have added a "scheme" property to the redirect targ= et object, to determine if the scheme is preset or to be the same as the or= iginal request (if the property is absent)
+ Expand FCI in Ab= stract - done
+ Requirement Langague - moved to the introduct= ion
+ Typos - all fixed

Be= njamin Kaduk
+ Geo DNS reference=C2=A0
=C2= =A0 =C2=A0 =C2=A0- there is no RFC or other official standard, instead we h= ave added a short explanation of that we mean by "Geo DNS"
<= div>+ The=C2=A0dCDN's advertisements interactio= n with the uCDN's DNS redirection decision=C2=A0
=C2=A0 =C2=A0 =C2=A0- we have elaborated more about how = uCDN is expected to use the dCDN advertisement
+ Change reference from section 5 of RFC8008 to sections 5.1 a= nd 5.2 of the same=C2=A0
=C2=A0 = =C2=A0- accepted and done
+ IP= address examples - see first comment in this email, we have removed the op= tions to route to IP addresses and left only CNAME
+ Redirection to TLS=C2=A0
=C2=A0 =C2=A0- we have added "scheme" property = to the Http redirect target. Regarding SNI, an implemenation should avoid u= sing an IP address for hostname if it is using HTTPS, that makes certificat= es more complex and creates SNI problems, but that is a general issue, not = specific to CDNI.
+ swapping of redirecting and target hos= t in the figures=C2=A0 - correct, I have fixed it. Thanks for catching it.<= br>
+ nits - all fixed
+ Attacks on the fallback - = we have added an explanation on how the fallback should be designed to have= the same level of load balancing and redundancy as the original uCDN nodes= , so that the fallback would be not expose a new attack surface (beyond the= original uCDN architecture)
+ Scheme in fallback address - the s= ame as in the redirect target, we have added a "scheme" property.= The default is to use the same scheme as the received request. One can set= a specific scheme if needed using this property.

<= div>

Best regards,
Ori=C2=A0
=C2=A0 =C2=A0





---------- Forwarded message ---------
From: <internet-drafts@= ietf.org>
Date: Wed, Nov 20, 2019 at 11:29 PM
Subject: = [CDNi] I-D Action: draft-ietf-cdni-request-routing-extensions-08.txt
To:= <i-d-announce@ietf.org>= ;
Cc: <cdni@ietf.org>



A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
This draft is a work item of the Content Delivery Networks Interconnection = WG of the IETF.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= CDNI Request Routing Extensions
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Ori = Finkelman
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Sanjay Mishra
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet= f-cdni-request-routing-extensions-08.txt
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= 19
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 := 2019-11-20

Abstract:
=C2=A0 =C2=A0Open Caching architecture is a use case of Content Delivery Ne= tworks
=C2=A0 =C2=A0Interconnection (CDNI) in which the commercial Content Deliver= y
=C2=A0 =C2=A0Network (CDN) is the upstream CDN (uCDN) and the ISP caching l= ayer
=C2=A0 =C2=A0serves as the downstream CDN (dCDN).=C2=A0 The extensions spec= ified in
=C2=A0 =C2=A0this document to the CDNI Metadata Interface (MI) and the Foot= print
=C2=A0 =C2=A0and Capabilities Interface (FCI) are derived from requirements= raised
=C2=A0 =C2=A0by Open Caching but are also applicable to CDNI use cases in g= eneral.


The IETF datatracker status page for this draft is:
https://datatracker.ietf= .org/doc/draft-ietf-cdni-request-routing-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html= /draft-ietf-cdni-request-routing-extensions-08
https://datatrack= er.ietf.org/doc/html/draft-ietf-cdni-request-routing-extensions-08

A diff from the previous version is available at:
https://www.ietf.or= g/rfcdiff?url2=3Ddraft-ietf-cdni-request-routing-extensions-08


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni
--0000000000004089a30597ce9aa8--