
From Dirk.Kutscher@neclab.eu  Thu Oct  4 01:21:40 2012
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB95E21F866D for <icnrg@ietfa.amsl.com>; Thu,  4 Oct 2012 01:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmOMCJnV6+nB for <icnrg@ietfa.amsl.com>; Thu,  4 Oct 2012 01:21:40 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id CE5BB21F866B for <icnrg@irtf.org>; Thu,  4 Oct 2012 01:21:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 7FEC6101FC6 for <icnrg@irtf.org>; Thu,  4 Oct 2012 10:21:38 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khVAyzH2R8o4 for <icnrg@irtf.org>; Thu,  4 Oct 2012 10:21:38 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 6446A1019CB for <icnrg@irtf.org>; Thu,  4 Oct 2012 10:21:33 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.21]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Thu, 4 Oct 2012 10:20:32 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt
Thread-Index: AQHNogcyn6p8hTw7q0qRQhNUYcBGd5eoy82Q
Date: Thu, 4 Oct 2012 08:20:32 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F5249550DD0CF@PALLENE.office.hd>
References: <20121004080638.31617.83123.idtracker@ietfa.amsl.com>
In-Reply-To: <20121004080638.31617.83123.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.99.203]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [icnrg] FW: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 08:21:40 -0000

SGVsbG8sDQoNCldlIGhhdmUgd3JpdHRlbiB1cCBhIHNwZWNpZmljYXRpb24gb2YgdGhlIE5ldElu
ZiBwcm90b2NvbCBhbmQgc3VibWl0dGVkIHRoaXMgYXMgYW4gSW50ZXJuZXQgRHJhZnQgdG9kYXkg
KHNlZSBsaW5rIGJlbG93KS4NCg0KVGhpcyBpbmNsdWRlcyBhIGRlc2NyaXB0aW9uIG9mIHNvbWUg
dW5kZXJseWluZyBjb25jZXB0cywgYSBzcGVjaWZpY2F0aW9uIG9mIGEgbWVzc2FnZS1iYXNlZCBw
cm90b2NvbCwgYW5kIGEgc3BlY2lmaWNhdGlvbiBvZiBIVFRQIGFuZCBVRFAgY29udmVyZ2VuY2Ug
bGF5ZXJzIGZvciB0aGUgcHJvdG9jb2wuDQoNCk1vc3Qgb2YgdGhpcyBpcyBpbXBsZW1lbnRlZCBp
biB0aGUgT3BlbiBTb3VyY2UgTmV0SW5mIHNvZnR3YXJlOiBodHRwOi8vc291cmNlZm9yZ2UubmV0
L3Byb2plY3RzL25ldGluZi8NCg0KV2UnZCBhcHByZWNpYXRlIGFueSBmZWVkYmFjay4NCg0KVGhh
bmtzLA0KRGlyaw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6
IERvbm5lcnN0YWcsIDQuIE9rdG9iZXIgMjAxMiAxMDowNw0KVG86IERpcmsgS3V0c2NoZXINCkNj
OiBkYXZpZXNlYkBzY3NzLnRjZC5pZTsgc3RlcGhlbi5mYXJyZWxsQGNzLnRjZC5pZQ0KU3ViamVj
dDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1rdXRzY2hlci1pY25yZy1uZXRp
bmYtcHJvdG8tMDAudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWt1dHNjaGVy
LWljbnJnLW5ldGluZi1wcm90by0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0
ZWQgYnkgRGlyayBLdXRzY2hlciBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoN
CkZpbGVuYW1lOgkgZHJhZnQta3V0c2NoZXItaWNucmctbmV0aW5mLXByb3RvDQpSZXZpc2lvbjoJ
IDAwDQpUaXRsZToJCSBUaGUgTmV0SW5mIFByb3RvY29sDQpDcmVhdGlvbiBkYXRlOgkgMjAxMi0x
MC0wNA0KV0cgSUQ6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDIx
DQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2Ry
YWZ0LWt1dHNjaGVyLWljbnJnLW5ldGluZi1wcm90by0wMC50eHQNClN0YXR1czogICAgICAgICAg
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1rdXRzY2hlci1pY25yZy1uZXRp
bmYtcHJvdG8NCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQta3V0c2NoZXItaWNucmctbmV0aW5mLXByb3RvLTAwDQoNCg0KQWJzdHJhY3Q6DQogICBUaGlz
IGRvY3VtZW50IGRlZmluZXMgYSBjb25jZXB0dWFsIHByb3RvY29sIGFuZCBjb3JyZXNwb25kaW5n
IG5vZGUNCiAgIHJlcXVpcmVtZW50cyBmb3IgTmV0SW5mIG5vZGVzIGluIGEgTmV0SW5mIG5ldHdv
cmsuICBBIE5ldEluZiBuZXR3b3JrDQogICBvZmZlcnMgYW4gaW5mb3JtYXRpb24tY2VudHJpYyBw
YXJhZGlnbSB0aGF0IHN1cHBvcnRzIHRoZSBjcmVhdGlvbiwNCiAgIGxvY2F0aW9uLCBleGNoYW5n
ZSBhbmQgc3RvcmFnZSBvZiBOYW1lZCBEYXRhIE9iamVjdHMgKE5ET3MpLiAgTmV0SW5mDQogICBu
b2RlcyBjYW4gcHJvdmlkZSBkaWZmZXJlbnQgc2VydmljZXMgdG8gb3RoZXIgTmV0SW5mIG5vZGVz
LCBlLmcuLA0KICAgZm9yd2FyZGluZyByZXF1ZXN0cyBmb3IgaW5mb3JtYXRpb24gb2JqZWN0cywg
ZGVsaXZlcmluZyBjb3JyZXNwb25kaW5nDQogICByZXNwb25zZSBtZXNzYWdlcywgbmFtZSByZXNv
bHV0aW9uIHNlcnZpY2VzIGV0Yy4gIFRoaXMgKGFic3RyYWN0KQ0KICAgcHJvdG9jb2wgaXMgaW50
ZW5kZWQgdG8gYmUgcnVuIG92ZXIgc29tZSAiY29udmVyZ2VuY2UgbGF5ZXIiIHRoYXQNCiAgIGhh
bmRsZXMgdHJhbnNwb3J0IGlzc3Vlcy4gIFR3byAid2lyZSIgZm9ybWF0cyBhcmUgZGVmaW5lZCwg
b25lIHRoYXQNCiAgIHVzZXMgSFRUUCBmb3IgbWVzc2FnZSB0cmFuc2ZlciBhbmQgb25lIGxheWVy
ZWQgb24gVURQLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2Vj
cmV0YXJpYXQNCg0K

From diego.perino@alcatel-lucent.com  Thu Oct  4 09:05:22 2012
Return-Path: <diego.perino@alcatel-lucent.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298091F0C94 for <icnrg@ietfa.amsl.com>; Thu,  4 Oct 2012 09:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.248
X-Spam-Level: 
X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fn2X9U928Ohd for <icnrg@ietfa.amsl.com>; Thu,  4 Oct 2012 09:05:21 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id B41901F0C96 for <icnrg@irtf.org>; Thu,  4 Oct 2012 09:05:20 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q94G3ARx011734 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <icnrg@irtf.org>; Thu, 4 Oct 2012 18:05:16 +0200
Received: from [172.27.205.133] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 4 Oct 2012 18:05:00 +0200
Message-ID: <506DB3AB.9010801@alcatel-lucent.com>
Date: Thu, 4 Oct 2012 18:04:59 +0200
From: Diego Perino <diego.perino@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: <icnrg@irtf.org>
Content-Type: multipart/alternative; boundary="------------090306080205030009080109"
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Subject: [icnrg] Call for Papers - Elsevier Computer Networks Special Issue on Information-Centric Networking
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 16:05:22 -0000

--------------090306080205030009080109
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

********************** CALL FOR PAPERS - Elsevier Computer Networks 
**********************

                                  Special Issue on Information-Centric 
Networking (ICN)

www.journals.elsevier.com/computer-networks/call-for-papers/information-centric-networking/ 


********************************************************************************************************* 



Information Centric Networking (ICN, also referred to as Content-Centric 
Networking, or Name-Oriented Networking) is a new communication paradigm 
centered around named-data. Accordingly, network primitives (e.g., 
routing, forwarding, data transfer) are based on content names rather 
than host identifiers, and every node can potentially store content to 
serve user requests. ICN has received increasing attention in the last 
few years as it is considered a promising approach to overcome the 
emerging limitations of overlay infrastructures to deal with today's 
traffic trends. Indeed, ICN has the potential to natively address the 
challenge of distributing  the large amount of content associated with 
different Internet services in a scalable, flexible, and efficient way.

This special issue invites novel contributions on ICN architecture and 
mechanism designs for different environments (e.g., Public Internet, 
MANET, virtual private network, cellular networks), performance 
evaluation and analysis, implementation and experimental evaluation. 
Submissions related to ICN deployment scenarios and business models are 
also welcome. Topics of interest include, but are not limited to:
-Naming and addressing
-Inter/intra domain name-based routing protocols
-High-speed name-based forwarding mechanisms
-Transport level algorithms and protocols
-Resource management, traffic control and traffic engineering
-Storage management and cache coordination strategies
-Content router design
-Security architecture and technologies
-Privacy and trust preserving mechanisms
-ICN legacy and new applications for multimedia, web services, mobile, 
cloud computing
-Services over ICN
-Mobility management
-Quality of Service
-Performance evaluation and analysis
-Implementation and practical experiences
-ICN testbeds and simulation frameworks
-ICN business models, deployment scenarios/use-cases and economic issues
-ICN regulatory policies and Intellectual Property Right issues


Important dates
*Paper submission: 15th December 2012
*Acceptance notification: 1st March 2013
*Final Papers: 1st May 2013

Guest Editors
*Yanghee Choi, Seoul National University, Seoul, Korea, yhchoi@snu.ac.kr__
*Andrea Detti, University of Rome Tor Vergata, Rome, Italy, 
andrea.detti@uniroma2.it
*Mario Gerla, UCLA, Los Angeles, CA, USA, gerla@cs.ucla.edu
*Diego Perino, Bell Labs, Alcatel-Lucent, Nozay, France, 
diego.perino@alcatel-lucent.com

Submission format
The submitted papers must be clearly written in excellent English and 
describe original research which is not published nor currently under 
review by other journals or conferences. Author guidelines for 
preparation of manuscript can be found atwww.elsevier.com/locate/comnet/

Submission Guideline
All manuscripts and any supplementary material should be submitted 
through the Elsevier Editorial System (EES). The authors must select as 
"Information Centric Networking" when they reach the "Article Type" step 
in the submission process. The EES website is located at: 
http://ees.elsevier.com/comnet/

Guide for Authors
This site will guide you stepwise through the creation and uploading of 
you article. The guide for Authors can be found on the journal homepage 
(www.elsevier.com/comnet/). Papers are limited to twenty pages.

-- 
*Diego Perino, Ph.D.*
Research Engineer
Networking Research Department
Bell Labs, Alcatel-Lucent
diego.perino@alcatel-lucent.com <mailto:diego.perino@alcatel-lucent.com>
Phone: +33 (0)1 3077 6164

--------------090306080205030009080109
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    ********************** CALL FOR PAPERS - Elsevier Computer Networks
    ********************** <br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; Special Issue on
    Information-Centric Networking (ICN) <br>
    <br>
    <a class="moz-txt-link-abbreviated"
href="http://www.journals.elsevier.com/computer-networks/call-for-papers/information-centric-networking/">www.journals.elsevier.com/computer-networks/call-for-papers/information-centric-networking/</a>
    <br>
    <br>
    *********************************************************************************************************






    <br>
    <br>
    <br>
    Information Centric Networking (ICN, also referred to as
    Content-Centric Networking, or Name-Oriented Networking) is a new
    communication paradigm centered around named-data. Accordingly,
    network primitives (e.g., routing, forwarding, data transfer) are
    based on content names rather than host identifiers, and every node
    can potentially store content to serve user requests. ICN has
    received increasing attention in the last few years as it is
    considered a promising approach to overcome the emerging limitations
    of overlay infrastructures to deal with today's traffic trends.&nbsp;
    Indeed, ICN has the potential to natively address the challenge of
    distributing&nbsp; the large amount of content associated with different
    Internet services in a scalable, flexible, and efficient way. <br>
    <br>
    This special issue invites novel contributions on ICN architecture
    and mechanism designs for different environments (e.g., Public
    Internet, MANET, virtual private network, cellular networks),&nbsp;
    performance evaluation and analysis, implementation and experimental
    evaluation. Submissions related to ICN deployment scenarios and
    business models are also welcome. Topics of interest include, but
    are not limited to: <br>
    -Naming and addressing <br>
    -Inter/intra domain name-based routing protocols <br>
    -High-speed name-based forwarding mechanisms <br>
    -Transport level algorithms and protocols <br>
    -Resource management, traffic control and traffic engineering <br>
    -Storage management and cache coordination strategies <br>
    -Content router design <br>
    -Security architecture and technologies <br>
    -Privacy and trust preserving mechanisms <br>
    -ICN legacy and new applications for multimedia, web services,
    mobile, cloud computing <br>
    -Services over ICN <br>
    -Mobility management <br>
    -Quality of Service <br>
    -Performance evaluation and analysis <br>
    -Implementation and practical experiences <br>
    -ICN testbeds and simulation frameworks <br>
    -ICN business models, deployment scenarios/use-cases and economic
    issues <br>
    -ICN regulatory policies and Intellectual Property Right issues <br>
    <br>
    <br>
    Important dates <br>
    *Paper submission: 15th December 2012 <br>
    *Acceptance notification: 1st March 2013 <br>
    *Final Papers: 1st May 2013 <br>
    <br>
    Guest Editors <br>
    *Yanghee Choi, Seoul National University, Seoul, Korea, <a
      class="moz-txt-link-abbreviated"
      href="mailto:Korea.yhchoi@snu.ac.kr">yhchoi@snu.ac.kr</a><u> </u><br>
    *Andrea Detti, University of Rome Tor Vergata, Rome, Italy, <a
      class="moz-txt-link-abbreviated"
      href="mailto:Italy.andrea.detti@uniroma2.it">andrea.detti@uniroma2.it</a>
    <br>
    *Mario Gerla, UCLA, Los Angeles, CA, USA, <a
      class="moz-txt-link-abbreviated"
      href="mailto:USA.gerla@cs.ucla.edu">gerla@cs.ucla.edu</a> <br>
    *Diego Perino, Bell Labs, Alcatel-Lucent, Nozay, France, <a
      class="moz-txt-link-abbreviated"
      href="mailto:France.diego.perino@alcatel-lucent.com">diego.perino@alcatel-lucent.com</a>
    <br>
    <br>
    Submission format <br>
    The submitted papers must be clearly written in excellent English
    and describe original research which is not published nor currently
    under review by other journals or conferences. Author guidelines for
    preparation of manuscript can be found
    atwww.elsevier.com/locate/comnet/ <br>
    <br>
    Submission Guideline <br>
    All manuscripts and any supplementary material should be submitted
    through the Elsevier Editorial System (EES). The authors must select
    as "Information Centric Networking" when they reach the "Article
    Type" step in the submission process. The EES website is located at:
    <a class="moz-txt-link-freetext"
      href="http://ees.elsevier.com/comnet/">http://ees.elsevier.com/comnet/</a>
    <br>
    <br>
    Guide for Authors <br>
    This site will guide you stepwise through the creation and uploading
    of you article. The guide for Authors can be found on the journal
    homepage (<a class="moz-txt-link-abbreviated"
      href="http://www.elsevier.com/comnet/">www.elsevier.com/comnet/</a>).






    Papers are limited to twenty pages.<br>
    <br>
    <div class="moz-signature">-- <br>
      <b>Diego Perino, Ph.D.</b>
      <br>
      Research Engineer
      <br>
      Networking Research Department
      <br>
      Bell Labs, Alcatel-Lucent
      <br>
      <a href="mailto:diego.perino@alcatel-lucent.com">diego.perino@alcatel-lucent.com</a>
      <br>
      Phone: +33 (0)1 3077 6164
    </div>
  </body>
</html>

--------------090306080205030009080109--

From l.wood@surrey.ac.uk  Fri Oct  5 02:12:45 2012
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B82121F855E for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 02:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.473
X-Spam-Level: 
X-Spam-Status: No, score=-5.473 tagged_above=-999 required=5 tests=[AWL=1.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EllpM1ha8tsX for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 02:12:44 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0CADC21F8607 for <icnrg@irtf.org>; Fri,  5 Oct 2012 02:12:43 -0700 (PDT)
Received: from [195.245.230.131:40183] by server-10.bemta-3.messagelabs.com id D2/90-02525-A84AE605; Fri, 05 Oct 2012 09:12:42 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-78.messagelabs.com!1349428362!32113768!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1389 invoked from network); 5 Oct 2012 09:12:42 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-11.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 5 Oct 2012 09:12:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.203]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Fri, 5 Oct 2012 10:12:41 +0100
From: <l.wood@surrey.ac.uk>
To: <icnrg@irtf.org>
Date: Fri, 5 Oct 2012 10:12:37 +0100
Thread-Topic: FW: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt,
Thread-Index: AQHNotmSm/XUmXPLe0GcHcwGF03c0g==
Message-ID: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1C@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [icnrg] FW: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt, 
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 09:12:45 -0000

Well, this NetInf (ni:) effort is interesting.

I am reminded of Monty Python's 'The Knights that say "Ni"'
from the Holy Grail. Except, in this case, it's the-authors-who-
say-ni-formerly-known-as-the-authors-that-said-dtn.

As in the Grail, there were words that, when said, had odd
effects on the authors-that-said-dtn: these included
'reliability' and 'MIME'.

In the world of delay-tolerant networking, just a research
group over from here, the bundle protocol did not need MIME -
even though dtn networks, like all networks, have to move
content around. Good to see that this ni effort uses MIME
"for significant specification and code re-use. For example,
we do not need to invent a new typing scheme nor any
associated registration rules nor registries."

It's a shame that such arguments never went far with
the bundle protocol.

Like dtn and the bundle protocol (and CFDP before it),
ni adopts convergence layers, to avoid the effort
of engineering a new transport and getting bogged
down in transport issues. Sensibly, in the ni draft below,
section 3 calls out the requirements that convergence layers
must meet:
"   Each CL has to offer the following minimal set of capabilities:
   o  unidirectional point-to-point transport of NetInf messages from
      source to destination,
   o  preservation of message boundaries,
   o  reliable transmission of message octets, and
   o  in-order delivery of message octets to the destination node."

Unfortunately, neither of the convergence layers proposed in the
draft meets those stated requirements: neither HTTP or UDP is by
itself reliable. (And, strictly speaking, neither is really much good as
a transport.)

HTTP would need Content-MD5: or similar as a minimum; UDP needs
a transport shim like LTP or Saratoga. And HTTP and UDP aren't
remotely similar in semantics or capabilities, in terms of message size,
security capabilities, content identification (MIME is not a port), etc.

Treating them as equivalent convergence layers is just wrong.
The bundle protocol tried treating UDP and TCP as equivalent; that
didn't work too well.

If the convergence layer doesn't offer reliability, perhaps the ni layer
running over it could do so? Apparently not. The bundle protocol has
that problem too.

Funnily enough, leveraging HTTP for content delivery has been
looked into before:
http://tools.ietf.org/html/draft-wood-dtnrg-http-dtn-delivery
http://sat-net.com/L.Wood/dtn/http-dtn.html

but since that was submitted in the dtnrg group, it never gained the
approval of the authors-who-said-dtn. That's proposing a bit of
re-engineering of the network stack to turn http into a layer in its
own right, supported by multiple transports - or convergence layers.

Once that's in place, building everything on http is much easier.
So http isn't just one convergence layer for a new protocol; it
becomes the common substrate for an ecosystem.

And something like ni becomes rather simpler, being
able to leverage rather than reinvent aspects of http; publish and
subscribe always map to http PUT and GET semantics, rather than
floundering over UDP.

But that was proposed in the wrong group, at the wrong time.
Really, dtn's funding bubble is waning, and content networking's is
waxing; it's a new paradigm for old ideas.

Bring out your dead ideas! We collect them!

L.

"Look, matey, I know a dead protocol when I see one, and I'm
looking at one right now." - with apologies to the Blue Norwegian Parrot.

Lloyd Wood
http://sat-net.com/L.Wood/

***

Hello,

We have written up a specification of the NetInf protocol and submitted thi=
s as an Internet Draft today (see link below).

This includes a description of some underlying concepts, a specification of=
 a message-based protocol, and a specification of HTTP and UDP convergence =
layers for the protocol.

Most of this is implemented in the Open Source NetInf software: http://sour=
ceforge.net/projects/netinf/

We'd appreciate any feedback.

Thanks,
Dirk

-----Original Message-----
From: internet-drafts at ietf.org [mailto:internet-drafts at ietf.org]=20
Sent: Donnerstag, 4. Oktober 2012 10:07
To: Dirk Kutscher
Cc: davieseb at scss.tcd.ie; stephen.farrell at cs.tcd.ie
Subject: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.=
txt


A new version of I-D, draft-kutscher-icnrg-netinf-proto-00.txt
has been successfully submitted by Dirk Kutscher and posted to the IETF rep=
ository.

Filename:	 draft-kutscher-icnrg-netinf-proto
Revision:	 00
Title:		 The NetInf Protocol
Creation date:	 2012-10-04
WG ID:		 Individual Submission
Number of pages: 21
URL:             http://www.ietf.org/internet-drafts/draft-kutscher-icnrg-n=
etinf-proto-00.txt
Status:          http://datatracker.ietf.org/doc/draft-kutscher-icnrg-netin=
f-proto
Htmlized:        http://tools.ietf.org/html/draft-kutscher-icnrg-netinf-pro=
to-00


Abstract:
   This document defines a conceptual protocol and corresponding node
   requirements for NetInf nodes in a NetInf network.  A NetInf network
   offers an information-centric paradigm that supports the creation,
   location, exchange and storage of Named Data Objects (NDOs).  NetInf
   nodes can provide different services to other NetInf nodes, e.g.,
   forwarding requests for information objects, delivering corresponding
   response messages, name resolution services etc.  This (abstract)
   protocol is intended to be run over some "convergence layer" that
   handles transport issues.  Two "wire" formats are defined, one that
   uses HTTP for message transfer and one layered on UDP.


	=09



From stephen.farrell@cs.tcd.ie  Fri Oct  5 03:03:27 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5CB21F8447 for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 03:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6K0LQGqMwUvS for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 03:03:26 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 8697921F8446 for <icnrg@irtf.org>; Fri,  5 Oct 2012 03:03:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id F1E1817147A; Fri,  5 Oct 2012 11:03:25 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1349431405; bh=uSHQXbJxeuNlgq i03PX2/ANXb10XHon11TIBP7+M8wg=; b=zLCkgUsmQJRlnEompjYB737a/W1R0p 79OjI3NVaHU2dHACoIQDBLVZwZ37iNxKOUVDK72nix2ze0XUbsoMCPw2hW8GW8pH YPL924hSSmNZWNQFZJHUUGQr9zRfOv4fuVmnO6YZSw47ikuWMIaQZsR8lhqDE7Uq gE0JIYusC5cVYCqdILjFme2M56qSVLVbGq6PO+m6zGUaajp7RTfmGypL9vePyzpE DJF6xwxaYij2fqaIN9VB/LU8/XP4vjbnTYcwYb07C5SxkfPPspIZTzK7lRpFJdgq ZfmKtzamAbEl7AhTJZrTuq+kKwIgt4XfMc7OmfMwf8BaJuGKUZjN0/RA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id eF9wRsBja-Zv; Fri,  5 Oct 2012 11:03:25 +0100 (IST)
Received: from [IPv6:2001:770:10:203:d04a:5e0:fbf4:d40b] (unknown [IPv6:2001:770:10:203:d04a:5e0:fbf4:d40b]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 25F4C171471; Fri,  5 Oct 2012 11:03:25 +0100 (IST)
Message-ID: <506EB06D.10902@cs.tcd.ie>
Date: Fri, 05 Oct 2012 11:03:25 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
References: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1C@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1C@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: icnrg@irtf.org
Subject: Re: [icnrg] FW: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt, 
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 10:03:27 -0000

Hi Lloyd,

I see the drum you constantly bang hasn't broken:-)

I'll not bother addressing your stale dtn-related gripes
but there are a couple of substantive points in your mail...

On 10/05/2012 10:12 AM, l.wood@surrey.ac.uk wrote:
>
> Sensibly, in the ni draft below,
> section 3 calls out the requirements that convergence layers
> must meet:
> "   Each CL has to offer the following minimal set of capabilities:
>    o  unidirectional point-to-point transport of NetInf messages from
>       source to destination,
>    o  preservation of message boundaries,
>    o  reliable transmission of message octets, and
>    o  in-order delivery of message octets to the destination node."
> 
> Unfortunately, neither of the convergence layers proposed in the
> draft meets those stated requirements: 

I agree that we've not yet sorted this. That's the nice thing
about -00 drafts and experimental code, they can get fixed.

> neither HTTP or UDP is by
> itself reliable. (And, strictly speaking, neither is really much good as
> a transport.)
> 
> HTTP would need Content-MD5: or similar as a minimum; UDP needs
> a transport shim like LTP or Saratoga. 

That's worth considering. To be honest, we're not sure what
protection netinf messages need in this respect given how
nodes can change responses and given the ability to verify
name-data integrity.

Content-MD5 for the HTTP-CL might be useful/good-enough and
is worth a look though, or it might be better to add a checksum
and/or (and I know you'll love this:-) the ability to sign/MAC
into the NetInf messages themselves. We've thought about that
but haven't landed on answers we're really happy with so far.

> And HTTP and UDP aren't
> remotely similar in semantics or capabilities, in terms of message size,
> security capabilities, content identification (MIME is not a port), etc.

True. The UDP CL is intended more for particular cases that
we've not documented in the draft yet. The idea is to use UDP
mainly for dealing with/finding a name resolution service
rather than for potentially large objects. We figured it was
better to start documenting it though.

Regards,
S.


From l.wood@surrey.ac.uk  Fri Oct  5 18:44:16 2012
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22BA321F8667 for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 18:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNZ4NSFxuYpz for <icnrg@ietfa.amsl.com>; Fri,  5 Oct 2012 18:44:14 -0700 (PDT)
Received: from mail72.messagelabs.com (mail72.messagelabs.com [193.109.255.147]) by ietfa.amsl.com (Postfix) with ESMTP id 47DE721F865D for <icnrg@irtf.org>; Fri,  5 Oct 2012 18:44:14 -0700 (PDT)
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-72.messagelabs.com!1349487853!14863033!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8447 invoked from network); 6 Oct 2012 01:44:13 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-14.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 6 Oct 2012 01:44:13 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.203]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sat, 6 Oct 2012 02:44:12 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>
Date: Sat, 6 Oct 2012 02:44:05 +0100
Thread-Topic: [icnrg] FW: New Version Notification for draft-kutscher-icnrg-netinf-proto-00.txt, 
Thread-Index: Ac2i4K5s+JNjw5XpQaWc7ugKHg1EHAAgj1Ne
Message-ID: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1F@EXMB01CMS.surrey.ac.uk>
References: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1C@EXMB01CMS.surrey.ac.uk>, <506EB06D.10902@cs.tcd.ie>
In-Reply-To: <506EB06D.10902@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: icnrg@irtf.org
Subject: Re: [icnrg] FW: New Version Notification for	draft-kutscher-icnrg-netinf-proto-00.txt, 
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Oct 2012 01:44:16 -0000

Stephen,

alas, as the deficient designs of LTP-T and the bundle protocol have demons=
trated,
that reliability drum has to be banged.

Fixing problems with -00 drafts is the normal way of things, when new conce=
pts
are tried, described, and fleshed out. However, I am concerned that your
new icnrg draft hasn't learned anything from five years of thinking about
convergence layers in the dtnrg, and is now proposing exactly the same
mistakes to a new audience. If my dtn-related gripes are stale, so are your
'new' dtn-related ideas.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: icnrg-bounces@irtf.org [icnrg-bounces@irtf.org] On Behalf Of Stephen =
Farrell [stephen.farrell@cs.tcd.ie]
Sent: 05 October 2012 11:03
To: Wood L  Dr (Electronic Eng)
Cc: icnrg@irtf.org
Subject: Re: [icnrg] FW: New Version Notification for   draft-kutscher-icnr=
g-netinf-proto-00.txt,

Hi Lloyd,

I see the drum you constantly bang hasn't broken:-)

I'll not bother addressing your stale dtn-related gripes
but there are a couple of substantive points in your mail...

On 10/05/2012 10:12 AM, l.wood@surrey.ac.uk wrote:
>
> Sensibly, in the ni draft below,
> section 3 calls out the requirements that convergence layers
> must meet:
> "   Each CL has to offer the following minimal set of capabilities:
>    o  unidirectional point-to-point transport of NetInf messages from
>       source to destination,
>    o  preservation of message boundaries,
>    o  reliable transmission of message octets, and
>    o  in-order delivery of message octets to the destination node."
>
> Unfortunately, neither of the convergence layers proposed in the
> draft meets those stated requirements:

I agree that we've not yet sorted this. That's the nice thing
about -00 drafts and experimental code, they can get fixed.

> neither HTTP or UDP is by
> itself reliable. (And, strictly speaking, neither is really much good as
> a transport.)
>
> HTTP would need Content-MD5: or similar as a minimum; UDP needs
> a transport shim like LTP or Saratoga.

That's worth considering. To be honest, we're not sure what
protection netinf messages need in this respect given how
nodes can change responses and given the ability to verify
name-data integrity.

Content-MD5 for the HTTP-CL might be useful/good-enough and
is worth a look though, or it might be better to add a checksum
and/or (and I know you'll love this:-) the ability to sign/MAC
into the NetInf messages themselves. We've thought about that
but haven't landed on answers we're really happy with so far.

> And HTTP and UDP aren't
> remotely similar in semantics or capabilities, in terms of message size,
> security capabilities, content identification (MIME is not a port), etc.

True. The UDP CL is intended more for particular cases that
we've not documented in the draft yet. The idea is to use UDP
mainly for dealing with/finding a name resolution service
rather than for potentially large objects. We figured it was
better to start documenting it though.

Regards,
S.


From Borje.Ohlman@ericsson.com  Mon Oct  8 01:00:07 2012
Return-Path: <Borje.Ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F97D21F86EA for <icnrg@ietfa.amsl.com>; Mon,  8 Oct 2012 01:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPtzsQ3ygriU for <icnrg@ietfa.amsl.com>; Mon,  8 Oct 2012 01:00:06 -0700 (PDT)
Received: from violet.abc.se (violet.abc.se [IPv6:2001:16d8:ffdc:0:230:48ff:fe80:2929]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA8821F86E8 for <icnrg@irtf.org>; Mon,  8 Oct 2012 01:00:06 -0700 (PDT)
Received: from [172.16.4.200] (static-213-115-148-132.sme.bredbandsbolaget.se [213.115.148.132]) (authenticated bits=0) by violet.abc.se (8.13.8/8.13.8) with ESMTP id q98800lN009168 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <icnrg@irtf.org>; Mon, 8 Oct 2012 10:00:01 +0200
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AF178D32-0144-4B06-B266-A1849CF1EE6D"
Date: Mon, 8 Oct 2012 10:00:00 +0200
Message-Id: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
To: icnrg <icnrg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2 (violet.abc.se [62.80.200.155]); Mon, 08 Oct 2012 10:00:01 +0200 (MEST)
Subject: [icnrg] Announcing  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 08:00:07 -0000

--Apple-Mail=_AF178D32-0144-4B06-B266-A1849CF1EE6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA, November =
4-9, 2012
      * Meeting time: WEDNESDAY 13.00-15.40 (prel)

The main discussion at the meeting will be the three documents that the =
RG has set out to produce.=20
ICN Survey document
A document that provides a survey of different approaches and techniques
ICN Problem statement
A document that describes the ICN problem statement, the main concepts =
and research challenges in depth.
ICN Baseline Scenarios
A document that defines reference baseline scenarios to enable =
performance comparisons between different approaches.
People are encouraged to present their views on what they think should =
be the contents of these documents. Early contributions (in bullet form =
or as draft text) are welcome both on the mailing list and the wiki. =
Presentations of draft material are welcome at the meeting.

Most likely we will also have time to discuss one or two specific =
technical topics at the meeting. Proposals for such topics as well as =
presentations are invited.

As we are expected to publish our agenda by 2012-10-24 (Wednesday) we =
would like to have your input by Sunday 2012-10-21.

	B=F6rje, Dave & Dirk


ICN RG Wiki:
http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg=

--Apple-Mail=_AF178D32-0144-4B06-B266-A1849CF1EE6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>The next ICNRG will be held at &nbsp;IETF 85, Atlanta, Georgia, =
USA, November 4-9, 2012</div><div>&nbsp; &nbsp; &nbsp; * Meeting time: =
WEDNESDAY 13.00-15.40 (prel)</div><div><br></div><div>The main =
discussion at the meeting will be the three documents that the RG has =
set out to produce.&nbsp;</div><div><ul style=3D"color: rgb(0, 0, 0); =
font-family: 'Times New Roman', times, serif; font-size: 15px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); =
"><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnSurveyDocument"=
 style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Survey document</a><ul><li>A document =
that provides a survey of different approaches and =
techniques</li></ul></li><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnProblemStatemen=
t" style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Problem statement</a><ul><li>A document =
that describes the ICN problem statement, the main concepts and research =
challenges in depth.</li></ul></li><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnBaselineScenari=
os" style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Baseline Scenarios</a><ul><li>A document =
that defines reference baseline scenarios to enable performance =
comparisons between different =
approaches.</li></ul></li></ul></div><div>People are encouraged to =
present their views on what they think should be the contents of these =
documents. Early contributions (in bullet form or as draft text) are =
welcome both on the mailing list and the wiki. Presentations of draft =
material are welcome at the meeting.</div><div><br></div><div>Most =
likely we will also have time to discuss one or two specific technical =
topics at the meeting. Proposals for such topics as well as =
presentations are invited.</div><div><br></div><div>As we are expected =
to publish our agenda by 2012-10-24 (Wednesday) we would like to have =
your input by Sunday 2012-10-21.</div><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>B=F6rje, =
Dave &amp; Dirk</div><div><br></div><div><br></div><div>ICN RG =
Wiki:</div><div><ul class=3D"MailOutline"><li><a =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg">http://trac=
.tools.ietf.org/group/irtf/trac/wiki/icnrg</a></li></ul></div></body></htm=
l>=

--Apple-Mail=_AF178D32-0144-4B06-B266-A1849CF1EE6D--

From Dirk.Kutscher@neclab.eu  Tue Oct  9 09:59:27 2012
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C09DE1F0C9B for <icnrg@ietfa.amsl.com>; Tue,  9 Oct 2012 09:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tOep65C0My1S for <icnrg@ietfa.amsl.com>; Tue,  9 Oct 2012 09:59:26 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 977D31F0C99 for <icnrg@irtf.org>; Tue,  9 Oct 2012 09:59:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id EC5561020D2; Tue,  9 Oct 2012 18:59:25 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uUec7dm4vbYd; Tue,  9 Oct 2012 18:59:25 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id CAD8F1020CE; Tue,  9 Oct 2012 18:59:10 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.21]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Tue, 9 Oct 2012 18:58:50 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "stephen.farrell@cs.tcd.ie" <stephen.farrell@cs.tcd.ie>
Thread-Topic: [icnrg] FW: New Version Notification	for draft-kutscher-icnrg-netinf-proto-00.txt, 
Thread-Index: AQHNo2QkREFD41MeYEWnj91p/rO6yJexNsFQ
Date: Tue, 9 Oct 2012 16:58:49 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F5249550E50B6@PALLENE.office.hd>
References: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1C@EXMB01CMS.surrey.ac.uk>, <506EB06D.10902@cs.tcd.ie> <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1F@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <FD7B10366AE3794AB1EC5DE97A93A37341C857DB1F@EXMB01CMS.surrey.ac.uk>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.204]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "icnrg@irtf.org" <icnrg@irtf.org>
Subject: Re: [icnrg] FW: New Version Notification	for	draft-kutscher-icnrg-netinf-proto-00.txt, 
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 16:59:27 -0000

Lloyd,

This is something different than the Bundle protocol. Regarding reliability=
, the one option (not specified in the draft) is that you'd use a (receiver=
-driven) transport protocol on top -- for example with the NetInf UDP CL.

Best regards,
Dirk


> -----Original Message-----
> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of
> l.wood@surrey.ac.uk
> Sent: Samstag, 6. Oktober 2012 03:44
> To: stephen.farrell@cs.tcd.ie
> Cc: icnrg@irtf.org
> Subject: Re: [icnrg] FW: New Version Notification for draft-kutscher-icnr=
g-
> netinf-proto-00.txt,
>=20
> Stephen,
>=20
> alas, as the deficient designs of LTP-T and the bundle protocol have
> demonstrated, that reliability drum has to be banged.
>=20
> Fixing problems with -00 drafts is the normal way of things, when new
> concepts are tried, described, and fleshed out. However, I am concerned
> that your new icnrg draft hasn't learned anything from five years of thin=
king
> about convergence layers in the dtnrg, and is now proposing exactly the
> same mistakes to a new audience. If my dtn-related gripes are stale, so a=
re
> your 'new' dtn-related ideas.
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: icnrg-bounces@irtf.org [icnrg-bounces@irtf.org] On Behalf Of Stephe=
n
> Farrell [stephen.farrell@cs.tcd.ie]
> Sent: 05 October 2012 11:03
> To: Wood L  Dr (Electronic Eng)
> Cc: icnrg@irtf.org
> Subject: Re: [icnrg] FW: New Version Notification for   draft-kutscher-ic=
nrg-
> netinf-proto-00.txt,
>=20
> Hi Lloyd,
>=20
> I see the drum you constantly bang hasn't broken:-)
>=20
> I'll not bother addressing your stale dtn-related gripes but there are a =
couple
> of substantive points in your mail...
>=20
> On 10/05/2012 10:12 AM, l.wood@surrey.ac.uk wrote:
> >
> > Sensibly, in the ni draft below,
> > section 3 calls out the requirements that convergence layers must
> > meet:
> > "   Each CL has to offer the following minimal set of capabilities:
> >    o  unidirectional point-to-point transport of NetInf messages from
> >       source to destination,
> >    o  preservation of message boundaries,
> >    o  reliable transmission of message octets, and
> >    o  in-order delivery of message octets to the destination node."
> >
> > Unfortunately, neither of the convergence layers proposed in the draft
> > meets those stated requirements:
>=20
> I agree that we've not yet sorted this. That's the nice thing about -00 d=
rafts
> and experimental code, they can get fixed.
>=20
> > neither HTTP or UDP is by
> > itself reliable. (And, strictly speaking, neither is really much good
> > as a transport.)
> >
> > HTTP would need Content-MD5: or similar as a minimum; UDP needs a
> > transport shim like LTP or Saratoga.
>=20
> That's worth considering. To be honest, we're not sure what protection
> netinf messages need in this respect given how nodes can change responses
> and given the ability to verify name-data integrity.
>=20
> Content-MD5 for the HTTP-CL might be useful/good-enough and is worth a
> look though, or it might be better to add a checksum and/or (and I know
> you'll love this:-) the ability to sign/MAC into the NetInf messages
> themselves. We've thought about that but haven't landed on answers we're
> really happy with so far.
>=20
> > And HTTP and UDP aren't
> > remotely similar in semantics or capabilities, in terms of message
> > size, security capabilities, content identification (MIME is not a port=
), etc.
>=20
> True. The UDP CL is intended more for particular cases that we've not
> documented in the draft yet. The idea is to use UDP mainly for dealing
> with/finding a name resolution service rather than for potentially large
> objects. We figured it was better to start documenting it though.
>=20
> Regards,
> S.
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From liushucheng@huawei.com  Mon Oct 15 04:48:11 2012
Return-Path: <liushucheng@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C113421F872A for <icnrg@ietfa.amsl.com>; Mon, 15 Oct 2012 04:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKVOfuQSplqR for <icnrg@ietfa.amsl.com>; Mon, 15 Oct 2012 04:48:10 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id 2834621F871C for <icnrg@irtf.org>; Mon, 15 Oct 2012 04:48:09 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml206-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AQP22543; Mon, 15 Oct 2012 19:47:58 +0800 (CST)
Received: from SZXEML431-HUB.china.huawei.com (10.72.61.39) by szxeml206-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 15 Oct 2012 19:47:47 +0800
Received: from SZXEML546-MBS.china.huawei.com ([169.254.4.97]) by szxeml431-hub.china.huawei.com ([10.72.61.39]) with mapi id 14.01.0323.003; Mon, 15 Oct 2012 19:47:52 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-ren-icn-content-retrieval-00.txt
Thread-Index: AQHNqsfn9DKyKKvea0ee707d4pjoOZe6O1hw
Date: Mon, 15 Oct 2012 11:47:51 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "jingren@cityu.edu.hk" <jingren@cityu.edu.hk>, "jianwang@cityu.edu.hk" <jianwang@cityu.edu.hk>, "feitang@cityu.edu.hk" <feitang@cityu.edu.hk>
Subject: [icnrg] FW: New Version Notification for draft-ren-icn-content-retrieval-00.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 11:48:11 -0000

SGVsbG8sDQoNCldlIGhhdmUgc3VibWl0dGVkIGEgbmV3IGRyYWZ0IGRpc2N1c3NpbmcgYWJvdXQg
Y29udGVudCByZXRyaWV2YWwgaW4gSUNOLiBIZXJlLCB3ZSBkaXNjdXNzZWQgYmFzaWMgcmVxdWly
ZW1lbnRzIG9uIHRoZSBiYXNpcyBvZiBwcmV2aW91cyBsaXRlcmF0dXJlcywgdGhlIGZ1bmRhbWVu
dGFsIGZ1bmN0aW9uYWxpdGllcyByZXF1aXJlZCB0byBzYXRpc2Z5IHRoZSBmb3JlZ29pbmcgcmVx
dWlyZW1lbnRzLCBhbmQgdGhlIGltcGxlbWVudGF0aW9uIHN0YXR1cyBvZiBzdWNoIGZ1bmN0aW9u
YWxpdGllcyBpbiB2YXJpb3VzIEluZm9ybWF0aW9uLUNlbnRyaWMgTmV0d29yayBhcmNoaXRlY3R1
cmVzLg0KDQpZb3VyIGNvbW1lbnRzIGFyZSBoaWdobHkgYXBwcmVjaWF0ZWQuDQoNClJlZ2FyZHMs
DQpTaHVjaGVuZyBMSVUgKFdpbGwpDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRm
Lm9yZ10gDQpTZW50OiBNb25kYXksIE9jdG9iZXIgMTUsIDIwMTIgNzoyNiBQTQ0KVG86IFdpbGwg
TGl1IChTaHVjaGVuZykNCkNjOiBqaW5ncmVuQGNpdHl1LmVkdS5oazsgamlhbndhbmdAY2l0eXUu
ZWR1LmhrOyBmZWl0YW5nQGNpdHl1LmVkdS5oaw0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1yZW4taWNuLWNvbnRlbnQtcmV0cmlldmFsLTAwLnR4dA0KDQoNCkEg
bmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1yZW4taWNuLWNvbnRlbnQtcmV0cmlldmFsLTAwLnR4
dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBXaWxsIExpdSBhbmQgcG9zdGVk
IHRvIHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRyYWZ0LXJlbi1pY24tY29u
dGVudC1yZXRyaWV2YWwNClJldmlzaW9uOgkgMDANClRpdGxlOgkJIE9uIHRoZSBDb250ZW50IFJl
dHJpZXZhbCBJbiBJbmZvcm1hdGlvbi1DZW50cmljIE5ldHdvcmsNCkNyZWF0aW9uIGRhdGU6CSAy
MDEyLTEwLTE1DQpXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdl
czogMTENClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtcmVuLWljbi1jb250ZW50LXJldHJpZXZhbC0wMC50eHQNClN0YXR1czogICAgICAg
ICAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1yZW4taWNuLWNvbnRlbnQt
cmV0cmlldmFsDQpIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LXJlbi1pY24tY29udGVudC1yZXRyaWV2YWwtMDANCg0KDQpBYnN0cmFjdDoNCiAgIEluZm9y
bWF0aW9uLUNlbnRyaWMgTmV0d29yayhJQ04pLCBhcyBhbiBlbWVyZ2luZyBuZXR3b3JrDQogICBh
cmNoaXRlY3R1cmUsIGZvY3VzIG9uIGRlbGl2ZXJpbmcgY29udGVudCBtb3JlIGVmZmljaWVudGx5
LiAgVGhpcw0KICAgYnJpZWYgcGFwZXIgZGlzY3Vzc2VzIHNvbWUgaXNzdWVzIGFib3V0IGNvbnRl
bnQgcmV0cmlldmFsIGluIHRoZQ0KICAgSW5mb3JtYXRpb24tQ2VudHJpYyBOZXR3b3JrLiAgSXQg
Zmlyc3QgbGlzdHMgYSBzZXQgb2YgYmFzaWMNCiAgIHJlcXVpcmVtZW50cyBvbiB0aGUgYmFzaXMg
b2YgcHJldmlvdXMgbGl0ZXJhdHVyZXMuICBUaGVuLCBpdCB0cmllcyB0bw0KICAgaWRlbnRpZnkg
dGhlIGZ1bmRhbWVudGFsIGZ1bmN0aW9uYWxpdGllcyByZXF1aXJlZCB0byBzYXRpc2Z5IHRoZQ0K
ICAgZm9yZWdvaW5nIHJlcXVpcmVtZW50cy4gIExhc3QsIGl0IHN1bW1hcml6ZXMgdGhlIGltcGxl
bWVudGF0aW9uDQogICBzdGF0dXMgb2Ygc3VjaCBmdW5jdGlvbmFsaXRpZXMgaW4gdmFyaW91cyBJ
bmZvcm1hdGlvbi1DZW50cmljIE5ldHdvcmsNCiAgIGFyY2hpdGVjdHVyZXMuDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICANCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=

From elwynd@folly.org.uk  Mon Oct 15 12:57:39 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A3F21F899D for <icnrg@ietfa.amsl.com>; Mon, 15 Oct 2012 12:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.135
X-Spam-Level: 
X-Spam-Status: No, score=0.135 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTTP_ESCAPED_HOST=0.134]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5F9zUKhYg1n7 for <icnrg@ietfa.amsl.com>; Mon, 15 Oct 2012 12:57:37 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 8882C21F899C for <icnrg@irtf.org>; Mon, 15 Oct 2012 12:57:37 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1TNqn9-0001Jt-Jx for icnrg@irtf.org; Mon, 15 Oct 2012 20:57:35 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Mon, 15 Oct 2012 21:00:09 +0100
Message-Id: <1350331209.23621.353.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Subject: [icnrg] New release (0.2) of NetInf nilib software now available
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 19:57:39 -0000

Hi.

The SAIL project is pleased to announce that a new version (0.2) of the
NetInf nilib code is now available in the Sourceforge repository at
https://sourceforge.net/projects/netinf/files/nilib/
The downloadable file for version 0.2 corresponds to changeset 126 in 
the Mercurial repository (see note about Sourceforge at the end of this
email).

This fully updates the c, Python, ruby, and clojure and the java code 
partially code to the most recent version of the ni naming specification
and the convergence layers match the recently published protocol
specification draft.  The servers now return metadata for cached NDOs as
JSON encoded strings.  To visualize these strings conveniently, you may
find it useful to install a JSON viewer add-on in your browser.  Here
are some references to suitable add-ons for various browsers:
- JSONview as a plugin for Firefox 
(https://addons.mozilla.org/en-US/firefox/addon/jsonview/)
or Chrome 
(http://www.google.co.uk/url?sa=t&rct=j&q=jsonview%
20chrome&source=web&cd=1&cad=rja&ved=0CCMQFjAA&url=https%3A%2F%
2Fchrome.google.com%2Fwebstore%2Fdetail%2Fjsonview%
2Fchklaanhfefbnpoihckbnefhakgolnmc&ei=0SFuUMG_Csq30QX1_YDoCg&usg=AFQjCNGifPJiJxwt22KAA3bkqyOWO936mg) 

- For Mac's try http://www.macupdate.com/app/mac/30621/xml-view-plugin
(I don't have first hand evidence of how well this works)

- Apparently you can work around the non-functionality of Microsoft 
Internet Explorer by following the instructions on
http://www.west-wind.com/weblog/posts/2011/Apr/01/Displaying-JSON-in-your-Browser 


Other improvements include:
- First stages of NRS functionality in c, Python and ruby
- Python setuputils installer for Python code
- QRcode image display for cached NDOs in Python

Note: Sourceforge is currently overloaded with updates to the code pages
of their web site due to migration from the old web interface/project
store to the new version.  As a result the web interface was about 10
days and 14 changesets out of date. However ther epository itself is
up-to-date and cloning or pulling from the repository will get you the 
most recent version.

Have fun!  Feedback and bug reports most welcome.

Regards,
Elwyn and the other authors.
For the SAIL project
http://www.sail-project.eu


From seungiklee@gmail.com  Wed Oct 17 19:00:03 2012
Return-Path: <seungiklee@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08BDB1F0417 for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.677
X-Spam-Level: 
X-Spam-Status: No, score=-102.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eCDN+6AE0QAe for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:00:02 -0700 (PDT)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by ietfa.amsl.com (Postfix) with ESMTP id B62021F0381 for <icnrg@irtf.org>; Wed, 17 Oct 2012 19:00:01 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id b5so6837301lbd.13 for <icnrg@irtf.org>; Wed, 17 Oct 2012 19:00:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ZLFI5kVxxFXtMDWrU+RGv1/5iEJrDhEEzxGZme6RwqY=; b=ECh6saityFElhji0poOM+WnRsUxakQ6QmurzpgbGOrNfA2bz2SMGkqfno8AZj+kB+Z /gHN79A0RorLTauDKtJ4TR9bwwtQiN3T7qdDZWDbi4n5+f3NwcX2ivL3bF5d5mrAo7g0 ctfMYVA6BX3tFrljdkhZPwlRLtU9n16mCl8YhTaFlmIL1o7nkIShgZdVEJacONjDwzcx 5nmAe7rHkOh7nOpXQ3yYlgZIeJ1JlSnCLzckOkueUzhDb65HAfHnbLZyl1govfwAutTX kh5VvOpn9cx8SIqXwJLRBQolzxHD+QamyA8AnSouBrXE5iPrmdVIxxPGl+YtD4bO8Bac b8iQ==
Received: by 10.152.103.100 with SMTP id fv4mr16879039lab.39.1350525600427; Wed, 17 Oct 2012 19:00:00 -0700 (PDT)
MIME-Version: 1.0
Sender: seungiklee@gmail.com
Received: by 10.114.68.70 with HTTP; Wed, 17 Oct 2012 18:59:40 -0700 (PDT)
In-Reply-To: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
From: Seung-Ik Lee <seungiklee@etri.re.kr>
Date: Thu, 18 Oct 2012 10:59:40 +0900
X-Google-Sender-Auth: NsymG4BrY5KmtF5mh0469hyMsq4
Message-ID: <CAHMWmA9YbizkTxCz8kk=WFDxqtbD0HM1dLOKgnb_GbgU8bQ_Aw@mail.gmail.com>
To: =?UTF-8?Q?B=C3=B6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 02:03:00 -0000

Dear icnrg colleagues,

Regarding the RG documents, don't we touch any issues on ICN deployments?

As we have seen in the presentation by ZTE in Vancouver, ISPs are
interested in the short-term approaches to ICN.
Though the traditional ICN approaches (such as CCN/NDN) have provided
ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
clean-slate approaches of ICN.
IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
are in the similar situation.

In this motivation, I have interests in ICN deployment strategies
(such as ICN over IP or ICN over SDN as short-term approaches)
but no idea which RG document would cover the deployment issues, even
whether icnrg will cover the deployment issue or not.


2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA, November
> 4-9, 2012
>       * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>
> The main discussion at the meeting will be the three documents that the R=
G
> has set out to produce.
>
> ICN Survey document
>
> A document that provides a survey of different approaches and techniques
>
> ICN Problem statement
>
> A document that describes the ICN problem statement, the main concepts an=
d
> research challenges in depth.
>
> ICN Baseline Scenarios
>
> A document that defines reference baseline scenarios to enable performanc=
e
> comparisons between different approaches.
>
> People are encouraged to present their views on what they think should be
> the contents of these documents. Early contributions (in bullet form or a=
s
> draft text) are welcome both on the mailing list and the wiki. Presentati=
ons
> of draft material are welcome at the meeting.
>
> Most likely we will also have time to discuss one or two specific technic=
al
> topics at the meeting. Proposals for such topics as well as presentations
> are invited.
>
> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we wou=
ld
> like to have your input by Sunday 2012-10-21.
>
> B=C3=B6rje, Dave & Dirk
>
>
> ICN RG Wiki:
>
> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>



--=20
Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
Standards Research Center, ETRI
Tel.    +82-42-860-1483
Fax.   +82-42-861-5404
Email. seungiklee@etri.re.kr

From Dirk.Kutscher@neclab.eu  Wed Oct 17 19:44:29 2012
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6887421F85E6 for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07tHEQr4O8Vr for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:44:28 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 666AB21F85D5 for <icnrg@irtf.org>; Wed, 17 Oct 2012 19:44:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id C2E1B102222; Thu, 18 Oct 2012 04:44:27 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mri-olHgWsRp; Thu, 18 Oct 2012 04:44:27 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id A565E10215D; Thu, 18 Oct 2012 04:44:17 +0200 (CEST)
Received: from DAPHNIS.office.hd ([169.254.2.239]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Thu, 18 Oct 2012 04:43:56 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: Seung-Ik Lee <seungiklee@etri.re.kr>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNTAf6/ot/eLqkyUBui6HUP0npe+Wqug
Date: Thu, 18 Oct 2012 02:44:06 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F524955106324@DAPHNIS.office.hd>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA9YbizkTxCz8kk=WFDxqtbD0HM1dLOKgnb_GbgU8bQ_Aw@mail.gmail.com>
In-Reply-To: <CAHMWmA9YbizkTxCz8kk=WFDxqtbD0HM1dLOKgnb_GbgU8bQ_Aw@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.212]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 02:44:29 -0000

SGVsbG8gU2V1bmctSWsgTGVlLA0KDQpZZXMsIHRoYXQncyBhIGdvb2QgcG9pbnQuIEhvdyBhYm91
dCBpbmNsdWRpbmcgdGhhdCBpbiB0aGUgcHJvYmxlbSBzdGF0ZW1lbnQ/DQoNCkJlc3QgcmVnYXJk
cywNCkRpcmsNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpY25yZy1i
b3VuY2VzQGlydGYub3JnIFttYWlsdG86aWNucmctYm91bmNlc0BpcnRmLm9yZ10gT24gQmVoYWxm
IE9mDQo+IFNldW5nLUlrIExlZQ0KPiBTZW50OiBEb25uZXJzdGFnLCAxOC4gT2t0b2JlciAyMDEy
IDA0OjAwDQo+IFRvOiBCw7ZyamUgT2hsbWFuDQo+IENjOiBpY25yZw0KPiBTdWJqZWN0OiBSZTog
W2ljbnJnXSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0KPiANCj4gRGVhciBpY25yZyBjb2xs
ZWFndWVzLA0KPiANCj4gUmVnYXJkaW5nIHRoZSBSRyBkb2N1bWVudHMsIGRvbid0IHdlIHRvdWNo
IGFueSBpc3N1ZXMgb24gSUNODQo+IGRlcGxveW1lbnRzPw0KPiANCj4gQXMgd2UgaGF2ZSBzZWVu
IGluIHRoZSBwcmVzZW50YXRpb24gYnkgWlRFIGluIFZhbmNvdXZlciwgSVNQcyBhcmUgaW50ZXJl
c3RlZA0KPiBpbiB0aGUgc2hvcnQtdGVybSBhcHByb2FjaGVzIHRvIElDTi4NCj4gVGhvdWdoIHRo
ZSB0cmFkaXRpb25hbCBJQ04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04vTkROKSBoYXZlIHByb3Zp
ZGVkDQo+IElTUHMgYSBsYWRkZXIgb3V0IG9mIGR1bWItcGlwZXMsIElTUHMgbWF5IGhhdmUgZGlm
ZmljdWx0aWVzIG9uIGNsZWFuLXNsYXRlDQo+IGFwcHJvYWNoZXMgb2YgSUNOLg0KPiBJTUhPLCBi
YXNlZCBvbiBvdXIgc3VydmV5cyBvbiBJU1AgUiZEIGFwcHJvYWNoZXMgdG8gSUNOLCBLb3JlYW4g
SVNQcyBhcmUNCj4gaW4gdGhlIHNpbWlsYXIgc2l0dWF0aW9uLg0KPiANCj4gSW4gdGhpcyBtb3Rp
dmF0aW9uLCBJIGhhdmUgaW50ZXJlc3RzIGluIElDTiBkZXBsb3ltZW50IHN0cmF0ZWdpZXMgKHN1
Y2ggYXMgSUNODQo+IG92ZXIgSVAgb3IgSUNOIG92ZXIgU0ROIGFzIHNob3J0LXRlcm0gYXBwcm9h
Y2hlcykgYnV0IG5vIGlkZWEgd2hpY2ggUkcNCj4gZG9jdW1lbnQgd291bGQgY292ZXIgdGhlIGRl
cGxveW1lbnQgaXNzdWVzLCBldmVuIHdoZXRoZXIgaWNucmcgd2lsbCBjb3Zlcg0KPiB0aGUgZGVw
bG95bWVudCBpc3N1ZSBvciBub3QuDQo+IA0KPiANCj4gMjAxMi8xMC84IELDtnJqZSBPaGxtYW4g
PEJvcmplLk9obG1hbkBlcmljc3Nvbi5jb20+Og0KPiA+IFRoZSBuZXh0IElDTlJHIHdpbGwgYmUg
aGVsZCBhdCAgSUVURiA4NSwgQXRsYW50YSwgR2VvcmdpYSwgVVNBLA0KPiA+IE5vdmVtYmVyIDQt
OSwgMjAxMg0KPiA+ICAgICAgICogTWVldGluZyB0aW1lOiBXRURORVNEQVkgMTMuMDAtMTUuNDAg
KHByZWwpDQo+ID4NCj4gPiBUaGUgbWFpbiBkaXNjdXNzaW9uIGF0IHRoZSBtZWV0aW5nIHdpbGwg
YmUgdGhlIHRocmVlIGRvY3VtZW50cyB0aGF0DQo+ID4gdGhlIFJHIGhhcyBzZXQgb3V0IHRvIHBy
b2R1Y2UuDQo+ID4NCj4gPiBJQ04gU3VydmV5IGRvY3VtZW50DQo+ID4NCj4gPiBBIGRvY3VtZW50
IHRoYXQgcHJvdmlkZXMgYSBzdXJ2ZXkgb2YgZGlmZmVyZW50IGFwcHJvYWNoZXMgYW5kDQo+ID4g
dGVjaG5pcXVlcw0KPiA+DQo+ID4gSUNOIFByb2JsZW0gc3RhdGVtZW50DQo+ID4NCj4gPiBBIGRv
Y3VtZW50IHRoYXQgZGVzY3JpYmVzIHRoZSBJQ04gcHJvYmxlbSBzdGF0ZW1lbnQsIHRoZSBtYWlu
IGNvbmNlcHRzDQo+ID4gYW5kIHJlc2VhcmNoIGNoYWxsZW5nZXMgaW4gZGVwdGguDQo+ID4NCj4g
PiBJQ04gQmFzZWxpbmUgU2NlbmFyaW9zDQo+ID4NCj4gPiBBIGRvY3VtZW50IHRoYXQgZGVmaW5l
cyByZWZlcmVuY2UgYmFzZWxpbmUgc2NlbmFyaW9zIHRvIGVuYWJsZQ0KPiA+IHBlcmZvcm1hbmNl
IGNvbXBhcmlzb25zIGJldHdlZW4gZGlmZmVyZW50IGFwcHJvYWNoZXMuDQo+ID4NCj4gPiBQZW9w
bGUgYXJlIGVuY291cmFnZWQgdG8gcHJlc2VudCB0aGVpciB2aWV3cyBvbiB3aGF0IHRoZXkgdGhp
bmsgc2hvdWxkDQo+ID4gYmUgdGhlIGNvbnRlbnRzIG9mIHRoZXNlIGRvY3VtZW50cy4gRWFybHkg
Y29udHJpYnV0aW9ucyAoaW4gYnVsbGV0DQo+ID4gZm9ybSBvciBhcyBkcmFmdCB0ZXh0KSBhcmUg
d2VsY29tZSBib3RoIG9uIHRoZSBtYWlsaW5nIGxpc3QgYW5kIHRoZQ0KPiA+IHdpa2kuIFByZXNl
bnRhdGlvbnMgb2YgZHJhZnQgbWF0ZXJpYWwgYXJlIHdlbGNvbWUgYXQgdGhlIG1lZXRpbmcuDQo+
ID4NCj4gPiBNb3N0IGxpa2VseSB3ZSB3aWxsIGFsc28gaGF2ZSB0aW1lIHRvIGRpc2N1c3Mgb25l
IG9yIHR3byBzcGVjaWZpYw0KPiA+IHRlY2huaWNhbCB0b3BpY3MgYXQgdGhlIG1lZXRpbmcuIFBy
b3Bvc2FscyBmb3Igc3VjaCB0b3BpY3MgYXMgd2VsbCBhcw0KPiA+IHByZXNlbnRhdGlvbnMgYXJl
IGludml0ZWQuDQo+ID4NCj4gPiBBcyB3ZSBhcmUgZXhwZWN0ZWQgdG8gcHVibGlzaCBvdXIgYWdl
bmRhIGJ5IDIwMTItMTAtMjQgKFdlZG5lc2RheSkgd2UNCj4gPiB3b3VsZCBsaWtlIHRvIGhhdmUg
eW91ciBpbnB1dCBieSBTdW5kYXkgMjAxMi0xMC0yMS4NCj4gPg0KPiA+IELDtnJqZSwgRGF2ZSAm
IERpcmsNCj4gPg0KPiA+DQo+ID4gSUNOIFJHIFdpa2k6DQo+ID4NCj4gPiBodHRwOi8vdHJhYy50
b29scy5pZXRmLm9yZy9ncm91cC9pcnRmL3RyYWMvd2lraS9pY25yZw0KPiA+DQo+ID4NCj4gPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IGljbnJn
IG1haWxpbmcgbGlzdA0KPiA+IGljbnJnQGlydGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaXJ0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9pY25yZw0KPiA+DQo+IA0KPiANCj4gDQo+IC0tDQo+IFNldW5n
LUlrIExlZSAo7J207Iq57J21KQ0KPiBTdGFuZGFyZHMgUmVzZWFyY2ggQ2VudGVyLCBFVFJJDQo+
IFRlbC4gICAgKzgyLTQyLTg2MC0xNDgzDQo+IEZheC4gICArODItNDItODYxLTU0MDQNCj4gRW1h
aWwuIHNldW5naWtsZWVAZXRyaS5yZS5rcg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiBpY25yZyBtYWlsaW5nIGxpc3QNCj4gaWNucmdAaXJ0Zi5v
cmcNCj4gaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pY25yZw0K

From borje.ohlman@ericsson.com  Wed Oct 17 19:55:17 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501FC21F845A for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSs5qD76TD8U for <icnrg@ietfa.amsl.com>; Wed, 17 Oct 2012 19:55:16 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1652821F844B for <icnrg@irtf.org>; Wed, 17 Oct 2012 19:55:15 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-1c-507f6f92c22a
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 5F.F5.04547.29F6F705; Thu, 18 Oct 2012 04:55:14 +0200 (CEST)
Received: from ESESSHC021.ericsson.se (153.88.183.81) by esessmw0191.eemea.ericsson.se (153.88.115.84) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 18 Oct 2012 04:55:14 +0200
Received: from ESESSMB107.ericsson.se ([169.254.7.89]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 04:55:14 +0200
From: =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman@ericsson.com>
To: Seung-Ik Lee <seungiklee@etri.re.kr>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNO74aIifGUZN0CW95Pc5hSV1pe+XlVP
Date: Thu, 18 Oct 2012 02:55:13 +0000
Message-ID: <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com>
In-Reply-To: <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM+Jvre6k/PoAg9/dhhY7Z+9ksti8cw+7 A5PH1s8PGT0mbzzMFsAUxWWTkpqTWZZapG+XwJVxf98e9oJJ6hVXtzUzNzBOUOti5OSQEDCR eL7+GwuELSZx4d56ti5GLg4hgVOMEvPmfWSGcHYySuxq+c4C4SxmlJiy6DhYC5uAk8Sy80/Z QWwRAQ2JL5N/M3YxcnAwC0hJ3G6tAAkLC+hL3Ni4kQWixEDi1L5vULaRxM+tj9hAbBYBVYlH vd9YQWxeAXuJvX2noK5oYZRoX7EIbD6nQKDEhSUbmEBsRgFZiS+Nq5lBbGYBcYnPcx8wQbwg ILFkz3lmCFtU4uXjf6wQ92hKrN+lD1GuKDGl+yE7xC5BiZMzn4DdIySgJnH8wzHmCYzis5BM nYXQPQtJ9ywk3QsYWVYxCucmZuaklxvppRZlJhcX5+fpFaduYgTG1MEtv1V3MN45J3KIUZqD RUmc13rrHn8hgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjGI3vGULV+fHXZ7hsqkkuOfMnI+G cQqCS9tUVHXk2iosk0+XyJ5/+K56cgIzR+cj1kUJD0pmhxj7bn2xV/XzoSNZ1e6hpp6v501k aLp/be2+eWeizh06bRwtFD//1v7AdOZFR9beTZKUsxTx+MXqs82hoV9hBkNYkgM7r0bJok/z WeQTpxz5qMRSnJFoqMVcVJwIAMgpcRJ3AgAA
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 02:55:17 -0000

RGVhciBTZXVuZy1JaywNCg0KSSB0aGluayB5b3UgYnJpbmcgdXAgYSB2ZXJ5IGdvb2QgcG9pbnQu
IEkgYWdyZWUgdGhhdCBkZXBsb3ltZW50IGFuZCBtaWdyYXRpb24gaXNzdWVzIGFyZSB2ZXJ5IGlt
cG9ydGFudC4gSSBhbHNvIGFncmVlIHRoYXQgdGhleSBkb24ndCBzZWVtIGxpa2UgYSBnb29kIGZp
dCBmb3IgYW55IG9mIHRoZSBjdXJyZW50bHkgcHJvcG9zZWQgSUNOUkcgZG9jdW1lbnRzLiANCg0K
VGhlIHRocmVlIGRvY3VtZW50cyBsaXN0ZWQgYXMgY3VycmVudCB3b3JrIGl0ZW1zIGFyZSBpbiBu
byB3YXkgc2V0IGluIHN0b25lLCB0aGV5IHNob3VsZCBqdXN0IGJlIHNlZW4gYXMgYSBzdGFydGlu
ZyBwb2ludCBmb3Igb3VyIHdvcmsuIElmIHlvdSB3b3VsZCBsaWtlIHRvIHByb3Bvc2UgdGhlIFJH
IHRoYXQgd2Ugc2hvdWxkIHN0YXJ0IHdvcmtpbmcgb24gYSBkZXBsb3ltZW50IGRvY3VtZW50IHlv
dSBhcmUgbW9zdCB3ZWxjb21lIHRvIGRvIHNvLCB0aGF0IHdpbGwgbW9zdCBjZXJ0YWlubHkgYmUg
aW4gc2NvcGUgZm9yIG91ciBkaXNjdXNzaW9uIGluIEF0bGFudGEuDQoNCkFzIGEgZ2VuZXJhbCBj
b21tZW50IEkgYWxzbyBsaWtlIHRvIG1lbnRpb24gdGhhdCB3ZSBhcyBhbiBSRyBhcmUgbm90IGJv
dW5kIGJ5IGFsbCB0aGUgcnVsZXMgdGhhdCBhcHBseSB0byBJRVRGIFdHcywgZS5nLiB3ZSBhcmUg
ZnJlZSB0byBkaXNjdXNzIGxhdGUgY29udHJpYnV0aW9ucyBwcm9kdWNlZCBhZnRlciB0aGUgSUVU
RiBkcmFmdCBkZWFkbGluZXMuIFNvIGlmIHBlb3BsZSBmaW5kIHRoZSB0aW1lIHRvIHdyaXRlIHVw
IHNvbWUgbWF0ZXJpYWwgZm9yIHRoZSBJQ05SRyBhZnRlciB0aGUgSUVURiBkcmFmdHMgYXJlIGRv
bmUgdGhleSBhcmUgd2VsY29tZSB0byBhbm5vdW5jZSBpdCB0byB0aGUgSUNOUkcgbWFpbGluZyBs
aXN0LiBJZiB0aGUgZ3JvdXAgYWdyZWVzIHdlIGFyZSBmcmVlIHRvIGRpc2N1c3MgYWxzbyBzdWNo
IG1hdGVyaWFsIGF0IG91ciBtZWV0aW5nLA0KDQogICAgIELDtnJqZQ0KDQoxOCBva3QgMjAxMiBr
bC4gMDM6NTYgc2tyZXYgIlNldW5nLUlrIExlZSIgPHNldW5naWtsZWVAZXRyaS5yZS5rcj46DQoN
Cj4gRGVhciBpY25yZyBjb2xsZWFndWVzLA0KPiANCj4gUmVnYXJkaW5nIHRoZSBSRyBkb2N1bWVu
dHMsIGRvbid0IHdlIHRvdWNoIGFueSBpc3N1ZXMgb24gSUNOIGRlcGxveW1lbnRzPw0KPiANCj4g
QXMgd2UgaGF2ZSBzZWVuIGluIHRoZSBwcmVzZW50YXRpb24gYnkgWlRFIGluIFZhbmNvdXZlciwg
SVNQcyBhcmUNCj4gaW50ZXJlc3RlZCBpbiB0aGUgc2hvcnQtdGVybSBhcHByb2FjaGVzIHRvIElD
Ti4NCj4gVGhvdWdoIHRoZSB0cmFkaXRpb25hbCBJQ04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04v
TkROKSBoYXZlIHByb3ZpZGVkDQo+IElTUHMgYSBsYWRkZXIgb3V0IG9mIGR1bWItcGlwZXMsIElT
UHMgbWF5IGhhdmUgZGlmZmljdWx0aWVzIG9uDQo+IGNsZWFuLXNsYXRlIGFwcHJvYWNoZXMgb2Yg
SUNOLg0KPiBJTUhPLCBiYXNlZCBvbiBvdXIgc3VydmV5cyBvbiBJU1AgUiZEIGFwcHJvYWNoZXMg
dG8gSUNOLCBLb3JlYW4gSVNQcw0KPiBhcmUgaW4gdGhlIHNpbWlsYXIgc2l0dWF0aW9uLg0KPiAN
Cj4gSW4gdGhpcyBtb3RpdmF0aW9uLCBJIGhhdmUgaW50ZXJlc3RzIGluIElDTiBkZXBsb3ltZW50
IHN0cmF0ZWdpZXMNCj4gKHN1Y2ggYXMgSUNOIG92ZXIgSVAgb3IgSUNOIG92ZXIgU0ROIGFzIHNo
b3J0LXRlcm0gYXBwcm9hY2hlcykNCj4gYnV0IG5vIGlkZWEgd2hpY2ggUkcgZG9jdW1lbnQgd291
bGQgY292ZXIgdGhlIGRlcGxveW1lbnQgaXNzdWVzLCBldmVuDQo+IHdoZXRoZXIgaWNucmcgd2ls
bCBjb3ZlciB0aGUgZGVwbG95bWVudCBpc3N1ZSBvciBub3QuDQo+IA0KPiANCj4gDQo+IDIwMTIv
MTAvOCBCw7ZyamUgT2hsbWFuIDxCb3JqZS5PaGxtYW5AZXJpY3Nzb24uY29tPjoNCj4+IFRoZSBu
ZXh0IElDTlJHIHdpbGwgYmUgaGVsZCBhdCAgSUVURiA4NSwgQXRsYW50YSwgR2VvcmdpYSwgVVNB
LCBOb3ZlbWJlcg0KPj4gNC05LCAyMDEyDQo+PiAgICAgICogTWVldGluZyB0aW1lOiBXRURORVNE
QVkgMTMuMDAtMTUuNDAgKHByZWwpDQo+PiANCj4+IFRoZSBtYWluIGRpc2N1c3Npb24gYXQgdGhl
IG1lZXRpbmcgd2lsbCBiZSB0aGUgdGhyZWUgZG9jdW1lbnRzIHRoYXQgdGhlIFJHDQo+PiBoYXMg
c2V0IG91dCB0byBwcm9kdWNlLg0KPj4gDQo+PiBJQ04gU3VydmV5IGRvY3VtZW50DQo+PiANCj4+
IEEgZG9jdW1lbnQgdGhhdCBwcm92aWRlcyBhIHN1cnZleSBvZiBkaWZmZXJlbnQgYXBwcm9hY2hl
cyBhbmQgdGVjaG5pcXVlcw0KPj4gDQo+PiBJQ04gUHJvYmxlbSBzdGF0ZW1lbnQNCj4+IA0KPj4g
QSBkb2N1bWVudCB0aGF0IGRlc2NyaWJlcyB0aGUgSUNOIHByb2JsZW0gc3RhdGVtZW50LCB0aGUg
bWFpbiBjb25jZXB0cyBhbmQNCj4+IHJlc2VhcmNoIGNoYWxsZW5nZXMgaW4gZGVwdGguDQo+PiAN
Cj4+IElDTiBCYXNlbGluZSBTY2VuYXJpb3MNCj4+IA0KPj4gQSBkb2N1bWVudCB0aGF0IGRlZmlu
ZXMgcmVmZXJlbmNlIGJhc2VsaW5lIHNjZW5hcmlvcyB0byBlbmFibGUgcGVyZm9ybWFuY2UNCj4+
IGNvbXBhcmlzb25zIGJldHdlZW4gZGlmZmVyZW50IGFwcHJvYWNoZXMuDQo+PiANCj4+IFBlb3Bs
ZSBhcmUgZW5jb3VyYWdlZCB0byBwcmVzZW50IHRoZWlyIHZpZXdzIG9uIHdoYXQgdGhleSB0aGlu
ayBzaG91bGQgYmUNCj4+IHRoZSBjb250ZW50cyBvZiB0aGVzZSBkb2N1bWVudHMuIEVhcmx5IGNv
bnRyaWJ1dGlvbnMgKGluIGJ1bGxldCBmb3JtIG9yIGFzDQo+PiBkcmFmdCB0ZXh0KSBhcmUgd2Vs
Y29tZSBib3RoIG9uIHRoZSBtYWlsaW5nIGxpc3QgYW5kIHRoZSB3aWtpLiBQcmVzZW50YXRpb25z
DQo+PiBvZiBkcmFmdCBtYXRlcmlhbCBhcmUgd2VsY29tZSBhdCB0aGUgbWVldGluZy4NCj4+IA0K
Pj4gTW9zdCBsaWtlbHkgd2Ugd2lsbCBhbHNvIGhhdmUgdGltZSB0byBkaXNjdXNzIG9uZSBvciB0
d28gc3BlY2lmaWMgdGVjaG5pY2FsDQo+PiB0b3BpY3MgYXQgdGhlIG1lZXRpbmcuIFByb3Bvc2Fs
cyBmb3Igc3VjaCB0b3BpY3MgYXMgd2VsbCBhcyBwcmVzZW50YXRpb25zDQo+PiBhcmUgaW52aXRl
ZC4NCj4+IA0KPj4gQXMgd2UgYXJlIGV4cGVjdGVkIHRvIHB1Ymxpc2ggb3VyIGFnZW5kYSBieSAy
MDEyLTEwLTI0IChXZWRuZXNkYXkpIHdlIHdvdWxkDQo+PiBsaWtlIHRvIGhhdmUgeW91ciBpbnB1
dCBieSBTdW5kYXkgMjAxMi0xMC0yMS4NCj4+IA0KPj4gQsO2cmplLCBEYXZlICYgRGlyaw0KPj4g
DQo+PiANCj4+IElDTiBSRyBXaWtpOg0KPj4gDQo+PiBodHRwOi8vdHJhYy50b29scy5pZXRmLm9y
Zy9ncm91cC9pcnRmL3RyYWMvd2lraS9pY25yZw0KPj4gDQo+PiANCj4+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBpY25yZyBtYWlsaW5nIGxpc3QN
Cj4+IGljbnJnQGlydGYub3JnDQo+PiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2ljbnJnDQo+PiANCj4gDQo+IA0KPiANCj4gLS0gDQo+IFNldW5nLUlrIExlZSAo7J207Iq5
7J21KQ0KPiBTdGFuZGFyZHMgUmVzZWFyY2ggQ2VudGVyLCBFVFJJDQo+IFRlbC4gICAgKzgyLTQy
LTg2MC0xNDgzDQo+IEZheC4gICArODItNDItODYxLTU0MDQNCj4gRW1haWwuIHNldW5naWtsZWVA
ZXRyaS5yZS5rcg0K

From liushucheng@huawei.com  Thu Oct 18 02:08:39 2012
Return-Path: <liushucheng@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4951D21F843C for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.149
X-Spam-Level: 
X-Spam-Status: No, score=-4.149 tagged_above=-999 required=5 tests=[AWL=1.550,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulabTRp5+Fww for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:08:38 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id A5C9121F843A for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:08:37 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml211-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AQW06211; Thu, 18 Oct 2012 17:08:32 +0800 (CST)
Received: from SZXEML444-HUB.china.huawei.com (10.82.67.182) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 18 Oct 2012 17:07:58 +0800
Received: from SZXEML546-MBS.china.huawei.com ([169.254.4.97]) by szxeml444-hub.china.huawei.com ([10.82.67.182]) with mapi id 14.01.0323.003; Thu, 18 Oct 2012 17:07:57 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman@ericsson.com>, Seung-Ik Lee <seungiklee@etri.re.kr>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNwGMPJ6/CM0kkqRBQCqzkpRc5e+xVfg
Date: Thu, 18 Oct 2012 09:07:56 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com>
In-Reply-To: <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: =?utf-8?B?5Lu75amn?= <renjing@uestc.edu.cn>, icnrg <icnrg@irtf.org>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 09:08:39 -0000

SGksDQoNCk15IGdyb3VwIGFyZSBhbHNvIGludGVyZXN0ZWQgaW4gSUNOIGRlcGxveW1lbnQgYW5k
IGhhdmUgZG9uZSBzb21lIHN1cnZleSBvbiB0aGlzIG1hdHRlci4gVGhlIGRpc2N1c3Npb24gb24g
SUNOIGRlcGxveW1lbnQgaXMgYSBncmVhdCB0b3BpYyB3aGljaCBJU1BzIHdpbGwgZGVmaW5pdGVs
eSBiZSBpbnRlcmVzdGVkIGluLiBIZXJlIGFyZSBvdXIgMi1jZW50cy4gDQoNClRoZSBldm9sdmVt
ZW50IG9mIElDTiBtYXkgdGFrZSB0aGUgZm9sbG93aW5nIHRocmVlIGltcGxlbWVudGF0aW9uczog
aW50ZWdyYXRlZCB3aXRoIElQLCBvdmVyIElQIGFuZCBvdmVyIFNETi4gVGhlc2Ugc3RyYXRlZ2ll
cyBhbGwgY2FuIGhlbHAgdGhlIElTUCBzaGlmdCBmcm9tIHRoZSB0cmFkaXRpb25hbCBJUCB0byBJ
Q04uIFRoZSBvbmx5IHF1ZXN0aW9uIGlzIHdoaWNoIG9uZSBpcyB0aGUgYmVzdCBjaG9pY2UgZm9y
IGxhcmdlIHNjYWxlIGRlcGxveW1lbnQ/IA0KDQpJbnRlZ3JhdGVkIHdpdGggSVAgc3RyYXRlZ3kg
ZXh0ZW5kcyB0aGUgZXhpc3RpbmcgSVAgcHJvdG9jb2wgKElQIG9wdGlvbikgdG8gc3VwcG9ydCBJ
Q04uIFRoZSB1cGRhdGVkIElQIHJvdXRlciwgY2FsbGVkIGNvbnRlbnQgcm91dGVyLCB3aWxsIGRl
YWwgd2l0aCBzdWNoIHNwZWNpYWwgcGFja2V0cy4gSG93ZXZlciwgbWFueSByb3V0ZXJzIHdpdGgg
bm8gc3VwcG9ydCBvZiBzdWNoIGV4dGVuc2lvbiBtYXkgZGlyZWN0bHkgZHJvcCB0aGUgcGFja2V0
cyB3aXRoIGFuIHVua25vd24gSVAgb3B0aW9uLiANCg0KSUNOIG92ZXIgSVAgc3RyYXRlZ3kgdXNl
cyBhbiBvdmVybGF5IGFwcHJvYWNoLiBDb250ZW50LXJlbGF0ZWQgb3BlcmF0aW9uIHdpbGwgYmUg
cGVyZm9ybWVkIG9uIHRoZSBoaWdoIGxheWVyIGFuZCBDb250ZW50LXJlbGF0ZWQgaW5mb3JtYXRp
b24gd2lsbCBiZSBzZW50IHRocm91Z2ggYSB0dW5uZWwuIER1ZSB0byB0aGUgbGltaXRlZCBrbm93
bGVkZ2Ugb2YgcGh5c2ljYWwgdG9wb2xvZ3kgYW5kIHVubmVjZXNzYXJ5IHBhY2tldCBlbmNhcHN1
bGF0aW9uL2Rpc2NvbnNvbGF0aW9uLCB0aGUgZWZmaWNpZW5jeSBtYXkgYmUgbGltaXRlZC4gDQoN
CklDTiBvdmVyIFNETiBzdHJhdGVneSBleHBsb2l0cyBTRE4gY29udHJvbGxlciB0byBwZXJmb3Jt
IGNvbnRlbnQtcmVsYXRlZCBvcGVyYXRpb24uIEhvd2V2ZXIsIFNETiBpdHNlbGYgaXMgYW4gb25n
b2luZyBhcHByb2FjaCBhbmQgaXMgdHlwaWNhbGx5IHVzZWQgaW4gYSBsb2NhbCBkb21haW4uIFRo
ZSBwZXJmb3JtYW5jZSBpbiBhIGxhcmdlIHNjYWxlIGRlcGxveW1lbnQgaXMgdW5rbm93bi4gDQoN
CldpbGwNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpY25yZy1ib3Vu
Y2VzQGlydGYub3JnIFttYWlsdG86aWNucmctYm91bmNlc0BpcnRmLm9yZ10gT24gQmVoYWxmIE9m
DQo+IEI/cmplIE9obG1hbg0KPiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOCwgMjAxMiAxMDo1
NSBBTQ0KPiBUbzogU2V1bmctSWsgTGVlDQo+IENjOiBpY25yZw0KPiBTdWJqZWN0OiBSZTogW2lj
bnJnXSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0KPiANCj4gRGVhciBTZXVuZy1JaywNCj4g
DQo+IEkgdGhpbmsgeW91IGJyaW5nIHVwIGEgdmVyeSBnb29kIHBvaW50LiBJIGFncmVlIHRoYXQg
ZGVwbG95bWVudCBhbmQNCj4gbWlncmF0aW9uIGlzc3VlcyBhcmUgdmVyeSBpbXBvcnRhbnQuIEkg
YWxzbyBhZ3JlZSB0aGF0IHRoZXkgZG9uJ3Qgc2VlbSBsaWtlIGENCj4gZ29vZCBmaXQgZm9yIGFu
eSBvZiB0aGUgY3VycmVudGx5IHByb3Bvc2VkIElDTlJHIGRvY3VtZW50cy4NCj4gDQo+IFRoZSB0
aHJlZSBkb2N1bWVudHMgbGlzdGVkIGFzIGN1cnJlbnQgd29yayBpdGVtcyBhcmUgaW4gbm8gd2F5
IHNldCBpbiBzdG9uZSwNCj4gdGhleSBzaG91bGQganVzdCBiZSBzZWVuIGFzIGEgc3RhcnRpbmcg
cG9pbnQgZm9yIG91ciB3b3JrLiBJZiB5b3Ugd291bGQgbGlrZSB0bw0KPiBwcm9wb3NlIHRoZSBS
RyB0aGF0IHdlIHNob3VsZCBzdGFydCB3b3JraW5nIG9uIGEgZGVwbG95bWVudCBkb2N1bWVudA0K
PiB5b3UgYXJlIG1vc3Qgd2VsY29tZSB0byBkbyBzbywgdGhhdCB3aWxsIG1vc3QgY2VydGFpbmx5
IGJlIGluIHNjb3BlIGZvciBvdXINCj4gZGlzY3Vzc2lvbiBpbiBBdGxhbnRhLg0KPiANCj4gQXMg
YSBnZW5lcmFsIGNvbW1lbnQgSSBhbHNvIGxpa2UgdG8gbWVudGlvbiB0aGF0IHdlIGFzIGFuIFJH
IGFyZSBub3QgYm91bmQNCj4gYnkgYWxsIHRoZSBydWxlcyB0aGF0IGFwcGx5IHRvIElFVEYgV0dz
LCBlLmcuIHdlIGFyZSBmcmVlIHRvIGRpc2N1c3MgbGF0ZQ0KPiBjb250cmlidXRpb25zIHByb2R1
Y2VkIGFmdGVyIHRoZSBJRVRGIGRyYWZ0IGRlYWRsaW5lcy4gU28gaWYgcGVvcGxlIGZpbmQgdGhl
DQo+IHRpbWUgdG8gd3JpdGUgdXAgc29tZSBtYXRlcmlhbCBmb3IgdGhlIElDTlJHIGFmdGVyIHRo
ZSBJRVRGIGRyYWZ0cyBhcmUgZG9uZQ0KPiB0aGV5IGFyZSB3ZWxjb21lIHRvIGFubm91bmNlIGl0
IHRvIHRoZSBJQ05SRyBtYWlsaW5nIGxpc3QuIElmIHRoZSBncm91cA0KPiBhZ3JlZXMgd2UgYXJl
IGZyZWUgdG8gZGlzY3VzcyBhbHNvIHN1Y2ggbWF0ZXJpYWwgYXQgb3VyIG1lZXRpbmcsDQo+IA0K
PiAgICAgIELDtnJqZQ0KPiANCj4gMTggb2t0IDIwMTIga2wuIDAzOjU2IHNrcmV2ICJTZXVuZy1J
ayBMZWUiIDxzZXVuZ2lrbGVlQGV0cmkucmUua3I+Og0KPiANCj4gPiBEZWFyIGljbnJnIGNvbGxl
YWd1ZXMsDQo+ID4NCj4gPiBSZWdhcmRpbmcgdGhlIFJHIGRvY3VtZW50cywgZG9uJ3Qgd2UgdG91
Y2ggYW55IGlzc3VlcyBvbiBJQ04NCj4gZGVwbG95bWVudHM/DQo+ID4NCj4gPiBBcyB3ZSBoYXZl
IHNlZW4gaW4gdGhlIHByZXNlbnRhdGlvbiBieSBaVEUgaW4gVmFuY291dmVyLCBJU1BzIGFyZQ0K
PiA+IGludGVyZXN0ZWQgaW4gdGhlIHNob3J0LXRlcm0gYXBwcm9hY2hlcyB0byBJQ04uDQo+ID4g
VGhvdWdoIHRoZSB0cmFkaXRpb25hbCBJQ04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04vTkROKSBo
YXZlIHByb3ZpZGVkDQo+ID4gSVNQcyBhIGxhZGRlciBvdXQgb2YgZHVtYi1waXBlcywgSVNQcyBt
YXkgaGF2ZSBkaWZmaWN1bHRpZXMgb24NCj4gPiBjbGVhbi1zbGF0ZSBhcHByb2FjaGVzIG9mIElD
Ti4NCj4gPiBJTUhPLCBiYXNlZCBvbiBvdXIgc3VydmV5cyBvbiBJU1AgUiZEIGFwcHJvYWNoZXMg
dG8gSUNOLCBLb3JlYW4gSVNQcw0KPiA+IGFyZSBpbiB0aGUgc2ltaWxhciBzaXR1YXRpb24uDQo+
ID4NCj4gPiBJbiB0aGlzIG1vdGl2YXRpb24sIEkgaGF2ZSBpbnRlcmVzdHMgaW4gSUNOIGRlcGxv
eW1lbnQgc3RyYXRlZ2llcw0KPiA+IChzdWNoIGFzIElDTiBvdmVyIElQIG9yIElDTiBvdmVyIFNE
TiBhcyBzaG9ydC10ZXJtIGFwcHJvYWNoZXMpDQo+ID4gYnV0IG5vIGlkZWEgd2hpY2ggUkcgZG9j
dW1lbnQgd291bGQgY292ZXIgdGhlIGRlcGxveW1lbnQgaXNzdWVzLCBldmVuDQo+ID4gd2hldGhl
ciBpY25yZyB3aWxsIGNvdmVyIHRoZSBkZXBsb3ltZW50IGlzc3VlIG9yIG5vdC4NCj4gPg0KPiA+
DQo+ID4NCj4gPiAyMDEyLzEwLzggQsO2cmplIE9obG1hbiA8Qm9yamUuT2hsbWFuQGVyaWNzc29u
LmNvbT46DQo+ID4+IFRoZSBuZXh0IElDTlJHIHdpbGwgYmUgaGVsZCBhdCAgSUVURiA4NSwgQXRs
YW50YSwgR2VvcmdpYSwgVVNBLA0KPiBOb3ZlbWJlcg0KPiA+PiA0LTksIDIwMTINCj4gPj4gICAg
ICAqIE1lZXRpbmcgdGltZTogV0VETkVTREFZIDEzLjAwLTE1LjQwIChwcmVsKQ0KPiA+Pg0KPiA+
PiBUaGUgbWFpbiBkaXNjdXNzaW9uIGF0IHRoZSBtZWV0aW5nIHdpbGwgYmUgdGhlIHRocmVlIGRv
Y3VtZW50cyB0aGF0IHRoZQ0KPiBSRw0KPiA+PiBoYXMgc2V0IG91dCB0byBwcm9kdWNlLg0KPiA+
Pg0KPiA+PiBJQ04gU3VydmV5IGRvY3VtZW50DQo+ID4+DQo+ID4+IEEgZG9jdW1lbnQgdGhhdCBw
cm92aWRlcyBhIHN1cnZleSBvZiBkaWZmZXJlbnQgYXBwcm9hY2hlcyBhbmQNCj4gdGVjaG5pcXVl
cw0KPiA+Pg0KPiA+PiBJQ04gUHJvYmxlbSBzdGF0ZW1lbnQNCj4gPj4NCj4gPj4gQSBkb2N1bWVu
dCB0aGF0IGRlc2NyaWJlcyB0aGUgSUNOIHByb2JsZW0gc3RhdGVtZW50LCB0aGUgbWFpbg0KPiBj
b25jZXB0cyBhbmQNCj4gPj4gcmVzZWFyY2ggY2hhbGxlbmdlcyBpbiBkZXB0aC4NCj4gPj4NCj4g
Pj4gSUNOIEJhc2VsaW5lIFNjZW5hcmlvcw0KPiA+Pg0KPiA+PiBBIGRvY3VtZW50IHRoYXQgZGVm
aW5lcyByZWZlcmVuY2UgYmFzZWxpbmUgc2NlbmFyaW9zIHRvIGVuYWJsZQ0KPiBwZXJmb3JtYW5j
ZQ0KPiA+PiBjb21wYXJpc29ucyBiZXR3ZWVuIGRpZmZlcmVudCBhcHByb2FjaGVzLg0KPiA+Pg0K
PiA+PiBQZW9wbGUgYXJlIGVuY291cmFnZWQgdG8gcHJlc2VudCB0aGVpciB2aWV3cyBvbiB3aGF0
IHRoZXkgdGhpbmsgc2hvdWxkDQo+IGJlDQo+ID4+IHRoZSBjb250ZW50cyBvZiB0aGVzZSBkb2N1
bWVudHMuIEVhcmx5IGNvbnRyaWJ1dGlvbnMgKGluIGJ1bGxldCBmb3JtIG9yIGFzDQo+ID4+IGRy
YWZ0IHRleHQpIGFyZSB3ZWxjb21lIGJvdGggb24gdGhlIG1haWxpbmcgbGlzdCBhbmQgdGhlIHdp
a2kuDQo+IFByZXNlbnRhdGlvbnMNCj4gPj4gb2YgZHJhZnQgbWF0ZXJpYWwgYXJlIHdlbGNvbWUg
YXQgdGhlIG1lZXRpbmcuDQo+ID4+DQo+ID4+IE1vc3QgbGlrZWx5IHdlIHdpbGwgYWxzbyBoYXZl
IHRpbWUgdG8gZGlzY3VzcyBvbmUgb3IgdHdvIHNwZWNpZmljIHRlY2huaWNhbA0KPiA+PiB0b3Bp
Y3MgYXQgdGhlIG1lZXRpbmcuIFByb3Bvc2FscyBmb3Igc3VjaCB0b3BpY3MgYXMgd2VsbCBhcyBw
cmVzZW50YXRpb25zDQo+ID4+IGFyZSBpbnZpdGVkLg0KPiA+Pg0KPiA+PiBBcyB3ZSBhcmUgZXhw
ZWN0ZWQgdG8gcHVibGlzaCBvdXIgYWdlbmRhIGJ5IDIwMTItMTAtMjQgKFdlZG5lc2RheSkgd2UN
Cj4gd291bGQNCj4gPj4gbGlrZSB0byBoYXZlIHlvdXIgaW5wdXQgYnkgU3VuZGF5IDIwMTItMTAt
MjEuDQo+ID4+DQo+ID4+IELDtnJqZSwgRGF2ZSAmIERpcmsNCj4gPj4NCj4gPj4NCj4gPj4gSUNO
IFJHIFdpa2k6DQo+ID4+DQo+ID4+IGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL2dyb3VwL2ly
dGYvdHJhYy93aWtpL2ljbnJnDQo+ID4+DQo+ID4+DQo+ID4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+IGljbnJnIG1haWxpbmcgbGlzdA0KPiA+
PiBpY25yZ0BpcnRmLm9yZw0KPiA+PiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2ljbnJnDQo+ID4+DQo+ID4NCj4gPg0KPiA+DQo+ID4gLS0NCj4gPiBTZXVuZy1JayBMZWUg
KOydtOyKueydtSkNCj4gPiBTdGFuZGFyZHMgUmVzZWFyY2ggQ2VudGVyLCBFVFJJDQo+ID4gVGVs
LiAgICArODItNDItODYwLTE0ODMNCj4gPiBGYXguICAgKzgyLTQyLTg2MS01NDA0DQo+ID4gRW1h
aWwuIHNldW5naWtsZWVAZXRyaS5yZS5rcg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiBpY25yZyBtYWlsaW5nIGxpc3QNCj4gaWNucmdAaXJ0Zi5v
cmcNCj4gaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pY25yZw0K

From seungiklee@gmail.com  Thu Oct 18 02:12:37 2012
Return-Path: <seungiklee@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D4021F85F3 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.677
X-Spam-Level: 
X-Spam-Status: No, score=-102.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhvotcV2KXuB for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:12:35 -0700 (PDT)
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by ietfa.amsl.com (Postfix) with ESMTP id 41DAA21F85F0 for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:12:35 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id e12so6948517lag.13 for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=v7ShH8kx+l7G8UhPnSqSrQJ++2so8ZnZTSmLqJwtzyU=; b=g6FiUUsXSdga4cOKscEQNbgYflN/PZD6A5PsTeGdWPRcUGcWZQcf3DYG/5q3XMy1ec N5Q9QCeK/tfoV02iZPi1SY6LDzfsVILnL+fvqYdsaAACZpk18Byg2a5g2xTDUk+52LOH 3oytrITOEsr6EjZzE53ri/0G2CD8Edf92nTp6H6b77FVKWNytDuh9KGBWCjXPjOSKUX8 Xaf1le96zQh8wF3CrYdzpe1zR7Jb/6ymrOPAN5q+l8Cgbm2YvAvk2+WXoLuVfQDPshxP q3WWxWSZyifLT75ajpBFxSl923vjNL1s7AXyiPir7gQzyujxqswK2MfR0VLUUkS2DZp2 vAnQ==
Received: by 10.152.105.174 with SMTP id gn14mr17806626lab.55.1350551554053; Thu, 18 Oct 2012 02:12:34 -0700 (PDT)
MIME-Version: 1.0
Sender: seungiklee@gmail.com
Received: by 10.114.68.70 with HTTP; Thu, 18 Oct 2012 02:12:13 -0700 (PDT)
In-Reply-To: <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com>
From: Seung-Ik Lee <seungiklee@etri.re.kr>
Date: Thu, 18 Oct 2012 18:12:13 +0900
X-Google-Sender-Auth: X9ILzP7CmnxMtakNs2VJFiLx7D8
Message-ID: <CAHMWmA_EzpETNCt8MiEFiciqe7pTL++egYZ-C7Ci0uoooEhOxQ@mail.gmail.com>
To: =?UTF-8?Q?B=C3=B6rje_Ohlman?= <borje.ohlman@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 09:12:37 -0000

Yes, I think that firstly we need to specify such deployment and
migration issues in the PS document as Dirk proposed.
But I'm not quite sure that the relevant ICN use cases in different
deployment approaches could be included in the scenario document as
B=C3=B6rje pointed out.
Then we may need a separate document for ICN deployment and migration issue=
s.


2012/10/18 B=C3=B6rje Ohlman <borje.ohlman@ericsson.com>:
> Dear Seung-Ik,
>
> I think you bring up a very good point. I agree that deployment and migra=
tion issues are very important. I also agree that they don't seem like a go=
od fit for any of the currently proposed ICNRG documents.
>
> The three documents listed as current work items are in no way set in sto=
ne, they should just be seen as a starting point for our work. If you would=
 like to propose the RG that we should start working on a deployment docume=
nt you are most welcome to do so, that will most certainly be in scope for =
our discussion in Atlanta.
>
> As a general comment I also like to mention that we as an RG are not boun=
d by all the rules that apply to IETF WGs, e.g. we are free to discuss late=
 contributions produced after the IETF draft deadlines. So if people find t=
he time to write up some material for the ICNRG after the IETF drafts are d=
one they are welcome to announce it to the ICNRG mailing list. If the group=
 agrees we are free to discuss also such material at our meeting,
>
>      B=C3=B6rje
>
> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>
>> Dear icnrg colleagues,
>>
>> Regarding the RG documents, don't we touch any issues on ICN deployments=
?
>>
>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>> interested in the short-term approaches to ICN.
>> Though the traditional ICN approaches (such as CCN/NDN) have provided
>> ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
>> clean-slate approaches of ICN.
>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
>> are in the similar situation.
>>
>> In this motivation, I have interests in ICN deployment strategies
>> (such as ICN over IP or ICN over SDN as short-term approaches)
>> but no idea which RG document would cover the deployment issues, even
>> whether icnrg will cover the deployment issue or not.
>>
>>
>>
>> 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA, Novembe=
r
>>> 4-9, 2012
>>>      * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>
>>> The main discussion at the meeting will be the three documents that the=
 RG
>>> has set out to produce.
>>>
>>> ICN Survey document
>>>
>>> A document that provides a survey of different approaches and technique=
s
>>>
>>> ICN Problem statement
>>>
>>> A document that describes the ICN problem statement, the main concepts =
and
>>> research challenges in depth.
>>>
>>> ICN Baseline Scenarios
>>>
>>> A document that defines reference baseline scenarios to enable performa=
nce
>>> comparisons between different approaches.
>>>
>>> People are encouraged to present their views on what they think should =
be
>>> the contents of these documents. Early contributions (in bullet form or=
 as
>>> draft text) are welcome both on the mailing list and the wiki. Presenta=
tions
>>> of draft material are welcome at the meeting.
>>>
>>> Most likely we will also have time to discuss one or two specific techn=
ical
>>> topics at the meeting. Proposals for such topics as well as presentatio=
ns
>>> are invited.
>>>
>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we w=
ould
>>> like to have your input by Sunday 2012-10-21.
>>>
>>> B=C3=B6rje, Dave & Dirk
>>>
>>>
>>> ICN RG Wiki:
>>>
>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>
>>>
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>
>>
>>
>>
>> --
>> Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
>> Standards Research Center, ETRI
>> Tel.    +82-42-860-1483
>> Fax.   +82-42-861-5404
>> Email. seungiklee@etri.re.kr
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg



--=20
Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
Standards Research Center, ETRI
Tel.    +82-42-860-1483
Fax.   +82-42-861-5404
Email. seungiklee@etri.re.kr

From seungiklee@gmail.com  Thu Oct 18 02:39:33 2012
Return-Path: <seungiklee@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DF721F8522 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAsDRTEmfTQz for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:39:32 -0700 (PDT)
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by ietfa.amsl.com (Postfix) with ESMTP id 193AC21F8501 for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:39:31 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id e12so6968304lag.13 for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:39:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=2iNeqHNXCoEpjy/v1LUOtW9Kd8fgDJj2dTZpX/gDupU=; b=TS+9oSgEPoUisnmhIRJ/GmxT4jSMcxr5ab3lk9gWg9zvOl51tf4uWez178EQkDLUq0 OHPBF5pMkZ/HADvPxDjNpEJL8o46+8KkSIa9NKbug8iEEmlCgnlq1R2nkw17OY7amRoo FspniFvOd/dUK1VHuti4E9UXxAkCRym1dTS+lTkIOr4K79WoiEnSVPpC3Xn8t766Oypx StcifNbqSBR2ICYYZvbhFEwqqI57FDiUudzFU63Kmx/ku31SO/txVM1S6M1H6D99CqJE xQZDCK46p6MxOlUDTELfhHmLzEkVksCB3XqnX1thEuQCnJ33jlV3F7JX54gX1lFau6nh 4f1A==
Received: by 10.112.40.42 with SMTP id u10mr4861296lbk.124.1350553170724; Thu, 18 Oct 2012 02:39:30 -0700 (PDT)
MIME-Version: 1.0
Sender: seungiklee@gmail.com
Received: by 10.114.68.70 with HTTP; Thu, 18 Oct 2012 02:39:10 -0700 (PDT)
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
From: Seung-Ik Lee <seungiklee@etri.re.kr>
Date: Thu, 18 Oct 2012 18:39:10 +0900
X-Google-Sender-Auth: POEMt0fvE01DlKGc7XOvZZR0yGg
Message-ID: <CAHMWmA-iLxCmyV-w2XTQ35PatqS6qn05jP9S9-L-ub6d9UdMmw@mail.gmail.com>
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: =?UTF-8?B?5Lu75amn?= <renjing@uestc.edu.cn>, =?UTF-8?Q?B=C3=B6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 09:39:33 -0000

Thank you for the useful information.

I think that the integrated deployment option is not that different
from the clean-slate approach of ICN.

IMHO, overlay approach is most short-term-feasible approach and some
ISPs have deployed their testbeds or some are in use in different
ways.
But what I usually heard about the overlay approach is "what is
different from CDN?". That kind of questions needs to be addressed.

SDN-based approach is quite adorable but, yes, it is in an early stage
yet and we need interworking protocols as done in CDNI.

I think that we can have such problems specified in PS document.


2012/10/18 Will Liu (Shucheng) <liushucheng@huawei.com>:
> Hi,
>
> My group are also interested in ICN deployment and have done some survey =
on this matter. The discussion on ICN deployment is a great topic which ISP=
s will definitely be interested in. Here are our 2-cents.
>
> The evolvement of ICN may take the following three implementations: integ=
rated with IP, over IP and over SDN. These strategies all can help the ISP =
shift from the traditional IP to ICN. The only question is which one is the=
 best choice for large scale deployment?
>
> Integrated with IP strategy extends the existing IP protocol (IP option) =
to support ICN. The updated IP router, called content router, will deal wit=
h such special packets. However, many routers with no support of such exten=
sion may directly drop the packets with an unknown IP option.
>
> ICN over IP strategy uses an overlay approach. Content-related operation =
will be performed on the high layer and Content-related information will be=
 sent through a tunnel. Due to the limited knowledge of physical topology a=
nd unnecessary packet encapsulation/disconsolation, the efficiency may be l=
imited.
>
> ICN over SDN strategy exploits SDN controller to perform content-related =
operation. However, SDN itself is an ongoing approach and is typically used=
 in a local domain. The performance in a large scale deployment is unknown.
>
> Will
>
>> -----Original Message-----
>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf O=
f
>> B?rje Ohlman
>> Sent: Thursday, October 18, 2012 10:55 AM
>> To: Seung-Ik Lee
>> Cc: icnrg
>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>
>> Dear Seung-Ik,
>>
>> I think you bring up a very good point. I agree that deployment and
>> migration issues are very important. I also agree that they don't seem l=
ike a
>> good fit for any of the currently proposed ICNRG documents.
>>
>> The three documents listed as current work items are in no way set in st=
one,
>> they should just be seen as a starting point for our work. If you would =
like to
>> propose the RG that we should start working on a deployment document
>> you are most welcome to do so, that will most certainly be in scope for =
our
>> discussion in Atlanta.
>>
>> As a general comment I also like to mention that we as an RG are not bou=
nd
>> by all the rules that apply to IETF WGs, e.g. we are free to discuss lat=
e
>> contributions produced after the IETF draft deadlines. So if people find=
 the
>> time to write up some material for the ICNRG after the IETF drafts are d=
one
>> they are welcome to announce it to the ICNRG mailing list. If the group
>> agrees we are free to discuss also such material at our meeting,
>>
>>      B=C3=B6rje
>>
>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>
>> > Dear icnrg colleagues,
>> >
>> > Regarding the RG documents, don't we touch any issues on ICN
>> deployments?
>> >
>> > As we have seen in the presentation by ZTE in Vancouver, ISPs are
>> > interested in the short-term approaches to ICN.
>> > Though the traditional ICN approaches (such as CCN/NDN) have provided
>> > ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
>> > clean-slate approaches of ICN.
>> > IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
>> > are in the similar situation.
>> >
>> > In this motivation, I have interests in ICN deployment strategies
>> > (such as ICN over IP or ICN over SDN as short-term approaches)
>> > but no idea which RG document would cover the deployment issues, even
>> > whether icnrg will cover the deployment issue or not.
>> >
>> >
>> >
>> > 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>> >> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>> November
>> >> 4-9, 2012
>> >>      * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>> >>
>> >> The main discussion at the meeting will be the three documents that t=
he
>> RG
>> >> has set out to produce.
>> >>
>> >> ICN Survey document
>> >>
>> >> A document that provides a survey of different approaches and
>> techniques
>> >>
>> >> ICN Problem statement
>> >>
>> >> A document that describes the ICN problem statement, the main
>> concepts and
>> >> research challenges in depth.
>> >>
>> >> ICN Baseline Scenarios
>> >>
>> >> A document that defines reference baseline scenarios to enable
>> performance
>> >> comparisons between different approaches.
>> >>
>> >> People are encouraged to present their views on what they think shoul=
d
>> be
>> >> the contents of these documents. Early contributions (in bullet form =
or as
>> >> draft text) are welcome both on the mailing list and the wiki.
>> Presentations
>> >> of draft material are welcome at the meeting.
>> >>
>> >> Most likely we will also have time to discuss one or two specific tec=
hnical
>> >> topics at the meeting. Proposals for such topics as well as presentat=
ions
>> >> are invited.
>> >>
>> >> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we
>> would
>> >> like to have your input by Sunday 2012-10-21.
>> >>
>> >> B=C3=B6rje, Dave & Dirk
>> >>
>> >>
>> >> ICN RG Wiki:
>> >>
>> >> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>> >>
>> >>
>> >> _______________________________________________
>> >> icnrg mailing list
>> >> icnrg@irtf.org
>> >> https://www.irtf.org/mailman/listinfo/icnrg
>> >>
>> >
>> >
>> >
>> > --
>> > Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
>> > Standards Research Center, ETRI
>> > Tel.    +82-42-860-1483
>> > Fax.   +82-42-861-5404
>> > Email. seungiklee@etri.re.kr
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg



--=20
Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
Standards Research Center, ETRI
Tel.    +82-42-860-1483
Fax.   +82-42-861-5404
Email. seungiklee@etri.re.kr

From stephen.farrell@cs.tcd.ie  Thu Oct 18 02:45:25 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93BCD21F85A4 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M0hzMPeaHDHG for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 02:45:25 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEBD21F84EF for <icnrg@irtf.org>; Thu, 18 Oct 2012 02:45:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 8EC75171487; Thu, 18 Oct 2012 10:45:21 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1350553521; bh=OvxHn8uO9ZWMdv EZBHGK1yK1YzrdD44KAR9mo5xn3/A=; b=U1uOwdKHXhNYfhAkxXGPTMuwu1c6bP HA1PM+EbgIVXCB4sLcBm1qN7Ikbj60q62Ey3dav+K+JHn47pFx5qOb9+rJgvNiM3 RnW+3AZ8EKU/foexFw8IlULiF4pYW+b6ylAPIduV7Nnb4U3YRrA3KhAzOhT4JLRw Fupvkl06DCUnfuSAI+kmxkoGsqC/OSfXj9jIMr27PCb/kR3EIOFKXLFiphEI1dV0 zZ9uQWL2Oa9rcJAGDr2+HSRhB6eZ+QwTl3xAfCR0lyLn0UHY8bGcg2nVXchAQUW4 xQtdiXu0PV1/wEatvqKpDytE7NWAJE88R7+OPxhK5jb5EDBvGUaEur9g==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id EdCmuvSFoyBd; Thu, 18 Oct 2012 10:45:21 +0100 (IST)
Received: from [IPv6:2001:770:10:203:a452:172f:3f09:ead2] (unknown [IPv6:2001:770:10:203:a452:172f:3f09:ead2]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 4CB59171479; Thu, 18 Oct 2012 10:45:18 +0100 (IST)
Message-ID: <507FCFAE.6020403@cs.tcd.ie>
Date: Thu, 18 Oct 2012 10:45:18 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
In-Reply-To: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 09:45:25 -0000

Hi Börje,

On 10/08/2012 09:00 AM, Börje Ohlman wrote:
> ICN Problem statement
> A document that describes the ICN problem statement, the main concepts and research challenges in depth.

Just on a terminology thing, which might be nothing or
might save significant confusion later. (And sorry if
this is a late/repeat comment, I don't recall if this
was discussed or not.)

The term problem statement seems wrong to me here.

In IETF WG's a <foo> problem statement draft is often
used to try make sure everyone's trying to solve the
same problem. (That may or may not be a good or bad
approach, but its sometimes done.)

Here, you seem to want to set out concepts and research
challenges, which seems to me like its a different
beast.

For example, there's nothing to stop folks participating
in ICNRG from working on entirely different problems
so discussion of "the" problem statement may well get
in the way and confuse people into thinking that we
must all work on the same thing and argue that folks
who're working on something different are wrong to
do that.

Bottom line: I'd suggest renaming this document to
"ICN concepts and research challenges" rather than
"ICN problem statement."

Cheers,
S.


From dt355@hermes.cam.ac.uk  Thu Oct 18 04:14:31 2012
Return-Path: <dt355@hermes.cam.ac.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA5A21F852B for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 04:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBEP6ul1N6IA for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 04:14:29 -0700 (PDT)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id F042921F8523 for <icnrg@irtf.org>; Thu, 18 Oct 2012 04:14:28 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from c0166.aw.cl.cam.ac.uk ([128.232.100.166]:52950) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:dt355) (TLSv1:AES128-SHA:128) id 1TOo3Q-0006Gq-Rs (Exim 4.72) (return-path <dt355@hermes.cam.ac.uk>); Thu, 18 Oct 2012 12:14:20 +0100
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=utf-8
From: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
In-Reply-To: <CAHMWmA-iLxCmyV-w2XTQ35PatqS6qn05jP9S9-L-ub6d9UdMmw@mail.gmail.com>
Date: Thu, 18 Oct 2012 12:14:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AACD8E5-84EC-4211-8D77-E5E9EC57A282@cl.cam.ac.uk>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CAHMWmA-iLxCmyV-w2XTQ35PatqS6qn05jP9S9-L-ub6d9UdMmw@mail.gmail.com>
To: Seung-Ik Lee <seungiklee@etri.re.kr>
X-Mailer: Apple Mail (2.1085)
Sender: Dirk Trossen <dt355@hermes.cam.ac.uk>
Cc: =?utf-8?B?5Lu75amn?= <renjing@uestc.edu.cn>, =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, "Will Liu \(Shucheng\)" <liushucheng@huawei.com>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 11:14:31 -0000

The PSIRP project (pre-decessor to the current EU PURSUIT project) has =
done some incentive and deployment analysis, which looked at the =
adoption of 'native' vs 'overlaid' deployments, driven by needs of =
industries demanding these solutions (and these industries are NOT ISPs =
since they merely fulfil a need).=20

It might be helpful for some of the discussion although the modelling =
part might be harder to digest at places ;-)

The document is available at =
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf

Best,

Dirk
On 18 Oct 2012, at 10:39, Seung-Ik Lee wrote:

> Thank you for the useful information.
>=20
> I think that the integrated deployment option is not that different
> from the clean-slate approach of ICN.
>=20
> IMHO, overlay approach is most short-term-feasible approach and some
> ISPs have deployed their testbeds or some are in use in different
> ways.
> But what I usually heard about the overlay approach is "what is
> different from CDN?". That kind of questions needs to be addressed.
>=20
> SDN-based approach is quite adorable but, yes, it is in an early stage
> yet and we need interworking protocols as done in CDNI.
>=20
> I think that we can have such problems specified in PS document.
>=20
>=20
> 2012/10/18 Will Liu (Shucheng) <liushucheng@huawei.com>:
>> Hi,
>>=20
>> My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic =
which ISPs will definitely be interested in. Here are our 2-cents.
>>=20
>> The evolvement of ICN may take the following three implementations: =
integrated with IP, over IP and over SDN. These strategies all can help =
the ISP shift from the traditional IP to ICN. The only question is which =
one is the best choice for large scale deployment?
>>=20
>> Integrated with IP strategy extends the existing IP protocol (IP =
option) to support ICN. The updated IP router, called content router, =
will deal with such special packets. However, many routers with no =
support of such extension may directly drop the packets with an unknown =
IP option.
>>=20
>> ICN over IP strategy uses an overlay approach. Content-related =
operation will be performed on the high layer and Content-related =
information will be sent through a tunnel. Due to the limited knowledge =
of physical topology and unnecessary packet =
encapsulation/disconsolation, the efficiency may be limited.
>>=20
>> ICN over SDN strategy exploits SDN controller to perform =
content-related operation. However, SDN itself is an ongoing approach =
and is typically used in a local domain. The performance in a large =
scale deployment is unknown.
>>=20
>> Will
>>=20
>>> -----Original Message-----
>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf Of
>>> B?rje Ohlman
>>> Sent: Thursday, October 18, 2012 10:55 AM
>>> To: Seung-Ik Lee
>>> Cc: icnrg
>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>=20
>>> Dear Seung-Ik,
>>>=20
>>> I think you bring up a very good point. I agree that deployment and
>>> migration issues are very important. I also agree that they don't =
seem like a
>>> good fit for any of the currently proposed ICNRG documents.
>>>=20
>>> The three documents listed as current work items are in no way set =
in stone,
>>> they should just be seen as a starting point for our work. If you =
would like to
>>> propose the RG that we should start working on a deployment document
>>> you are most welcome to do so, that will most certainly be in scope =
for our
>>> discussion in Atlanta.
>>>=20
>>> As a general comment I also like to mention that we as an RG are not =
bound
>>> by all the rules that apply to IETF WGs, e.g. we are free to discuss =
late
>>> contributions produced after the IETF draft deadlines. So if people =
find the
>>> time to write up some material for the ICNRG after the IETF drafts =
are done
>>> they are welcome to announce it to the ICNRG mailing list. If the =
group
>>> agrees we are free to discuss also such material at our meeting,
>>>=20
>>>     B=C3=B6rje
>>>=20
>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>>=20
>>>> Dear icnrg colleagues,
>>>>=20
>>>> Regarding the RG documents, don't we touch any issues on ICN
>>> deployments?
>>>>=20
>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>>> interested in the short-term approaches to ICN.
>>>> Though the traditional ICN approaches (such as CCN/NDN) have =
provided
>>>> ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
>>>> clean-slate approaches of ICN.
>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean =
ISPs
>>>> are in the similar situation.
>>>>=20
>>>> In this motivation, I have interests in ICN deployment strategies
>>>> (such as ICN over IP or ICN over SDN as short-term approaches)
>>>> but no idea which RG document would cover the deployment issues, =
even
>>>> whether icnrg will cover the deployment issue or not.
>>>>=20
>>>>=20
>>>>=20
>>>> 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>> November
>>>>> 4-9, 2012
>>>>>     * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>=20
>>>>> The main discussion at the meeting will be the three documents =
that the
>>> RG
>>>>> has set out to produce.
>>>>>=20
>>>>> ICN Survey document
>>>>>=20
>>>>> A document that provides a survey of different approaches and
>>> techniques
>>>>>=20
>>>>> ICN Problem statement
>>>>>=20
>>>>> A document that describes the ICN problem statement, the main
>>> concepts and
>>>>> research challenges in depth.
>>>>>=20
>>>>> ICN Baseline Scenarios
>>>>>=20
>>>>> A document that defines reference baseline scenarios to enable
>>> performance
>>>>> comparisons between different approaches.
>>>>>=20
>>>>> People are encouraged to present their views on what they think =
should
>>> be
>>>>> the contents of these documents. Early contributions (in bullet =
form or as
>>>>> draft text) are welcome both on the mailing list and the wiki.
>>> Presentations
>>>>> of draft material are welcome at the meeting.
>>>>>=20
>>>>> Most likely we will also have time to discuss one or two specific =
technical
>>>>> topics at the meeting. Proposals for such topics as well as =
presentations
>>>>> are invited.
>>>>>=20
>>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday) =
we
>>> would
>>>>> like to have your input by Sunday 2012-10-21.
>>>>>=20
>>>>> B=C3=B6rje, Dave & Dirk
>>>>>=20
>>>>>=20
>>>>> ICN RG Wiki:
>>>>>=20
>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> icnrg mailing list
>>>>> icnrg@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
>>>> Standards Research Center, ETRI
>>>> Tel.    +82-42-860-1483
>>>> Fax.   +82-42-861-5404
>>>> Email. seungiklee@etri.re.kr
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
>=20
>=20
> --=20
> Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
> Standards Research Center, ETRI
> Tel.    +82-42-860-1483
> Fax.   +82-42-861-5404
> Email. seungiklee@etri.re.kr
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From liushucheng@huawei.com  Thu Oct 18 05:06:53 2012
Return-Path: <liushucheng@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB7321F86C1 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 05:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.374
X-Spam-Level: 
X-Spam-Status: No, score=-3.374 tagged_above=-999 required=5 tests=[AWL=-0.775, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbsYdjnQxtbV for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 05:06:52 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id 16DB021F86BD for <icnrg@irtf.org>; Thu, 18 Oct 2012 05:06:51 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AQU11315; Thu, 18 Oct 2012 20:06:48 +0800 (CST)
Received: from SZXEML430-HUB.china.huawei.com (10.72.61.38) by szxeml207-edg.china.huawei.com (172.24.2.56) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 18 Oct 2012 20:06:42 +0800
Received: from SZXEML546-MBS.china.huawei.com ([169.254.4.97]) by szxeml430-hub.china.huawei.com ([10.72.61.38]) with mapi id 14.01.0323.003; Thu, 18 Oct 2012 20:06:41 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: "borje.ohlman@ericsson.com" <borje.ohlman@ericsson.com>, "kutscher@neclab.eu" <kutscher@neclab.eu>, "oran@cisco.com" <oran@cisco.com>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: Can we ask for a time slot?
Thread-Index: AQHNrSkIJoQ7YQgmrE2zI8cqrU0xdg==
Date: Thu, 18 Oct 2012 12:06:40 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B98E245@szxeml546-mbs.china.huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "jingren@cityu.edu.hk" <jingren@cityu.edu.hk>, "jianwang@cityu.edu.hk" <jianwang@cityu.edu.hk>, "feitang@cityu.edu.hk" <feitang@cityu.edu.hk>
Subject: [icnrg] Can we ask for a time slot?
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 12:06:53 -0000

Hi all,

We'd like to ask for a time slot to discuss the following submitted new dra=
ft, if we could. Thanks.

Regards,
Will


> -----Original Message-----
> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of
> Will Liu (Shucheng)
> Sent: Monday, October 15, 2012 7:48 PM
> To: icnrg@irtf.org
> Cc: jingren@cityu.edu.hk; jianwang@cityu.edu.hk; feitang@cityu.edu.hk
> Subject: [icnrg] FW: New Version Notification for
> draft-ren-icn-content-retrieval-00.txt
>=20
> Hello,
>=20
> We have submitted a new draft discussing about content retrieval in ICN.
> Here, we discussed basic requirements on the basis of previous literature=
s,
> the fundamental functionalities required to satisfy the foregoing
> requirements, and the implementation status of such functionalities in
> various Information-Centric Network architectures.
>=20
> Your comments are highly appreciated.
>=20
> Regards,
> Shucheng LIU (Will)
>=20
>=20
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, October 15, 2012 7:26 PM
> To: Will Liu (Shucheng)
> Cc: jingren@cityu.edu.hk; jianwang@cityu.edu.hk; feitang@cityu.edu.hk
> Subject: New Version Notification for draft-ren-icn-content-retrieval-00.=
txt
>=20
>=20
> A new version of I-D, draft-ren-icn-content-retrieval-00.txt
> has been successfully submitted by Will Liu and posted to the
> IETF repository.
>=20
> Filename:	 draft-ren-icn-content-retrieval
> Revision:	 00
> Title:		 On the Content Retrieval In Information-Centric Network
> Creation date:	 2012-10-15
> WG ID:		 Individual Submission
> Number of pages: 11
> URL:
> http://www.ietf.org/internet-drafts/draft-ren-icn-content-retrieval-00.tx=
t
> Status:
> http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval
> Htmlized:
> http://tools.ietf.org/html/draft-ren-icn-content-retrieval-00
>=20
>=20
> Abstract:
>    Information-Centric Network(ICN), as an emerging network
>    architecture, focus on delivering content more efficiently.  This
>    brief paper discusses some issues about content retrieval in the
>    Information-Centric Network.  It first lists a set of basic
>    requirements on the basis of previous literatures.  Then, it tries to
>    identify the fundamental functionalities required to satisfy the
>    foregoing requirements.  Last, it summarizes the implementation
>    status of such functionalities in various Information-Centric Network
>    architectures.
>=20
>=20
>=20
> The IETF Secretariat
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From damien.saucez@gmail.com  Thu Oct 18 05:35:05 2012
Return-Path: <damien.saucez@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B56621F8732 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 05:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CnbYwpmEKJ2C for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 05:35:03 -0700 (PDT)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1E49C21F8746 for <icnrg@irtf.org>; Thu, 18 Oct 2012 05:35:02 -0700 (PDT)
Received: by mail-bk0-f54.google.com with SMTP id jf20so3969944bkc.13 for <icnrg@irtf.org>; Thu, 18 Oct 2012 05:35:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=3MgDMg7oEJwWvvkDufdNFADHgf/axbZOaaEZpxjWT3o=; b=AJMPi8HTJnmxFab0JNrFIk/IcKlxBUTL/EXFUKiBl7OcYB/EPF0H2uCorySTFVu9/r P5kPhshyimpHIR0WNeYD3wLxkTeKznO0hh6qUAaOQ57qhTfelMam+PLe/5PsX1OVKPA3 BGK2rjmn9JK8kXKs8d4FBXm8OpP7lareoHqC2StezLjb+b83ih+kUF78tnAQK4glArTs oB194odYQn4FdQImubjbL27hpICU8r2zY9h9hgOGQ3r41KdFjqosLnxhRozwLT/uT2kk vdDwJnB5NMpzCOTGHiYZMe/+RvNCg4a/C+ptrlzQ01yW/0IF6n7eqMgx5GQ6PLguCyJl z3YA==
Received: by 10.204.150.220 with SMTP id z28mr6365625bkv.125.1350563701967; Thu, 18 Oct 2012 05:35:01 -0700 (PDT)
Received: from faucon.inria.fr (faucon.inria.fr. [138.96.201.73]) by mx.google.com with ESMTPS id z22sm14738339bkw.2.2012.10.18.05.34.59 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 05:35:00 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <4AACD8E5-84EC-4211-8D77-E5E9EC57A282@cl.cam.ac.uk>
Date: Thu, 18 Oct 2012 14:34:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <57F8CD4A-F050-4068-AA43-2A687ACDE1DF@gmail.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CAHMWmA-iLxCmyV-w2XTQ35PatqS6qn05jP9S9-L-ub6d9UdMmw@mail.gmail.com> <4AACD8E5-84EC-4211-8D77-E5E9EC57A282@cl.cam.ac.uk>
To: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
X-Mailer: Apple Mail (2.1499)
Cc: Chadi Barakat <Chadi.Barakat@inria.fr>, =?utf-8?Q?B=C3=B6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, Thierry Turletti <Thierry.Turletti@inria.fr>, "Will Liu \(Shucheng\)" <liushucheng@huawei.com>, Seung-Ik Lee <seungiklee@etri.re.kr>, =?utf-8?B?5Lu75amn?= <renjing@uestc.edu.cn>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 12:35:05 -0000

On 18 Oct 2012, at 13:14, Dirk Trossen <dirk.trossen@cl.cam.ac.uk> =
wrote:

> The PSIRP project (pre-decessor to the current EU PURSUIT project) has =
done some incentive and deployment analysis, which looked at the =
adoption of 'native' vs 'overlaid' deployments, driven by needs of =
industries demanding these solutions (and these industries are NOT ISPs =
since they merely fulfil a need).=20
>=20
> It might be helpful for some of the discussion although the modelling =
part might be harder to digest at places ;-)
>=20
> The document is available at =
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf
>=20

thank you for the link, this model is interesting.

Sec. 4 of http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf can be
read as a mean to deal with ICN islands (here running CCN, but it
can be generalised), inter-connected with IP. The idea is to form
an overlay and the technology we had in mind, even though we
do not name it in the report, is LISP.

Regards,

Damien Saucez

> Best,
>=20
> Dirk
> On 18 Oct 2012, at 10:39, Seung-Ik Lee wrote:
>=20
>> Thank you for the useful information.
>>=20
>> I think that the integrated deployment option is not that different
>> from the clean-slate approach of ICN.
>>=20
>> IMHO, overlay approach is most short-term-feasible approach and some
>> ISPs have deployed their testbeds or some are in use in different
>> ways.
>> But what I usually heard about the overlay approach is "what is
>> different from CDN?". That kind of questions needs to be addressed.
>>=20
>> SDN-based approach is quite adorable but, yes, it is in an early =
stage
>> yet and we need interworking protocols as done in CDNI.
>>=20
>> I think that we can have such problems specified in PS document.
>>=20
>>=20
>> 2012/10/18 Will Liu (Shucheng) <liushucheng@huawei.com>:
>>> Hi,
>>>=20
>>> My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic =
which ISPs will definitely be interested in. Here are our 2-cents.
>>>=20
>>> The evolvement of ICN may take the following three implementations: =
integrated with IP, over IP and over SDN. These strategies all can help =
the ISP shift from the traditional IP to ICN. The only question is which =
one is the best choice for large scale deployment?
>>>=20
>>> Integrated with IP strategy extends the existing IP protocol (IP =
option) to support ICN. The updated IP router, called content router, =
will deal with such special packets. However, many routers with no =
support of such extension may directly drop the packets with an unknown =
IP option.
>>>=20
>>> ICN over IP strategy uses an overlay approach. Content-related =
operation will be performed on the high layer and Content-related =
information will be sent through a tunnel. Due to the limited knowledge =
of physical topology and unnecessary packet =
encapsulation/disconsolation, the efficiency may be limited.
>>>=20
>>> ICN over SDN strategy exploits SDN controller to perform =
content-related operation. However, SDN itself is an ongoing approach =
and is typically used in a local domain. The performance in a large =
scale deployment is unknown.
>>>=20
>>> Will
>>>=20
>>>> -----Original Message-----
>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf Of
>>>> B?rje Ohlman
>>>> Sent: Thursday, October 18, 2012 10:55 AM
>>>> To: Seung-Ik Lee
>>>> Cc: icnrg
>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>=20
>>>> Dear Seung-Ik,
>>>>=20
>>>> I think you bring up a very good point. I agree that deployment and
>>>> migration issues are very important. I also agree that they don't =
seem like a
>>>> good fit for any of the currently proposed ICNRG documents.
>>>>=20
>>>> The three documents listed as current work items are in no way set =
in stone,
>>>> they should just be seen as a starting point for our work. If you =
would like to
>>>> propose the RG that we should start working on a deployment =
document
>>>> you are most welcome to do so, that will most certainly be in scope =
for our
>>>> discussion in Atlanta.
>>>>=20
>>>> As a general comment I also like to mention that we as an RG are =
not bound
>>>> by all the rules that apply to IETF WGs, e.g. we are free to =
discuss late
>>>> contributions produced after the IETF draft deadlines. So if people =
find the
>>>> time to write up some material for the ICNRG after the IETF drafts =
are done
>>>> they are welcome to announce it to the ICNRG mailing list. If the =
group
>>>> agrees we are free to discuss also such material at our meeting,
>>>>=20
>>>>    B=C3=B6rje
>>>>=20
>>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>>>=20
>>>>> Dear icnrg colleagues,
>>>>>=20
>>>>> Regarding the RG documents, don't we touch any issues on ICN
>>>> deployments?
>>>>>=20
>>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>>>> interested in the short-term approaches to ICN.
>>>>> Though the traditional ICN approaches (such as CCN/NDN) have =
provided
>>>>> ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
>>>>> clean-slate approaches of ICN.
>>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean =
ISPs
>>>>> are in the similar situation.
>>>>>=20
>>>>> In this motivation, I have interests in ICN deployment strategies
>>>>> (such as ICN over IP or ICN over SDN as short-term approaches)
>>>>> but no idea which RG document would cover the deployment issues, =
even
>>>>> whether icnrg will cover the deployment issue or not.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>>> November
>>>>>> 4-9, 2012
>>>>>>    * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>>=20
>>>>>> The main discussion at the meeting will be the three documents =
that the
>>>> RG
>>>>>> has set out to produce.
>>>>>>=20
>>>>>> ICN Survey document
>>>>>>=20
>>>>>> A document that provides a survey of different approaches and
>>>> techniques
>>>>>>=20
>>>>>> ICN Problem statement
>>>>>>=20
>>>>>> A document that describes the ICN problem statement, the main
>>>> concepts and
>>>>>> research challenges in depth.
>>>>>>=20
>>>>>> ICN Baseline Scenarios
>>>>>>=20
>>>>>> A document that defines reference baseline scenarios to enable
>>>> performance
>>>>>> comparisons between different approaches.
>>>>>>=20
>>>>>> People are encouraged to present their views on what they think =
should
>>>> be
>>>>>> the contents of these documents. Early contributions (in bullet =
form or as
>>>>>> draft text) are welcome both on the mailing list and the wiki.
>>>> Presentations
>>>>>> of draft material are welcome at the meeting.
>>>>>>=20
>>>>>> Most likely we will also have time to discuss one or two specific =
technical
>>>>>> topics at the meeting. Proposals for such topics as well as =
presentations
>>>>>> are invited.
>>>>>>=20
>>>>>> As we are expected to publish our agenda by 2012-10-24 =
(Wednesday) we
>>>> would
>>>>>> like to have your input by Sunday 2012-10-21.
>>>>>>=20
>>>>>> B=C3=B6rje, Dave & Dirk
>>>>>>=20
>>>>>>=20
>>>>>> ICN RG Wiki:
>>>>>>=20
>>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> icnrg mailing list
>>>>>> icnrg@irtf.org
>>>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
>>>>> Standards Research Center, ETRI
>>>>> Tel.    +82-42-860-1483
>>>>> Fax.   +82-42-861-5404
>>>>> Email. seungiklee@etri.re.kr
>>>> _______________________________________________
>>>> icnrg mailing list
>>>> icnrg@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>>=20
>>=20
>>=20
>> --=20
>> Seung-Ik Lee (=EC=9D=B4=EC=8A=B9=EC=9D=B5)
>> Standards Research Center, ETRI
>> Tel.    +82-42-860-1483
>> Fax.   +82-42-861-5404
>> Email. seungiklee@etri.re.kr
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From borje.ohlman@ericsson.com  Thu Oct 18 06:53:02 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8C721F8816 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 06:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNGBCdbYG7Gz for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 06:53:02 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5157021F8815 for <icnrg@irtf.org>; Thu, 18 Oct 2012 06:53:01 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-44-508009bbe793
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id CA.C7.11467.BB900805; Thu, 18 Oct 2012 15:52:59 +0200 (CEST)
Received: from dhcp-147-214-183-183.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.93) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 18 Oct 2012 15:52:59 +0200
Content-Type: multipart/signed; boundary="Apple-Mail=_BD8EB150-5FDB-43B2-AA90-650F109A236C"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
In-Reply-To: <507FCFAE.6020403@cs.tcd.ie>
Date: Thu, 18 Oct 2012 15:53:14 +0200
Message-ID: <E9677582-A292-4F01-BEFB-F6A234E2E775@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <507FCFAE.6020403@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1498)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUyM+Jvre5uzoYAg85eK4uds3cyWUzfe43d gcljbfdVNo/JGw+zBTBFcdmkpOZklqUW6dslcGWsWTybrWCyVcX3xXUNjH9Nuxg5OSQETCTe 7T3BBGGLSVy4t56ti5GLQ0jgFKPEm54tTBDOMUaJlgX7WEEcZoEpjBJPVq1hBWnhFdCTWL/i LhuILSwQIzFh5QEwm03AUeJxy3qwGk4BTYn9a3+wg9gsAqoS6/+fYe5i5AAaJCVxu7UCYoy9 xO0dPWDlQkBjnh84xAhiiwjoS+zdfI4d4jpZiXsvfrNB1KhJzPj4iGkCo8AsZCfNQnISiM0s oC2xbOFrZghbT+Jl0zt2CNtU4vXRj4wQtrXEjF8HoeoVJaZ0P2RfwMi+ilE4NzEzJ73cUC+1 KDO5uDg/T684dRMjMOgPbvmtu4Px1DmRQ4zSHCxK4rxcSfv9hQTSE0tSs1NTC1KL4otKc1KL DzEycXBKNTBOvst9kGOyuuWB/kDLaMnNMV8myW/r6nvopLBcX/5ZqPHpuN8L1v87f3g399qa bxp2DIfMVp09PP3p/MtTLm2+86noOqvVbMOX90LDZUWUZDOYOjkyrp9gcQ0q38b7Szz6tbiC BsPT8kdfTa3X+CVIacsvTGmu1leuT5fh8kz6Xr7mht+Z2AtKLMUZiYZazEXFiQDYgqr/SAIA AA==
Cc: icnrg <icnrg@irtf.org>
Subject: [icnrg] Title of Problem Statement document (was: Re: Announcing ICNRG @ IETF 85)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 13:53:02 -0000

--Apple-Mail=_BD8EB150-5FDB-43B2-AA90-650F109A236C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Stephen,

I think you have a good point. I never liked the Problem Statement title =
anyway, but never  managed to formulate why I didn't like it. I propose =
we change the title as you propose.

Other views?
Dirk and Dave, what do you think?

	B=F6rje

On 18 okt 2012, at 11:45, Stephen Farrell <stephen.farrell@cs.tcd.ie>
 wrote:

>=20
> Hi B=F6rje,
>=20
> On 10/08/2012 09:00 AM, B=F6rje Ohlman wrote:
>> ICN Problem statement
>> A document that describes the ICN problem statement, the main =
concepts and research challenges in depth.
>=20
> Just on a terminology thing, which might be nothing or
> might save significant confusion later. (And sorry if
> this is a late/repeat comment, I don't recall if this
> was discussed or not.)
>=20
> The term problem statement seems wrong to me here.
>=20
> In IETF WG's a <foo> problem statement draft is often
> used to try make sure everyone's trying to solve the
> same problem. (That may or may not be a good or bad
> approach, but its sometimes done.)
>=20
> Here, you seem to want to set out concepts and research
> challenges, which seems to me like its a different
> beast.
>=20
> For example, there's nothing to stop folks participating
> in ICNRG from working on entirely different problems
> so discussion of "the" problem statement may well get
> in the way and confuse people into thinking that we
> must all work on the same thing and argue that folks
> who're working on something different are wrong to
> do that.
>=20
> Bottom line: I'd suggest renaming this document to
> "ICN concepts and research challenges" rather than
> "ICN problem statement."
>=20
> Cheers,
> S.
>=20


--Apple-Mail=_BD8EB150-5FDB-43B2-AA90-650F109A236C
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM6jCCBCww
ggMUoAMCAQICEE+J7kJLlbt5Cwozb3PkitEwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMTA2MTAxMTE1
NTNaFw0xNDA2MTAxMTE1NTBaMGYxETAPBgNVBAoMCEVyaWNzc29uMRUwEwYDVQQDDAxCb3JqZSBP
aGxtYW4xEDAOBgNVBAUTB2VyYWJvamUxKDAmBgkqhkiG9w0BCQEWGWJvcmplLm9obG1hbkBlcmlj
c3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAIMxmMrirYNu/BYirDVZKIkHIN3r
RMpA0nXsSWLJqWP3y2DLzNy3UVIxHeKg4j+ImGIRHxbK3VT+309C1E3LVkrWWasgbNusiD+wBLwu
hP2oU9+ZNSQRR27izpm+hS6JdiDvAyT7WNXEWLevdFm0pGFuDiWR50tyPoHFtc8PAJSzAgMBAAGj
ggGFMIIBgTCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0LnRlbGlhLmNv
bS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVzdC50ZWxpYS5j
b20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nzb24/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAkBgNVHREEHTAbgRlib3JqZS5vaGxtYW5A
ZXJpY3Nzb24uY29tMEYGA1UdIAQ/MD0wOwYGKoVwawEBMDEwLwYIKwYBBQUHAgEWI2h0dHA6Ly93
d3cuZXJpY3Nzb24uY29tL2xlZ2FsLnNodG1sMB0GA1UdDgQWBBRsbk1c9Soh8MAC6OU8J+UH9NnV
gDAfBgNVHSMEGDAWgBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZI
hvcNAQEFBQADggEBAFJdGY8Vo/HyTbwJpLKWE2ed4YAbqM8AQFZaEaVRofyRuCvTv+S2JMFmoNr9
9UkCqiwlNX5r2l0UeZTxAkHqblHfJ3PxMHe0KyS8fzg4Cuxf2Y/aDdp0TSWCPbiruaLZyiJcZQZV
Ay74AAGDPpNy4d3l/1qrOiXMRKhv79kLfo5XGCUWLCt2xhUlfuKGpOoPnSNyWZb+pd8vwS+mU2x6
8XfXPWFEjICtVvn5cBklBgRPAnQnHvL70Bj7x3RZerN95+hcG9W0+2yb3bh+kN9BGPIbqhDwuIZO
fewQqfWq+7oSZUSjJ9LDeqNNeVC8jRo5aN3s73gTByaQjeYlrzj75LwwggRFMIIDLaADAgECAhAT
yer/3iatqdykyiOBg0fjMA0GCSqGSIb3DQEBBQUAMEQxGjAYBgNVBAoMEVRlbGlhU29uZXJhIEdy
b3VwMSYwJAYDVQQDDB1UZWxpYVNvbmVyYSBQdWJsaWMgUm9vdCBDQSB2MTAeFw0wNjEwMDYxMDAw
NTNaFw0xNjEwMDIwNTA0MTdaMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC2EHfk
NR7rh8Q8jRhZRD8wsbjzxTuVtscq/p6glZzSeEGBXtRwAqmr6jS8FBiKiBMh79ay537m/SwXO3UK
UR45f3YIIp9DjThSd+p2xhG3x4yyc9gczlr8JfOEnPhcdPSKw1P0mUlhUn4ak7t009/Ye/W6x3UZ
HTwVIAWILIhSq4hyNE4z+RvOtvB9uwQ86lKcxi0mFoLev7acLjh+ZXHzXx1jHAmF0ZaG79CpbvJc
RuWplqgJ6qx+hAjsmCU0Wx07GkyGTh8vUMP9Hlz7oyk+7VOccUiNknXHias1GwM9qBUUOj8e/xsn
aTP0ZfqmKBj3Grh1C9WknlSWagxanCBdAgMBAAGjggE8MIIBODASBgNVHRMBAf8ECDAGAQH/AgEA
MEYGA1UdIAQ/MD0wOwYHKoVwIwIBATAwMC4GCCsGAQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWEuY29tMIGJBgNVHR8EgYEwfzB9oHugeYZ3bGRhcDovL2xkYXAudHJ1c3QudGVs
aWEuY29tL2NuPVRlbGlhU29uZXJhJTIwUHVibGljJTIwUm9vdCUyMENBJTIwdjEsbz1UZWxpYVNv
bmVyYSUyMEdyb3VwP2F1dGhvcml0eXJldm9jYXRpb25saXN0P2Jhc2UwDgYDVR0PAQH/BAQDAgEG
MB0GA1UdDgQWBBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAfBgNVHSMEGDAWgBRF2/CPuBpioagjG2OI
OKPb4Bpi8TANBgkqhkiG9w0BAQUFAAOCAQEAdgBKKkM/jN0WvWpZKZ/2J8IVyL+rT44VL0rjbNND
YXdE/V4ZSFN2uuQmgf1Ckqp2shNLe0NEKt6/sfxit4p/5opPIvzytv6vB7rc2BUs8+jac7aaNiRu
wBCjiT1Wnnm454OOZurzQu0SH81PbBtiwUf4XsEvLOnRRZ+9MO/ecVMCQVmeuzsyCl6yFVbx0zmK
W1gPjBEigF8BYZ1Tjazk1pVcKzFIuB24j1qTpPsUG4HoQhIu5rt3F7GlNV6t5DF7ojbgu1SqKG/J
hTvaPUU/nZYqw9rkV8Dabwrt27reisobtPp78tolxio3ZcZVk7HQ8rpV2M/jmAjGfZRVkczCDzCC
BG0wggNVoAMCAQICEQCcsIwEmsuXInhjYrYbhlo9MA0GCSqGSIb3DQEBBQUAMDoxGTAXBgNVBAoT
EFJTQSBTZWN1cml0eSBJbmMxHTAbBgNVBAsTFFJTQSBTZWN1cml0eSAyMDQ4IFYzMB4XDTA2MTAz
MTIwNDIyN1oXDTE2MTEwMTE1NDIyNVowRDEaMBgGA1UECgwRVGVsaWFTb25lcmEgR3JvdXAxJjAk
BgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAyk8QA2qQgKt5qZV+EeIDbflmXuUChp2lREEsmO5SAiheQ7lXVjzCxw484cOS
Mw3fOtGWcf9Fa4Rgdw5j+EgyFgiqNj8b2OTXJHQVj1qf09rmkHTgMIKh6TdKXtV+/43pefVrFmFy
hoP/NVrYe92Sv4HhOxs/T749S1OjeGISzIKKMSpwkvmYweYnFgIPkHdUKUIReOh9Ym6ei7AVg6ee
jD6YPBeV+suzBlXCmC3Zyzj7POLsUVvarNZAaKc0AY+rOUslYfAPo+ZYgwY4IV2KcP/qWhhHahz3
khWMWSniWrZoxCi2JcXGVkSn+N+ir0APYwYTBJsrTDWxonEdZkR+rQIDAQABo4IBYjCCAV4wHwYD
VR0jBBgwFoAUB8NRMKSq6UWuNST6/yQsM9CxnYwwHQYDVR0OBBYEFEXb8I+4GmKhqCMbY4g4o9vg
GmLxMBIGA1UdEwEB/wQIMAYBAf8CAQQwgYUGA1UdIAR+MHwwPQYJKoZIhvcNBQYBMDAwLgYIKwYB
BQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wOwYHKoVwIwIBATAwMC4G
CCsGAQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWEuY29tMHAGA1UdHwRpMGcw
ZaBjoGGGX2h0dHA6Ly93d3cucnNhc2VjdXJpdHkuY29tL3Byb2R1Y3RzL2tlb24vcmVwb3NpdG9y
eS9jZXJ0aWZpY2F0ZV9zdGF0dXMvUlNBX1NlY3VyaXR5XzIwNDhfdjMuQ1JMMA4GA1UdDwEB/wQE
AwIBBjANBgkqhkiG9w0BAQUFAAOCAQEABF6aLNgpyJu//O9srUqxB1mYL4TlBJFJtuT1n/15FpKO
NU2i/byEtUugHVgoTalpp2Ikuxn2iIgzPbNQ+iu4YnVgQzpuOmzXTN2cITMgwn5AyUoHidMPu2Jo
7wobu4Fqg2QrG7WeYANYsQk3Q57mQeuyRkjxluq+93KK2gz/HYjqYkKLjLzOmyrkzwR/9aaC3HLF
MbCoK0NtyQvS1gkW/HGB5GY1xR9SuOE7CJeS53tqE9CSN6cHQNr+ozuKfzix57T/p6Y8D23nTD1G
ZA2ApHdy0sY/HNyU8bQPEpTwrSBxNYYeucYoYNSUSJYkqYa6q/ZG38B3XlcT3TiORrQ2DzGCAhIw
ggIOAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2
aWR1YWwgQ0EwMQIQT4nuQkuVu3kLCjNvc+SK0TAJBgUrDgMCGgUAoIIBGzAYBgkqhkiG9w0BCQMx
CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjEwMTgxMzUzMTVaMCMGCSqGSIb3DQEJBDEW
BBS5PPRALhSrZz8xAi59y3tVEiXOIDBcBgkrBgEEAYI3EAQxTzBNMDkxETAPBgNVBAoMCEVyaWNz
c29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE+J7kJLlbt5Cwozb3Pk
itEwXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmlj
c3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE+J7kJLlbt5Cwozb3PkitEwDQYJKoZIhvcNAQEBBQAE
gYAGb1/bl6U3y6XsKx0KtyQ5VfcjaToxZDW6DdQMC6tbKP62uOvmDFqBgZkcHx3yiRvyPBnV4BHk
ELITuVZUcCIN/CT1fYDmLD1SJ1BxfwANkHYjoIL6iyse5AUjRH+6pihHsWHtU1T+I6AkFlBHJMcX
4opBYnGcujShMe5lAcGfAgAAAAAAAA==

--Apple-Mail=_BD8EB150-5FDB-43B2-AA90-650F109A236C--

From daveoran@orandom.net  Thu Oct 18 10:35:16 2012
Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 503F521F8470 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 10:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1XVXhqondJY for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 10:35:15 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2001:470:d:21b:3c00::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA86F21F846F for <icnrg@irtf.org>; Thu, 18 Oct 2012 10:35:15 -0700 (PDT)
Received: from [10.154.212.34] (128-107-239-234.cisco.com [128.107.239.234]) (authenticated bits=0) by spark.crystalorb.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9IHZ4ov023276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Oct 2012 10:35:05 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: David R Oran <daveoran@orandom.net>
In-Reply-To: <E9677582-A292-4F01-BEFB-F6A234E2E775@ericsson.com>
Date: Thu, 18 Oct 2012 10:34:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4EA6312-22C8-4E83-B247-5F25754A2487@orandom.net>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <507FCFAE.6020403@cs.tcd.ie> <E9677582-A292-4F01-BEFB-F6A234E2E775@ericsson.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
X-Mailer: Apple Mail (2.1499)
Cc: icnrg <icnrg@irtf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [icnrg] Title of Problem Statement document (was: Re: Announcing ICNRG @ IETF 85)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 17:35:16 -0000

On Oct 18, 2012, at 6:53 AM, B=F6rje Ohlman <borje.ohlman@ericsson.com> =
wrote:

> Stephen,
>=20
> I think you have a good point. I never liked the Problem Statement =
title anyway, but never  managed to formulate why I didn't like it. I =
propose we change the title as you propose.
>=20
> Other views?
> Dirk and Dave, what do you think?
>=20
I agree with Stephen's assessment. Problem statement is the wrong =
terminology. I also like the proposed title.

> 	B=F6rje
>=20
> On 18 okt 2012, at 11:45, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
>=20
>>=20
>> Hi B=F6rje,
>>=20
>> On 10/08/2012 09:00 AM, B=F6rje Ohlman wrote:
>>> ICN Problem statement
>>> A document that describes the ICN problem statement, the main =
concepts and research challenges in depth.
>>=20
>> Just on a terminology thing, which might be nothing or
>> might save significant confusion later. (And sorry if
>> this is a late/repeat comment, I don't recall if this
>> was discussed or not.)
>>=20
>> The term problem statement seems wrong to me here.
>>=20
>> In IETF WG's a <foo> problem statement draft is often
>> used to try make sure everyone's trying to solve the
>> same problem. (That may or may not be a good or bad
>> approach, but its sometimes done.)
>>=20
>> Here, you seem to want to set out concepts and research
>> challenges, which seems to me like its a different
>> beast.
>>=20
>> For example, there's nothing to stop folks participating
>> in ICNRG from working on entirely different problems
>> so discussion of "the" problem statement may well get
>> in the way and confuse people into thinking that we
>> must all work on the same thing and argue that folks
>> who're working on something different are wrong to
>> do that.
>>=20
>> Bottom line: I'd suggest renaming this document to
>> "ICN concepts and research challenges" rather than
>> "ICN problem statement."
>>=20
>> Cheers,
>> S.
>>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From brian_field@cable.comcast.com  Thu Oct 18 11:54:48 2012
Return-Path: <brian_field@cable.comcast.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 878CE21F84C9 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 11:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.997
X-Spam-Level: 
X-Spam-Status: No, score=-99.997 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ek5u7LNBv9s1 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 11:54:47 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 5B54721F84C5 for <icnrg@irtf.org>; Thu, 18 Oct 2012 11:54:47 -0700 (PDT)
Received: from ([147.191.109.19]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.30931116; Thu, 18 Oct 2012 14:47:20 -0400
Received: from COPDCEXMB07.cable.comcast.com ([169.254.5.242]) by COPDCEXHUB03.cable.comcast.com ([fe80::48b0:651:4100:4cfd%17]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 12:54:27 -0600
From: "Field, Brian" <Brian_Field@cable.comcast.com>
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>, =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman@ericsson.com>, Seung-Ik Lee <seungiklee@etri.re.kr>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNwFWKayz875o0yFihD6GGIvaJe/KvwAgAA9bNA=
Date: Thu, 18 Oct 2012 18:54:26 +0000
Message-ID: <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.191.109.77]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: ?? <renjing@uestc.edu.cn>, icnrg <icnrg@irtf.org>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 18:54:48 -0000

RG9lcyBhbnlvbmUgKGJlc2lkZSBtZSkgdGhpbmsgdGhhdCBhIENETiBlZmZlY3RpdmVseSBpcyBh
bHJlYWR5IGRvaW5nICJJQ04iIGJ1dCB0dW5uZWxlZCBvdmVyIGFuIEhUVFAgaW5mcmFzdHJ1Y3R1
cmUgKHZpYSBIVFRQL1RDUC9JUCkuICAgSSB0aGluayBvZiBDRE4gYW5kIG5hdGl2ZSBJQ04gKHdo
ZXJlIHRoZSByb3V0ZXIgaXMgY2FjaGluZyBhbmQgZm9yd2FyZGluZyBhdCB0aGUgSUNOIGxldmVs
KSBuZWFybHkgaWRlbnRpY2FsIGZvcndhcmRpbmcgcGFyYWRpZ21zIGp1c3Qgb3BlcmF0aW5nIGF0
IGRpZmZlcmVudCBsZXZlbHMgaW4gdGhlIHN0YWNrLiAgDQoNClRoZXJlJ3Mgd29yayBpbiBzdGFu
ZGFyZGl6aW5nIHRoZSBpbnRyYS1DRE4gIGFuZCBpbnRlci1DRE4gY29udHJvbCBwbGFuIChpbiBD
RE4tSSBhbmQgZWxzZXdoZXJlKS4gIElNTywgaXQgd291bGQgYmUgdXNlZnVsIGlmIHdlIGhhZCB0
aGUgc2FtZSBjb250cm9sIHByb3RvY29sIG9wZXJhdGluZyBpbiBib3RoIHRoZSBDRE4gYW5kIElD
TiBkb21haW5zIGFuZCB0aGUgInRyYW5zaXRpb24iIHdhcyBqdXN0IGNoYW5naW5nIHRoZSBsYXll
ciBhdCB3aGljaCBmb3J3YXJkaW5nIG9jY3VycmVkLg0KDQpCcmlhbg0KDQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpY25yZy1ib3VuY2VzQGlydGYub3JnIFttYWlsdG86aWNu
cmctYm91bmNlc0BpcnRmLm9yZ10gT24gQmVoYWxmIE9mIFdpbGwgTGl1IChTaHVjaGVuZykNClNl
bnQ6IFRodXJzZGF5LCBPY3RvYmVyIDE4LCAyMDEyIDM6MDggQU0NClRvOiBCw7ZyamUgT2hsbWFu
OyBTZXVuZy1JayBMZWUNCkNjOiDku7vlqac7IGljbnJnOyBKaWFucGluZyBXYW5nDQpTdWJqZWN0
OiBSZTogW2ljbnJnXSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0KDQpIaSwNCg0KTXkgZ3Jv
dXAgYXJlIGFsc28gaW50ZXJlc3RlZCBpbiBJQ04gZGVwbG95bWVudCBhbmQgaGF2ZSBkb25lIHNv
bWUgc3VydmV5IG9uIHRoaXMgbWF0dGVyLiBUaGUgZGlzY3Vzc2lvbiBvbiBJQ04gZGVwbG95bWVu
dCBpcyBhIGdyZWF0IHRvcGljIHdoaWNoIElTUHMgd2lsbCBkZWZpbml0ZWx5IGJlIGludGVyZXN0
ZWQgaW4uIEhlcmUgYXJlIG91ciAyLWNlbnRzLiANCg0KVGhlIGV2b2x2ZW1lbnQgb2YgSUNOIG1h
eSB0YWtlIHRoZSBmb2xsb3dpbmcgdGhyZWUgaW1wbGVtZW50YXRpb25zOiBpbnRlZ3JhdGVkIHdp
dGggSVAsIG92ZXIgSVAgYW5kIG92ZXIgU0ROLiBUaGVzZSBzdHJhdGVnaWVzIGFsbCBjYW4gaGVs
cCB0aGUgSVNQIHNoaWZ0IGZyb20gdGhlIHRyYWRpdGlvbmFsIElQIHRvIElDTi4gVGhlIG9ubHkg
cXVlc3Rpb24gaXMgd2hpY2ggb25lIGlzIHRoZSBiZXN0IGNob2ljZSBmb3IgbGFyZ2Ugc2NhbGUg
ZGVwbG95bWVudD8gDQoNCkludGVncmF0ZWQgd2l0aCBJUCBzdHJhdGVneSBleHRlbmRzIHRoZSBl
eGlzdGluZyBJUCBwcm90b2NvbCAoSVAgb3B0aW9uKSB0byBzdXBwb3J0IElDTi4gVGhlIHVwZGF0
ZWQgSVAgcm91dGVyLCBjYWxsZWQgY29udGVudCByb3V0ZXIsIHdpbGwgZGVhbCB3aXRoIHN1Y2gg
c3BlY2lhbCBwYWNrZXRzLiBIb3dldmVyLCBtYW55IHJvdXRlcnMgd2l0aCBubyBzdXBwb3J0IG9m
IHN1Y2ggZXh0ZW5zaW9uIG1heSBkaXJlY3RseSBkcm9wIHRoZSBwYWNrZXRzIHdpdGggYW4gdW5r
bm93biBJUCBvcHRpb24uIA0KDQpJQ04gb3ZlciBJUCBzdHJhdGVneSB1c2VzIGFuIG92ZXJsYXkg
YXBwcm9hY2guIENvbnRlbnQtcmVsYXRlZCBvcGVyYXRpb24gd2lsbCBiZSBwZXJmb3JtZWQgb24g
dGhlIGhpZ2ggbGF5ZXIgYW5kIENvbnRlbnQtcmVsYXRlZCBpbmZvcm1hdGlvbiB3aWxsIGJlIHNl
bnQgdGhyb3VnaCBhIHR1bm5lbC4gRHVlIHRvIHRoZSBsaW1pdGVkIGtub3dsZWRnZSBvZiBwaHlz
aWNhbCB0b3BvbG9neSBhbmQgdW5uZWNlc3NhcnkgcGFja2V0IGVuY2Fwc3VsYXRpb24vZGlzY29u
c29sYXRpb24sIHRoZSBlZmZpY2llbmN5IG1heSBiZSBsaW1pdGVkLiANCg0KSUNOIG92ZXIgU0RO
IHN0cmF0ZWd5IGV4cGxvaXRzIFNETiBjb250cm9sbGVyIHRvIHBlcmZvcm0gY29udGVudC1yZWxh
dGVkIG9wZXJhdGlvbi4gSG93ZXZlciwgU0ROIGl0c2VsZiBpcyBhbiBvbmdvaW5nIGFwcHJvYWNo
IGFuZCBpcyB0eXBpY2FsbHkgdXNlZCBpbiBhIGxvY2FsIGRvbWFpbi4gVGhlIHBlcmZvcm1hbmNl
IGluIGEgbGFyZ2Ugc2NhbGUgZGVwbG95bWVudCBpcyB1bmtub3duLiANCg0KV2lsbA0KDQo+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGljbnJnLWJvdW5jZXNAaXJ0Zi5vcmcg
W21haWx0bzppY25yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhhbGYgDQo+IE9mIEI/cmplIE9o
bG1hbg0KPiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOCwgMjAxMiAxMDo1NSBBTQ0KPiBUbzog
U2V1bmctSWsgTGVlDQo+IENjOiBpY25yZw0KPiBTdWJqZWN0OiBSZTogW2ljbnJnXSBBbm5vdW5j
aW5nIElDTlJHIEAgSUVURiA4NQ0KPiANCj4gRGVhciBTZXVuZy1JaywNCj4gDQo+IEkgdGhpbmsg
eW91IGJyaW5nIHVwIGEgdmVyeSBnb29kIHBvaW50LiBJIGFncmVlIHRoYXQgZGVwbG95bWVudCBh
bmQgDQo+IG1pZ3JhdGlvbiBpc3N1ZXMgYXJlIHZlcnkgaW1wb3J0YW50LiBJIGFsc28gYWdyZWUg
dGhhdCB0aGV5IGRvbid0IHNlZW0gDQo+IGxpa2UgYSBnb29kIGZpdCBmb3IgYW55IG9mIHRoZSBj
dXJyZW50bHkgcHJvcG9zZWQgSUNOUkcgZG9jdW1lbnRzLg0KPiANCj4gVGhlIHRocmVlIGRvY3Vt
ZW50cyBsaXN0ZWQgYXMgY3VycmVudCB3b3JrIGl0ZW1zIGFyZSBpbiBubyB3YXkgc2V0IGluIA0K
PiBzdG9uZSwgdGhleSBzaG91bGQganVzdCBiZSBzZWVuIGFzIGEgc3RhcnRpbmcgcG9pbnQgZm9y
IG91ciB3b3JrLiBJZiANCj4geW91IHdvdWxkIGxpa2UgdG8gcHJvcG9zZSB0aGUgUkcgdGhhdCB3
ZSBzaG91bGQgc3RhcnQgd29ya2luZyBvbiBhIA0KPiBkZXBsb3ltZW50IGRvY3VtZW50IHlvdSBh
cmUgbW9zdCB3ZWxjb21lIHRvIGRvIHNvLCB0aGF0IHdpbGwgbW9zdCANCj4gY2VydGFpbmx5IGJl
IGluIHNjb3BlIGZvciBvdXIgZGlzY3Vzc2lvbiBpbiBBdGxhbnRhLg0KPiANCj4gQXMgYSBnZW5l
cmFsIGNvbW1lbnQgSSBhbHNvIGxpa2UgdG8gbWVudGlvbiB0aGF0IHdlIGFzIGFuIFJHIGFyZSBu
b3QgDQo+IGJvdW5kIGJ5IGFsbCB0aGUgcnVsZXMgdGhhdCBhcHBseSB0byBJRVRGIFdHcywgZS5n
LiB3ZSBhcmUgZnJlZSB0byANCj4gZGlzY3VzcyBsYXRlIGNvbnRyaWJ1dGlvbnMgcHJvZHVjZWQg
YWZ0ZXIgdGhlIElFVEYgZHJhZnQgZGVhZGxpbmVzLiBTbyANCj4gaWYgcGVvcGxlIGZpbmQgdGhl
IHRpbWUgdG8gd3JpdGUgdXAgc29tZSBtYXRlcmlhbCBmb3IgdGhlIElDTlJHIGFmdGVyIA0KPiB0
aGUgSUVURiBkcmFmdHMgYXJlIGRvbmUgdGhleSBhcmUgd2VsY29tZSB0byBhbm5vdW5jZSBpdCB0
byB0aGUgSUNOUkcgDQo+IG1haWxpbmcgbGlzdC4gSWYgdGhlIGdyb3VwIGFncmVlcyB3ZSBhcmUg
ZnJlZSB0byBkaXNjdXNzIGFsc28gc3VjaCANCj4gbWF0ZXJpYWwgYXQgb3VyIG1lZXRpbmcsDQo+
IA0KPiAgICAgIELDtnJqZQ0KPiANCj4gMTggb2t0IDIwMTIga2wuIDAzOjU2IHNrcmV2ICJTZXVu
Zy1JayBMZWUiIDxzZXVuZ2lrbGVlQGV0cmkucmUua3I+Og0KPiANCj4gPiBEZWFyIGljbnJnIGNv
bGxlYWd1ZXMsDQo+ID4NCj4gPiBSZWdhcmRpbmcgdGhlIFJHIGRvY3VtZW50cywgZG9uJ3Qgd2Ug
dG91Y2ggYW55IGlzc3VlcyBvbiBJQ04NCj4gZGVwbG95bWVudHM/DQo+ID4NCj4gPiBBcyB3ZSBo
YXZlIHNlZW4gaW4gdGhlIHByZXNlbnRhdGlvbiBieSBaVEUgaW4gVmFuY291dmVyLCBJU1BzIGFy
ZSANCj4gPiBpbnRlcmVzdGVkIGluIHRoZSBzaG9ydC10ZXJtIGFwcHJvYWNoZXMgdG8gSUNOLg0K
PiA+IFRob3VnaCB0aGUgdHJhZGl0aW9uYWwgSUNOIGFwcHJvYWNoZXMgKHN1Y2ggYXMgQ0NOL05E
TikgaGF2ZSANCj4gPiBwcm92aWRlZCBJU1BzIGEgbGFkZGVyIG91dCBvZiBkdW1iLXBpcGVzLCBJ
U1BzIG1heSBoYXZlIGRpZmZpY3VsdGllcyANCj4gPiBvbiBjbGVhbi1zbGF0ZSBhcHByb2FjaGVz
IG9mIElDTi4NCj4gPiBJTUhPLCBiYXNlZCBvbiBvdXIgc3VydmV5cyBvbiBJU1AgUiZEIGFwcHJv
YWNoZXMgdG8gSUNOLCBLb3JlYW4gSVNQcyANCj4gPiBhcmUgaW4gdGhlIHNpbWlsYXIgc2l0dWF0
aW9uLg0KPiA+DQo+ID4gSW4gdGhpcyBtb3RpdmF0aW9uLCBJIGhhdmUgaW50ZXJlc3RzIGluIElD
TiBkZXBsb3ltZW50IHN0cmF0ZWdpZXMgDQo+ID4gKHN1Y2ggYXMgSUNOIG92ZXIgSVAgb3IgSUNO
IG92ZXIgU0ROIGFzIHNob3J0LXRlcm0gYXBwcm9hY2hlcykgYnV0IA0KPiA+IG5vIGlkZWEgd2hp
Y2ggUkcgZG9jdW1lbnQgd291bGQgY292ZXIgdGhlIGRlcGxveW1lbnQgaXNzdWVzLCBldmVuIA0K
PiA+IHdoZXRoZXIgaWNucmcgd2lsbCBjb3ZlciB0aGUgZGVwbG95bWVudCBpc3N1ZSBvciBub3Qu
DQo+ID4NCj4gPg0KPiA+DQo+ID4gMjAxMi8xMC84IELDtnJqZSBPaGxtYW4gPEJvcmplLk9obG1h
bkBlcmljc3Nvbi5jb20+Og0KPiA+PiBUaGUgbmV4dCBJQ05SRyB3aWxsIGJlIGhlbGQgYXQgIElF
VEYgODUsIEF0bGFudGEsIEdlb3JnaWEsIFVTQSwNCj4gTm92ZW1iZXINCj4gPj4gNC05LCAyMDEy
DQo+ID4+ICAgICAgKiBNZWV0aW5nIHRpbWU6IFdFRE5FU0RBWSAxMy4wMC0xNS40MCAocHJlbCkN
Cj4gPj4NCj4gPj4gVGhlIG1haW4gZGlzY3Vzc2lvbiBhdCB0aGUgbWVldGluZyB3aWxsIGJlIHRo
ZSB0aHJlZSBkb2N1bWVudHMgdGhhdCANCj4gPj4gdGhlDQo+IFJHDQo+ID4+IGhhcyBzZXQgb3V0
IHRvIHByb2R1Y2UuDQo+ID4+DQo+ID4+IElDTiBTdXJ2ZXkgZG9jdW1lbnQNCj4gPj4NCj4gPj4g
QSBkb2N1bWVudCB0aGF0IHByb3ZpZGVzIGEgc3VydmV5IG9mIGRpZmZlcmVudCBhcHByb2FjaGVz
IGFuZA0KPiB0ZWNobmlxdWVzDQo+ID4+DQo+ID4+IElDTiBQcm9ibGVtIHN0YXRlbWVudA0KPiA+
Pg0KPiA+PiBBIGRvY3VtZW50IHRoYXQgZGVzY3JpYmVzIHRoZSBJQ04gcHJvYmxlbSBzdGF0ZW1l
bnQsIHRoZSBtYWluDQo+IGNvbmNlcHRzIGFuZA0KPiA+PiByZXNlYXJjaCBjaGFsbGVuZ2VzIGlu
IGRlcHRoLg0KPiA+Pg0KPiA+PiBJQ04gQmFzZWxpbmUgU2NlbmFyaW9zDQo+ID4+DQo+ID4+IEEg
ZG9jdW1lbnQgdGhhdCBkZWZpbmVzIHJlZmVyZW5jZSBiYXNlbGluZSBzY2VuYXJpb3MgdG8gZW5h
YmxlDQo+IHBlcmZvcm1hbmNlDQo+ID4+IGNvbXBhcmlzb25zIGJldHdlZW4gZGlmZmVyZW50IGFw
cHJvYWNoZXMuDQo+ID4+DQo+ID4+IFBlb3BsZSBhcmUgZW5jb3VyYWdlZCB0byBwcmVzZW50IHRo
ZWlyIHZpZXdzIG9uIHdoYXQgdGhleSB0aGluayANCj4gPj4gc2hvdWxkDQo+IGJlDQo+ID4+IHRo
ZSBjb250ZW50cyBvZiB0aGVzZSBkb2N1bWVudHMuIEVhcmx5IGNvbnRyaWJ1dGlvbnMgKGluIGJ1
bGxldCANCj4gPj4gZm9ybSBvciBhcyBkcmFmdCB0ZXh0KSBhcmUgd2VsY29tZSBib3RoIG9uIHRo
ZSBtYWlsaW5nIGxpc3QgYW5kIHRoZSB3aWtpLg0KPiBQcmVzZW50YXRpb25zDQo+ID4+IG9mIGRy
YWZ0IG1hdGVyaWFsIGFyZSB3ZWxjb21lIGF0IHRoZSBtZWV0aW5nLg0KPiA+Pg0KPiA+PiBNb3N0
IGxpa2VseSB3ZSB3aWxsIGFsc28gaGF2ZSB0aW1lIHRvIGRpc2N1c3Mgb25lIG9yIHR3byBzcGVj
aWZpYyANCj4gPj4gdGVjaG5pY2FsIHRvcGljcyBhdCB0aGUgbWVldGluZy4gUHJvcG9zYWxzIGZv
ciBzdWNoIHRvcGljcyBhcyB3ZWxsIA0KPiA+PiBhcyBwcmVzZW50YXRpb25zIGFyZSBpbnZpdGVk
Lg0KPiA+Pg0KPiA+PiBBcyB3ZSBhcmUgZXhwZWN0ZWQgdG8gcHVibGlzaCBvdXIgYWdlbmRhIGJ5
IDIwMTItMTAtMjQgKFdlZG5lc2RheSkgDQo+ID4+IHdlDQo+IHdvdWxkDQo+ID4+IGxpa2UgdG8g
aGF2ZSB5b3VyIGlucHV0IGJ5IFN1bmRheSAyMDEyLTEwLTIxLg0KPiA+Pg0KPiA+PiBCw7ZyamUs
IERhdmUgJiBEaXJrDQo+ID4+DQo+ID4+DQo+ID4+IElDTiBSRyBXaWtpOg0KPiA+Pg0KPiA+PiBo
dHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9ncm91cC9pcnRmL3RyYWMvd2lraS9pY25yZw0KPiA+
Pg0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiA+PiBpY25yZyBtYWlsaW5nIGxpc3QNCj4gPj4gaWNucmdAaXJ0Zi5vcmcNCj4gPj4g
aHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pY25yZw0KPiA+Pg0KPiA+DQo+
ID4NCj4gPg0KPiA+IC0tDQo+ID4gU2V1bmctSWsgTGVlICjsnbTsirnsnbUpDQo+ID4gU3RhbmRh
cmRzIFJlc2VhcmNoIENlbnRlciwgRVRSSQ0KPiA+IFRlbC4gICAgKzgyLTQyLTg2MC0xNDgzDQo+
ID4gRmF4LiAgICs4Mi00Mi04NjEtNTQwNA0KPiA+IEVtYWlsLiBzZXVuZ2lrbGVlQGV0cmkucmUu
a3INCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
aWNucmcgbWFpbGluZyBsaXN0DQo+IGljbnJnQGlydGYub3JnDQo+IGh0dHBzOi8vd3d3LmlydGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaWNucmcNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQppY25yZyBtYWlsaW5nIGxpc3QNCmljbnJnQGlydGYub3JnDQpo
dHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQo=

From fred@cisco.com  Thu Oct 18 12:19:33 2012
Return-Path: <fred@cisco.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F13F721F81FF for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 12:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.095
X-Spam-Level: 
X-Spam-Status: No, score=-109.095 tagged_above=-999 required=5 tests=[AWL=-0.796, BAYES_00=-2.599, MANGLED_SHOP=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upWWAjeWcL42 for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 12:19:33 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3793521F8493 for <icnrg@irtf.org>; Thu, 18 Oct 2012 12:19:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=712; q=dns/txt; s=iport; t=1350587973; x=1351797573; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ejrR7YEl5BtAVgZ8GNS7TvtJS37DSfZwmVKu0DieXdo=; b=YEjw4oRkIf4bOeo5pu/YXKZk66l4iwyFIqqvdNbiDfzLUeKTX6HM2TnC 5jjmufc7qecErUYWRMhogt+KpaE7lHWQuYl9HuWW/9OSbtjZ2d6y3NV5w VcZAGnRrwKUi+A6UKbQwP5OEOSdtYwJTRrqFq1h4bq8IZy8spwzwB+fMl o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAApWgFCtJV2b/2dsb2JhbABFhhK5SHmBCIIgAQEBAwESARARMxIFCwIBCBoCBiACAgIwFRACBA4NGodcBpx6jSGTEoEhijeFMDJgA6Q0gWuCb4IX
X-IronPort-AV: E=Sophos;i="4.80,608,1344211200"; d="scan'208";a="132937436"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 18 Oct 2012 19:19:13 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q9IJJDfU019928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Oct 2012 19:19:13 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 14:19:12 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNwD+tZSppm8kkiqrYUd++MQ3pe/GjkAgACqxYA=
Date: Thu, 18 Oct 2012 19:19:12 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B17E639@xmb-rcd-x09.cisco.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.246.110]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19284.002
x-tm-as-result: No--25.910500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-ID: <1C8EC1E503BF7644A2248F4EFA075843@cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Seung-Ik Lee <seungiklee@etri.re.kr>, =?utf-8?B?5Lu75amn?= <renjing@uestc.edu.cn>, =?utf-8?B?QsO2cmplIE9obG1hbg==?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, Jianping Wang <jianwang@cityu.edu.hk>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 19:19:34 -0000

DQpPbiBPY3QgMTgsIDIwMTIsIGF0IDg6MDcgUE0sIFdpbGwgTGl1IChTaHVjaGVuZykgd3JvdGU6
DQoNCj4gSW50ZWdyYXRlZCB3aXRoIElQIHN0cmF0ZWd5IGV4dGVuZHMgdGhlIGV4aXN0aW5nIElQ
IHByb3RvY29sIChJUCBvcHRpb24pIHRvIHN1cHBvcnQgSUNOLiBUaGUgdXBkYXRlZCBJUCByb3V0
ZXIsIGNhbGxlZCBjb250ZW50IHJvdXRlciwgd2lsbCBkZWFsIHdpdGggc3VjaCBzcGVjaWFsIHBh
Y2tldHMuIEhvd2V2ZXIsIG1hbnkgcm91dGVycyB3aXRoIG5vIHN1cHBvcnQgb2Ygc3VjaCBleHRl
bnNpb24gbWF5IGRpcmVjdGx5IGRyb3AgdGhlIHBhY2tldHMgd2l0aCBhbiB1bmtub3duIElQIG9w
dGlvbi4gDQoNCklQLWxheWVyIGluZm9ybWF0aW9uIGNvdWxkIGJlIGNhcnJpZWQgaW4gSVB2Nidz
IGhvcC1ieS1ob3Agb3B0aW9uLCBhbmQgaXMgbm90ICpzdXBwb3NlZCogdG8gaGF2ZSB0aGF0IGVm
ZmVjdC4gVHlpbmcgdGhpcyB0byBJUHY0IGRvZXMnIHNvdW5kIGxpa2UgYSBsb25nIHRlcm0gc3Ry
YXRlZ3ku

From Ignacio.Solis@parc.com  Thu Oct 18 13:00:26 2012
Return-Path: <Ignacio.Solis@parc.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F1F21F85CB for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 13:00:26 -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=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KG2GWd0DqEge for <icnrg@ietfa.amsl.com>; Thu, 18 Oct 2012 13:00:25 -0700 (PDT)
Received: from omega.xerox.com (omega.xerox.com [13.1.64.95]) by ietfa.amsl.com (Postfix) with ESMTP id 636A521F84A8 for <icnrg@irtf.org>; Thu, 18 Oct 2012 13:00:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by omega.xerox.com (Postfix) with ESMTP id 653B9522007; Thu, 18 Oct 2012 13:00:23 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at parc.com
Received: from omega.xerox.com ([127.0.0.1]) by localhost (omega.xerox.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D49Ykj1juiS5; Thu, 18 Oct 2012 13:00:23 -0700 (PDT)
Received: from exchangehub.parc.xerox.com (vertigo.parc.xerox.com [13.2.13.102]) by omega.xerox.com (Postfix) with ESMTPS id 3A9BB522001; Thu, 18 Oct 2012 13:00:23 -0700 (PDT)
Received: from E2010DAG5.corp.ad.parc.com ([fe80::3d0b:7158:aec4:e05e]) by vertigo.corp.ad.parc.com ([fe80::606e:47ce:f5e2:fe3a%16]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 13:00:23 -0700
From: <Ignacio.Solis@parc.com>
To: <Brian_Field@cable.comcast.com>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNrNwCbMb4oP6GXk67QOg3U2AGMpe/O8AAgACj3gCAABJqgA==
Date: Thu, 18 Oct 2012 20:00:21 +0000
Message-ID: <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com>
In-Reply-To: <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.244.190.163]
Content-Type: text/plain; charset="utf-8"
Content-ID: <31FD6BAD4F4D944EB3D1DB19517DDAC2@ad.parc.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: icnrg@irtf.org
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 20:00:26 -0000

SGkgQnJpYW4uDQoNCllvdSBhcmUgcmlnaHQgdGhhdCBmb3IgYSBzdWJzZXQgb2YgY2FzZXMgIGl0
IHNlZW1zIGxpa2UgSUNOIGlzIGp1c3QgQ0ROLCBidXQgdGhhdCB3b3VsZCBiZSBtaXNzaW5nIGEg
bG90IG9mIHRoZSBwaWN0dXJlLg0KDQpGaXJzdCwgY2FuIHlvdSBkZXNjcmliZSB3aGF0IHRoZSBw
cm9wZXJ0aWVzIG9mIG5hdGl2ZSBJQ04gYW5kIG5vbi1uYXRpdmUgSUNOIGFyZT8gIElzIHRoZXJl
IG5vICJyb3V0ZXIgY2FjaGluZyIgaW4gbm9uLW5hdGl2ZSBJQ04/DQoNCkEgZmV3IG9mIHRoZSB0
aGluZ3MgdGhhdCBkb24ndCBzZWVtIHRvIGZpdCBpbnRvIHRyYWRpdGlvbmFsIENETnMgKHdpdGgg
bXkgbGltaXRlZCBrbm93bGVkZ2Ugb2Ygc3RhdGUtb2YtdGhlIGFydCBDRE5zKSBhcmU6DQoNCi0g
UGVlci10by1wZWVyLiAgSG93IGNhbiBDRE5zIGhlbHAgdHdvIG5vZGVzIGNvbW11bmljYXRlIHdp
dGhvdXQgaW5mcmFzdHJ1Y3R1cmU/ICBJZiB0d28gbm9kZXMgbWVldCBpbiB0aGUgZmllbGQgKHN1
Y2ggYXMgaW4gdGhlIERBUlBBIENCTUVOIHByb2dyYW0sIG9yIHR3byBwaG9uZXMgb24gYSBwbGFu
ZSBvciB0dW5uZWwgb3Igc2hpcCksIGhvdyBjYW4gQ0ROcyBoZWxwIHRoZW0gZXhjaGFuZ2UgaW5m
b3JtYXRpb24/DQoNCi0gU2VjdXJpdHkuIEhvdyBjYW4gQ0ROcyBlbnN1cmUgdGhlIHByb3ZlbmFu
Y2Ugb2YgdGhlIGRhdGE/DQoNCi0gRGlzcnVwdGlvbiB0b2xlcmFuY2UuIEhvdyBjYW4gQ0ROcyBl
bmFibGUgZGF0YS1tdWxpbmc/DQoNCi0gRmxvdyBjb250cm9sLiBIb3cgY2FuIHlvdSBjaGFuZ2Ug
dGhlIHdheSB3ZSBkbyBmbG93LWNvbnRyb2wgdXNpbmcgQ0ROcz8NCg0KLSBMb25lIGhpdC4gSG93
IGNhbiBDRE5zIGhlbHAgZGlzdHJpYnV0ZSBkYXRhIHRoYXQgd2FzIHByZXZpb3VzbHkgdW5rbm93
biB0byB0aGUgQ0ROLiBGb3IgZXhhbXBsZSwgZnJvbSBhIHJhbmRvbSB3ZWJwYWdlLg0KDQoNCkdy
YW50ZWQsIHNvbWUgb2YgdGhvc2UgYXJlIHNvbWV3aGF0IHBvc3NpYmxlIHVzaW5nIENETnMuIFNv
bWUgb2YgdGhvc2UgYXJlIHBvc3NpYmxlIHdpdGggYSBsaXR0bGUgYml0IG9mIHdvcmsgb24gQ0RO
cyBhbmQgc29tZSBhcmUgcG9zc2libGUgd2l0aCBhIGxvdCBvZiB3b3JrLiAgDQoNCkV2ZXJ5dGhp
bmcgaXMgcG9zc2libGUuDQoNCkJ1dCwgd2UncmUgZ29pbmcgdG8gZ2V0IHRvIGEgcG9pbnQgd2hl
cmUgd2UncmUgY2hhbmdpbmcgc28gbXVjaCB0aGF0IHdoYXQgd2Ugc3RhcnRlZCB3aXRoIGlzIHVu
cmVjb2duaXphYmxlLiAgU3RhcnRpbmcgd2l0aCBDRE5zIGlzIGxpbWl0aW5nIHdoYXQgd2UgY2Fu
IGRvIGFuZCBob3cgd2UgZG8gaXQuICBUaGUgbW9kZWwgbWFueSBJQ05zIHRha2UgaXMgYSBjbGVh
biBzbGF0ZSBvbmUuIEFuZCBhcyBmYXIgYXMgcG9zc2libGUsIHdlIHRyeSB0byBsZWFybiB0aGUg
bGVzc29ucyBvZiBDRE5zLCBEVE5zLCBJUHMsIEdudXRlbGxhcywgTXVsdGljYXN0LCBSVFBzLCBJ
UFNlY3MsIFRDUHMsIEROU3MsIE9TUEZzLCBldGMuDQoNCkNhY2hpbmcgYXQgdGhlIHJvdXRlciBs
ZXZlbCBpcyBvbmUgb2YgdGhlIG1hbnkgcG90ZW50aWFsbHkgYmVuZWZpY2lhbCAoYnV0IG5vdC1y
ZXF1aXJlZCkgY2hhcmFjdGVyaXN0aWNzIG9mIElDTnMuDQoNCklmIHdlIHRhbGsgYWJvdXQgYSBz
cGVjaWZpYyBJQ04gYXJjaGl0ZWN0dXJlIChsaWtlIENDTikgd2UgY2FuIHRhbGsgYWJvdXQgc3Bl
Y2lmaWMgYWR2YW50YWdlcyBhbmQgZGlzYWR2YW50YWdlcywgdHJhZGVvZmZzIG1hZGUsIHdvcmsg
ZG9uZSBzbyBmYXIsIHdvcmsgcGxhbm5lZCBhbmQgd29yayB5ZXQgdG8gYmUgZG9uZS4NCg0KTmFj
aG8NCg0KDQoNCi0tDQpOYWNobyAoSWduYWNpbykgU29saXMNClNlbmlvciBSZXNlYXJjaCBTY2ll
bnRpc3QNClBhbG8gQWx0byBSZXNlYXJjaCBDZW50ZXIgKFBBUkMpDQorMSg2NTApIDgxMi00NDU4
DQpJZ25hY2lvLlNvbGlzQHBhcmMuY29tDQoNCg0KDQoNCk9uIE9jdCAxOCwgMjAxMiwgYXQgMjo1
NCBQTSwgIkZpZWxkLCBCcmlhbiIgPEJyaWFuX0ZpZWxkQGNhYmxlLmNvbWNhc3QuY29tPg0KIHdy
b3RlOg0KDQo+IERvZXMgYW55b25lIChiZXNpZGUgbWUpIHRoaW5rIHRoYXQgYSBDRE4gZWZmZWN0
aXZlbHkgaXMgYWxyZWFkeSBkb2luZyAiSUNOIiBidXQgdHVubmVsZWQgb3ZlciBhbiBIVFRQIGlu
ZnJhc3RydWN0dXJlICh2aWEgSFRUUC9UQ1AvSVApLiAgIEkgdGhpbmsgb2YgQ0ROIGFuZCBuYXRp
dmUgSUNOICh3aGVyZSB0aGUgcm91dGVyIGlzIGNhY2hpbmcgYW5kIGZvcndhcmRpbmcgYXQgdGhl
IElDTiBsZXZlbCkgbmVhcmx5IGlkZW50aWNhbCBmb3J3YXJkaW5nIHBhcmFkaWdtcyBqdXN0IG9w
ZXJhdGluZyBhdCBkaWZmZXJlbnQgbGV2ZWxzIGluIHRoZSBzdGFjay4gIA0KPiANCj4gVGhlcmUn
cyB3b3JrIGluIHN0YW5kYXJkaXppbmcgdGhlIGludHJhLUNETiAgYW5kIGludGVyLUNETiBjb250
cm9sIHBsYW4gKGluIENETi1JIGFuZCBlbHNld2hlcmUpLiAgSU1PLCBpdCB3b3VsZCBiZSB1c2Vm
dWwgaWYgd2UgaGFkIHRoZSBzYW1lIGNvbnRyb2wgcHJvdG9jb2wgb3BlcmF0aW5nIGluIGJvdGgg
dGhlIENETiBhbmQgSUNOIGRvbWFpbnMgYW5kIHRoZSAidHJhbnNpdGlvbiIgd2FzIGp1c3QgY2hh
bmdpbmcgdGhlIGxheWVyIGF0IHdoaWNoIGZvcndhcmRpbmcgb2NjdXJyZWQuDQo+IA0KPiBCcmlh
bg0KPiANCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGljbnJnLWJv
dW5jZXNAaXJ0Zi5vcmcgW21haWx0bzppY25yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhhbGYg
T2YgV2lsbCBMaXUgKFNodWNoZW5nKQ0KPiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOCwgMjAx
MiAzOjA4IEFNDQo+IFRvOiBCw7ZyamUgT2hsbWFuOyBTZXVuZy1JayBMZWUNCj4gQ2M6IOS7u+Wp
pzsgaWNucmc7IEppYW5waW5nIFdhbmcNCj4gU3ViamVjdDogUmU6IFtpY25yZ10gQW5ub3VuY2lu
ZyBJQ05SRyBAIElFVEYgODUNCj4gDQo+IEhpLA0KPiANCj4gTXkgZ3JvdXAgYXJlIGFsc28gaW50
ZXJlc3RlZCBpbiBJQ04gZGVwbG95bWVudCBhbmQgaGF2ZSBkb25lIHNvbWUgc3VydmV5IG9uIHRo
aXMgbWF0dGVyLiBUaGUgZGlzY3Vzc2lvbiBvbiBJQ04gZGVwbG95bWVudCBpcyBhIGdyZWF0IHRv
cGljIHdoaWNoIElTUHMgd2lsbCBkZWZpbml0ZWx5IGJlIGludGVyZXN0ZWQgaW4uIEhlcmUgYXJl
IG91ciAyLWNlbnRzLiANCj4gDQo+IFRoZSBldm9sdmVtZW50IG9mIElDTiBtYXkgdGFrZSB0aGUg
Zm9sbG93aW5nIHRocmVlIGltcGxlbWVudGF0aW9uczogaW50ZWdyYXRlZCB3aXRoIElQLCBvdmVy
IElQIGFuZCBvdmVyIFNETi4gVGhlc2Ugc3RyYXRlZ2llcyBhbGwgY2FuIGhlbHAgdGhlIElTUCBz
aGlmdCBmcm9tIHRoZSB0cmFkaXRpb25hbCBJUCB0byBJQ04uIFRoZSBvbmx5IHF1ZXN0aW9uIGlz
IHdoaWNoIG9uZSBpcyB0aGUgYmVzdCBjaG9pY2UgZm9yIGxhcmdlIHNjYWxlIGRlcGxveW1lbnQ/
IA0KPiANCj4gSW50ZWdyYXRlZCB3aXRoIElQIHN0cmF0ZWd5IGV4dGVuZHMgdGhlIGV4aXN0aW5n
IElQIHByb3RvY29sIChJUCBvcHRpb24pIHRvIHN1cHBvcnQgSUNOLiBUaGUgdXBkYXRlZCBJUCBy
b3V0ZXIsIGNhbGxlZCBjb250ZW50IHJvdXRlciwgd2lsbCBkZWFsIHdpdGggc3VjaCBzcGVjaWFs
IHBhY2tldHMuIEhvd2V2ZXIsIG1hbnkgcm91dGVycyB3aXRoIG5vIHN1cHBvcnQgb2Ygc3VjaCBl
eHRlbnNpb24gbWF5IGRpcmVjdGx5IGRyb3AgdGhlIHBhY2tldHMgd2l0aCBhbiB1bmtub3duIElQ
IG9wdGlvbi4gDQo+IA0KPiBJQ04gb3ZlciBJUCBzdHJhdGVneSB1c2VzIGFuIG92ZXJsYXkgYXBw
cm9hY2guIENvbnRlbnQtcmVsYXRlZCBvcGVyYXRpb24gd2lsbCBiZSBwZXJmb3JtZWQgb24gdGhl
IGhpZ2ggbGF5ZXIgYW5kIENvbnRlbnQtcmVsYXRlZCBpbmZvcm1hdGlvbiB3aWxsIGJlIHNlbnQg
dGhyb3VnaCBhIHR1bm5lbC4gRHVlIHRvIHRoZSBsaW1pdGVkIGtub3dsZWRnZSBvZiBwaHlzaWNh
bCB0b3BvbG9neSBhbmQgdW5uZWNlc3NhcnkgcGFja2V0IGVuY2Fwc3VsYXRpb24vZGlzY29uc29s
YXRpb24sIHRoZSBlZmZpY2llbmN5IG1heSBiZSBsaW1pdGVkLiANCj4gDQo+IElDTiBvdmVyIFNE
TiBzdHJhdGVneSBleHBsb2l0cyBTRE4gY29udHJvbGxlciB0byBwZXJmb3JtIGNvbnRlbnQtcmVs
YXRlZCBvcGVyYXRpb24uIEhvd2V2ZXIsIFNETiBpdHNlbGYgaXMgYW4gb25nb2luZyBhcHByb2Fj
aCBhbmQgaXMgdHlwaWNhbGx5IHVzZWQgaW4gYSBsb2NhbCBkb21haW4uIFRoZSBwZXJmb3JtYW5j
ZSBpbiBhIGxhcmdlIHNjYWxlIGRlcGxveW1lbnQgaXMgdW5rbm93bi4gDQo+IA0KPiBXaWxsDQo+
IA0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IGljbnJnLWJvdW5jZXNA
aXJ0Zi5vcmcgW21haWx0bzppY25yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhhbGYgDQo+PiBP
ZiBCP3JqZSBPaGxtYW4NCj4+IFNlbnQ6IFRodXJzZGF5LCBPY3RvYmVyIDE4LCAyMDEyIDEwOjU1
IEFNDQo+PiBUbzogU2V1bmctSWsgTGVlDQo+PiBDYzogaWNucmcNCj4+IFN1YmplY3Q6IFJlOiBb
aWNucmddIEFubm91bmNpbmcgSUNOUkcgQCBJRVRGIDg1DQo+PiANCj4+IERlYXIgU2V1bmctSWss
DQo+PiANCj4+IEkgdGhpbmsgeW91IGJyaW5nIHVwIGEgdmVyeSBnb29kIHBvaW50LiBJIGFncmVl
IHRoYXQgZGVwbG95bWVudCBhbmQgDQo+PiBtaWdyYXRpb24gaXNzdWVzIGFyZSB2ZXJ5IGltcG9y
dGFudC4gSSBhbHNvIGFncmVlIHRoYXQgdGhleSBkb24ndCBzZWVtIA0KPj4gbGlrZSBhIGdvb2Qg
Zml0IGZvciBhbnkgb2YgdGhlIGN1cnJlbnRseSBwcm9wb3NlZCBJQ05SRyBkb2N1bWVudHMuDQo+
PiANCj4+IFRoZSB0aHJlZSBkb2N1bWVudHMgbGlzdGVkIGFzIGN1cnJlbnQgd29yayBpdGVtcyBh
cmUgaW4gbm8gd2F5IHNldCBpbiANCj4+IHN0b25lLCB0aGV5IHNob3VsZCBqdXN0IGJlIHNlZW4g
YXMgYSBzdGFydGluZyBwb2ludCBmb3Igb3VyIHdvcmsuIElmIA0KPj4geW91IHdvdWxkIGxpa2Ug
dG8gcHJvcG9zZSB0aGUgUkcgdGhhdCB3ZSBzaG91bGQgc3RhcnQgd29ya2luZyBvbiBhIA0KPj4g
ZGVwbG95bWVudCBkb2N1bWVudCB5b3UgYXJlIG1vc3Qgd2VsY29tZSB0byBkbyBzbywgdGhhdCB3
aWxsIG1vc3QgDQo+PiBjZXJ0YWlubHkgYmUgaW4gc2NvcGUgZm9yIG91ciBkaXNjdXNzaW9uIGlu
IEF0bGFudGEuDQo+PiANCj4+IEFzIGEgZ2VuZXJhbCBjb21tZW50IEkgYWxzbyBsaWtlIHRvIG1l
bnRpb24gdGhhdCB3ZSBhcyBhbiBSRyBhcmUgbm90IA0KPj4gYm91bmQgYnkgYWxsIHRoZSBydWxl
cyB0aGF0IGFwcGx5IHRvIElFVEYgV0dzLCBlLmcuIHdlIGFyZSBmcmVlIHRvIA0KPj4gZGlzY3Vz
cyBsYXRlIGNvbnRyaWJ1dGlvbnMgcHJvZHVjZWQgYWZ0ZXIgdGhlIElFVEYgZHJhZnQgZGVhZGxp
bmVzLiBTbyANCj4+IGlmIHBlb3BsZSBmaW5kIHRoZSB0aW1lIHRvIHdyaXRlIHVwIHNvbWUgbWF0
ZXJpYWwgZm9yIHRoZSBJQ05SRyBhZnRlciANCj4+IHRoZSBJRVRGIGRyYWZ0cyBhcmUgZG9uZSB0
aGV5IGFyZSB3ZWxjb21lIHRvIGFubm91bmNlIGl0IHRvIHRoZSBJQ05SRyANCj4+IG1haWxpbmcg
bGlzdC4gSWYgdGhlIGdyb3VwIGFncmVlcyB3ZSBhcmUgZnJlZSB0byBkaXNjdXNzIGFsc28gc3Vj
aCANCj4+IG1hdGVyaWFsIGF0IG91ciBtZWV0aW5nLA0KPj4gDQo+PiAgICAgQsO2cmplDQo+PiAN
Cj4+IDE4IG9rdCAyMDEyIGtsLiAwMzo1NiBza3JldiAiU2V1bmctSWsgTGVlIiA8c2V1bmdpa2xl
ZUBldHJpLnJlLmtyPjoNCj4+IA0KPj4+IERlYXIgaWNucmcgY29sbGVhZ3VlcywNCj4+PiANCj4+
PiBSZWdhcmRpbmcgdGhlIFJHIGRvY3VtZW50cywgZG9uJ3Qgd2UgdG91Y2ggYW55IGlzc3VlcyBv
biBJQ04NCj4+IGRlcGxveW1lbnRzPw0KPj4+IA0KPj4+IEFzIHdlIGhhdmUgc2VlbiBpbiB0aGUg
cHJlc2VudGF0aW9uIGJ5IFpURSBpbiBWYW5jb3V2ZXIsIElTUHMgYXJlIA0KPj4+IGludGVyZXN0
ZWQgaW4gdGhlIHNob3J0LXRlcm0gYXBwcm9hY2hlcyB0byBJQ04uDQo+Pj4gVGhvdWdoIHRoZSB0
cmFkaXRpb25hbCBJQ04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04vTkROKSBoYXZlIA0KPj4+IHBy
b3ZpZGVkIElTUHMgYSBsYWRkZXIgb3V0IG9mIGR1bWItcGlwZXMsIElTUHMgbWF5IGhhdmUgZGlm
ZmljdWx0aWVzIA0KPj4+IG9uIGNsZWFuLXNsYXRlIGFwcHJvYWNoZXMgb2YgSUNOLg0KPj4+IElN
SE8sIGJhc2VkIG9uIG91ciBzdXJ2ZXlzIG9uIElTUCBSJkQgYXBwcm9hY2hlcyB0byBJQ04sIEtv
cmVhbiBJU1BzIA0KPj4+IGFyZSBpbiB0aGUgc2ltaWxhciBzaXR1YXRpb24uDQo+Pj4gDQo+Pj4g
SW4gdGhpcyBtb3RpdmF0aW9uLCBJIGhhdmUgaW50ZXJlc3RzIGluIElDTiBkZXBsb3ltZW50IHN0
cmF0ZWdpZXMgDQo+Pj4gKHN1Y2ggYXMgSUNOIG92ZXIgSVAgb3IgSUNOIG92ZXIgU0ROIGFzIHNo
b3J0LXRlcm0gYXBwcm9hY2hlcykgYnV0IA0KPj4+IG5vIGlkZWEgd2hpY2ggUkcgZG9jdW1lbnQg
d291bGQgY292ZXIgdGhlIGRlcGxveW1lbnQgaXNzdWVzLCBldmVuIA0KPj4+IHdoZXRoZXIgaWNu
cmcgd2lsbCBjb3ZlciB0aGUgZGVwbG95bWVudCBpc3N1ZSBvciBub3QuDQo+Pj4gDQo+Pj4gDQo+
Pj4gDQo+Pj4gMjAxMi8xMC84IELDtnJqZSBPaGxtYW4gPEJvcmplLk9obG1hbkBlcmljc3Nvbi5j
b20+Og0KPj4+PiBUaGUgbmV4dCBJQ05SRyB3aWxsIGJlIGhlbGQgYXQgIElFVEYgODUsIEF0bGFu
dGEsIEdlb3JnaWEsIFVTQSwNCj4+IE5vdmVtYmVyDQo+Pj4+IDQtOSwgMjAxMg0KPj4+PiAgICAg
KiBNZWV0aW5nIHRpbWU6IFdFRE5FU0RBWSAxMy4wMC0xNS40MCAocHJlbCkNCj4+Pj4gDQo+Pj4+
IFRoZSBtYWluIGRpc2N1c3Npb24gYXQgdGhlIG1lZXRpbmcgd2lsbCBiZSB0aGUgdGhyZWUgZG9j
dW1lbnRzIHRoYXQgDQo+Pj4+IHRoZQ0KPj4gUkcNCj4+Pj4gaGFzIHNldCBvdXQgdG8gcHJvZHVj
ZS4NCj4+Pj4gDQo+Pj4+IElDTiBTdXJ2ZXkgZG9jdW1lbnQNCj4+Pj4gDQo+Pj4+IEEgZG9jdW1l
bnQgdGhhdCBwcm92aWRlcyBhIHN1cnZleSBvZiBkaWZmZXJlbnQgYXBwcm9hY2hlcyBhbmQNCj4+
IHRlY2huaXF1ZXMNCj4+Pj4gDQo+Pj4+IElDTiBQcm9ibGVtIHN0YXRlbWVudA0KPj4+PiANCj4+
Pj4gQSBkb2N1bWVudCB0aGF0IGRlc2NyaWJlcyB0aGUgSUNOIHByb2JsZW0gc3RhdGVtZW50LCB0
aGUgbWFpbg0KPj4gY29uY2VwdHMgYW5kDQo+Pj4+IHJlc2VhcmNoIGNoYWxsZW5nZXMgaW4gZGVw
dGguDQo+Pj4+IA0KPj4+PiBJQ04gQmFzZWxpbmUgU2NlbmFyaW9zDQo+Pj4+IA0KPj4+PiBBIGRv
Y3VtZW50IHRoYXQgZGVmaW5lcyByZWZlcmVuY2UgYmFzZWxpbmUgc2NlbmFyaW9zIHRvIGVuYWJs
ZQ0KPj4gcGVyZm9ybWFuY2UNCj4+Pj4gY29tcGFyaXNvbnMgYmV0d2VlbiBkaWZmZXJlbnQgYXBw
cm9hY2hlcy4NCj4+Pj4gDQo+Pj4+IFBlb3BsZSBhcmUgZW5jb3VyYWdlZCB0byBwcmVzZW50IHRo
ZWlyIHZpZXdzIG9uIHdoYXQgdGhleSB0aGluayANCj4+Pj4gc2hvdWxkDQo+PiBiZQ0KPj4+PiB0
aGUgY29udGVudHMgb2YgdGhlc2UgZG9jdW1lbnRzLiBFYXJseSBjb250cmlidXRpb25zIChpbiBi
dWxsZXQgDQo+Pj4+IGZvcm0gb3IgYXMgZHJhZnQgdGV4dCkgYXJlIHdlbGNvbWUgYm90aCBvbiB0
aGUgbWFpbGluZyBsaXN0IGFuZCB0aGUgd2lraS4NCj4+IFByZXNlbnRhdGlvbnMNCj4+Pj4gb2Yg
ZHJhZnQgbWF0ZXJpYWwgYXJlIHdlbGNvbWUgYXQgdGhlIG1lZXRpbmcuDQo+Pj4+IA0KPj4+PiBN
b3N0IGxpa2VseSB3ZSB3aWxsIGFsc28gaGF2ZSB0aW1lIHRvIGRpc2N1c3Mgb25lIG9yIHR3byBz
cGVjaWZpYyANCj4+Pj4gdGVjaG5pY2FsIHRvcGljcyBhdCB0aGUgbWVldGluZy4gUHJvcG9zYWxz
IGZvciBzdWNoIHRvcGljcyBhcyB3ZWxsIA0KPj4+PiBhcyBwcmVzZW50YXRpb25zIGFyZSBpbnZp
dGVkLg0KPj4+PiANCj4+Pj4gQXMgd2UgYXJlIGV4cGVjdGVkIHRvIHB1Ymxpc2ggb3VyIGFnZW5k
YSBieSAyMDEyLTEwLTI0IChXZWRuZXNkYXkpIA0KPj4+PiB3ZQ0KPj4gd291bGQNCj4+Pj4gbGlr
ZSB0byBoYXZlIHlvdXIgaW5wdXQgYnkgU3VuZGF5IDIwMTItMTAtMjEuDQo+Pj4+IA0KPj4+PiBC
w7ZyamUsIERhdmUgJiBEaXJrDQo+Pj4+IA0KPj4+PiANCj4+Pj4gSUNOIFJHIFdpa2k6DQo+Pj4+
IA0KPj4+PiBodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy9ncm91cC9pcnRmL3RyYWMvd2lraS9p
Y25yZw0KPj4+PiANCj4+Pj4gDQo+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+Pj4+IGljbnJnIG1haWxpbmcgbGlzdA0KPj4+PiBpY25yZ0BpcnRm
Lm9yZw0KPj4+PiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQo+
Pj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IC0tDQo+Pj4gU2V1bmctSWsgTGVlICjsnbTsirns
nbUpDQo+Pj4gU3RhbmRhcmRzIFJlc2VhcmNoIENlbnRlciwgRVRSSQ0KPj4+IFRlbC4gICAgKzgy
LTQyLTg2MC0xNDgzDQo+Pj4gRmF4LiAgICs4Mi00Mi04NjEtNTQwNA0KPj4+IEVtYWlsLiBzZXVu
Z2lrbGVlQGV0cmkucmUua3INCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+PiBpY25yZyBtYWlsaW5nIGxpc3QNCj4+IGljbnJnQGlydGYub3JnDQo+
PiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQo+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGljbnJnIG1haWxpbmcg
bGlzdA0KPiBpY25yZ0BpcnRmLm9yZw0KPiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2ljbnJnDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+IGljbnJnIG1haWxpbmcgbGlzdA0KPiBpY25yZ0BpcnRmLm9yZw0KPiBodHRwczov
L3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQoNCg==

From spis@intracom.com  Fri Oct 19 00:35:46 2012
Return-Path: <spis@intracom.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B64F21F8630 for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 00:35:46 -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=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUhnd+dHmQIk for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 00:35:45 -0700 (PDT)
Received: from extmail.intranet.gr (extmail.intranet.gr [192.92.155.11]) by ietfa.amsl.com (Postfix) with ESMTP id 49D8C21F8620 for <icnrg@irtf.org>; Fri, 19 Oct 2012 00:35:44 -0700 (PDT)
Received: from mailserv.intranet.gr (mailserv.intranet.GR [146.124.14.106]) by extmail.intranet.gr (8.14.5/8.14.5) with ESMTP id q9J7ZaXg017924 for <icnrg@irtf.org>; Fri, 19 Oct 2012 10:35:36 +0300 (EEST)
Received: from mailserv.intranet.gr (localhost [127.0.0.1]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id q9J7ZaPs028333 for <icnrg@irtf.org>; Fri, 19 Oct 2012 10:35:36 +0300 (EEST)
Received: from iris.intranet.gr (iris.intranet.GR [146.124.80.178]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id q9J7ZWuS028298; Fri, 19 Oct 2012 10:35:32 +0300 (EEST)
Received: from [10.124.82.96] ([10.124.82.96] verified) by iris.intranet.gr (CommuniGate Pro SMTP 5.3.13) with ESMTP id 50430898; Fri, 19 Oct 2012 10:35:31 +0300
Message-ID: <508102C3.2040302@intracom.com>
Date: Fri, 19 Oct 2012 10:35:31 +0300
From: Spiros Spirou <spis@intracom.com>
Organization: Intracom Telecom
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ignacio.Solis@parc.com
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com>
In-Reply-To: <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: icnrg@irtf.org
Subject: Re: [icnrg] CDN and ICN (was: Announcing ICNRG @ IETF 85)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: spis@intracom.com
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 07:35:46 -0000

Hi Nacho and Brian,

Good points! In CDNI, the relationship between CDN and ICN was briefly 
discussed in section 3 of the (now expired) 
draft-fmn-cdni-advanced-use-cases. Unfortunately, we never carried this 
work forward.

The draft is available at:
http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt

Spiros

On 18/10/2012 11:00 ÎĽÎĽ, Ignacio.Solis@parc.com wrote:
> Hi Brian.
>
> You are right that for a subset of cases  it seems like ICN is just CDN, but that would be missing a lot of the picture.
>
> First, can you describe what the properties of native ICN and non-native ICN are?  Is there no "router caching" in non-native ICN?
>
> A few of the things that don't seem to fit into traditional CDNs (with my limited knowledge of state-of-the art CDNs) are:
>
> - Peer-to-peer.  How can CDNs help two nodes communicate without infrastructure?  If two nodes meet in the field (such as in the DARPA CBMEN program, or two phones on a plane or tunnel or ship), how can CDNs help them exchange information?
>
> - Security. How can CDNs ensure the provenance of the data?
>
> - Disruption tolerance. How can CDNs enable data-muling?
>
> - Flow control. How can you change the way we do flow-control using CDNs?
>
> - Lone hit. How can CDNs help distribute data that was previously unknown to the CDN. For example, from a random webpage.
>
>
> Granted, some of those are somewhat possible using CDNs. Some of those are possible with a little bit of work on CDNs and some are possible with a lot of work.
>
> Everything is possible.
>
> But, we're going to get to a point where we're changing so much that what we started with is unrecognizable.  Starting with CDNs is limiting what we can do and how we do it.  The model many ICNs take is a clean slate one. And as far as possible, we try to learn the lessons of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs, OSPFs, etc.
>
> Caching at the router level is one of the many potentially beneficial (but not-required) characteristics of ICNs.
>
> If we talk about a specific ICN architecture (like CCN) we can talk about specific advantages and disadvantages, tradeoffs made, work done so far, work planned and work yet to be done.
>
> Nacho
>
>
>
> --
> Nacho (Ignacio) Solis
> Senior Research Scientist
> Palo Alto Research Center (PARC)
> +1(650) 812-4458
> Ignacio.Solis@parc.com
>
>
>
>
> On Oct 18, 2012, at 2:54 PM, "Field, Brian" <Brian_Field@cable.comcast.com>
>   wrote:
>
>> Does anyone (beside me) think that a CDN effectively is already doing "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).   I think of CDN and native ICN (where the router is caching and forwarding at the ICN level) nearly identical forwarding paradigms just operating at different levels in the stack.
>>
>> There's work in standardizing the intra-CDN  and inter-CDN control plan (in CDN-I and elsewhere).  IMO, it would be useful if we had the same control protocol operating in both the CDN and ICN domains and the "transition" was just changing the layer at which forwarding occurred.
>>
>> Brian
>>
>>
>> -----Original Message-----
>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of Will Liu (Shucheng)
>> Sent: Thursday, October 18, 2012 3:08 AM
>> To: BÎ“Â¶rje Ohlman; Seung-Ik Lee
>> Cc: Î´Â»Â»ÎµÂ©Â§; icnrg; Jianping Wang
>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>
>> Hi,
>>
>> My group are also interested in ICN deployment and have done some survey on this matter. The discussion on ICN deployment is a great topic which ISPs will definitely be interested in. Here are our 2-cents.
>>
>> The evolvement of ICN may take the following three implementations: integrated with IP, over IP and over SDN. These strategies all can help the ISP shift from the traditional IP to ICN. The only question is which one is the best choice for large scale deployment?
>>
>> Integrated with IP strategy extends the existing IP protocol (IP option) to support ICN. The updated IP router, called content router, will deal with such special packets. However, many routers with no support of such extension may directly drop the packets with an unknown IP option.
>>
>> ICN over IP strategy uses an overlay approach. Content-related operation will be performed on the high layer and Content-related information will be sent through a tunnel. Due to the limited knowledge of physical topology and unnecessary packet encapsulation/disconsolation, the efficiency may be limited.
>>
>> ICN over SDN strategy exploits SDN controller to perform content-related operation. However, SDN itself is an ongoing approach and is typically used in a local domain. The performance in a large scale deployment is unknown.
>>
>> Will
>>
>>> -----Original Message-----
>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf
>>> Of B?rje Ohlman
>>> Sent: Thursday, October 18, 2012 10:55 AM
>>> To: Seung-Ik Lee
>>> Cc: icnrg
>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>
>>> Dear Seung-Ik,
>>>
>>> I think you bring up a very good point. I agree that deployment and
>>> migration issues are very important. I also agree that they don't seem
>>> like a good fit for any of the currently proposed ICNRG documents.
>>>
>>> The three documents listed as current work items are in no way set in
>>> stone, they should just be seen as a starting point for our work. If
>>> you would like to propose the RG that we should start working on a
>>> deployment document you are most welcome to do so, that will most
>>> certainly be in scope for our discussion in Atlanta.
>>>
>>> As a general comment I also like to mention that we as an RG are not
>>> bound by all the rules that apply to IETF WGs, e.g. we are free to
>>> discuss late contributions produced after the IETF draft deadlines. So
>>> if people find the time to write up some material for the ICNRG after
>>> the IETF drafts are done they are welcome to announce it to the ICNRG
>>> mailing list. If the group agrees we are free to discuss also such
>>> material at our meeting,
>>>
>>>      BÎ“Â¶rje
>>>
>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>>
>>>> Dear icnrg colleagues,
>>>>
>>>> Regarding the RG documents, don't we touch any issues on ICN
>>> deployments?
>>>>
>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>>> interested in the short-term approaches to ICN.
>>>> Though the traditional ICN approaches (such as CCN/NDN) have
>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have difficulties
>>>> on clean-slate approaches of ICN.
>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
>>>> are in the similar situation.
>>>>
>>>> In this motivation, I have interests in ICN deployment strategies
>>>> (such as ICN over IP or ICN over SDN as short-term approaches) but
>>>> no idea which RG document would cover the deployment issues, even
>>>> whether icnrg will cover the deployment issue or not.
>>>>
>>>>
>>>>
>>>> 2012/10/8 BÎ“Â¶rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>> November
>>>>> 4-9, 2012
>>>>>      * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>
>>>>> The main discussion at the meeting will be the three documents that
>>>>> the
>>> RG
>>>>> has set out to produce.
>>>>>
>>>>> ICN Survey document
>>>>>
>>>>> A document that provides a survey of different approaches and
>>> techniques
>>>>>
>>>>> ICN Problem statement
>>>>>
>>>>> A document that describes the ICN problem statement, the main
>>> concepts and
>>>>> research challenges in depth.
>>>>>
>>>>> ICN Baseline Scenarios
>>>>>
>>>>> A document that defines reference baseline scenarios to enable
>>> performance
>>>>> comparisons between different approaches.
>>>>>
>>>>> People are encouraged to present their views on what they think
>>>>> should
>>> be
>>>>> the contents of these documents. Early contributions (in bullet
>>>>> form or as draft text) are welcome both on the mailing list and the wiki.
>>> Presentations
>>>>> of draft material are welcome at the meeting.
>>>>>
>>>>> Most likely we will also have time to discuss one or two specific
>>>>> technical topics at the meeting. Proposals for such topics as well
>>>>> as presentations are invited.
>>>>>
>>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday)
>>>>> we
>>> would
>>>>> like to have your input by Sunday 2012-10-21.
>>>>>
>>>>> BÎ“Â¶rje, Dave & Dirk
>>>>>
>>>>>
>>>>> ICN RG Wiki:
>>>>>
>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> icnrg mailing list
>>>>> icnrg@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Seung-Ik Lee (ÎĽďż˝Î„ÎĽďż˝Î‰ÎĽďż˝Âµ)
>>>> Standards Research Center, ETRI
>>>> Tel.    +82-42-860-1483
>>>> Fax.   +82-42-861-5404
>>>> Email. seungiklee@etri.re.kr
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From k.pentikousis@huawei.com  Fri Oct 19 01:44:50 2012
Return-Path: <k.pentikousis@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2552921F8630 for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 01:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dlSNgrXHLpZB for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 01:44:49 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 48D1321F85C2 for <icnrg@irtf.org>; Fri, 19 Oct 2012 01:44:49 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml206-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AQX61353; Fri, 19 Oct 2012 16:44:45 +0800 (CST)
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml206-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 19 Oct 2012 16:44:04 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.98]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Fri, 19 Oct 2012 16:44:11 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
Thread-Topic: [icnrg] Announcing  ICNRG @  IETF 85
Thread-Index: AQHNrSHD4SQ7DNGrgk+yQBXFMrjVTpfAUPnw
Date: Fri, 19 Oct 2012 08:44:10 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4E0B6F@szxeml545-mbx.china.huawei.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <507FCFAE.6020403@cs.tcd.ie>
In-Reply-To: <507FCFAE.6020403@cs.tcd.ie>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.37.56]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Announcing  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 08:44:50 -0000

  |Bottom line: I'd suggest renaming this document to
  |"ICN concepts and research challenges" rather than
  |"ICN problem statement."

I second this too, although the "concepts" part may overlap with the survey=
 document.

Best Regards,

Kostas




From andrea.detti@uniroma2.it  Fri Oct 19 05:56:57 2012
Return-Path: <andrea.detti@uniroma2.it>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72C4021F859E for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 05:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.119
X-Spam-Level: 
X-Spam-Status: No, score=-4.119 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+UGHERvBsQL for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 05:56:54 -0700 (PDT)
Received: from smtp.uniroma2.it (smtp.uniroma2.it [160.80.6.23]) by ietfa.amsl.com (Postfix) with ESMTP id 02C3C21F85A4 for <icnrg@irtf.org>; Fri, 19 Oct 2012 05:56:53 -0700 (PDT)
Received: from smtpauth.uniroma2.it (smtpauth.uniroma2.it [160.80.6.46]) by smtp.uniroma2.it (8.13.6/8.13.6) with ESMTP id q9JCrLb4022669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Oct 2012 14:53:22 +0200
Received: from [192.168.1.101] ([160.80.82.70]) (authenticated bits=0) by smtpauth.uniroma2.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9JCuMOI031899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Oct 2012 14:56:26 +0200
Message-ID: <50814DF6.1050904@uniroma2.it>
Date: Fri, 19 Oct 2012 14:56:22 +0200
From: Andrea Detti <andrea.detti@uniroma2.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>, icnrg@irtf.org
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>, <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
X-MailScanner-From: andrea.detti@uniroma2.it
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 12:56:57 -0000

Dear Will,
regarding the "Integrated with IP" strategy, we proposed in [1], in 2011 
we assessed performance of sending IP packets with a novel IP Option 
(named CONET option [2]) and we found that the most of traversed routers 
did NOT block packets with the, unknown, IP CONET Option. See our 
measurements in section 5.2 of [1].
Have you some novel measurements that motivates your sentence " many 
routers with no support of such extension may directly drop the packets 
with an unknown IP option" ?
Regards,

Andrea


[1] A. DETTI, N. BLEFARI-MELAZZI, S. SALSANO, M. POMPOSINI â€ś CONET: A 
Content Centric Inter-Networking Architectureâ€ť, ACM SIGCOMM 2011, ICN 
workshop, Toronto , Canada, 19 August 2011 
(http://netgroup.uniroma2.it/Andrea_Detti/papers/conferences/CONET.pdf)
[2] https://tools.ietf.org/html/draft-detti-conet-ip-option-02



On 10/18/2012 11:07 AM, Will Liu (Shucheng) wrote:
> Hi,
>
> My group are also interested in ICN deployment and have done some survey on this matter. The discussion on ICN deployment is a great topic which ISPs will definitely be interested in. Here are our 2-cents.
>
> The evolvement of ICN may take the following three implementations: integrated with IP, over IP and over SDN. These strategies all can help the ISP shift from the traditional IP to ICN. The only question is which one is the best choice for large scale deployment?
>
> Integrated with IP strategy extends the existing IP protocol (IP option) to support ICN. The updated IP router, called content router, will deal with such special packets. However, many routers with no support of such extension may directly drop the packets with an unknown IP option.
>
> ICN over IP strategy uses an overlay approach. Content-related operation will be performed on the high layer and Content-related information will be sent through a tunnel. Due to the limited knowledge of physical topology and unnecessary packet encapsulation/disconsolation, the efficiency may be limited.
>
> ICN over SDN strategy exploits SDN controller to perform content-related operation. However, SDN itself is an ongoing approach and is typically used in a local domain. The performance in a large scale deployment is unknown.
>
> Will
>
>> -----Original Message-----
>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of
>> B?rje Ohlman
>> Sent: Thursday, October 18, 2012 10:55 AM
>> To: Seung-Ik Lee
>> Cc: icnrg
>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>
>> Dear Seung-Ik,
>>
>> I think you bring up a very good point. I agree that deployment and
>> migration issues are very important. I also agree that they don't seem like a
>> good fit for any of the currently proposed ICNRG documents.
>>
>> The three documents listed as current work items are in no way set in stone,
>> they should just be seen as a starting point for our work. If you would like to
>> propose the RG that we should start working on a deployment document
>> you are most welcome to do so, that will most certainly be in scope for our
>> discussion in Atlanta.
>>
>> As a general comment I also like to mention that we as an RG are not bound
>> by all the rules that apply to IETF WGs, e.g. we are free to discuss late
>> contributions produced after the IETF draft deadlines. So if people find the
>> time to write up some material for the ICNRG after the IETF drafts are done
>> they are welcome to announce it to the ICNRG mailing list. If the group
>> agrees we are free to discuss also such material at our meeting,
>>
>>       BĂ¶rje
>>
>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>
>>> Dear icnrg colleagues,
>>>
>>> Regarding the RG documents, don't we touch any issues on ICN
>> deployments?
>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>> interested in the short-term approaches to ICN.
>>> Though the traditional ICN approaches (such as CCN/NDN) have provided
>>> ISPs a ladder out of dumb-pipes, ISPs may have difficulties on
>>> clean-slate approaches of ICN.
>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
>>> are in the similar situation.
>>>
>>> In this motivation, I have interests in ICN deployment strategies
>>> (such as ICN over IP or ICN over SDN as short-term approaches)
>>> but no idea which RG document would cover the deployment issues, even
>>> whether icnrg will cover the deployment issue or not.
>>>
>>>
>>>
>>> 2012/10/8 BĂ¶rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>> November
>>>> 4-9, 2012
>>>>       * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>
>>>> The main discussion at the meeting will be the three documents that the
>> RG
>>>> has set out to produce.
>>>>
>>>> ICN Survey document
>>>>
>>>> A document that provides a survey of different approaches and
>> techniques
>>>> ICN Problem statement
>>>>
>>>> A document that describes the ICN problem statement, the main
>> concepts and
>>>> research challenges in depth.
>>>>
>>>> ICN Baseline Scenarios
>>>>
>>>> A document that defines reference baseline scenarios to enable
>> performance
>>>> comparisons between different approaches.
>>>>
>>>> People are encouraged to present their views on what they think should
>> be
>>>> the contents of these documents. Early contributions (in bullet form or as
>>>> draft text) are welcome both on the mailing list and the wiki.
>> Presentations
>>>> of draft material are welcome at the meeting.
>>>>
>>>> Most likely we will also have time to discuss one or two specific technical
>>>> topics at the meeting. Proposals for such topics as well as presentations
>>>> are invited.
>>>>
>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we
>> would
>>>> like to have your input by Sunday 2012-10-21.
>>>>
>>>> BĂ¶rje, Dave & Dirk
>>>>
>>>>
>>>> ICN RG Wiki:
>>>>
>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>>
>>>>
>>>> _______________________________________________
>>>> icnrg mailing list
>>>> icnrg@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>>
>>>
>>>
>>> --
>>> Seung-Ik Lee (ěť´ěŠąěťµ)
>>> Standards Research Center, ETRI
>>> Tel.    +82-42-860-1483
>>> Fax.   +82-42-861-5404
>>> Email. seungiklee@etri.re.kr
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


-- 
---------------------------------------
Andrea Detti, PhD
Dip. Ingegneria Elettronica
Universita' di Roma "Tor Vergata"
Via del Politecnico 1, 00133 Roma, Italy
Tel.: +39-06-7259-7445
Fax : +39-06-7259-7435
Mobile: +39-320-4391909
email: andrea.detti@uniroma2.it
---------------------------------------


From andrea.detti@uniroma2.it  Fri Oct 19 06:05:31 2012
Return-Path: <andrea.detti@uniroma2.it>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3A021F859E for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 06:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=-0.606, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4, SARE_SPEC_REPLICA_OBFU=1.812]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUGqkmAWUShj for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 06:05:27 -0700 (PDT)
Received: from smtp.uniroma2.it (smtp.uniroma2.it [160.80.6.23]) by ietfa.amsl.com (Postfix) with ESMTP id CE4E521F84F1 for <icnrg@irtf.org>; Fri, 19 Oct 2012 06:05:26 -0700 (PDT)
Received: from smtpauth.uniroma2.it (smtpauth.uniroma2.it [160.80.6.46]) by smtp.uniroma2.it (8.13.6/8.13.6) with ESMTP id q9JD1xa8023309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Oct 2012 15:02:00 +0200
Received: from [192.168.1.101] ([160.80.82.70]) (authenticated bits=0) by smtpauth.uniroma2.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9JD52sX032024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Oct 2012 15:05:03 +0200
Message-ID: <50814FFE.3090101@uniroma2.it>
Date: Fri, 19 Oct 2012 15:05:02 +0200
From: Andrea Detti <andrea.detti@uniroma2.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: icnrg@irtf.org, "Will Liu (Shucheng)" <liushucheng@huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
X-MailScanner-From: andrea.detti@uniroma2.it
Subject: Re: [icnrg] FW: New Version Notification for draft-ren-icn-content-retrieval-00.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 13:05:31 -0000

Dear Will,

I have some comments regarding the CONVERGENCE project, in which I am 
involved.

The CONVERGENCE network (CONET) is similar to CCNx; we complement it 
with some missing functionality or we try to improve its performance, 
e.g. routing [1], named-sap [2], transport, etc..


In what follows I propose some changes to the valuable description 
provided by the draft, regarding how CONVERGENCE deals with the 
following issues:



<Content name resolution>

the draft reports : "Dedicate Name-System-Nodes (similar to DNS) are 
deployed"

This sentence might be understood as: “to forward a content request, a 
CONET node always queries the Name-System-Nodes to resolve the next-hop”.

This is not true since, as CCNx, a CONET node usually resolves the 
names, en-route, by means of a name-based forwarding information base 
(FIB), i.e. without contacting the Name-System-Nodes (or better 
Name-Routing-System nodes, see [1])

However, current fast FIBs (e.g. based on SRAM) have a size unable to 
store all possible name-prefixes.

To cope with this issue, a CONET node uses the FIB as "route cache".

If the node does not have the routing entry necessary to route-by-name 
an Interest message, then the node lookups the routing information in 
the Name-Routing-System and caches the routing entry in the FIB.

Therefore, lookups occur only in cases of route-cache misses, which 
should be a rare event.

Furthermore, as general comment, I think that it could be important to 
specify, for any project, if Content Name Resolution is performed at 
packet-rate or only one-time per download, i.e. at session-rate.

A CONET node performs name resolution at packet-rate by using a FIB and, 
sometimes, by contacting nodes of a Name-Routing-System.

Consequently, I would revise the draft as follows "En-route name 
resolution performed at packet-rate by means of name-based forwarding 
tables, which are used as route-caches. Route-cache misses are resolved 
by means of a dedicated Name-Routing-Sytem node (similar to DNS)."




<k-anycast and multicast>

the draft reports: " Traditional point-to-point sessions between two 
upper layer entities can be supported by coupling the upper layer 
entities with named-service-assess-points. This functionality can be 
extended to support multicast"


I think that this is not completely true. Indeed, named-saps are not 
meant for multicasting purpose, but [2] to support legacy point-to-point 
interactive service sessions, e.g. home banking.

Multicast is achieved in CCNx/CONET by exploiting both en-route 
in-network caching and the mechanism of Pending Interest Table (PIT), as 
described in [NDN].

In case of a multicast service, e.g. video live streaming, many sources 
send the same Interest message, e.g. to request the next video frame. 
Using the PIT mechanism, in case of quite-synchronous Interests, or 
using in-network caching, in case of nearly-synchronous Interest, the 
same content chunk is transferred only one time, on a link of the 
multicast tree rooted at source.

Consequently, regarding multicast, I would revise the draft as follows:

"Receiver-driven multicast based on i) routing information temporary 
left in network nodes (aka Pending Interest Table) and ii) in-network 
caching"

Regarding k-multicast, I would revise the draft as follows 
"Receiver-driven k-multicast, by concurrently fetching different data 
chunks from the different replica Servers"



<Content replication>

it is OK



<In-network cache discovery>

it is OK



Thanks a lot for your effort,



Andrea



[1] A. Detti, M. Pomposini, N. Blefari-Melazzi, S. Salsano, “Supporting 
the Web with an Information Centric Network that Routes by Name”, 
Elsevier Computer Networks, vol. 56, Issue 17, p. 3705–3722 
(http://netgroup.uniroma2.it/Andrea_Detti/Lookup-and-Cache/comnet-web-ICN-ext.pdf)

[2] "D3.1 - Definition of the system services and functional 
components", CONVERGENCE deliverable, see Section 4.1


On 10/15/2012 01:47 PM, Will Liu (Shucheng) wrote:
> Hello,
>
> We have submitted a new draft discussing about content retrieval in ICN. Here, we discussed basic requirements on the basis of previous literatures, the fundamental functionalities required to satisfy the foregoing requirements, and the implementation status of such functionalities in various Information-Centric Network architectures.
>
> Your comments are highly appreciated.
>
> Regards,
> Shucheng LIU (Will)
>
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, October 15, 2012 7:26 PM
> To: Will Liu (Shucheng)
> Cc: jingren@cityu.edu.hk; jianwang@cityu.edu.hk; feitang@cityu.edu.hk
> Subject: New Version Notification for draft-ren-icn-content-retrieval-00.txt
>
>
> A new version of I-D, draft-ren-icn-content-retrieval-00.txt
> has been successfully submitted by Will Liu and posted to the
> IETF repository.
>
> Filename:	 draft-ren-icn-content-retrieval
> Revision:	 00
> Title:		 On the Content Retrieval In Information-Centric Network
> Creation date:	 2012-10-15
> WG ID:		 Individual Submission
> Number of pages: 11
> URL:             http://www.ietf.org/internet-drafts/draft-ren-icn-content-retrieval-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval
> Htmlized:        http://tools.ietf.org/html/draft-ren-icn-content-retrieval-00
>
>
> Abstract:
>     Information-Centric Network(ICN), as an emerging network
>     architecture, focus on delivering content more efficiently.  This
>     brief paper discusses some issues about content retrieval in the
>     Information-Centric Network.  It first lists a set of basic
>     requirements on the basis of previous literatures.  Then, it tries to
>     identify the fundamental functionalities required to satisfy the
>     foregoing requirements.  Last, it summarizes the implementation
>     status of such functionalities in various Information-Centric Network
>     architectures.
>                                                                                
>
>
> The IETF Secretariat
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>


-- 
---------------------------------------
Andrea Detti, PhD
Dip. Ingegneria Elettronica
Universita' di Roma "Tor Vergata"
Via del Politecnico 1, 00133 Roma, Italy
Tel.: +39-06-7259-7445
Fax : +39-06-7259-7435
Mobile: +39-320-4391909
email: andrea.detti@uniroma2.it
---------------------------------------


From paulo.mendes@ulusofona.pt  Fri Oct 19 14:16:57 2012
Return-Path: <paulo.mendes@ulusofona.pt>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D949A21F879B for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 14:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFKUhrxKW2Mb for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 14:16:57 -0700 (PDT)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9638121F8799 for <icnrg@irtf.org>; Fri, 19 Oct 2012 14:16:56 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id x43so591652wey.13 for <icnrg@irtf.org>; Fri, 19 Oct 2012 14:16:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=5aj6g2/0+kzOCHFU1kpTnIfjWpr3jlTcEq6hfez6z1Y=; b=lfkB6LWyEcQf/DbBXEsMLx4BbKeSXVPggjM5Z38sAFnrQ4Eu4n/CiMiXug6s332jrb ukG4VDDwwSDFVmBvDRQk4tWOj0nceejAot6IeYGs9gOhtRzrhVmwOOQN1YzeVwxxCeq9 +E46Guy5ZuNVS8RExP/ThJWf/AAvupcUDFoo4adclWtdKQCh9hjlerZax58dSd82jcNk EzA+/4TTpfSTvW0gsyyfxdZAq+4MGMoOFWmsn3PiQjJgI8GgX0KgaPIVBermOQH8auLV x+jIQDf1muyQ8g1lP6q0n8ptzuSiLvJwMCdW3OyPwtBfA1Onpnln8lHnCrTzIVsfBote DUZw==
Received: by 10.180.108.38 with SMTP id hh6mr2919957wib.0.1350681415256; Fri, 19 Oct 2012 14:16:55 -0700 (PDT)
Received: from unknown-f8-1e-df-e9-b9-b2.lan ([89.181.195.175]) by mx.google.com with ESMTPS id cu1sm36753607wib.6.2012.10.19.14.16.45 (version=SSLv3 cipher=OTHER); Fri, 19 Oct 2012 14:16:47 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3E0DBD9C-7783-4794-9AFE-CDB9AA258DA8"
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4E0B6F@szxeml545-mbx.china.huawei.com>
Date: Fri, 19 Oct 2012 22:16:44 +0100
Message-Id: <318BADD8-F240-4F61-B3E6-F45B2BD76A77@ulusofona.pt>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <507FCFAE.6020403@cs.tcd.ie> <8D38716F0C1A444BA0CD7E96454366C23A4E0B6F@szxeml545-mbx.china.huawei.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQnkArLlaz3M8dFraVl+yjxKyyyxysxEsbdgB6BD5KHAMp4KO5hS6LtvCJFK3g5LoQjTYNAc
Cc: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [icnrg] Announcing  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 21:16:58 -0000

--Apple-Mail=_3E0DBD9C-7783-4794-9AFE-CDB9AA258DA8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I support the idea of renaming the "problem statement" draft by an =
"research challenges" draft.. I also agree that "concepts" are more a =
subject of the survey drafts. Actually IMO these two drafts should =
really be align, to avoid too much overlapping..

I would say that for a RG (not WG) we need to have a glimpse of the =
following to start with:
a) Characterization of the major ICN concepts and techniques
b) identification of the major research challenges

So why not to rename the two drafts as:
a) ICN Concepts (instead of he survey one)
b) ICN Research Challenges (instead of the problem statement)

The first one may be used later on to drive some common understanding =
about an ICN architecture. The second one to drive the identification of =
specific (protocol) components.

Regards
Paulo


On Oct 19, 2012, at 9:44 AM, Konstantinos Pentikousis wrote:

>  |Bottom line: I'd suggest renaming this document to
>  |"ICN concepts and research challenges" rather than
>  |"ICN problem statement."
>=20
> I second this too, although the "concepts" part may overlap with the =
survey document.
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

-------------------------------------------------------------
Paulo Mendes, Ph.D
Scientific Director for Innovation of the Research Unit in Informatics =
Systems and Technologies (SITI)
Director of the Ph.D program on Informatics - New Media and Pervasive =
Systems (NEMPS)
Secretary of the ACM SIGCOMM Chapter - Portugal
University Lusofona, Portugal
paulo.mendes@ulusofona.pt
http://siti.ulusofona.pt/~pmendes
Tel.: 217 515 500 Fax: 21 757 7006


--Apple-Mail=_3E0DBD9C-7783-4794-9AFE-CDB9AA258DA8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
support the idea of renaming the "problem statement" draft by an =
"research challenges" draft.. I also agree that "concepts" are more a =
subject of the survey drafts. Actually IMO these two drafts should =
really be align, to avoid too much overlapping..<div><br></div><div>I =
would say that for a RG (not WG) we need to have a glimpse of the =
following to start with:</div><div>a) Characterization of the major ICN =
concepts and techniques</div><div>b) identification of the major =
research challenges<br><div><br></div><div>So why not to rename the two =
drafts as:</div><div>a) ICN Concepts (instead of he survey =
one)</div><div>b) ICN Research Challenges (instead of the problem =
statement)</div><div><br></div><div>The first one may be used later on =
to drive some common understanding about an ICN architecture. The second =
one to drive the identification of specific (protocol) =
components.</div><div><br></div><div>Regards</div><div>Paulo</div><div><br=
></div><div><br><div><div>On Oct 19, 2012, at 9:44 AM, Konstantinos =
Pentikousis wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div> =
&nbsp;|Bottom line: I'd suggest renaming this document to<br> =
&nbsp;|"ICN concepts and research challenges" rather than<br> =
&nbsp;|"ICN problem statement."<br><br>I second this too, although the =
"concepts" part may overlap with the survey document.<br><br>Best =
Regards,<br><br>Kostas<br><br><br><br>____________________________________=
___________<br>icnrg mailing list<br><a =
href=3D"mailto:icnrg@irtf.org">icnrg@irtf.org</a><br>https://www.irtf.org/=
mailman/listinfo/icnrg<br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div>-------------------------------------------------------------</div>=
<div>Paulo Mendes, Ph.D</div><div>Scientific Director for Innovation of =
the Research Unit in Informatics Systems and Technologies =
(SITI)</div><div>Director of the Ph.D program on Informatics - New Media =
and Pervasive Systems (NEMPS)</div><div>Secretary of the ACM SIGCOMM =
Chapter - Portugal</div><div>University Lusofona, Portugal</div><div><a =
href=3D"mailto:paulo.mendes@ulusofona.pt">paulo.mendes@ulusofona.pt</a></d=
iv><div><a =
href=3D"http://siti.ulusofona.pt/~pmendes">http://siti.ulusofona.pt/~pmend=
es</a></div><div>Tel.: 217&nbsp;515 500 Fax: 21 757 =
7006</div></div></span></div></span></div></span></div></span></div></span=
></div></span></div></span></div></span></div></span></div></span></div></=
span></div></span></div></span></div></span></div></span></div></span></di=
v></span></span>
</div>
<br></div></div></body></html>=

--Apple-Mail=_3E0DBD9C-7783-4794-9AFE-CDB9AA258DA8--

From xu.xin18@zte.com.cn  Fri Oct 19 20:20:25 2012
Return-Path: <xu.xin18@zte.com.cn>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDF721F889F for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 20:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeIPOHK+rg3m for <icnrg@ietfa.amsl.com>; Fri, 19 Oct 2012 20:20:24 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id CA63A21F889B for <icnrg@irtf.org>; Fri, 19 Oct 2012 20:20:19 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id B0E00126E564; Sat, 20 Oct 2012 11:21:06 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q9K3KDVB062033; Sat, 20 Oct 2012 11:20:13 +0800 (GMT-8) (envelope-from xu.xin18@zte.com.cn)
To: borje.ohlman@ericsson.com, kutscher@neclab.eu, oran@cisco.com, icnrg@irtf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFB0DFF510.BE03AD94-ON48257A9D.001159F0-48257A9D.00126B71@zte.com.cn>
From: xu.xin18@zte.com.cn
Date: Sat, 20 Oct 2012 11:19:57 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-10-20 11:19:51, Serialize complete at 2012-10-20 11:19:51
Content-Type: multipart/alternative; boundary="=_alternative 00126B6D48257A9D_="
X-MAIL: mse01.zte.com.cn q9K3KDVB062033
Subject: [icnrg] Can we ask for a time slot at ICNRG @Atlanta?
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2012 03:20:26 -0000

This is a multipart message in MIME format.

--=_alternative 00126B6D48257A9D_=
Content-Type: text/plain; charset="US-ASCII"

Hi all,

We have updated our draft about ICN deployment considerations and ICN 
design for ISP's existing networks. It can be access at 
http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01. Comments are 
welcome.

Can we ask for a time slot to present this update? Thank you!

Best regards,
Xin Xu

> -----Original Message-----
> 
> A new version of I-D, draft-li-icnrg-icn-isp-01.txt
> has been successfully submitted by Xin Xu and posted to the
> IETF repository.
> 
> Filename:    draft-li-icnrg-icn-isp
> Revision:    01
> Title:       Information-Centric Network in an ISP
> Creation date:    2012-10-20
> WG ID:       Individual Submission
> Number of pages: 9
> URL:             http://www.ietf.org/internet-drafts/draft-li-icnrg-
> icn-isp-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-li-icnrg-icn-isp
> Htmlized:        http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01
> Diff: http://www.ietf.org/rfcdiff?url2=draft-li-icnrg-icn-isp-01
> 
> Abstract:
>    Information-Centric Network (ICN) may be deployed over different
>    underlying networks, e.g. ad hoc networks, DTN and ISP's networks.
>    This document discusses deploying ICN in an ISP's existing networks
>    and ICN design for ISPs.
> 
>  
> 
> 
> The IETF Secretariat
> 
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.

--=_alternative 00126B6D48257A9D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi all,</font>
<br>
<br><font size=2 face="sans-serif">We have updated our draft about ICN
deployment considerations and ICN design for ISP's existing networks. It
can be access at </font><font size=2><tt>http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01.
Comments are welcome.</tt></font>
<br><font size=2 face="sans-serif"><br>
Can we ask for a time slot to present this update? Thank you!<br>
<br>
Best regards,<br>
Xin Xu<br>
</font>
<br><font size=2><tt>&gt; -----Original Message-----<br>
&gt; <br>
&gt; A new version of I-D, draft-li-icnrg-icn-isp-01.txt<br>
&gt; has been successfully submitted by Xin Xu and posted to the<br>
&gt; IETF repository.<br>
&gt; <br>
&gt; Filename: &nbsp; &nbsp;draft-li-icnrg-icn-isp<br>
&gt; Revision: &nbsp; &nbsp;01<br>
&gt; Title: &nbsp; &nbsp; &nbsp; Information-Centric Network in an ISP<br>
&gt; Creation date: &nbsp; &nbsp;2012-10-20<br>
&gt; WG ID: &nbsp; &nbsp; &nbsp; Individual Submission<br>
&gt; Number of pages: 9<br>
&gt; URL: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; http://www.ietf.org/internet-drafts/draft-li-icnrg-<br>
&gt; icn-isp-01.txt<br>
&gt; Status: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;http://datatracker.ietf.org/doc/draft-li-icnrg-icn-isp<br>
&gt; Htmlized: &nbsp; &nbsp; &nbsp; &nbsp;http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01<br>
&gt; Diff: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;http://www.ietf.org/rfcdiff?url2=draft-li-icnrg-icn-isp-01<br>
&gt; <br>
&gt; Abstract:<br>
&gt; &nbsp; &nbsp;Information-Centric Network (ICN) may be deployed over
different<br>
&gt; &nbsp; &nbsp;underlying networks, e.g. ad hoc networks, DTN and ISP's
networks.<br>
&gt; &nbsp; &nbsp;This document discusses deploying ICN in an ISP's existing
networks<br>
&gt; &nbsp; &nbsp;and ICN design for ISPs.<br>
&gt; <br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; <br>
&gt; <br>
&gt; The IETF Secretariat<br>
&gt; <br>
</tt></font>
<br><pre><font color="blue">
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.

</font></pre><br>

--=_alternative 00126B6D48257A9D_=--

From borje.ohlman@ericsson.com  Mon Oct 22 04:28:58 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1BF21F8B97 for <icnrg@ietfa.amsl.com>; Mon, 22 Oct 2012 04:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.948
X-Spam-Level: 
X-Spam-Status: No, score=-5.948 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pfmy8XpPCv7W for <icnrg@ietfa.amsl.com>; Mon, 22 Oct 2012 04:28:57 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id B8CFD21F8B7A for <icnrg@irtf.org>; Mon, 22 Oct 2012 04:28:56 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-64-50852df78a84
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 05.2B.04547.6FD25805; Mon, 22 Oct 2012 13:28:55 +0200 (CEST)
Received: from dhcp-147-214-183-183.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.93) with Microsoft SMTP Server id 8.3.279.1; Mon, 22 Oct 2012 13:28:38 +0200
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2C0CF179-68DD-41BC-B6DC-354A640425B0"
Date: Mon, 22 Oct 2012 13:28:37 +0200
In-Reply-To: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
To: icnrg <icnrg@irtf.org>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com>
Message-ID: <5657F0FD-6706-441B-BA93-683A3266836F@ericsson.com>
X-Mailer: Apple Mail (2.1278)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42KZGfG3Vve7bmuAwdw5/BY7Z+9kcmD0mLzx MFsAYxSXTUpqTmZZapG+XQJXxorL/AWtARVHL89lbWC86NbFyMEhIWAiseM3excjJ5ApJnHh 3nq2LkYuDiGBU4wSJ5+dZoZwDjBKHPl7H6yKTcBR4nHLelaQZl4BQ4nOwzkgYWaBJInVO68y g9jCAgYSTx6sZAYpYRFQlfhzPQ0kzCngIDF37V1WEFtEQEpi0967bCC2kIC9RPeJG4wQE+0l 9s9lgjhHVuJ28wR2iBI1iRkfHzFNYOSfhbB3FpK9ELa2xLKFr6FsPYkbU6ewYYrrSsz4d4hl ASPbKkbh3MTMnPRyI73Uoszk4uL8PL3i1E2MwCA9uOW36g7GO+dEDjFKc7AoifNab93jLySQ nliSmp2aWpBaFF9UmpNafIiRiYNTqoFxGteevv9fz+/KmGFoUvlcNqLZ+N0FjRJ20edO06/y L1b5+HZ6cQ/fuds3L+ydaDFt4b2q/Lpd6ew3Y02uPfw6VSdMxt0h6GBny8JdR6MemZvcaT4V 4RweFDwzpne1QFRPoWDAl2UH3ja+6I04Lblpkt5/h76ycv6PCsrCIVW/Nasm/67MkI1UYinO SDTUYi4qTgQAMJ1jjiACAAA=
Subject: [icnrg] Proposed agenda items  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 11:28:58 -0000

--Apple-Mail=_2C0CF179-68DD-41BC-B6DC-354A640425B0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

I've listed the proposed agenda items on the Wiki, see also below. =
Please let me know if I missed some proposition or if you have any last =
minute request before we make the agenda tomorrow, Tuesday.

	B=F6rje

---------------
Proposed agenda items for ICNRG@IETF 85
Discussion ICNRG documents
Discussing who to deal with ICN deployment issues
Proposed inputs:
 =
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf
 http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf
Presentation of On the Content Retrieval In Information-Centric Network, =
http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval
ICN vs. CDN  =
http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt
Presentation of updates to Information-Centric Network in an ISP,  =
http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01
Planning of interim meeting


On 8 okt 2012, at 10:00, B=F6rje Ohlman wrote:

> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA, =
November 4-9, 2012
>       * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>=20
> The main discussion at the meeting will be the three documents that =
the RG has set out to produce.=20
> ICN Survey document
> A document that provides a survey of different approaches and =
techniques
> ICN Problem statement
> A document that describes the ICN problem statement, the main concepts =
and research challenges in depth.
> ICN Baseline Scenarios
> A document that defines reference baseline scenarios to enable =
performance comparisons between different approaches.
> People are encouraged to present their views on what they think should =
be the contents of these documents. Early contributions (in bullet form =
or as draft text) are welcome both on the mailing list and the wiki. =
Presentations of draft material are welcome at the meeting.
>=20
> Most likely we will also have time to discuss one or two specific =
technical topics at the meeting. Proposals for such topics as well as =
presentations are invited.
>=20
> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we =
would like to have your input by Sunday 2012-10-21.
>=20
> 	B=F6rje, Dave & Dirk
>=20
>=20
> ICN RG Wiki:
> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


--Apple-Mail=_2C0CF179-68DD-41BC-B6DC-354A640425B0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I've =
listed the proposed agenda items on the Wiki, see also below. Please let =
me know if I missed some proposition or if you have any last minute =
request before we make the agenda tomorrow, =
Tuesday.<div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>B=F6rje</div><div><br></div><div>---------------</div><div><ul =
style=3D"color: rgb(0, 0, 0); font-family: 'Times New Roman', times, =
serif; font-size: 15px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
background-color: rgb(255, 255, 255); "><li><ul><li>Proposed agenda =
items for ICNRG@IETF 85<ul><li>Discussion ICNRG =
documents</li><li>Discussing who to deal with ICN deployment =
issues<ul><li>Proposed inputs:<ul><li><a class=3D"ext-link" =
href=3D"http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP=
-D4.6_FinalReportOnDeplIncBusinessModels.pdf" style=3D"text-decoration: =
underline; color: rgb(68, 0, 136); border-bottom-width: 0px; "><span =
class=3D"icon" style=3D"background-image: =
url(http://trac.tools.ietf.org/group/irtf/trac/chrome/common/extlink.gif);=
 padding-left: 12px; background-position: 50% 50%; background-repeat: =
no-repeat no-repeat; =
">&nbsp;</span>http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-21617=
3-PSIRP-D4.6_FinalReportOnDeplIncBusinessModels.pdf</a></li><li><a =
class=3D"ext-link" =
href=3D"http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf" =
style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; "><span class=3D"icon" =
style=3D"background-image: =
url(http://trac.tools.ietf.org/group/irtf/trac/chrome/common/extlink.gif);=
 padding-left: 12px; background-position: 50% 50%; background-repeat: =
no-repeat no-repeat; =
">&nbsp;</span>http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf</a></li>=
</ul></li></ul></li><li>Presentation of&nbsp;<em>On the Content =
Retrieval In Information-Centric Network</em>,<a class=3D"ext-link" =
href=3D"http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval" =
style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; "><span class=3D"icon" =
style=3D"background-image: =
url(http://trac.tools.ietf.org/group/irtf/trac/chrome/common/extlink.gif);=
 padding-left: 12px; background-position: 50% 50%; background-repeat: =
no-repeat no-repeat; =
">&nbsp;</span>http://datatracker.ietf.org/doc/draft-ren-icn-content-retri=
eval</a></li><li>ICN vs. CDN&nbsp;<a class=3D"ext-link" =
href=3D"http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt"=
 style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; "><span class=3D"icon" =
style=3D"background-image: =
url(http://trac.tools.ietf.org/group/irtf/trac/chrome/common/extlink.gif);=
 padding-left: 12px; background-position: 50% 50%; background-repeat: =
no-repeat no-repeat; =
">&nbsp;</span>http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-=
00.txt</a></li><li>Presentation of updates =
to&nbsp;<em>Information-Centric Network in an ISP</em>,&nbsp;<a =
class=3D"ext-link" =
href=3D"http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01" =
style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; "><span class=3D"icon" =
style=3D"background-image: =
url(http://trac.tools.ietf.org/group/irtf/trac/chrome/common/extlink.gif);=
 padding-left: 12px; background-position: 50% 50%; background-repeat: =
no-repeat no-repeat; =
">&nbsp;</span>http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01</a></l=
i><li>Planning of interim meeting</li></ul></li></ul><br =
class=3D"Apple-interchange-newline"></li></ul><div><br></div></div><div><d=
iv><div>On 8 okt 2012, at 10:00, B=F6rje Ohlman wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>The next ICNRG will be =
held at &nbsp;IETF 85, Atlanta, Georgia, USA, November 4-9, =
2012</div><div>&nbsp; &nbsp; &nbsp; * Meeting time: WEDNESDAY =
13.00-15.40 (prel)</div><div><br></div><div>The main discussion at the =
meeting will be the three documents that the RG has set out to =
produce.&nbsp;</div><div><ul style=3D"color: rgb(0, 0, 0); font-family: =
'Times New Roman', times, serif; font-size: 15px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
background-color: rgb(255, 255, 255); "><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnSurveyDocument"=
 style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Survey document</a><ul><li>A document =
that provides a survey of different approaches and =
techniques</li></ul></li><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnProblemStatemen=
t" style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Problem statement</a><ul><li>A document =
that describes the ICN problem statement, the main concepts and research =
challenges in depth.</li></ul></li><li><a class=3D"wiki" =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnBaselineScenari=
os" style=3D"text-decoration: underline; color: rgb(68, 0, 136); =
border-bottom-width: 0px; ">ICN Baseline Scenarios</a><ul><li>A document =
that defines reference baseline scenarios to enable performance =
comparisons between different =
approaches.</li></ul></li></ul></div><div>People are encouraged to =
present their views on what they think should be the contents of these =
documents. Early contributions (in bullet form or as draft text) are =
welcome both on the mailing list and the wiki. Presentations of draft =
material are welcome at the meeting.</div><div><br></div><div>Most =
likely we will also have time to discuss one or two specific technical =
topics at the meeting. Proposals for such topics as well as =
presentations are invited.</div><div><br></div><div>As we are expected =
to publish our agenda by 2012-10-24 (Wednesday) we would like to have =
your input by Sunday 2012-10-21.</div><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>B=F6rje, =
Dave &amp; Dirk</div><div><br></div><div><br></div><div>ICN RG =
Wiki:</div><div><ul class=3D"MailOutline"><li><a =
href=3D"http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg">http://trac=
.tools.ietf.org/group/irtf/trac/wiki/icnrg</a></li></ul></div></div>______=
_________________________________________<br>icnrg mailing list<br><a =
href=3D"mailto:icnrg@irtf.org">icnrg@irtf.org</a><br>https://www.irtf.org/=
mailman/listinfo/icnrg<br></blockquote></div><br></div></body></html>=

--Apple-Mail=_2C0CF179-68DD-41BC-B6DC-354A640425B0--

From damien.saucez@gmail.com  Mon Oct 22 05:54:52 2012
Return-Path: <damien.saucez@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECA721F8B8B for <icnrg@ietfa.amsl.com>; Mon, 22 Oct 2012 05:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5FMclCvthNZ for <icnrg@ietfa.amsl.com>; Mon, 22 Oct 2012 05:54:50 -0700 (PDT)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by ietfa.amsl.com (Postfix) with ESMTP id BC23021F88D5 for <icnrg@irtf.org>; Mon, 22 Oct 2012 05:54:49 -0700 (PDT)
Received: by mail-bk0-f54.google.com with SMTP id jf20so978843bkc.13 for <icnrg@irtf.org>; Mon, 22 Oct 2012 05:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=5LtTCIWcOXY5VLLSvqpf2cZQHTm1b+oMCJ5pke3092E=; b=uD4FtiJHLrSHuVRya9ioeO05deOpBaGOgKr953t4cX/qsRmHbaEgCdi7g/lcrPq90l ICt2tqZdg0c16i7p8TGSAWCM9fSww1Nkm3b6vnjDGnA4ZeN0UgM4pPxh1+9yb2sMT4+T KVodrp3AC7gjoM9vnDGOjVF0QIt+g/nZF1hi9Fgn4xMmVbf40IW6q0xNEfwfbzmmzBe+ nwfnLW8a/iI9GIHSvPMqA+GbJLkEP83+Uy8lkxZWxCgaUE8dtrP9kKQkwVjS5wo0Ugdy tbMhE2zY5wCK5RG2O70XG3cEDx1njtY0Afs4QG8MLwlfBn+wdFihUzPxfEAZ2D9dasMh 34Ow==
Received: by 10.204.11.194 with SMTP id u2mr2590056bku.41.1350910487351; Mon, 22 Oct 2012 05:54:47 -0700 (PDT)
Received: from faucon.inria.fr (faucon.inria.fr. [138.96.201.73]) by mx.google.com with ESMTPS id j24sm3514809bkv.0.2012.10.22.05.54.45 (version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 05:54:46 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <5657F0FD-6706-441B-BA93-683A3266836F@ericsson.com>
Date: Mon, 22 Oct 2012 14:54:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BF73217-EA8D-4668-85B9-F29F9785FB7B@gmail.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <5657F0FD-6706-441B-BA93-683A3266836F@ericsson.com>
To: =?windows-1252?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
X-Mailer: Apple Mail (2.1499)
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Proposed agenda items  ICNRG @  IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 12:54:52 -0000

Hello,

That sounds nice to me.

If we have still time, I would ask for a 5 minute slot regarding
fairness. If so, I will put discussion on the wiki.

Damien Saucez

On 22 Oct 2012, at 13:28, B=F6rje Ohlman <Borje.Ohlman@ericsson.com> =
wrote:

> I've listed the proposed agenda items on the Wiki, see also below. =
Please let me know if I missed some proposition or if you have any last =
minute request before we make the agenda tomorrow, Tuesday.
>=20
> 	B=F6rje
>=20
> ---------------
> 	=95
> 		=95 Proposed agenda items for ICNRG@IETF 85
> 			=95 Discussion ICNRG documents
> 			=95 Discussing who to deal with ICN deployment =
issues
> 				=95 Proposed inputs:
> 					=95  =
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf
> 					=95  =
http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf
> 			=95 Presentation of On the Content Retrieval In =
Information-Centric Network, =
http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval
> 			=95 ICN vs. CDN  =
http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt
> 			=95 Presentation of updates to =
Information-Centric Network in an ISP,  =
http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01
> 			=95 Planning of interim meeting
>=20
>=20
> On 8 okt 2012, at 10:00, B=F6rje Ohlman wrote:
>=20
>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA, =
November 4-9, 2012
>>       * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>=20
>> The main discussion at the meeting will be the three documents that =
the RG has set out to produce.=20
>> 	=95 ICN Survey document
>> 		=95 A document that provides a survey of different =
approaches and techniques
>> 	=95 ICN Problem statement
>> 		=95 A document that describes the ICN problem statement, =
the main concepts and research challenges in depth.
>> 	=95 ICN Baseline Scenarios
>> 		=95 A document that defines reference baseline scenarios =
to enable performance comparisons between different approaches.
>> People are encouraged to present their views on what they think =
should be the contents of these documents. Early contributions (in =
bullet form or as draft text) are welcome both on the mailing list and =
the wiki. Presentations of draft material are welcome at the meeting.
>>=20
>> Most likely we will also have time to discuss one or two specific =
technical topics at the meeting. Proposals for such topics as well as =
presentations are invited.
>>=20
>> As we are expected to publish our agenda by 2012-10-24 (Wednesday) we =
would like to have your input by Sunday 2012-10-21.
>>=20
>> 	B=F6rje, Dave & Dirk
>>=20
>>=20
>> ICN RG Wiki:
>> 	=95 http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From k.pentikousis@huawei.com  Tue Oct 23 05:51:55 2012
Return-Path: <k.pentikousis@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9E3F21F86E8 for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 05:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yY9qUfOjVwtO for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 05:51:55 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id 86F6221F84C7 for <icnrg@irtf.org>; Tue, 23 Oct 2012 05:51:54 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml211-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARA85917; Tue, 23 Oct 2012 20:51:50 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 20:51:39 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Tue, 23 Oct 2012 20:51:39 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: icnrg <icnrg@irtf.org>
Thread-Topic: IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: Ac2xHSMYHmGcCj4dT7GVkqlZglE43Q==
Date: Tue, 23 Oct 2012 12:51:38 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.37.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 12:51:56 -0000

Hi all,

It seems that ICNRG overlaps with CDNi (1300-1430) and ALTO (1440-1540).

Best Regards,

Kostas



From bengta@P142.sics.se  Tue Oct 23 12:39:19 2012
Return-Path: <bengta@P142.sics.se>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0701621F859D for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 12:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wa9hSdLLx2Kq for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 12:39:18 -0700 (PDT)
Received: from sink.sics.se (sink.sics.se [193.10.64.88]) by ietfa.amsl.com (Postfix) with ESMTP id A817721F8596 for <icnrg@irtf.org>; Tue, 23 Oct 2012 12:39:17 -0700 (PDT)
Received: from P142.sics.se (h139n3-u-d1.ias.bredband.telia.com [90.228.197.139]) by sink.sics.se (8.14.5/8.14.5) with ESMTP id q9NJdAPB049565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Oct 2012 21:39:10 +0200 (CEST) (envelope-from bengta@P142.sics.se)
Received: from P142.sics.se (localhost [127.0.0.1]) by P142.sics.se (8.14.5/8.14.4) with ESMTP id q9NJdiRF002029; Tue, 23 Oct 2012 21:39:44 +0200 (CEST) (envelope-from bengta@P142.sics.se)
Received: (from bengta@localhost) by P142.sics.se (8.14.5/8.14.5/Submit) id q9NJdgsS002028; Tue, 23 Oct 2012 21:39:42 +0200 (CEST) (envelope-from bengta@P142.sics.se)
From: Bengt Ahlgren <bengta@sics.se>
To: <Ignacio.Solis@parc.com>
In-Reply-To: <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> (Ignacio Solis's message of "Thu, 18 Oct 2012 20:00:21 +0000")
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (berkeley-unix)
Date: Tue, 23 Oct 2012 21:39:41 +0200
Message-ID: <uh7zk3dq8oy.fsf@P142.sics.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: icnrg@irtf.org, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 19:42:32 -0000

I agree with Nacho, but would like to add an angle to this discussion!

CDN, IMO, is more a business model than a particular set of protocols
and services.  CDN operators agree to deliver the content of particular
publishers for a fee at some level of service.  Whether this is done on
an IP network or something else is not really important.

ICN is a different set of protocols and services compared to IP, but not
really a specific business model, although it may change the business
playing field somewhat.  So, even though we can argue that ICN is good
for content distribution, I don't think the CDN business becomes
redundant.  There will still be content publishers that want to make
sure that their content is delivered at some known level of service to
their customers.  The "normal" ICN caching simply corresponds to current
best-effort IP packet forwarding, with similar non-guarantee of service.

Having said that, when the CDN folks now are starting to define
particular protocols and interfaces (e.g., CDNI), they are working on
stuff that touches ICN, but for supporting their particular purpose (the
CDN business model).

Bengt

<Ignacio.Solis@parc.com> writes:

> Hi Brian.
>
> You are right that for a subset of cases it seems like ICN is just
> CDN, but that would be missing a lot of the picture.
>
> First, can you describe what the properties of native ICN and
> non-native ICN are?  Is there no "router caching" in non-native ICN?
>
> A few of the things that don't seem to fit into traditional CDNs (with
> my limited knowledge of state-of-the art CDNs) are:
>
> - Peer-to-peer.  How can CDNs help two nodes communicate without
> infrastructure?  If two nodes meet in the field (such as in the DARPA
> CBMEN program, or two phones on a plane or tunnel or ship), how can
> CDNs help them exchange information?
>
> - Security. How can CDNs ensure the provenance of the data?
>
> - Disruption tolerance. How can CDNs enable data-muling?
>
> - Flow control. How can you change the way we do flow-control using CDNs?
>
> - Lone hit. How can CDNs help distribute data that was previously
> unknown to the CDN. For example, from a random webpage.
>
>
> Granted, some of those are somewhat possible using CDNs. Some of those
> are possible with a little bit of work on CDNs and some are possible
> with a lot of work.
>
> Everything is possible.
>
> But, we're going to get to a point where we're changing so much that
> what we started with is unrecognizable.  Starting with CDNs is
> limiting what we can do and how we do it.  The model many ICNs take is
> a clean slate one. And as far as possible, we try to learn the lessons
> of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,
> OSPFs, etc.
>
> Caching at the router level is one of the many potentially beneficial
> (but not-required) characteristics of ICNs.
>
> If we talk about a specific ICN architecture (like CCN) we can talk
> about specific advantages and disadvantages, tradeoffs made, work done
> so far, work planned and work yet to be done.
>
> Nacho
>
>
>
> --
> Nacho (Ignacio) Solis
> Senior Research Scientist
> Palo Alto Research Center (PARC)
> +1(650) 812-4458
> Ignacio.Solis@parc.com
>
>
>
>
> On Oct 18, 2012, at 2:54 PM, "Field, Brian" <Brian_Field@cable.comcast.co=
m>
>  wrote:
>
>> Does anyone (beside me) think that a CDN effectively is already doing "I=
CN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).   I think o=
f CDN and native ICN (where the router is caching and forwarding at the ICN=
 level) nearly identical forwarding paradigms just operating at different l=
evels in the stack.=20=20
>>=20
>> There's work in standardizing the intra-CDN  and inter-CDN control plan =
(in CDN-I and elsewhere).  IMO, it would be useful if we had the same contr=
ol protocol operating in both the CDN and ICN domains and the "transition" =
was just changing the layer at which forwarding occurred.
>>=20
>> Brian
>>=20
>>=20
>> -----Original Message-----
>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf O=
f Will Liu (Shucheng)
>> Sent: Thursday, October 18, 2012 3:08 AM
>> To: B=C3=B6rje Ohlman; Seung-Ik Lee
>> Cc: =E4=BB=BB=E5=A9=A7; icnrg; Jianping Wang
>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>=20
>> Hi,
>>=20
>> My group are also interested in ICN deployment and have done some survey=
 on this matter. The discussion on ICN deployment is a great topic which IS=
Ps will definitely be interested in. Here are our 2-cents.=20
>>=20
>> The evolvement of ICN may take the following three implementations: inte=
grated with IP, over IP and over SDN. These strategies all can help the ISP=
 shift from the traditional IP to ICN. The only question is which one is th=
e best choice for large scale deployment?=20
>>=20
>> Integrated with IP strategy extends the existing IP protocol (IP option)=
 to support ICN. The updated IP router, called content router, will deal wi=
th such special packets. However, many routers with no support of such exte=
nsion may directly drop the packets with an unknown IP option.=20
>>=20
>> ICN over IP strategy uses an overlay approach. Content-related operation=
 will be performed on the high layer and Content-related information will b=
e sent through a tunnel. Due to the limited knowledge of physical topology =
and unnecessary packet encapsulation/disconsolation, the efficiency may be =
limited.=20
>>=20
>> ICN over SDN strategy exploits SDN controller to perform content-related=
 operation. However, SDN itself is an ongoing approach and is typically use=
d in a local domain. The performance in a large scale deployment is unknown=
.=20
>>=20
>> Will
>>=20
>>> -----Original Message-----
>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf=
=20
>>> Of B?rje Ohlman
>>> Sent: Thursday, October 18, 2012 10:55 AM
>>> To: Seung-Ik Lee
>>> Cc: icnrg
>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>=20
>>> Dear Seung-Ik,
>>>=20
>>> I think you bring up a very good point. I agree that deployment and=20
>>> migration issues are very important. I also agree that they don't seem=
=20
>>> like a good fit for any of the currently proposed ICNRG documents.
>>>=20
>>> The three documents listed as current work items are in no way set in=20
>>> stone, they should just be seen as a starting point for our work. If=20
>>> you would like to propose the RG that we should start working on a=20
>>> deployment document you are most welcome to do so, that will most=20
>>> certainly be in scope for our discussion in Atlanta.
>>>=20
>>> As a general comment I also like to mention that we as an RG are not=20
>>> bound by all the rules that apply to IETF WGs, e.g. we are free to=20
>>> discuss late contributions produced after the IETF draft deadlines. So=
=20
>>> if people find the time to write up some material for the ICNRG after=20
>>> the IETF drafts are done they are welcome to announce it to the ICNRG=20
>>> mailing list. If the group agrees we are free to discuss also such=20
>>> material at our meeting,
>>>=20
>>>     B=C3=B6rje
>>>=20
>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>>=20
>>>> Dear icnrg colleagues,
>>>>=20
>>>> Regarding the RG documents, don't we touch any issues on ICN
>>> deployments?
>>>>=20
>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are=20
>>>> interested in the short-term approaches to ICN.
>>>> Though the traditional ICN approaches (such as CCN/NDN) have=20
>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have difficulties=20
>>>> on clean-slate approaches of ICN.
>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs=20
>>>> are in the similar situation.
>>>>=20
>>>> In this motivation, I have interests in ICN deployment strategies=20
>>>> (such as ICN over IP or ICN over SDN as short-term approaches) but=20
>>>> no idea which RG document would cover the deployment issues, even=20
>>>> whether icnrg will cover the deployment issue or not.
>>>>=20
>>>>=20
>>>>=20
>>>> 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>> November
>>>>> 4-9, 2012
>>>>>     * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>=20
>>>>> The main discussion at the meeting will be the three documents that=20
>>>>> the
>>> RG
>>>>> has set out to produce.
>>>>>=20
>>>>> ICN Survey document
>>>>>=20
>>>>> A document that provides a survey of different approaches and
>>> techniques
>>>>>=20
>>>>> ICN Problem statement
>>>>>=20
>>>>> A document that describes the ICN problem statement, the main
>>> concepts and
>>>>> research challenges in depth.
>>>>>=20
>>>>> ICN Baseline Scenarios
>>>>>=20
>>>>> A document that defines reference baseline scenarios to enable
>>> performance
>>>>> comparisons between different approaches.
>>>>>=20
>>>>> People are encouraged to present their views on what they think=20
>>>>> should
>>> be
>>>>> the contents of these documents. Early contributions (in bullet=20
>>>>> form or as draft text) are welcome both on the mailing list and the w=
iki.
>>> Presentations
>>>>> of draft material are welcome at the meeting.
>>>>>=20
>>>>> Most likely we will also have time to discuss one or two specific=20
>>>>> technical topics at the meeting. Proposals for such topics as well=20
>>>>> as presentations are invited.
>>>>>=20
>>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday)=20
>>>>> we
>>> would
>>>>> like to have your input by Sunday 2012-10-21.
>>>>>=20
>>>>> B=C3=B6rje, Dave & Dirk
>>>>>=20
>>>>>=20
>>>>> ICN RG Wiki:
>>>>>=20
>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg

From dykim6@gmail.com  Tue Oct 23 15:47:58 2012
Return-Path: <dykim6@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349E61F0C3A for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 15:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.376
X-Spam-Level: 
X-Spam-Status: No, score=-2.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Zx4Ngs5QNwb for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 15:47:56 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id 60BC31F0C95 for <icnrg@irtf.org>; Tue, 23 Oct 2012 15:47:56 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id i29so2602522qaf.13 for <icnrg@irtf.org>; Tue, 23 Oct 2012 15:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=GGaINJwvEl71WYJair81Q/Dbqqw/U8CSxR/wSfLFWvk=; b=NJrGmTPxzxmPNPwju9oVmh+3B0qEhMkz3IFodr0fxuTDmzilo5F4tVFqtGbTiaqqrM NqY0Nl0ycXoyqc6/SspbhI/xuoaf7zhPgQA4AenC4E+GmywFYG8EzZ2nvSZ30wz/OGSr jq4Lv531BM2DcSFWmyVORoeVooCShxIy+laLNGYDFijKp193I0JJ29FtYYt2N9yC3dEB TGKeN7YkP8GrdnTxeFN7zXTGgIzgZ9s3Wd8Q093Sm7DIzNfor00y6t8M0h6ju94/wODf V4heRnHa6pIbKu49SfBsNY8cr7SwVtMt9ytvJIBP4A6u6Irpqb+t1xp25XS+aiTpofyQ 5vEQ==
Received: by 10.224.196.132 with SMTP id eg4mr6407829qab.93.1351032471274; Tue, 23 Oct 2012 15:47:51 -0700 (PDT)
MIME-Version: 1.0
Sender: dykim6@gmail.com
Received: by 10.49.12.9 with HTTP; Tue, 23 Oct 2012 15:47:31 -0700 (PDT)
In-Reply-To: <uh7zk3dq8oy.fsf@P142.sics.se>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se>
From: Dae Young KIM <dykim@cnu.kr>
Date: Wed, 24 Oct 2012 07:47:31 +0900
X-Google-Sender-Auth: szOQlTYJGdTSkP4EF5BBbGrVvSI
Message-ID: <CAFgODJeX4YePR-LK+ErwAnQnDp287g1w72PBy9HXSNjBv4MjSA@mail.gmail.com>
To: Bengt Ahlgren <bengta@sics.se>
Content-Type: multipart/alternative; boundary=20cf300fb3bd87c30804ccc1c205
Cc: Ignacio.Solis@parc.com, icnrg@irtf.org, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:47:58 -0000

--20cf300fb3bd87c30804ccc1c205
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

The ultimate criteria might be the level of incentive for end users,
content providers, and ISP's like:

  1. Are there any service differences perceived by the end users?
      o Any advantage/benefit perceived by the users?
      o Any strong incentive for end users to choose ICN against iCDN?

  2. Are there any differences perceived by the content providers?
      o Any strong incentive for content providers to choose ICN against
iCDN?

  3. Are there any incentive for the ISP's to provide the same content
delivery service by choosing the infrastructure of ICN against iCDN?

If the differential incentives are not strong enough, iCDN will only be a
pastime game.

On Wed, Oct 24, 2012 at 4:39 AM, Bengt Ahlgren <bengta@sics.se> wrote:

> I agree with Nacho, but would like to add an angle to this discussion!
>
> CDN, IMO, is more a business model than a particular set of protocols
> and services.  CDN operators agree to deliver the content of particular
> publishers for a fee at some level of service.  Whether this is done on
> an IP network or something else is not really important.
>
> ICN is a different set of protocols and services compared to IP, but not
> really a specific business model, although it may change the business
> playing field somewhat.  So, even though we can argue that ICN is good
> for content distribution, I don't think the CDN business becomes
> redundant.  There will still be content publishers that want to make
> sure that their content is delivered at some known level of service to
> their customers.  The "normal" ICN caching simply corresponds to current
> best-effort IP packet forwarding, with similar non-guarantee of service.
>
> Having said that, when the CDN folks now are starting to define
> particular protocols and interfaces (e.g., CDNI), they are working on
> stuff that touches ICN, but for supporting their particular purpose (the
> CDN business model).
>
> Bengt
>
> <Ignacio.Solis@parc.com> writes:
>
> > Hi Brian.
> >
> > You are right that for a subset of cases it seems like ICN is just
> > CDN, but that would be missing a lot of the picture.
> >
> > First, can you describe what the properties of native ICN and
> > non-native ICN are?  Is there no "router caching" in non-native ICN?
> >
> > A few of the things that don't seem to fit into traditional CDNs (with
> > my limited knowledge of state-of-the art CDNs) are:
> >
> > - Peer-to-peer.  How can CDNs help two nodes communicate without
> > infrastructure?  If two nodes meet in the field (such as in the DARPA
> > CBMEN program, or two phones on a plane or tunnel or ship), how can
> > CDNs help them exchange information?
> >
> > - Security. How can CDNs ensure the provenance of the data?
> >
> > - Disruption tolerance. How can CDNs enable data-muling?
> >
> > - Flow control. How can you change the way we do flow-control using CDN=
s?
> >
> > - Lone hit. How can CDNs help distribute data that was previously
> > unknown to the CDN. For example, from a random webpage.
> >
> >
> > Granted, some of those are somewhat possible using CDNs. Some of those
> > are possible with a little bit of work on CDNs and some are possible
> > with a lot of work.
> >
> > Everything is possible.
> >
> > But, we're going to get to a point where we're changing so much that
> > what we started with is unrecognizable.  Starting with CDNs is
> > limiting what we can do and how we do it.  The model many ICNs take is
> > a clean slate one. And as far as possible, we try to learn the lessons
> > of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,
> > OSPFs, etc.
> >
> > Caching at the router level is one of the many potentially beneficial
> > (but not-required) characteristics of ICNs.
> >
> > If we talk about a specific ICN architecture (like CCN) we can talk
> > about specific advantages and disadvantages, tradeoffs made, work done
> > so far, work planned and work yet to be done.
> >
> > Nacho
> >
> >
> >
> > --
> > Nacho (Ignacio) Solis
> > Senior Research Scientist
> > Palo Alto Research Center (PARC)
> > +1(650) 812-4458
> > Ignacio.Solis@parc.com
> >
> >
> >
> >
> > On Oct 18, 2012, at 2:54 PM, "Field, Brian" <
> Brian_Field@cable.comcast.com>
> >  wrote:
> >
> >> Does anyone (beside me) think that a CDN effectively is already doing
> "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).   I thi=
nk
> of CDN and native ICN (where the router is caching and forwarding at the
> ICN level) nearly identical forwarding paradigms just operating at
> different levels in the stack.
> >>
> >> There's work in standardizing the intra-CDN  and inter-CDN control pla=
n
> (in CDN-I and elsewhere).  IMO, it would be useful if we had the same
> control protocol operating in both the CDN and ICN domains and the
> "transition" was just changing the layer at which forwarding occurred.
> >>
> >> Brian
> >>
> >>
> >> -----Original Message-----
> >> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf
> Of Will Liu (Shucheng)
> >> Sent: Thursday, October 18, 2012 3:08 AM
> >> To: B=C3=B6rje Ohlman; Seung-Ik Lee
> >> Cc: =E4=BB=BB=E5=A9=A7; icnrg; Jianping Wang
> >> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
> >>
> >> Hi,
> >>
> >> My group are also interested in ICN deployment and have done some
> survey on this matter. The discussion on ICN deployment is a great topic
> which ISPs will definitely be interested in. Here are our 2-cents.
> >>
> >> The evolvement of ICN may take the following three implementations:
> integrated with IP, over IP and over SDN. These strategies all can help t=
he
> ISP shift from the traditional IP to ICN. The only question is which one =
is
> the best choice for large scale deployment?
> >>
> >> Integrated with IP strategy extends the existing IP protocol (IP
> option) to support ICN. The updated IP router, called content router, wil=
l
> deal with such special packets. However, many routers with no support of
> such extension may directly drop the packets with an unknown IP option.
> >>
> >> ICN over IP strategy uses an overlay approach. Content-related
> operation will be performed on the high layer and Content-related
> information will be sent through a tunnel. Due to the limited knowledge o=
f
> physical topology and unnecessary packet encapsulation/disconsolation, th=
e
> efficiency may be limited.
> >>
> >> ICN over SDN strategy exploits SDN controller to perform
> content-related operation. However, SDN itself is an ongoing approach and
> is typically used in a local domain. The performance in a large scale
> deployment is unknown.
> >>
> >> Will
> >>
> >>> -----Original Message-----
> >>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behal=
f
> >>> Of B?rje Ohlman
> >>> Sent: Thursday, October 18, 2012 10:55 AM
> >>> To: Seung-Ik Lee
> >>> Cc: icnrg
> >>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
> >>>
> >>> Dear Seung-Ik,
> >>>
> >>> I think you bring up a very good point. I agree that deployment and
> >>> migration issues are very important. I also agree that they don't see=
m
> >>> like a good fit for any of the currently proposed ICNRG documents.
> >>>
> >>> The three documents listed as current work items are in no way set in
> >>> stone, they should just be seen as a starting point for our work. If
> >>> you would like to propose the RG that we should start working on a
> >>> deployment document you are most welcome to do so, that will most
> >>> certainly be in scope for our discussion in Atlanta.
> >>>
> >>> As a general comment I also like to mention that we as an RG are not
> >>> bound by all the rules that apply to IETF WGs, e.g. we are free to
> >>> discuss late contributions produced after the IETF draft deadlines. S=
o
> >>> if people find the time to write up some material for the ICNRG after
> >>> the IETF drafts are done they are welcome to announce it to the ICNRG
> >>> mailing list. If the group agrees we are free to discuss also such
> >>> material at our meeting,
> >>>
> >>>     B=C3=B6rje
> >>>
> >>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
> >>>
> >>>> Dear icnrg colleagues,
> >>>>
> >>>> Regarding the RG documents, don't we touch any issues on ICN
> >>> deployments?
> >>>>
> >>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
> >>>> interested in the short-term approaches to ICN.
> >>>> Though the traditional ICN approaches (such as CCN/NDN) have
> >>>> provided ISPs a ladder out of dumb-pipes, ISPs may have difficulties
> >>>> on clean-slate approaches of ICN.
> >>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
> >>>> are in the similar situation.
> >>>>
> >>>> In this motivation, I have interests in ICN deployment strategies
> >>>> (such as ICN over IP or ICN over SDN as short-term approaches) but
> >>>> no idea which RG document would cover the deployment issues, even
> >>>> whether icnrg will cover the deployment issue or not.
> >>>>
> >>>>
> >>>>
> >>>> 2012/10/8 B=C3=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
> >>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
> >>> November
> >>>>> 4-9, 2012
> >>>>>     * Meeting time: WEDNESDAY 13.00-15.40 (prel)
> >>>>>
> >>>>> The main discussion at the meeting will be the three documents that
> >>>>> the
> >>> RG
> >>>>> has set out to produce.
> >>>>>
> >>>>> ICN Survey document
> >>>>>
> >>>>> A document that provides a survey of different approaches and
> >>> techniques
> >>>>>
> >>>>> ICN Problem statement
> >>>>>
> >>>>> A document that describes the ICN problem statement, the main
> >>> concepts and
> >>>>> research challenges in depth.
> >>>>>
> >>>>> ICN Baseline Scenarios
> >>>>>
> >>>>> A document that defines reference baseline scenarios to enable
> >>> performance
> >>>>> comparisons between different approaches.
> >>>>>
> >>>>> People are encouraged to present their views on what they think
> >>>>> should
> >>> be
> >>>>> the contents of these documents. Early contributions (in bullet
> >>>>> form or as draft text) are welcome both on the mailing list and the
> wiki.
> >>> Presentations
> >>>>> of draft material are welcome at the meeting.
> >>>>>
> >>>>> Most likely we will also have time to discuss one or two specific
> >>>>> technical topics at the meeting. Proposals for such topics as well
> >>>>> as presentations are invited.
> >>>>>
> >>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday)
> >>>>> we
> >>> would
> >>>>> like to have your input by Sunday 2012-10-21.
> >>>>>
> >>>>> B=C3=B6rje, Dave & Dirk
> >>>>>
> >>>>>
> >>>>> ICN RG Wiki:
> >>>>>
> >>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>



--=20
DY

--20cf300fb3bd87c30804ccc1c205
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>The ultimate criteria might be the level of incentiv=
e for end users, content providers, and ISP&#39;s like:</div><div><br></div=
><div>=C2=A0 1. Are there any service differences perceived by the end user=
s?</div>

<div>=C2=A0 =C2=A0 =C2=A0 o Any advantage/benefit perceived by the users?</=
div><div>=C2=A0 =C2=A0 =C2=A0 o Any strong incentive for end users to choos=
e ICN against iCDN?</div><div><br></div><div>=C2=A0 2. Are there any differ=
ences perceived by the content providers?</div>

<div>=C2=A0 =C2=A0 =C2=A0 o Any strong incentive for content providers to c=
hoose ICN against iCDN?</div><div><br></div><div>=C2=A0 3. Are there any in=
centive for the ISP&#39;s to provide the same content delivery service by c=
hoosing the infrastructure of ICN against iCDN?</div>

<div><br></div><div>If the differential incentives are not strong enough, i=
CDN will only be a pastime game.<br><br><div class=3D"gmail_quote">On Wed, =
Oct 24, 2012 at 4:39 AM, Bengt Ahlgren <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:bengta@sics.se" target=3D"_blank">bengta@sics.se</a>&gt;</span> wrote:<=
br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I agree with Nacho, but would like to add an=
 angle to this discussion!<br>
<br>
CDN, IMO, is more a business model than a particular set of protocols<br>
and services. =C2=A0CDN operators agree to deliver the content of particula=
r<br>
publishers for a fee at some level of service. =C2=A0Whether this is done o=
n<br>
an IP network or something else is not really important.<br>
<br>
ICN is a different set of protocols and services compared to IP, but not<br=
>
really a specific business model, although it may change the business<br>
playing field somewhat. =C2=A0So, even though we can argue that ICN is good=
<br>
for content distribution, I don&#39;t think the CDN business becomes<br>
redundant. =C2=A0There will still be content publishers that want to make<b=
r>
sure that their content is delivered at some known level of service to<br>
their customers. =C2=A0The &quot;normal&quot; ICN caching simply correspond=
s to current<br>
best-effort IP packet forwarding, with similar non-guarantee of service.<br=
>
<br>
Having said that, when the CDN folks now are starting to define<br>
particular protocols and interfaces (e.g., CDNI), they are working on<br>
stuff that touches ICN, but for supporting their particular purpose (the<br=
>
CDN business model).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Bengt<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&lt;<a href=3D"mailto:Ignacio.Solis@parc.com">Ignacio.Solis@parc.com</a>&gt=
; writes:<br>
<br>
&gt; Hi Brian.<br>
&gt;<br>
&gt; You are right that for a subset of cases it seems like ICN is just<br>
&gt; CDN, but that would be missing a lot of the picture.<br>
&gt;<br>
&gt; First, can you describe what the properties of native ICN and<br>
&gt; non-native ICN are? =C2=A0Is there no &quot;router caching&quot; in no=
n-native ICN?<br>
&gt;<br>
&gt; A few of the things that don&#39;t seem to fit into traditional CDNs (=
with<br>
&gt; my limited knowledge of state-of-the art CDNs) are:<br>
&gt;<br>
&gt; - Peer-to-peer. =C2=A0How can CDNs help two nodes communicate without<=
br>
&gt; infrastructure? =C2=A0If two nodes meet in the field (such as in the D=
ARPA<br>
&gt; CBMEN program, or two phones on a plane or tunnel or ship), how can<br=
>
&gt; CDNs help them exchange information?<br>
&gt;<br>
&gt; - Security. How can CDNs ensure the provenance of the data?<br>
&gt;<br>
&gt; - Disruption tolerance. How can CDNs enable data-muling?<br>
&gt;<br>
&gt; - Flow control. How can you change the way we do flow-control using CD=
Ns?<br>
&gt;<br>
&gt; - Lone hit. How can CDNs help distribute data that was previously<br>
&gt; unknown to the CDN. For example, from a random webpage.<br>
&gt;<br>
&gt;<br>
&gt; Granted, some of those are somewhat possible using CDNs. Some of those=
<br>
&gt; are possible with a little bit of work on CDNs and some are possible<b=
r>
&gt; with a lot of work.<br>
&gt;<br>
&gt; Everything is possible.<br>
&gt;<br>
&gt; But, we&#39;re going to get to a point where we&#39;re changing so muc=
h that<br>
&gt; what we started with is unrecognizable. =C2=A0Starting with CDNs is<br=
>
&gt; limiting what we can do and how we do it. =C2=A0The model many ICNs ta=
ke is<br>
&gt; a clean slate one. And as far as possible, we try to learn the lessons=
<br>
&gt; of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,<br=
>
&gt; OSPFs, etc.<br>
&gt;<br>
&gt; Caching at the router level is one of the many potentially beneficial<=
br>
&gt; (but not-required) characteristics of ICNs.<br>
&gt;<br>
&gt; If we talk about a specific ICN architecture (like CCN) we can talk<br=
>
&gt; about specific advantages and disadvantages, tradeoffs made, work done=
<br>
&gt; so far, work planned and work yet to be done.<br>
&gt;<br>
&gt; Nacho<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Nacho (Ignacio) Solis<br>
&gt; Senior Research Scientist<br>
&gt; Palo Alto Research Center (PARC)<br>
&gt; <a href=3D"tel:%2B1%28650%29%20812-4458" value=3D"+16508124458">+1(650=
) 812-4458</a><br>
&gt; <a href=3D"mailto:Ignacio.Solis@parc.com">Ignacio.Solis@parc.com</a><b=
r>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Oct 18, 2012, at 2:54 PM, &quot;Field, Brian&quot; &lt;<a href=3D"m=
ailto:Brian_Field@cable.comcast.com">Brian_Field@cable.comcast.com</a>&gt;<=
br>
&gt; =C2=A0wrote:<br>
&gt;<br>
&gt;&gt; Does anyone (beside me) think that a CDN effectively is already do=
ing &quot;ICN&quot; but tunneled over an HTTP infrastructure (via HTTP/TCP/=
IP). =C2=A0 I think of CDN and native ICN (where the router is caching and =
forwarding at the ICN level) nearly identical forwarding paradigms just ope=
rating at different levels in the stack.<br>


&gt;&gt;<br>
&gt;&gt; There&#39;s work in standardizing the intra-CDN =C2=A0and inter-CD=
N control plan (in CDN-I and elsewhere). =C2=A0IMO, it would be useful if w=
e had the same control protocol operating in both the CDN and ICN domains a=
nd the &quot;transition&quot; was just changing the layer at which forwardi=
ng occurred.<br>


&gt;&gt;<br>
&gt;&gt; Brian<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: <a href=3D"mailto:icnrg-bounces@irtf.org">icnrg-bounces@irtf=
.org</a> [mailto:<a href=3D"mailto:icnrg-bounces@irtf.org">icnrg-bounces@ir=
tf.org</a>] On Behalf Of Will Liu (Shucheng)<br>
&gt;&gt; Sent: Thursday, October 18, 2012 3:08 AM<br>
&gt;&gt; To: B=C3=B6rje Ohlman; Seung-Ik Lee<br>
&gt;&gt; Cc: =E4=BB=BB=E5=A9=A7; icnrg; Jianping Wang<br>
&gt;&gt; Subject: Re: [icnrg] Announcing ICNRG @ IETF 85<br>
&gt;&gt;<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic wh=
ich ISPs will definitely be interested in. Here are our 2-cents.<br>
&gt;&gt;<br>
&gt;&gt; The evolvement of ICN may take the following three implementations=
: integrated with IP, over IP and over SDN. These strategies all can help t=
he ISP shift from the traditional IP to ICN. The only question is which one=
 is the best choice for large scale deployment?<br>


&gt;&gt;<br>
&gt;&gt; Integrated with IP strategy extends the existing IP protocol (IP o=
ption) to support ICN. The updated IP router, called content router, will d=
eal with such special packets. However, many routers with no support of suc=
h extension may directly drop the packets with an unknown IP option.<br>


&gt;&gt;<br>
&gt;&gt; ICN over IP strategy uses an overlay approach. Content-related ope=
ration will be performed on the high layer and Content-related information =
will be sent through a tunnel. Due to the limited knowledge of physical top=
ology and unnecessary packet encapsulation/disconsolation, the efficiency m=
ay be limited.<br>


&gt;&gt;<br>
&gt;&gt; ICN over SDN strategy exploits SDN controller to perform content-r=
elated operation. However, SDN itself is an ongoing approach and is typical=
ly used in a local domain. The performance in a large scale deployment is u=
nknown.<br>


&gt;&gt;<br>
&gt;&gt; Will<br>
&gt;&gt;<br>
&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt; From: <a href=3D"mailto:icnrg-bounces@irtf.org">icnrg-bounces@=
irtf.org</a> [mailto:<a href=3D"mailto:icnrg-bounces@irtf.org">icnrg-bounce=
s@irtf.org</a>] On Behalf<br>
&gt;&gt;&gt; Of B?rje Ohlman<br>
&gt;&gt;&gt; Sent: Thursday, October 18, 2012 10:55 AM<br>
&gt;&gt;&gt; To: Seung-Ik Lee<br>
&gt;&gt;&gt; Cc: icnrg<br>
&gt;&gt;&gt; Subject: Re: [icnrg] Announcing ICNRG @ IETF 85<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Dear Seung-Ik,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think you bring up a very good point. I agree that deploymen=
t and<br>
&gt;&gt;&gt; migration issues are very important. I also agree that they do=
n&#39;t seem<br>
&gt;&gt;&gt; like a good fit for any of the currently proposed ICNRG docume=
nts.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The three documents listed as current work items are in no way=
 set in<br>
&gt;&gt;&gt; stone, they should just be seen as a starting point for our wo=
rk. If<br>
&gt;&gt;&gt; you would like to propose the RG that we should start working =
on a<br>
&gt;&gt;&gt; deployment document you are most welcome to do so, that will m=
ost<br>
&gt;&gt;&gt; certainly be in scope for our discussion in Atlanta.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; As a general comment I also like to mention that we as an RG a=
re not<br>
&gt;&gt;&gt; bound by all the rules that apply to IETF WGs, e.g. we are fre=
e to<br>
&gt;&gt;&gt; discuss late contributions produced after the IETF draft deadl=
ines. So<br>
&gt;&gt;&gt; if people find the time to write up some material for the ICNR=
G after<br>
&gt;&gt;&gt; the IETF drafts are done they are welcome to announce it to th=
e ICNRG<br>
&gt;&gt;&gt; mailing list. If the group agrees we are free to discuss also =
such<br>
&gt;&gt;&gt; material at our meeting,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =C2=A0 =C2=A0 B=C3=B6rje<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; 18 okt 2012 kl. 03:56 skrev &quot;Seung-Ik Lee&quot; &lt;<a hr=
ef=3D"mailto:seungiklee@etri.re.kr">seungiklee@etri.re.kr</a>&gt;:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Dear icnrg colleagues,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Regarding the RG documents, don&#39;t we touch any issues =
on ICN<br>
&gt;&gt;&gt; deployments?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; As we have seen in the presentation by ZTE in Vancouver, I=
SPs are<br>
&gt;&gt;&gt;&gt; interested in the short-term approaches to ICN.<br>
&gt;&gt;&gt;&gt; Though the traditional ICN approaches (such as CCN/NDN) ha=
ve<br>
&gt;&gt;&gt;&gt; provided ISPs a ladder out of dumb-pipes, ISPs may have di=
fficulties<br>
&gt;&gt;&gt;&gt; on clean-slate approaches of ICN.<br>
&gt;&gt;&gt;&gt; IMHO, based on our surveys on ISP R&amp;D approaches to IC=
N, Korean ISPs<br>
&gt;&gt;&gt;&gt; are in the similar situation.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In this motivation, I have interests in ICN deployment str=
ategies<br>
&gt;&gt;&gt;&gt; (such as ICN over IP or ICN over SDN as short-term approac=
hes) but<br>
&gt;&gt;&gt;&gt; no idea which RG document would cover the deployment issue=
s, even<br>
&gt;&gt;&gt;&gt; whether icnrg will cover the deployment issue or not.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2012/10/8 B=C3=B6rje Ohlman &lt;<a href=3D"mailto:Borje.Oh=
lman@ericsson.com">Borje.Ohlman@ericsson.com</a>&gt;:<br>
&gt;&gt;&gt;&gt;&gt; The next ICNRG will be held at =C2=A0IETF 85, Atlanta,=
 Georgia, USA,<br>
&gt;&gt;&gt; November<br>
&gt;&gt;&gt;&gt;&gt; 4-9, 2012<br>
&gt;&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 * Meeting time: WEDNESDAY 13.00-15.40 (p=
rel)<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The main discussion at the meeting will be the three d=
ocuments that<br>
&gt;&gt;&gt;&gt;&gt; the<br>
&gt;&gt;&gt; RG<br>
&gt;&gt;&gt;&gt;&gt; has set out to produce.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; ICN Survey document<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; A document that provides a survey of different approac=
hes and<br>
&gt;&gt;&gt; techniques<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; ICN Problem statement<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; A document that describes the ICN problem statement, t=
he main<br>
&gt;&gt;&gt; concepts and<br>
&gt;&gt;&gt;&gt;&gt; research challenges in depth.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; ICN Baseline Scenarios<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; A document that defines reference baseline scenarios t=
o enable<br>
&gt;&gt;&gt; performance<br>
&gt;&gt;&gt;&gt;&gt; comparisons between different approaches.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; People are encouraged to present their views on what t=
hey think<br>
&gt;&gt;&gt;&gt;&gt; should<br>
&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt; the contents of these documents. Early contributions (=
in bullet<br>
&gt;&gt;&gt;&gt;&gt; form or as draft text) are welcome both on the mailing=
 list and the wiki.<br>
&gt;&gt;&gt; Presentations<br>
&gt;&gt;&gt;&gt;&gt; of draft material are welcome at the meeting.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Most likely we will also have time to discuss one or t=
wo specific<br>
&gt;&gt;&gt;&gt;&gt; technical topics at the meeting. Proposals for such to=
pics as well<br>
&gt;&gt;&gt;&gt;&gt; as presentations are invited.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; As we are expected to publish our agenda by 2012-10-24=
 (Wednesday)<br>
&gt;&gt;&gt;&gt;&gt; we<br>
&gt;&gt;&gt; would<br>
&gt;&gt;&gt;&gt;&gt; like to have your input by Sunday 2012-10-21.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; B=C3=B6rje, Dave &amp; Dirk<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; ICN RG Wiki:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"http://trac.tools.ietf.org/group/irtf/trac/=
wiki/icnrg" target=3D"_blank">http://trac.tools.ietf.org/group/irtf/trac/wi=
ki/icnrg</a><br>
_______________________________________________<br>
icnrg mailing list<br>
<a href=3D"mailto:icnrg@irtf.org">icnrg@irtf.org</a><br>
<a href=3D"https://www.irtf.org/mailman/listinfo/icnrg" target=3D"_blank">h=
ttps://www.irtf.org/mailman/listinfo/icnrg</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
DY<br>
</div>

--20cf300fb3bd87c30804ccc1c205--

From borje.ohlman@ericsson.com  Tue Oct 23 22:32:23 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34CFB21F8D29 for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 22:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnbqflnWxYiN for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2012 22:32:22 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id CC2BB21F8D2B for <icnrg@irtf.org>; Tue, 23 Oct 2012 22:32:21 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-da-50877d633fa6
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id E9.FD.17130.36D77805; Wed, 24 Oct 2012 07:32:20 +0200 (CEST)
Received: from ESESSHC013.ericsson.se (153.88.183.57) by esessmw0237.eemea.ericsson.se (153.88.115.90) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 24 Oct 2012 07:32:19 +0200
Received: from ESESSMB107.ericsson.se ([169.254.7.89]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0318.001; Wed, 24 Oct 2012 07:32:19 +0200
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: AQHNsajua6NfubUpn0CSoOItbxeoBw==
Date: Wed, 24 Oct 2012 05:32:18 +0000
Message-ID: <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+JvrW5KbXuAwdINPBY7Z+9kslgw/y6T A5NHy5G3rB6TNx5mC2CK4rJJSc3JLEst0rdL4Mr4OXsHc8EsjoqHq08xNjCeZOti5OSQEDCR eDGznRXCFpO4cG89UJyLQ0jgFKPEjPb5LBDOTkaJy3NnM0E4ixklnl5fB9bCJuAo8f7pATBb RMBconHWKqB2Dg5mASmJ260VIGFhoJKvDeeYQcIiAk4Sa5qKIKr1JFZN2cUEYrMIqEosWTYB rJNXwF7i26likLCQQKjEne3Twe7kFAiTOLJ/EzOIzSggK/GlcTWYzSwgLvF57gMmiPsFJJbs Oc8MYYtKvHz8jxWiRk/ixtQpbBC2tsSyha/BangFBCVOznzCArFLTeL4h2PMExjFZyEZOwtJ +ywk7bOQtC9gZFnFKJybmJmTXm6ul1qUmVxcnJ+nV5y6iREYUQe3/DbYwbjpvtghRmkOFiVx Xj3V/f5CAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGI/Lcrq/uqZsVbQ1I3XOzz6fy7+5jh75 Ker66quUZO826SP/2C7NtzlWyN251l3a+VTnZa2M+vIy76wVN6RLeabGhL+vfMHSdETvKsMe 5s2OOrHufQ95qk87CrMuqIysdhCw+W/RJOXOFb4762/GlbU39wV18TQ4XQr4r63dtjMkzWtj qa+3EktxRqKhFnNRcSIA6BjW0nYCAAA=
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 05:32:23 -0000

Yes, it is a bit unfortunate. When we (the ICNRG chairs) gave feedback on t=
he initial schedule our meeting was on Wednesday morning, which looked alri=
ght, but then they moved the IRTF Open Meeting there end we were pushed to =
the afternoon.=20
If there is a lot of people having issues with the Wednesday afternoon slot=
 we could try to move the meeting to Monday or Tuesday. But moving meetings=
 forward  in the schedule is usually not a good idea as some people will no=
t note the change in time, and thus miss the meeting. Moving to Thursday or=
 Friday is unfortunately not an option as non of the chairs will be availab=
le those days.

       B=F6rje

23 okt 2012 kl. 14:52 skrev "Konstantinos Pentikousis" <k.pentikousis@huawe=
i.com>:

> Hi all,
>=20
> It seems that ICNRG overlaps with CDNi (1300-1430) and ALTO (1440-1540).
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From spis@intracom.com  Wed Oct 24 02:14:31 2012
Return-Path: <spis@intracom.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C95121F8570 for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 02:14:31 -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=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFNAIX-l+7fT for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 02:14:30 -0700 (PDT)
Received: from extmail.intranet.gr (extmail.intranet.gr [192.92.155.11]) by ietfa.amsl.com (Postfix) with ESMTP id DB47C21F8584 for <icnrg@irtf.org>; Wed, 24 Oct 2012 02:14:29 -0700 (PDT)
Received: from mailserv.intranet.gr (mailserv.intranet.GR [146.124.14.106]) by extmail.intranet.gr (8.14.5/8.14.5) with ESMTP id q9O9EKGb005280 for <icnrg@irtf.org>; Wed, 24 Oct 2012 12:14:21 +0300 (EEST)
Received: from mailserv.intranet.gr (localhost [127.0.0.1]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id q9O9EKm4017493 for <icnrg@irtf.org>; Wed, 24 Oct 2012 12:14:21 +0300 (EEST)
Received: from iris.intranet.gr (iris.intranet.GR [146.124.80.178]) by mailserv.intranet.gr (8.13.6/8.13.1) with ESMTP id q9O9ECSM017433; Wed, 24 Oct 2012 12:14:12 +0300 (EEST)
Received: from [10.124.82.96] ([10.124.82.96] verified) by iris.intranet.gr (CommuniGate Pro SMTP 5.3.13) with ESMTP id 50541268; Wed, 24 Oct 2012 12:14:11 +0300
Message-ID: <5087B162.9040305@intracom.com>
Date: Wed, 24 Oct 2012 12:14:10 +0300
From: Spiros Spirou <spis@intracom.com>
Organization: Intracom Telecom
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Bengt Ahlgren <bengta@sics.se>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se>
In-Reply-To: <uh7zk3dq8oy.fsf@P142.sics.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Ignacio.Solis@parc.com, icnrg@irtf.org, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: spis@intracom.com
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 09:14:31 -0000

Hi Bengt!

If ICN does not provide any sort of better-than-best-effort delivery, 
then it seems (to me at least) that neither ISPs nor content providers 
have any significant incentive to adopt ICN. They can simply stick with 
the entrenched CDN technology and business model where all stekeholders 
(end-users, ISPs, CDN operators, and content providers/owners) seem to 
be happy enough.

If, on the other hand, ICN does provide guarantees in delivery, then ICN 
and CDN seem likely to become competitors, as they would be offering a 
very similar service. The question for me is why would ISPs risk losing 
existing revenue from CDN operators in favor of capital expenditure for 
deploying ICN? There's of course the hope that content providers would 
be lured away from CDN, but this seems realistic only if ICN is cheaper 
or somehow better than CDN.

Spiros

On 23/10/2012 10:39 ÎĽÎĽ, Bengt Ahlgren wrote:
> I agree with Nacho, but would like to add an angle to this discussion!
>
> CDN, IMO, is more a business model than a particular set of protocols
> and services.  CDN operators agree to deliver the content of particular
> publishers for a fee at some level of service.  Whether this is done on
> an IP network or something else is not really important.
>
> ICN is a different set of protocols and services compared to IP, but not
> really a specific business model, although it may change the business
> playing field somewhat.  So, even though we can argue that ICN is good
> for content distribution, I don't think the CDN business becomes
> redundant.  There will still be content publishers that want to make
> sure that their content is delivered at some known level of service to
> their customers.  The "normal" ICN caching simply corresponds to current
> best-effort IP packet forwarding, with similar non-guarantee of service.
>
> Having said that, when the CDN folks now are starting to define
> particular protocols and interfaces (e.g., CDNI), they are working on
> stuff that touches ICN, but for supporting their particular purpose (the
> CDN business model).
>
> Bengt
>
> <Ignacio.Solis@parc.com> writes:
>
>> Hi Brian.
>>
>> You are right that for a subset of cases it seems like ICN is just
>> CDN, but that would be missing a lot of the picture.
>>
>> First, can you describe what the properties of native ICN and
>> non-native ICN are?  Is there no "router caching" in non-native ICN?
>>
>> A few of the things that don't seem to fit into traditional CDNs (with
>> my limited knowledge of state-of-the art CDNs) are:
>>
>> - Peer-to-peer.  How can CDNs help two nodes communicate without
>> infrastructure?  If two nodes meet in the field (such as in the DARPA
>> CBMEN program, or two phones on a plane or tunnel or ship), how can
>> CDNs help them exchange information?
>>
>> - Security. How can CDNs ensure the provenance of the data?
>>
>> - Disruption tolerance. How can CDNs enable data-muling?
>>
>> - Flow control. How can you change the way we do flow-control using CDNs?
>>
>> - Lone hit. How can CDNs help distribute data that was previously
>> unknown to the CDN. For example, from a random webpage.
>>
>>
>> Granted, some of those are somewhat possible using CDNs. Some of those
>> are possible with a little bit of work on CDNs and some are possible
>> with a lot of work.
>>
>> Everything is possible.
>>
>> But, we're going to get to a point where we're changing so much that
>> what we started with is unrecognizable.  Starting with CDNs is
>> limiting what we can do and how we do it.  The model many ICNs take is
>> a clean slate one. And as far as possible, we try to learn the lessons
>> of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,
>> OSPFs, etc.
>>
>> Caching at the router level is one of the many potentially beneficial
>> (but not-required) characteristics of ICNs.
>>
>> If we talk about a specific ICN architecture (like CCN) we can talk
>> about specific advantages and disadvantages, tradeoffs made, work done
>> so far, work planned and work yet to be done.
>>
>> Nacho
>>
>>
>>
>> --
>> Nacho (Ignacio) Solis
>> Senior Research Scientist
>> Palo Alto Research Center (PARC)
>> +1(650) 812-4458
>> Ignacio.Solis@parc.com
>>
>>
>>
>>
>> On Oct 18, 2012, at 2:54 PM, "Field, Brian" <Brian_Field@cable.comcast.com>
>>   wrote:
>>
>>> Does anyone (beside me) think that a CDN effectively is already doing "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).   I think of CDN and native ICN (where the router is caching and forwarding at the ICN level) nearly identical forwarding paradigms just operating at different levels in the stack.
>>>
>>> There's work in standardizing the intra-CDN  and inter-CDN control plan (in CDN-I and elsewhere).  IMO, it would be useful if we had the same control protocol operating in both the CDN and ICN domains and the "transition" was just changing the layer at which forwarding occurred.
>>>
>>> Brian
>>>
>>>
>>> -----Original Message-----
>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of Will Liu (Shucheng)
>>> Sent: Thursday, October 18, 2012 3:08 AM
>>> To: BÎ“Â¶rje Ohlman; Seung-Ik Lee
>>> Cc: Î´Â»Â»ÎµÂ©Â§; icnrg; Jianping Wang
>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>
>>> Hi,
>>>
>>> My group are also interested in ICN deployment and have done some survey on this matter. The discussion on ICN deployment is a great topic which ISPs will definitely be interested in. Here are our 2-cents.
>>>
>>> The evolvement of ICN may take the following three implementations: integrated with IP, over IP and over SDN. These strategies all can help the ISP shift from the traditional IP to ICN. The only question is which one is the best choice for large scale deployment?
>>>
>>> Integrated with IP strategy extends the existing IP protocol (IP option) to support ICN. The updated IP router, called content router, will deal with such special packets. However, many routers with no support of such extension may directly drop the packets with an unknown IP option.
>>>
>>> ICN over IP strategy uses an overlay approach. Content-related operation will be performed on the high layer and Content-related information will be sent through a tunnel. Due to the limited knowledge of physical topology and unnecessary packet encapsulation/disconsolation, the efficiency may be limited.
>>>
>>> ICN over SDN strategy exploits SDN controller to perform content-related operation. However, SDN itself is an ongoing approach and is typically used in a local domain. The performance in a large scale deployment is unknown.
>>>
>>> Will
>>>
>>>> -----Original Message-----
>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf
>>>> Of B?rje Ohlman
>>>> Sent: Thursday, October 18, 2012 10:55 AM
>>>> To: Seung-Ik Lee
>>>> Cc: icnrg
>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>
>>>> Dear Seung-Ik,
>>>>
>>>> I think you bring up a very good point. I agree that deployment and
>>>> migration issues are very important. I also agree that they don't seem
>>>> like a good fit for any of the currently proposed ICNRG documents.
>>>>
>>>> The three documents listed as current work items are in no way set in
>>>> stone, they should just be seen as a starting point for our work. If
>>>> you would like to propose the RG that we should start working on a
>>>> deployment document you are most welcome to do so, that will most
>>>> certainly be in scope for our discussion in Atlanta.
>>>>
>>>> As a general comment I also like to mention that we as an RG are not
>>>> bound by all the rules that apply to IETF WGs, e.g. we are free to
>>>> discuss late contributions produced after the IETF draft deadlines. So
>>>> if people find the time to write up some material for the ICNRG after
>>>> the IETF drafts are done they are welcome to announce it to the ICNRG
>>>> mailing list. If the group agrees we are free to discuss also such
>>>> material at our meeting,
>>>>
>>>>      BÎ“Â¶rje
>>>>
>>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" <seungiklee@etri.re.kr>:
>>>>
>>>>> Dear icnrg colleagues,
>>>>>
>>>>> Regarding the RG documents, don't we touch any issues on ICN
>>>> deployments?
>>>>>
>>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>>>> interested in the short-term approaches to ICN.
>>>>> Though the traditional ICN approaches (such as CCN/NDN) have
>>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have difficulties
>>>>> on clean-slate approaches of ICN.
>>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean ISPs
>>>>> are in the similar situation.
>>>>>
>>>>> In this motivation, I have interests in ICN deployment strategies
>>>>> (such as ICN over IP or ICN over SDN as short-term approaches) but
>>>>> no idea which RG document would cover the deployment issues, even
>>>>> whether icnrg will cover the deployment issue or not.
>>>>>
>>>>>
>>>>>
>>>>> 2012/10/8 BÎ“Â¶rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>>> November
>>>>>> 4-9, 2012
>>>>>>      * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>>
>>>>>> The main discussion at the meeting will be the three documents that
>>>>>> the
>>>> RG
>>>>>> has set out to produce.
>>>>>>
>>>>>> ICN Survey document
>>>>>>
>>>>>> A document that provides a survey of different approaches and
>>>> techniques
>>>>>>
>>>>>> ICN Problem statement
>>>>>>
>>>>>> A document that describes the ICN problem statement, the main
>>>> concepts and
>>>>>> research challenges in depth.
>>>>>>
>>>>>> ICN Baseline Scenarios
>>>>>>
>>>>>> A document that defines reference baseline scenarios to enable
>>>> performance
>>>>>> comparisons between different approaches.
>>>>>>
>>>>>> People are encouraged to present their views on what they think
>>>>>> should
>>>> be
>>>>>> the contents of these documents. Early contributions (in bullet
>>>>>> form or as draft text) are welcome both on the mailing list and the wiki.
>>>> Presentations
>>>>>> of draft material are welcome at the meeting.
>>>>>>
>>>>>> Most likely we will also have time to discuss one or two specific
>>>>>> technical topics at the meeting. Proposals for such topics as well
>>>>>> as presentations are invited.
>>>>>>
>>>>>> As we are expected to publish our agenda by 2012-10-24 (Wednesday)
>>>>>> we
>>>> would
>>>>>> like to have your input by Sunday 2012-10-21.
>>>>>>
>>>>>> BÎ“Â¶rje, Dave & Dirk
>>>>>>
>>>>>>
>>>>>> ICN RG Wiki:
>>>>>>
>>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From dlake@cisco.com  Wed Oct 24 03:13:11 2012
Return-Path: <dlake@cisco.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D984A21F8B76 for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 03:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPXG9IRbjsBE for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 03:13:10 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8991821F893F for <icnrg@irtf.org>; Wed, 24 Oct 2012 03:13:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16348; q=dns/txt; s=iport; t=1351073582; x=1352283182; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=NqgMy5dPNmOKvgiJO/JEFo2rjYQ+PDw3Jb5c/WPIEFY=; b=aKkURp2zTz/cFnU6oRh6Pc2eyAyDAQ2IrwurwCeE9eTuPv/EhAJLuKf8 /FzWJA/Q6srt3Fxgyl9L0pxBWh5DEN9uXNlFNitco3Vq1mhoOEbvCmgPR cOHDEgEutZ1/DJ8L5jyKGdJjdcjR2OSrV6f7YLnS9VeqSq1wd3SeO7mbP k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAJ69h1CtJXHA/2dsb2JhbABBA4YUum56gQiCHgEBAQMBAQEBDwEFCxE6CwwEAgEGAhEBAwEBAQICBh0DAgICJQsUAQIGCAIEAQ0FCBqHXAYLmxKNIZJdgSCKQBSDL4IWMmADlwqNN4Frgm+BWiAe
X-IronPort-AV: E=Sophos;i="4.80,639,1344211200"; d="scan'208";a="134811239"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 24 Oct 2012 10:13:01 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id q9OAD10t000863 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Oct 2012 10:13:01 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.239]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.001; Wed, 24 Oct 2012 05:13:01 -0500
From: "David Lake (dlake)" <dlake@cisco.com>
To: "spis@intracom.com" <spis@intracom.com>, Bengt Ahlgren <bengta@sics.se>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNsVaNOYTb8FHbREesns7kHfbO45fIgP4A//+47JA=
Date: Wed, 24 Oct 2012 10:13:00 +0000
Message-ID: <3512BB31280C39448A9880F61DD54CEB1B3961@xmb-aln-x09.cisco.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com>
In-Reply-To: <5087B162.9040305@intracom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.89.167]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19302.000
x-tm-as-result: No--37.361100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "Ignacio.Solis@parc.com" <Ignacio.Solis@parc.com>, "icnrg@irtf.org" <icnrg@irtf.org>, "Brian_Field@cable.comcast.com" <Brian_Field@cable.comcast.com>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 10:13:12 -0000

U3Bpcm9zDQoNCkkgY29tcGxldGVseSBhZ3JlZSwgYnV0IEkgc3VzcGVjdCB3ZSB3aWxsIG5lZWQg
c29tZSBraW5kIG9mIG1lcmdpbmcgb2YgSUNOIGFuZCBTRE4gdG8gYWNoaWV2ZSB0aGF0LiANCg0K
VGhlIGNvbW1lbnRzIGZyb20gYSBmZXcgU1BzIGF0IHRoZSBXb3JsZCBTRE4vT3BlbmZsb3cgY29u
Z3Jlc3MgdGhpcyB3ZWVrIGluIEZyYW5rZnVydCB3YXMgbW9zdCBlbmxpZ2h0ZW5pbmcgLSB5ZXMs
IHRoZXJlIGlzIHJldmVudWUgZnJvbSB0aGUgQ0ROIHByb3ZpZGVycywgYnV0IHRoZXJlIGlzIGFs
c28gc3Vic3RhbnRpYWwgb3BlcmF0aW9uYWwgY29zdCBhbmQgZXhjZXNzaXZlIGNvbXBsZXhpdHkg
cGx1cyBzdWItb3B0aW1hbCB1c2Ugb2YgdW5kZXJseWluZyBuZXR3b3JrIHJlc291cmNlcy4NCg0K
T25lIGFzcGVjdCB0aGF0IHdhcyBzcGVjaWZpY2FsbHkgY2FsbGVkLW91dCB3YXMgdGhlIE9UVCBD
RE4gbmV0d29yay4gICBZb3VyIHBocmFzZSAiIHNlZW0gdG8gYmUgaGFwcHkgZW5vdWdoIiBkaWQg
bm90IGFwcGx5ICEhISENCg0KUmVnYXJkcw0KDQpEYXZpZA0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogaWNucmctYm91bmNlc0BpcnRmLm9yZyBbbWFpbHRvOmljbnJnLWJvdW5j
ZXNAaXJ0Zi5vcmddIE9uIEJlaGFsZiBPZiBTcGlyb3MgU3Bpcm91DQpTZW50OiBXZWRuZXNkYXks
IE9jdG9iZXIgMjQsIDIwMTIgMTE6MTQgQU0NClRvOiBCZW5ndCBBaGxncmVuDQpDYzogSWduYWNp
by5Tb2xpc0BwYXJjLmNvbTsgaWNucmdAaXJ0Zi5vcmc7IEJyaWFuX0ZpZWxkQGNhYmxlLmNvbWNh
c3QuY29tDQpTdWJqZWN0OiBSZTogW2ljbnJnXSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0K
DQpIaSBCZW5ndCENCg0KSWYgSUNOIGRvZXMgbm90IHByb3ZpZGUgYW55IHNvcnQgb2YgYmV0dGVy
LXRoYW4tYmVzdC1lZmZvcnQgZGVsaXZlcnksIHRoZW4gaXQgc2VlbXMgKHRvIG1lIGF0IGxlYXN0
KSB0aGF0IG5laXRoZXIgSVNQcyBub3IgY29udGVudCBwcm92aWRlcnMgaGF2ZSBhbnkgc2lnbmlm
aWNhbnQgaW5jZW50aXZlIHRvIGFkb3B0IElDTi4gVGhleSBjYW4gc2ltcGx5IHN0aWNrIHdpdGgg
dGhlIGVudHJlbmNoZWQgQ0ROIHRlY2hub2xvZ3kgYW5kIGJ1c2luZXNzIG1vZGVsIHdoZXJlIGFs
bCBzdGVrZWhvbGRlcnMgKGVuZC11c2VycywgSVNQcywgQ0ROIG9wZXJhdG9ycywgYW5kIGNvbnRl
bnQgcHJvdmlkZXJzL293bmVycykgc2VlbSB0byBiZSBoYXBweSBlbm91Z2guDQoNCklmLCBvbiB0
aGUgb3RoZXIgaGFuZCwgSUNOIGRvZXMgcHJvdmlkZSBndWFyYW50ZWVzIGluIGRlbGl2ZXJ5LCB0
aGVuIElDTiBhbmQgQ0ROIHNlZW0gbGlrZWx5IHRvIGJlY29tZSBjb21wZXRpdG9ycywgYXMgdGhl
eSB3b3VsZCBiZSBvZmZlcmluZyBhIHZlcnkgc2ltaWxhciBzZXJ2aWNlLiBUaGUgcXVlc3Rpb24g
Zm9yIG1lIGlzIHdoeSB3b3VsZCBJU1BzIHJpc2sgbG9zaW5nIGV4aXN0aW5nIHJldmVudWUgZnJv
bSBDRE4gb3BlcmF0b3JzIGluIGZhdm9yIG9mIGNhcGl0YWwgZXhwZW5kaXR1cmUgZm9yIGRlcGxv
eWluZyBJQ04/IFRoZXJlJ3Mgb2YgY291cnNlIHRoZSBob3BlIHRoYXQgY29udGVudCBwcm92aWRl
cnMgd291bGQgYmUgbHVyZWQgYXdheSBmcm9tIENETiwgYnV0IHRoaXMgc2VlbXMgcmVhbGlzdGlj
IG9ubHkgaWYgSUNOIGlzIGNoZWFwZXIgb3Igc29tZWhvdyBiZXR0ZXIgdGhhbiBDRE4uDQoNClNw
aXJvcw0KDQpPbiAyMy8xMC8yMDEyIDEwOjM5IM68zrwsIEJlbmd0IEFobGdyZW4gd3JvdGU6DQo+
IEkgYWdyZWUgd2l0aCBOYWNobywgYnV0IHdvdWxkIGxpa2UgdG8gYWRkIGFuIGFuZ2xlIHRvIHRo
aXMgZGlzY3Vzc2lvbiENCj4NCj4gQ0ROLCBJTU8sIGlzIG1vcmUgYSBidXNpbmVzcyBtb2RlbCB0
aGFuIGEgcGFydGljdWxhciBzZXQgb2YgcHJvdG9jb2xzIA0KPiBhbmQgc2VydmljZXMuICBDRE4g
b3BlcmF0b3JzIGFncmVlIHRvIGRlbGl2ZXIgdGhlIGNvbnRlbnQgb2YgDQo+IHBhcnRpY3VsYXIg
cHVibGlzaGVycyBmb3IgYSBmZWUgYXQgc29tZSBsZXZlbCBvZiBzZXJ2aWNlLiAgV2hldGhlciAN
Cj4gdGhpcyBpcyBkb25lIG9uIGFuIElQIG5ldHdvcmsgb3Igc29tZXRoaW5nIGVsc2UgaXMgbm90
IHJlYWxseSBpbXBvcnRhbnQuDQo+DQo+IElDTiBpcyBhIGRpZmZlcmVudCBzZXQgb2YgcHJvdG9j
b2xzIGFuZCBzZXJ2aWNlcyBjb21wYXJlZCB0byBJUCwgYnV0IA0KPiBub3QgcmVhbGx5IGEgc3Bl
Y2lmaWMgYnVzaW5lc3MgbW9kZWwsIGFsdGhvdWdoIGl0IG1heSBjaGFuZ2UgdGhlIA0KPiBidXNp
bmVzcyBwbGF5aW5nIGZpZWxkIHNvbWV3aGF0LiAgU28sIGV2ZW4gdGhvdWdoIHdlIGNhbiBhcmd1
ZSB0aGF0IA0KPiBJQ04gaXMgZ29vZCBmb3IgY29udGVudCBkaXN0cmlidXRpb24sIEkgZG9uJ3Qg
dGhpbmsgdGhlIENETiBidXNpbmVzcyANCj4gYmVjb21lcyByZWR1bmRhbnQuICBUaGVyZSB3aWxs
IHN0aWxsIGJlIGNvbnRlbnQgcHVibGlzaGVycyB0aGF0IHdhbnQgDQo+IHRvIG1ha2Ugc3VyZSB0
aGF0IHRoZWlyIGNvbnRlbnQgaXMgZGVsaXZlcmVkIGF0IHNvbWUga25vd24gbGV2ZWwgb2YgDQo+
IHNlcnZpY2UgdG8gdGhlaXIgY3VzdG9tZXJzLiAgVGhlICJub3JtYWwiIElDTiBjYWNoaW5nIHNp
bXBseSANCj4gY29ycmVzcG9uZHMgdG8gY3VycmVudCBiZXN0LWVmZm9ydCBJUCBwYWNrZXQgZm9y
d2FyZGluZywgd2l0aCBzaW1pbGFyIG5vbi1ndWFyYW50ZWUgb2Ygc2VydmljZS4NCj4NCj4gSGF2
aW5nIHNhaWQgdGhhdCwgd2hlbiB0aGUgQ0ROIGZvbGtzIG5vdyBhcmUgc3RhcnRpbmcgdG8gZGVm
aW5lIA0KPiBwYXJ0aWN1bGFyIHByb3RvY29scyBhbmQgaW50ZXJmYWNlcyAoZS5nLiwgQ0ROSSks
IHRoZXkgYXJlIHdvcmtpbmcgb24gDQo+IHN0dWZmIHRoYXQgdG91Y2hlcyBJQ04sIGJ1dCBmb3Ig
c3VwcG9ydGluZyB0aGVpciBwYXJ0aWN1bGFyIHB1cnBvc2UgDQo+ICh0aGUgQ0ROIGJ1c2luZXNz
IG1vZGVsKS4NCj4NCj4gQmVuZ3QNCj4NCj4gPElnbmFjaW8uU29saXNAcGFyYy5jb20+IHdyaXRl
czoNCj4NCj4+IEhpIEJyaWFuLg0KPj4NCj4+IFlvdSBhcmUgcmlnaHQgdGhhdCBmb3IgYSBzdWJz
ZXQgb2YgY2FzZXMgaXQgc2VlbXMgbGlrZSBJQ04gaXMganVzdCANCj4+IENETiwgYnV0IHRoYXQg
d291bGQgYmUgbWlzc2luZyBhIGxvdCBvZiB0aGUgcGljdHVyZS4NCj4+DQo+PiBGaXJzdCwgY2Fu
IHlvdSBkZXNjcmliZSB3aGF0IHRoZSBwcm9wZXJ0aWVzIG9mIG5hdGl2ZSBJQ04gYW5kIA0KPj4g
bm9uLW5hdGl2ZSBJQ04gYXJlPyAgSXMgdGhlcmUgbm8gInJvdXRlciBjYWNoaW5nIiBpbiBub24t
bmF0aXZlIElDTj8NCj4+DQo+PiBBIGZldyBvZiB0aGUgdGhpbmdzIHRoYXQgZG9uJ3Qgc2VlbSB0
byBmaXQgaW50byB0cmFkaXRpb25hbCBDRE5zIA0KPj4gKHdpdGggbXkgbGltaXRlZCBrbm93bGVk
Z2Ugb2Ygc3RhdGUtb2YtdGhlIGFydCBDRE5zKSBhcmU6DQo+Pg0KPj4gLSBQZWVyLXRvLXBlZXIu
ICBIb3cgY2FuIENETnMgaGVscCB0d28gbm9kZXMgY29tbXVuaWNhdGUgd2l0aG91dCANCj4+IGlu
ZnJhc3RydWN0dXJlPyAgSWYgdHdvIG5vZGVzIG1lZXQgaW4gdGhlIGZpZWxkIChzdWNoIGFzIGlu
IHRoZSBEQVJQQSANCj4+IENCTUVOIHByb2dyYW0sIG9yIHR3byBwaG9uZXMgb24gYSBwbGFuZSBv
ciB0dW5uZWwgb3Igc2hpcCksIGhvdyBjYW4gDQo+PiBDRE5zIGhlbHAgdGhlbSBleGNoYW5nZSBp
bmZvcm1hdGlvbj8NCj4+DQo+PiAtIFNlY3VyaXR5LiBIb3cgY2FuIENETnMgZW5zdXJlIHRoZSBw
cm92ZW5hbmNlIG9mIHRoZSBkYXRhPw0KPj4NCj4+IC0gRGlzcnVwdGlvbiB0b2xlcmFuY2UuIEhv
dyBjYW4gQ0ROcyBlbmFibGUgZGF0YS1tdWxpbmc/DQo+Pg0KPj4gLSBGbG93IGNvbnRyb2wuIEhv
dyBjYW4geW91IGNoYW5nZSB0aGUgd2F5IHdlIGRvIGZsb3ctY29udHJvbCB1c2luZyBDRE5zPw0K
Pj4NCj4+IC0gTG9uZSBoaXQuIEhvdyBjYW4gQ0ROcyBoZWxwIGRpc3RyaWJ1dGUgZGF0YSB0aGF0
IHdhcyBwcmV2aW91c2x5IA0KPj4gdW5rbm93biB0byB0aGUgQ0ROLiBGb3IgZXhhbXBsZSwgZnJv
bSBhIHJhbmRvbSB3ZWJwYWdlLg0KPj4NCj4+DQo+PiBHcmFudGVkLCBzb21lIG9mIHRob3NlIGFy
ZSBzb21ld2hhdCBwb3NzaWJsZSB1c2luZyBDRE5zLiBTb21lIG9mIA0KPj4gdGhvc2UgYXJlIHBv
c3NpYmxlIHdpdGggYSBsaXR0bGUgYml0IG9mIHdvcmsgb24gQ0ROcyBhbmQgc29tZSBhcmUgDQo+
PiBwb3NzaWJsZSB3aXRoIGEgbG90IG9mIHdvcmsuDQo+Pg0KPj4gRXZlcnl0aGluZyBpcyBwb3Nz
aWJsZS4NCj4+DQo+PiBCdXQsIHdlJ3JlIGdvaW5nIHRvIGdldCB0byBhIHBvaW50IHdoZXJlIHdl
J3JlIGNoYW5naW5nIHNvIG11Y2ggdGhhdCANCj4+IHdoYXQgd2Ugc3RhcnRlZCB3aXRoIGlzIHVu
cmVjb2duaXphYmxlLiAgU3RhcnRpbmcgd2l0aCBDRE5zIGlzIA0KPj4gbGltaXRpbmcgd2hhdCB3
ZSBjYW4gZG8gYW5kIGhvdyB3ZSBkbyBpdC4gIFRoZSBtb2RlbCBtYW55IElDTnMgdGFrZSANCj4+
IGlzIGEgY2xlYW4gc2xhdGUgb25lLiBBbmQgYXMgZmFyIGFzIHBvc3NpYmxlLCB3ZSB0cnkgdG8g
bGVhcm4gdGhlIA0KPj4gbGVzc29ucyBvZiBDRE5zLCBEVE5zLCBJUHMsIEdudXRlbGxhcywgTXVs
dGljYXN0LCBSVFBzLCBJUFNlY3MsIFRDUHMsIA0KPj4gRE5TcywgT1NQRnMsIGV0Yy4NCj4+DQo+
PiBDYWNoaW5nIGF0IHRoZSByb3V0ZXIgbGV2ZWwgaXMgb25lIG9mIHRoZSBtYW55IHBvdGVudGlh
bGx5IGJlbmVmaWNpYWwgDQo+PiAoYnV0IG5vdC1yZXF1aXJlZCkgY2hhcmFjdGVyaXN0aWNzIG9m
IElDTnMuDQo+Pg0KPj4gSWYgd2UgdGFsayBhYm91dCBhIHNwZWNpZmljIElDTiBhcmNoaXRlY3R1
cmUgKGxpa2UgQ0NOKSB3ZSBjYW4gdGFsayANCj4+IGFib3V0IHNwZWNpZmljIGFkdmFudGFnZXMg
YW5kIGRpc2FkdmFudGFnZXMsIHRyYWRlb2ZmcyBtYWRlLCB3b3JrIA0KPj4gZG9uZSBzbyBmYXIs
IHdvcmsgcGxhbm5lZCBhbmQgd29yayB5ZXQgdG8gYmUgZG9uZS4NCj4+DQo+PiBOYWNobw0KPj4N
Cj4+DQo+Pg0KPj4gLS0NCj4+IE5hY2hvIChJZ25hY2lvKSBTb2xpcw0KPj4gU2VuaW9yIFJlc2Vh
cmNoIFNjaWVudGlzdA0KPj4gUGFsbyBBbHRvIFJlc2VhcmNoIENlbnRlciAoUEFSQykNCj4+ICsx
KDY1MCkgODEyLTQ0NTgNCj4+IElnbmFjaW8uU29saXNAcGFyYy5jb20NCj4+DQo+Pg0KPj4NCj4+
DQo+PiBPbiBPY3QgMTgsIDIwMTIsIGF0IDI6NTQgUE0sICJGaWVsZCwgQnJpYW4iIDxCcmlhbl9G
aWVsZEBjYWJsZS5jb21jYXN0LmNvbT4NCj4+ICAgd3JvdGU6DQo+Pg0KPj4+IERvZXMgYW55b25l
IChiZXNpZGUgbWUpIHRoaW5rIHRoYXQgYSBDRE4gZWZmZWN0aXZlbHkgaXMgYWxyZWFkeSBkb2lu
ZyAiSUNOIiBidXQgdHVubmVsZWQgb3ZlciBhbiBIVFRQIGluZnJhc3RydWN0dXJlICh2aWEgSFRU
UC9UQ1AvSVApLiAgIEkgdGhpbmsgb2YgQ0ROIGFuZCBuYXRpdmUgSUNOICh3aGVyZSB0aGUgcm91
dGVyIGlzIGNhY2hpbmcgYW5kIGZvcndhcmRpbmcgYXQgdGhlIElDTiBsZXZlbCkgbmVhcmx5IGlk
ZW50aWNhbCBmb3J3YXJkaW5nIHBhcmFkaWdtcyBqdXN0IG9wZXJhdGluZyBhdCBkaWZmZXJlbnQg
bGV2ZWxzIGluIHRoZSBzdGFjay4NCj4+Pg0KPj4+IFRoZXJlJ3Mgd29yayBpbiBzdGFuZGFyZGl6
aW5nIHRoZSBpbnRyYS1DRE4gIGFuZCBpbnRlci1DRE4gY29udHJvbCBwbGFuIChpbiBDRE4tSSBh
bmQgZWxzZXdoZXJlKS4gIElNTywgaXQgd291bGQgYmUgdXNlZnVsIGlmIHdlIGhhZCB0aGUgc2Ft
ZSBjb250cm9sIHByb3RvY29sIG9wZXJhdGluZyBpbiBib3RoIHRoZSBDRE4gYW5kIElDTiBkb21h
aW5zIGFuZCB0aGUgInRyYW5zaXRpb24iIHdhcyBqdXN0IGNoYW5naW5nIHRoZSBsYXllciBhdCB3
aGljaCBmb3J3YXJkaW5nIG9jY3VycmVkLg0KPj4+DQo+Pj4gQnJpYW4NCj4+Pg0KPj4+DQo+Pj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+PiBGcm9tOiBpY25yZy1ib3VuY2VzQGlydGYu
b3JnIFttYWlsdG86aWNucmctYm91bmNlc0BpcnRmLm9yZ10gT24gDQo+Pj4gQmVoYWxmIE9mIFdp
bGwgTGl1IChTaHVjaGVuZykNCj4+PiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxOCwgMjAxMiAz
OjA4IEFNDQo+Pj4gVG86IELOk8K2cmplIE9obG1hbjsgU2V1bmctSWsgTGVlDQo+Pj4gQ2M6IM60
wrvCu861wqnCpzsgaWNucmc7IEppYW5waW5nIFdhbmcNCj4+PiBTdWJqZWN0OiBSZTogW2ljbnJn
XSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0KPj4+DQo+Pj4gSGksDQo+Pj4NCj4+PiBNeSBn
cm91cCBhcmUgYWxzbyBpbnRlcmVzdGVkIGluIElDTiBkZXBsb3ltZW50IGFuZCBoYXZlIGRvbmUg
c29tZSBzdXJ2ZXkgb24gdGhpcyBtYXR0ZXIuIFRoZSBkaXNjdXNzaW9uIG9uIElDTiBkZXBsb3lt
ZW50IGlzIGEgZ3JlYXQgdG9waWMgd2hpY2ggSVNQcyB3aWxsIGRlZmluaXRlbHkgYmUgaW50ZXJl
c3RlZCBpbi4gSGVyZSBhcmUgb3VyIDItY2VudHMuDQo+Pj4NCj4+PiBUaGUgZXZvbHZlbWVudCBv
ZiBJQ04gbWF5IHRha2UgdGhlIGZvbGxvd2luZyB0aHJlZSBpbXBsZW1lbnRhdGlvbnM6IGludGVn
cmF0ZWQgd2l0aCBJUCwgb3ZlciBJUCBhbmQgb3ZlciBTRE4uIFRoZXNlIHN0cmF0ZWdpZXMgYWxs
IGNhbiBoZWxwIHRoZSBJU1Agc2hpZnQgZnJvbSB0aGUgdHJhZGl0aW9uYWwgSVAgdG8gSUNOLiBU
aGUgb25seSBxdWVzdGlvbiBpcyB3aGljaCBvbmUgaXMgdGhlIGJlc3QgY2hvaWNlIGZvciBsYXJn
ZSBzY2FsZSBkZXBsb3ltZW50Pw0KPj4+DQo+Pj4gSW50ZWdyYXRlZCB3aXRoIElQIHN0cmF0ZWd5
IGV4dGVuZHMgdGhlIGV4aXN0aW5nIElQIHByb3RvY29sIChJUCBvcHRpb24pIHRvIHN1cHBvcnQg
SUNOLiBUaGUgdXBkYXRlZCBJUCByb3V0ZXIsIGNhbGxlZCBjb250ZW50IHJvdXRlciwgd2lsbCBk
ZWFsIHdpdGggc3VjaCBzcGVjaWFsIHBhY2tldHMuIEhvd2V2ZXIsIG1hbnkgcm91dGVycyB3aXRo
IG5vIHN1cHBvcnQgb2Ygc3VjaCBleHRlbnNpb24gbWF5IGRpcmVjdGx5IGRyb3AgdGhlIHBhY2tl
dHMgd2l0aCBhbiB1bmtub3duIElQIG9wdGlvbi4NCj4+Pg0KPj4+IElDTiBvdmVyIElQIHN0cmF0
ZWd5IHVzZXMgYW4gb3ZlcmxheSBhcHByb2FjaC4gQ29udGVudC1yZWxhdGVkIG9wZXJhdGlvbiB3
aWxsIGJlIHBlcmZvcm1lZCBvbiB0aGUgaGlnaCBsYXllciBhbmQgQ29udGVudC1yZWxhdGVkIGlu
Zm9ybWF0aW9uIHdpbGwgYmUgc2VudCB0aHJvdWdoIGEgdHVubmVsLiBEdWUgdG8gdGhlIGxpbWl0
ZWQga25vd2xlZGdlIG9mIHBoeXNpY2FsIHRvcG9sb2d5IGFuZCB1bm5lY2Vzc2FyeSBwYWNrZXQg
ZW5jYXBzdWxhdGlvbi9kaXNjb25zb2xhdGlvbiwgdGhlIGVmZmljaWVuY3kgbWF5IGJlIGxpbWl0
ZWQuDQo+Pj4NCj4+PiBJQ04gb3ZlciBTRE4gc3RyYXRlZ3kgZXhwbG9pdHMgU0ROIGNvbnRyb2xs
ZXIgdG8gcGVyZm9ybSBjb250ZW50LXJlbGF0ZWQgb3BlcmF0aW9uLiBIb3dldmVyLCBTRE4gaXRz
ZWxmIGlzIGFuIG9uZ29pbmcgYXBwcm9hY2ggYW5kIGlzIHR5cGljYWxseSB1c2VkIGluIGEgbG9j
YWwgZG9tYWluLiBUaGUgcGVyZm9ybWFuY2UgaW4gYSBsYXJnZSBzY2FsZSBkZXBsb3ltZW50IGlz
IHVua25vd24uDQo+Pj4NCj4+PiBXaWxsDQo+Pj4NCj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4+Pj4gRnJvbTogaWNucmctYm91bmNlc0BpcnRmLm9yZyBbbWFpbHRvOmljbnJnLWJv
dW5jZXNAaXJ0Zi5vcmddIE9uIA0KPj4+PiBCZWhhbGYgT2YgQj9yamUgT2hsbWFuDQo+Pj4+IFNl
bnQ6IFRodXJzZGF5LCBPY3RvYmVyIDE4LCAyMDEyIDEwOjU1IEFNDQo+Pj4+IFRvOiBTZXVuZy1J
ayBMZWUNCj4+Pj4gQ2M6IGljbnJnDQo+Pj4+IFN1YmplY3Q6IFJlOiBbaWNucmddIEFubm91bmNp
bmcgSUNOUkcgQCBJRVRGIDg1DQo+Pj4+DQo+Pj4+IERlYXIgU2V1bmctSWssDQo+Pj4+DQo+Pj4+
IEkgdGhpbmsgeW91IGJyaW5nIHVwIGEgdmVyeSBnb29kIHBvaW50LiBJIGFncmVlIHRoYXQgZGVw
bG95bWVudCBhbmQgDQo+Pj4+IG1pZ3JhdGlvbiBpc3N1ZXMgYXJlIHZlcnkgaW1wb3J0YW50LiBJ
IGFsc28gYWdyZWUgdGhhdCB0aGV5IGRvbid0IA0KPj4+PiBzZWVtIGxpa2UgYSBnb29kIGZpdCBm
b3IgYW55IG9mIHRoZSBjdXJyZW50bHkgcHJvcG9zZWQgSUNOUkcgZG9jdW1lbnRzLg0KPj4+Pg0K
Pj4+PiBUaGUgdGhyZWUgZG9jdW1lbnRzIGxpc3RlZCBhcyBjdXJyZW50IHdvcmsgaXRlbXMgYXJl
IGluIG5vIHdheSBzZXQgDQo+Pj4+IGluIHN0b25lLCB0aGV5IHNob3VsZCBqdXN0IGJlIHNlZW4g
YXMgYSBzdGFydGluZyBwb2ludCBmb3Igb3VyIA0KPj4+PiB3b3JrLiBJZiB5b3Ugd291bGQgbGlr
ZSB0byBwcm9wb3NlIHRoZSBSRyB0aGF0IHdlIHNob3VsZCBzdGFydCANCj4+Pj4gd29ya2luZyBv
biBhIGRlcGxveW1lbnQgZG9jdW1lbnQgeW91IGFyZSBtb3N0IHdlbGNvbWUgdG8gZG8gc28sIA0K
Pj4+PiB0aGF0IHdpbGwgbW9zdCBjZXJ0YWlubHkgYmUgaW4gc2NvcGUgZm9yIG91ciBkaXNjdXNz
aW9uIGluIEF0bGFudGEuDQo+Pj4+DQo+Pj4+IEFzIGEgZ2VuZXJhbCBjb21tZW50IEkgYWxzbyBs
aWtlIHRvIG1lbnRpb24gdGhhdCB3ZSBhcyBhbiBSRyBhcmUgDQo+Pj4+IG5vdCBib3VuZCBieSBh
bGwgdGhlIHJ1bGVzIHRoYXQgYXBwbHkgdG8gSUVURiBXR3MsIGUuZy4gd2UgYXJlIGZyZWUgDQo+
Pj4+IHRvIGRpc2N1c3MgbGF0ZSBjb250cmlidXRpb25zIHByb2R1Y2VkIGFmdGVyIHRoZSBJRVRG
IGRyYWZ0IA0KPj4+PiBkZWFkbGluZXMuIFNvIGlmIHBlb3BsZSBmaW5kIHRoZSB0aW1lIHRvIHdy
aXRlIHVwIHNvbWUgbWF0ZXJpYWwgZm9yIA0KPj4+PiB0aGUgSUNOUkcgYWZ0ZXIgdGhlIElFVEYg
ZHJhZnRzIGFyZSBkb25lIHRoZXkgYXJlIHdlbGNvbWUgdG8gDQo+Pj4+IGFubm91bmNlIGl0IHRv
IHRoZSBJQ05SRyBtYWlsaW5nIGxpc3QuIElmIHRoZSBncm91cCBhZ3JlZXMgd2UgYXJlIA0KPj4+
PiBmcmVlIHRvIGRpc2N1c3MgYWxzbyBzdWNoIG1hdGVyaWFsIGF0IG91ciBtZWV0aW5nLA0KPj4+
Pg0KPj4+PiAgICAgIELOk8K2cmplDQo+Pj4+DQo+Pj4+IDE4IG9rdCAyMDEyIGtsLiAwMzo1NiBz
a3JldiAiU2V1bmctSWsgTGVlIiA8c2V1bmdpa2xlZUBldHJpLnJlLmtyPjoNCj4+Pj4NCj4+Pj4+
IERlYXIgaWNucmcgY29sbGVhZ3VlcywNCj4+Pj4+DQo+Pj4+PiBSZWdhcmRpbmcgdGhlIFJHIGRv
Y3VtZW50cywgZG9uJ3Qgd2UgdG91Y2ggYW55IGlzc3VlcyBvbiBJQ04NCj4+Pj4gZGVwbG95bWVu
dHM/DQo+Pj4+Pg0KPj4+Pj4gQXMgd2UgaGF2ZSBzZWVuIGluIHRoZSBwcmVzZW50YXRpb24gYnkg
WlRFIGluIFZhbmNvdXZlciwgSVNQcyBhcmUgDQo+Pj4+PiBpbnRlcmVzdGVkIGluIHRoZSBzaG9y
dC10ZXJtIGFwcHJvYWNoZXMgdG8gSUNOLg0KPj4+Pj4gVGhvdWdoIHRoZSB0cmFkaXRpb25hbCBJ
Q04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04vTkROKSBoYXZlIA0KPj4+Pj4gcHJvdmlkZWQgSVNQ
cyBhIGxhZGRlciBvdXQgb2YgZHVtYi1waXBlcywgSVNQcyBtYXkgaGF2ZSANCj4+Pj4+IGRpZmZp
Y3VsdGllcyBvbiBjbGVhbi1zbGF0ZSBhcHByb2FjaGVzIG9mIElDTi4NCj4+Pj4+IElNSE8sIGJh
c2VkIG9uIG91ciBzdXJ2ZXlzIG9uIElTUCBSJkQgYXBwcm9hY2hlcyB0byBJQ04sIEtvcmVhbiAN
Cj4+Pj4+IElTUHMgYXJlIGluIHRoZSBzaW1pbGFyIHNpdHVhdGlvbi4NCj4+Pj4+DQo+Pj4+PiBJ
biB0aGlzIG1vdGl2YXRpb24sIEkgaGF2ZSBpbnRlcmVzdHMgaW4gSUNOIGRlcGxveW1lbnQgc3Ry
YXRlZ2llcyANCj4+Pj4+IChzdWNoIGFzIElDTiBvdmVyIElQIG9yIElDTiBvdmVyIFNETiBhcyBz
aG9ydC10ZXJtIGFwcHJvYWNoZXMpIGJ1dCANCj4+Pj4+IG5vIGlkZWEgd2hpY2ggUkcgZG9jdW1l
bnQgd291bGQgY292ZXIgdGhlIGRlcGxveW1lbnQgaXNzdWVzLCBldmVuIA0KPj4+Pj4gd2hldGhl
ciBpY25yZyB3aWxsIGNvdmVyIHRoZSBkZXBsb3ltZW50IGlzc3VlIG9yIG5vdC4NCj4+Pj4+DQo+
Pj4+Pg0KPj4+Pj4NCj4+Pj4+IDIwMTIvMTAvOCBCzpPCtnJqZSBPaGxtYW4gPEJvcmplLk9obG1h
bkBlcmljc3Nvbi5jb20+Og0KPj4+Pj4+IFRoZSBuZXh0IElDTlJHIHdpbGwgYmUgaGVsZCBhdCAg
SUVURiA4NSwgQXRsYW50YSwgR2VvcmdpYSwgVVNBLA0KPj4+PiBOb3ZlbWJlcg0KPj4+Pj4+IDQt
OSwgMjAxMg0KPj4+Pj4+ICAgICAgKiBNZWV0aW5nIHRpbWU6IFdFRE5FU0RBWSAxMy4wMC0xNS40
MCAocHJlbCkNCj4+Pj4+Pg0KPj4+Pj4+IFRoZSBtYWluIGRpc2N1c3Npb24gYXQgdGhlIG1lZXRp
bmcgd2lsbCBiZSB0aGUgdGhyZWUgZG9jdW1lbnRzIA0KPj4+Pj4+IHRoYXQgdGhlDQo+Pj4+IFJH
DQo+Pj4+Pj4gaGFzIHNldCBvdXQgdG8gcHJvZHVjZS4NCj4+Pj4+Pg0KPj4+Pj4+IElDTiBTdXJ2
ZXkgZG9jdW1lbnQNCj4+Pj4+Pg0KPj4+Pj4+IEEgZG9jdW1lbnQgdGhhdCBwcm92aWRlcyBhIHN1
cnZleSBvZiBkaWZmZXJlbnQgYXBwcm9hY2hlcyBhbmQNCj4+Pj4gdGVjaG5pcXVlcw0KPj4+Pj4+
DQo+Pj4+Pj4gSUNOIFByb2JsZW0gc3RhdGVtZW50DQo+Pj4+Pj4NCj4+Pj4+PiBBIGRvY3VtZW50
IHRoYXQgZGVzY3JpYmVzIHRoZSBJQ04gcHJvYmxlbSBzdGF0ZW1lbnQsIHRoZSBtYWluDQo+Pj4+
IGNvbmNlcHRzIGFuZA0KPj4+Pj4+IHJlc2VhcmNoIGNoYWxsZW5nZXMgaW4gZGVwdGguDQo+Pj4+
Pj4NCj4+Pj4+PiBJQ04gQmFzZWxpbmUgU2NlbmFyaW9zDQo+Pj4+Pj4NCj4+Pj4+PiBBIGRvY3Vt
ZW50IHRoYXQgZGVmaW5lcyByZWZlcmVuY2UgYmFzZWxpbmUgc2NlbmFyaW9zIHRvIGVuYWJsZQ0K
Pj4+PiBwZXJmb3JtYW5jZQ0KPj4+Pj4+IGNvbXBhcmlzb25zIGJldHdlZW4gZGlmZmVyZW50IGFw
cHJvYWNoZXMuDQo+Pj4+Pj4NCj4+Pj4+PiBQZW9wbGUgYXJlIGVuY291cmFnZWQgdG8gcHJlc2Vu
dCB0aGVpciB2aWV3cyBvbiB3aGF0IHRoZXkgdGhpbmsgDQo+Pj4+Pj4gc2hvdWxkDQo+Pj4+IGJl
DQo+Pj4+Pj4gdGhlIGNvbnRlbnRzIG9mIHRoZXNlIGRvY3VtZW50cy4gRWFybHkgY29udHJpYnV0
aW9ucyAoaW4gYnVsbGV0IA0KPj4+Pj4+IGZvcm0gb3IgYXMgZHJhZnQgdGV4dCkgYXJlIHdlbGNv
bWUgYm90aCBvbiB0aGUgbWFpbGluZyBsaXN0IGFuZCB0aGUgd2lraS4NCj4+Pj4gUHJlc2VudGF0
aW9ucw0KPj4+Pj4+IG9mIGRyYWZ0IG1hdGVyaWFsIGFyZSB3ZWxjb21lIGF0IHRoZSBtZWV0aW5n
Lg0KPj4+Pj4+DQo+Pj4+Pj4gTW9zdCBsaWtlbHkgd2Ugd2lsbCBhbHNvIGhhdmUgdGltZSB0byBk
aXNjdXNzIG9uZSBvciB0d28gc3BlY2lmaWMgDQo+Pj4+Pj4gdGVjaG5pY2FsIHRvcGljcyBhdCB0
aGUgbWVldGluZy4gUHJvcG9zYWxzIGZvciBzdWNoIHRvcGljcyBhcyANCj4+Pj4+PiB3ZWxsIGFz
IHByZXNlbnRhdGlvbnMgYXJlIGludml0ZWQuDQo+Pj4+Pj4NCj4+Pj4+PiBBcyB3ZSBhcmUgZXhw
ZWN0ZWQgdG8gcHVibGlzaCBvdXIgYWdlbmRhIGJ5IDIwMTItMTAtMjQgDQo+Pj4+Pj4gKFdlZG5l
c2RheSkgd2UNCj4+Pj4gd291bGQNCj4+Pj4+PiBsaWtlIHRvIGhhdmUgeW91ciBpbnB1dCBieSBT
dW5kYXkgMjAxMi0xMC0yMS4NCj4+Pj4+Pg0KPj4+Pj4+IELOk8K2cmplLCBEYXZlICYgRGlyaw0K
Pj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+PiBJQ04gUkcgV2lraToNCj4+Pj4+Pg0KPj4+Pj4+IGh0dHA6
Ly90cmFjLnRvb2xzLmlldGYub3JnL2dyb3VwL2lydGYvdHJhYy93aWtpL2ljbnJnDQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGljbnJnIG1haWxp
bmcgbGlzdA0KPiBpY25yZ0BpcnRmLm9yZw0KPiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2ljbnJnDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KaWNucmcgbWFpbGluZyBsaXN0DQppY25yZ0BpcnRmLm9yZw0KaHR0cHM6Ly93d3cu
aXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pY25yZw0K

From hannu.flinck@nsn.com  Wed Oct 24 04:05:49 2012
Return-Path: <hannu.flinck@nsn.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17C6221F88A9 for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 04:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSMrkfwto3A0 for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 04:05:48 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3E86C21F889E for <icnrg@irtf.org>; Wed, 24 Oct 2012 04:05:47 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q9OB5hwY018878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 24 Oct 2012 13:05:43 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q9OB5eph009709; Wed, 24 Oct 2012 13:05:43 +0200
Received: from FIESEXC008.nsn-intra.net ([10.159.0.16]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 24 Oct 2012 13:05:14 +0200
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: Wed, 24 Oct 2012 14:05:13 +0300
Message-ID: <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net>
In-Reply-To: <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: AQHNsajua6NfubUpn0CSoOItbxeoB5fISzBQ
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com>
From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
To: =?iso-8859-1?Q?ext_B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, "Konstantinos Pentikousis" <k.pentikousis@huawei.com>
X-OriginalArrivalTime: 24 Oct 2012 11:05:14.0612 (UTC) FILETIME=[71A1B340:01CDB1D7]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1636
X-purgate-ID: 151667::1351076743-000048BF-0ED5366F/0-0/0-0
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 11:05:49 -0000

Most likely people who attend to icnrg will also attend to CDNi and =
ALTO. Many in addition to me would appreciate if these meetings would =
not conflict.

- Hannu=20

-----Original Message-----
From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf =
Of ext B=F6rje Ohlman
Sent: Wednesday, October 24, 2012 8:32 AM
To: Konstantinos Pentikousis
Cc: icnrg
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap

Yes, it is a bit unfortunate. When we (the ICNRG chairs) gave feedback =
on the initial schedule our meeting was on Wednesday morning, which =
looked alright, but then they moved the IRTF Open Meeting there end we =
were pushed to the afternoon.=20
If there is a lot of people having issues with the Wednesday afternoon =
slot we could try to move the meeting to Monday or Tuesday. But moving =
meetings forward  in the schedule is usually not a good idea as some =
people will not note the change in time, and thus miss the meeting. =
Moving to Thursday or Friday is unfortunately not an option as non of =
the chairs will be available those days.

       B=F6rje

23 okt 2012 kl. 14:52 skrev "Konstantinos Pentikousis" =
<k.pentikousis@huawei.com>:

> Hi all,
>=20
> It seems that ICNRG overlaps with CDNi (1300-1430) and ALTO =
(1440-1540).
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg

From k.pentikousis@huawei.com  Wed Oct 24 06:23:12 2012
Return-Path: <k.pentikousis@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7C521F87DC for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 06:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.016
X-Spam-Level: 
X-Spam-Status: No, score=-5.016 tagged_above=-999 required=5 tests=[AWL=1.283,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LsjBrvt0tEd for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 06:23:12 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 72DA621F87DB for <icnrg@irtf.org>; Wed, 24 Oct 2012 06:23:11 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml209-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARF48807; Wed, 24 Oct 2012 21:23:08 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Oct 2012 21:21:55 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 24 Oct 2012 21:21:54 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>, =?iso-8859-1?Q?ext_B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: Ac2xHSMYHmGcCj4dT7GVkqlZglE43QASL1oAAAuggoAAFYP9kA==
Date: Wed, 24 Oct 2012 13:21:53 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net>
In-Reply-To: <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.216.136]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:23:12 -0000

  |Most likely people who attend to icnrg will also attend to CDNi and
  |ALTO. Many in addition to me would appreciate if these meetings would
  |not conflict.
=20
Second this too.

Best Regards,

Kostas




From Ignacio.Solis@parc.com  Wed Oct 24 08:56:11 2012
Return-Path: <Ignacio.Solis@parc.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 143D221F8C0B for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 08:56:11 -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=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKb4bDvti7zy for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 08:56:10 -0700 (PDT)
Received: from omega.xerox.com (omega.xerox.com [13.1.64.95]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6B21F8BE4 for <icnrg@irtf.org>; Wed, 24 Oct 2012 08:56:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by omega.xerox.com (Postfix) with ESMTP id B977025401C; Wed, 24 Oct 2012 08:56:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at parc.com
Received: from omega.xerox.com ([127.0.0.1]) by localhost (omega.xerox.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43v-So5gTf+m; Wed, 24 Oct 2012 08:56:04 -0700 (PDT)
Received: from exchangehub.parc.xerox.com (e2010hub1.parc.xerox.com [13.2.12.22]) by omega.xerox.com (Postfix) with ESMTPS id 6E1E5522001; Wed, 24 Oct 2012 08:56:04 -0700 (PDT)
Received: from E2010DAG5.corp.ad.parc.com ([fe80::3d0b:7158:aec4:e05e]) by e2010hub1.corp.ad.parc.com ([fe80::8945:a39d:8c92:373f%12]) with mapi id 14.02.0318.004; Wed, 24 Oct 2012 08:56:03 -0700
From: <Ignacio.Solis@parc.com>
To: <spis@intracom.com>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNsVYeAHIgkogGRUiJNLSWYIgNIJfIooYAgABwSAA=
Date: Wed, 24 Oct 2012 15:56:03 +0000
Message-ID: <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com>
In-Reply-To: <5087B162.9040305@intracom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.244.190.163]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C8960AE5B9199043AAA47B8130D9BDA9@ad.parc.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: icnrg@irtf.org, bengta@sics.se, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 15:56:11 -0000

IkJlc3QtZWZmb3J0IiBmb3Igc29tZSBJQ05zIGhhcyBkaWZmZXJlbnQgY2hhcmFjdGVyaXN0aWNz
IHRoYXQgSVAgYmVzdC1lZmZvcnQsIHNvIGNvbXBhcmluZyBpdCBkaXJlY3RseSBtaWdodCBub3Qg
YmUgYWNjdXJhdGUuICAgRm9yIGFsbCB3ZSBrbm93IElDTnMgYmVzdC1lZmZvcnQgaXMgYmV0dGVy
LXRoYW4tSVAtYmVzdC1lZmZvcnQuDQoNCkkgZG9uJ3QgdGhpbmsgdGhhdCBldmVyeWJvZHkgaXMg
aGFwcHktZW5vdWdoLCBhZnRlciBhbGwsIGV2ZXJ5Ym9keSB3YW50cyB0byBiZSBoYXBwaWVyLg0K
DQpJIHRoaW5rIHRoZSBwb2ludHMgSSBtYWRlIGFyZSBzdGlsbCB1bmFuc3dlcmVkLiAgSXQncyBw
cm9iYWJseSB0cnVlIHRoYXQgbWFueSBvZiB0aG9zZSBhcmUgbm90IHRoZSBiaWdnZXN0IHBhaW4g
cG9pbnRzIGZvciBJU1BzLCBidXQgSVNQcyBhcmUgbm90IHRoZSBvbmx5IHN0YWtlaG9sZGVycyAo
ZGV2aWNlIG1hbnVmYWN0dXJlcnM/IElvVCBjb21wYW5pZXM/IE9TIHZlbmRvcnM/IG9wZW4gc291
cmNlIHByb2plY3RzPyBDb21wYW5pZXMgdGhhdCBkb24ndCB3YW50IHRvIGRlcGVuZCBvbiBvdGhl
cnMgdG8gcHJvdmlkZSBDRE4gbGlrZSBzZXJ2aWNlIGFuZCBuZWVkIHRvIGJ1aWxkIHRoZWlyIG93
bj8gSW50ZXJuYWwgZW50ZXJwcmlzZSBzZXJ2aWNlcz8gRGF0YWNlbnRlciBjb21tdW5pY2F0aW9u
cz8pDQoNCkZpbmFsbHksIGFzIHN0YXRlZCBieSBvdGhlcnMsIEkgZG9uJ3QgdGhpbmsgdGhlcmUg
aXMgYSBkaXJlY3QgY29tcGV0aXRpb24gYmV0d2VlbiBJQ04gYW5kIENETnMuICBPbmUgaXMgYSBz
ZXQgb2YgcHJvdG9jb2xzIGFuZCB0aGUgb3RoZXIgaXMgYSBzZXJ2aWNlL2J1c2luZXNzIG1vZGVs
LiAgVGhlIGZ1bmN0aW9ucyBwcm92aWRlZCBieSBDRE5zIGFyZSBzdGlsbCBuZWVkZWQgaW4gYSB3
b3JsZCB3aXRoIElDTi4gIENvbnRlbnQgcHJvdmlkZXJzIHdpbGwgc3RpbGwgcmVxdWlyZSBoZWxw
IGRpc3RyaWJ1dGluZyB0aGVpciBjb250ZW50LCBwcmUtcGxhY2luZyBpdCwgbW9uaXRvcmluZyBp
dCwgYWNjb3VudGluZyBmb3IgdXNhZ2UsIHN0b3JpbmcgaXQuICBQYXJ0IG9mIHRoaXMgY2FuIGJl
IGRvbmUgYnkgYSBDRE4tY29tcGFueSBkaXJlY3RseS4gQW5vdGhlciBwYXJ0IGNhbiBwb3RlbnRp
YWxseSBiZSBicm9rZXJlZCB2aWEgYSBDRE4uIENETnMgY291bGQgcG90ZW50aWFsbHkgYnV5IElD
Ti1zdG9yYWdlIGZyb20gSVNQcyBhbmQgcmVzZWxsIHRvIGNsaWVudHMgYXMgdGhleSBzZWUgZml0
LiAgSVNQcyBjb3VsZCBwcm92aWRlIEFQSXMsIHN0b3JhZ2UgYW5kIGNlcnRhaW4gZ3VhcmFudGVl
cyB0byBDTkRzLiAgKFllcywgeWVzLCBJJ20gd2F2aW5nIG15IGhhbmRzIHRocm91Z2ggbmV0IG5l
dXRyYWxpdHkgaXNzdWVzKS4gDQoNCldlIGRvbid0IGtub3cgd2hhdCB0aGUgd29ybGQgY291bGQg
bG9vayBsaWtlIGJlY2F1c2Ugd2UgaGF2ZW4ndCBmaW5pc2hlZCBkZXZlbG9waW5nIHRoZSBJQ04g
YXJjaGl0ZWN0dXJlcyBhbmQgcHJvdG9jb2xzLiAgTWF5YmUgdGhpcyBpcyBub3QgdGhlIHJpZ2h0
IG1vZGVsLg0KDQpJJ20gbm90IHN1cmUgd2hhdCB5b3VyIGRlZmluaXRpb24gb2YgZ3VhcmFudGVl
cyBpbiBkZWxpdmVyeSBpcywgYnV0IHVuZGVyIHNvbWUgZGVmaW5pdGlvbiBUQ1Agd291bGQgYWxz
byBmaXQgYW5kIGl0IGRvZXNuJ3QgY29tcGV0ZS4gQWxzbywgd2h5IHdvdWxkIElTUHMgcmlzayBs
b29zaW5nIHJldmVudWUgYnkgbm90IHNlbGxpbmcgcG90ZW50aWFsIElDTiBzZXJ2aWNlcyB0byBD
RE5zIGFuZCBvdGhlcnM/DQoNCk5hY2hvDQoNCi0tDQpOYWNobyAoSWduYWNpbykgU29saXMNClNl
bmlvciBSZXNlYXJjaCBTY2llbnRpc3QNClBhbG8gQWx0byBSZXNlYXJjaCBDZW50ZXIgKFBBUkMp
DQorMSg2NTApIDgxMi00NDU4DQpJZ25hY2lvLlNvbGlzQHBhcmMuY29tDQoNCg0KDQoNCk9uIE9j
dCAyNCwgMjAxMiwgYXQgNToxNCBBTSwgU3Bpcm9zIFNwaXJvdSA8c3Bpc0BpbnRyYWNvbS5jb20+
DQogd3JvdGU6DQoNCj4gSGkgQmVuZ3QhDQo+IA0KPiBJZiBJQ04gZG9lcyBub3QgcHJvdmlkZSBh
bnkgc29ydCBvZiBiZXR0ZXItdGhhbi1iZXN0LWVmZm9ydCBkZWxpdmVyeSwgdGhlbiBpdCBzZWVt
cyAodG8gbWUgYXQgbGVhc3QpIHRoYXQgbmVpdGhlciBJU1BzIG5vciBjb250ZW50IHByb3ZpZGVy
cyBoYXZlIGFueSBzaWduaWZpY2FudCBpbmNlbnRpdmUgdG8gYWRvcHQgSUNOLiBUaGV5IGNhbiBz
aW1wbHkgc3RpY2sgd2l0aCB0aGUgZW50cmVuY2hlZCBDRE4gdGVjaG5vbG9neSBhbmQgYnVzaW5l
c3MgbW9kZWwgd2hlcmUgYWxsIHN0ZWtlaG9sZGVycyAoZW5kLXVzZXJzLCBJU1BzLCBDRE4gb3Bl
cmF0b3JzLCBhbmQgY29udGVudCBwcm92aWRlcnMvb3duZXJzKSBzZWVtIHRvIGJlIGhhcHB5IGVu
b3VnaC4NCj4gDQo+IElmLCBvbiB0aGUgb3RoZXIgaGFuZCwgSUNOIGRvZXMgcHJvdmlkZSBndWFy
YW50ZWVzIGluIGRlbGl2ZXJ5LCB0aGVuIElDTiBhbmQgQ0ROIHNlZW0gbGlrZWx5IHRvIGJlY29t
ZSBjb21wZXRpdG9ycywgYXMgdGhleSB3b3VsZCBiZSBvZmZlcmluZyBhIHZlcnkgc2ltaWxhciBz
ZXJ2aWNlLiBUaGUgcXVlc3Rpb24gZm9yIG1lIGlzIHdoeSB3b3VsZCBJU1BzIHJpc2sgbG9zaW5n
IGV4aXN0aW5nIHJldmVudWUgZnJvbSBDRE4gb3BlcmF0b3JzIGluIGZhdm9yIG9mIGNhcGl0YWwg
ZXhwZW5kaXR1cmUgZm9yIGRlcGxveWluZyBJQ04/IFRoZXJlJ3Mgb2YgY291cnNlIHRoZSBob3Bl
IHRoYXQgY29udGVudCBwcm92aWRlcnMgd291bGQgYmUgbHVyZWQgYXdheSBmcm9tIENETiwgYnV0
IHRoaXMgc2VlbXMgcmVhbGlzdGljIG9ubHkgaWYgSUNOIGlzIGNoZWFwZXIgb3Igc29tZWhvdyBi
ZXR0ZXIgdGhhbiBDRE4uDQo+IA0KPiBTcGlyb3MNCj4gDQo+IE9uIDIzLzEwLzIwMTIgMTA6Mzkg
zrzOvCwgQmVuZ3QgQWhsZ3JlbiB3cm90ZToNCj4+IEkgYWdyZWUgd2l0aCBOYWNobywgYnV0IHdv
dWxkIGxpa2UgdG8gYWRkIGFuIGFuZ2xlIHRvIHRoaXMgZGlzY3Vzc2lvbiENCj4+IA0KPj4gQ0RO
LCBJTU8sIGlzIG1vcmUgYSBidXNpbmVzcyBtb2RlbCB0aGFuIGEgcGFydGljdWxhciBzZXQgb2Yg
cHJvdG9jb2xzDQo+PiBhbmQgc2VydmljZXMuICBDRE4gb3BlcmF0b3JzIGFncmVlIHRvIGRlbGl2
ZXIgdGhlIGNvbnRlbnQgb2YgcGFydGljdWxhcg0KPj4gcHVibGlzaGVycyBmb3IgYSBmZWUgYXQg
c29tZSBsZXZlbCBvZiBzZXJ2aWNlLiAgV2hldGhlciB0aGlzIGlzIGRvbmUgb24NCj4+IGFuIElQ
IG5ldHdvcmsgb3Igc29tZXRoaW5nIGVsc2UgaXMgbm90IHJlYWxseSBpbXBvcnRhbnQuDQo+PiAN
Cj4+IElDTiBpcyBhIGRpZmZlcmVudCBzZXQgb2YgcHJvdG9jb2xzIGFuZCBzZXJ2aWNlcyBjb21w
YXJlZCB0byBJUCwgYnV0IG5vdA0KPj4gcmVhbGx5IGEgc3BlY2lmaWMgYnVzaW5lc3MgbW9kZWws
IGFsdGhvdWdoIGl0IG1heSBjaGFuZ2UgdGhlIGJ1c2luZXNzDQo+PiBwbGF5aW5nIGZpZWxkIHNv
bWV3aGF0LiAgU28sIGV2ZW4gdGhvdWdoIHdlIGNhbiBhcmd1ZSB0aGF0IElDTiBpcyBnb29kDQo+
PiBmb3IgY29udGVudCBkaXN0cmlidXRpb24sIEkgZG9uJ3QgdGhpbmsgdGhlIENETiBidXNpbmVz
cyBiZWNvbWVzDQo+PiByZWR1bmRhbnQuICBUaGVyZSB3aWxsIHN0aWxsIGJlIGNvbnRlbnQgcHVi
bGlzaGVycyB0aGF0IHdhbnQgdG8gbWFrZQ0KPj4gc3VyZSB0aGF0IHRoZWlyIGNvbnRlbnQgaXMg
ZGVsaXZlcmVkIGF0IHNvbWUga25vd24gbGV2ZWwgb2Ygc2VydmljZSB0bw0KPj4gdGhlaXIgY3Vz
dG9tZXJzLiAgVGhlICJub3JtYWwiIElDTiBjYWNoaW5nIHNpbXBseSBjb3JyZXNwb25kcyB0byBj
dXJyZW50DQo+PiBiZXN0LWVmZm9ydCBJUCBwYWNrZXQgZm9yd2FyZGluZywgd2l0aCBzaW1pbGFy
IG5vbi1ndWFyYW50ZWUgb2Ygc2VydmljZS4NCj4+IA0KPj4gSGF2aW5nIHNhaWQgdGhhdCwgd2hl
biB0aGUgQ0ROIGZvbGtzIG5vdyBhcmUgc3RhcnRpbmcgdG8gZGVmaW5lDQo+PiBwYXJ0aWN1bGFy
IHByb3RvY29scyBhbmQgaW50ZXJmYWNlcyAoZS5nLiwgQ0ROSSksIHRoZXkgYXJlIHdvcmtpbmcg
b24NCj4+IHN0dWZmIHRoYXQgdG91Y2hlcyBJQ04sIGJ1dCBmb3Igc3VwcG9ydGluZyB0aGVpciBw
YXJ0aWN1bGFyIHB1cnBvc2UgKHRoZQ0KPj4gQ0ROIGJ1c2luZXNzIG1vZGVsKS4NCj4+IA0KPj4g
QmVuZ3QNCj4+IA0KPj4gPElnbmFjaW8uU29saXNAcGFyYy5jb20+IHdyaXRlczoNCj4+IA0KPj4+
IEhpIEJyaWFuLg0KPj4+IA0KPj4+IFlvdSBhcmUgcmlnaHQgdGhhdCBmb3IgYSBzdWJzZXQgb2Yg
Y2FzZXMgaXQgc2VlbXMgbGlrZSBJQ04gaXMganVzdA0KPj4+IENETiwgYnV0IHRoYXQgd291bGQg
YmUgbWlzc2luZyBhIGxvdCBvZiB0aGUgcGljdHVyZS4NCj4+PiANCj4+PiBGaXJzdCwgY2FuIHlv
dSBkZXNjcmliZSB3aGF0IHRoZSBwcm9wZXJ0aWVzIG9mIG5hdGl2ZSBJQ04gYW5kDQo+Pj4gbm9u
LW5hdGl2ZSBJQ04gYXJlPyAgSXMgdGhlcmUgbm8gInJvdXRlciBjYWNoaW5nIiBpbiBub24tbmF0
aXZlIElDTj8NCj4+PiANCj4+PiBBIGZldyBvZiB0aGUgdGhpbmdzIHRoYXQgZG9uJ3Qgc2VlbSB0
byBmaXQgaW50byB0cmFkaXRpb25hbCBDRE5zICh3aXRoDQo+Pj4gbXkgbGltaXRlZCBrbm93bGVk
Z2Ugb2Ygc3RhdGUtb2YtdGhlIGFydCBDRE5zKSBhcmU6DQo+Pj4gDQo+Pj4gLSBQZWVyLXRvLXBl
ZXIuICBIb3cgY2FuIENETnMgaGVscCB0d28gbm9kZXMgY29tbXVuaWNhdGUgd2l0aG91dA0KPj4+
IGluZnJhc3RydWN0dXJlPyAgSWYgdHdvIG5vZGVzIG1lZXQgaW4gdGhlIGZpZWxkIChzdWNoIGFz
IGluIHRoZSBEQVJQQQ0KPj4+IENCTUVOIHByb2dyYW0sIG9yIHR3byBwaG9uZXMgb24gYSBwbGFu
ZSBvciB0dW5uZWwgb3Igc2hpcCksIGhvdyBjYW4NCj4+PiBDRE5zIGhlbHAgdGhlbSBleGNoYW5n
ZSBpbmZvcm1hdGlvbj8NCj4+PiANCj4+PiAtIFNlY3VyaXR5LiBIb3cgY2FuIENETnMgZW5zdXJl
IHRoZSBwcm92ZW5hbmNlIG9mIHRoZSBkYXRhPw0KPj4+IA0KPj4+IC0gRGlzcnVwdGlvbiB0b2xl
cmFuY2UuIEhvdyBjYW4gQ0ROcyBlbmFibGUgZGF0YS1tdWxpbmc/DQo+Pj4gDQo+Pj4gLSBGbG93
IGNvbnRyb2wuIEhvdyBjYW4geW91IGNoYW5nZSB0aGUgd2F5IHdlIGRvIGZsb3ctY29udHJvbCB1
c2luZyBDRE5zPw0KPj4+IA0KPj4+IC0gTG9uZSBoaXQuIEhvdyBjYW4gQ0ROcyBoZWxwIGRpc3Ry
aWJ1dGUgZGF0YSB0aGF0IHdhcyBwcmV2aW91c2x5DQo+Pj4gdW5rbm93biB0byB0aGUgQ0ROLiBG
b3IgZXhhbXBsZSwgZnJvbSBhIHJhbmRvbSB3ZWJwYWdlLg0KPj4+IA0KPj4+IA0KPj4+IEdyYW50
ZWQsIHNvbWUgb2YgdGhvc2UgYXJlIHNvbWV3aGF0IHBvc3NpYmxlIHVzaW5nIENETnMuIFNvbWUg
b2YgdGhvc2UNCj4+PiBhcmUgcG9zc2libGUgd2l0aCBhIGxpdHRsZSBiaXQgb2Ygd29yayBvbiBD
RE5zIGFuZCBzb21lIGFyZSBwb3NzaWJsZQ0KPj4+IHdpdGggYSBsb3Qgb2Ygd29yay4NCj4+PiAN
Cj4+PiBFdmVyeXRoaW5nIGlzIHBvc3NpYmxlLg0KPj4+IA0KPj4+IEJ1dCwgd2UncmUgZ29pbmcg
dG8gZ2V0IHRvIGEgcG9pbnQgd2hlcmUgd2UncmUgY2hhbmdpbmcgc28gbXVjaCB0aGF0DQo+Pj4g
d2hhdCB3ZSBzdGFydGVkIHdpdGggaXMgdW5yZWNvZ25pemFibGUuICBTdGFydGluZyB3aXRoIENE
TnMgaXMNCj4+PiBsaW1pdGluZyB3aGF0IHdlIGNhbiBkbyBhbmQgaG93IHdlIGRvIGl0LiAgVGhl
IG1vZGVsIG1hbnkgSUNOcyB0YWtlIGlzDQo+Pj4gYSBjbGVhbiBzbGF0ZSBvbmUuIEFuZCBhcyBm
YXIgYXMgcG9zc2libGUsIHdlIHRyeSB0byBsZWFybiB0aGUgbGVzc29ucw0KPj4+IG9mIENETnMs
IERUTnMsIElQcywgR251dGVsbGFzLCBNdWx0aWNhc3QsIFJUUHMsIElQU2VjcywgVENQcywgRE5T
cywNCj4+PiBPU1BGcywgZXRjLg0KPj4+IA0KPj4+IENhY2hpbmcgYXQgdGhlIHJvdXRlciBsZXZl
bCBpcyBvbmUgb2YgdGhlIG1hbnkgcG90ZW50aWFsbHkgYmVuZWZpY2lhbA0KPj4+IChidXQgbm90
LXJlcXVpcmVkKSBjaGFyYWN0ZXJpc3RpY3Mgb2YgSUNOcy4NCj4+PiANCj4+PiBJZiB3ZSB0YWxr
IGFib3V0IGEgc3BlY2lmaWMgSUNOIGFyY2hpdGVjdHVyZSAobGlrZSBDQ04pIHdlIGNhbiB0YWxr
DQo+Pj4gYWJvdXQgc3BlY2lmaWMgYWR2YW50YWdlcyBhbmQgZGlzYWR2YW50YWdlcywgdHJhZGVv
ZmZzIG1hZGUsIHdvcmsgZG9uZQ0KPj4+IHNvIGZhciwgd29yayBwbGFubmVkIGFuZCB3b3JrIHll
dCB0byBiZSBkb25lLg0KPj4+IA0KPj4+IE5hY2hvDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gLS0N
Cj4+PiBOYWNobyAoSWduYWNpbykgU29saXMNCj4+PiBTZW5pb3IgUmVzZWFyY2ggU2NpZW50aXN0
DQo+Pj4gUGFsbyBBbHRvIFJlc2VhcmNoIENlbnRlciAoUEFSQykNCj4+PiArMSg2NTApIDgxMi00
NDU4DQo+Pj4gSWduYWNpby5Tb2xpc0BwYXJjLmNvbQ0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0K
Pj4+IE9uIE9jdCAxOCwgMjAxMiwgYXQgMjo1NCBQTSwgIkZpZWxkLCBCcmlhbiIgPEJyaWFuX0Zp
ZWxkQGNhYmxlLmNvbWNhc3QuY29tPg0KPj4+ICB3cm90ZToNCj4+PiANCj4+Pj4gRG9lcyBhbnlv
bmUgKGJlc2lkZSBtZSkgdGhpbmsgdGhhdCBhIENETiBlZmZlY3RpdmVseSBpcyBhbHJlYWR5IGRv
aW5nICJJQ04iIGJ1dCB0dW5uZWxlZCBvdmVyIGFuIEhUVFAgaW5mcmFzdHJ1Y3R1cmUgKHZpYSBI
VFRQL1RDUC9JUCkuICAgSSB0aGluayBvZiBDRE4gYW5kIG5hdGl2ZSBJQ04gKHdoZXJlIHRoZSBy
b3V0ZXIgaXMgY2FjaGluZyBhbmQgZm9yd2FyZGluZyBhdCB0aGUgSUNOIGxldmVsKSBuZWFybHkg
aWRlbnRpY2FsIGZvcndhcmRpbmcgcGFyYWRpZ21zIGp1c3Qgb3BlcmF0aW5nIGF0IGRpZmZlcmVu
dCBsZXZlbHMgaW4gdGhlIHN0YWNrLg0KPj4+PiANCj4+Pj4gVGhlcmUncyB3b3JrIGluIHN0YW5k
YXJkaXppbmcgdGhlIGludHJhLUNETiAgYW5kIGludGVyLUNETiBjb250cm9sIHBsYW4gKGluIENE
Ti1JIGFuZCBlbHNld2hlcmUpLiAgSU1PLCBpdCB3b3VsZCBiZSB1c2VmdWwgaWYgd2UgaGFkIHRo
ZSBzYW1lIGNvbnRyb2wgcHJvdG9jb2wgb3BlcmF0aW5nIGluIGJvdGggdGhlIENETiBhbmQgSUNO
IGRvbWFpbnMgYW5kIHRoZSAidHJhbnNpdGlvbiIgd2FzIGp1c3QgY2hhbmdpbmcgdGhlIGxheWVy
IGF0IHdoaWNoIGZvcndhcmRpbmcgb2NjdXJyZWQuDQo+Pj4+IA0KPj4+PiBCcmlhbg0KPj4+PiAN
Cj4+Pj4gDQo+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+IEZyb206IGljbnJn
LWJvdW5jZXNAaXJ0Zi5vcmcgW21haWx0bzppY25yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBCZWhh
bGYgT2YgV2lsbCBMaXUgKFNodWNoZW5nKQ0KPj4+PiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAx
OCwgMjAxMiAzOjA4IEFNDQo+Pj4+IFRvOiBCzpPCtnJqZSBPaGxtYW47IFNldW5nLUlrIExlZQ0K
Pj4+PiBDYzogzrTCu8K7zrXCqcKnOyBpY25yZzsgSmlhbnBpbmcgV2FuZw0KPj4+PiBTdWJqZWN0
OiBSZTogW2ljbnJnXSBBbm5vdW5jaW5nIElDTlJHIEAgSUVURiA4NQ0KPj4+PiANCj4+Pj4gSGks
DQo+Pj4+IA0KPj4+PiBNeSBncm91cCBhcmUgYWxzbyBpbnRlcmVzdGVkIGluIElDTiBkZXBsb3lt
ZW50IGFuZCBoYXZlIGRvbmUgc29tZSBzdXJ2ZXkgb24gdGhpcyBtYXR0ZXIuIFRoZSBkaXNjdXNz
aW9uIG9uIElDTiBkZXBsb3ltZW50IGlzIGEgZ3JlYXQgdG9waWMgd2hpY2ggSVNQcyB3aWxsIGRl
ZmluaXRlbHkgYmUgaW50ZXJlc3RlZCBpbi4gSGVyZSBhcmUgb3VyIDItY2VudHMuDQo+Pj4+IA0K
Pj4+PiBUaGUgZXZvbHZlbWVudCBvZiBJQ04gbWF5IHRha2UgdGhlIGZvbGxvd2luZyB0aHJlZSBp
bXBsZW1lbnRhdGlvbnM6IGludGVncmF0ZWQgd2l0aCBJUCwgb3ZlciBJUCBhbmQgb3ZlciBTRE4u
IFRoZXNlIHN0cmF0ZWdpZXMgYWxsIGNhbiBoZWxwIHRoZSBJU1Agc2hpZnQgZnJvbSB0aGUgdHJh
ZGl0aW9uYWwgSVAgdG8gSUNOLiBUaGUgb25seSBxdWVzdGlvbiBpcyB3aGljaCBvbmUgaXMgdGhl
IGJlc3QgY2hvaWNlIGZvciBsYXJnZSBzY2FsZSBkZXBsb3ltZW50Pw0KPj4+PiANCj4+Pj4gSW50
ZWdyYXRlZCB3aXRoIElQIHN0cmF0ZWd5IGV4dGVuZHMgdGhlIGV4aXN0aW5nIElQIHByb3RvY29s
IChJUCBvcHRpb24pIHRvIHN1cHBvcnQgSUNOLiBUaGUgdXBkYXRlZCBJUCByb3V0ZXIsIGNhbGxl
ZCBjb250ZW50IHJvdXRlciwgd2lsbCBkZWFsIHdpdGggc3VjaCBzcGVjaWFsIHBhY2tldHMuIEhv
d2V2ZXIsIG1hbnkgcm91dGVycyB3aXRoIG5vIHN1cHBvcnQgb2Ygc3VjaCBleHRlbnNpb24gbWF5
IGRpcmVjdGx5IGRyb3AgdGhlIHBhY2tldHMgd2l0aCBhbiB1bmtub3duIElQIG9wdGlvbi4NCj4+
Pj4gDQo+Pj4+IElDTiBvdmVyIElQIHN0cmF0ZWd5IHVzZXMgYW4gb3ZlcmxheSBhcHByb2FjaC4g
Q29udGVudC1yZWxhdGVkIG9wZXJhdGlvbiB3aWxsIGJlIHBlcmZvcm1lZCBvbiB0aGUgaGlnaCBs
YXllciBhbmQgQ29udGVudC1yZWxhdGVkIGluZm9ybWF0aW9uIHdpbGwgYmUgc2VudCB0aHJvdWdo
IGEgdHVubmVsLiBEdWUgdG8gdGhlIGxpbWl0ZWQga25vd2xlZGdlIG9mIHBoeXNpY2FsIHRvcG9s
b2d5IGFuZCB1bm5lY2Vzc2FyeSBwYWNrZXQgZW5jYXBzdWxhdGlvbi9kaXNjb25zb2xhdGlvbiwg
dGhlIGVmZmljaWVuY3kgbWF5IGJlIGxpbWl0ZWQuDQo+Pj4+IA0KPj4+PiBJQ04gb3ZlciBTRE4g
c3RyYXRlZ3kgZXhwbG9pdHMgU0ROIGNvbnRyb2xsZXIgdG8gcGVyZm9ybSBjb250ZW50LXJlbGF0
ZWQgb3BlcmF0aW9uLiBIb3dldmVyLCBTRE4gaXRzZWxmIGlzIGFuIG9uZ29pbmcgYXBwcm9hY2gg
YW5kIGlzIHR5cGljYWxseSB1c2VkIGluIGEgbG9jYWwgZG9tYWluLiBUaGUgcGVyZm9ybWFuY2Ug
aW4gYSBsYXJnZSBzY2FsZSBkZXBsb3ltZW50IGlzIHVua25vd24uDQo+Pj4+IA0KPj4+PiBXaWxs
DQo+Pj4+IA0KPj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+IEZyb206IGlj
bnJnLWJvdW5jZXNAaXJ0Zi5vcmcgW21haWx0bzppY25yZy1ib3VuY2VzQGlydGYub3JnXSBPbiBC
ZWhhbGYNCj4+Pj4+IE9mIEI/cmplIE9obG1hbg0KPj4+Pj4gU2VudDogVGh1cnNkYXksIE9jdG9i
ZXIgMTgsIDIwMTIgMTA6NTUgQU0NCj4+Pj4+IFRvOiBTZXVuZy1JayBMZWUNCj4+Pj4+IENjOiBp
Y25yZw0KPj4+Pj4gU3ViamVjdDogUmU6IFtpY25yZ10gQW5ub3VuY2luZyBJQ05SRyBAIElFVEYg
ODUNCj4+Pj4+IA0KPj4+Pj4gRGVhciBTZXVuZy1JaywNCj4+Pj4+IA0KPj4+Pj4gSSB0aGluayB5
b3UgYnJpbmcgdXAgYSB2ZXJ5IGdvb2QgcG9pbnQuIEkgYWdyZWUgdGhhdCBkZXBsb3ltZW50IGFu
ZA0KPj4+Pj4gbWlncmF0aW9uIGlzc3VlcyBhcmUgdmVyeSBpbXBvcnRhbnQuIEkgYWxzbyBhZ3Jl
ZSB0aGF0IHRoZXkgZG9uJ3Qgc2VlbQ0KPj4+Pj4gbGlrZSBhIGdvb2QgZml0IGZvciBhbnkgb2Yg
dGhlIGN1cnJlbnRseSBwcm9wb3NlZCBJQ05SRyBkb2N1bWVudHMuDQo+Pj4+PiANCj4+Pj4+IFRo
ZSB0aHJlZSBkb2N1bWVudHMgbGlzdGVkIGFzIGN1cnJlbnQgd29yayBpdGVtcyBhcmUgaW4gbm8g
d2F5IHNldCBpbg0KPj4+Pj4gc3RvbmUsIHRoZXkgc2hvdWxkIGp1c3QgYmUgc2VlbiBhcyBhIHN0
YXJ0aW5nIHBvaW50IGZvciBvdXIgd29yay4gSWYNCj4+Pj4+IHlvdSB3b3VsZCBsaWtlIHRvIHBy
b3Bvc2UgdGhlIFJHIHRoYXQgd2Ugc2hvdWxkIHN0YXJ0IHdvcmtpbmcgb24gYQ0KPj4+Pj4gZGVw
bG95bWVudCBkb2N1bWVudCB5b3UgYXJlIG1vc3Qgd2VsY29tZSB0byBkbyBzbywgdGhhdCB3aWxs
IG1vc3QNCj4+Pj4+IGNlcnRhaW5seSBiZSBpbiBzY29wZSBmb3Igb3VyIGRpc2N1c3Npb24gaW4g
QXRsYW50YS4NCj4+Pj4+IA0KPj4+Pj4gQXMgYSBnZW5lcmFsIGNvbW1lbnQgSSBhbHNvIGxpa2Ug
dG8gbWVudGlvbiB0aGF0IHdlIGFzIGFuIFJHIGFyZSBub3QNCj4+Pj4+IGJvdW5kIGJ5IGFsbCB0
aGUgcnVsZXMgdGhhdCBhcHBseSB0byBJRVRGIFdHcywgZS5nLiB3ZSBhcmUgZnJlZSB0bw0KPj4+
Pj4gZGlzY3VzcyBsYXRlIGNvbnRyaWJ1dGlvbnMgcHJvZHVjZWQgYWZ0ZXIgdGhlIElFVEYgZHJh
ZnQgZGVhZGxpbmVzLiBTbw0KPj4+Pj4gaWYgcGVvcGxlIGZpbmQgdGhlIHRpbWUgdG8gd3JpdGUg
dXAgc29tZSBtYXRlcmlhbCBmb3IgdGhlIElDTlJHIGFmdGVyDQo+Pj4+PiB0aGUgSUVURiBkcmFm
dHMgYXJlIGRvbmUgdGhleSBhcmUgd2VsY29tZSB0byBhbm5vdW5jZSBpdCB0byB0aGUgSUNOUkcN
Cj4+Pj4+IG1haWxpbmcgbGlzdC4gSWYgdGhlIGdyb3VwIGFncmVlcyB3ZSBhcmUgZnJlZSB0byBk
aXNjdXNzIGFsc28gc3VjaA0KPj4+Pj4gbWF0ZXJpYWwgYXQgb3VyIG1lZXRpbmcsDQo+Pj4+PiAN
Cj4+Pj4+ICAgICBCzpPCtnJqZQ0KPj4+Pj4gDQo+Pj4+PiAxOCBva3QgMjAxMiBrbC4gMDM6NTYg
c2tyZXYgIlNldW5nLUlrIExlZSIgPHNldW5naWtsZWVAZXRyaS5yZS5rcj46DQo+Pj4+PiANCj4+
Pj4+PiBEZWFyIGljbnJnIGNvbGxlYWd1ZXMsDQo+Pj4+Pj4gDQo+Pj4+Pj4gUmVnYXJkaW5nIHRo
ZSBSRyBkb2N1bWVudHMsIGRvbid0IHdlIHRvdWNoIGFueSBpc3N1ZXMgb24gSUNODQo+Pj4+PiBk
ZXBsb3ltZW50cz8NCj4+Pj4+PiANCj4+Pj4+PiBBcyB3ZSBoYXZlIHNlZW4gaW4gdGhlIHByZXNl
bnRhdGlvbiBieSBaVEUgaW4gVmFuY291dmVyLCBJU1BzIGFyZQ0KPj4+Pj4+IGludGVyZXN0ZWQg
aW4gdGhlIHNob3J0LXRlcm0gYXBwcm9hY2hlcyB0byBJQ04uDQo+Pj4+Pj4gVGhvdWdoIHRoZSB0
cmFkaXRpb25hbCBJQ04gYXBwcm9hY2hlcyAoc3VjaCBhcyBDQ04vTkROKSBoYXZlDQo+Pj4+Pj4g
cHJvdmlkZWQgSVNQcyBhIGxhZGRlciBvdXQgb2YgZHVtYi1waXBlcywgSVNQcyBtYXkgaGF2ZSBk
aWZmaWN1bHRpZXMNCj4+Pj4+PiBvbiBjbGVhbi1zbGF0ZSBhcHByb2FjaGVzIG9mIElDTi4NCj4+
Pj4+PiBJTUhPLCBiYXNlZCBvbiBvdXIgc3VydmV5cyBvbiBJU1AgUiZEIGFwcHJvYWNoZXMgdG8g
SUNOLCBLb3JlYW4gSVNQcw0KPj4+Pj4+IGFyZSBpbiB0aGUgc2ltaWxhciBzaXR1YXRpb24uDQo+
Pj4+Pj4gDQo+Pj4+Pj4gSW4gdGhpcyBtb3RpdmF0aW9uLCBJIGhhdmUgaW50ZXJlc3RzIGluIElD
TiBkZXBsb3ltZW50IHN0cmF0ZWdpZXMNCj4+Pj4+PiAoc3VjaCBhcyBJQ04gb3ZlciBJUCBvciBJ
Q04gb3ZlciBTRE4gYXMgc2hvcnQtdGVybSBhcHByb2FjaGVzKSBidXQNCj4+Pj4+PiBubyBpZGVh
IHdoaWNoIFJHIGRvY3VtZW50IHdvdWxkIGNvdmVyIHRoZSBkZXBsb3ltZW50IGlzc3VlcywgZXZl
bg0KPj4+Pj4+IHdoZXRoZXIgaWNucmcgd2lsbCBjb3ZlciB0aGUgZGVwbG95bWVudCBpc3N1ZSBv
ciBub3QuDQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+Pj4gMjAxMi8xMC84IELOk8K2
cmplIE9obG1hbiA8Qm9yamUuT2hsbWFuQGVyaWNzc29uLmNvbT46DQo+Pj4+Pj4+IFRoZSBuZXh0
IElDTlJHIHdpbGwgYmUgaGVsZCBhdCAgSUVURiA4NSwgQXRsYW50YSwgR2VvcmdpYSwgVVNBLA0K
Pj4+Pj4gTm92ZW1iZXINCj4+Pj4+Pj4gNC05LCAyMDEyDQo+Pj4+Pj4+ICAgICAqIE1lZXRpbmcg
dGltZTogV0VETkVTREFZIDEzLjAwLTE1LjQwIChwcmVsKQ0KPj4+Pj4+PiANCj4+Pj4+Pj4gVGhl
IG1haW4gZGlzY3Vzc2lvbiBhdCB0aGUgbWVldGluZyB3aWxsIGJlIHRoZSB0aHJlZSBkb2N1bWVu
dHMgdGhhdA0KPj4+Pj4+PiB0aGUNCj4+Pj4+IFJHDQo+Pj4+Pj4+IGhhcyBzZXQgb3V0IHRvIHBy
b2R1Y2UuDQo+Pj4+Pj4+IA0KPj4+Pj4+PiBJQ04gU3VydmV5IGRvY3VtZW50DQo+Pj4+Pj4+IA0K
Pj4+Pj4+PiBBIGRvY3VtZW50IHRoYXQgcHJvdmlkZXMgYSBzdXJ2ZXkgb2YgZGlmZmVyZW50IGFw
cHJvYWNoZXMgYW5kDQo+Pj4+PiB0ZWNobmlxdWVzDQo+Pj4+Pj4+IA0KPj4+Pj4+PiBJQ04gUHJv
YmxlbSBzdGF0ZW1lbnQNCj4+Pj4+Pj4gDQo+Pj4+Pj4+IEEgZG9jdW1lbnQgdGhhdCBkZXNjcmli
ZXMgdGhlIElDTiBwcm9ibGVtIHN0YXRlbWVudCwgdGhlIG1haW4NCj4+Pj4+IGNvbmNlcHRzIGFu
ZA0KPj4+Pj4+PiByZXNlYXJjaCBjaGFsbGVuZ2VzIGluIGRlcHRoLg0KPj4+Pj4+PiANCj4+Pj4+
Pj4gSUNOIEJhc2VsaW5lIFNjZW5hcmlvcw0KPj4+Pj4+PiANCj4+Pj4+Pj4gQSBkb2N1bWVudCB0
aGF0IGRlZmluZXMgcmVmZXJlbmNlIGJhc2VsaW5lIHNjZW5hcmlvcyB0byBlbmFibGUNCj4+Pj4+
IHBlcmZvcm1hbmNlDQo+Pj4+Pj4+IGNvbXBhcmlzb25zIGJldHdlZW4gZGlmZmVyZW50IGFwcHJv
YWNoZXMuDQo+Pj4+Pj4+IA0KPj4+Pj4+PiBQZW9wbGUgYXJlIGVuY291cmFnZWQgdG8gcHJlc2Vu
dCB0aGVpciB2aWV3cyBvbiB3aGF0IHRoZXkgdGhpbmsNCj4+Pj4+Pj4gc2hvdWxkDQo+Pj4+PiBi
ZQ0KPj4+Pj4+PiB0aGUgY29udGVudHMgb2YgdGhlc2UgZG9jdW1lbnRzLiBFYXJseSBjb250cmli
dXRpb25zIChpbiBidWxsZXQNCj4+Pj4+Pj4gZm9ybSBvciBhcyBkcmFmdCB0ZXh0KSBhcmUgd2Vs
Y29tZSBib3RoIG9uIHRoZSBtYWlsaW5nIGxpc3QgYW5kIHRoZSB3aWtpLg0KPj4+Pj4gUHJlc2Vu
dGF0aW9ucw0KPj4+Pj4+PiBvZiBkcmFmdCBtYXRlcmlhbCBhcmUgd2VsY29tZSBhdCB0aGUgbWVl
dGluZy4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IE1vc3QgbGlrZWx5IHdlIHdpbGwgYWxzbyBoYXZlIHRp
bWUgdG8gZGlzY3VzcyBvbmUgb3IgdHdvIHNwZWNpZmljDQo+Pj4+Pj4+IHRlY2huaWNhbCB0b3Bp
Y3MgYXQgdGhlIG1lZXRpbmcuIFByb3Bvc2FscyBmb3Igc3VjaCB0b3BpY3MgYXMgd2VsbA0KPj4+
Pj4+PiBhcyBwcmVzZW50YXRpb25zIGFyZSBpbnZpdGVkLg0KPj4+Pj4+PiANCj4+Pj4+Pj4gQXMg
d2UgYXJlIGV4cGVjdGVkIHRvIHB1Ymxpc2ggb3VyIGFnZW5kYSBieSAyMDEyLTEwLTI0IChXZWRu
ZXNkYXkpDQo+Pj4+Pj4+IHdlDQo+Pj4+PiB3b3VsZA0KPj4+Pj4+PiBsaWtlIHRvIGhhdmUgeW91
ciBpbnB1dCBieSBTdW5kYXkgMjAxMi0xMC0yMS4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IELOk8K2cmpl
LCBEYXZlICYgRGlyaw0KPj4+Pj4+PiANCj4+Pj4+Pj4gDQo+Pj4+Pj4+IElDTiBSRyBXaWtpOg0K
Pj4+Pj4+PiANCj4+Pj4+Pj4gaHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvZ3JvdXAvaXJ0Zi90
cmFjL3dpa2kvaWNucmcNCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+PiBpY25yZyBtYWlsaW5nIGxpc3QNCj4+IGljbnJnQGlydGYub3JnDQo+PiBo
dHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQo+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGljbnJnIG1haWxpbmcgbGlz
dA0KPiBpY25yZ0BpcnRmLm9yZw0KPiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2ljbnJnDQoNCg==

From i.psaras@ucl.ac.uk  Wed Oct 24 08:58:34 2012
Return-Path: <i.psaras@ucl.ac.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C48E421F8C6E for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 08:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[AWL=-0.597, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0yihSzjKzwy for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 08:58:28 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAF421F8853 for <icnrg@irtf.org>; Wed, 24 Oct 2012 08:58:27 -0700 (PDT)
Received: from mail120-va3-R.bigfish.com (10.7.14.238) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.23; Wed, 24 Oct 2012 15:58:26 +0000
Received: from mail120-va3 (localhost [127.0.0.1])	by mail120-va3-R.bigfish.com (Postfix) with ESMTP id 6FE6B3400F6; Wed, 24 Oct 2012 15:58:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.9.135; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0104HT020.eurprd01.prod.exchangelabs.com; RD:none; EFVD:NLI
X-SpamScore: -29
X-BigFish: PS-29(zzbb2dI98dI9371Ic89bh936eI542M1432Izz1d18h1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h8e2h8e3h93fhd25he5bhf0ah1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537hbe9i1155h)
Received: from mail120-va3 (localhost.localdomain [127.0.0.1]) by mail120-va3 (MessageSwitch) id 1351094303443670_31292; Wed, 24 Oct 2012 15:58:23 +0000 (UTC)
Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.237])	by mail120-va3.bigfish.com (Postfix) with ESMTP id 66C05400083; Wed, 24 Oct 2012 15:58:23 +0000 (UTC)
Received: from DB3PRD0104HT020.eurprd01.prod.exchangelabs.com (157.55.9.135) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 24 Oct 2012 15:58:21 +0000
Received: from dhcp-186-251.internal.eduroam.ucl.ac.uk (144.82.186.251) by pod51002.outlook.com (10.4.156.49) with Microsoft SMTP Server (TLS) id 14.15.129.3; Wed, 24 Oct 2012 15:58:19 +0000
MIME-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="utf-8"
From: Ioannis Psaras <i.psaras@ucl.ac.uk>
In-Reply-To: <5087B162.9040305@intracom.com>
Date: Wed, 24 Oct 2012 16:58:17 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <1745C882-C9B9-4E9E-9F1D-77CDC074C238@ucl.ac.uk>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com>
To: <spis@intracom.com>
X-Mailer: Apple Mail (2.1084)
X-Originating-IP: [144.82.186.251]
X-UCLLIVE-SCLRULE: HASRUN
X-OriginatorOrg: ucl.ac.uk
Cc: Ignacio.Solis@parc.com, icnrg@irtf.org, Bengt Ahlgren <bengta@sics.se>, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 15:58:35 -0000

Hi Spiros,

I don't think ICN (caching in particular) and the CDN model have =
conflicting goals: there is (and will always be) a need for permanently =
storing content. Whether performance can improve due to caching is a =
different discussion IMO and not necessarily in the interest of CDNs. =
This is (part of) the reason why we have CDNs anyway - otherwise ISPs =
could deploy their own servers/CDNs (which they do to an extend, but =
always within their own domain).

ICN (caching) may improve performance and this is where ISPs should =
focus on to see whether it's good/profitable for them to deploy.

Regards,
Yiannis.

On 24 Oct 2012, at 10:14, Spiros Spirou wrote:

> Hi Bengt!
>=20
> If ICN does not provide any sort of better-than-best-effort delivery, =
then it seems (to me at least) that neither ISPs nor content providers =
have any significant incentive to adopt ICN. They can simply stick with =
the entrenched CDN technology and business model where all stekeholders =
(end-users, ISPs, CDN operators, and content providers/owners) seem to =
be happy enough.
>=20
> If, on the other hand, ICN does provide guarantees in delivery, then =
ICN and CDN seem likely to become competitors, as they would be offering =
a very similar service. The question for me is why would ISPs risk =
losing existing revenue from CDN operators in favor of capital =
expenditure for deploying ICN? There's of course the hope that content =
providers would be lured away from CDN, but this seems realistic only if =
ICN is cheaper or somehow better than CDN.
>=20
> Spiros
>=20
> On 23/10/2012 10:39 =CE=BC=CE=BC, Bengt Ahlgren wrote:
>> I agree with Nacho, but would like to add an angle to this =
discussion!
>>=20
>> CDN, IMO, is more a business model than a particular set of protocols
>> and services.  CDN operators agree to deliver the content of =
particular
>> publishers for a fee at some level of service.  Whether this is done =
on
>> an IP network or something else is not really important.
>>=20
>> ICN is a different set of protocols and services compared to IP, but =
not
>> really a specific business model, although it may change the business
>> playing field somewhat.  So, even though we can argue that ICN is =
good
>> for content distribution, I don't think the CDN business becomes
>> redundant.  There will still be content publishers that want to make
>> sure that their content is delivered at some known level of service =
to
>> their customers.  The "normal" ICN caching simply corresponds to =
current
>> best-effort IP packet forwarding, with similar non-guarantee of =
service.
>>=20
>> Having said that, when the CDN folks now are starting to define
>> particular protocols and interfaces (e.g., CDNI), they are working on
>> stuff that touches ICN, but for supporting their particular purpose =
(the
>> CDN business model).
>>=20
>> Bengt
>>=20
>> <Ignacio.Solis@parc.com> writes:
>>=20
>>> Hi Brian.
>>>=20
>>> You are right that for a subset of cases it seems like ICN is just
>>> CDN, but that would be missing a lot of the picture.
>>>=20
>>> First, can you describe what the properties of native ICN and
>>> non-native ICN are?  Is there no "router caching" in non-native ICN?
>>>=20
>>> A few of the things that don't seem to fit into traditional CDNs =
(with
>>> my limited knowledge of state-of-the art CDNs) are:
>>>=20
>>> - Peer-to-peer.  How can CDNs help two nodes communicate without
>>> infrastructure?  If two nodes meet in the field (such as in the =
DARPA
>>> CBMEN program, or two phones on a plane or tunnel or ship), how can
>>> CDNs help them exchange information?
>>>=20
>>> - Security. How can CDNs ensure the provenance of the data?
>>>=20
>>> - Disruption tolerance. How can CDNs enable data-muling?
>>>=20
>>> - Flow control. How can you change the way we do flow-control using =
CDNs?
>>>=20
>>> - Lone hit. How can CDNs help distribute data that was previously
>>> unknown to the CDN. For example, from a random webpage.
>>>=20
>>>=20
>>> Granted, some of those are somewhat possible using CDNs. Some of =
those
>>> are possible with a little bit of work on CDNs and some are possible
>>> with a lot of work.
>>>=20
>>> Everything is possible.
>>>=20
>>> But, we're going to get to a point where we're changing so much that
>>> what we started with is unrecognizable.  Starting with CDNs is
>>> limiting what we can do and how we do it.  The model many ICNs take =
is
>>> a clean slate one. And as far as possible, we try to learn the =
lessons
>>> of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,
>>> OSPFs, etc.
>>>=20
>>> Caching at the router level is one of the many potentially =
beneficial
>>> (but not-required) characteristics of ICNs.
>>>=20
>>> If we talk about a specific ICN architecture (like CCN) we can talk
>>> about specific advantages and disadvantages, tradeoffs made, work =
done
>>> so far, work planned and work yet to be done.
>>>=20
>>> Nacho
>>>=20
>>>=20
>>>=20
>>> --
>>> Nacho (Ignacio) Solis
>>> Senior Research Scientist
>>> Palo Alto Research Center (PARC)
>>> +1(650) 812-4458
>>> Ignacio.Solis@parc.com
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Oct 18, 2012, at 2:54 PM, "Field, Brian" =
<Brian_Field@cable.comcast.com>
>>>  wrote:
>>>=20
>>>> Does anyone (beside me) think that a CDN effectively is already =
doing "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).  =
 I think of CDN and native ICN (where the router is caching and =
forwarding at the ICN level) nearly identical forwarding paradigms just =
operating at different levels in the stack.
>>>>=20
>>>> There's work in standardizing the intra-CDN  and inter-CDN control =
plan (in CDN-I and elsewhere).  IMO, it would be useful if we had the =
same control protocol operating in both the CDN and ICN domains and the =
"transition" was just changing the layer at which forwarding occurred.
>>>>=20
>>>> Brian
>>>>=20
>>>>=20
>>>> -----Original Message-----
>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf Of Will Liu (Shucheng)
>>>> Sent: Thursday, October 18, 2012 3:08 AM
>>>> To: B=CE=93=C2=B6rje Ohlman; Seung-Ik Lee
>>>> Cc: =CE=B4=C2=BB=C2=BB=CE=B5=C2=A9=C2=A7; icnrg; Jianping Wang
>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>=20
>>>> Hi,
>>>>=20
>>>> My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic =
which ISPs will definitely be interested in. Here are our 2-cents.
>>>>=20
>>>> The evolvement of ICN may take the following three implementations: =
integrated with IP, over IP and over SDN. These strategies all can help =
the ISP shift from the traditional IP to ICN. The only question is which =
one is the best choice for large scale deployment?
>>>>=20
>>>> Integrated with IP strategy extends the existing IP protocol (IP =
option) to support ICN. The updated IP router, called content router, =
will deal with such special packets. However, many routers with no =
support of such extension may directly drop the packets with an unknown =
IP option.
>>>>=20
>>>> ICN over IP strategy uses an overlay approach. Content-related =
operation will be performed on the high layer and Content-related =
information will be sent through a tunnel. Due to the limited knowledge =
of physical topology and unnecessary packet =
encapsulation/disconsolation, the efficiency may be limited.
>>>>=20
>>>> ICN over SDN strategy exploits SDN controller to perform =
content-related operation. However, SDN itself is an ongoing approach =
and is typically used in a local domain. The performance in a large =
scale deployment is unknown.
>>>>=20
>>>> Will
>>>>=20
>>>>> -----Original Message-----
>>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf
>>>>> Of B?rje Ohlman
>>>>> Sent: Thursday, October 18, 2012 10:55 AM
>>>>> To: Seung-Ik Lee
>>>>> Cc: icnrg
>>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>>=20
>>>>> Dear Seung-Ik,
>>>>>=20
>>>>> I think you bring up a very good point. I agree that deployment =
and
>>>>> migration issues are very important. I also agree that they don't =
seem
>>>>> like a good fit for any of the currently proposed ICNRG documents.
>>>>>=20
>>>>> The three documents listed as current work items are in no way set =
in
>>>>> stone, they should just be seen as a starting point for our work. =
If
>>>>> you would like to propose the RG that we should start working on a
>>>>> deployment document you are most welcome to do so, that will most
>>>>> certainly be in scope for our discussion in Atlanta.
>>>>>=20
>>>>> As a general comment I also like to mention that we as an RG are =
not
>>>>> bound by all the rules that apply to IETF WGs, e.g. we are free to
>>>>> discuss late contributions produced after the IETF draft =
deadlines. So
>>>>> if people find the time to write up some material for the ICNRG =
after
>>>>> the IETF drafts are done they are welcome to announce it to the =
ICNRG
>>>>> mailing list. If the group agrees we are free to discuss also such
>>>>> material at our meeting,
>>>>>=20
>>>>>     B=CE=93=C2=B6rje
>>>>>=20
>>>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" =
<seungiklee@etri.re.kr>:
>>>>>=20
>>>>>> Dear icnrg colleagues,
>>>>>>=20
>>>>>> Regarding the RG documents, don't we touch any issues on ICN
>>>>> deployments?
>>>>>>=20
>>>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs are
>>>>>> interested in the short-term approaches to ICN.
>>>>>> Though the traditional ICN approaches (such as CCN/NDN) have
>>>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have =
difficulties
>>>>>> on clean-slate approaches of ICN.
>>>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean =
ISPs
>>>>>> are in the similar situation.
>>>>>>=20
>>>>>> In this motivation, I have interests in ICN deployment strategies
>>>>>> (such as ICN over IP or ICN over SDN as short-term approaches) =
but
>>>>>> no idea which RG document would cover the deployment issues, even
>>>>>> whether icnrg will cover the deployment issue or not.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 2012/10/8 B=CE=93=C2=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>>>> November
>>>>>>> 4-9, 2012
>>>>>>>     * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>>>=20
>>>>>>> The main discussion at the meeting will be the three documents =
that
>>>>>>> the
>>>>> RG
>>>>>>> has set out to produce.
>>>>>>>=20
>>>>>>> ICN Survey document
>>>>>>>=20
>>>>>>> A document that provides a survey of different approaches and
>>>>> techniques
>>>>>>>=20
>>>>>>> ICN Problem statement
>>>>>>>=20
>>>>>>> A document that describes the ICN problem statement, the main
>>>>> concepts and
>>>>>>> research challenges in depth.
>>>>>>>=20
>>>>>>> ICN Baseline Scenarios
>>>>>>>=20
>>>>>>> A document that defines reference baseline scenarios to enable
>>>>> performance
>>>>>>> comparisons between different approaches.
>>>>>>>=20
>>>>>>> People are encouraged to present their views on what they think
>>>>>>> should
>>>>> be
>>>>>>> the contents of these documents. Early contributions (in bullet
>>>>>>> form or as draft text) are welcome both on the mailing list and =
the wiki.
>>>>> Presentations
>>>>>>> of draft material are welcome at the meeting.
>>>>>>>=20
>>>>>>> Most likely we will also have time to discuss one or two =
specific
>>>>>>> technical topics at the meeting. Proposals for such topics as =
well
>>>>>>> as presentations are invited.
>>>>>>>=20
>>>>>>> As we are expected to publish our agenda by 2012-10-24 =
(Wednesday)
>>>>>>> we
>>>>> would
>>>>>>> like to have your input by Sunday 2012-10-21.
>>>>>>>=20
>>>>>>> B=CE=93=C2=B6rje, Dave & Dirk
>>>>>>>=20
>>>>>>>=20
>>>>>>> ICN RG Wiki:
>>>>>>>=20
>>>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg



From damien.saucez@gmail.com  Wed Oct 24 13:41:23 2012
Return-Path: <damien.saucez@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B5121F8947 for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 13:41:23 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyvWvDyeRocB for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 13:41:22 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id EE39621F8A2F for <icnrg@irtf.org>; Wed, 24 Oct 2012 13:41:21 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id 16so776225wgi.19 for <icnrg@irtf.org>; Wed, 24 Oct 2012 13:41:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=KrsPvx7X4WWDi+Sah2N/RYGhCzKTbzhhOt9/ZVyCOsk=; b=knx6pGa9twaK6/ALnyAwm0kQdu7UKfvdEYyPYSOJILO+b7D3hu6mTL2q5MLXwpogJU h4OJL+uXH/7qEn+3LItdthQjGOxqa2UcphWJii3sDIIAsB0pPFHgpLoiRlLvLJkzbusC 02uztLtdzmng+/A21l/e65vJiDqZ5AfmWEKVhsK+LcHE4Mq5I2Ru/qWuAHGDWhSHA+JW XMzHBnIQGdoPd65jqLHrBOJVr5ynDdS00dsO9SlVkItMWHmDNsuhddYtB8eHT23f4WIS YnKiSpcdpjSF7vxWF1Fj2rGKLghl6Krj1eeHkvnHsKqic1uX8CvdEGQ7CXJ2k2ofVnRN TJdA==
Received: by 10.216.134.218 with SMTP id s68mr10831975wei.72.1351111281100; Wed, 24 Oct 2012 13:41:21 -0700 (PDT)
Received: from [172.16.139.253] (10.189.101.84.rev.sfr.net. [84.101.189.10]) by mx.google.com with ESMTPS id dt9sm6200396wib.1.2012.10.24.13.41.18 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 13:41:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com>
Date: Wed, 24 Oct 2012 22:41:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com>
To: Ignacio.Solis@parc.com
X-Mailer: Apple Mail (2.1499)
Cc: icnrg@irtf.org, spis@intracom.com, bengta@sics.se, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 20:41:23 -0000

Hello,
On 24 Oct 2012, at 17:56, Ignacio.Solis@parc.com wrote:

> "Best-effort" for some ICNs has different characteristics that IP =
best-effort, so comparing it directly might not be accurate.   For all =
we know ICNs best-effort is better-than-IP-best-effort.

How do you define better-than? What is the metric? Which criterion?

Thank you in advance for the clarification.

Damien Saucez=

From Ignacio.Solis@parc.com  Wed Oct 24 14:14:56 2012
Return-Path: <Ignacio.Solis@parc.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9580921F863B for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 14:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1K2uoXFpzV+r for <icnrg@ietfa.amsl.com>; Wed, 24 Oct 2012 14:14:56 -0700 (PDT)
Received: from omega.xerox.com (omega.xerox.com [13.1.64.95]) by ietfa.amsl.com (Postfix) with ESMTP id 15F8C21F85AF for <icnrg@irtf.org>; Wed, 24 Oct 2012 14:14:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by omega.xerox.com (Postfix) with ESMTP id 664BD2540BA; Wed, 24 Oct 2012 14:14:55 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at parc.com
Received: from omega.xerox.com ([127.0.0.1]) by localhost (omega.xerox.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0Jo-tTag1CU; Wed, 24 Oct 2012 14:14:55 -0700 (PDT)
Received: from exchangehub.parc.xerox.com (e2010hub1.parc.xerox.com [13.2.12.22]) by omega.xerox.com (Postfix) with ESMTPS id 3ECCF2540B7; Wed, 24 Oct 2012 14:14:55 -0700 (PDT)
Received: from E2010DAG5.corp.ad.parc.com ([fe80::3d0b:7158:aec4:e05e]) by e2010hub1.corp.ad.parc.com ([fe80::8945:a39d:8c92:373f%12]) with mapi id 14.02.0318.004; Wed, 24 Oct 2012 14:14:54 -0700
From: <Ignacio.Solis@parc.com>
To: <damien.saucez@gmail.com>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNsVYeAHIgkogGRUiJNLSWYIgNIJfIooYAgABwSACAAE+yAIAACWSA
Date: Wed, 24 Oct 2012 21:14:54 +0000
Message-ID: <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com> <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com>
In-Reply-To: <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.244.190.163]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <605E29673F03994785E559CD0F4C60A2@ad.parc.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: icnrg@irtf.org, spis@intracom.com, bengta@sics.se, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:14:56 -0000

On Oct 24, 2012, at 4:41 PM, Damien Saucez <damien.saucez@gmail.com>
 wrote:

> Hello,
> On 24 Oct 2012, at 17:56, Ignacio.Solis@parc.com wrote:
>=20
>> "Best-effort" for some ICNs has different characteristics that IP best-e=
ffort, so comparing it directly might not be accurate.   For all we know IC=
Ns best-effort is better-than-IP-best-effort.
>=20
> How do you define better-than? What is the metric? Which criterion?
>=20
> Thank you in advance for the clarification.

That is exactly my question, we haven't defined that.

How is multicast best-effort different than non-multicast best effort?  You=
 can't compare easily.  This was exactly my point to the critique of:  "If =
ICN does not provide any sort of better-than-best-effort delivery, then it =
seems (to me at least) that neither ISPs nor content providers have any sig=
nificant incentive to adopt ICN." that Spiros brought up. I was commenting =
on the better-than-best-effort qualification.

I could construct scenarios where best effort ICN (CCN in my example) can a=
chieve better-than-IP-best-effort for delivery, delay and availability.  I =
could also construct scenarios where IP might have less overhead. I was jus=
t pointing out that comparing "best-efforts" in a general is not trivial.

ICN is still a research topic. It doesn't have all the answers and there ar=
e many open questions. Yes, there is some overlap with CDNs, but they are n=
ot in direct competition.


Nacho


--
Nacho (Ignacio) Solis
Senior Research Scientist
Palo Alto Research Center (PARC)
+1(650) 812-4458
Ignacio.Solis@parc.com=

From borje.ohlman@ericsson.com  Thu Oct 25 01:00:54 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD7921F89AD for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 01:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8nJex5eto2e for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 01:00:53 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id D904C21F89AF for <icnrg@irtf.org>; Thu, 25 Oct 2012 01:00:52 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-ec-5088f1b3de15
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 31.08.17130.3B1F8805; Thu, 25 Oct 2012 10:00:51 +0200 (CEST)
Received: from dhcp-147-214-183-183.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.96) with Microsoft SMTP Server id 8.3.279.1; Thu, 25 Oct 2012 10:00:51 +0200
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
In-Reply-To: <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>
Date: Thu, 25 Oct 2012 10:00:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-ID: <FAFF11DF-6427-4C32-88D2-A7DC78BA5C23@ericsson.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com> <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com> <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>
To: "Ignacio.Solis@parc.com> <Ignacio.Solis@parc.com" <Ignacio.Solis@parc.com>, Damien Saucez <damien.saucez@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvre7mjx0BBp03FSw63mhZ3Di2kdFi 0mIti52zdzJZvNwxm8Vi8aUtrA5sHs8f+3rsnHWX3ePAmpnsHpM3HmbzeDVjCZNH77HfbAFs UVw2Kak5mWWpRfp2CVwZjX+vMhc0SlQsPviIpYHxhHAXIweHhICJxJu7pV2MnECmmMSFe+vZ uhi5OIQETjFK/Du8nwXCOcAo8eX+fVaQKmEBfYkbGzeygDTzChhKdB7OAQkzC+hJ3Jg6hQ3E ZhNwlHjcsh6snFMgSGLbt5dgNouAqsSM1XOZQWYyCzQwSnTv3cwE0awtsWzha2YQm1fAXuLG 0x2MILaQQC+rxOJvaSC2iEC1xPyZp9khLpWVuN08gR2iRk1ixsdHTBMYBWchnDQLyUmzkGxY wMi8ilE4NzEzJ73cXC+1KDO5uDg/T684dRMjMOQPbvltsINx032xQ4zSHCxK4rx6qvv9hQTS E0tSs1NTC1KL4otKc1KLDzEycXBKNTD6STv0s3tdqH80Y8pzn19taxcGl6pmZCg2p8vKnk85 +XZd+bznp3IsZ3jefKii4SHuNmlKiKtM4XkV1513dkhun7TJhfd249O6FjeHPp3XUw9cmZB9 QsD1wSZHB8EUrd5fmd9vTkz+fZPxpXGBWvKGzyu+O1yZ7tk/aTfnLvbbh+ZaWz6pm2mkxFKc kWioxVxUnAgAWa4BYkcCAAA=
Cc: Spiros Spirou <spis@intracom.com>, icnrg <icnrg@irtf.org>, Bengt Ahlgren <bengta@sics.se>, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 08:00:54 -0000

Some comments on this discussion. It is clearly important to define =
metrics for comparing the how efficiently content can be distributed =
using different solutions. We should make sure to do it in such a way, =
that in addition to compare a specific ICN technology with existing CDN =
solutions, we are also able to compare different ICN solutions with each =
other. That is what we are aiming for with the 'ICN Baseline Scenarios' =
document.

A second comment is that, even if providing inherent CDN functionality =
is a key feature of ICN, I don't think it is the most important feature =
of ICN. To me the idea of an application independent naming scheme for =
information/data objects bears even greater potential, especially for =
application developers that more easily can reuse information bases from =
one application to another. Also having the pub/sub like API to ICN =
opens the door to include a lot of nice features into the network in a =
way that is transparent to the application developers. Examples of such =
features include p2p-functionality, seamless mobility, =
DTN-functionality, ...

	B=F6rje

On 24 okt 2012, at 23:14, <Ignacio.Solis@parc.com>
 <Ignacio.Solis@parc.com> wrote:

> On Oct 24, 2012, at 4:41 PM, Damien Saucez <damien.saucez@gmail.com>
> wrote:
>=20
>> Hello,
>> On 24 Oct 2012, at 17:56, Ignacio.Solis@parc.com wrote:
>>=20
>>> "Best-effort" for some ICNs has different characteristics that IP =
best-effort, so comparing it directly might not be accurate.   For all =
we know ICNs best-effort is better-than-IP-best-effort.
>>=20
>> How do you define better-than? What is the metric? Which criterion?
>>=20
>> Thank you in advance for the clarification.
>=20
> That is exactly my question, we haven't defined that.
>=20
> How is multicast best-effort different than non-multicast best effort? =
 You can't compare easily.  This was exactly my point to the critique =
of:  "If ICN does not provide any sort of better-than-best-effort =
delivery, then it seems (to me at least) that neither ISPs nor content =
providers have any significant incentive to adopt ICN." that Spiros =
brought up. I was commenting on the better-than-best-effort =
qualification.
>=20
> I could construct scenarios where best effort ICN (CCN in my example) =
can achieve better-than-IP-best-effort for delivery, delay and =
availability.  I could also construct scenarios where IP might have less =
overhead. I was just pointing out that comparing "best-efforts" in a =
general is not trivial.
>=20
> ICN is still a research topic. It doesn't have all the answers and =
there are many open questions. Yes, there is some overlap with CDNs, but =
they are not in direct competition.
>=20
>=20
> Nacho
>=20
>=20
> --
> Nacho (Ignacio) Solis
> Senior Research Scientist
> Palo Alto Research Center (PARC)
> +1(650) 812-4458
> Ignacio.Solis@parc.com
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From borje.ohlman@ericsson.com  Thu Oct 25 01:20:53 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89F1421F89C6 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 01:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-HXlEGFGg26 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 01:20:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1865721F89B0 for <icnrg@irtf.org>; Thu, 25 Oct 2012 01:20:51 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-8c-5088f662c781
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id C2.49.04547.266F8805; Thu, 25 Oct 2012 10:20:50 +0200 (CEST)
Received: from dhcp-147-214-183-183.ki.sw.ericsson.se (153.88.115.8) by smtps.internal.ericsson.com (153.88.115.84) with Microsoft SMTP Server id 8.3.279.1; Thu, 25 Oct 2012 10:20:50 +0200
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Oct 2012 10:20:54 +0200
Message-ID: <298D68FB-5E93-4832-9163-2574A8F84A1B@ericsson.com>
To: icnrg <icnrg@irtf.org>
MIME-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgluLIzCtJLcpLzFFi42KZGfG3VjfpW0eAwcQ2K4uHj9Itds7eyWTR uuIRuwOzx5TfG1k9Jm88zOYx49hL9gDmKC6blNSczLLUIn27BK6MhmWTmAvu8VUcbznH3MD4 lruLkZNDQsBEomHnPUYIW0ziwr31bF2MXBxCAqcYJZ6s7YRyDjBK7P63nRmkik3AUeL90wOs IDazgJ7EjalT2CBsbYllC18D1XBwCAuoS6xp5AMJswioSkz42c0OYvMK2EucOjCdEWQms8By Rol3zz+CJUQEpCQ27b3LBtLLK2Ao0Xk4B+IgWYnbzRPASoQE1CSOfzjGPIGRfxaSzbOQbJ6F 0L2AkXkVo3BuYmZOermRXmpRZnJxcX6eXnHqJkZgKB7c8lt1B+OdcyKHGKU5WJTEea237vEX EkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwMij1bpxo+hbna6+Tn4WYfv2QuaVblIv1O/9/q20 RK1HqLVaRLrYM9n23coZbD2X3p77wnvBU6lqzjX7n+sfp82csfzgC6MHz7X2bJ/9RnDhcv2/ D5zC/nY/+HeobMUmpg05999J3r5akaRWUX3AvvLS2pxNa44bXurxyXdL2d/o+vBx1IkJ3QeU WIozEg21mIuKEwGiLI1pEwIAAA==
Cc: Dave Oran <oran@cisco.com>, Johan Myrberger <johan.myrberger@ericsson.com>, Thomas Edwall <thomas.edwall@ericsson.com>, Dirk Kutscher <Dirk.Kutscher@neclab.eu>
Subject: [icnrg] ICNRG interim meeting planning
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 08:20:53 -0000

Even though we are just doing the planning for the Atlanta meeting it is =
also time to start planning for an ICNRG interim meeting, this so we can =
agree on it in Atlanta.

We discussed some options at the last ICNRG meeting, they are also =
listed on the Wiki. There has not been any great enthusiasm for any of =
those options. But now we think we have a good proposal.=20

There will be a final demo from the SAIL project in conjunction with a =
future networks workshop focusing on ICN, including regulatory issues =
relating to ICN. The workshop will be organized by SAIL and a Swedish =
ICN project called Efraim (partners include TV broadcasters (SVT, TV4), =
Spotify, CDN providers (QBrick, Peeralism), Telia, Ericsson and academic =
parners (SICS, Acreeo, Lund University)). The workshop will have invited =
speakers, demos and  industry discussions. There will be no paper =
submissions nor any open call for contributions, but if you feel you =
have something you would like to contribute, please feel free to contact =
B=F6rje Ohlman. The workshop will be a public workshop open for anyone =
interested, though there will be a limited number of seats and for that =
reason registration will be required.

The date for this workshop will be Tuesday February 12th, 2013. It will =
be held in Kista, Stockholm, Sweden. The proposal is colocate the ICNRG =
interim meeting and have it on Wednesday-Thursday February 13-14th, =
2013. This will give those that have an interest to participate in the =
workshop some added value for their travel. We also think the =
presentations at the workshop can serve as a good introduction to the =
ICNRG meeting.

Please let you know what you think of this. In particular let us know if =
their would be some major conflict during these dates with some other =
ICN related event.

	B=F6rje, Dirk & Dave=

From borje.ohlman@ericsson.com  Thu Oct 25 09:56:22 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C3C21F8920 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 09:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84-iVE1U4O48 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 09:56:22 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id D52C621F888D for <icnrg@irtf.org>; Thu, 25 Oct 2012 09:56:21 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f1e6d000002d2c-ef-50896f3389aa
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 7F.68.11564.33F69805; Thu, 25 Oct 2012 18:56:20 +0200 (CEST)
Received: from abro.ki.sw.ericsson.se (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Thu, 25 Oct 2012 18:56:20 +0200
Received: from [IPv6:::1] (abro.ki.sw.ericsson.se [147.214.177.159])	by abro.ki.sw.ericsson.se (Postfix) with ESMTP id 9F09F16AC66F; Thu, 25 Oct 2012 18:56:19 +0200 (CEST)
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com>
Date: Thu, 25 Oct 2012 18:56:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-ID: <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
X-Mailer: Apple Mail (2.1278)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFLMWRmVeSWpSXmKPExsUyM+Jvra5JfmeAQeNfdotHD7sYLXbO3slk sWD+XSYHZo+WI29ZPSZvPMzm8XP9VfYA5igum5TUnMyy1CJ9uwSujJ4/35kLDrFX/G/rZW5g fMXaxcjJISFgIvFj83x2CFtM4sK99WwgtpDAKUaJ6Y0FXYxcQPYmRolDv3+wQDjrGSWObG1g AqkSFnCU+NpwjrmLkYODV8BQovNwDkiYWUBP4sbUKWCD2IBK3j89ALaMUyBMYuLR/WA2i4Cq xPK+fiaI+lCJyTNeMkPY2hLLFr4Gs3kF7CXe3D7JDrF3OpPEho9PwIaKCJhLNM5axQZxtazE 7eYJ7BBXq0kc/3CMeQKj0CyEk2YhOWkWkhULGJlXMbLnJmbmpJcbbmIEhu/BLb91dzCeOidy iFGag0VJnJcrab+/kEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsbM1zoS62bu2XQq9U/ikqbT f86vPcVlYfrwv8a95We3WrhbOxZUXqpPbjjJbZ3noXF0mfTJmbt4DW2rzIr9Np+4fMr5+byq s0kXdN14p1o3zKsva9/hJOEf6OISnL1p+bNlTxSWma09fuILw28d//uZGTzz+Ca9d7D+5+xf 2q795NPXBxq7GNcosRRnJBpqMRcVJwIAJi5UCy0CAAA=
Cc: icnrg <icnrg@irtf.org>, "Flinck, Hannu \(NSN - FI/Espoo\)" <hannu.flinck@nsn.com>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 16:56:22 -0000

The options we have for moving are:

Monday
1520-1720 (2hrs) - up against INSIPID, NETEXT, ROLL, WPKOPS BoF, PWE3, =
SUNSET4, and TSVAREA.
1740-1940 (2hrs) - up against WEIRDS, IPSECME, LWIG, VIDEOCODEC, and =
IRS.

Tuesday
1520-1650 (1.5 hrs) - up against RADEXT, BMWG, STRAW, MILE, MDNSEXT, =
PCE, and MPTCP.
1700-1830 (1.5 hrs) - up against IRI, NETMOD, IPPM, P2PSIP, FMC, TLS, =
and CCAMP

I think the 1.5 h slots on Tuesday are too short (unless we can get two =
of them, I'll check). If we would go for a Monday slot I prefer the =
earlier one as I'll be really jet-legged having arrived Sunday.

Opinions?

	B=F6rje

On 24 okt 2012, at 15:21, Konstantinos Pentikousis wrote:

>  |Most likely people who attend to icnrg will also attend to CDNi and
>  |ALTO. Many in addition to me would appreciate if these meetings =
would
>  |not conflict.
>=20
> Second this too.
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
>=20


From swb@internet2.edu  Thu Oct 25 09:58:29 2012
Return-Path: <swb@internet2.edu>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D624321F89A7 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 09:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fbao3rKuaH4j for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 09:58:29 -0700 (PDT)
Received: from int-proxy01.merit.edu (int-proxy01.merit.edu [207.75.116.230]) by ietfa.amsl.com (Postfix) with ESMTP id 82E2821F8695 for <icnrg@irtf.org>; Thu, 25 Oct 2012 09:58:27 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy01.merit.edu (Postfix) with ESMTP id 0A28810007C; Thu, 25 Oct 2012 12:58:27 -0400 (EDT)
X-Virus-Scanned: amavisd-new at int-proxy01.merit.edu
Received: from int-proxy01.merit.edu ([127.0.0.1]) by localhost (int-proxy01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IzVdbTHHE-b4; Thu, 25 Oct 2012 12:58:25 -0400 (EDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy01.merit.edu (Postfix) with ESMTPSA id 6B113100057; Thu, 25 Oct 2012 12:58:23 -0400 (EDT)
Message-ID: <50896FAB.20806@internet2.edu>
Date: Thu, 25 Oct 2012 12:58:19 -0400
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com> <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
In-Reply-To: <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: icnrg <icnrg@irtf.org>, "Flinck, Hannu \(NSN - FI/Espoo\)" <hannu.flinck@nsn.com>, Konstantinos Pentikousis <k.pentikousis@huawei.com>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 16:58:30 -0000

On 10/25/12 12:56, Börje Ohlman allegedly wrote:
> The options we have for moving are:
> 
> Monday
> 1520-1720 (2hrs) - up against INSIPID, NETEXT, ROLL, WPKOPS BoF, PWE3, SUNSET4, and TSVAREA.
> 1740-1940 (2hrs) - up against WEIRDS, IPSECME, LWIG, VIDEOCODEC, and IRS.
> 
> Tuesday
> 1520-1650 (1.5 hrs) - up against RADEXT, BMWG, STRAW, MILE, MDNSEXT, PCE, and MPTCP.
> 1700-1830 (1.5 hrs) - up against IRI, NETMOD, IPPM, P2PSIP, FMC, TLS, and CCAMP
> 
> I think the 1.5 h slots on Tuesday are too short (unless we can get two of them, I'll check). If we would go for a Monday slot I prefer the earlier one as I'll be really jet-legged having arrived Sunday.
> 
> Opinions?

I vote for Monday 17:40


From damien.saucez@gmail.com  Thu Oct 25 10:03:21 2012
Return-Path: <damien.saucez@gmail.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E49EE21F899A for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 10:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.159
X-Spam-Level: 
X-Spam-Status: No, score=-3.159 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H65VreTtgmwH for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 10:03:21 -0700 (PDT)
Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by ietfa.amsl.com (Postfix) with ESMTP id A94A121F8782 for <icnrg@irtf.org>; Thu, 25 Oct 2012 10:03:20 -0700 (PDT)
Received: by mail-ea0-f182.google.com with SMTP id c10so718211eaa.13 for <icnrg@irtf.org>; Thu, 25 Oct 2012 10:03:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=VcgfH1Tognl3zo2FKQBN5tTdgr2kIj3czgihOwiw8Bg=; b=Jl+ltAyJh5w/or3GRv4K5qGmVUFo4H0hPyhdUHY61PHtUhGAEcvwuDwoKOb/z5UjSH OX1MGCq7rY11+hwX4q4rfgX0tQrfkLRPVPGMAmh5RS1PSd/fRGvTqB/H56CLeQkWSi7X xteatj9jFrjCG7euzQIL72a0pGD/eJ9qhtDys800Diie82SuDEXZ7yo9Xli4TPXf3nWo Lwehr/ay+tp5j5FGD7XDld+sPrUtHbDorjwrIjmXz0X4RypR0Ntf4r5q5TBs9whE52ue oC5qEeUDuryRnVmDD+RX4Fk2rvqDLYdVkDtEQFTxhfZFjxSY5aMSoDLFDCcg/r0epcgr V0cw==
Received: by 10.14.0.198 with SMTP id 46mr27788916eeb.21.1351184599704; Thu, 25 Oct 2012 10:03:19 -0700 (PDT)
Received: from faucon.inria.fr (faucon.inria.fr. [138.96.201.73]) by mx.google.com with ESMTPS id 42sm31419515eee.0.2012.10.25.10.03.18 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 10:03:18 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <50896FAB.20806@internet2.edu>
Date: Thu, 25 Oct 2012 19:03:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3411A7E-ED35-44CE-B4FB-64A682839503@gmail.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com> <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com> <50896FAB.20806@internet2.edu>
To: Scott Brim <swb@internet2.edu>
X-Mailer: Apple Mail (2.1499)
Cc: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>, "Flinck, Hannu \(NSN - FI/Espoo\)" <hannu.flinck@nsn.com>, Konstantinos Pentikousis <k.pentikousis@huawei.com>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 17:03:22 -0000

On 25 Oct 2012, at 18:58, Scott Brim <swb@internet2.edu> wrote:

> On 10/25/12 12:56, B=F6rje Ohlman allegedly wrote:
>> The options we have for moving are:
>>=20
>> Monday
>> 1520-1720 (2hrs) - up against INSIPID, NETEXT, ROLL, WPKOPS BoF, =
PWE3, SUNSET4, and TSVAREA.
>> 1740-1940 (2hrs) - up against WEIRDS, IPSECME, LWIG, VIDEOCODEC, and =
IRS.
>>=20
>> Tuesday
>> 1520-1650 (1.5 hrs) - up against RADEXT, BMWG, STRAW, MILE, MDNSEXT, =
PCE, and MPTCP.
>> 1700-1830 (1.5 hrs) - up against IRI, NETMOD, IPPM, P2PSIP, FMC, TLS, =
and CCAMP
>>=20
>> I think the 1.5 h slots on Tuesday are too short (unless we can get =
two of them, I'll check). If we would go for a Monday slot I prefer the =
earlier one as I'll be really jet-legged having arrived Sunday.
>>=20
>> Opinions?
>=20
> I vote for Monday 17:40
>=20

both on Monday are ok. Not ok for Tuesday

> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From myeong.jang@samsung.com  Thu Oct 25 20:27:59 2012
Return-Path: <myeong.jang@samsung.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D1921F860F for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 20:27:59 -0700 (PDT)
X-Quarantine-ID: <g+ZeSqZ4TUvm>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -3.711
X-Spam-Level: 
X-Spam-Status: No, score=-3.711 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+ZeSqZ4TUvm for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 20:27:58 -0700 (PDT)
Received: from mailout3.samsung.com (mailout3.samsung.com [203.254.224.33]) by ietfa.amsl.com (Postfix) with ESMTP id 91A7121F8608 for <icnrg@irtf.org>; Thu, 25 Oct 2012 20:27:57 -0700 (PDT)
Received: from epcpsbge6.samsung.com (epcpsbge6 [203.254.230.16]) by mailout3.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0MCH006K6DM9Z9L0@mailout3.samsung.com> for icnrg@irtf.org; Fri, 26 Oct 2012 12:27:55 +0900 (KST)
Received: from epcpsbge6.samsung.com ( [203.254.230.43]) by epcpsbge6.samsung.com (EPCPMTA) with SMTP id 84.8A.06565.B330A805; Fri, 26 Oct 2012 12:27:55 +0900 (KST)
X-AuditID: cbfee610-b7f866d0000019a5-1e-508a033b4328
Received: from epextmailer02 ( [203.254.219.152]) by epcpsbge6.samsung.com (EPCPMTA) with SMTP id 64.8A.06565.B330A805; Fri, 26 Oct 2012 12:27:55 +0900 (KST)
Date: Fri, 26 Oct 2012 03:27:55 +0000 (GMT)
From: =?euc-kr?B?wOW47b/t?= <myeong.jang@samsung.com>
To: =?euc-kr?Q?B=3Frje_Ohlman?= <borje.ohlman@ericsson.com>
MIME-version: 1.0
X-MTR: 20121026032513959@myeong.jang
Msgkey: 20121026032513959@myeong.jang
X-EPLocale: ko_KR.euc-kr
X-Priority: 3
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-EPHeader: ML
X-EPTrCode: 
X-EPTrName: 
X-MLAttribute: 
X-RootMTR: 20121026032513959@myeong.jang
X-ParentMTR: 
X-ArchiveUser: 
X-CPGSPASS: N
Content-transfer-encoding: base64
Content-type: text/plain; charset=euc-kr
MIME-version: 1.0
Message-id: <30650046.155181351222075220.JavaMail.weblogic@epml25>
DLP-Filter: Pass
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGKsWRmVeSWpSXmKPExsVy+t8zbV1r5q4Ag6WnTS12zt7J5MDoMXnj YbYAxigum5TUnMyy1CJ9uwSujGmP21kKbglWHF+6hKWBcY5gFyMnh5CAmsTK59+ZQGwJAROJ zS+nsEPYYhIX7q1n62LkAqpZxiixfOVyNpiivo6tLBDN8xklZt7PBbFZBFQlPjQ9ZQax2QTM JJpPnQSrFxZwlfh7/DqYLSJgK7GxvZ0VxGYWkJHY2rqQCWKOosT7DT/AenkFBCVOznzCArFL ReLjol6ouKrE2QPboG6QkJg1/QIrhM0rMaP9KVS9nMS0r2uYIWxpifOzNjDCPLP4+2OoOL/E sds7gPZygPU+uR8MM2b35i9Q4wUkpp45CNWqKfHh+2Zo+PBJrFn4lgVmzK5Ty5lheu9vmcsE 8ZaixJTuh+wQtpbElx/72NC9xSvgJPHk7UO2CYzKs5CkZiFpn4WkHVnNAkaWVYyiqQXJBcVJ 6almesWJucWleel6yfm5mxghiUFgB+OSBotDjAIcjEo8vA8mdAYIsSaWFVfmHmKU4GBWEuHd PRUoxJuSWFmVWpQfX1Sak1p8iNEHGIETmaVEk/OBSSuvJN7Q2MDY0NDS0MzU0tQAh7CSOG+Z R0qAkEB6YklqdmpqQWoRzDgmDk6pBsb8yWfdrNRu777blfj/X4BE19y+N66Hry43LXuxdI5k fFLRs1OLg2a/DS8N1ngsZXu/51butZC5P3Q+SV7h/s6u9vvP9HfLlr5YGbrj8xc5q7Vnlgh+ aLzCq2+1V+Ze8NaOGc9url6+fb/rrzqnmbNeLpt+8cOrB8dfzwueEvPkwf/1DvO4LvT/PqDE UpyRaKjFXFScCAAYpJngOQMAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNKsWRmVeSWpSXmKPExsVy+t/tGbrWzF0BBnNfGlrsnL2TyYHRY/LG w2wBjFEZNhmpiSmpRQqpecn5KZl56bZK3sHxzvGmZgaGuoaWFuZKCnmJuam2Si4+AbpumTlA U5UUyhJzSoFCAYnFxUr6djZF+aUlqQoZ+cUltkrRRgbGekamJnpGxgZ6JgaxVoYGBkamQFUJ GRnTHrezFNwSrDi+dAlLA+McwS5GTg4hATWJlc+/M4HYEgImEn0dW1kgbDGJC/fWs0HUzGeU mHk/F8RmEVCV+ND0lBnEZhMwk2g+dRKsRljAVeLv8etgtoiArcTG9nZWEJtZQEZia+tCJog5 ihLvN/wA6+UVEJQ4OfMJ1C4ViY+LeqHiqhJnD2xjg4hLSMyafoEVwuaVmNH+FKpeTmLa1zXM ELa0xPlZGxhhbl78/TFUnF/i2O0dQHs5wHqf3A+GGbN78xeo8QISU88chGrVlPjwfTM0GPgk 1ix8ywIzZtep5cwwvfe3zGWCeEtRYkr3Q3YIW0viy499bOje4hVwknjy9iHbBEa5WUhSs5C0 z0LSjqxmASPLKkbR1ILkguKk9FQzveLE3OLSvHS95PzcTYzgFPVMYAfjkgaLQ4wCHIxKPLwP JnQGCLEmlhVX5h5ilOBgVhLh3T0VKMSbklhZlVqUH19UmpNafIjRBxiBE5mlRJPzgekzryTe 0NjA2NDQ0tzA1NDIAoewkjhvmUdKgJBAemJJanZqakFqEcw4Jg5OqQbGxUsMvpUlcPR9fnK4 lscnLe584RoF2RnbFXmta/W5ko9+e6udp9TuPsv4s36dpNnc/ErDzHvf3e5xSZ/bqWN+/end izUKWrZ/hIKFmiQvSa6afTFml+za38wPo0X1Lht0cu1pYS6Yrmsstno5i5Niwrypf6fM1Yjm ff79tdAlNfOrhwrij11WYinOSDTUYi4qTgQAhOznF34DAAA=
X-CFilter-Loop: Reflected
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: myeong.jang@samsung.com
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 03:27:59 -0000

MmhycyBpcyBtdWNoIGJldHRlciB0aGFuIDEuNWhycy4NCkkgcHJlZmVyIE1vbmRheSAxNToyMCwg
YnV0IE1vbmRheSAxNzo0MCBpcyBhbHNvIG9rLg0KDQpCZXN0IHJlZ2FyZHMsDQoNCk15ZW9uZy4N
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCk15ZW9uZy1XdWsgSmFu
Zw0KUHJpbmNpcGFsIFJlc2VhcmNoZXIgLyBQaC5ELg0KU0FNU1VORyBFbGVjdHJvbmljcywgQ28u
LCBMdGQuDQpUZWw6ICs4Mi0zMS0yODAtOTYyNA0KRU1haWw6IG15ZW9uZy5qYW5nQHNhbXN1bmcu
Y29tDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCi0tLS0tLS0g
T3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tDQpTZW5kZXIgOiBEYW1pZW4gU2F1Y2V6PGRhbWllbi5z
YXVjZXpAZ21haWwuY29tPiANCkRhdGUgICA6IDIwMTItMTAtMjYgMDI6MDMgKEdNVCswOTowMCkN
ClRpdGxlICA6IFJlOiBbaWNucmddIElFVEYgODU6IElDTlJHIGFuZCBDRE5pL0FMVE8gbWVldGlu
ZyBvdmVybGFwDQoNCg0KT24gMjUgT2N0IDIwMTIsIGF0IDE4OjU4LCBTY290dCBCcmltIDxzd2JA
aW50ZXJuZXQyLmVkdT4gd3JvdGU6DQoNCj4gT24gMTAvMjUvMTIgMTI6NTYsIEI/cmplIE9obG1h
biBhbGxlZ2VkbHkgd3JvdGU6DQo+PiBUaGUgb3B0aW9ucyB3ZSBoYXZlIGZvciBtb3ZpbmcgYXJl
Og0KPj4gDQo+PiBNb25kYXkNCj4+IDE1MjAtMTcyMCAoMmhycykgLSB1cCBhZ2FpbnN0IElOU0lQ
SUQsIE5FVEVYVCwgUk9MTCwgV1BLT1BTIEJvRiwgUFdFMywgU1VOU0VUNCwgYW5kIFRTVkFSRUEu
DQo+PiAxNzQwLTE5NDAgKDJocnMpIC0gdXAgYWdhaW5zdCBXRUlSRFMsIElQU0VDTUUsIExXSUcs
IFZJREVPQ09ERUMsIGFuZCBJUlMuDQo+PiANCj4+IFR1ZXNkYXkNCj4+IDE1MjAtMTY1MCAoMS41
IGhycykgLSB1cCBhZ2FpbnN0IFJBREVYVCwgQk1XRywgU1RSQVcsIE1JTEUsIE1ETlNFWFQsIFBD
RSwgYW5kIE1QVENQLg0KPj4gMTcwMC0xODMwICgxLjUgaHJzKSAtIHVwIGFnYWluc3QgSVJJLCBO
RVRNT0QsIElQUE0sIFAyUFNJUCwgRk1DLCBUTFMsIGFuZCBDQ0FNUA0KPj4gDQo+PiBJIHRoaW5r
IHRoZSAxLjUgaCBzbG90cyBvbiBUdWVzZGF5IGFyZSB0b28gc2hvcnQgKHVubGVzcyB3ZSBjYW4g
Z2V0IHR3byBvZiB0aGVtLCBJJ2xsIGNoZWNrKS4gSWYgd2Ugd291bGQgZ28gZm9yIGEgTW9uZGF5
IHNsb3QgSSBwcmVmZXIgdGhlIGVhcmxpZXIgb25lIGFzIEknbGwgYmUgcmVhbGx5IGpldC1sZWdn
ZWQgaGF2aW5nIGFycml2ZWQgU3VuZGF5Lg0KPj4gDQo+PiBPcGluaW9ucz8NCj4gDQo+IEkgdm90
ZSBmb3IgTW9uZGF5IDE3OjQwDQo+IA0KDQpib3RoIG9uIE1vbmRheSBhcmUgb2suIE5vdCBvayBm
b3IgVHVlc2RheQ0KDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+IGljbnJnIG1haWxpbmcgbGlzdA0KPiBpY25yZ0BpcnRmLm9yZw0KPiBodHRwczov
L3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQoNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQppY25yZyBtYWlsaW5nIGxpc3QNCmljbnJn
QGlydGYub3JnDQpodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ljbnJnDQo=



From liushucheng@huawei.com  Thu Oct 25 23:16:54 2012
Return-Path: <liushucheng@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916EA21F8661 for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 23:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.666
X-Spam-Level: 
X-Spam-Status: No, score=-2.666 tagged_above=-999 required=5 tests=[AWL=-0.967, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQUjyi9W+8pb for <icnrg@ietfa.amsl.com>; Thu, 25 Oct 2012 23:16:54 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id A484021F8634 for <icnrg@irtf.org>; Thu, 25 Oct 2012 23:16:53 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARE86987; Fri, 26 Oct 2012 14:16:51 +0800 (CST)
Received: from SZXEML439-HUB.china.huawei.com (10.72.61.74) by szxeml208-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 26 Oct 2012 14:16:20 +0800
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.157]) by szxeml439-hub.china.huawei.com ([10.72.61.74]) with mapi id 14.01.0323.003; Fri, 26 Oct 2012 14:16:15 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, Konstantinos Pentikousis <k.pentikousis@huawei.com>
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: Ac2xHSMYHmGcCj4dT7GVkqlZglE43QASL1oAAAuggoAAFYP9kAApCbGAACyRbtA=
Date: Fri, 26 Oct 2012 06:16:14 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B9A2011@szxeml546-mbx.china.huawei.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com> <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
In-Reply-To: <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: icnrg <icnrg@irtf.org>, "Flinck, Hannu \(NSN - FI/Espoo\)" <hannu.flinck@nsn.com>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 06:16:54 -0000

I will do presentation on Monday in both SUNSET4(1520-1720) and IPSECME(174=
0-1940). If we can get 1.5hours*2 on Tuesday, that would be the best result=
. Thanks.

Will


> -----Original Message-----
> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On Behalf Of
> B?rje Ohlman
> Sent: Friday, October 26, 2012 12:56 AM
> To: Konstantinos Pentikousis
> Cc: icnrg; Flinck, Hannu (NSN - FI/Espoo)
> Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
>=20
> The options we have for moving are:
>=20
> Monday
> 1520-1720 (2hrs) - up against INSIPID, NETEXT, ROLL, WPKOPS BoF, PWE3,
> SUNSET4, and TSVAREA.
> 1740-1940 (2hrs) - up against WEIRDS, IPSECME, LWIG, VIDEOCODEC, and
> IRS.
>=20
> Tuesday
> 1520-1650 (1.5 hrs) - up against RADEXT, BMWG, STRAW, MILE, MDNSEXT,
> PCE, and MPTCP.
> 1700-1830 (1.5 hrs) - up against IRI, NETMOD, IPPM, P2PSIP, FMC, TLS, and
> CCAMP
>=20
> I think the 1.5 h slots on Tuesday are too short (unless we can get two o=
f
> them, I'll check). If we would go for a Monday slot I prefer the earlier =
one as
> I'll be really jet-legged having arrived Sunday.
>=20
> Opinions?
>=20
> 	B=F6rje
>=20
> On 24 okt 2012, at 15:21, Konstantinos Pentikousis wrote:
>=20
> >  |Most likely people who attend to icnrg will also attend to CDNi and
> >  |ALTO. Many in addition to me would appreciate if these meetings would
> >  |not conflict.
> >
> > Second this too.
> >
> > Best Regards,
> >
> > Kostas
> >
> >
> >
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From k.pentikousis@huawei.com  Fri Oct 26 00:08:07 2012
Return-Path: <k.pentikousis@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CFE21F868C for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 00:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.337
X-Spam-Level: 
X-Spam-Status: No, score=-3.337 tagged_above=-999 required=5 tests=[AWL=-1.037, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhqA+jdXerwX for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 00:08:06 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7A06121F867E for <icnrg@irtf.org>; Fri, 26 Oct 2012 00:08:05 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARE94141; Fri, 26 Oct 2012 15:08:04 +0800 (CST)
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml208-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 26 Oct 2012 15:08:00 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml412-hub.china.huawei.com ([10.82.67.91]) with mapi id 14.01.0323.003; Fri, 26 Oct 2012 15:08:00 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: Ac2xHSMYHmGcCj4dT7GVkqlZglE43QASL1oAAAuggoAAFYP9kAApCbGAAC5aP0A=
Date: Fri, 26 Oct 2012 07:07:59 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4EBF0A@szxeml545-mbx.china.huawei.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com> <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
In-Reply-To: <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.218.167]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 07:08:07 -0000

  |Opinions?

The second slot on Tuesday is not ok for me. Monday is better, and Monday 1=
740-1940 is excellent wrt overalaps, although a bit late, I agree.

Best regards,

Kostas

From hannu.flinck@nsn.com  Fri Oct 26 03:21:33 2012
Return-Path: <hannu.flinck@nsn.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD1DA21F850A for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 03:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECwn2O3WZP3m for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 03:21:33 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id ED1EA21F8510 for <icnrg@irtf.org>; Fri, 26 Oct 2012 03:21:31 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q9QALMYC020053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Oct 2012 12:21:22 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q9QALJrc010524; Fri, 26 Oct 2012 12:21:22 +0200
Received: from FIESEXC008.nsn-intra.net ([10.159.0.16]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 26 Oct 2012 12:20:57 +0200
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: Fri, 26 Oct 2012 13:20:56 +0300
Message-ID: <E6647B13E38E7C4E965285DCC22260AF018B5BA9@FIESEXC008.nsn-intra.net>
In-Reply-To: <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
Thread-Index: Ac2y0ak/FgcJPjoeQf67fpsJDDQz/QAkdgZQ
References: <8D38716F0C1A444BA0CD7E96454366C23A4EB744@szxeml545-mbx.china.huawei.com> <812FE28F-2B75-4EB4-86DF-E7A12AA80D49@ericsson.com> <E6647B13E38E7C4E965285DCC22260AF018B5367@FIESEXC008.nsn-intra.net> <8D38716F0C1A444BA0CD7E96454366C23A4EBB11@szxeml545-mbx.china.huawei.com> <F9AFE390-5A41-43B1-A319-96664FFC2EC4@ericsson.com>
From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
To: =?iso-8859-1?Q?ext_B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, "Konstantinos Pentikousis" <k.pentikousis@huawei.com>
X-OriginalArrivalTime: 26 Oct 2012 10:20:57.0832 (UTC) FILETIME=[96E4BE80:01CDB363]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1295
X-purgate-ID: 151667::1351246883-00006DFC-273A8EC8/0-0/0-0
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 10:21:33 -0000

All those overlaps are fine with me.=20

- Hannu=20

-----Original Message-----
From: ext B=F6rje Ohlman [mailto:borje.ohlman@ericsson.com]=20
Sent: Thursday, October 25, 2012 7:56 PM
To: Konstantinos Pentikousis
Cc: Flinck, Hannu (NSN - FI/Espoo); icnrg
Subject: Re: [icnrg] IETF 85: ICNRG and CDNi/ALTO meeting overlap

The options we have for moving are:

Monday
1520-1720 (2hrs) - up against INSIPID, NETEXT, ROLL, WPKOPS BoF, PWE3, =
SUNSET4, and TSVAREA.
1740-1940 (2hrs) - up against WEIRDS, IPSECME, LWIG, VIDEOCODEC, and =
IRS.

Tuesday
1520-1650 (1.5 hrs) - up against RADEXT, BMWG, STRAW, MILE, MDNSEXT, =
PCE, and MPTCP.
1700-1830 (1.5 hrs) - up against IRI, NETMOD, IPPM, P2PSIP, FMC, TLS, =
and CCAMP

I think the 1.5 h slots on Tuesday are too short (unless we can get two =
of them, I'll check). If we would go for a Monday slot I prefer the =
earlier one as I'll be really jet-legged having arrived Sunday.

Opinions?

	B=F6rje

On 24 okt 2012, at 15:21, Konstantinos Pentikousis wrote:

>  |Most likely people who attend to icnrg will also attend to CDNi and
>  |ALTO. Many in addition to me would appreciate if these meetings =
would
>  |not conflict.
>=20
> Second this too.
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
>=20


From haiyong.xie@huawei.com  Fri Oct 26 13:56:31 2012
Return-Path: <haiyong.xie@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE5921F85B1 for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 13:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXNe3JuCwBhb for <icnrg@ietfa.amsl.com>; Fri, 26 Oct 2012 13:56:31 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id EB1C221F85AF for <icnrg@irtf.org>; Fri, 26 Oct 2012 13:56:30 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id BMO44339; Fri, 26 Oct 2012 12:56:29 -0800 (PST)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 26 Oct 2012 13:56:25 -0700
Received: from [127.0.0.1] (10.193.38.31) by smtpsus.huawei.com (10.193.5.131) with Microsoft SMTP Server id 14.1.323.3; Fri, 26 Oct 2012 13:56:17 -0700
Message-ID: <508AF9E3.3050000@huawei.com>
Date: Fri, 26 Oct 2012 14:00:19 -0700
From: Haiyong Xie <haiyong.xie@huawei.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: <icnrg@irtf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.193.38.31]
X-CFilter-Loop: Reflected
Cc: Guoqiang Wang <guoqiangwang@huawei.com>, Haiyong Xie <haiyong.xie@huawei.com>
Subject: [icnrg] New Version Notification for draft-xie-icnrg-coordinated-caching-forwarding.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 20:56:31 -0000

Dear All,

We posted a draft on coordinated caching and forwarding for
information-centric networks. The draft has not been submitted via the
data tracker but we are looking for your comments, so we put the draft
on a public web server, the link is below:

http://sites.google.com/site/haiyongxie/draft-xie-icn-coordinated-caching-forwarding.txt

Your comments are very welcome.

Best regards,
Haiyong

From liushucheng@huawei.com  Sat Oct 27 03:56:11 2012
Return-Path: <liushucheng@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF3A21F8493 for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 03:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.092
X-Spam-Level: 
X-Spam-Status: No, score=-1.092 tagged_above=-999 required=5 tests=[AWL=-2.058, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, SARE_SPEC_REPLICA_OBFU=1.812]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-dnHC-k+l9w for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 03:56:10 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by ietfa.amsl.com (Postfix) with ESMTP id C6E9821F84AE for <icnrg@irtf.org>; Sat, 27 Oct 2012 03:56:08 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml214-edg.china.huawei.com) ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARG37484; Sat, 27 Oct 2012 18:56:01 +0800 (CST)
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 27 Oct 2012 18:55:58 +0800
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.157]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Sat, 27 Oct 2012 18:55:55 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: Andrea Detti <andrea.detti@uniroma2.it>
Thread-Topic: [icnrg] FW: New Version Notification for draft-ren-icn-content-retrieval-00.txt
Thread-Index: AQHNqsfn9DKyKKvea0ee707d4pjoOZe6O1hwgAXdrwCADPLSIA==
Date: Sat, 27 Oct 2012 10:55:55 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B9A243E@szxeml546-mbx.china.huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com> <50814FFE.3090101@uniroma2.it>
In-Reply-To: <50814FFE.3090101@uniroma2.it>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: =?gb2312?B?yM7mug==?= <renjing@uestc.edu.cn>, "icnrg@irtf.org" <icnrg@irtf.org>
Subject: Re: [icnrg] FW: New Version Notification for draft-ren-icn-content-retrieval-00.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2012 10:56:11 -0000

RGVhciBBbmRyZWEsDQoNClNvcnJ5IGZvciBiZWluZyBsYXRlLiBNYW55IHRoYW5rcyBmb3IgeW91
ciB2YWx1YWJsZSBjb21tZW50cy4gDQogDQpXaGVuIHdlIHdlcmUgd3JpdGluZyB0aGlzIGRyYWZ0
LCB3ZSBjbGFzc2lmaWVkIG5hbWUgcmVzb2x1dGlvbiBtZWNoYW5pc21zIGludG8gdHdvIGNhdGVn
b3JpZXM6IHJvdXRlLWJ5LW5hbWUgYW5kIEROUy1saWtlIHJlc29sdXRpb24gc3lzdGVtLiBXZSBk
ZWZpbmVkIHJvdXRlLWJ5LW5hbWUgYXMgobByb3V0ZXJzIGRpc3NlbWluYXRlIG5hbWUtYmFzZWQg
cm91dGluZyBpbmZvcm1hdGlvbiB3aXRoIGVhY2ggb3RoZXIgYW5kIGZvcndhcmQgcGFja2V0cyBi
YXNlZCBvbiB0aGUgbmFtZS1iYXNlZCByb3V0aW5nIHRhYmxlobEgKHNvcnJ5IHRoYXQgd2UgZGlk
IG5vdCB3cml0ZSB0aGlzIGRlZmluaXRpb24gY2xlYXJseSBpbiB0aGUgZHJhZnQpLiBGcm9tIHRo
aXMgcG9pbnQsIHdlIGNvbnNpZGVyZWQgdGhhdCBDT05FVCBkb2VzIG5vdCBkaXNzZW1pbmF0ZSBy
b3V0aW5nIGluZm9ybWF0aW9uLCBidXQgZXN0YWJsaXNoZXMgYSBETlMtbGlrZSBzeXN0ZW0uIFdl
IGlnbm9yZWQgdGhhdCBDT05FVCBhbHNvIGRlcGxveWVkIGEgcm91dGUtY2FjaGUgbWVjaGFuaXNt
LiBUaGFua3MgZm9yIHBvaW50aW5nIG91dCB0aGlzLiBXZSB3aWxsIHJld3JpdGUgdGhlIGRyYWZ0
IGFjY29yZGluZyB0byB5b3VyIHN1Z2dlc3Rpb24uIA0KIA0KPGstYW55Y2FzdCBhbmQgbXVsdGlj
YXN0Pg0KIA0KSW4gY29uZHVjdGluZyB0aGUgc3VydmV5IG9mIG11bHRpY2FzdCBtZWNoYW5pc20s
IHdlIHJlYWQgYSBmZXcgcHVibGlzaGVkIENPTkVUIHBhcGVycywgc3VjaCBhcyBbMV1bMl0uIFdl
IG9ubHkgZmluZCBhIGZldyBzZW50ZW5jZXMgYWJvdXQgbXVsdGljYXN0LCB3aGljaCBzdGF0ZWQg
dGhhdCBuYW1lZC1zYXAgY2FuIGJlIGV4dGVuZGVkIHRvIG11bHRpY2FzdCAoc2VlIFsxXSBzZWMx
LCBbMl0gc2VjNy4xKS4gDQogDQpSZWdhcmRpbmcgdGhlIFBJVCwgSSBoYXZlIGEgcXVlc3Rpb24u
IEluIFsxXSAsIGl0IHNheXMgdGhhdCChsFRoaXMgaW5mbyB3aWxsIGJlIHVzZWQgdG8gZmluZCB0
aGUgcmV2ZXJzZS1wYXRoIHRvIHJvdXRlIHRoZSBuYW1lZC1kYXRhIENJVSBiYWNrIHRvIHRoZSBy
ZXF1ZXN0aW5nIG5vZGUsIGluIHRoZSBkZWxpdmVyeSBwaGFzZS4gSW4gWzNdIHRoZSBzYW1lIGdv
YWwgaXMgYWNoaWV2ZWQgYnkgbWFpbnRhaW5pbmcgc3RhdGVzIGluIG5ldHdvcmsgbm9kZXMuIFdl
IHByb3Bvc2UgdG8gdXNlIHNvdXJjZS1yb3V0aW5nLCBiZWluZyBhd2FyZSBvZiB0aGUgaW52b2x2
ZWQgdHJhZGUtb2ZmcywgYW5kIGdpdmVuIHRoYXQgd2UgdGhpbmsgdGhhdCB0aGUgbnVtYmVyIG9m
IHRyYXZlcnNlZCBDT05FVCBib3JkZXIgbm9kZXMgc2hvdWxkIGJlIHJhdGhlciBsaW1pdGVkIChl
LmcuIENTU3Mgc2hvdWxkIGNvaW5jaWRlIHdpdGggSW50ZXJuZXQgQXV0b25vbW91cyBTeXN0ZW1z
KS6hsQ0KIA0KQWNjb3JkaW5nIHRvIHRoZSBhYm92ZSBpbmZvcm1hdGlvbiwgd2UgdGhpbmsgdGhh
dCBDT05FVCB0YWtlcyBhIGRpZmZlcmVudCB3YXkgZnJvbSBDQ04gYWJvdXQgbXVsdGljYXN0LiBN
YXliZSB3ZSBoYXZlIG1pc3NlZCBzb21lIGltcG9ydGFudCBsaXRlcmF0dXJlcy4gQ2FuIHlvdSBn
aXZlIHVzIHNvbWUgcmVmZXJlbmNlcz8gVGhhbmsgeW91IHNvIG11Y2guDQogDQogDQogDQpbMV1E
ZXR0aSwgQS4sIE4uIEIuIE1lbGF6emksIGV0IGFsLiAoMjAxMSkuIENPTkVUOiBhIGNvbnRlbnQg
Y2VudHJpYyBpbnRlci1uZXR3b3JraW5nIGFyY2hpdGVjdHVyZS4gUHJvY2VlZGluZ3Mgb2YgdGhl
IEFDTSBTSUdDT01NIHdvcmtzaG9wIG9uIEluZm9ybWF0aW9uLWNlbnRyaWMgbmV0d29ya2luZy4g
VG9yb250bywgT250YXJpbywgQ2FuYWRhLCBBQ006IDUwLTU1Lg0KWzJdobBEMy4yIC0gU3lzdGVt
IGFyY2hpdGVjdHVyZaGxLCBDT05WRVJHRU5DRSBkZWxpdmVyYWJsZQ0KWzNdIFYuIEphY29ic29u
LCBELiBLLiBTbWV0dGVycywgSi4gRC4gVGhvcm50b24gZXQgYWwuLCChsU5ldHdvcmtpbmcgbmFt
ZWQgY29udGVudKGxLCBBQ00gQ29ORVhUIDIwMDkNCg0KUmVnYXJkcywNCldpbGwNCg0KDQo+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEFuZHJlYSBEZXR0aSBbbWFpbHRvOmFu
ZHJlYS5kZXR0aUB1bmlyb21hMi5pdF0NCj4gU2VudDogRnJpZGF5LCBPY3RvYmVyIDE5LCAyMDEy
IDk6MDUgUE0NCj4gVG86IGljbnJnQGlydGYub3JnOyBXaWxsIExpdSAoU2h1Y2hlbmcpDQo+IFN1
YmplY3Q6IFJlOiBbaWNucmddIEZXOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+IGRy
YWZ0LXJlbi1pY24tY29udGVudC1yZXRyaWV2YWwtMDAudHh0DQo+IA0KPiBEZWFyIFdpbGwsDQo+
IA0KPiBJIGhhdmUgc29tZSBjb21tZW50cyByZWdhcmRpbmcgdGhlIENPTlZFUkdFTkNFIHByb2pl
Y3QsIGluIHdoaWNoIEkgYW0NCj4gaW52b2x2ZWQuDQo+IA0KPiBUaGUgQ09OVkVSR0VOQ0UgbmV0
d29yayAoQ09ORVQpIGlzIHNpbWlsYXIgdG8gQ0NOeDsgd2UgY29tcGxlbWVudCBpdA0KPiB3aXRo
IHNvbWUgbWlzc2luZyBmdW5jdGlvbmFsaXR5IG9yIHdlIHRyeSB0byBpbXByb3ZlIGl0cyBwZXJm
b3JtYW5jZSwNCj4gZS5nLiByb3V0aW5nIFsxXSwgbmFtZWQtc2FwIFsyXSwgdHJhbnNwb3J0LCBl
dGMuLg0KPiANCj4gDQo+IEluIHdoYXQgZm9sbG93cyBJIHByb3Bvc2Ugc29tZSBjaGFuZ2VzIHRv
IHRoZSB2YWx1YWJsZSBkZXNjcmlwdGlvbg0KPiBwcm92aWRlZCBieSB0aGUgZHJhZnQsIHJlZ2Fy
ZGluZyBob3cgQ09OVkVSR0VOQ0UgZGVhbHMgd2l0aCB0aGUNCj4gZm9sbG93aW5nIGlzc3VlczoN
Cj4gDQo+IA0KPiANCj4gPENvbnRlbnQgbmFtZSByZXNvbHV0aW9uPg0KPiANCj4gdGhlIGRyYWZ0
IHJlcG9ydHMgOiAiRGVkaWNhdGUgTmFtZS1TeXN0ZW0tTm9kZXMgKHNpbWlsYXIgdG8gRE5TKSBh
cmUNCj4gZGVwbG95ZWQiDQo+IA0KPiBUaGlzIHNlbnRlbmNlIG1pZ2h0IGJlIHVuZGVyc3Rvb2Qg
YXM6IKGwdG8gZm9yd2FyZCBhIGNvbnRlbnQgcmVxdWVzdCwgYQ0KPiBDT05FVCBub2RlIGFsd2F5
cyBxdWVyaWVzIHRoZSBOYW1lLVN5c3RlbS1Ob2RlcyB0byByZXNvbHZlIHRoZQ0KPiBuZXh0LWhv
cKGxLg0KPiANCj4gVGhpcyBpcyBub3QgdHJ1ZSBzaW5jZSwgYXMgQ0NOeCwgYSBDT05FVCBub2Rl
IHVzdWFsbHkgcmVzb2x2ZXMgdGhlDQo+IG5hbWVzLCBlbi1yb3V0ZSwgYnkgbWVhbnMgb2YgYSBu
YW1lLWJhc2VkIGZvcndhcmRpbmcgaW5mb3JtYXRpb24gYmFzZQ0KPiAoRklCKSwgaS5lLiB3aXRo
b3V0IGNvbnRhY3RpbmcgdGhlIE5hbWUtU3lzdGVtLU5vZGVzIChvciBiZXR0ZXINCj4gTmFtZS1S
b3V0aW5nLVN5c3RlbSBub2Rlcywgc2VlIFsxXSkNCj4gDQo+IEhvd2V2ZXIsIGN1cnJlbnQgZmFz
dCBGSUJzIChlLmcuIGJhc2VkIG9uIFNSQU0pIGhhdmUgYSBzaXplIHVuYWJsZSB0bw0KPiBzdG9y
ZSBhbGwgcG9zc2libGUgbmFtZS1wcmVmaXhlcy4NCj4gDQo+IFRvIGNvcGUgd2l0aCB0aGlzIGlz
c3VlLCBhIENPTkVUIG5vZGUgdXNlcyB0aGUgRklCIGFzICJyb3V0ZSBjYWNoZSIuDQo+IA0KPiBJ
ZiB0aGUgbm9kZSBkb2VzIG5vdCBoYXZlIHRoZSByb3V0aW5nIGVudHJ5IG5lY2Vzc2FyeSB0byBy
b3V0ZS1ieS1uYW1lDQo+IGFuIEludGVyZXN0IG1lc3NhZ2UsIHRoZW4gdGhlIG5vZGUgbG9va3Vw
cyB0aGUgcm91dGluZyBpbmZvcm1hdGlvbiBpbg0KPiB0aGUgTmFtZS1Sb3V0aW5nLVN5c3RlbSBh
bmQgY2FjaGVzIHRoZSByb3V0aW5nIGVudHJ5IGluIHRoZSBGSUIuDQo+IA0KPiBUaGVyZWZvcmUs
IGxvb2t1cHMgb2NjdXIgb25seSBpbiBjYXNlcyBvZiByb3V0ZS1jYWNoZSBtaXNzZXMsIHdoaWNo
DQo+IHNob3VsZCBiZSBhIHJhcmUgZXZlbnQuDQo+IA0KPiBGdXJ0aGVybW9yZSwgYXMgZ2VuZXJh
bCBjb21tZW50LCBJIHRoaW5rIHRoYXQgaXQgY291bGQgYmUgaW1wb3J0YW50IHRvDQo+IHNwZWNp
ZnksIGZvciBhbnkgcHJvamVjdCwgaWYgQ29udGVudCBOYW1lIFJlc29sdXRpb24gaXMgcGVyZm9y
bWVkIGF0DQo+IHBhY2tldC1yYXRlIG9yIG9ubHkgb25lLXRpbWUgcGVyIGRvd25sb2FkLCBpLmUu
IGF0IHNlc3Npb24tcmF0ZS4NCj4gDQo+IEEgQ09ORVQgbm9kZSBwZXJmb3JtcyBuYW1lIHJlc29s
dXRpb24gYXQgcGFja2V0LXJhdGUgYnkgdXNpbmcgYSBGSUIgYW5kLA0KPiBzb21ldGltZXMsIGJ5
IGNvbnRhY3Rpbmcgbm9kZXMgb2YgYSBOYW1lLVJvdXRpbmctU3lzdGVtLg0KPiANCj4gQ29uc2Vx
dWVudGx5LCBJIHdvdWxkIHJldmlzZSB0aGUgZHJhZnQgYXMgZm9sbG93cyAiRW4tcm91dGUgbmFt
ZQ0KPiByZXNvbHV0aW9uIHBlcmZvcm1lZCBhdCBwYWNrZXQtcmF0ZSBieSBtZWFucyBvZiBuYW1l
LWJhc2VkIGZvcndhcmRpbmcNCj4gdGFibGVzLCB3aGljaCBhcmUgdXNlZCBhcyByb3V0ZS1jYWNo
ZXMuIFJvdXRlLWNhY2hlIG1pc3NlcyBhcmUgcmVzb2x2ZWQNCj4gYnkgbWVhbnMgb2YgYSBkZWRp
Y2F0ZWQgTmFtZS1Sb3V0aW5nLVN5dGVtIG5vZGUgKHNpbWlsYXIgdG8gRE5TKS4iDQo+IA0KPiAN
Cj4gDQo+IA0KPiA8ay1hbnljYXN0IGFuZCBtdWx0aWNhc3Q+DQo+IA0KPiB0aGUgZHJhZnQgcmVw
b3J0czogIiBUcmFkaXRpb25hbCBwb2ludC10by1wb2ludCBzZXNzaW9ucyBiZXR3ZWVuIHR3bw0K
PiB1cHBlciBsYXllciBlbnRpdGllcyBjYW4gYmUgc3VwcG9ydGVkIGJ5IGNvdXBsaW5nIHRoZSB1
cHBlciBsYXllcg0KPiBlbnRpdGllcyB3aXRoIG5hbWVkLXNlcnZpY2UtYXNzZXNzLXBvaW50cy4g
VGhpcyBmdW5jdGlvbmFsaXR5IGNhbiBiZQ0KPiBleHRlbmRlZCB0byBzdXBwb3J0IG11bHRpY2Fz
dCINCj4gDQo+IA0KPiBJIHRoaW5rIHRoYXQgdGhpcyBpcyBub3QgY29tcGxldGVseSB0cnVlLiBJ
bmRlZWQsIG5hbWVkLXNhcHMgYXJlIG5vdA0KPiBtZWFudCBmb3IgbXVsdGljYXN0aW5nIHB1cnBv
c2UsIGJ1dCBbMl0gdG8gc3VwcG9ydCBsZWdhY3kgcG9pbnQtdG8tcG9pbnQNCj4gaW50ZXJhY3Rp
dmUgc2VydmljZSBzZXNzaW9ucywgZS5nLiBob21lIGJhbmtpbmcuDQo+IA0KPiBNdWx0aWNhc3Qg
aXMgYWNoaWV2ZWQgaW4gQ0NOeC9DT05FVCBieSBleHBsb2l0aW5nIGJvdGggZW4tcm91dGUNCj4g
aW4tbmV0d29yayBjYWNoaW5nIGFuZCB0aGUgbWVjaGFuaXNtIG9mIFBlbmRpbmcgSW50ZXJlc3Qg
VGFibGUgKFBJVCksIGFzDQo+IGRlc2NyaWJlZCBpbiBbTkROXS4NCj4gDQo+IEluIGNhc2Ugb2Yg
YSBtdWx0aWNhc3Qgc2VydmljZSwgZS5nLiB2aWRlbyBsaXZlIHN0cmVhbWluZywgbWFueSBzb3Vy
Y2VzDQo+IHNlbmQgdGhlIHNhbWUgSW50ZXJlc3QgbWVzc2FnZSwgZS5nLiB0byByZXF1ZXN0IHRo
ZSBuZXh0IHZpZGVvIGZyYW1lLg0KPiBVc2luZyB0aGUgUElUIG1lY2hhbmlzbSwgaW4gY2FzZSBv
ZiBxdWl0ZS1zeW5jaHJvbm91cyBJbnRlcmVzdHMsIG9yDQo+IHVzaW5nIGluLW5ldHdvcmsgY2Fj
aGluZywgaW4gY2FzZSBvZiBuZWFybHktc3luY2hyb25vdXMgSW50ZXJlc3QsIHRoZQ0KPiBzYW1l
IGNvbnRlbnQgY2h1bmsgaXMgdHJhbnNmZXJyZWQgb25seSBvbmUgdGltZSwgb24gYSBsaW5rIG9m
IHRoZQ0KPiBtdWx0aWNhc3QgdHJlZSByb290ZWQgYXQgc291cmNlLg0KPiANCj4gQ29uc2VxdWVu
dGx5LCByZWdhcmRpbmcgbXVsdGljYXN0LCBJIHdvdWxkIHJldmlzZSB0aGUgZHJhZnQgYXMgZm9s
bG93czoNCj4gDQo+ICJSZWNlaXZlci1kcml2ZW4gbXVsdGljYXN0IGJhc2VkIG9uIGkpIHJvdXRp
bmcgaW5mb3JtYXRpb24gdGVtcG9yYXJ5DQo+IGxlZnQgaW4gbmV0d29yayBub2RlcyAoYWthIFBl
bmRpbmcgSW50ZXJlc3QgVGFibGUpIGFuZCBpaSkgaW4tbmV0d29yaw0KPiBjYWNoaW5nIg0KPiAN
Cj4gUmVnYXJkaW5nIGstbXVsdGljYXN0LCBJIHdvdWxkIHJldmlzZSB0aGUgZHJhZnQgYXMgZm9s
bG93cw0KPiAiUmVjZWl2ZXItZHJpdmVuIGstbXVsdGljYXN0LCBieSBjb25jdXJyZW50bHkgZmV0
Y2hpbmcgZGlmZmVyZW50IGRhdGENCj4gY2h1bmtzIGZyb20gdGhlIGRpZmZlcmVudCByZXBsaWNh
IFNlcnZlcnMiDQo+IA0KPiANCj4gDQo+IDxDb250ZW50IHJlcGxpY2F0aW9uPg0KPiANCj4gaXQg
aXMgT0sNCj4gDQo+IA0KPiANCj4gPEluLW5ldHdvcmsgY2FjaGUgZGlzY292ZXJ5Pg0KPiANCj4g
aXQgaXMgT0sNCj4gDQo+IA0KPiANCj4gVGhhbmtzIGEgbG90IGZvciB5b3VyIGVmZm9ydCwNCj4g
DQo+IA0KPiANCj4gQW5kcmVhDQo+IA0KPiANCj4gDQo+IFsxXSBBLiBEZXR0aSwgTS4gUG9tcG9z
aW5pLCBOLiBCbGVmYXJpLU1lbGF6emksIFMuIFNhbHNhbm8sIKGwU3VwcG9ydGluZw0KPiB0aGUg
V2ViIHdpdGggYW4gSW5mb3JtYXRpb24gQ2VudHJpYyBOZXR3b3JrIHRoYXQgUm91dGVzIGJ5IE5h
bWWhsSwNCj4gRWxzZXZpZXIgQ29tcHV0ZXIgTmV0d29ya3MsIHZvbC4gNTYsIElzc3VlIDE3LCBw
LiAzNzA1qEMzNzIyDQo+IChodHRwOi8vbmV0Z3JvdXAudW5pcm9tYTIuaXQvQW5kcmVhX0RldHRp
L0xvb2t1cC1hbmQtQ2FjaGUvY29tbmV0LXdlYg0KPiAtSUNOLWV4dC5wZGYpDQo+IA0KPiBbMl0g
IkQzLjEgLSBEZWZpbml0aW9uIG9mIHRoZSBzeXN0ZW0gc2VydmljZXMgYW5kIGZ1bmN0aW9uYWwN
Cj4gY29tcG9uZW50cyIsIENPTlZFUkdFTkNFIGRlbGl2ZXJhYmxlLCBzZWUgU2VjdGlvbiA0LjEN
Cj4gDQo+IA0KPiBPbiAxMC8xNS8yMDEyIDAxOjQ3IFBNLCBXaWxsIExpdSAoU2h1Y2hlbmcpIHdy
b3RlOg0KPiA+IEhlbGxvLA0KPiA+DQo+ID4gV2UgaGF2ZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQg
ZGlzY3Vzc2luZyBhYm91dCBjb250ZW50IHJldHJpZXZhbCBpbiBJQ04uDQo+IEhlcmUsIHdlIGRp
c2N1c3NlZCBiYXNpYyByZXF1aXJlbWVudHMgb24gdGhlIGJhc2lzIG9mIHByZXZpb3VzIGxpdGVy
YXR1cmVzLA0KPiB0aGUgZnVuZGFtZW50YWwgZnVuY3Rpb25hbGl0aWVzIHJlcXVpcmVkIHRvIHNh
dGlzZnkgdGhlIGZvcmVnb2luZw0KPiByZXF1aXJlbWVudHMsIGFuZCB0aGUgaW1wbGVtZW50YXRp
b24gc3RhdHVzIG9mIHN1Y2ggZnVuY3Rpb25hbGl0aWVzIGluDQo+IHZhcmlvdXMgSW5mb3JtYXRp
b24tQ2VudHJpYyBOZXR3b3JrIGFyY2hpdGVjdHVyZXMuDQo+ID4NCj4gPiBZb3VyIGNvbW1lbnRz
IGFyZSBoaWdobHkgYXBwcmVjaWF0ZWQuDQo+ID4NCj4gPiBSZWdhcmRzLA0KPiA+IFNodWNoZW5n
IExJVSAoV2lsbCkNCj4gPg0KPiA+DQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
PiBGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmddDQo+ID4gU2VudDogTW9uZGF5LCBPY3RvYmVyIDE1LCAyMDEyIDc6MjYgUE0NCj4g
PiBUbzogV2lsbCBMaXUgKFNodWNoZW5nKQ0KPiA+IENjOiBqaW5ncmVuQGNpdHl1LmVkdS5oazsg
amlhbndhbmdAY2l0eXUuZWR1LmhrOyBmZWl0YW5nQGNpdHl1LmVkdS5oaw0KPiA+IFN1YmplY3Q6
IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtcmVuLWljbi1jb250ZW50LXJldHJp
ZXZhbC0wMC50eHQNCj4gPg0KPiA+DQo+ID4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXJl
bi1pY24tY29udGVudC1yZXRyaWV2YWwtMDAudHh0DQo+ID4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5
IHN1Ym1pdHRlZCBieSBXaWxsIExpdSBhbmQgcG9zdGVkIHRvIHRoZQ0KPiA+IElFVEYgcmVwb3Np
dG9yeS4NCj4gPg0KPiA+IEZpbGVuYW1lOgkgZHJhZnQtcmVuLWljbi1jb250ZW50LXJldHJpZXZh
bA0KPiA+IFJldmlzaW9uOgkgMDANCj4gPiBUaXRsZToJCSBPbiB0aGUgQ29udGVudCBSZXRyaWV2
YWwgSW4gSW5mb3JtYXRpb24tQ2VudHJpYyBOZXR3b3JrDQo+ID4gQ3JlYXRpb24gZGF0ZToJIDIw
MTItMTAtMTUNCj4gPiBXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4gPiBOdW1iZXIg
b2YgcGFnZXM6IDExDQo+ID4gVVJMOg0KPiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1yZW4taWNuLWNvbnRlbnQtcmV0cmlldmFsLTAwLnR4dA0KPiA+IFN0YXR1czoN
Cj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1yZW4taWNuLWNvbnRlbnQt
cmV0cmlldmFsDQo+ID4gSHRtbGl6ZWQ6DQo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LXJlbi1pY24tY29udGVudC1yZXRyaWV2YWwtMDANCj4gPg0KPiA+DQo+ID4gQWJzdHJhY3Q6
DQo+ID4gICAgIEluZm9ybWF0aW9uLUNlbnRyaWMgTmV0d29yayhJQ04pLCBhcyBhbiBlbWVyZ2lu
ZyBuZXR3b3JrDQo+ID4gICAgIGFyY2hpdGVjdHVyZSwgZm9jdXMgb24gZGVsaXZlcmluZyBjb250
ZW50IG1vcmUgZWZmaWNpZW50bHkuICBUaGlzDQo+ID4gICAgIGJyaWVmIHBhcGVyIGRpc2N1c3Nl
cyBzb21lIGlzc3VlcyBhYm91dCBjb250ZW50IHJldHJpZXZhbCBpbiB0aGUNCj4gPiAgICAgSW5m
b3JtYXRpb24tQ2VudHJpYyBOZXR3b3JrLiAgSXQgZmlyc3QgbGlzdHMgYSBzZXQgb2YgYmFzaWMN
Cj4gPiAgICAgcmVxdWlyZW1lbnRzIG9uIHRoZSBiYXNpcyBvZiBwcmV2aW91cyBsaXRlcmF0dXJl
cy4gIFRoZW4sIGl0IHRyaWVzIHRvDQo+ID4gICAgIGlkZW50aWZ5IHRoZSBmdW5kYW1lbnRhbCBm
dW5jdGlvbmFsaXRpZXMgcmVxdWlyZWQgdG8gc2F0aXNmeSB0aGUNCj4gPiAgICAgZm9yZWdvaW5n
IHJlcXVpcmVtZW50cy4gIExhc3QsIGl0IHN1bW1hcml6ZXMgdGhlIGltcGxlbWVudGF0aW9uDQo+
ID4gICAgIHN0YXR1cyBvZiBzdWNoIGZ1bmN0aW9uYWxpdGllcyBpbiB2YXJpb3VzIEluZm9ybWF0
aW9uLUNlbnRyaWMgTmV0d29yaw0KPiA+ICAgICBhcmNoaXRlY3R1cmVzLg0KPiA+DQo+ID4NCj4g
Pg0KPiA+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IGljbnJnIG1haWxpbmcgbGlzdA0KPiA+
IGljbnJnQGlydGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pY25yZw0KPiA+DQo+IA0KPiANCj4gLS0NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+IEFuZHJlYSBEZXR0aSwgUGhEDQo+IERpcC4gSW5nZWduZXJpYSBFbGV0
dHJvbmljYQ0KPiBVbml2ZXJzaXRhJyBkaSBSb21hICJUb3IgVmVyZ2F0YSINCj4gVmlhIGRlbCBQ
b2xpdGVjbmljbyAxLCAwMDEzMyBSb21hLCBJdGFseQ0KPiBUZWwuOiArMzktMDYtNzI1OS03NDQ1
DQo+IEZheCA6ICszOS0wNi03MjU5LTc0MzUNCj4gTW9iaWxlOiArMzktMzIwLTQzOTE5MDkNCj4g
ZW1haWw6IGFuZHJlYS5kZXR0aUB1bmlyb21hMi5pdA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0K

From daveoran@orandom.net  Sat Oct 27 07:41:41 2012
Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B108E21F8551 for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvUHGYqy19MX for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:41:40 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2001:470:d:21b:3c00::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9935E21F854F for <icnrg@irtf.org>; Sat, 27 Oct 2012 07:41:40 -0700 (PDT)
Received: from stealth-10-32-245-152.cisco.com (c-66-31-41-8.hsd1.ma.comcast.net [66.31.41.8]) (authenticated bits=0) by spark.crystalorb.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9REfdGH021570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Oct 2012 07:41:40 -0700
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: David R Oran <daveoran@orandom.net>
In-Reply-To: <1745C882-C9B9-4E9E-9F1D-77CDC074C238@ucl.ac.uk>
Date: Sat, 27 Oct 2012 10:41:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E04FEF9-D474-4BFA-BA08-06119FD4D8F4@orandom.net>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <1745C882-C9B9-4E9E-9F1D-77CDC074C238@ucl.ac.uk>
To: Ioannis Psaras <i.psaras@ucl.ac.uk>
X-Mailer: Apple Mail (2.1499)
Cc: Ignacio.Solis@parc.com, icnrg@irtf.org, spis@intracom.com, Bengt Ahlgren <bengta@sics.se>, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2012 14:41:41 -0000

On Oct 24, 2012, at 11:58 AM, Ioannis Psaras <i.psaras@ucl.ac.uk> wrote:

> Hi Spiros,
>=20
> I don't think ICN (caching in particular) and the CDN model have =
conflicting goals: there is (and will always be) a need for permanently =
storing content.
Please define "permanent".

> Whether performance can improve due to caching is a different =
discussion IMO and not necessarily in the interest of CDNs. This is =
(part of) the reason why we have CDNs anyway - otherwise ISPs could =
deploy their own servers/CDNs (which they do to an extend, but always =
within their own domain).
>=20
> ICN (caching) may improve performance and this is where ISPs should =
focus on to see whether it's good/profitable for them to deploy.
ICN =E2=89=A0 caching

>=20
> Regards,
> Yiannis.
>=20
> On 24 Oct 2012, at 10:14, Spiros Spirou wrote:
>=20
>> Hi Bengt!
>>=20
>> If ICN does not provide any sort of better-than-best-effort delivery, =
then it seems (to me at least) that neither ISPs nor content providers =
have any significant incentive to adopt ICN. They can simply stick with =
the entrenched CDN technology and business model where all stekeholders =
(end-users, ISPs, CDN operators, and content providers/owners) seem to =
be happy enough.
>>=20
>> If, on the other hand, ICN does provide guarantees in delivery, then =
ICN and CDN seem likely to become competitors, as they would be offering =
a very similar service. The question for me is why would ISPs risk =
losing existing revenue from CDN operators in favor of capital =
expenditure for deploying ICN? There's of course the hope that content =
providers would be lured away from CDN, but this seems realistic only if =
ICN is cheaper or somehow better than CDN.
>>=20
>> Spiros
>>=20
>> On 23/10/2012 10:39 =CE=BC=CE=BC, Bengt Ahlgren wrote:
>>> I agree with Nacho, but would like to add an angle to this =
discussion!
>>>=20
>>> CDN, IMO, is more a business model than a particular set of =
protocols
>>> and services.  CDN operators agree to deliver the content of =
particular
>>> publishers for a fee at some level of service.  Whether this is done =
on
>>> an IP network or something else is not really important.
>>>=20
>>> ICN is a different set of protocols and services compared to IP, but =
not
>>> really a specific business model, although it may change the =
business
>>> playing field somewhat.  So, even though we can argue that ICN is =
good
>>> for content distribution, I don't think the CDN business becomes
>>> redundant.  There will still be content publishers that want to make
>>> sure that their content is delivered at some known level of service =
to
>>> their customers.  The "normal" ICN caching simply corresponds to =
current
>>> best-effort IP packet forwarding, with similar non-guarantee of =
service.
>>>=20
>>> Having said that, when the CDN folks now are starting to define
>>> particular protocols and interfaces (e.g., CDNI), they are working =
on
>>> stuff that touches ICN, but for supporting their particular purpose =
(the
>>> CDN business model).
>>>=20
>>> Bengt
>>>=20
>>> <Ignacio.Solis@parc.com> writes:
>>>=20
>>>> Hi Brian.
>>>>=20
>>>> You are right that for a subset of cases it seems like ICN is just
>>>> CDN, but that would be missing a lot of the picture.
>>>>=20
>>>> First, can you describe what the properties of native ICN and
>>>> non-native ICN are?  Is there no "router caching" in non-native =
ICN?
>>>>=20
>>>> A few of the things that don't seem to fit into traditional CDNs =
(with
>>>> my limited knowledge of state-of-the art CDNs) are:
>>>>=20
>>>> - Peer-to-peer.  How can CDNs help two nodes communicate without
>>>> infrastructure?  If two nodes meet in the field (such as in the =
DARPA
>>>> CBMEN program, or two phones on a plane or tunnel or ship), how can
>>>> CDNs help them exchange information?
>>>>=20
>>>> - Security. How can CDNs ensure the provenance of the data?
>>>>=20
>>>> - Disruption tolerance. How can CDNs enable data-muling?
>>>>=20
>>>> - Flow control. How can you change the way we do flow-control using =
CDNs?
>>>>=20
>>>> - Lone hit. How can CDNs help distribute data that was previously
>>>> unknown to the CDN. For example, from a random webpage.
>>>>=20
>>>>=20
>>>> Granted, some of those are somewhat possible using CDNs. Some of =
those
>>>> are possible with a little bit of work on CDNs and some are =
possible
>>>> with a lot of work.
>>>>=20
>>>> Everything is possible.
>>>>=20
>>>> But, we're going to get to a point where we're changing so much =
that
>>>> what we started with is unrecognizable.  Starting with CDNs is
>>>> limiting what we can do and how we do it.  The model many ICNs take =
is
>>>> a clean slate one. And as far as possible, we try to learn the =
lessons
>>>> of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, DNSs,
>>>> OSPFs, etc.
>>>>=20
>>>> Caching at the router level is one of the many potentially =
beneficial
>>>> (but not-required) characteristics of ICNs.
>>>>=20
>>>> If we talk about a specific ICN architecture (like CCN) we can talk
>>>> about specific advantages and disadvantages, tradeoffs made, work =
done
>>>> so far, work planned and work yet to be done.
>>>>=20
>>>> Nacho
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Nacho (Ignacio) Solis
>>>> Senior Research Scientist
>>>> Palo Alto Research Center (PARC)
>>>> +1(650) 812-4458
>>>> Ignacio.Solis@parc.com
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On Oct 18, 2012, at 2:54 PM, "Field, Brian" =
<Brian_Field@cable.comcast.com>
>>>> wrote:
>>>>=20
>>>>> Does anyone (beside me) think that a CDN effectively is already =
doing "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).  =
 I think of CDN and native ICN (where the router is caching and =
forwarding at the ICN level) nearly identical forwarding paradigms just =
operating at different levels in the stack.
>>>>>=20
>>>>> There's work in standardizing the intra-CDN  and inter-CDN control =
plan (in CDN-I and elsewhere).  IMO, it would be useful if we had the =
same control protocol operating in both the CDN and ICN domains and the =
"transition" was just changing the layer at which forwarding occurred.
>>>>>=20
>>>>> Brian
>>>>>=20
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf Of Will Liu (Shucheng)
>>>>> Sent: Thursday, October 18, 2012 3:08 AM
>>>>> To: B=CE=93=C2=B6rje Ohlman; Seung-Ik Lee
>>>>> Cc: =CE=B4=C2=BB=C2=BB=CE=B5=C2=A9=C2=A7; icnrg; Jianping Wang
>>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic =
which ISPs will definitely be interested in. Here are our 2-cents.
>>>>>=20
>>>>> The evolvement of ICN may take the following three =
implementations: integrated with IP, over IP and over SDN. These =
strategies all can help the ISP shift from the traditional IP to ICN. =
The only question is which one is the best choice for large scale =
deployment?
>>>>>=20
>>>>> Integrated with IP strategy extends the existing IP protocol (IP =
option) to support ICN. The updated IP router, called content router, =
will deal with such special packets. However, many routers with no =
support of such extension may directly drop the packets with an unknown =
IP option.
>>>>>=20
>>>>> ICN over IP strategy uses an overlay approach. Content-related =
operation will be performed on the high layer and Content-related =
information will be sent through a tunnel. Due to the limited knowledge =
of physical topology and unnecessary packet =
encapsulation/disconsolation, the efficiency may be limited.
>>>>>=20
>>>>> ICN over SDN strategy exploits SDN controller to perform =
content-related operation. However, SDN itself is an ongoing approach =
and is typically used in a local domain. The performance in a large =
scale deployment is unknown.
>>>>>=20
>>>>> Will
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf
>>>>>> Of B?rje Ohlman
>>>>>> Sent: Thursday, October 18, 2012 10:55 AM
>>>>>> To: Seung-Ik Lee
>>>>>> Cc: icnrg
>>>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>>>=20
>>>>>> Dear Seung-Ik,
>>>>>>=20
>>>>>> I think you bring up a very good point. I agree that deployment =
and
>>>>>> migration issues are very important. I also agree that they don't =
seem
>>>>>> like a good fit for any of the currently proposed ICNRG =
documents.
>>>>>>=20
>>>>>> The three documents listed as current work items are in no way =
set in
>>>>>> stone, they should just be seen as a starting point for our work. =
If
>>>>>> you would like to propose the RG that we should start working on =
a
>>>>>> deployment document you are most welcome to do so, that will most
>>>>>> certainly be in scope for our discussion in Atlanta.
>>>>>>=20
>>>>>> As a general comment I also like to mention that we as an RG are =
not
>>>>>> bound by all the rules that apply to IETF WGs, e.g. we are free =
to
>>>>>> discuss late contributions produced after the IETF draft =
deadlines. So
>>>>>> if people find the time to write up some material for the ICNRG =
after
>>>>>> the IETF drafts are done they are welcome to announce it to the =
ICNRG
>>>>>> mailing list. If the group agrees we are free to discuss also =
such
>>>>>> material at our meeting,
>>>>>>=20
>>>>>>    B=CE=93=C2=B6rje
>>>>>>=20
>>>>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" =
<seungiklee@etri.re.kr>:
>>>>>>=20
>>>>>>> Dear icnrg colleagues,
>>>>>>>=20
>>>>>>> Regarding the RG documents, don't we touch any issues on ICN
>>>>>> deployments?
>>>>>>>=20
>>>>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs =
are
>>>>>>> interested in the short-term approaches to ICN.
>>>>>>> Though the traditional ICN approaches (such as CCN/NDN) have
>>>>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have =
difficulties
>>>>>>> on clean-slate approaches of ICN.
>>>>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean =
ISPs
>>>>>>> are in the similar situation.
>>>>>>>=20
>>>>>>> In this motivation, I have interests in ICN deployment =
strategies
>>>>>>> (such as ICN over IP or ICN over SDN as short-term approaches) =
but
>>>>>>> no idea which RG document would cover the deployment issues, =
even
>>>>>>> whether icnrg will cover the deployment issue or not.
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> 2012/10/8 B=CE=93=C2=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, USA,
>>>>>> November
>>>>>>>> 4-9, 2012
>>>>>>>>    * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>>>>=20
>>>>>>>> The main discussion at the meeting will be the three documents =
that
>>>>>>>> the
>>>>>> RG
>>>>>>>> has set out to produce.
>>>>>>>>=20
>>>>>>>> ICN Survey document
>>>>>>>>=20
>>>>>>>> A document that provides a survey of different approaches and
>>>>>> techniques
>>>>>>>>=20
>>>>>>>> ICN Problem statement
>>>>>>>>=20
>>>>>>>> A document that describes the ICN problem statement, the main
>>>>>> concepts and
>>>>>>>> research challenges in depth.
>>>>>>>>=20
>>>>>>>> ICN Baseline Scenarios
>>>>>>>>=20
>>>>>>>> A document that defines reference baseline scenarios to enable
>>>>>> performance
>>>>>>>> comparisons between different approaches.
>>>>>>>>=20
>>>>>>>> People are encouraged to present their views on what they think
>>>>>>>> should
>>>>>> be
>>>>>>>> the contents of these documents. Early contributions (in bullet
>>>>>>>> form or as draft text) are welcome both on the mailing list and =
the wiki.
>>>>>> Presentations
>>>>>>>> of draft material are welcome at the meeting.
>>>>>>>>=20
>>>>>>>> Most likely we will also have time to discuss one or two =
specific
>>>>>>>> technical topics at the meeting. Proposals for such topics as =
well
>>>>>>>> as presentations are invited.
>>>>>>>>=20
>>>>>>>> As we are expected to publish our agenda by 2012-10-24 =
(Wednesday)
>>>>>>>> we
>>>>>> would
>>>>>>>> like to have your input by Sunday 2012-10-21.
>>>>>>>>=20
>>>>>>>> B=CE=93=C2=B6rje, Dave & Dirk
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> ICN RG Wiki:
>>>>>>>>=20
>>>>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From dlake@cisco.com  Sat Oct 27 07:46:25 2012
Return-Path: <dlake@cisco.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4342A21F84DA for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level: 
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id daJL45azfcNk for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:46:24 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5028521F84B9 for <icnrg@irtf.org>; Sat, 27 Oct 2012 07:46:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3567; q=dns/txt; s=iport; t=1351349184; x=1352558784; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tL31EYYjOR51i8+Hc77OfFnFJzcLmHxDWrFAbUioOHc=; b=Mmo6hzcaxnwu5twoyFM40HVaDCp4W/NDrAuYClR1R2kdG7N5/GB8qd24 z3FdPio80IPZJGFly4eIIalLf0HqckustPI5eFPHAz3/x0yHky8DukcGY 911iSsZXt7WJ2g2bGw3KIaZIT9bSMYPW3Sfbjyvq9D7lj60OqAsfUJGTY E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEPzi1CtJXG8/2dsb2JhbABAA8JbgQiCHgEBAQMBAQEBDwFbCwULAgEIGC4hBgslAgQOBRsHh1IDCQYLnCeWBA2JUASLDmcggxSCSGEDiCSLe4FViy+DJYFrgm+BXB8
X-IronPort-AV: E=Sophos;i="4.80,662,1344211200"; d="scan'208";a="136043093"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 27 Oct 2012 14:46:23 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9REkN4m026157 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 27 Oct 2012 14:46:23 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.239]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.001; Sat, 27 Oct 2012 09:46:22 -0500
From: "David Lake (dlake)" <dlake@cisco.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
Thread-Topic: [icnrg] Announcing ICNRG @ IETF 85
Thread-Index: AQHNsVaNOYTb8FHbREesns7kHfbO45fIgP4AgABwSYCAAE+xAIAACWUAgAC0fYCAA0Ijaw==
Date: Sat, 27 Oct 2012 14:46:22 +0000
Message-ID: <96FF79F3-3F63-4509-8754-9E70F0BCC6BB@cisco.com>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com> <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com> <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>, <FAFF11DF-6427-4C32-88D2-A7DC78BA5C23@ericsson.com>
In-Reply-To: <FAFF11DF-6427-4C32-88D2-A7DC78BA5C23@ericsson.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19314.001
x-tm-as-result: No--55.067400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: icnrg <icnrg@irtf.org>, "Brian_Field@cable.comcast.com" <Brian_Field@cable.comcast.com>, Bengt Ahlgren <bengta@sics.se>, Damien Saucez <damien.saucez@gmail.com>, "Ignacio.Solis@parc.com> <Ignacio.Solis@parc.com" <Ignacio.Solis@parc.com>, Spiros Spirou <spis@intracom.com>
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2012 14:46:25 -0000

Please correct me if I'm wrong, but I thought that ICN was to do with a new=
 way of locating content and the distribution mechanism associated with tha=
t, not content storage ?

David

Sent from my iPhone

On 25 Oct 2012, at 01:01, "B=F6rje Ohlman" <Borje.Ohlman@ericsson.com> wrot=
e:

> Some comments on this discussion. It is clearly important to define metri=
cs for comparing the how efficiently content can be distributed using diffe=
rent solutions. We should make sure to do it in such a way, that in additio=
n to compare a specific ICN technology with existing CDN solutions, we are =
also able to compare different ICN solutions with each other. That is what =
we are aiming for with the 'ICN Baseline Scenarios' document.
>=20
> A second comment is that, even if providing inherent CDN functionality is=
 a key feature of ICN, I don't think it is the most important feature of IC=
N. To me the idea of an application independent naming scheme for informati=
on/data objects bears even greater potential, especially for application de=
velopers that more easily can reuse information bases from one application =
to another. Also having the pub/sub like API to ICN opens the door to inclu=
de a lot of nice features into the network in a way that is transparent to =
the application developers. Examples of such features include p2p-functiona=
lity, seamless mobility, DTN-functionality, ...
>=20
>    B=F6rje
>=20
> On 24 okt 2012, at 23:14, <Ignacio.Solis@parc.com>
> <Ignacio.Solis@parc.com> wrote:
>=20
>> On Oct 24, 2012, at 4:41 PM, Damien Saucez <damien.saucez@gmail.com>
>> wrote:
>>=20
>>> Hello,
>>> On 24 Oct 2012, at 17:56, Ignacio.Solis@parc.com wrote:
>>>=20
>>>> "Best-effort" for some ICNs has different characteristics that IP best=
-effort, so comparing it directly might not be accurate.   For all we know =
ICNs best-effort is better-than-IP-best-effort.
>>>=20
>>> How do you define better-than? What is the metric? Which criterion?
>>>=20
>>> Thank you in advance for the clarification.
>>=20
>> That is exactly my question, we haven't defined that.
>>=20
>> How is multicast best-effort different than non-multicast best effort?  =
You can't compare easily.  This was exactly my point to the critique of:  "=
If ICN does not provide any sort of better-than-best-effort delivery, then =
it seems (to me at least) that neither ISPs nor content providers have any =
significant incentive to adopt ICN." that Spiros brought up. I was commenti=
ng on the better-than-best-effort qualification.
>>=20
>> I could construct scenarios where best effort ICN (CCN in my example) ca=
n achieve better-than-IP-best-effort for delivery, delay and availability. =
 I could also construct scenarios where IP might have less overhead. I was =
just pointing out that comparing "best-efforts" in a general is not trivial=
.
>>=20
>> ICN is still a research topic. It doesn't have all the answers and there=
 are many open questions. Yes, there is some overlap with CDNs, but they ar=
e not in direct competition.
>>=20
>>=20
>> Nacho
>>=20
>>=20
>> --
>> Nacho (Ignacio) Solis
>> Senior Research Scientist
>> Palo Alto Research Center (PARC)
>> +1(650) 812-4458
>> Ignacio.Solis@parc.com
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

From daveoran@orandom.net  Sat Oct 27 07:48:37 2012
Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B6E21F84FC for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MThaSUGyyRPc for <icnrg@ietfa.amsl.com>; Sat, 27 Oct 2012 07:48:36 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2001:470:d:21b:3c00::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8353C21F84DA for <icnrg@irtf.org>; Sat, 27 Oct 2012 07:48:36 -0700 (PDT)
Received: from stealth-10-32-245-152.cisco.com (c-66-31-41-8.hsd1.ma.comcast.net [66.31.41.8]) (authenticated bits=0) by spark.crystalorb.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9REmVb8021622 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 27 Oct 2012 07:48:32 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: David R Oran <daveoran@orandom.net>
In-Reply-To: <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>
Date: Sat, 27 Oct 2012 10:48:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F003F453-2CBD-4AC9-BC92-245340E990DA@orandom.net>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <F8E6C815CCDF764DA766988AF300DBF636C35FD1@e2010dag5.corp.ad.parc.com> <B7589521-5643-4CD5-A278-736EA6147A56@gmail.com> <F8E6C815CCDF764DA766988AF300DBF636C3756B@e2010dag5.corp.ad.parc.com>
To: Ignacio.Solis@parc.com
X-Mailer: Apple Mail (2.1499)
Cc: damien.saucez@gmail.com, spis@intracom.com, icnrg@irtf.org, bengta@sics.se, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2012 14:48:37 -0000

Some definitions that might be pertinent to the discussion:

"Best Effort" - up to a higher level to decide if something worked or =
not. It is not a measure of relative quality of a service compared to a =
service which claims to have stronger semantics.

"Guaranteed delivery" - a service which makes more than minimal effort =
to tell you when it is broken. It is not a measure of actually working =
any better than a service with weaker semantics.

DaveO.


On Oct 24, 2012, at 5:14 PM, Ignacio.Solis@parc.com wrote:

> On Oct 24, 2012, at 4:41 PM, Damien Saucez <damien.saucez@gmail.com>
> wrote:
>=20
>> Hello,
>> On 24 Oct 2012, at 17:56, Ignacio.Solis@parc.com wrote:
>>=20
>>> "Best-effort" for some ICNs has different characteristics that IP =
best-effort, so comparing it directly might not be accurate.   For all =
we know ICNs best-effort is better-than-IP-best-effort.
>>=20
>> How do you define better-than? What is the metric? Which criterion?
>>=20
>> Thank you in advance for the clarification.
>=20
> That is exactly my question, we haven't defined that.
>=20
> How is multicast best-effort different than non-multicast best effort? =
 You can't compare easily.  This was exactly my point to the critique =
of:  "If ICN does not provide any sort of better-than-best-effort =
delivery, then it seems (to me at least) that neither ISPs nor content =
providers have any significant incentive to adopt ICN." that Spiros =
brought up. I was commenting on the better-than-best-effort =
qualification.
>=20
> I could construct scenarios where best effort ICN (CCN in my example) =
can achieve better-than-IP-best-effort for delivery, delay and =
availability.  I could also construct scenarios where IP might have less =
overhead. I was just pointing out that comparing "best-efforts" in a =
general is not trivial.
>=20
> ICN is still a research topic. It doesn't have all the answers and =
there are many open questions. Yes, there is some overlap with CDNs, but =
they are not in direct competition.
>=20
>=20
> Nacho
>=20
>=20
> --
> Nacho (Ignacio) Solis
> Senior Research Scientist
> Palo Alto Research Center (PARC)
> +1(650) 812-4458
> Ignacio.Solis@parc.com
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From i.psaras@ucl.ac.uk  Sun Oct 28 15:48:20 2012
Return-Path: <i.psaras@ucl.ac.uk>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B07721F867B for <icnrg@ietfa.amsl.com>; Sun, 28 Oct 2012 15:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.399
X-Spam-Level: 
X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYrsH0C8maxj for <icnrg@ietfa.amsl.com>; Sun, 28 Oct 2012 15:48:19 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 48F3721F84A2 for <icnrg@irtf.org>; Sun, 28 Oct 2012 15:48:18 -0700 (PDT)
Received: from mail132-co1-R.bigfish.com (10.243.78.238) by CO1EHSOBE004.bigfish.com (10.243.66.67) with Microsoft SMTP Server id 14.1.225.23; Sun, 28 Oct 2012 22:48:17 +0000
Received: from mail132-co1 (localhost [127.0.0.1])	by mail132-co1-R.bigfish.com (Postfix) with ESMTP id 6FFA61200A0; Sun, 28 Oct 2012 22:48:17 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.9.135; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0104HT003.eurprd01.prod.exchangelabs.com; RD:none; EFVD:NLI
X-SpamScore: -29
X-BigFish: PS-29(zzbb2dI98dI9371Ic89bh936eI542M1432Izz1d18h1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h8e2h8e3h93fhd25he5bhf0ah1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537hbe9i1155h)
Received: from mail132-co1 (localhost.localdomain [127.0.0.1]) by mail132-co1 (MessageSwitch) id 1351464495325010_753; Sun, 28 Oct 2012 22:48:15 +0000 (UTC)
Received: from CO1EHSMHS016.bigfish.com (unknown [10.243.78.241])	by mail132-co1.bigfish.com (Postfix) with ESMTP id 4A60DAC0047; Sun, 28 Oct 2012 22:48:15 +0000 (UTC)
Received: from DB3PRD0104HT003.eurprd01.prod.exchangelabs.com (157.55.9.135) by CO1EHSMHS016.bigfish.com (10.243.66.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 28 Oct 2012 22:48:12 +0000
Received: from [192.168.1.88] (149.241.250.72) by pod51002.outlook.com (10.3.186.97) with Microsoft SMTP Server (TLS) id 14.15.129.3; Sun, 28 Oct 2012 22:48:10 +0000
MIME-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="utf-8"
From: Ioannis Psaras <i.psaras@ucl.ac.uk>
In-Reply-To: <4E04FEF9-D474-4BFA-BA08-06119FD4D8F4@orandom.net>
Date: Sun, 28 Oct 2012 22:48:07 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <2999BFEC-C691-4D4F-AC08-8606A1ED20FF@ucl.ac.uk>
References: <C5E8CB0E-A617-4209-A072-C47E76786F75@ericsson.com> <CAHMWmA-XtupzBojNZEoZSJBiEcxkFCPGSo0ozyC=nBvge7hkjg@mail.gmail.com> <D89FCA8A-8AD1-46A2-8CCB-D936CD5E4EB9@ericsson.com> <C9B5F12337F6F841B35C404CF0554ACB2B98E155@szxeml546-mbs.china.huawei.com> <CA76207EE5EB484793FE8BB49C7B44575F46FCF8@COPDCEXMB07.cable.comcast.com> <F8E6C815CCDF764DA766988AF300DBF636C0FC75@e2010dag5.corp.ad.parc.com> <uh7zk3dq8oy.fsf@P142.sics.se> <5087B162.9040305@intracom.com> <1745C882-C9B9-4E9E-9F1D-77CDC074C238@ucl.ac.uk> <4E04FEF9-D474-4BFA-BA08-06119FD4D8F4@orandom.net>
To: David R Oran <daveoran@orandom.net>
X-Mailer: Apple Mail (2.1084)
X-Originating-IP: [149.241.250.72]
X-UCLLIVE-SCLRULE: HASRUN
X-OriginatorOrg: ucl.ac.uk
Cc: Ignacio.Solis@parc.com, spis@intracom.com, icnrg@irtf.org, Bengt Ahlgren <bengta@sics.se>, Brian_Field@cable.comcast.com
Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 22:48:20 -0000

Hi David,

>> I don't think ICN (caching in particular) and the CDN model have =
conflicting goals: there is (and will always be) a need for permanently =
storing content.
> Please define "permanent".

I mean a CDN-like service.

Caching cannot guarantee that something will be found after some time in =
that place. Permanent storage guarantees that content will be there =
until some other agreement is made between the storage provider (CDN in =
this case) and the content provider.

>=20
>> Whether performance can improve due to caching is a different =
discussion IMO and not necessarily in the interest of CDNs. This is =
(part of) the reason why we have CDNs anyway - otherwise ISPs could =
deploy their own servers/CDNs (which they do to an extend, but always =
within their own domain).
>>=20
>> ICN (caching) may improve performance and this is where ISPs should =
focus on to see whether it's good/profitable for them to deploy.
> ICN =E2=89=A0 caching

Absolutely!

Regards,
Yiannis.

>=20
>>=20
>> Regards,
>> Yiannis.
>>=20
>> On 24 Oct 2012, at 10:14, Spiros Spirou wrote:
>>=20
>>> Hi Bengt!
>>>=20
>>> If ICN does not provide any sort of better-than-best-effort =
delivery, then it seems (to me at least) that neither ISPs nor content =
providers have any significant incentive to adopt ICN. They can simply =
stick with the entrenched CDN technology and business model where all =
stekeholders (end-users, ISPs, CDN operators, and content =
providers/owners) seem to be happy enough.
>>>=20
>>> If, on the other hand, ICN does provide guarantees in delivery, then =
ICN and CDN seem likely to become competitors, as they would be offering =
a very similar service. The question for me is why would ISPs risk =
losing existing revenue from CDN operators in favor of capital =
expenditure for deploying ICN? There's of course the hope that content =
providers would be lured away from CDN, but this seems realistic only if =
ICN is cheaper or somehow better than CDN.
>>>=20
>>> Spiros
>>>=20
>>> On 23/10/2012 10:39 =CE=BC=CE=BC, Bengt Ahlgren wrote:
>>>> I agree with Nacho, but would like to add an angle to this =
discussion!
>>>>=20
>>>> CDN, IMO, is more a business model than a particular set of =
protocols
>>>> and services.  CDN operators agree to deliver the content of =
particular
>>>> publishers for a fee at some level of service.  Whether this is =
done on
>>>> an IP network or something else is not really important.
>>>>=20
>>>> ICN is a different set of protocols and services compared to IP, =
but not
>>>> really a specific business model, although it may change the =
business
>>>> playing field somewhat.  So, even though we can argue that ICN is =
good
>>>> for content distribution, I don't think the CDN business becomes
>>>> redundant.  There will still be content publishers that want to =
make
>>>> sure that their content is delivered at some known level of service =
to
>>>> their customers.  The "normal" ICN caching simply corresponds to =
current
>>>> best-effort IP packet forwarding, with similar non-guarantee of =
service.
>>>>=20
>>>> Having said that, when the CDN folks now are starting to define
>>>> particular protocols and interfaces (e.g., CDNI), they are working =
on
>>>> stuff that touches ICN, but for supporting their particular purpose =
(the
>>>> CDN business model).
>>>>=20
>>>> Bengt
>>>>=20
>>>> <Ignacio.Solis@parc.com> writes:
>>>>=20
>>>>> Hi Brian.
>>>>>=20
>>>>> You are right that for a subset of cases it seems like ICN is just
>>>>> CDN, but that would be missing a lot of the picture.
>>>>>=20
>>>>> First, can you describe what the properties of native ICN and
>>>>> non-native ICN are?  Is there no "router caching" in non-native =
ICN?
>>>>>=20
>>>>> A few of the things that don't seem to fit into traditional CDNs =
(with
>>>>> my limited knowledge of state-of-the art CDNs) are:
>>>>>=20
>>>>> - Peer-to-peer.  How can CDNs help two nodes communicate without
>>>>> infrastructure?  If two nodes meet in the field (such as in the =
DARPA
>>>>> CBMEN program, or two phones on a plane or tunnel or ship), how =
can
>>>>> CDNs help them exchange information?
>>>>>=20
>>>>> - Security. How can CDNs ensure the provenance of the data?
>>>>>=20
>>>>> - Disruption tolerance. How can CDNs enable data-muling?
>>>>>=20
>>>>> - Flow control. How can you change the way we do flow-control =
using CDNs?
>>>>>=20
>>>>> - Lone hit. How can CDNs help distribute data that was previously
>>>>> unknown to the CDN. For example, from a random webpage.
>>>>>=20
>>>>>=20
>>>>> Granted, some of those are somewhat possible using CDNs. Some of =
those
>>>>> are possible with a little bit of work on CDNs and some are =
possible
>>>>> with a lot of work.
>>>>>=20
>>>>> Everything is possible.
>>>>>=20
>>>>> But, we're going to get to a point where we're changing so much =
that
>>>>> what we started with is unrecognizable.  Starting with CDNs is
>>>>> limiting what we can do and how we do it.  The model many ICNs =
take is
>>>>> a clean slate one. And as far as possible, we try to learn the =
lessons
>>>>> of CDNs, DTNs, IPs, Gnutellas, Multicast, RTPs, IPSecs, TCPs, =
DNSs,
>>>>> OSPFs, etc.
>>>>>=20
>>>>> Caching at the router level is one of the many potentially =
beneficial
>>>>> (but not-required) characteristics of ICNs.
>>>>>=20
>>>>> If we talk about a specific ICN architecture (like CCN) we can =
talk
>>>>> about specific advantages and disadvantages, tradeoffs made, work =
done
>>>>> so far, work planned and work yet to be done.
>>>>>=20
>>>>> Nacho
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Nacho (Ignacio) Solis
>>>>> Senior Research Scientist
>>>>> Palo Alto Research Center (PARC)
>>>>> +1(650) 812-4458
>>>>> Ignacio.Solis@parc.com
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Oct 18, 2012, at 2:54 PM, "Field, Brian" =
<Brian_Field@cable.comcast.com>
>>>>> wrote:
>>>>>=20
>>>>>> Does anyone (beside me) think that a CDN effectively is already =
doing "ICN" but tunneled over an HTTP infrastructure (via HTTP/TCP/IP).  =
 I think of CDN and native ICN (where the router is caching and =
forwarding at the ICN level) nearly identical forwarding paradigms just =
operating at different levels in the stack.
>>>>>>=20
>>>>>> There's work in standardizing the intra-CDN  and inter-CDN =
control plan (in CDN-I and elsewhere).  IMO, it would be useful if we =
had the same control protocol operating in both the CDN and ICN domains =
and the "transition" was just changing the layer at which forwarding =
occurred.
>>>>>>=20
>>>>>> Brian
>>>>>>=20
>>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf Of Will Liu (Shucheng)
>>>>>> Sent: Thursday, October 18, 2012 3:08 AM
>>>>>> To: B=CE=93=C2=B6rje Ohlman; Seung-Ik Lee
>>>>>> Cc: =CE=B4=C2=BB=C2=BB=CE=B5=C2=A9=C2=A7; icnrg; Jianping Wang
>>>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> My group are also interested in ICN deployment and have done some =
survey on this matter. The discussion on ICN deployment is a great topic =
which ISPs will definitely be interested in. Here are our 2-cents.
>>>>>>=20
>>>>>> The evolvement of ICN may take the following three =
implementations: integrated with IP, over IP and over SDN. These =
strategies all can help the ISP shift from the traditional IP to ICN. =
The only question is which one is the best choice for large scale =
deployment?
>>>>>>=20
>>>>>> Integrated with IP strategy extends the existing IP protocol (IP =
option) to support ICN. The updated IP router, called content router, =
will deal with such special packets. However, many routers with no =
support of such extension may directly drop the packets with an unknown =
IP option.
>>>>>>=20
>>>>>> ICN over IP strategy uses an overlay approach. Content-related =
operation will be performed on the high layer and Content-related =
information will be sent through a tunnel. Due to the limited knowledge =
of physical topology and unnecessary packet =
encapsulation/disconsolation, the efficiency may be limited.
>>>>>>=20
>>>>>> ICN over SDN strategy exploits SDN controller to perform =
content-related operation. However, SDN itself is an ongoing approach =
and is typically used in a local domain. The performance in a large =
scale deployment is unknown.
>>>>>>=20
>>>>>> Will
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: icnrg-bounces@irtf.org [mailto:icnrg-bounces@irtf.org] On =
Behalf
>>>>>>> Of B?rje Ohlman
>>>>>>> Sent: Thursday, October 18, 2012 10:55 AM
>>>>>>> To: Seung-Ik Lee
>>>>>>> Cc: icnrg
>>>>>>> Subject: Re: [icnrg] Announcing ICNRG @ IETF 85
>>>>>>>=20
>>>>>>> Dear Seung-Ik,
>>>>>>>=20
>>>>>>> I think you bring up a very good point. I agree that deployment =
and
>>>>>>> migration issues are very important. I also agree that they =
don't seem
>>>>>>> like a good fit for any of the currently proposed ICNRG =
documents.
>>>>>>>=20
>>>>>>> The three documents listed as current work items are in no way =
set in
>>>>>>> stone, they should just be seen as a starting point for our =
work. If
>>>>>>> you would like to propose the RG that we should start working on =
a
>>>>>>> deployment document you are most welcome to do so, that will =
most
>>>>>>> certainly be in scope for our discussion in Atlanta.
>>>>>>>=20
>>>>>>> As a general comment I also like to mention that we as an RG are =
not
>>>>>>> bound by all the rules that apply to IETF WGs, e.g. we are free =
to
>>>>>>> discuss late contributions produced after the IETF draft =
deadlines. So
>>>>>>> if people find the time to write up some material for the ICNRG =
after
>>>>>>> the IETF drafts are done they are welcome to announce it to the =
ICNRG
>>>>>>> mailing list. If the group agrees we are free to discuss also =
such
>>>>>>> material at our meeting,
>>>>>>>=20
>>>>>>>   B=CE=93=C2=B6rje
>>>>>>>=20
>>>>>>> 18 okt 2012 kl. 03:56 skrev "Seung-Ik Lee" =
<seungiklee@etri.re.kr>:
>>>>>>>=20
>>>>>>>> Dear icnrg colleagues,
>>>>>>>>=20
>>>>>>>> Regarding the RG documents, don't we touch any issues on ICN
>>>>>>> deployments?
>>>>>>>>=20
>>>>>>>> As we have seen in the presentation by ZTE in Vancouver, ISPs =
are
>>>>>>>> interested in the short-term approaches to ICN.
>>>>>>>> Though the traditional ICN approaches (such as CCN/NDN) have
>>>>>>>> provided ISPs a ladder out of dumb-pipes, ISPs may have =
difficulties
>>>>>>>> on clean-slate approaches of ICN.
>>>>>>>> IMHO, based on our surveys on ISP R&D approaches to ICN, Korean =
ISPs
>>>>>>>> are in the similar situation.
>>>>>>>>=20
>>>>>>>> In this motivation, I have interests in ICN deployment =
strategies
>>>>>>>> (such as ICN over IP or ICN over SDN as short-term approaches) =
but
>>>>>>>> no idea which RG document would cover the deployment issues, =
even
>>>>>>>> whether icnrg will cover the deployment issue or not.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> 2012/10/8 B=CE=93=C2=B6rje Ohlman <Borje.Ohlman@ericsson.com>:
>>>>>>>>> The next ICNRG will be held at  IETF 85, Atlanta, Georgia, =
USA,
>>>>>>> November
>>>>>>>>> 4-9, 2012
>>>>>>>>>   * Meeting time: WEDNESDAY 13.00-15.40 (prel)
>>>>>>>>>=20
>>>>>>>>> The main discussion at the meeting will be the three documents =
that
>>>>>>>>> the
>>>>>>> RG
>>>>>>>>> has set out to produce.
>>>>>>>>>=20
>>>>>>>>> ICN Survey document
>>>>>>>>>=20
>>>>>>>>> A document that provides a survey of different approaches and
>>>>>>> techniques
>>>>>>>>>=20
>>>>>>>>> ICN Problem statement
>>>>>>>>>=20
>>>>>>>>> A document that describes the ICN problem statement, the main
>>>>>>> concepts and
>>>>>>>>> research challenges in depth.
>>>>>>>>>=20
>>>>>>>>> ICN Baseline Scenarios
>>>>>>>>>=20
>>>>>>>>> A document that defines reference baseline scenarios to enable
>>>>>>> performance
>>>>>>>>> comparisons between different approaches.
>>>>>>>>>=20
>>>>>>>>> People are encouraged to present their views on what they =
think
>>>>>>>>> should
>>>>>>> be
>>>>>>>>> the contents of these documents. Early contributions (in =
bullet
>>>>>>>>> form or as draft text) are welcome both on the mailing list =
and the wiki.
>>>>>>> Presentations
>>>>>>>>> of draft material are welcome at the meeting.
>>>>>>>>>=20
>>>>>>>>> Most likely we will also have time to discuss one or two =
specific
>>>>>>>>> technical topics at the meeting. Proposals for such topics as =
well
>>>>>>>>> as presentations are invited.
>>>>>>>>>=20
>>>>>>>>> As we are expected to publish our agenda by 2012-10-24 =
(Wednesday)
>>>>>>>>> we
>>>>>>> would
>>>>>>>>> like to have your input by Sunday 2012-10-21.
>>>>>>>>>=20
>>>>>>>>> B=CE=93=C2=B6rje, Dave & Dirk
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> ICN RG Wiki:
>>>>>>>>>=20
>>>>>>>>> http://trac.tools.ietf.org/group/irtf/trac/wiki/icnrg
>>>> _______________________________________________
>>>> icnrg mailing list
>>>> icnrg@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/icnrg
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>>=20
>>=20
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg



From Dirk.Kutscher@neclab.eu  Tue Oct 30 09:14:09 2012
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B39121F85EB for <icnrg@ietfa.amsl.com>; Tue, 30 Oct 2012 09:14:09 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwulfsmiWFFP for <icnrg@ietfa.amsl.com>; Tue, 30 Oct 2012 09:14:09 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 06A7221F84CD for <icnrg@irtf.org>; Tue, 30 Oct 2012 09:14:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 5786D10238C for <icnrg@irtf.org>; Tue, 30 Oct 2012 17:14:08 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UA1ng7+wjnpx for <icnrg@irtf.org>; Tue, 30 Oct 2012 17:14:08 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 3E2D110238A for <icnrg@irtf.org>; Tue, 30 Oct 2012 17:14:03 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.239]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Tue, 30 Oct 2012 17:13:25 +0100
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: draft agenda for ATL posted
Thread-Index: Ac22uVShxmGCe3GeQ2SYUp7ekjuuWg==
Date: Tue, 30 Oct 2012 16:13:24 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F524955112F53@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.204]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [icnrg] draft agenda for ATL posted
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2012 16:14:09 -0000

See http://www.ietf.org/proceedings/85/agenda/agenda-85-icnrg


Thanks,
Dirk




From borje.ohlman@ericsson.com  Tue Oct 30 22:41:18 2012
Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD67421F851E for <icnrg@ietfa.amsl.com>; Tue, 30 Oct 2012 22:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+ovYBWpVoAq for <icnrg@ietfa.amsl.com>; Tue, 30 Oct 2012 22:41:18 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id DE21321F850D for <icnrg@irtf.org>; Tue, 30 Oct 2012 22:41:17 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f1e6d000002d2c-f3-5090b9fb43cd
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id D3.46.11564.BF9B0905; Wed, 31 Oct 2012 06:41:16 +0100 (CET)
Received: from abro.ki.sw.ericsson.se (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Wed, 31 Oct 2012 06:41:15 +0100
Received: from [IPv6:::1] (abro.ki.sw.ericsson.se [147.214.177.159])	by abro.ki.sw.ericsson.se (Postfix) with ESMTP id 1184416AC654; Wed, 31 Oct 2012 06:41:14 +0100 (CET)
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
In-Reply-To: <82AB329A76E2484D934BBCA77E9F524955112F53@DAPHNIS.office.hd>
Date: Wed, 31 Oct 2012 06:41:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <D3E72BF7-9795-4417-ACDD-CB804BE8DC1A@ericsson.com>
References: <82AB329A76E2484D934BBCA77E9F524955112F53@DAPHNIS.office.hd>
To: icnrg <icnrg@irtf.org>
X-Mailer: Apple Mail (2.1278)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42KZGfG3VvfPzgkBBrPesFo8fJRusXP2TiYH Jo/JGw+zecw49pI9gCmKyyYlNSezLLVI3y6BK+PopH72gvlsFa2XAhoYe1i7GDk5JARMJDaf 2coOYYtJXLi3nq2LkYtDSOAko8SFL5OgnE2MEud/HmGFcNYxSpw60AnkcHAICxhITGt3BDF5 BQwlOg/ngAxiFtCTuDF1ChuIzSbgKPG4ZT3YMk4BT4m3m3rAlrEIqErMeXWSCaJeW+LTusOM MPayha+ZIUbaSxx94A4SFhLwkDjb+RisVURASmLT3rtsEDfLStxunsAOUaMmMePjI6YJjEKz EA6aheSgWUgWLGBkXsXInpuYmZNebriJERiiB7f81t3BeOqcyCFGaQ4WJXFerqT9/kIC6Ykl qdmpqQWpRfFFpTmpxYcYmTg4pRoYOxc0+S30Zz7ZMvGRQvmjXfbGAe0tdxJ2rrnjNOuMkGtO L+dmo2WdWY4/muJOX3KYov9nWmnM3dVSPRdM/qy48X5B/kGudImSq9JZhgw7l7kf4jyqp6J6 wvDJ7HNcvmwzNgvPfM3b2P/mD9sVz+cOnXF7Yk7V2fO9t95x+uDduwmXvbg8pqd/UGIpzkg0 1GIuKk4EAMZ1S58fAgAA
Cc: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
Subject: Re: [icnrg] draft agenda for ATL posted
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 05:41:18 -0000

Just some clarifications.
We've decided to stay on Wednesday, considering all the requests and the =
inherent disadvantage of moving things around it didn't seem to make =
sense to move the ICNRG meeting.
But please note that we will keep *both* the scheduled sessions on =
Wednesday: 13:00 -- 14:30 AND 1440-1540. The presently posted agenda =
crams everything into the first slot, but we will have more time. We =
will update the agenda to reflect this.

Best regards,
			B=F6rje

On 30 okt 2012, at 17:13, Dirk Kutscher wrote:

> See http://www.ietf.org/proceedings/85/agenda/agenda-85-icnrg
>=20
>=20
> Thanks,
> Dirk
>=20
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From andrea.detti@uniroma2.it  Wed Oct 31 10:19:52 2012
Return-Path: <andrea.detti@uniroma2.it>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E079F21F87E8 for <icnrg@ietfa.amsl.com>; Wed, 31 Oct 2012 10:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.907
X-Spam-Level: 
X-Spam-Status: No, score=-2.907 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4, SARE_SPEC_REPLICA_OBFU=1.812]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DurAUd0js3Ap for <icnrg@ietfa.amsl.com>; Wed, 31 Oct 2012 10:19:51 -0700 (PDT)
Received: from smtp.uniroma2.it (smtp.uniroma2.it [160.80.6.23]) by ietfa.amsl.com (Postfix) with ESMTP id F24A421F87DB for <icnrg@irtf.org>; Wed, 31 Oct 2012 10:19:48 -0700 (PDT)
Received: from smtpauth.uniroma2.it (smtpauth.uniroma2.it [160.80.6.46]) by smtp.uniroma2.it (8.13.6/8.13.6) with ESMTP id q9VHFsRh032227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 Oct 2012 18:15:56 +0100
Received: from [192.168.1.120] ([160.80.82.70]) (authenticated bits=0) by smtpauth.uniroma2.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id q9VHJPst009251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Oct 2012 18:19:27 +0100
Message-ID: <50915D9D.4080707@uniroma2.it>
Date: Wed, 31 Oct 2012 18:19:25 +0100
From: Andrea Detti <andrea.detti@uniroma2.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: "Will Liu (Shucheng)" <liushucheng@huawei.com>
References: <C9B5F12337F6F841B35C404CF0554ACB2B98BE77@szxeml546-mbs.china.huawei.com> <50814FFE.3090101@uniroma2.it> <C9B5F12337F6F841B35C404CF0554ACB2B9A243E@szxeml546-mbx.china.huawei.com>
In-Reply-To: <C9B5F12337F6F841B35C404CF0554ACB2B9A243E@szxeml546-mbx.china.huawei.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
X-MailScanner-From: andrea.detti@uniroma2.it
Cc: =?GB2312?B?yM7mug==?= <renjing@uestc.edu.cn>, "icnrg@irtf.org" <icnrg@irtf.org>
Subject: Re: [icnrg] FW: New Version Notification for draft-ren-icn-content-retrieval-00.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 17:19:53 -0000

Dear Will,
thank you for your interest in CONVERGENCE project.

Regarding multicast, we just published the Final Architecture of the
project (see D5.3 on http://www.ict-convergence.eu/deliverables/), where
we state in section 4.2.1

"The Data forwarding process exploits reverse-path information either
temporarily stored in the traversed nodes during the Interest forwarding
process (see Pending
Interest Table of [CCN]), or contained in the header of Data message,
and previously collected in
the Interest message during the forwarding process (see reverse-path
source-routing in [CONET ICN SIGCOM Paper] or
D3.2) "

So, depending on specific deployment choice, the CONET supports both PIT
and reverse-path source-routing Data forwarding mechanisms. In the
former case, we deal with multicast (synchronous and asynchronous, see
later) as CCN. In the second case, we only support "asynchronous"
multicast through in-network caching, as CCN. With the term asynchronous
multicast, I mean the case where requests of a same content object are
issued by different nodes in close, but different, times. In this case,
the first common in-network cache of the multicast tree rooted at source
acts as the splitting point of a multicast distribution tree (e.g. see
http://www.verivue.com/blog/index.php/cdn-architecture/asynchronous-multicast/).


Consequently, regarding multicast, I would revise the draft as follows:

"Receiver-driven multicast based on i) in-network
caching and ii) routing information temporary
left in network nodes (in case of using PIT based reverse-path approach)"

Regards,

Andrea


On 10/27/2012 12:55 PM, Will Liu (Shucheng) wrote:
> Dear Andrea,
>
> Sorry for being late. Many thanks for your valuable comments. 
>  
> When we were writing this draft, we classified name resolution mechanisms into two categories: route-by-name and DNS-like resolution system. We defined route-by-name as ˇ°routers disseminate name-based routing information with each other and forward packets based on the name-based routing tableˇ± (sorry that we did not write this definition clearly in the draft). From this point, we considered that CONET does not disseminate routing information, but establishes a DNS-like system. We ignored that CONET also deployed a route-cache mechanism. Thanks for pointing out this. We will rewrite the draft according to your suggestion. 
>  
> <k-anycast and multicast>
>  
> In conducting the survey of multicast mechanism, we read a few published CONET papers, such as [1][2]. We only find a few sentences about multicast, which stated that named-sap can be extended to multicast (see [1] sec1, [2] sec7.1). 
>  
> Regarding the PIT, I have a question. In [1] , it says that ˇ°This info will be used to find the reverse-path to route the named-data CIU back to the requesting node, in the delivery phase. In [3] the same goal is achieved by maintaining states in network nodes. We propose to use source-routing, being aware of the involved trade-offs, and given that we think that the number of traversed CONET border nodes should be rather limited (e.g. CSSs should coincide with Internet Autonomous Systems).ˇ±
>  
> According to the above information, we think that CONET takes a different way from CCN about multicast. Maybe we have missed some important literatures. Can you give us some references? Thank you so much.
>  
>  
>  
> [1]Detti, A., N. B. Melazzi, et al. (2011). CONET: a content centric inter-networking architecture. Proceedings of the ACM SIGCOMM workshop on Information-centric networking. Toronto, Ontario, Canada, ACM: 50-55.
> [2]ˇ°D3.2 - System architectureˇ±, CONVERGENCE deliverable
> [3] V. Jacobson, D. K. Smetters, J. D. Thornton et al., ˇ±Networking named contentˇ±, ACM CoNEXT 2009
>
> Regards,
> Will
>
>
>> -----Original Message-----
>> From: Andrea Detti [mailto:andrea.detti@uniroma2.it]
>> Sent: Friday, October 19, 2012 9:05 PM
>> To: icnrg@irtf.org; Will Liu (Shucheng)
>> Subject: Re: [icnrg] FW: New Version Notification for
>> draft-ren-icn-content-retrieval-00.txt
>>
>> Dear Will,
>>
>> I have some comments regarding the CONVERGENCE project, in which I am
>> involved.
>>
>> The CONVERGENCE network (CONET) is similar to CCNx; we complement it
>> with some missing functionality or we try to improve its performance,
>> e.g. routing [1], named-sap [2], transport, etc..
>>
>>
>> In what follows I propose some changes to the valuable description
>> provided by the draft, regarding how CONVERGENCE deals with the
>> following issues:
>>
>>
>>
>> <Content name resolution>
>>
>> the draft reports : "Dedicate Name-System-Nodes (similar to DNS) are
>> deployed"
>>
>> This sentence might be understood as: ˇ°to forward a content request, a
>> CONET node always queries the Name-System-Nodes to resolve the
>> next-hopˇ±.
>>
>> This is not true since, as CCNx, a CONET node usually resolves the
>> names, en-route, by means of a name-based forwarding information base
>> (FIB), i.e. without contacting the Name-System-Nodes (or better
>> Name-Routing-System nodes, see [1])
>>
>> However, current fast FIBs (e.g. based on SRAM) have a size unable to
>> store all possible name-prefixes.
>>
>> To cope with this issue, a CONET node uses the FIB as "route cache".
>>
>> If the node does not have the routing entry necessary to route-by-name
>> an Interest message, then the node lookups the routing information in
>> the Name-Routing-System and caches the routing entry in the FIB.
>>
>> Therefore, lookups occur only in cases of route-cache misses, which
>> should be a rare event.
>>
>> Furthermore, as general comment, I think that it could be important to
>> specify, for any project, if Content Name Resolution is performed at
>> packet-rate or only one-time per download, i.e. at session-rate.
>>
>> A CONET node performs name resolution at packet-rate by using a FIB and,
>> sometimes, by contacting nodes of a Name-Routing-System.
>>
>> Consequently, I would revise the draft as follows "En-route name
>> resolution performed at packet-rate by means of name-based forwarding
>> tables, which are used as route-caches. Route-cache misses are resolved
>> by means of a dedicated Name-Routing-Sytem node (similar to DNS)."
>>
>>
>>
>>
>> <k-anycast and multicast>
>>
>> the draft reports: " Traditional point-to-point sessions between two
>> upper layer entities can be supported by coupling the upper layer
>> entities with named-service-assess-points. This functionality can be
>> extended to support multicast"
>>
>>
>> I think that this is not completely true. Indeed, named-saps are not
>> meant for multicasting purpose, but [2] to support legacy point-to-point
>> interactive service sessions, e.g. home banking.
>>
>> Multicast is achieved in CCNx/CONET by exploiting both en-route
>> in-network caching and the mechanism of Pending Interest Table (PIT), as
>> described in [NDN].
>>
>> In case of a multicast service, e.g. video live streaming, many sources
>> send the same Interest message, e.g. to request the next video frame.
>> Using the PIT mechanism, in case of quite-synchronous Interests, or
>> using in-network caching, in case of nearly-synchronous Interest, the
>> same content chunk is transferred only one time, on a link of the
>> multicast tree rooted at source.
>>
>> Consequently, regarding multicast, I would revise the draft as follows:
>>
>> "Receiver-driven multicast based on i) routing information temporary
>> left in network nodes (aka Pending Interest Table) and ii) in-network
>> caching"
>>
>> Regarding k-multicast, I would revise the draft as follows
>> "Receiver-driven k-multicast, by concurrently fetching different data
>> chunks from the different replica Servers"
>>
>>
>>
>> <Content replication>
>>
>> it is OK
>>
>>
>>
>> <In-network cache discovery>
>>
>> it is OK
>>
>>
>>
>> Thanks a lot for your effort,
>>
>>
>>
>> Andrea
>>
>>
>>
>> [1] A. Detti, M. Pomposini, N. Blefari-Melazzi, S. Salsano, ˇ°Supporting
>> the Web with an Information Centric Network that Routes by Nameˇ±,
>> Elsevier Computer Networks, vol. 56, Issue 17, p. 3705¨C3722
>> (http://netgroup.uniroma2.it/Andrea_Detti/Lookup-and-Cache/comnet-web
>> -ICN-ext.pdf)
>>
>> [2] "D3.1 - Definition of the system services and functional
>> components", CONVERGENCE deliverable, see Section 4.1
>>
>>
>> On 10/15/2012 01:47 PM, Will Liu (Shucheng) wrote:
>>> Hello,
>>>
>>> We have submitted a new draft discussing about content retrieval in ICN.
>> Here, we discussed basic requirements on the basis of previous literatures,
>> the fundamental functionalities required to satisfy the foregoing
>> requirements, and the implementation status of such functionalities in
>> various Information-Centric Network architectures.
>>> Your comments are highly appreciated.
>>>
>>> Regards,
>>> Shucheng LIU (Will)
>>>
>>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Monday, October 15, 2012 7:26 PM
>>> To: Will Liu (Shucheng)
>>> Cc: jingren@cityu.edu.hk; jianwang@cityu.edu.hk; feitang@cityu.edu.hk
>>> Subject: New Version Notification for draft-ren-icn-content-retrieval-00.txt
>>>
>>>
>>> A new version of I-D, draft-ren-icn-content-retrieval-00.txt
>>> has been successfully submitted by Will Liu and posted to the
>>> IETF repository.
>>>
>>> Filename:	 draft-ren-icn-content-retrieval
>>> Revision:	 00
>>> Title:		 On the Content Retrieval In Information-Centric Network
>>> Creation date:	 2012-10-15
>>> WG ID:		 Individual Submission
>>> Number of pages: 11
>>> URL:
>> http://www.ietf.org/internet-drafts/draft-ren-icn-content-retrieval-00.txt
>>> Status:
>> http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval
>>> Htmlized:
>> http://tools.ietf.org/html/draft-ren-icn-content-retrieval-00
>>>
>>> Abstract:
>>>     Information-Centric Network(ICN), as an emerging network
>>>     architecture, focus on delivering content more efficiently.  This
>>>     brief paper discusses some issues about content retrieval in the
>>>     Information-Centric Network.  It first lists a set of basic
>>>     requirements on the basis of previous literatures.  Then, it tries to
>>>     identify the fundamental functionalities required to satisfy the
>>>     foregoing requirements.  Last, it summarizes the implementation
>>>     status of such functionalities in various Information-Centric Network
>>>     architectures.
>>>
>>>
>>>
>>> The IETF Secretariat
>>>
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>>>
>>
>> --
>> ---------------------------------------
>> Andrea Detti, PhD
>> Dip. Ingegneria Elettronica
>> Universita' di Roma "Tor Vergata"
>> Via del Politecnico 1, 00133 Roma, Italy
>> Tel.: +39-06-7259-7445
>> Fax : +39-06-7259-7435
>> Mobile: +39-320-4391909
>> email: andrea.detti@uniroma2.it
>> ---------------------------------------


-- 
---------------------------------------
Andrea Detti, PhD
Dip. Ingegneria Elettronica
Universita' di Roma "Tor Vergata"
Via del Politecnico 1, 00133 Roma, Italy
Tel.: +39-06-7259-7445
Fax : +39-06-7259-7435
Mobile: +39-320-4391909
email: andrea.detti@uniroma2.it
---------------------------------------


From k.pentikousis@huawei.com  Wed Oct 31 12:06:30 2012
Return-Path: <k.pentikousis@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6DB21F882E for <icnrg@ietfa.amsl.com>; Wed, 31 Oct 2012 12:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zdVA1zWBXVx for <icnrg@ietfa.amsl.com>; Wed, 31 Oct 2012 12:06:29 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D2EB821F881B for <icnrg@irtf.org>; Wed, 31 Oct 2012 12:06:28 -0700 (PDT)
Received: from 172.24.2.119 (EHLO szxeml213-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARP08817; Thu, 01 Nov 2012 03:06:20 +0800 (CST)
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml213-edg.china.huawei.com (172.24.2.30) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 1 Nov 2012 03:05:26 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml405-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Thu, 1 Nov 2012 03:05:25 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: icnrg <icnrg@irtf.org>
Thread-Topic: First draft on ICN baseline scenarios
Thread-Index: Ac23mqvc3Sf1PMcaTJqvI0NQPKRCLw==
Date: Wed, 31 Oct 2012 19:05:24 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4EC74F@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.163]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
Subject: [icnrg] First draft on ICN baseline scenarios
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/icnrg>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 19:06:30 -0000

Dear all,

B=F6rje and I made a first attempt to capture some of the ICN scenarios alr=
eady published in the literature. The document is available from our wiki a=
t=20
http://trac.tools.ietf.org/group/irtf/trac/attachment/wiki/IcnBaselineScena=
rios/draft-pentikousis-icn-scenarios-00.txt

I also cleaned up http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnBaseli=
neScenarios and updated the table of contents to reflect the changes. Of co=
urse, feel free to edit and add to the wiki page. We're looking forward to =
your comments, updates, text contributions, further references, and so on f=
or the draft as well.

Best Regards,

Kostas


