From kleung@cisco.com Mon Dec 2 11:57:18 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF101ADEB1 for ; Mon, 2 Dec 2013 11:57:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.502 X-Spam-Level: X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 LAA6ZGlwlrUc for ; Mon, 2 Dec 2013 11:57:17 -0800 (PST) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9B21ADEA7 for ; Mon, 2 Dec 2013 11:57:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3259; q=dns/txt; s=iport; t=1386014235; x=1387223835; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aBO/BaRWfaj94lF51UOBp1H4v58e7Ckdq+Y9bHYUa2g=; b=cnHL/Etimltu5BoHNbMIDgr9szU1GoJWFGh64dNSORqOu5zRyEZ7l7i8 Ejer/1feXKNDzB8kEF+pCAOAq1OP1SVO8LV/xwjhIp+jNzEersZMcfkv1 2qnfgS+XyzH1sfeP78syhruyUGnhKKeZiyVRcSg1nUmgw8I03OO3fotpF k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag8HAObknFKtJV2Y/2dsb2JhbABZgwc4TQa4Z4EmFm0HgiUBAQEEAQEBNzQEBwwEAgEIEQQBAQsUCQcnCxQJCAIEDgUIAYd4CAXABReOVw8iBwaDGoETA5lEkGODKYIq X-IronPort-AV: E=Sophos;i="4.93,812,1378857600"; d="scan'208";a="288850994" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 02 Dec 2013 19:57:13 +0000 Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB2JvDOv008555 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Dec 2013 19:57:13 GMT Received: from xmb-aln-x03.cisco.com ([169.254.6.155]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 13:57:13 -0600 From: "Kent Leung (kleung)" To: "lapeters@akamai.com" Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-framework-07.txt Thread-Index: AQHO6fl5wTgWKN0m1UKfjMrKPZxZM5pBWeqA Date: Mon, 2 Dec 2013 19:57:12 +0000 Message-ID: References: <20131125161436.14041.97394.idtracker@ietfa.amsl.com> In-Reply-To: <20131125161436.14041.97394.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.79.199] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "cdni@ietf.org" Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-framework-07.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 02 Dec 2013 19:57:18 -0000 Hi Larry. Just a couple of nits. 1. Section 2: Trying to keep the requirements draft and framework draft in = sync. Replace the following text from: o CDNI Request Routing interface: Operations to determine what CDN (and optionally what surrogate within a CDN) is to serve end- user's requests. Is actually a logical bundling of two separate but related interfaces: to: o CDNI Request Routing interface: Operations to determine what CDN (and optionally what surrogate within a CDN) is to serve end- user's requests. This interface is actually a logical bundling of two separate but related interfaces: 2. Change: o CDNI Logging interface (LI): Operations that allow interconnected CDNs to exchange relevant activity logs. May include a combination of: to: o CDNI Logging interface (LI): Operations that allow interconnected CDNs to exchange relevant activity logs. It may include a combination of: I'll update the requirements draft to match. Kent -----Original Message----- From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: Monday, November 25, 2013 8:15 AM To: i-d-announce@ietf.org Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-framework-07.txt 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= Working Group of the IETF. Title : Framework for CDN Interconnection Author(s) : Larry Peterson Bruce Davie Filename : draft-ietf-cdni-framework-07.txt Pages : 52 Date : 2013-11-25 Abstract: This document presents a framework for Content Distribution Network Interconnection (CDNI). The purpose of the framework is to provide an overall picture of the problem space of CDNI and to describe the relationships among the various components necessary to interconnect CDNs. CDN Interconnection requires the specification of interfaces and mechanisms to address issues such as request routing, distribution metadata exchange, and logging information exchange across CDNs. The intent of this document is to outline what each interface needs to accomplish, and to describe how these interfaces and mechanisms fit together, while leaving their detailed specification to other documents. It obsoletes RFC 3466. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-framework There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cdni-framework-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-framework-07 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 From internet-drafts@ietf.org Tue Dec 3 05:52:34 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9090D1A802D; Tue, 3 Dec 2013 05:52:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 SrLc7Gn_mLsf; Tue, 3 Dec 2013 05:52:32 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9FB1AC4C1; Tue, 3 Dec 2013 05:52:32 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131203135232.29099.57672.idtracker@ietfa.amsl.com> Date: Tue, 03 Dec 2013 05:52:32 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-control-triggers-02.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Tue, 03 Dec 2013 13:52:34 -0000 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= Working Group of the IETF. Title : CDNI Control Interface / Triggers Author(s) : Rob Murray Ben Niven-Jenkins Filename : draft-ietf-cdni-control-triggers-02.txt Pages : 37 Date : 2013-12-03 Abstract: This document describes the part of the CDN Interconnect Control Interface that allows a CDN to trigger activity in an interconnected CDN that is configured to deliver content on its behalf. The upstream CDN can use this mechanism to request that the downstream CDN pre-positions metadata or content, or that it re-validate or purge metadata or content. The upstream CDN can monitor the status of activity that it has triggered in the downstream CDN. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-control-triggers There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cdni-control-triggers-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-control-triggers-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 iesg-secretary@ietf.org Fri Dec 6 09:40:34 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4301ADFC6; Fri, 6 Dec 2013 09:40:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 zfokdPfiap8m; Fri, 6 Dec 2013 09:40:31 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 013EB1AE01E; Fri, 6 Dec 2013 09:40:28 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131206174027.8405.25838.idtracker@ietfa.amsl.com> Date: Fri, 06 Dec 2013 09:40:27 -0800 Cc: cdni WG Subject: [CDNi] WG Action: Rechartered Content Delivery Networks Interconnection (cdni) X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Fri, 06 Dec 2013 17:40:34 -0000 The Content Delivery Networks Interconnection (cdni) working group in the Transport Area of the IETF has been rechartered. For additional information please contact the Area Directors or the WG Chairs. Content Delivery Networks Interconnection (cdni) ------------------------------------------------ Current Status: Active WG Chairs: Daryl Malas Francois Le Faucheur Assigned Area Director: Spencer Dawkins Mailing list Address: cdni@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/cdni Archive: http://www.ietf.org/mail-archive/web/cdni/ Charter: A Content Delivery Network (CDN) is an infrastructure of network elements operating at layer 4 through layer 7, arranged for the efficient distribution and delivery of digital content. Such content includes, but is not limited to, web pages and images delivered via HTTP, and streaming of continuous media delivered via HTTP, RTSP, RTMP, etc. CDNs typically provide services to multiple Content Service Providers (CSPs). CDNs provide numerous benefits: a shared platform for multi-service content delivery, reduced transmission costs for cacheable content, improved quality of experience for end users and increased robustness of delivery. For these reasons they are frequently used for large-scale content delivery. As a result of the significant growth in content delivered over IP networks, existing CDN providers are scaling up their infrastructure and many Network Service Providers and Enterprise Service Providers are deploying their own CDNs. Subject to the policy of the CSP, it is generally desirable that a given item of content can be delivered to an end user regardless of that end user's location or attachment network. This creates a need for interconnecting (previously) standalone CDNs so they can interoperate and collectively behave as a single delivery infrastructure. The goal of the CDNI Working Group is to allow the interconnection of separately administered CDNs in support of the end-to-end delivery of content from CSPs through multiple CDNs and ultimately to end users (via their respective User Agents). The CDNI WG aims at delivering a targeted, deployable solution in a short timeframe as needed by the industry. It is expected that the CDNI interfaces will be realized using existing IETF protocols for transport and message exchange, and using existing object notation grammars/languages for the definition of CDNI objects and semantics. In the event that protocol extensions or new protocols are deemed necessary by the WG, the WG will recharter. The working group will focus on the following items: - A "requirements" document. This document lists the requirements for the CDNI architecture and the CDNI interfaces. In particular, this document will focus on identifying a reasonable set of more urgent and important requirements that will be addressed in the initial set of CDNI protocols and solutions produced by the working group. This document will list the requirements stemming from the threat analysis and to be met by each of the CDNI interfaces. - A "framework" document providing a description of the different components of the CDNI architecture and how they interact with one another. This document will also include a "threat analysis" discussing the security concerns and threats, the trust model and privacy issues specific to CDNI. - A specification of the "CDNI Request Routing Redirection interface". This interface will allow an upstream CDN Request Routing system to obtain from the downstream CDN the information necessary to perform request redirection. It is actually a logical bundling of two separate but related interfaces: * Footprint & Capability Advertisement interface: Asynchronous operations to exchange routing information (e.g., the network footprint and capabilities served by a given CDN) that enables CDN selection for subsequent user requests; and * Request Routing Redirection interface: Synchronous operations to select a delivery CDN (surrogate) for a given user request. - A specification of the "CDNI Metadata interface". This interface will allow the CDNs to exchange content distribution metadata of inter-CDN scope. Content distribution metadata refers to the subset of content metadata that is relevant to the distribution of the content and therefore is to be processed by CDNs (for example, this may include information enabling: content acquisition, geo-blocking, enforcement of availability windows or access control). - A specification of the "CDNI Logging interface". This interface will allow CDN logging systems to exchange logging information associated with actions that are relevant across CDNs (such as content distribution, content delivery and content routing actions) for purposes of accounting, analytics, monitoring, etc. - A specification of the "CDNI Control interface". In particular, this interface will allow an upstream CDN to remove or invalidate content in a downstream CDN. - A specification for "CDNI URI Signing". This document will specify a mechanism that allows interconnected CDNs to support access control by signing content URIs. This may involve extensions to the CDNI interfaces (e.g. CDNI Metadata interface, CDNI Logging interface). The WG will discuss and address the security, management and operational issues specific to CDNI, inside the above documents and specifications. The working group will only define solutions for aspects of the CDN Interconnection problem space that require direct communication or interoperation between CDNs. In particular, the WG will not define: - New session, transport or network protocols. - New protocols for delivering content from a CDN to an End User/User Agent. - New protocols for ingestion of content or metadata between a CSP and a CDN. - New protocols for acquiring content across CDNs. - Protocols and algorithms for intra-CDN operations. - Support for Transparent Caching across CDNs. - New applications consuming CDNI logs. - Digital Right Management (DRM) mechanisms. The CDNI WG will work with other IETF WGs to assess, and where appropriate, leverage protocols developed by those WGs, in order to realize the CDNI requirements and CDNI interfaces. For example, the WG may assess the suitability of the ALTO protocol as a protocol to enable downstream CDNs to exchange information which may aid an upstream CDN with making CDNI request routing decisions. The CDNI WG will also coordinate with relevant groups outside the IETF, if and where appropriate. Milestones: Done - Submit CDNI problem statement to IESG as Informational Done - Submit CDNI use cases to IESG as Informational Sep 2013 - Submit CDNI requirements to IESG as Informational Dec 2013 - Submit CDNI framework to IESG as Informational Dec 2013 - Submit specification of the CDNI Logging interface to IESG as Proposed Standard Dec 2013 - Submit specification of the CDNI Metadata interface to IESG as Proposed Standard Apr 2014 - Submit specification of the CDNI Control interface to IESG as proposed Standard Apr 2014 - Submit specification of the CDNI Request Routing Redirection interface to IESG as Proposed Standard Sep 2014 - Submit specification of the CDNI Footprint & Capabilities Advertisement interface to IESG as Proposed Standard Sep 2014 - Submit specification of URI Signing for CDNI to IESG as Proposed Standard Oct 2014 - Recharter or dissolve From internet-drafts@ietf.org Fri Dec 6 13:35:01 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB26D1AE14D; Fri, 6 Dec 2013 13:35:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 q-8OBf0pcSvp; Fri, 6 Dec 2013 13:34:59 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 216E61AE043; Fri, 6 Dec 2013 13:34:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131206213458.31340.91161.idtracker@ietfa.amsl.com> Date: Fri, 06 Dec 2013 13:34:58 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-metadata-04.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Fri, 06 Dec 2013 21:35:01 -0000 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= Working Group of the IETF. Title : CDN Interconnect Metadata Author(s) : Ben Niven-Jenkins Rob Murray Grant Watson Matt Caulfield Kent Leung Kevin J. Ma Filename : draft-ietf-cdni-metadata-04.txt Pages : 41 Date : 2013-12-06 Abstract: The CDNI Metadata Interface enables interconnected CDNs to exchange content distribution metadata in order to enable content acquisition and delivery. The CDNI metadata associated with a piece of content provides a downstream CDN with sufficient information for the downstream CDN to service content requests on behalf of an upstream CDN. This document describes both the core set of CDNI metadata and the protocol for exchanging that metadata. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-metadata There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cdni-metadata-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-metadata-04 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 mcaulfie@cisco.com Fri Dec 6 13:40:48 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087451AD8E1 for ; Fri, 6 Dec 2013 13:40:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.502 X-Spam-Level: X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 lQYBuvV2gioE for ; Fri, 6 Dec 2013 13:40:45 -0800 (PST) Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 74DB01AE0ED for ; Fri, 6 Dec 2013 13:40:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2346; q=dns/txt; s=iport; t=1386366041; x=1387575641; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=nIIuyEFWXiBdaw84EqeDl4uTgNF8XzM/jlOYcxURpB8=; b=WuqkY2xkK3GAKY/CUzvfYqc7pHf4WPO4lgqmzX1rMn8Ncmhf0xDAqhZE lgDqtB6wA4hSXJlDXkoBU0cHYdn1w1yaASGtLgMbcgkEH7yFOKuq7UsX2 hNW+PxFBmgVivYXT0M2ZlQgPweTErrJ7vRyBEjwSGZX4CaoFafrCbeyFJ Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FACpEolKtJV2a/2dsb2JhbABZgwc4TQa5CIEjFm0HgiUBAQEEAQEBNzQXBAIBCBEEAQELFAkHJwsUCQgCBBMIAYd5CAXAXxeOXw8pBoMagRMDlDGFE5BjgymCKg X-IronPort-AV: E=Sophos;i="4.93,842,1378857600"; d="scan'208";a="289945109" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 06 Dec 2013 21:40:40 +0000 Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB6LeejZ018018 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 6 Dec 2013 21:40:40 GMT Received: from xmb-aln-x03.cisco.com ([169.254.6.155]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 15:40:39 -0600 From: "Matt Caulfield (mcaulfie)" To: "cdni@ietf.org" Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-metadata-04.txt Thread-Index: AQHO8ssG5Z8HSb/+NE2Hknx6FTuRHppHsXeg Date: Fri, 6 Dec 2013 21:40:39 +0000 Message-ID: <166EBB70C264A9479E459B01B1BA6C921DE2C4E8@xmb-aln-x03.cisco.com> References: <20131206213458.31340.91161.idtracker@ietfa.amsl.com> In-Reply-To: <20131206213458.31340.91161.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.131.76.103] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-metadata-04.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Fri, 06 Dec 2013 21:40:48 -0000 This revision of the CDNI Metadata draft attempts to address the shortcomin= gs identified during the WG meeting in Vancouver; specifically cleaning up = the IANA Considerations and adding more information on Extensibility. Pleas= e review at your convenience. Regards, Matt Caulfield -----Original Message----- From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: Friday, December 06, 2013 4:35 PM To: i-d-announce@ietf.org Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-metadata-04.txt 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= Working Group of the IETF. Title : CDN Interconnect Metadata Author(s) : Ben Niven-Jenkins Rob Murray Grant Watson Matt Caulfield Kent Leung Kevin J. Ma Filename : draft-ietf-cdni-metadata-04.txt Pages : 41 Date : 2013-12-06 Abstract: The CDNI Metadata Interface enables interconnected CDNs to exchange content distribution metadata in order to enable content acquisition and delivery. The CDNI metadata associated with a piece of content provides a downstream CDN with sufficient information for the downstream CDN to service content requests on behalf of an upstream CDN. This document describes both the core set of CDNI metadata and the protocol for exchanging that metadata. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-metadata There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cdni-metadata-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-metadata-04 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 From flefauch@cisco.com Mon Dec 9 00:15:11 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62BD21AE23B for ; Mon, 9 Dec 2013 00:15:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.501 X-Spam-Level: X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham 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 rmQAR8QWjLDB for ; Mon, 9 Dec 2013 00:15:08 -0800 (PST) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id A5FD41AE23A for ; Mon, 9 Dec 2013 00:15:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7592; q=dns/txt; s=iport; t=1386576904; x=1387786504; h=from:to:subject:date:message-id:references:mime-version; bh=ZjkSrG3ZokF7b6h3c74tM7WEcQrJshd4sMiJew6i7sY=; b=futQUE8gSZHR56TWY8f9j+p3HfGUhRxRVG6XnMEXEmgOdDd6Jr1yIGhv 5RHLXJCA4Y6G4yUlYOs6ivcx+sEQJj/8ddB563eexqa9aPpGlcGVSK6Hg VbDCUFCKYhAQdYt37Yh6fbWjQ23Oh/5UopodMxYDYoxAAN+QPWYSnRCBh 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnMFAOB6pVKtJXHB/2dsb2JhbABZgwc4TQa5FIElFm0HgiUBAQEEAQEBaxsCARkDAQIoBycLFAkIAgQTCYd5CAXAXBeOfw0KB4MagRMDmBSBMIsthTaDKYIq X-IronPort-AV: E=Sophos;i="4.93,856,1378857600"; d="scan'208,217";a="5307156" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-6.cisco.com with ESMTP; 09 Dec 2013 08:15:03 +0000 Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id rB98F3iX018325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 9 Dec 2013 08:15:03 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.250]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 02:15:03 -0600 From: "Francois Le Faucheur (flefauch)" To: "cdni@ietf.org" Thread-Topic: "Problem Details for HTTP APIs" Thread-Index: AQHO9LbCs4litgXsZ0Gn0mVBTepCxw== Date: Mon, 9 Dec 2013 08:15:02 +0000 Message-ID: <53252DC4-AE88-4BF7-8651-044C2C9E1540@cisco.com> References: <20131209055506.26533.85630.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.55.161.202] Content-Type: multipart/alternative; boundary="_000_53252DC4AE884BF78651044C2C9E1540ciscocom_" MIME-Version: 1.0 Subject: [CDNi] "Problem Details for HTTP APIs" X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 09 Dec 2013 08:15:11 -0000 --_000_53252DC4AE884BF78651044C2C9E1540ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, We've had some early discusions around the problem of conveying meaningful = error details in a flexible and extensible way, in some of our CDNI interfa= ces (e.g., CDNI Redirection Interface). I just wanted to point to draft-not= tingham-http-problem in case it can help. Cheers Francois Begin forwarded message: From: > Subject: I-D Action: draft-nottingham-http-problem-05.txt Date: 9 December 2013 06:55:06 CET To: > Reply-To: > A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : Problem Details for HTTP APIs Author(s) : Mark Nottingham Erik Wilde Filename : draft-nottingham-http-problem-05.txt Pages : 13 Date : 2013-12-08 Abstract: This document defines a "problem detail" as a way to carry machine- readable details of errors in a HTTP response, to avoid the need to invent new error response formats for HTTP APIs. Note to Readers This draft should be discussed on the apps-discuss mailing list [1]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-nottingham-http-problem There's also a htmlized version available at: http://tools.ietf.org/html/draft-nottingham-http-problem-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-nottingham-http-problem-05 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/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --_000_53252DC4AE884BF78651044C2C9E1540ciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable Folks,

We've had some early discusions around the problem of conveying meanin= gful error details in a flexible and extensible way, in some of our CDNI in= terfaces (e.g., CDNI Redirection Interface). I just wanted to point to = ;draft-nottingham-http-problem in case it can help.

Cheers

Francois


Begin forwarded message:

From: <<= a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org>=
Subject: I-= D Action: draft-nottingham-http-problem-05.txt
Date: 9 Dec= ember 2013 06:55:06 CET
To: <<= a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org>
Reply-To: <<= a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org>=


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.


Title  = ;         : Problem Details fo= r HTTP APIs
Author(s) &= nbsp;     : Mark Nottingham
            &nb= sp;            = Erik Wilde
Filename &n= bsp;      : draft-nottingham-http-problem-05.= txt
Pages  = ;         : 13
Date  =           : 2013-12-08
Abstract:
  This document defines a "problem detail" as a way to = carry machine-
  readable details of errors in a HTTP response, to avoid the nee= d to
  invent new error response formats for HTTP APIs.

Note to Readers

  This draft should be discussed on the apps-discuss mailing list= [1].


The IETF datatracker status page for this draft is:
= https://datatracker.ietf.org/doc/draft-nottingham-http-problem

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-nottingham-http-problem-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-nottingham-http-problem-05


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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--_000_53252DC4AE884BF78651044C2C9E1540ciscocom_-- From internet-drafts@ietf.org Tue Dec 24 13:35:01 2013 Return-Path: X-Original-To: cdni@ietfa.amsl.com Delivered-To: cdni@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B38921AE0E2; Tue, 24 Dec 2013 13:35:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 J6Vty1Kjkb5p; Tue, 24 Dec 2013 13:35:00 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3062D1AE0CB; Tue, 24 Dec 2013 13:35:00 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131224213459.7221.83877.idtracker@ietfa.amsl.com> Date: Tue, 24 Dec 2013 13:34:59 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-14.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 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: Tue, 24 Dec 2013 21:35:01 -0000 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= Working Group of the IETF. Title : Content Distribution Network Interconnection (CDN= I) Requirements Authors : Kent Leung Yiu Lee Filename : draft-ietf-cdni-requirements-14.txt Pages : 24 Date : 2013-12-24 Abstract: Content delivery is frequently provided by specifically architected and provisioned Content Delivery Networks (CDNs). As a result of significant growth in content delivered over IP networks, existing CDN providers are scaling up their infrastructure. Many Network Service Providers and Enterprise Service Providers are also deploying their own CDNs. To deliver contents from the Content Service Provider (CSP) to end users, the contents may traverse across multiple CDNs. This creates a need for interconnecting (previously) standalone CDNs so that they can collectively act as a single delivery platform from the CSP to the end users. The goal of the present document is to outline the requirements for the solution and interfaces to be specified by the CDNI working group. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cdni-requirements/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-cdni-requirements-14 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-14 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/