From nobody Tue May 5 00:37:24 2015 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 065661B2EE6 for ; Tue, 5 May 2015 00:37:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.79 X-Spam-Level: X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wIrP9yAafidz for ; Tue, 5 May 2015 00:37:20 -0700 (PDT) Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 37E831B2EE2 for ; Tue, 5 May 2015 00:37:20 -0700 (PDT) Received: from CNNIC-PC (unknown [218.241.103.69]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0BpcIQsc0hV9xlCAA--.988S2; Tue, 05 May 2015 15:37:17 +0800 (CST) Date: Tue, 5 May 2015 15:37:13 +0800 From: "qinxiaowei@cnnic.cn" To: cdni X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <2015050515371273981114@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart062642350205_=----" X-CM-TRANSID: AQAAf0BpcIQsc0hV9xlCAA--.988S2 X-Coremail-Antispam: 1UD129KBjvJXoWxJr47tFW7Jw4ktw4DGr18uFg_yoW8WF4kpF 45KrnrAFZrK3WFkwn7Za1ru3s8Wrn7ArWS9r9rJ3s5Ar45JF1v9w18t34Yqay5ur1fXF42 vrWYqFyYva4YyFDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUlY14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26ryj6F1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4j 6F4UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv6xkF7I0E14v26rxl6s 0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAaz4v26cxKscIFY7kG0wAqx4xG6I80 eVA0xI0YY7vIx2IE14AGzxvEb7x7Mc02F40Ex2IqxVA2YxCjr7Iv64kEw24lYx0E2Ix0cI 8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwAC jcxG0xvY0x0EwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1lFcxC0VAYjxAxZF0Ew4CEw7 xC0wACY4xI67k04243AVC20s07Mx8GjcxK6IxK0xIIj40E5I8CrwCY1x0264kExVAvwVAq 07x20xylc2xSY4AK67AK6r4xMxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r 4UMI8I3I0E5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF 67AKxVWUXVWUAwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2I x0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY 6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjx AxZFUvcSsGvfC2KfnxnUUI43ZEXa7sRiK0PDUUUUU== X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/ Archived-At: Subject: [CDNi] Uploading Acceleration Interface for CDN Interconnection 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: Tue, 05 May 2015 07:37:23 -0000 This is a multi-part message in MIME format. ------=_001_NextPart062642350205_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 RGVhciBmb2xrcywNCiAgICAgICAgVW50aWwgbm93LCBDb250ZW50IERlbGl2ZXJ5IE5ldHdvcmtz IChDRE5zKSBhcmUgY29tbW9ubHkgdXNlZCBmb3IgaW1wcm92aW5nIHRoZSBFbmQgVXNlciBleHBl cmllbmNlIG9mIGEgY29udGVudCBkZWxpdmVyeSBzZXJ2aWNlIHdoaWxlIGtlZXBpbmcgY29zdCBh dCBhIHJlYXNvbmFibGUgbGV2ZWwuIEhvd2V2ZXIscGhvdG9zLCB2aWRlb3MgYW5kIG90aGVyIHVw c3RyZWFtIHRyYWZmaWNzIGdlbmVyYXRlZCBieSBzbWFydCBkZXZpY2VzIGdyb3cgZHJhc3RpY2Fs bHkgdGhlc2UgZGF5cy4gT24gb25lIGhhbmQsIEVVcyBsaWtlIGRpcmVjdGx5IHNoYXJpbmcgdGhl aXIgcGhvdG9zLCB2aWRlb3MgYnkgcG9wdWxhciBDbG91ZCBDb21wdXRpbmcgc2VydmljZXMgKHN1 Y2ggYXMgWW91VHViZSwgVHdpdHRlciwgRmFjZWJvb2ssIGV0Yy4pLCBhbmQgb24gdGhlIG90aGVy LCBzbWFydCBkZXZpY2VzIGFyZSBlbWVyZ2luZyB0aGF0IGFyZSBub3QgZXF1aXBwZWQgd2l0aCBt dWNoIHN0b3JhZ2UgKGZvciBleGFtcGxlLCBzb21lIGlwaG9uZXMgb25seSBoYXZlIDE2Ry1zdG9y YWdlICkuIEZvciB0aGVzZSByZWFzb25zLCBFVXMgaGF2ZSB0byByZWx5IG9uIGxhcmdlIHN0b3Jh Z2UgaW4gY2xvdWQsIHN1Y2ggYXMgaUNsb3VkLCBCYWlkdSBTa3lEcml2ZSwzNjAgQ2xvdWQgRGlz ayxldGMuIA0KICAgICAgICBJbmRlZWQsIG1hbnkgTmV0d29yayBTZXJ2aWNlIFByb3ZpZGVycyAo TlNQcykgYXJlIGRlcGxveWluZyBvciBoYXZlIGRlcGxveWVkIHRoZWlyIG93biIgQ29udGVudCBV cGxvYWQgTmV0d29ya3MiKENVTnMpIHRvIGltcHJvdmUgdGhlIHVwbG9hZGluZyBleHBlcmllbmNl IGZvciB0aGUgRW5kIFVzZXIuIERlc3BpdGUgdGhlIHBvdGVudGlhbCBiZW5lZml0cyBvZiBpbnRl cmNvbm5lY3RpbmcgQ0ROcywgdG9kYXkgZWFjaCBDVU4gaXMgYSBzdGFuZC1hbG9uZSBuZXR3b3Jr IGxpa2UgdGhlaXIgQ0ROIGNvdW50ZXJwYXJ0cyBmb3JtZXIgY29uZGl0aW9uLiANCiAgICAgIFN1 YmplY3QgdG8gdGhlIHBvbGljeSBvZiB0aGUgQ29udGVudCBVcGxvYWQgTmV0d29ya3MsIGl0IGlz IGdlbmVyYWxseSBkZXNpcmFibGUgdGhhdCBhIGdpdmVuIGl0ZW0gb2YgY29udGVudCBjYW4gYmUg dXBsb2FkZWQgdG8gYW4gTmV0d29yayBTZXJ2aWNlIFByb3ZpZGVyIChOU1ApIHJlZ2FyZGxlc3Mg b2YgdGhhdCBlbmQgdXNlcidzIGxvY2F0aW9uIG9yIGF0dGFjaG1lbnQgbmV0d29yay4gVGhpcyBp cyB0aGUgbW90aXZhdGlvbiBmb3IgaW50ZXJjb25uZWN0aW5nIHN0YW5kYWxvbmUgQ1VOcyBzbyB0 aGV5IGNhbiBpbnRlcm9wZXJhdGUgYXMgYW4gb3BlbiBjb250ZW50IGRlbGl2ZXJ5IGluZnJhc3Ry dWN0dXJlIGZvciB0aGUgZW5kLXRvLWVuZCBkZWxpdmVyeSBvZiBjb250ZW50IGZyb20gRW5kIFVz ZXJzIHRvIE5ldHdvcmsgU2VydmljZSBQcm92aWRlcnMgKE5TUHMpLiAgDQogICAgIEZvcnR1bmF0 ZWx5LCB0aGUgQ0ROIGNhbiBhbHNvIHByb3ZpZGVyIGFjY2VsZXJhdGlvbiBzZXJ2aWNlIGZvciB1 cGxvYWRpbmcuIEl0IG5lZWQgYWRkIGFuIHVwbG9hZGluZyBJbnRlcmZhY2UgdG8gQ0ROSSBmb3Ig dXBsb2FkaW5nIHNlcnZpY2UuDQogICAgVGhvdWdodHM/DQoNCiAgIHJlZ2FyZHMNCg0KICBYaWFv d2VpIFFpbiANCg0KDQoNCg0K ------=_001_NextPart062642350205_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable =0A
Dear folks,
   = ;     Until now, C= ontent Delivery Networks (CDNs) are commonly used for improving the End Us= er experience of a content delivery service while keeping cost at a reason= able level. However,photos, = videos and other upstream traffics generated by smart devices grow drastic= ally these days. On one hand, EUs like directly sharing their photos, vide= os by popular Cloud Computing services (such as YouTube, Twitter, Facebook= , etc.), and on the other, smart devices are emerging that are not equippe= d with much storage (for example, some iphones only have 16G-storage ). Fo= r these reasons, EUs have to rely on large storage in cloud, such as iClou= d, Baidu SkyDrive,360 Cloud Disk,etc. 
   =     Indeed, many Network Service Providers (NSPs) are deploying= or have deployed their own" Content Upload Networks"(CUNs) to improve the= uploading experience for the End User. Despite the potential benefits of = interconnecting CDNs, today each CUN is a stand-alone network like their C= DN counterparts former condition.=0A
      Subject to th= e policy of the Content Upload Networks, it is generally desirable that a = given item of content can be uploaded to an Network Service Provider (NSP)= regardless of that end user's location or attachment network. This is the= motivation for interconnecting standalone CUNs so they can interoperate a= s an open content delivery infrastructure for the end-to-end delivery of c= ontent from End Users to Network Service Providers (NSPs).  
     Fortunately, the CDN can also provider acceler= ation service for uploading. It need add an uploading Interface to CDNI fo= r uploading service.
&n= bsp;   Thoughts?

  &= nbsp;regards

=0A
=0A ------=_001_NextPart062642350205_=------ From nobody Wed May 6 18:51:12 2015 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 437351B304B for ; Wed, 6 May 2015 18:51:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.789 X-Spam-Level: X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UQZvw24_R0a5 for ; Wed, 6 May 2015 18:51:08 -0700 (PDT) Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id A272B1B3046 for ; Wed, 6 May 2015 18:51:07 -0700 (PDT) Received: from CNNIC-PC (unknown [218.241.103.72]) by ocmail02.zx.nicx.cn (Coremail) with SMTP id AQAAf0CZoZUKxUpVG3r5AA--.1200S2; Thu, 07 May 2015 09:51:06 +0800 (CST) Date: Thu, 7 May 2015 09:51:03 +0800 From: "qinxiaowei@cnnic.cn" To: cdni X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <201505070951030685693@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart245208482741_=----" X-CM-TRANSID: AQAAf0CZoZUKxUpVG3r5AA--.1200S2 X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUOG7k0a2IF6w4kM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6xIIjxv20xvE14v26ryj 6F1UM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4j6F4UM28EF7xvwVC2z280aVAFwI0_Gr 1j6F4UJwA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Cr1j6rxdM2AIxVAIcxkEcVAq07x20xvE ncxIr21le4C262xC7I0v67AEwI8IwI1l5I8CrVAaz4v26cxKscIFY7kG0wAqx4xG6I8I3I 0E8cIF7480aVAKz4kxMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8 JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjxAxZF0Ew4CEw7 xC0wACY4xI67k04243AVC20s07Mx8GjcxK6IxK0xIIj40E5I8CrwCY02Avz4vE14v_KwCF 04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r106r 1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jr0_JrylIxkGc2Ij64vI r41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr 1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAI cVC2z280aVCY1x0267AKxVWUJVW8JwCE64xvF2IEb7IF0Fy7YxBIdaVFxhVjvjDU0xZFpf 9x07bFa9fUUUUU= X-CM-SenderInfo: xtlq5x5drzvxw6fq0xffof0/ Archived-At: Subject: [CDNi] Using cache to accelerate uploading traffic generated by End User is the scope of CDNI? 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, 07 May 2015 01:51:10 -0000 This is a multi-part message in MIME format. ------=_001_NextPart245208482741_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 aGmjrGZvbGtzICAgICANCkV4aXN0aW5nIENETnMgYXJlIGZyZXF1ZW50bHkgdXNlZCB0byBkZWxp dmVyIGxhcmdlLXNjYWxlIGNvbnRlbnQgZnJvbSBOU1BzIHRvIEVuZCBVc2VycywgYnV0IHRoZSB1 cHN0cmVhbSBiYW5kd2lkdGggaGFzIGdvbmUgdG8gd2FzdGUuIA0KU2luY2UgbWFueSBwb3B1bGFy IENsb3VkIENvbXB1dGluZyBzZXJ2aWNlcyBzdWNoIGFzIFlvdVR1YmUsIEZhY2Vib29rLCBldGMu LCBhcmUgcHJvbGlmZXJhdGluZywgcGhvdG9zLCB2aWRlb3MgYW5kIG90aGVyIHVwc3RyZWFtIHRy YWZmaWNzIGdlbmVyYXRlZCBieSBFVXMgZ3JvdyBkcmFzdGljYWxseSB0aGVzZSBkYXlzLiANCklN TywgQ0ROcyBtYXkgcHJvdmlkZXIgdXBsb2FkaW5nIGFjY2VsZXJhdGlvbjogYSBjb250ZW50IGl0 ZW0gZ2VuZXJhdGVkIGJ5IEVuZCBVc2VyIGNhbiBiZSBkZWxpdmVyZWQgdG8gYSBOU1AsIHdoaWNo IGlzIGFjY2VsZXJhdGVkIGJ5IENETnMuIFBlcmhhcHMsIGluIHRoaXMgY2FzZSwgdGhlIHVwc3Ry ZWFtIGJhbmR3aWR0aCBvZiBDRE4gUHJvdmlkZXJzIG1heSBiZSBmdWxseSB1dGlsaXplZCwgYW5k IHRoZSBOU1AgY2FuIGltcHJvdmUgdXNlciBleHBlcmllbmNlcyhlLmcuLCBsb3dlciBsYXRlbmN5 LCBib3R0bGVuZWNrcyBhdm9pZGVkKS4gDQoNClRoaXMgaXMgdGhlIHNjb3BlIG9mIHRoZSBDRE5J Pw0KDQoNCg0K ------=_001_NextPart245208482741_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable =0A
hi=A3=ACfolks     
<= div>Existing CDNs are = frequently used to deliver large-scale content from NSPs to End Users, but= the upstream bandwidth has gone to waste. 
Since many popular Cloud Compu= ting services such as YouTube, Facebook, etc., are proliferating, photos, = videos and other upstream traffics generated by EUs grow drastically these= days. 
IMO, CDNs may provider uploading acceleration: a content i= tem generated by End User can be delivered to a NSP, which is accelerated = by CDNs. Perhaps, in this case, the upstream bandwidth of CDN Providers ma= y be fully utilized, and the NSP can improve user experiences(e.g., lower = latency, bottlenecks avoided). 

This is the scope of the CDNI?=
=0A

=0A
=0A ------=_001_NextPart245208482741_=------ From nobody Mon May 11 02:50:13 2015 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 EF2C11A88E8; Mon, 11 May 2015 02:50:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.299 X-Spam-Level: X-Spam-Status: No, score=0.299 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MIME_8BIT_HEADER=0.3] autolearn=no 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 L36VLV9zME_Q; Mon, 11 May 2015 02:50:09 -0700 (PDT) Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 62DE41A88C4; Mon, 11 May 2015 02:50:08 -0700 (PDT) Received: from host4.velocix.com ([81.134.152.4] helo=[172.18.0.54]) by smtp04.mailcore.me with esmtpa (Exim 4.80.1) (envelope-from ) id 1YrkLf-0000xq-2k; Mon, 11 May 2015 10:50:07 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Ben Niven-Jenkins In-Reply-To: <552D6F72.7060901@cisco.com> Date: Mon, 11 May 2015 10:50:03 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <74AB9882-4C1F-4EE1-9718-49D2BA33B5F5@niven-jenkins.co.uk> References: <552D6F72.7060901@cisco.com> To: =?utf-8?Q?=E2=8C=98_Matt_Miller?= X-Mailer: Apple Mail (2.2070.6) X-Mailcore-Auth: 9600544 X-Mailcore-Domain: 172912 Archived-At: Cc: draft-ietf-cdni-metadata.all@tools.ietf.org, cdni@ietf.org, IETF Apps Discuss Subject: Re: [CDNi] Appsdir early review of draft-ietf-cdni-metadata-09 X-BeenThere: cdni@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2015 09:50:12 -0000 Hi Matt, Thanks for the review and apologies for the delay in responding. I will discuss your review with my co-authors and we'll re-work the = document to incorporate your comments. Thanks again Ben > On 14 Apr 2015, at 20:50, =E2=8C=98 Matt Miller = wrote: >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > I have been selected as the Applications Area Directorate early > reviewer for this draft (for background on appsdir, please see > = http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorat > e > ). >=20 > Please resolve these comments along with any other Last Call comments > you may receive. Please wait for direction from your document shepherd > or AD before posting a new version of the draft. >=20 > Document: draft-ietf-cdni-metadata > Title: CDN Interconnection Metadata > Reviewer: Matthew Miller > Review Date: 2015-04-14 > IETF Last Call Date: N/A > IESG Telechat Date: N/A >=20 > Summary: This draft is not ready for publication as a Proposed > Standard and should be revised. >=20 > Comments: >=20 > This draft is written expecting multiple encodings in the future, then > spends very little space discussing the one encoding that is defined > (JSON). The end result is a document that, in my opinion, is too > abstract. I think it would be more understandable if this draft > mentioned and used JSON throughout (e.g., a micro-example for each of > the defined types). I think it's appropriate to do this and yet still > reserve the right to support other encoding formats in the future. >=20 > Also, this draft is not very internally consistent (e.g., terminology > usage, editorial structuring, etc.), which I found made it hard to > follow at times. I would recommend that the authors do a round of > editing to be more internally consistent; I've noted in the nits a > number of specific examples. >=20 > Major Issues: >=20 > * I think Section 6.4.2. is underspecified. There are a number of > quirks and gotchas I noticed that are not discussed: >=20 > - dealing with large (requiring more than ~53 bits) integers (encode > as JSON String) > - dealing with duplicate keys within a JSON Object (MUST NOT have > duplicates) > - dealing with escaping (see Minor Issue #2) >=20 > I note that the examples in 6.4.2.1. illustrate some of the > concerns, but nowhere are they explicitly discussed. I would strongly > recommend outlining these concerns, better would be to refer to RFC > 7492 (I-JSON) and follow its recommendations explicitly. I don't > think this is much of a burden since this document appears to already > follow them implicitly. >=20 >=20 > Minor Issues: >=20 > * In Section 3.1., I find Table 2 hard to follow. I suggest each row > be broken out to its own item in an unordered list. It would also > help to point to each item's full definition. >=20 > * In Section 4.1.5., note that '\' must be escaped as '\\' in JSON, > which means the JSON string for a with a literal '\' would have > '\\\\' (this also applies for literal '?' and '*'). I can understand > why an alternative form of escaping, such as percent encoding, would > be undesirable, but it will be surprising to some to see this "extra > escaping". This effect on pattern escaping ought to be called out; if > not in Section 4.1.5. then I suggest in Section 6.4.2. >=20 > * Sections 8.2., 8.3., and 8.5., seem to cover the concerns, but I > would recommend reviewing and referencing draf-ietf-uta-tls-bcp, as I > think you would get a more complete picture here. >=20 > Nits: >=20 > * In Abstract, CDN is not expanded on first occurrence. >=20 > * In Abstract, CDNI is not expanded on first occurrence. >=20 > * In Section 1.2., dCDN is not expanded on first occurrence. >=20 > * In Section 1.2., uCDN is not expanded on first occurrence. >=20 > * Reference to HTTPv1.1 (commonly referred to as "HTTP/1.1") (RFC7230, > et al) comes very late (Section 7.2.), first noted in Section 1.2. >=20 > * No reference to HTTPv2.0 (often referred to as "http/2") > (draft-ietf-httpbis-http2-17), first noted in Section 1.2. >=20 > * Reference to HTTP over TLS (RFC 2818) comes very late (Section > 7.2.), first noted in Section 1.2. >=20 > * No reference to JSON (RFC 7159), first noted in Section 2. >=20 > * In Section 3.2., the two tables are not captioned. >=20 > * In Section 4.2.4.1., "protocol" is not capitalized (i.e., > "Protocol") like other type references in "Type: List of protocol = object > s" >=20 > * In Section 6. and many of its subsections, "Downstream CDN" is often > used instead of "dCDN", which is elsewhere in this document. I would > recommend more consistency and use "dCDN". >=20 > * In Section 6. and many of its subsections, "Upstream CDN" is often > used instead of "uCDN", which is elsewhere in this document. I would > recommend more consistency and use "uCDN". >=20 >=20 > - --=20 > - - m&m >=20 > Matt Miller < mamille2@cisco.com > > Cisco Systems, Inc. >=20 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - https://gpgtools.org >=20 > iQEcBAEBCgAGBQJVLW9yAAoJEDWi+S0W7cO1g9UIAJIV8yShj/0KiqhC82m/ixk6 > VkW5IZvB8iWp9mVStx+fQtwwm1B7LrvccFnSr5CwmyURjmaljSBKP97F6I/QnjpL > 6YJkfGyRLTP1r/fpH7N9ptpHZJQpNd5iQlBElWforfBaNHd5xm4mhLkCzlv8UKjk > TP8SDYeW5pKvUkHtK7fhW7h2eTcs/EuPZr/GlTb9yIWQAAwN0q7JTnwXVN1Lo9uQ > ap1mqUnG2YdZMuAKqrDUQRywazIuBGPu8DopbKX6Hl9fyuSEnPUry73P+7aK727x > T+/qHyARqy5PGSgesRYAQdFy3gS4/8SeeYWHpkE+7MPSjTNj4nTralxfcu7uxAU=3D > =3D+QNl > -----END PGP SIGNATURE----- >=20 > _______________________________________________ > CDNi mailing list > CDNi@ietf.org > https://www.ietf.org/mailman/listinfo/cdni From nobody Sat May 30 16:35:37 2015 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 1A0911ACEFE; Sat, 30 May 2015 16:35:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 0qhpQnL1TfXU; Sat, 30 May 2015 16:35:34 -0700 (PDT) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39CAB1AD061; Sat, 30 May 2015 16:35:34 -0700 (PDT) Received: by labpy14 with SMTP id py14so66639809lab.0; Sat, 30 May 2015 16:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=rMmrsnsubh29T/+nZyrth9fasxHkXAnh5QHO+cGXmx8=; b=pGdBk2lKG0KCqxITV23PCXZb8jHGX/pJJFNIlmsqRkygeswCNrerC6DQnsAGuGPg6e dv15MhSENGGHDMZNKAh8qI/Prur+kcA/odAm8VOQdlK5SEb+o8eCX7cOAnm8/6iFEs0t Zu19cdSz3IgynRaHZxkGVG3l+BqCmZhVlw7y0HWueBth/vcefe+h+evNWWHzi22I1gaB yEpXy8MmzvAJjkezZfqC6ccXzMLznEZwFIkcyq/1GihdEblSGPAFAVlTL+MdKxnUK1/6 yGbaabxPIaem36/Ofm+T6YMIPdQUD9w0eOqIAhf0jc7AfKwNRRGpYcMPhOq/+KZiQHus a7ow== MIME-Version: 1.0 X-Received: by 10.112.25.10 with SMTP id y10mr14390097lbf.61.1433028932741; Sat, 30 May 2015 16:35:32 -0700 (PDT) Received: by 10.152.185.198 with HTTP; Sat, 30 May 2015 16:35:32 -0700 (PDT) Received: by 10.152.185.198 with HTTP; Sat, 30 May 2015 16:35:32 -0700 (PDT) In-Reply-To: <20150529212706.10837.28310.idtracker@ietfa.amsl.com> References: <20150529212706.10837.28310.idtracker@ietfa.amsl.com> Date: Sat, 30 May 2015 18:35:32 -0500 Message-ID: From: Spencer Dawkins at IETF To: "tsv-area@ietf.org >> \"tsv-area@ietf.org\"" , "" , tsv-chairs@tools.ietf.org, mls.ietf@gmail.com, Barry Leiba Content-Type: multipart/alternative; boundary=001a1133d1487d305a0517550cb6 Archived-At: Subject: [CDNi] Fwd: Applications and Real-Time Area (ART) 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: Sat, 30 May 2015 23:35:36 -0000 --001a1133d1487d305a0517550cb6 Content-Type: text/plain; charset=UTF-8 Dear CDNI, Those of you who are also subscribed to the IETF-Announce mailing list may have seen this post, and if you read all the way to the bottom, you'll notice that CDNI is moving to the new ART area, with Barry Leiba as your responsible AD. Martin and I discussed this with the CDNI chairs before we discussed it with the IESG, and we all agreed that this was a good plan, especially since most CDNI work is closer to ART than TSV. I have enjoyed being your AD since 2013, and appreciate Daryl and Francois as your chairs. Please keep doing good work. Spencer ---------- Forwarded message ---------- From: "IESG Secretary" Date: May 29, 2015 14:27 Subject: Applications and Real-Time Area (ART) To: "IETF Announcement List" Cc: On 28 May, the IESG approved the creation of the Applications and Real-Time (ART) Area, which will replace the existing Applications (APP) and Real-time Applications and Infrastructure (RAI) Areas. All existing working groups from those two areas will move into the new ART Area, and the three existing area directors -- Alissa Cooper, Barry Leiba, and Ben Campbell -- will be the ART ADs (or "ART Directors"). In addition, the CDNI working group will move from TSV to ART. Barry will be the responsible AD for CDNI, and no other AD assignments will change. The Secretariat will immediately begin working on the administrative changes required, and the change from APP+RAI to ART will be effective as soon as the administrative work can be completed. --001a1133d1487d305a0517550cb6 Content-Type: text/html; charset=UTF-8

Dear CDNI,

Those of you who are also subscribed to the IETF-Announce mailing list may have seen this post, and if you read all the way to the bottom, you'll notice that CDNI is moving to the new ART area, with Barry Leiba as your responsible AD.

Martin and I discussed this with the CDNI chairs before we discussed it with the IESG, and we all agreed that this was a good plan, especially since most CDNI work is closer to ART than TSV.

I have enjoyed being your AD since 2013, and appreciate Daryl and Francois as your chairs.

Please keep doing good work.

Spencer

---------- Forwarded message ----------
From: "IESG Secretary" <iesg-secretary@ietf.org>
Date: May 29, 2015 14:27
Subject: Applications and Real-Time Area (ART)
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: <iesg@ietf.org>

On 28 May, the IESG approved the creation of the Applications and
Real-Time (ART) Area, which will replace the existing Applications
(APP) and Real-time Applications and Infrastructure (RAI) Areas. All
existing working groups from those two areas will move into the new
ART Area, and the three existing area directors -- Alissa Cooper,
Barry Leiba, and Ben Campbell -- will be the ART ADs (or "ART
Directors"). In addition, the CDNI working group will move from TSV
to ART. Barry will be the responsible AD for CDNI, and no other AD
assignments will change.

The Secretariat will immediately begin working on the administrative
changes required, and the change from APP+RAI to ART will be effective
as soon as the administrative work can be completed.

--001a1133d1487d305a0517550cb6--