From vkg@bell-labs.com Thu Jan 2 10:05:33 2014 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 C4FF31A1F02 for ; Thu, 2 Jan 2014 10:05:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-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 4ZjnmkBn0Coj for ; Thu, 2 Jan 2014 10:05:31 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 046441AC403 for ; Thu, 2 Jan 2014 10:05:30 -0800 (PST) Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s02I5MYV015044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 2 Jan 2014 12:05:23 -0600 (CST) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s02I5MLn009956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jan 2014 12:05:22 -0600 Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.43.108]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s02I5L4e015553; Thu, 2 Jan 2014 12:05:22 -0600 (CST) Message-ID: <52C5AA85.1070806@bell-labs.com> Date: Thu, 02 Jan 2014 12:05:57 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "draft-ietf-cdni-metadata@tools.ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9 Cc: "cdni@ietf.org" Subject: [CDNi] Review of draft-ietf-cdni-metadata-04 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: Thu, 02 Jan 2014 18:05:34 -0000 Greetings with good wishes for a new year. During the Vancouver IETF, I volunteered to review draft-ietf-cdni-metadata. The review is below, in linear order and nits and substantive comments are intermixed. Generally, the document is well written. I do feel that a set of more comprehensive examples can add to the understanding of the idea. Detailed review is below in document-order form. - S1: s/Specifically this/Specifically, this/ - S3, first paragraph: In the sentence "Metadata properties describe how to acquire, authorize, and deliver content from a downstream CDN.", I would break down the prepositions depending on who is doing what. In the absence of individual prepositions, you are left with applying the lone preposition ("from") to all verbs ("acquire", "authorize" and "deliver"). In other words, saying something like "Metadata properties describe how to acquire content from a downstream CDN, authorize a downstream CDN and deliver content to a downstream CDN." - S3, first pargraph: s/content delivered for that Hostname/content delivered to that Hostname/ - S3.1, third paragraph: s/As well as/Besides/ - S3.1, Figure 1: The "Key" at the bottom left of the figure appears to be redundant; you have already described the symbols above (on top left). Similarly, Table 1 does not add much beyond what is implicit in Figure 1; you can remove Table 1 without impacting anything (I believe). - S3.1, Table 2: May be helpful to provide an example for "PathMatch". I found the examples in other definitions to be very useful. Ditto for "GenericMetaData". - S3.2, first paragraph: Not sure what you mean by "opaque Metadata distribution". If this is a term that is well known in the domain, you can leave it as such, if not, then expanding what this means may be useful. Reading the rest of the section it appears that you are treating the properties that the dCDN does not understand as "opaque". My suggestion would be to just s/and opaque Metadata distribution/and Metadata distribution/ since the text in the rest of the section demonstrates what can be distributed and what is not subject to distribution. - S4.1.6: How rigorous is the PatternMatch object? Is the full regexp grammar permitted or only the subset shown in the section is allowed? Right now, the wording is ambiguous. The patter may contain the wildcards, but are ranges allowed (as an example)? I cannot tell from the current text. - S4.2.2.1: What is a "Location object"? I cannot find it in the Terminology section of this document nor can I find it in rfc6707. - S4.2.3.1: You may want to consider putting a forward reference to the definition of TimeWindow objects here. - S6, first/second paragraphs: Any specific reason why you changed from "dCDN" to "Downstream CDN" and from "uCDN" to "Upstream CDN"? While doing so is okay, it is better to retain one of these for uniformity throught the manuscript. - S6.2, paragraph four: I suspect the mechanisms of dCDN decision are not subject to standardization (or out of scope)? If so, may be a good idea to simply state this. - S6.4.1, Table 3: Any specific reason why the syntax name suffix (+json, c.f. rfc6838, Section 4.2.8) is omitted from the MIME types defined in the table? You do use the suffix in examples later. - S6.4.2.1: The text at the bottom of page 29 s/fetch from the next/fetch the next/ - S6.5: Seems to me that you are best moving steps 1-5 to the IANA Considerations (S7) since it overlaps with what is currently in the IANA Consideration section. In S6.5, simply state that "Any document that defines a new GenericMetadata object MUST follow the steps outlined in Section 7 (IANA Considerations)." - S6.6, end of the first paragraph: A spurious ':' perhaps? Cheers, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq From flefauch@cisco.com Thu Jan 2 10:29:38 2014 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 B63A51A1F7A for ; Thu, 2 Jan 2014 10:29:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.039 X-Spam-Level: X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, 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 OMq7uJQFfQ4b for ; Thu, 2 Jan 2014 10:29:34 -0800 (PST) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 031941A1F71 for ; Thu, 2 Jan 2014 10:29:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4652; q=dns/txt; s=iport; t=1388687367; x=1389896967; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RBu/OUIpHJ53vfmL5TQJYKNlwEuKBOBVvM3IBz/0Tjw=; b=iUfKGGMMqKH9M6B7sj87nMq9fDOSAVq1xj6eA8XvqoPxBxhWpRIfHixQ 8GrZ3HVxf8toy+hKcjGLg8RNOf4mi05/shHiGcnibCqHwzUr4ftejis8j Mcw9OhaSHcmsa11SfIF/fJ7ikDFnx15o8Zw7WKx4useG9lXQSN4wipgFm E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AksFAMuuxVKtJXHB/2dsb2JhbABYgws4Twa4b4ELFnSCJQEBAQMBAQEBNzQLBQsCAQg2ECcLJQIEDgWHfAgIBcMNF447EQFQB4MjgRMElDODZIxdAYU2gy1xAQF+OQ X-IronPort-AV: E=Sophos;i="4.95,592,1384300800"; d="scan'208";a="10160461" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-7.cisco.com with ESMTP; 02 Jan 2014 18:29:26 +0000 Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s02ITQN1003128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Jan 2014 18:29:26 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.227]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Thu, 2 Jan 2014 12:29:26 -0600 From: "Francois Le Faucheur (flefauch)" To: "Vijay K. Gurbani" Thread-Topic: [CDNi] Review of draft-ietf-cdni-metadata-04 Thread-Index: AQHPB+U7WtfXI+dsik6XOVerGH4GhZpyJeuA Date: Thu, 2 Jan 2014 18:29:26 +0000 Message-ID: <5DE02AA9-5384-4F9A-AB3C-F09E4B6C010F@cisco.com> References: <52C5AA85.1070806@bell-labs.com> In-Reply-To: <52C5AA85.1070806@bell-labs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.55.161.197] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "draft-ietf-cdni-metadata@tools.ietf.org" , "cdni@ietf.org" Subject: Re: [CDNi] Review of draft-ietf-cdni-metadata-04 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: Thu, 02 Jan 2014 18:29:38 -0000 Hi Vijay, Thanks for following up on your commitment and doing the review.=20 Francois On 2 Jan 2014, at 19:05, "Vijay K. Gurbani" wrote: > Greetings with good wishes for a new year. >=20 > During the Vancouver IETF, I volunteered to review > draft-ietf-cdni-metadata. The review is below, in linear order and nits > and substantive comments are intermixed. >=20 > Generally, the document is well written. I do feel that a set of more > comprehensive examples can add to the understanding of the idea. > Detailed review is below in document-order form. >=20 > - S1: s/Specifically this/Specifically, this/ >=20 > - S3, first paragraph: In the sentence "Metadata properties describe > how to acquire, authorize, and deliver content from a downstream CDN.", > I would break down the prepositions depending on who is doing what. > In the absence of individual prepositions, you are left with applying > the lone preposition ("from") to all verbs ("acquire", "authorize" and > "deliver"). In other words, saying something like "Metadata > properties describe how to acquire content from a downstream CDN, > authorize a downstream CDN and deliver content to a downstream CDN." >=20 > - S3, first pargraph: s/content delivered for that Hostname/content > delivered to that Hostname/ >=20 > - S3.1, third paragraph: s/As well as/Besides/ >=20 > - S3.1, Figure 1: The "Key" at the bottom left of the figure appears > to be redundant; you have already described the symbols above > (on top left). Similarly, Table 1 does not add much beyond what > is implicit in Figure 1; you can remove Table 1 without impacting > anything (I believe). >=20 > - S3.1, Table 2: May be helpful to provide an example for "PathMatch". > I found the examples in other definitions to be very useful. >=20 > Ditto for "GenericMetaData". >=20 > - S3.2, first paragraph: Not sure what you mean by "opaque Metadata > distribution". If this is a term that is well known in the domain, > you can leave it as such, if not, then expanding what this means > may be useful. Reading the rest of the section it appears that > you are treating the properties that the dCDN does not understand > as "opaque". My suggestion would be to just > s/and opaque Metadata distribution/and Metadata distribution/ > since the text in the rest of the section demonstrates what can > be distributed and what is not subject to distribution. >=20 > - S4.1.6: How rigorous is the PatternMatch object? Is the full regexp > grammar permitted or only the subset shown in the section is allowed? > Right now, the wording is ambiguous. The patter may contain the > wildcards, but are ranges allowed (as an example)? I cannot tell > from the current text. >=20 > - S4.2.2.1: What is a "Location object"? I cannot find it in the > Terminology section of this document nor can I find it in rfc6707. >=20 > - S4.2.3.1: You may want to consider putting a forward reference > to the definition of TimeWindow objects here. >=20 > - S6, first/second paragraphs: Any specific reason why you changed > from "dCDN" to "Downstream CDN" and from "uCDN" to "Upstream CDN"? > While doing so is okay, it is better to retain one of these > for uniformity throught the manuscript. >=20 > - S6.2, paragraph four: I suspect the mechanisms of dCDN decision are > not subject to standardization (or out of scope)? If so, may be > a good idea to simply state this. >=20 > - S6.4.1, Table 3: Any specific reason why the syntax name suffix > (+json, c.f. rfc6838, Section 4.2.8) is omitted from the MIME types > defined in the table? You do use the suffix in examples later. >=20 > - S6.4.2.1: The text at the bottom of page 29 > s/fetch from the next/fetch the next/ >=20 > - S6.5: Seems to me that you are best moving steps 1-5 to the IANA > Considerations (S7) since it overlaps with what is currently in > the IANA Consideration section. In S6.5, simply state that "Any > document that defines a new GenericMetadata object MUST follow the > steps outlined in Section 7 (IANA Considerations)." >=20 > - S6.6, end of the first paragraph: A spurious ':' perhaps? >=20 > Cheers, >=20 > - vijay > --=20 > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent > 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com > Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni From internet-drafts@ietf.org Tue Jan 14 11:14:31 2014 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 532AF1AE1DA; Tue, 14 Jan 2014 11:14:31 -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 FHNMI_RG-TRs; Tue, 14 Jan 2014 11:14:28 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5991C1ADF90; Tue, 14 Jan 2014 11:14:28 -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.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140114191428.24848.93082.idtracker@ietfa.amsl.com> Date: Tue, 14 Jan 2014 11:14:28 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-15.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, 14 Jan 2014 19:14:31 -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-15.txt Pages : 24 Date : 2014-01-14 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-15 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-15 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 internet-drafts@ietf.org Fri Jan 17 11:02:13 2014 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 733A91AE146; Fri, 17 Jan 2014 11:02:13 -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 SqW4753nvJoM; Fri, 17 Jan 2014 11:02:12 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0402B1A1F3D; Fri, 17 Jan 2014 11:02:12 -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.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140117190212.24941.64814.idtracker@ietfa.amsl.com> Date: Fri, 17 Jan 2014 11:02:12 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-16.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, 17 Jan 2014 19:02:13 -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-16.txt Pages : 24 Date : 2014-01-17 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-16 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-16 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 internet-drafts@ietf.org Sun Jan 19 11:59:15 2014 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 CFCE21AE026; Sun, 19 Jan 2014 11:59:15 -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 cF2fII3E7GP5; Sun, 19 Jan 2014 11:59:13 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EAADC1ADF76; Sun, 19 Jan 2014 11:59:10 -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.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140119195910.21307.1867.idtracker@ietfa.amsl.com> Date: Sun, 19 Jan 2014 11:59:10 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-framework-08.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: Sun, 19 Jan 2014 19:59:16 -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 : Framework for CDN Interconnection Authors : Larry Peterson Bruce Davie Filename : draft-ietf-cdni-framework-08.txt Pages : 54 Date : 2014-01-19 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-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-framework-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From kleung@cisco.com Thu Jan 23 12:35:02 2014 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 50B971A0099 for ; Thu, 23 Jan 2014 12:35:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.036 X-Spam-Level: X-Spam-Status: No, score=-15.036 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.535, 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 fWElC4fLqooh for ; Thu, 23 Jan 2014 12:34:59 -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 53A591A00C5 for ; Thu, 23 Jan 2014 12:34:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5058; q=dns/txt; s=iport; t=1390509299; x=1391718899; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=se9IAX04zUiTiOnlQwRU8TAEixrSryf3vid3bvwN4LI=; b=Oqtfg44R8YjR912NFc/b52LRT47sV+5ffgozk8XI9Z3GlCam3JrukW+A 083FIo/jMARILxpcnvxap3v0EX2rxmaw3qR2k07i4HU1Wuii27ALcTstZ YIxSmGBO77GXH8j9p3fQI2dUhGFHPtTQyFVxFSFc3yu9nZuq3/wUXrham Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlAFAK984VKtJXHA/2dsb2JhbABQCoMMOFAGvDeBFRZ0giUBAQEEAQEBNy0HAhUEAgEIEQQBAQsUCQcnCxQHAQEFAwIEEwgBEodpAQgFxnQXjiQrDykGgx6BFASZVZBmgy2CKg X-IronPort-AV: E=Sophos;i="4.95,708,1384300800"; d="scan'208";a="299314007" Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jan 2014 20:34:47 +0000 Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s0NKYkIY000771 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 23 Jan 2014 20:34:46 GMT Received: from xmb-aln-x03.cisco.com ([169.254.6.14]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 14:34:46 -0600 From: "Kent Leung (kleung)" To: "cdni@ietf.org" Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-requirements-16.txt Thread-Index: AQHPE7afI4xaDOzyJ0KhPMGYc7e35pqSxkYQ Date: Thu, 23 Jan 2014 20:34:45 +0000 Message-ID: References: <20140117190212.24941.64814.idtracker@ietfa.amsl.com> In-Reply-To: <20140117190212.24941.64814.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [171.71.231.143] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [CDNi] FW: I-D Action: draft-ietf-cdni-requirements-16.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: Thu, 23 Jan 2014 20:35:02 -0000 Hi. IESG review of this draft is almost complete. During the process, updat= es were made to the specification to address the review comments. Some key = changes are noted below. 1. The terminology section was updated with text that clarified the priorit= ization of the requirements. o "High Priority": When a requirement is tagged as "{HIGH}", it is considered by the working group as an essential function for CDNI and necessary to a deployable solution. This requirement has to be met even if it causes a delay in the delivery by the working group of a deployable solution. o "Medium Priority": When a requirement is tagged as "{MED}", it is considered by the working group as an important function for CDNI. This requirement has to be met, unless it is established that attempting to meet this requirement would cause a delay in the delivery by the working group of a deployable solution. o "Low Priority": When a requirement is tagged as "{LOW}", it is considered by the working group as a useful function for CDNI. The working group will attempt to meet this requirement as long as it does not prevent meeting the "High Priority" and "Medium Priority" requirements and does not cause a delay in the delivery by the working group of a deployable solution. 2. These requirements were added: FCI-7 {HIGH} The CDNI Footprint & Capabilities Advertisement interface shall support extensible fields used to convey the CDN capabilities and methods to indicate the footprint in the advertisement from the Downstream CDN to the Upstream CDN. MI-22 {HIGH} The CDNI Metadata interface shall support extensible format for CDNI metadata delivery from the Upstream CDN to the Downstream CDN. LI-17 {MED} The CDNI Logging interface should provide privacy protection by not disclosing information that can be used to identify the user (e.g. method that anonymizes the IP address carried in the logging field). The use of the privacy protection mechanism is optional. 3. The following requirement was removed because it overlapped with the nex= t requirement (LI-15). This resulted in LI-15, LI-16, and LI-17 becoming LI= -14, LI-15, and LI-16, respectively. LI-14 [HIGH] The CDNI Logging interface shall support extensibility to allow proprietary information fields to be carried. These information fields shall be agreed upon ahead of time between the corresponding CDNs. I'll assume the changes are fine unless someone raises objections. Thanks. Kent -----Original Message----- From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of internet-drafts@ietf= .org Sent: Friday, January 17, 2014 11:02 AM To: i-d-announce@ietf.org Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-16.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 : Content Distribution Network Interconnection (CDN= I) Requirements Authors : Kent Leung Yiu Lee Filename : draft-ietf-cdni-requirements-16.txt Pages : 24 Date : 2014-01-17 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-16 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-16 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 kleung@cisco.com Thu Jan 23 14:42:04 2014 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 188FC1A0462 for ; Thu, 23 Jan 2014 14:42:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.036 X-Spam-Level: X-Spam-Status: No, score=-15.036 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.535, 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 XCAk6HItX6ho for ; Thu, 23 Jan 2014 14:42:02 -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 9A1421A045A for ; Thu, 23 Jan 2014 14:42:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11548; q=dns/txt; s=iport; t=1390516921; x=1391726521; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=oUivDSuMfWtph9kAmZ850nKIMsFjYAgOIpplToCPFrQ=; b=Li/iPgtccXMxJ4yBF6I4lkFMisZfIOFfLheOsEmYkWekedpAzwxpO1F5 kbXV0jLk4XCEqPjBs2zQmCiP0ct3UKXj9LU9e+Si33cSMzF8u1rh4M/bk Q/J72Z0y+zFXf9AtPYiTYzYyscb4psWBCxpX5gvh6yLmgofQt7sD+3qbT Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak8FABWa4VKtJXHA/2dsb2JhbABagww4UAa8N4EWFnSCJQEBAQQBAQFrBBMEAgEIEQQBAQsdBycLFAkIAgQTCAEFh3YBCAXHExeOTw8pBoMegRQEkDyJGYsuhTiDLYIq X-IronPort-AV: E=Sophos;i="4.95,709,1384300800"; d="scan'208";a="299340935" Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jan 2014 22:42:00 +0000 Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s0NMg0HF029529 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 23 Jan 2014 22:42:00 GMT Received: from xmb-aln-x03.cisco.com ([169.254.6.14]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 16:42:00 -0600 From: "Kent Leung (kleung)" To: "cdni@ietf.org" Thread-Topic: I-D Action: draft-ietf-cdni-framework-08.txt Thread-Index: AQHPFVDySjYLQ0+gaEupqo/qPJ+JspqS7TqA Date: Thu, 23 Jan 2014 22:41:59 +0000 Message-ID: References: <20140119195910.21307.1867.idtracker@ietfa.amsl.com> In-Reply-To: <20140119195910.21307.1867.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [171.71.231.143] Content-Type: multipart/mixed; boundary="_002_CD85F32117029D4F9AEF48BDEF5536AB4DDC440Dxmbalnx03ciscoc_" MIME-Version: 1.0 Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-framework-08.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: Thu, 23 Jan 2014 22:42:04 -0000 --_002_CD85F32117029D4F9AEF48BDEF5536AB4DDC440Dxmbalnx03ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi. Just a note that my comments (see attachment) were not addressed in thi= s version. Please do so in the next revision. Thanks. Kent -----Original Message----- From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of inte= rnet-drafts@ietf.org Sent: Sunday, January 19, 2014 11:59 AM To: i-d-announce@ietf.org Cc: cdni@ietf.org Subject: I-D Action: draft-ietf-cdni-framework-08.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 Authors : Larry Peterson Bruce Davie Filename : draft-ietf-cdni-framework-08.txt Pages : 54 Date : 2014-01-19 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-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-framework-08 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ 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.ie= tf.org/ietf/1shadow-sites.txt --_002_CD85F32117029D4F9AEF48BDEF5536AB4DDC440Dxmbalnx03ciscoc_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Thu, 23 Jan 2014 22:41:58 GMT"; modification-date="Thu, 23 Jan 2014 22:41:58 GMT" Received: from rcdn-iport-1.cisco.com (173.37.86.72) by mail.cisco.com (173.36.12.80) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 2 Dec 2013 13:57:21 -0600 Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 02 Dec 2013 19:57:20 +0000 Received: from alln-inbound-k.cisco.com (alln-inbound-k.cisco.com [173.37.147.241]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB2JvKRp019529; Mon, 2 Dec 2013 19:57:20 GMT Received: from mail.ietf.org ([4.31.198.44]) by alln-inbound-k.cisco.com with ESMTP; 02 Dec 2013 19:57:19 +0000 Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1991ADEB4; Mon, 2 Dec 2013 11:57:20 -0800 (PST) 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) 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) 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" CC: "cdni@ietf.org" Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-framework-07.txt Thread-Topic: [CDNi] I-D Action: draft-ietf-cdni-framework-07.txt Thread-Index: AQHO6fl5wTgWKN0m1UKfjMrKPZxZM5pBWeqA Sender: CDNi Date: Mon, 2 Dec 2013 19:57:12 +0000 Message-ID: References: <20131125161436.14041.97394.idtracker@ietfa.amsl.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <20131125161436.14041.97394.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthMechanism: 10 X-MS-Exchange-Organization-AuthSource: xhc-aln-x06.cisco.com X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: authentication-results: alln-inbound-k.cisco.com; dkim=pass (signature verified) header.i=@ietf.org x-ironport-av: E=Sophos;i="4.93,812,1378857600"; d="scan'208";a="288850994" 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-original-to: cdni@ietfa.amsl.com delivered-to: cdni@ietfa.amsl.com x-ironport-anti-spam-result: AkECAIXlnFIEH8YsnGdsb2JhbABZgmZZTQa4Z4EmFg4BAQEBAQYNCQkUIQeCJQEBAQEDAQEBNwYBAQQKHgQHAQIDAQIDAwEBAQEIEQQBAQsUCAEHAwEjCxQJCAIEEwUDAYd4AQIFBa88hFIBBYtxEQaOZgkmgxqBE5lHlAyCKg list-archive: errors-to: cdni-bounces@ietf.org x-from-outside-cisco: 4.31.198.44 x-originating-ip: [10.21.79.199] list-id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" x-virus-scanned: amavisd-new at amsl.com x-mailman-version: 2.1.15 x-beenthere: cdni@ietf.org x-spam-flag: NO 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 x-spam-level: x-spam-score: -14.502 list-post: received-spf: None (alln-inbound-k.cisco.com: no sender authenticity information available from domain of postmaster@mail.ietf.org) identity=helo; client-ip=4.31.198.44; receiver=alln-inbound-k.cisco.com; envelope-from="cdni-bounces@ietf.org"; x-sender="postmaster@mail.ietf.org"; x-conformance=spf_only Content-Type: text/plain; charset="us-ascii" Content-ID: <44E73BBA39B5A74DB343E16441F4919E@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 _______________________________________________ CDNi mailing list CDNi@ietf.org https://www.ietf.org/mailman/listinfo/cdni --_002_CD85F32117029D4F9AEF48BDEF5536AB4DDC440Dxmbalnx03ciscoc_-- From internet-drafts@ietf.org Thu Jan 30 07:10:02 2014 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 543181A0416; Thu, 30 Jan 2014 07:10:02 -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 3UC0lrCuKBNB; Thu, 30 Jan 2014 07:10:01 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1791A038E; Thu, 30 Jan 2014 07:10: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.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140130151000.10215.11395.idtracker@ietfa.amsl.com> Date: Thu, 30 Jan 2014 07:10:00 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-framework-09.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: Thu, 30 Jan 2014 15:10:02 -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 : Framework for CDN Interconnection Authors : Larry Peterson Bruce Davie Ray van Brandenburg Filename : draft-ietf-cdni-framework-09.txt Pages : 54 Date : 2014-01-30 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-09 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-framework-09 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 internet-drafts@ietf.org Thu Jan 30 10:40:56 2014 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 9B6F21A0468; Thu, 30 Jan 2014 10:40:56 -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 YINF-D1Rz18v; Thu, 30 Jan 2014 10:40:55 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E541A0072; Thu, 30 Jan 2014 10:40:55 -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.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140130184054.29633.40133.idtracker@ietfa.amsl.com> Date: Thu, 30 Jan 2014 10:40:54 -0800 Cc: cdni@ietf.org Subject: [CDNi] I-D Action: draft-ietf-cdni-requirements-17.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: Thu, 30 Jan 2014 18:40:56 -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-17.txt Pages : 24 Date : 2014-01-30 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-17 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-cdni-requirements-17 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 Thu Jan 30 13:00:09 2014 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 DF8AD1A0452; Thu, 30 Jan 2014 13:00:09 -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 ztFjHhQlfMzD; Thu, 30 Jan 2014 13:00:08 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6351A04D0; Thu, 30 Jan 2014 13:00:05 -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.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140130210005.4142.28409.idtracker@ietfa.amsl.com> Date: Thu, 30 Jan 2014 13:00:05 -0800 Cc: cdni chair , cdni mailing list , RFC Editor Subject: [CDNi] Document Action: 'Content Distribution Network Interconnection (CDNI) Requirements' to Informational RFC (draft-ietf-cdni-requirements-17.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: Thu, 30 Jan 2014 21:00:10 -0000 The IESG has approved the following document: - 'Content Distribution Network Interconnection (CDNI) Requirements' (draft-ietf-cdni-requirements-17.txt) as Informational RFC This document is the product of the Content Delivery Networks Interconnection Working Group. The IESG contact persons are Spencer Dawkins and Martin Stiemerling. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-cdni-requirements/ Technical Summary Content Delivery Networks (CDNs) are frequently used for content delivery. 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 Protect (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. Working Group Summary The only major controversy was regarding when the requirements draft should be completed. Some argued the requirements draft should be the last document completed in the working group, so that any requirements "discovered" during the development of other RFCs could be added later. Others argued that we should finish this and publish it, so we can reference it in solutions drafts, do not have scope creep and stray far from the original consensus of the working group. The latter won out. Document Quality Besides incremental reviews and revisions through working group discussions, both of the chairs did a thorough review of the draft during WGLC. These reviews resulted in a number of revisions. This requirements draft is being referenced frequently and leveraged for the CDNI solutions drafts. Personnel Daryl Malas is the Document Shepherd. The Area Director for this working group is Spencer Dawkins. From georgehanes@hushmail.com Thu Jan 30 14:39:56 2014 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 285351A04DA for ; Thu, 30 Jan 2014 14:39:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.323 X-Spam-Level: X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_HELO_NEUTRAL=0.112, SPF_PASS=-0.001] 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 JtTxX76Y_4CK for ; Thu, 30 Jan 2014 14:39:54 -0800 (PST) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by ietfa.amsl.com (Postfix) with ESMTP id AC9251A039C for ; Thu, 30 Jan 2014 14:39:54 -0800 (PST) Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by smtp5.hushmail.com (Postfix) with SMTP id 06D4F6018E for ; Thu, 30 Jan 2014 22:05:59 +0000 (UTC) Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp5.hushmail.com (Postfix) with ESMTP for ; Thu, 30 Jan 2014 22:05:58 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id E44A96018A; Thu, 30 Jan 2014 22:05:58 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 17:05:58 -0500 To: cdni@ietf.org From: georgehanes@hushmail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20140130220558.E44A96018A@smtp.hushmail.com> Subject: [CDNi] Be cautious of this computer science conference 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: Thu, 30 Jan 2014 22:39:56 -0000 Be cautious of this computer science conference If you have any thought of attending the world’s biggest f-a-k-e conference in computer science http://www.world-academy-of-science.org you should visit any websites below https://sites.google.com/site/worlddump1 or https://sites.google.com/site/dumpconf https://sites.google.com/site/moneycomp1 https://sites.google.com/site/worlddump4 The organizer of this conference is H-amid A-rabnia http://www.cs.uga.edu/~hra a professor from University of Georgia, Athens, US. He already earned millions of dollars from the registration fee. He recently started a new conference CSCI due to his hunger for money http://www.americancse.org He did not reveal the reviews and reviewers' information for all the papers he received, despite repeated requests and challenges. The reason for his failure is there are no reviews and reviewers and he just cheated the research community for more than a decade by announcing that each draft paper is reviewed by two experts. We challenge him to publish these details at the conference website. Where are your experts? Where are your reviews? Soon he comes up with a story announcing that he lost all the information having reviews and reviewers because of computer crash or theft. DBLP stopped indexing these conferences since 2011 and displayed an explicit message; "The DBLP Advisory Board decided to discontinue indexing of this conference series". Visit http://www.informatik.uni-trier.de/~ley/db/conf/biocomp/index.html as a sample. He was forced to remove his name, the university of Georgia name, and university of Georgia email address from the conference’s contact page because the University has banned him from doing that. Do not spoil your resume by publishing in this conference. Apologies for posting to multiple mailing lists. Spreading the news is the only way to stop this conference from harming innocent researchers. Respectfully, Many researchers cheated by these conferences