[CDNi] FW: New Version Notification for draft-he-cdni-cap-info-advertising-00.txt

On 30 Jan 2012, at = 14:37, Francois Le Faucheur wrote:

All,

This is the = start of a two-week working group last call on = draft-ietf-cdni-use-cases-03.txt:
https= ://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/

This = working group last call will end 13 Feb 2012. Please send your comments = to the CDNI mailing list.

Francois & = Rich

Begin forwarded message:

From: <gilles.bertrand@orange.com&= gt;
Date: 30 January 2012 12:12:50 CET
To: <cdni@ietf.org>
Subject: [CDNi] TR: I-D = Action: = draft-ietf-cdni-use-cases-03.txt

Hi,

W= e have submitted a revision addressing Kent's comments.

http://tools.ietf.org//rfcdiff?url1=3Dhttp://too= ls.ietf.org/id/draft-ietf-cdni-use-cases-02.txt&url2=3Dhttp://tools.ie= tf.org/id/draft-ietf-cdni-use-cases-03.txt

Best = regards,

Gilles

-----Message = d'origine-----
De : cdni-bounces@ietf.org = [mailto:cdni-bounces@ietf.org] De la part de internet-drafts@ietf.org
E= nvoy=E9 : lundi 30 janvier 2012 12:07
=C0 : i-d-announce@ietf.org
Cc = ;: cdni@ietf.org
Objet : = [CDNi] I-D Action: draft-ietf-cdni-use-cases-03.txt

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 Working Group of the IETF.

Title =           : Use Cases = for Content Delivery Network Interconnection
Author(s) =       : Gilles Bertrand
=             &n= bsp;           &nbs= p;Stephan Emile
=             &n= bsp;           &nbs= p;Grant Watson
=             &n= bsp;           &nbs= p;Trevor Burbridge
=             &n= bsp;           &nbs= p;Philip Eardley
=             &n= bsp;           &nbs= p;Kevin Ma
= Filename        : = draft-ietf-cdni-use-cases-03.txt
Pages =           : = 18
= Date =            : = 2012-01-30

  Content Delivery Networks (CDNs) are = commonly used for improving the
  End User experience of a = content delivery service, at a reasonable
  cost. = This document outlines real world use cases (not technical
=   solutions) for interconnecting CDNs. It focuses on use = cases that
  correspond to identified industry needs and = that are expected to be
  realized once a CDN = Interconnection (CDNI) solution is available.
  This = document can be used to provide guidance to the CDNI WG about
=   the interconnection arrangements to be supported and to = validate the
  requirements of the various CDNI = interfaces.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt

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

This Internet-Draft can be retrieved = at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt=

_______________________________________________
CDNi mailing = list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni
___= ____________________________________________
CDNi mailing = list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni

=

_______________________________________________=
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/ma= ilman/listinfo/cdni

In-Reply-To: <562ECB2F-4F36-4AF1-AD30-EEEC9146DCFC@cisco.com> Date: Wed, 22 Feb 2012 17:59:54 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <088BA1E4-8C19-4A43-B0EE-BBCF6D599BF0@cisco.com> References: <8E09C72DBC577D489F13A71228C0B7BF031722A3@ftrdmel0.rd.francetelecom.fr> <4715AB6C-6566-4E09-BCE1-1B7F5C604C80@cisco.com> <562ECB2F-4F36-4AF1-AD30-EEEC9146DCFC@cisco.com> To: draft-ietf-cdni-use-cases@tools.ietf.org X-Mailer: Apple Mail (2.1084) Cc: cdni@ietf.org Subject: Re: [CDNi] Working Group Last Call on draft-ietf-cdni-use-cases-03.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 22 Feb 2012 16:59:50 -0000 To cdni-use-cases authors, I had another look and here are a few additional comments: 1) references to the "CDNI Working Group": The IESG recommends we avoid referring to the Working Groups because = those are only ephemeral and will be outlasted by this document. For example: "This document can be used to provide guidance to the CDNI WG about the interconnection arrangements to be supported and to validate the requirements of the various CDNI interfaces. " I suggest this is rephrased into something like "This document can be = used to guide the definition of the requirements to be supported by the = various CDNI interfaces defined in [I-D.ietf-cdni-problem-statement]". 2) references to the "CDNI solution": The IESG requires that we do not refer to "solutions" from a given = Working Group as this is too vague and changing. For example: "It focuses on use cases that correspond to identified industry needs = and that are expected to be realized once a CDN Interconnection (CDNI) solution is available. " Perhaps this could be rephrased into something like: "It focuses on use cases that correspond to identified industry needs = and that are expected to be realized once open interfaces and protocols supporting = interconnection of CDNs are specified and implemented." 3) "1.4. The Need for CDN Interconnection Standards" I think this section is in complete overlap with the = cdni-problem-statement. In fact, it actually starts with: " The problem statement draft [I-D.ietf-cdni-problem-statement] describes extensively the CDNI problem space and explains why CDNI standards are required. " I suggest this section be removed altogether, and a reference to the = cdni-problem-statement should appear earlier in the document (i.e. in = teh first paragraphs of section 1). Cheers Francois On 22 Feb 2012, at 17:31, Francois Le Faucheur wrote: > Folks, >=20 > The Last Call period for draft-ietf-cdni-use-cases has now closed, but = we haven't received any comments, so we'll extend it until 2 March. > =20 > As per the show of hand at the last IETF meeting, quite a few of you = are familiar with this document. So can you please have a look at the = latest version and pass on your comments, or a brief statement like "I = think it's ready" or "I think it needs rework before going further", so = we can get explicit confirmation that the document is ready (or not) = from the WG perspective. >=20 > Thanks >=20 > Francois & Rich >=20 >=20 > On 30 Jan 2012, at 14:37, Francois Le Faucheur wrote: >=20 >> All, >>=20 >> This is the start of a two-week working group last call on = draft-ietf-cdni-use-cases-03.txt: >> https://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ >>=20 >> This working group last call will end 13 Feb 2012. Please send your = comments to the CDNI mailing list. >>=20 >> Francois & Rich >>=20 >>=20 >> Begin forwarded message: >>=20 >>> From: >>> Date: 30 January 2012 12:12:50 CET >>> To: >>> Subject: [CDNi] TR: I-D Action: draft-ietf-cdni-use-cases-03.txt >>>=20 >>> Hi, >>>=20 >>> We have submitted a revision addressing Kent's comments. >>>=20 >>> = http://tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-ietf-= cdni-use-cases-02.txt&url2=3Dhttp://tools.ietf.org/id/draft-ietf-cdni-use-= cases-03.txt=20 >>>=20 >>> Best regards, >>>=20 >>> Gilles >>>=20 >>>=20 >>>=20 >>>=20 >>> -----Message d'origine----- >>> De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part = de internet-drafts@ietf.org >>> Envoy=E9 : lundi 30 janvier 2012 12:07 >>> =C0 : i-d-announce@ietf.org >>> Cc : cdni@ietf.org >>> Objet : [CDNi] I-D Action: draft-ietf-cdni-use-cases-03.txt >>>=20 >>>=20 >>> 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 Working Group of the IETF. >>>=20 >>> Title : Use Cases for Content Delivery Network = Interconnection >>> Author(s) : Gilles Bertrand >>> Stephan Emile >>> Grant Watson >>> Trevor Burbridge >>> Philip Eardley >>> Kevin Ma >>> Filename : draft-ietf-cdni-use-cases-03.txt >>> Pages : 18 >>> Date : 2012-01-30 >>>=20 >>> Content Delivery Networks (CDNs) are commonly used for improving = the >>> End User experience of a content delivery service, at a reasonable >>> cost. This document outlines real world use cases (not technical >>> solutions) for interconnecting CDNs. It focuses on use cases that >>> correspond to identified industry needs and that are expected to = be >>> realized once a CDN Interconnection (CDNI) solution is available. >>> This document can be used to provide guidance to the CDNI WG about >>> the interconnection arrangements to be supported and to validate = the >>> requirements of the various CDNI interfaces. >>>=20 >>>=20 >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt >>>=20 >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>>=20 >>> This Internet-Draft can be retrieved at: >>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt >>>=20 >>> _______________________________________________ >>> CDNi mailing list >>> CDNi@ietf.org >>> https://www.ietf.org/mailman/listinfo/cdni >>> _______________________________________________ >>> CDNi mailing list >>> CDNi@ietf.org >>> https://www.ietf.org/mailman/listinfo/cdni >>=20 >>=20 >> _______________________________________________ >> CDNi mailing list >> CDNi@ietf.org >> https://www.ietf.org/mailman/listinfo/cdni >=20 >=20 > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni From flefauch@cisco.com Thu Feb 23 23:24:17 2012 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 2B04E21E801B for ; Thu, 23 Feb 2012 23:24:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.099 X-Spam-Level: X-Spam-Status: No, score=-10.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzReSqCloviP for ; Thu, 23 Feb 2012 23:24:16 -0800 (PST) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4386B21E800C for ; Thu, 23 Feb 2012 23:24:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=flefauch@cisco.com; l=469; q=dns/txt; s=iport; t=1330068256; x=1331277856; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=wu/RTbY2lm2Qoi6jCvhyd6aLVcjqjwryqeWvWuKiAp0=; b=GO7NL5xp0EUXvUv6lDopSRy9zOmZ6Wrnc/T3CV/Dckm6UGYF6kqz71AV sbtKM6zTPW+SiQFNUbgbYTaqUQ0dDZdpn6qcT2ZZKn2+07RmDLzkK7kC6 0f5rJRZLVRCi5BKg5Pl91mlh/YpFTNBw24jfzd2Y2adO4qOXh7NlvkIw/ 8=; X-IronPort-AV: E=Sophos;i="4.73,474,1325462400"; d="scan'208";a="130443103" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 24 Feb 2012 07:24:15 +0000 Received: from ams-flefauch-8715.cisco.com (ams-flefauch-8715.cisco.com [10.55.161.198]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1O7OERx012971; Fri, 24 Feb 2012 07:24:15 GMT From: Francois Le Faucheur Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Feb 2012 08:24:08 +0100 Message-Id: To: cdni@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [CDNi] Tentative CDNI sessions schedule for IETF-83 X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 24 Feb 2012 07:24:17 -0000 Hello, For information, the CDNI sessions have been tentatively scheduled to = Thursday afternoon and Friday morning. Note that this may be modified until the IETF-83 agenda is finales (on 2 = March 2012). --------------------------------------------- cdni Session 1 Thursday, Afternoon Session I 1300-1500 --------------------------------------------- cdni Session 2 Friday, Morning Session I 0900-1100 Cheers Francois & Rich= From ray.vanbrandenburg@tno.nl Fri Feb 24 08:03:04 2012 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 6D3B421F8817 for ; Fri, 24 Feb 2012 08:03:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.198 X-Spam-Level: X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[AWL=0.305, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZ16uofFQGJV for ; Fri, 24 Feb 2012 08:03:03 -0800 (PST) Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1B91321F87EB for ; Fri, 24 Feb 2012 08:03:02 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.73,476,1325458800"; d="scan'208,217";a="14618388" Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1b.tno.nl with ESMTP; 24 Feb 2012 17:03:01 +0100 Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.71]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.01.0323.003; Fri, 24 Feb 2012 17:03:01 +0100 From: "Brandenburg, R. (Ray) van" To: "cdni@ietf.org" Thread-Topic: New draft on HTTP Adaptive Streaming and CDNI Thread-Index: AQHM8w3IYRbNg6xbTEmgWw9FChCjsw== Date: Fri, 24 Feb 2012 16:03:00 +0000 Message-ID: <8855A934-878A-4B1C-BD90-C4A173288A45@tno.nl> References: <20120224155054.22549.25411.idtracker@ietfa.amsl.com> In-Reply-To: <20120224155054.22549.25411.idtracker@ietfa.amsl.com> Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_8855A934878A4B1CBD90C4A173288A45tnonl_" MIME-Version: 1.0 Subject: [CDNi] New draft on HTTP Adaptive Streaming and CDNI X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 24 Feb 2012 16:03:04 -0000 --_000_8855A934878A4B1CBD90C4A173288A45tnonl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear CDNI WG, We have just uploaded a new I-D that discusses the impact of HTTP Adaptive = Streaming on the CDNI interfaces. Our intent with this draft is not to prop= ose solutions, but to spur discussion on this topic. In order to do so, it = describes some issues that are unique to adaptive streaming in a CDNI conte= xt. Some of the topics discussed might also be relevant when discussing the= CDNI Framework draft. Please review the draft and if you have any comments, lets discuss them on = the list. @Chairs, if possible I would be available for giving a short presentation o= n this draft during the upcoming Paris meeting. Best regards, Ray van Brandenburg Begin forwarded message: From: > Date: 24 februari 2012 16:50:54 GMT+01:00 To: > Cc: > Subject: New Version Notification for draft-brandenburg-cdni-has-00.txt A new version of I-D, draft-brandenburg-cdni-has-00.txt has been successful= ly submitted by Ray Brandenburg and posted to the IETF repository. Filename: draft-brandenburg-cdni-has Revision: 00 Title: Models for adaptive-streaming-aware CDN Interconnection Creation date: 2012-02-24 WG ID: Individual Submission Number of pages: 15 Abstract: This documents presents thougths on the potential impact of supporting HTTP Adaptive Streaming technologies in CDN Interconnection scenarios. Our intent is to spur discussion on how the different CDNI interfaces should deal with content delivered using adaptive streaming technologies. The IETF Secretariat This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer --_000_8855A934878A4B1CBD90C4A173288A45tnonl_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear CDNI WG,

We have just uploaded a new I-D that discusses the impact of HTTP Adap= tive Streaming on the CDNI interfaces. Our intent with this draft is n= ot to propose solutions, but to spur discussion on this topic. In order to = do so, it describes some issues that are unique to adaptive streaming in a CDNI context. Some of the topics dis= cussed might also be relevant when discussing the CDNI Framework draft.&nbs= p;

Please review the draft and if you have any comments, lets discuss the= m on the list.

@Chairs, if possible I would be available for giving a short presentat= ion on this draft during the upcoming Paris meeting.

Best regards,

Ray van Brandenburg

Begin forwarded message:

From: <internet-= drafts@ietf.org>
Date: 24 februari 2012 16:50:54 GMT+01:00
To: <ray.vanbrandenb= urg@tno.nl>
Cc: <ray.vanbrandenb= urg@tno.nl>
Subject: New Version Notification for draft-brandenburg-cdni-has-= 00.txt

A new version of I-D, draft-brandenburg-cdni-has-00.txt has been= successfully submitted by Ray Brandenburg and posted to the IETF repositor= y.

Filename: draft-brandenburg-cdni-has
Revision: 00
Title: Models for adaptive-streaming-awar= e CDN Interconnection
Creation date: 2012-02-24
WG ID: Individual Submission
Number of pages: 15

Abstract:
  This documents presents thougths on the potential impact = of
  supporting HTTP Adaptive Streaming technologies in CDN
  Interconnection scenarios. Our intent is to spur di= scussion on how
  the different CDNI interfaces should deal with content de= livered
  using adaptive streaming technologies.

The IETF Secretariat

This e-mail and its contents are subject to the DI= SCLAIMER at http://www.tno.nl/emaildisclaimer --_000_8855A934878A4B1CBD90C4A173288A45tnonl_-- From ray.vanbrandenburg@tno.nl Fri Feb 24 08:09:39 2012 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 5423821F84D7 for ; Fri, 24 Feb 2012 08:09:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.242 X-Spam-Level: X-Spam-Status: No, score=-0.242 tagged_above=-999 required=5 tests=[AWL=0.261, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRxaw+HIXmJ2 for ; Fri, 24 Feb 2012 08:09:38 -0800 (PST) Received: from fromintouta.tno.nl (fromintouta.tno.nl [134.221.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 9954721F867C for ; Fri, 24 Feb 2012 08:09:37 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.73,476,1325458800"; d="scan'208,217";a="64921931" Received: from unknown (HELO mail.tno.nl) ([134.221.225.221]) by mailhost1a.tno.nl with ESMTP; 24 Feb 2012 17:09:31 +0100 Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.71]) by EXC-CASHUB02.tsn.tno.nl ([134.221.225.221]) with mapi id 14.01.0323.003; Fri, 24 Feb 2012 17:09:30 +0100 From: "Brandenburg, R. (Ray) van" To: "cdni@ietf.org" Thread-Topic: [CDNi] New draft on HTTP Adaptive Streaming and CDNI Thread-Index: AQHM8w6w4C0IHqR160O72O9u7kWkMg== Date: Fri, 24 Feb 2012 16:09:29 +0000 Message-ID: <5DC46020-8C6F-44D8-9524-2AB73C390ADB@tno.nl> References: <20120224155054.22549.25411.idtracker@ietfa.amsl.com>, <8855A934-878A-4B1C-BD90-C4A173288A45@tno.nl> In-Reply-To: <8855A934-878A-4B1C-BD90-C4A173288A45@tno.nl> Accept-Language: en-US, nl-NL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_5DC460208C6F44D895242AB73C390ADBtnonl_" MIME-Version: 1.0 Subject: Re: [CDNi] New draft on HTTP Adaptive Streaming and CDNI X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 24 Feb 2012 16:09:39 -0000 --_000_5DC460208C6F44D895242AB73C390ADBtnonl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable And the URL, for extra convenience: http://tools.ietf.org/id/draft-brandenburg-cdni-has-00.txt Ray On 24 feb. 2012, at 17:03, "Brandenburg, R. (Ray) van" > wrote: Dear CDNI WG, We have just uploaded a new I-D that discusses the impact of HTTP Adaptive = Streaming on the CDNI interfaces. Our intent with this draft is not to prop= ose solutions, but to spur discussion on this topic. In order to do so, it = describes some issues that are unique to adaptive streaming in a CDNI conte= xt. Some of the topics discussed might also be relevant when discussing the= CDNI Framework draft. Please review the draft and if you have any comments, lets discuss them on = the list. @Chairs, if possible I would be available for giving a short presentation o= n this draft during the upcoming Paris meeting. Best regards, Ray van Brandenburg Begin forwarded message: From: > Date: 24 februari 2012 16:50:54 GMT+01:00 To: > Cc: > Subject: New Version Notification for draft-brandenburg-cdni-has-00.txt A new version of I-D, draft-brandenburg-cdni-has-00.txt has been successful= ly submitted by Ray Brandenburg and posted to the IETF repository. Filename: draft-brandenburg-cdni-has Revision: 00 Title: Models for adaptive-streaming-aware CDN Interconnection Creation date: 2012-02-24 WG ID: Individual Submission Number of pages: 15 Abstract: This documents presents thougths on the potential impact of supporting HTTP Adaptive Streaming technologies in CDN Interconnection scenarios. Our intent is to spur discussion on how the different CDNI interfaces should deal with content delivered using adaptive streaming technologies. The IETF Secretariat This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/emaildisclaimer _______________________________________________ CDNi mailing list CDNi@ietf.org https://www.ietf.org/mailman/listinfo/cdni --_000_5DC460208C6F44D895242AB73C390ADBtnonl_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

And the URL, for extra convenience:

http://tools.ietf.org/id/draft-brandenburg-cdni-has-00.txt

Ray

On 24 feb. 2012, at 17:03, "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl> wr= ote:

Dear CDNI WG,

We have just uploaded a new I-D that discusses the impact of HTTP Adap= tive Streaming on the CDNI interfaces. Our intent with this draft is n= ot to propose solutions, but to spur discussion on this topic. In order to = do so, it describes some issues that are unique to adaptive streaming in a CDNI context. Some of the topics dis= cussed might also be relevant when discussing the CDNI Framework draft.&nbs= p;

Please review the draft and if you have any comments, lets discuss the= m on the list.

@Chairs, if possible I would be available for giving a short presentat= ion on this draft during the upcoming Paris meeting.

Best regards,

Ray van Brandenburg

Begin forwarded message:

From: <internet-= drafts@ietf.org>
Date: 24 februari 2012 16:50:54 GMT+01:00
To: <ray.vanbrandenb= urg@tno.nl>
Cc: <ray.vanbrandenb= urg@tno.nl>
Subject: New Version Notification for draft-brandenburg-cdni-has-= 00.txt

A new version of I-D, draft-brandenburg-cdni-has-00.txt has been= successfully submitted by Ray Brandenburg and posted to the IETF repositor= y.

Filename: draft-brandenburg-cdni-has
Revision: 00
Title: Models for adaptive-streaming-awar= e CDN Interconnection
Creation date: 2012-02-24
WG ID: Individual Submission
Number of pages: 15

Abstract:
  This documents presents thougths on the potential impact = of
  supporting HTTP Adaptive Streaming technologies in CDN
  Interconnection scenarios. Our intent is to spur di= scussion on how
  the different CDNI interfaces should deal with content de= livered
  using adaptive streaming technologies.

The IETF Secretariat

This e-mail and its contents are subject to the DI= SCLAIMER at http://www.tno.nl/emaildiscla= imer

_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ie= tf.org/mailman/listinfo/cdni

--_000_5DC460208C6F44D895242AB73C390ADBtnonl_-- From flefauch@cisco.com Fri Feb 24 08:36:28 2012 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 441E321F87E4 for ; Fri, 24 Feb 2012 08:36:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.117 X-Spam-Level: X-Spam-Status: No, score=-10.117 tagged_above=-999 required=5 tests=[AWL=0.481, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwmkKWGAKiSN for ; Fri, 24 Feb 2012 08:36:27 -0800 (PST) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4C51421F87C8 for ; Fri, 24 Feb 2012 08:36:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=flefauch@cisco.com; l=6375; q=dns/txt; s=iport; t=1330101368; x=1331310968; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=IvV85yQaXkACQc3pTXYox8+MrrxmKD5+B6Mu+W8IQ0o=; b=lbOqJppNnaWSJLCXNzhjPhKn9AaJTo/dBhHwM+IWuR8pvQyHQlvrLxhH Zy2L7WRNv+ELbQUG/bKEc90PFchlB1+nqLhd7tJ09DqwH8oNsbnrGtZ5K IfEfJ6uQ/WklDPDIgBThrnhh+zsuW6AZqB1WfM+o9LQ0wSPWXPvwrJpuJ I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAFO7R0+Q/khL/2dsb2JhbABDsxiBB4FzAQEBAwEBAQEPAVsLBQsLEQMBAi8nKAgGARIbB4dfBQugNgGWfol4gwMKBgICBgQBBgEJBgIYFAsRCAEMCoRSIxcGGQUJCgUMDAYIEgyCTWMElTuScIFb X-IronPort-AV: E=Sophos;i="4.73,476,1325462400"; d="scan'208,217";a="130516574" Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 24 Feb 2012 16:36:03 +0000 Received: from ams-flefauch-8715.cisco.com (ams-flefauch-8715.cisco.com [10.55.161.198]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1OGa2tj008568; Fri, 24 Feb 2012 16:36:02 GMT Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-143--393146461 From: Francois Le Faucheur In-Reply-To: <8855A934-878A-4B1C-BD90-C4A173288A45@tno.nl> Date: Fri, 24 Feb 2012 17:36:11 +0100 Message-Id: <0505CCB8-C4CF-4154-ABBB-23EC19891E92@cisco.com> References: <20120224155054.22549.25411.idtracker@ietfa.amsl.com> <8855A934-878A-4B1C-BD90-C4A173288A45@tno.nl> To: Aaron Falk , Bruce Davie , Larry Peterson , "Brandenburg, R. (Ray) van" X-Mailer: Apple Mail (2.1084) Cc: cdni@ietf.org Subject: Re: [CDNi] New draft on HTTP Adaptive Streaming and CDNI X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 24 Feb 2012 16:36:28 -0000 --Apple-Mail-143--393146461 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, As discussed earlier on the list, I believe we agreed that = cdni-framework would discuss adaptive streaming and how it impacts the = CDNI solution. So this new document may provide additional input in that = exercise. Cheers Francois On 24 Feb 2012, at 17:03, Brandenburg, R. (Ray) van wrote: > Dear CDNI WG, >=20 > We have just uploaded a new I-D that discusses the impact of HTTP = Adaptive Streaming on the CDNI interfaces. Our intent with this draft is = not to propose solutions, but to spur discussion on this topic. In order = to do so, it describes some issues that are unique to adaptive streaming = in a CDNI context. Some of the topics discussed might also be relevant = when discussing the CDNI Framework draft.=20 >=20 > Please review the draft and if you have any comments, lets discuss = them on the list. >=20 > @Chairs, if possible I would be available for giving a short = presentation on this draft during the upcoming Paris meeting. >=20 > Best regards, >=20 > Ray van Brandenburg >=20 >=20 >=20 > Begin forwarded message: >=20 >> From: >> Date: 24 februari 2012 16:50:54 GMT+01:00 >> To: >> Cc: >> Subject: New Version Notification for = draft-brandenburg-cdni-has-00.txt >>=20 >> A new version of I-D, draft-brandenburg-cdni-has-00.txt has been = successfully submitted by Ray Brandenburg and posted to the IETF = repository. >>=20 >> Filename: draft-brandenburg-cdni-has >> Revision: 00 >> Title: Models for adaptive-streaming-aware CDN = Interconnection >> Creation date: 2012-02-24 >> WG ID: Individual Submission >> Number of pages: 15 >>=20 >> Abstract: >> This documents presents thougths on the potential impact of >> supporting HTTP Adaptive Streaming technologies in CDN >> Interconnection scenarios. Our intent is to spur discussion on how >> the different CDNI interfaces should deal with content delivered >> using adaptive streaming technologies. >>=20 >>=20 >>=20 >>=20 >> The IETF Secretariat > This e-mail and its contents are subject to the DISCLAIMER at = http://www.tno.nl/emaildisclaimer > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni --Apple-Mail-143--393146461 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi,

As discussed earlier on the list, I believe we agreed that cdni-framework would discuss adaptive streaming and how it impacts the CDNI solution. So this new document may provide additional input in that exercise.

Cheers

Francois

On 24 Feb 2012, at 17:03, Brandenburg, R. (Ray) van wrote:

Dear CDNI WG,

We have just uploaded a new I-D that discusses the impact of HTTP Adaptive Streaming on the CDNI interfaces. Our intent with this draft is not to propose solutions, but to spur discussion on this topic. In order to do so, it describes some issues that are unique to adaptive streaming in a CDNI context. Some of the topics discussed might also be relevant when discussing the CDNI Framework draft.

Please review the draft and if you have any comments, lets discuss them on the list.

@Chairs, if possible I would be available for giving a short presentation on this draft during the upcoming Paris meeting.

Best regards,

Ray van Brandenburg

Begin forwarded message:

From: <internet-drafts@ietf.org>
Date: 24 februari 2012 16:50:54 GMT+01:00
To: <ray.vanbrandenburg@tno.nl>
Cc: <ray.vanbrandenburg@tno.nl>
Subject: New Version Notification for draft-brandenburg-cdni-has-00.txt

A new version of I-D, draft-brandenburg-cdni-has-00.txt has been successfully submitted by Ray Brandenburg and posted to the IETF repository.

Filename: draft-brandenburg-cdni-has
Revision: 00
Title: Models for adaptive-streaming-aware CDN Interconnection
Creation date: 2012-02-24
WG ID: Individual Submission
Number of pages: 15

Abstract:
  This documents presents thougths on the potential impact of
  supporting HTTP Adaptive Streaming technologies in CDN
  Interconnection scenarios. Our intent is to spur discussion on how
  the different CDNI interfaces should deal with content delivered
  using adaptive streaming technologies.

The IETF Secretariat

This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer
_______________________________________________
CDNi mailing list
CDNi@ietf.org
https://www.ietf.org/mailman/listinfo/cdni

--Apple-Mail-143--393146461-- From gilles.bertrand@orange.com Mon Feb 27 07:39:19 2012 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 9E8D321F8742 for ; Mon, 27 Feb 2012 07:39:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.841 X-Spam-Level: X-Spam-Status: No, score=-5.841 tagged_above=-999 required=5 tests=[AWL=0.408, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7zEP-Nuu+Gr for ; Mon, 27 Feb 2012 07:39:17 -0800 (PST) Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id 494F421F8730 for ; Mon, 27 Feb 2012 07:39:00 -0800 (PST) Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 719175D88DF; Mon, 27 Feb 2012 16:38:58 +0100 (CET) Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 64DF35D86E4; Mon, 27 Feb 2012 16:38:58 +0100 (CET) Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Feb 2012 16:38:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 27 Feb 2012 16:38:37 +0100 Message-ID: <8E09C72DBC577D489F13A71228C0B7BF032C4A5B@ftrdmel0.rd.francetelecom.fr> In-Reply-To: <088BA1E4-8C19-4A43-B0EE-BBCF6D599BF0@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [CDNi] Working Group Last Call ondraft-ietf-cdni-use-cases-03.txt Thread-Index: Aczxg2X6yuT05G8CRyWxes/5hNtU6wD4fNYw References: <8E09C72DBC577D489F13A71228C0B7BF031722A3@ftrdmel0.rd.francetelecom.fr><4715AB6C-6566-4E09-BCE1-1B7F5C604C80@cisco.com><562ECB2F-4F36-4AF1-AD30-EEEC9146DCFC@cisco.com> <088BA1E4-8C19-4A43-B0EE-BBCF6D599BF0@cisco.com> From: To: , X-OriginalArrivalTime: 27 Feb 2012 15:38:58.0144 (UTC) FILETIME=[EBADCE00:01CCF565] Cc: cdni@ietf.org Subject: Re: [CDNi] Working Group Last Call ondraft-ietf-cdni-use-cases-03.txt X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 27 Feb 2012 15:39:20 -0000 Hi Fran=E7ois, thanks for this review.=20 We will wait for any other comment on the list until march 2nd (end of = extended last-call period) and submit a final revision. Best regards, Gilles -----Message d'origine----- De=A0: cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part = de Francois Le Faucheur Envoy=E9=A0: mercredi 22 f=E9vrier 2012 18:00 =C0=A0: draft-ietf-cdni-use-cases@tools.ietf.org Cc=A0: cdni@ietf.org Objet=A0: Re: [CDNi] Working Group Last Call = ondraft-ietf-cdni-use-cases-03.txt To cdni-use-cases authors, I had another look and here are a few additional comments: 1) references to the "CDNI Working Group": The IESG recommends we avoid referring to the Working Groups because = those are only ephemeral and will be outlasted by this document. For example: "This document can be used to provide guidance to the CDNI WG about the interconnection arrangements to be supported and to validate the requirements of the various CDNI interfaces. " I suggest this is rephrased into something like "This document can be = used to guide the definition of the requirements to be supported by the = various CDNI interfaces defined in [I-D.ietf-cdni-problem-statement]". 2) references to the "CDNI solution": The IESG requires that we do not refer to "solutions" from a given = Working Group as this is too vague and changing. For example: "It focuses on use cases that correspond to identified industry needs = and that are expected to be realized once a CDN Interconnection (CDNI) solution is available. " Perhaps this could be rephrased into something like: "It focuses on use cases that correspond to identified industry needs = and that are expected to be realized once open interfaces and protocols supporting = interconnection of CDNs are specified and implemented." 3) "1.4. The Need for CDN Interconnection Standards" I think this section is in complete overlap with the = cdni-problem-statement. In fact, it actually starts with: " The problem statement draft [I-D.ietf-cdni-problem-statement] describes extensively the CDNI problem space and explains why CDNI standards are required. " I suggest this section be removed altogether, and a reference to the = cdni-problem-statement should appear earlier in the document (i.e. in = teh first paragraphs of section 1). Cheers Francois On 22 Feb 2012, at 17:31, Francois Le Faucheur wrote: > Folks, >=20 > The Last Call period for draft-ietf-cdni-use-cases has now closed, but = we haven't received any comments, so we'll extend it until 2 March. > =20 > As per the show of hand at the last IETF meeting, quite a few of you = are familiar with this document. So can you please have a look at the = latest version and pass on your comments, or a brief statement like "I = think it's ready" or "I think it needs rework before going further", so = we can get explicit confirmation that the document is ready (or not) = from the WG perspective. >=20 > Thanks >=20 > Francois & Rich >=20 >=20 > On 30 Jan 2012, at 14:37, Francois Le Faucheur wrote: >=20 >> All, >>=20 >> This is the start of a two-week working group last call on = draft-ietf-cdni-use-cases-03.txt: >> https://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ >>=20 >> This working group last call will end 13 Feb 2012. Please send your = comments to the CDNI mailing list. >>=20 >> Francois & Rich >>=20 >>=20 >> Begin forwarded message: >>=20 >>> From: >>> Date: 30 January 2012 12:12:50 CET >>> To: >>> Subject: [CDNi] TR: I-D Action: draft-ietf-cdni-use-cases-03.txt >>>=20 >>> Hi, >>>=20 >>> We have submitted a revision addressing Kent's comments. >>>=20 >>> = http://tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-i >>> = etf-cdni-use-cases-02.txt&url2=3Dhttp://tools.ietf.org/id/draft-ietf-c >>> dni-use-cases-03.txt >>>=20 >>> Best regards, >>>=20 >>> Gilles >>>=20 >>>=20 >>>=20 >>>=20 >>> -----Message d'origine----- >>> De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la part = >>> de internet-drafts@ietf.org Envoy=E9 : lundi 30 janvier 2012 12:07 = =C0 :=20 >>> i-d-announce@ietf.org Cc : cdni@ietf.org Objet : [CDNi] I-D Action:=20 >>> draft-ietf-cdni-use-cases-03.txt >>>=20 >>>=20 >>> 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 Working Group of the IETF. >>>=20 >>> Title : Use Cases for Content Delivery Network = Interconnection >>> Author(s) : Gilles Bertrand >>> Stephan Emile >>> Grant Watson >>> Trevor Burbridge >>> Philip Eardley >>> Kevin Ma >>> Filename : draft-ietf-cdni-use-cases-03.txt >>> Pages : 18 >>> Date : 2012-01-30 >>>=20 >>> Content Delivery Networks (CDNs) are commonly used for improving = the >>> End User experience of a content delivery service, at a reasonable >>> cost. This document outlines real world use cases (not technical >>> solutions) for interconnecting CDNs. It focuses on use cases that >>> correspond to identified industry needs and that are expected to = be >>> realized once a CDN Interconnection (CDNI) solution is available. >>> This document can be used to provide guidance to the CDNI WG about >>> the interconnection arrangements to be supported and to validate = the >>> requirements of the various CDNI interfaces. >>>=20 >>>=20 >>> A URL for this Internet-Draft is: >>> http://www.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt >>>=20 >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>>=20 >>> This Internet-Draft can be retrieved at: >>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt >>>=20 >>> _______________________________________________ >>> CDNi mailing list >>> CDNi@ietf.org >>> https://www.ietf.org/mailman/listinfo/cdni >>> _______________________________________________ >>> CDNi mailing list >>> CDNi@ietf.org >>> https://www.ietf.org/mailman/listinfo/cdni >>=20 >>=20 >> _______________________________________________ >> CDNi mailing list >> CDNi@ietf.org >> https://www.ietf.org/mailman/listinfo/cdni >=20 >=20 > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni _______________________________________________ CDNi mailing list CDNi@ietf.org https://www.ietf.org/mailman/listinfo/cdni From Jan.Seedorf@neclab.eu Tue Feb 28 06:54:24 2012 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 5B2D121F8513 for ; Tue, 28 Feb 2012 06:54:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trA3u94SMwJM for ; Tue, 28 Feb 2012 06:54:23 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 47F7921F848A for ; Tue, 28 Feb 2012 06:54:23 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 75391280000F8; Tue, 28 Feb 2012 15:54:22 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0P6fg7Pa8+o6; Tue, 28 Feb 2012 15:54:22 +0100 (CET) Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 5726628000084; Tue, 28 Feb 2012 15:54:12 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.41]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Tue, 28 Feb 2012 15:53:51 +0100 From: Jan Seedorf To: Ina Minei , "cdni@ietf.org" Thread-Topic: Question regarding downstream CDN selection Thread-Index: AczoAzqhH0Gxf7unQsKRfBfXt4YXFQAFyaQQA4NenDA= Date: Tue, 28 Feb 2012 14:53:51 +0000 Message-ID: <2779C9F0771F974CAD742BAE6D9904FE24F11CAE@DAPHNIS.office.hd> References: <2779C9F0771F974CAD742BAE6D9904FE24EE7153@PALLENE.office.hd> <189716C74BBB9C4095FE8CA503B1FC3A5762A589C0@EMBX02-HQ.jnpr.net> In-Reply-To: <189716C74BBB9C4095FE8CA503B1FC3A5762A589C0@EMBX02-HQ.jnpr.net> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.227] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [CDNi] Question regarding downstream CDN selection X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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: Tue, 28 Feb 2012 14:54:24 -0000 Dear Ina, Thanks for your reply and sorry for my late answer. From your answer, it se= ems my description of the two different models was clear :), which is good. Still, my question to this WG remains: do we assume either model or are we = considering both of them? And if we consider the second model (independent agreements with CP), is th= e fact that a dCDN can serve content for a given CP part of the "capabiliti= es" part of the request routing interface? - Jan > -----Original Message----- > From: Ina Minei [mailto:ina@juniper.net] > Sent: Friday, February 10, 2012 7:17 PM > To: Jan Seedorf; cdni@ietf.org > Subject: RE: Question regarding downstream CDN selection >=20 > Jan, >=20 > The answer to that question depends on how you assume redirection is > done in the case you are describing, and I think this boils down to the > different models of CDN federations. >=20 > The first (the one described in the quote), relies on bilateral agreement= s. In > that case, the request is redirected to the authoritative, who will redi= rect to > the best downstream. >=20 > The second model (the one you describe), sounds like an exchange model, > with multiple members of the exchange having a relation to the same CSP, > and the request being redirected to a coordinating entity for the exchang= e. > In the second case, as you are pointing out, user location information is= not > enough to determine the CDN from which the content will be served > (because that CDN may not be serving content for the CSP), and the set of > candidate CDNs has to be determined based on the content. >=20 > Ina >=20 > -----Original Message----- > From: cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] On Behalf Of > Jan Seedorf > Sent: Friday, February 10, 2012 6:58 AM > To: cdni@ietf.org > Subject: [CDNi] Question regarding downstream CDN selection >=20 > Folks, >=20 > I have a question regarding downstream CDN selection. The introduction of > the CDNI problem statement draft says: "As an example, a CSP could contra= ct > with an "authoritative" CDN Provider for the delivery of content and that > authoritative CDN Provider could contract with one or more downstream > CDN Provider(s) to distribute and deliver some or all of the content on b= ehalf > of the authoritative CDN Provider. The formation and details of any busi= ness > relationships between a CSP and a CDN Provider and between one CDN > Provider and another CDN Provider are out of scope of this document. > However, no standards or open specifications currently exist to facilitat= e such > CDN interconnection." >=20 > My question is if we always assume this model, where there is an > "authoritative" CDN provider which transitively has itself contracted sev= eral > downstream CDN providers. Or do we account for the possibility that > potentially a CSP has own its own made several independent agreements > with other CDNs (e.g. because they are covering different geographical > areas). If we want to consider the latter case, how does the upstream CDN > know for a given downstream CDN if it serves the content for a given CSP? >=20 > - Jan >=20 > > -----Original Message----- > > From: cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] On Behalf Of > > Francois Le Faucheur > > Sent: Monday, January 30, 2012 2:38 PM > > To: cdni@ietf.org > > Subject: [CDNi] Working Group Last Call on draft-ietf-cdni-use-cases-03= .txt > > > > All, > > > > This is the start of a two-week working group last call on draft-ietf-c= dni- > use- > > cases-03.txt: > > https://datatracker.ietf.org/doc/draft-ietf-cdni-use-cases/ > > > > This working group last call will end 13 Feb 2012. Please send your > comments > > to the CDNI mailing list. > > > > Francois & Rich > > > > > > Begin forwarded message: > > > > > > From: > > > > Date: 30 January 2012 12:12:50 CET > > > > To: > > > > Subject: [CDNi] TR: I-D Action: draft-ietf-cdni-use-cases-03.txt > > > > > > Hi, > > > > We have submitted a revision addressing Kent's comments. > > > > http://tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-i= etf- > > cdni-use-cases-02.txt&url2=3Dhttp://tools.ietf.org/id/draft-ietf-cdni-u= se- > > cases-03.txt > > > > Best regards, > > > > Gilles > > > > > > > > > > -----Message d'origine----- > > De : cdni-bounces@ietf.org [mailto:cdni-bounces@ietf.org] De la > > part de internet-drafts@ietf.org > > Envoy=E9 : lundi 30 janvier 2012 12:07 > > =C0 : i-d-announce@ietf.org > > Cc : cdni@ietf.org > > Objet : [CDNi] I-D Action: draft-ietf-cdni-use-cases-03.txt > > > > > > 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 Working Group of the IETF. > > > > Title : Use Cases for Content Delivery Network Interconnecti= on > > Author(s) : Gilles Bertrand > > Stephan Emile > > Grant Watson > > Trevor Burbridge > > Philip Eardley > > Kevin Ma > > Filename : draft-ietf-cdni-use-cases-03.txt > > Pages : 18 > > Date : 2012-01-30 > > > > Content Delivery Networks (CDNs) are commonly used for > > improving the > > End User experience of a content delivery service, at a reasonable > > cost. This document outlines real world use cases (not technical > > solutions) for interconnecting CDNs. It focuses on use cases that > > correspond to identified industry needs and that are expected to be > > realized once a CDN Interconnection (CDNI) solution is available. > > This document can be used to provide guidance to the CDNI WG > > about > > the interconnection arrangements to be supported and to validate > > the > > requirements of the various CDNI interfaces. > > > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > This Internet-Draft can be retrieved at: > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-cdni-use-cases-03.txt > > > > _______________________________________________ > > CDNi mailing list > > CDNi@ietf.org > > https://www.ietf.org/mailman/listinfo/cdni > > _______________________________________________ > > CDNi mailing list > > CDNi@ietf.org > > https://www.ietf.org/mailman/listinfo/cdni > > > > > > >=20 > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni From Jan.Seedorf@neclab.eu Tue Feb 28 08:15:19 2012 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 B1AA421F864E for ; Tue, 28 Feb 2012 08:15:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zu12zjJYet4Z for ; Tue, 28 Feb 2012 08:15:18 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id AD65121F85D8 for ; Tue, 28 Feb 2012 08:15:18 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 1D5BA280000F8; Tue, 28 Feb 2012 17:15:18 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PZAOUhhyMLG; Tue, 28 Feb 2012 17:15:18 +0100 (CET) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id F306F28000084; Tue, 28 Feb 2012 17:14:57 +0100 (CET) Received: from DAPHNIS.office.hd ([169.254.2.41]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 28 Feb 2012 17:14:53 +0100 From: Jan Seedorf To: "stefano previdi (sprevidi@cisco.com)" , "flefauch@cisco.com" , "jmedved@juniper.net" , "cdni@ietf.org" Thread-Topic: Questions on draft-previdi-cdni-footprint-advertisement-00 Thread-Index: Acz2Lv2ue6S3SGEmQby1HP94jyog0Q== Date: Tue, 28 Feb 2012 16:14:56 +0000 Message-ID: <2779C9F0771F974CAD742BAE6D9904FE24F11D2A@DAPHNIS.office.hd> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.2.227] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [CDNi] Questions on draft-previdi-cdni-footprint-advertisement-00 X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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: Tue, 28 Feb 2012 16:15:19 -0000 Dear authors of the BGP CDNI Footprint Advertisement draft, I have some questions, maybe you can clarify: -- BGP communities are currently used per AS, e.g. 100:500 means AS 100 is = attaching a value of 100 to a given route. In your scheme, do you intend to= use communities per footprint identifier, e.g. 100:200:300 means AS 100 is= attaching a value of 300 for footprint identifier 100:200? -- section 4.2.3 says " The CDNI Connectivity Advertisement contains a new = (TBD) attribute called Origin_AS_PATH that contains the AS_PATH value descr= ibing the distance (expressed in AS Hop Count) between the CDN and the adve= rtised connected footprint."; in the examples in section 7, however, Origin= _AS_PATH is not the AS hop count but the ID of the source AS; I assume it i= s a mistake in the example, correct? -- in your scheme, how can you explicitly express costs (e.g. latency, band= width, monetary costs, ...) to a certain footprint identifier? I understand= a ranking, but it is not clear to me how you express explicit costs. Via a= n extended community value per footprint identifier? -- what is confusing to me is that original BGP connectivity refers to AS-l= evel routing, while CDN connectivity to me is (in principle) quite independ= ent from AS-level routing. For instance, I can very well imagine 2 CDNs whi= ch have a direct bilateral CDN-interconnection agreement, but which have ma= ny AS-hops between their footprints. So the connectivity via AS-level BGP f= ootprints is very confusing to me. Maybe you can explain it. Thanks for answering, - Jan From sprevidi@cisco.com Tue Feb 28 09:55:49 2012 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 87C8E21F8699 for ; Tue, 28 Feb 2012 09:55:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.499 X-Spam-Level: X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QqU+4lzpyWFf for ; Tue, 28 Feb 2012 09:55:48 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id C491D21F8551 for ; Tue, 28 Feb 2012 09:55:47 -0800 (PST) X-TACSUNS: Virus Scanned Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q1SHtCBl008980 for ; Tue, 28 Feb 2012 18:55:12 +0100 (CET) Received: from dhcp-10-55-89-11.cisco.com (dhcp-10-55-89-11.cisco.com [10.55.89.11]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q1SHt9Zv011596; Tue, 28 Feb 2012 18:55:10 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: stefano previdi In-Reply-To: <2779C9F0771F974CAD742BAE6D9904FE24F11D2A@DAPHNIS.office.hd> Date: Tue, 28 Feb 2012 18:55:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <075049AD-E2B9-40DA-8900-F54E7B6AF64E@cisco.com> References: <2779C9F0771F974CAD742BAE6D9904FE24F11D2A@DAPHNIS.office.hd> To: Jan Seedorf X-Mailer: Apple Mail (2.1257) Cc: Jan Medved , cdni@ietf.org Subject: Re: [CDNi] Questions on draft-previdi-cdni-footprint-advertisement-00 X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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: Tue, 28 Feb 2012 17:55:49 -0000 Hi Jan, I'm in the process of submitting version 01 which has some changes in=20 terminology and encoding options. I'll try to address your questions=20 below. On Feb 28, 2012, at 5:14 PM, Jan Seedorf wrote: > Dear authors of the BGP CDNI Footprint Advertisement draft, >=20 > I have some questions, maybe you can clarify: > -- BGP communities are currently used per AS, e.g. 100:500 means AS = 100 is attaching a value of 100 to a given route. to be more precise, in your example AS100 is attaching a value of 500. > In your scheme, do you intend to use communities per footprint = identifier, e.g. 100:200:300 means AS 100 is attaching a value of 300 = for footprint identifier 100:200? not really. We propose the use of BGP Extended community (RFC4360) for=20= FPE Identifiers. > -- section 4.2.3 says " The CDNI Connectivity Advertisement contains a = new (TBD) attribute called Origin_AS_PATH that contains the AS_PATH = value describing the distance (expressed in AS Hop Count) between the = CDN and the advertised connected footprint."; in the examples in section = 7, however, Origin_AS_PATH is not the AS hop count but the ID of the = source AS; I assume it is a mistake in the example, correct? nope, the example is correct. AS_PATH Attribute in BGP contains the list=20= of AS# the update traversed. AS hop-count is computed when you process=20= the update. Origin_AS_PATH has the same format. > -- in your scheme, how can you explicitly express costs (e.g. latency, = bandwidth, monetary costs, ...) to a certain footprint identifier? I = understand a ranking, but it is not clear to me how you express explicit = costs. Via an extended community value per footprint identifier? BGP distane is based on AS hop-count. THere's no topology involved (as = you=20 rarely exchange topology between ASs). However, nothing prevents to use BGP attributes (MED, Communities) in = order to represent preferences that could also be based on costs. > -- what is confusing to me is that original BGP connectivity refers to = AS-level routing, while CDN connectivity to me is (in principle) quite = independent from AS-level routing. We use a tool called BGP but we use it in the CDNI context.=20 So, the messaging and the signaling will reflect the shape of the CDNI = Mesh=20 and not the Internet mesh. > For instance, I can very well imagine 2 CDNs which have a direct = bilateral CDN-interconnection agreement, but which have many AS-hops = between their footprints. So the connectivity via AS-level BGP = footprints is very confusing to me. Maybe you can explain it. AS number (in the CDNI context) refers to the CDN using such AS number.=20= The different CDN BGP sessions you will have will tell you about all CDN=20= interconnectivity. This is not related to the underneath inter-AS=20 connectivity. In the new draft I also include a topology example that, hopefully, will help... s. >=20 >=20 > Thanks for answering, >=20 > - Jan >=20 From sprevidi@cisco.com Tue Feb 28 10:25:35 2012 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 5667621F8645 for ; Tue, 28 Feb 2012 10:25:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.509 X-Spam-Level: X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7VHfEk2meyE for ; Tue, 28 Feb 2012 10:25:34 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 5142A21F85E3 for ; Tue, 28 Feb 2012 10:25:34 -0800 (PST) X-TACSUNS: Virus Scanned Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q1SHxeF0009593 for ; Tue, 28 Feb 2012 18:59:40 +0100 (CET) Received: from dhcp-10-55-89-11.cisco.com (dhcp-10-55-89-11.cisco.com [10.55.89.11]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q1SHxbG5014777; Tue, 28 Feb 2012 18:59:37 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: stefano previdi In-Reply-To: <075049AD-E2B9-40DA-8900-F54E7B6AF64E@cisco.com> Date: Tue, 28 Feb 2012 18:59:36 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <2779C9F0771F974CAD742BAE6D9904FE24F11D2A@DAPHNIS.office.hd> <075049AD-E2B9-40DA-8900-F54E7B6AF64E@cisco.com> To: Jan Seedorf X-Mailer: Apple Mail (2.1257) Cc: "Jan Medved \(jmedved\)" , cdni@ietf.org Subject: Re: [CDNi] Questions on draft-previdi-cdni-footprint-advertisement-00 X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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: Tue, 28 Feb 2012 18:25:35 -0000 On Feb 28, 2012, at 6:55 PM, stefano previdi wrote: Hi Jan, I'm in the process of submitting version 01 which has some changes in=20 terminology and encoding options. I'll try to address your questions=20 below. On Feb 28, 2012, at 5:14 PM, Jan Seedorf wrote: > Dear authors of the BGP CDNI Footprint Advertisement draft, >=20 > I have some questions, maybe you can clarify: > -- BGP communities are currently used per AS, e.g. 100:500 means AS = 100 is attaching a value of 100 to a given route. to be more precise, in your example AS100 is attaching a value of 500. > In your scheme, do you intend to use communities per footprint = identifier, e.g. 100:200:300 means AS 100 is attaching a value of 300 = for footprint identifier 100:200? not really. We propose the use of BGP Extended community (RFC4360) for=20= FPE Identifiers. > -- section 4.2.3 says " The CDNI Connectivity Advertisement contains a = new (TBD) attribute called Origin_AS_PATH that contains the AS_PATH = value describing the distance (expressed in AS Hop Count) between the = CDN and the advertised connected footprint."; in the examples in section = 7, however, Origin_AS_PATH is not the AS hop count but the ID of the = source AS; I assume it is a mistake in the example, correct? nope, the example is correct. AS_PATH Attribute in BGP contains the list=20= of AS# the update traversed. AS hop-count is computed when you process=20= the update. Origin_AS_PATH has the same format. > -- in your scheme, how can you explicitly express costs (e.g. latency, = bandwidth, monetary costs, ...) to a certain footprint identifier? I = understand a ranking, but it is not clear to me how you express explicit = costs. Via an extended community value per footprint identifier? BGP distane is based on AS hop-count. THere's no topology involved (as = you=20 rarely exchange topology between ASs). However, nothing prevents to use BGP attributes (MED, Communities) in = order to represent preferences that could also be based on costs. > -- what is confusing to me is that original BGP connectivity refers to = AS-level routing, while CDN connectivity to me is (in principle) quite = independent from AS-level routing. We use a tool called BGP but we use it in the CDNI context.=20 So, the messaging and the signaling will reflect the shape of the CDNI = Mesh=20 and not the Internet mesh. > For instance, I can very well imagine 2 CDNs which have a direct = bilateral CDN-interconnection agreement, but which have many AS-hops = between their footprints. So the connectivity via AS-level BGP = footprints is very confusing to me. Maybe you can explain it. AS number (in the CDNI context) refers to the CDN using such AS number.=20= The different CDN BGP sessions you will have will tell you about all CDN=20= interconnectivity. This is not related to the underneath inter-AS=20 connectivity. In the new draft I also include a topology example that, hopefully, will help... s. >=20 >=20 > Thanks for answering, >=20 > - Jan >=20 From robmry@gmail.com Wed Feb 29 14:34:08 2012 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 6FB3B21E802A for ; Wed, 29 Feb 2012 14:34:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNuL8Vx-ZEsS for ; Wed, 29 Feb 2012 14:34:07 -0800 (PST) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 96F6F21F86D3 for ; Wed, 29 Feb 2012 14:34:07 -0800 (PST) Received: by wicr5 with SMTP id r5so3101145wic.31 for ; Wed, 29 Feb 2012 14:34:04 -0800 (PST) Received-SPF: pass (google.com: domain of robmry@gmail.com designates 10.180.86.9 as permitted sender) client-ip=10.180.86.9; Authentication-Results: mr.google.com; spf=pass (google.com: domain of robmry@gmail.com designates 10.180.86.9 as permitted sender) smtp.mail=robmry@gmail.com; dkim=pass header.i=robmry@gmail.com Received: from mr.google.com ([10.180.86.9]) by 10.180.86.9 with SMTP id l9mr4789879wiz.15.1330554844864 (num_hops = 1); Wed, 29 Feb 2012 14:34:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=dQXnmI+4gsYJuj8Nka5cJ3zxoZx+rED11acWuLQ4ixs=; b=x/DxxCpwRCa3KKJI5VbMz3+ev1YgFj3RXmGwAHuztzyZyeENsf7cNYLMuw5l/gB1JP sJaZtQs0wo/0ODMzdLdysO0NMlAsj4Ne+rVi1dDLG+3ZKRXhtOPC+4gZGwnRWBILnW8n I1Sjy4UbuFwVw5XVP99vDcWWEqVcnIGzWF8qU= MIME-Version: 1.0 Received: by 10.180.86.9 with SMTP id l9mr3868990wiz.15.1330554844824; Wed, 29 Feb 2012 14:34:04 -0800 (PST) Received: by 10.216.232.215 with HTTP; Wed, 29 Feb 2012 14:34:04 -0800 (PST) Date: Wed, 29 Feb 2012 22:34:04 +0000 Message-ID: From: Rob Murray To: cdni@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [CDNi] CDNI Triggers interface X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.12 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, 29 Feb 2012 22:37:03 -0000 Hi all, I've just uploaded a new draft that proposes a CDNI Triggers interface ... http://tools.ietf.org/html/draft-murray-cdni-triggers-00 There was some discussion at the last WG meeting about whether triggers fit best as part of the control or metadata interface - the suggestion was that concrete proposals for the interface might help us spot commonality with one or the other, so let's see! Please take a look, your comments are welcome. Best regards, Rob. On 29/02/2012 19:37, "internet-drafts@ietf.org" wrote: >A new version of I-D, draft-murray-cdni-triggers-00.txt has been >successfully submitted by Rob Murray and posted to the IETF repository. > >Filename: draft-murray-cdni-triggers >Revision: 00 >Title: CDN Interconnect Triggers >Creation date: 2012-02-29 >WG ID: Individual Submission >Number of pages: 33 > >Abstract: > This document proposes a mechanism for 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 Secretariat