
From dt355@hermes.cam.ac.uk  Thu Nov  1 04:51:25 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 C563E21F8479 for <icnrg@ietfa.amsl.com>; Thu,  1 Nov 2012 04:51:25 -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 37mYoX9lbjNf for <icnrg@ietfa.amsl.com>; Thu,  1 Nov 2012 04:51:23 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 3E69521F846F for <icnrg@irtf.org>; Thu,  1 Nov 2012 04:51:23 -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 5e08abcd.bb.sky.com ([94.8.171.205]:64758 helo=[192.168.1.55]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:dt355) (TLSv1:AES128-SHA:128) id 1TTtIs-0004Jv-Yw (Exim 4.72) (return-path <dt355@hermes.cam.ac.uk>); Thu, 01 Nov 2012 11:51:19 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=iso-8859-1
From: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4EC74F@szxeml545-mbx.china.huawei.com>
Date: Thu, 1 Nov 2012 11:51:18 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C718770E-B1CF-43C9-99D9-BE6E9833040B@cl.cam.ac.uk>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EC74F@szxeml545-mbx.china.huawei.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
X-Mailer: Apple Mail (2.1085)
Sender: Dirk Trossen <dt355@hermes.cam.ac.uk>
Cc: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>
Subject: Re: [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: Thu, 01 Nov 2012 11:51:26 -0000

Hi Konstantinos,

thanks for the document. It is a good start into a difficult area.

You describe it as baseline scenario for a possible (experimental) =
comparison. At this stage, it seems however more like a survey of what =
the different efforts have their work being placed into (which could be =
a start, I admit). An area such as "content dissemination", however, =
then ends up to be so broad that it hardly provides a basis for =
comparison as such. Hence, the document will ultimately need to converge =
more in a description of scenarios that can indeed by replicated in =
setups for experiments etc.=20

As a possible contribution or inspiration (if you will), let me point to =
two pieces that might be useful:
1) at the start of the PSIRP project (the predecessor to the currently =
ongoing PURSUIT project in the EU's FP7) in 2008, we asked project =
members to write down "stories" of the beautiful new ICN world that =
we/they envisioned, the stories largely centred around the idea of =
"information at your fingertips". The outcome can be found at =
http://www.psirp.org/files/Deliverables/PSIRP-TR08-0001_Vision.pdf (skip =
over the vision part and jump straight to the stories)

2) for the content dissemination aspect, we looked into something in =
this area that is more than "making CDNs better" (personally, I have =
doubts that this proposition would fly in any case, given the high =
engineering efforts to make CDNs better, faster, grander, ...). We =
identified the area of highly personalised and interactive media. Here, =
the delivered 'content' is highly similar in underlying media assets but =
still highly personalised (e.g., towards regions, markets, location, =
specific end users,...). Working with content producers (our project =
partner CTVC from London is one such producers), we identified that such =
high degree of personalisation poses a significant burden on production =
and delivery of the content. While standards such as MPEG DASH attempt =
to provide solutions for this at the application level, we see the =
fairly 'low level' realisation in an ICN as a potential differentiator =
in this particular "scenario space", e.g., through the usage of caching, =
the exposure of metadata at a low level of the infrastructure that =
allows for optimising the delivery, ... For more information, we have =
created small videos with an intro into the current work on this - hope =
this might help. You can find the videos at =
http://www.fp7-pursuit.eu/PursuitWeb/?p=3D837

Best,

Dirk
On 31 Oct 2012, at 19:05, Konstantinos Pentikousis wrote:

> Dear all,
>=20
> B=F6rje and I made a first attempt to capture some of the ICN =
scenarios already published in the literature. The document is available =
from our wiki at=20
> =
http://trac.tools.ietf.org/group/irtf/trac/attachment/wiki/IcnBaselineScen=
arios/draft-pentikousis-icn-scenarios-00.txt
>=20
> I also cleaned up =
http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnBaselineScenarios and =
updated the table of contents to reflect the changes. Of course, 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 for =
the draft as well.
>=20
> Best Regards,
>=20
> Kostas
>=20
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From Dirk.Kutscher@neclab.eu  Mon Nov  5 11:47:17 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 BF1AA21F8765 for <icnrg@ietfa.amsl.com>; Mon,  5 Nov 2012 11:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7WdvyfTQDHbk for <icnrg@ietfa.amsl.com>; Mon,  5 Nov 2012 11:47:17 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 056FE21F895A for <icnrg@irtf.org>; Mon,  5 Nov 2012 11:47:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 2C99410242C for <icnrg@irtf.org>; Mon,  5 Nov 2012 20:47:16 +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 43X0voie8l4P for <icnrg@irtf.org>; Mon,  5 Nov 2012 20:47:16 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 125A910242B for <icnrg@irtf.org>; Mon,  5 Nov 2012 20:47:11 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.239]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 5 Nov 2012 20:47:10 +0100
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: Wednesday meeting on Webex
Thread-Index: Ac27jk9JcQYqz2EdS0KevdFCb/J+vg==
Date: Mon, 5 Nov 2012 19:46:38 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F5249551191B7@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] Wednesday meeting on Webex
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, 05 Nov 2012 19:47:17 -0000

Hello,

We are hoping to have a Webex remote participation option and an audio stre=
am for Wednesday's ICNRG meeting.

You have to join both the audio session and the webex session to follow the=
 discussion.

More information:

http://www.ietf.org/meeting/85/remote-participation.html

Best regards,
Dirk



From borje.ohlman@ericsson.com  Mon Nov  5 19:34:51 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 43EB221F85C6 for <icnrg@ietfa.amsl.com>; Mon,  5 Nov 2012 19:34:51 -0800 (PST)
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 HUYpGOKmiRXW for <icnrg@ietfa.amsl.com>; Mon,  5 Nov 2012 19:34:50 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 79F2421F85BA for <icnrg@irtf.org>; Mon,  5 Nov 2012 19:34:50 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-03-509885590720
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id BC.CD.06323.95588905; Tue,  6 Nov 2012 04:34:49 +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; Tue, 6 Nov 2012 04:34:49 +0100
Received: from [IPv6:::1] (abro.ki.sw.ericsson.se [147.214.177.159])	by abro.ki.sw.ericsson.se (Postfix) with ESMTP id CD8A816AC678	for <icnrg@irtf.org>; Tue,  6 Nov 2012 04:34:48 +0100 (CET)
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: Tue, 6 Nov 2012 04:34:49 +0100
Message-ID: <7D205040-F6C5-4A1F-89CC-DCD2F9FD3D8A@ericsson.com>
To: icnrg <icnrg@irtf.org>
MIME-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMJMWRmVeSWpSXmKPExsUyM+JvjW5k64wAg7NdshY7Z+9kcmD0mLzx MFsAYxSXTUpqTmZZapG+XQJXxpr9q5gK7jJW/Lv6m7GBcT1jFyMnh4SAicTKSSuZIWwxiQv3 1rN1MXJxCAmcZJTYt3QPI4SzkVFi74qTLBDOYUaJefcugrWwCThKPG5ZzwpiMwvoSdyYOoUN wtaWWLbwNViNsICaxMXWS0BxDg4WARWJhdfKQcK8AvYSbX+ugrWKCEhJbNp7lw0ibiixsOkV G8RFshIbtz9gB7GFgMbM+PiIaQIj/ywk22Yh2TYLSfsCRuZVjOy5iZk56eXmmxiBAXVwy2+D HYyb7osdYpTmYFES59VT3e8vJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgZF16jONdJ+VsUvt BPZsfHXBR05p54R9nHc/q1q9qC9atSFl6yo25l2bNk/hinbt2M3Ikixe99fq9VeRpxdc9j/f JzJFnns9+yUx0SKb1WLXrq7a5+tw8PycZz/CRAJ0sznPnhKc86rRycDibmaCorfAtimHH8is vpx640728f8RwSanOddJz3mjxFKckWioxVxUnAgAnuUYMfYBAAA=
Subject: [icnrg] Slides for the ICNRG meeting
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, 06 Nov 2012 03:34:51 -0000

For those doing presentations at the ICNRG meeting: Please send me your =
slides, preferably by lunch on Tuesday, but no later than Wednesday 6.00 =
AM.
I need to post them on the meetings material site.

	B=F6rje=

From daveoran@orandom.net  Tue Nov  6 04:28:12 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 DC4DD21F849B for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 04:28:12 -0800 (PST)
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 QhjjI6s7cqin for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 04:28:12 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2001:470:d:21b:3c00::1]) by ietfa.amsl.com (Postfix) with ESMTP id 958AD21F849A for <icnrg@irtf.org>; Tue,  6 Nov 2012 04:28:12 -0800 (PST)
Received: from [130.129.68.157] (dhcp-449d.meeting.ietf.org [130.129.68.157]) (authenticated bits=0) by spark.crystalorb.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id qA6CSKfr028630 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <icnrg@irtf.org>; Tue, 6 Nov 2012 04:28:21 -0800
From: David R Oran <daveoran@orandom.net>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (10A523)
Message-Id: <3E43744C-466E-4BD3-9DCD-20DD1EAD59E5@orandom.net>
Date: Tue, 6 Nov 2012 07:28:09 -0500
To: icnrg@irtf.org
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: [icnrg] Need a jabber room minder for ICNRG meeting tomorrow
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, 06 Nov 2012 12:28:13 -0000

Can I have a volunteer from among those of you planning to be at the session?

Thanks in advance,
Dave Oran - co-chair ICNRG 

From k.pentikousis@huawei.com  Tue Nov  6 11:57:27 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 0765321F89A3 for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 11:57:26 -0800 (PST)
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 RISZ8BTD7JtG for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 11:57:24 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4901B21F841A for <icnrg@irtf.org>; Tue,  6 Nov 2012 11:57:23 -0800 (PST)
Received: from 172.24.2.119 (EHLO szxeml210-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ARX10719; Wed, 07 Nov 2012 03:57:15 +0800 (CST)
Received: from SZXEML423-HUB.china.huawei.com (10.82.67.162) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 7 Nov 2012 03:57:11 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml423-hub.china.huawei.com ([10.82.67.162]) with mapi id 14.01.0323.003; Wed, 7 Nov 2012 03:57:11 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
Thread-Topic: [icnrg] First draft on ICN baseline scenarios
Thread-Index: Ac23mqvc3Sf1PMcaTJqvI0NQPKRCLwASXoIAARvTA9A=
Date: Tue, 6 Nov 2012 19:57:11 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4ED622@szxeml545-mbx.china.huawei.com>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EC74F@szxeml545-mbx.china.huawei.com> <C718770E-B1CF-43C9-99D9-BE6E9833040B@cl.cam.ac.uk>
In-Reply-To: <C718770E-B1CF-43C9-99D9-BE6E9833040B@cl.cam.ac.uk>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.150.166]
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>, icnrg <icnrg@irtf.org>
Subject: Re: [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: Tue, 06 Nov 2012 19:57:27 -0000

Hi Dirk, all,

  |thanks for the document. It is a good start into a difficult area.

Many thanks for your kind words and quick reply. Apologies for my late repl=
y, it has been a busy week.
=20
  |You describe it as baseline scenario for a possible (experimental)
  |comparison. At this stage, it seems however more like a survey of what
  |the different efforts have their work being placed into (which could
  |be a start, I admit).

Indeed, the starting point for this document is what people have already at=
tempted to demonstrate. From this point onwards, I would expect that folks =
in the RG would start voicing their interest in shaping these scenarios fur=
ther as well as actively contributing new ones.

  |An area such as "content dissemination",
  |however, then ends up to be so broad that it hardly provides a basis
  |for comparison as such. Hence, the document will ultimately need to
  |converge more in a description of scenarios that can indeed by
  |replicated in setups for experiments etc.

Couldn't agree more with you. I would however avoid overemphasizing this ca=
tegory, which is indeed too broad. Perhaps we should consider subcategories=
.

  |As a possible contribution or inspiration (if you will), let me point
  |to two pieces that might be useful:
  |1) at the start of the PSIRP project (the predecessor to the currently
  |ongoing PURSUIT project in the EU's FP7) in 2008, we asked project
  |members to write down "stories" of the beautiful new ICN world that
  |we/they envisioned, the stories largely centred around the idea of
  |"information at your fingertips". The outcome can be found at
  |http://www.psirp.org/files/Deliverables/PSIRP-TR08-0001_Vision.pdf
  |(skip over the vision part and jump straight to the stories)

Thanks for sharing! I think the scenarios in subsection 4.1-2 could enhance=
 the social networking section, for example, although they're kind of cover=
ed already. Others, though, could form the foundation for new scenarios, es=
p. if there are related simulations/demos already available. Looking forwar=
d to some text for the draft :)

  |2) for the content dissemination aspect, we looked into something in
  |this area that is more than "making CDNs better" (personally, I have
  |doubts that this proposition would fly in any case, given the high
  |engineering efforts to make CDNs better, faster, grander, ...).

I think that the main point with ICN is that you can potentially offer all =
services without such a large infra and target different optimalities than =
those we go after today. CDNs are primarily serving large players. But I wo=
uld really prefer to avoid having to continuously compare ICN with CDNs and=
 what they can do today, or what they will be able to do tomorrow. I'm sure=
 that a couple of decades ago many argued that circuit-switched was the onl=
y way to do voice. I hope we do not need to argue that CDN is the only way =
to do content dissemination in the future.=20

<snip>
  |that such high degree of personalisation poses a significant burden on
  |production and delivery of the content. While standards such as MPEG
  |DASH attempt to provide solutions for this at the application level,
  |we see the fairly 'low level' realisation in an ICN as a potential
  |differentiator in this particular "scenario space", e.g., through the

I would be very interested to hear more about this, perhaps a paper/present=
ation?


Best Regards,

Kostas


From dt355@hermes.cam.ac.uk  Tue Nov  6 12:44:30 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 60CF321F8C0E for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 12:44:30 -0800 (PST)
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 6Rly9ehaFjVo for <icnrg@ietfa.amsl.com>; Tue,  6 Nov 2012 12:44:29 -0800 (PST)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 8A11121F8B9A for <icnrg@irtf.org>; Tue,  6 Nov 2012 12:44:29 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from 5e016fd0.bb.sky.com ([94.1.111.208]:55789 helo=[192.168.1.57]) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:dt355) (TLSv1:AES128-SHA:128) id 1TVq0Z-0001qq-XX (Exim 4.72) (return-path <dt355@hermes.cam.ac.uk>); Tue, 06 Nov 2012 20:44:27 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4ED622@szxeml545-mbx.china.huawei.com>
Date: Tue, 6 Nov 2012 20:44:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <43C76614-9BCA-4DD2-8E77-AF5480316254@cl.cam.ac.uk>
References: <8D38716F0C1A444BA0CD7E96454366C23A4EC74F@szxeml545-mbx.china.huawei.com> <C718770E-B1CF-43C9-99D9-BE6E9833040B@cl.cam.ac.uk> <8D38716F0C1A444BA0CD7E96454366C23A4ED622@szxeml545-mbx.china.huawei.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
X-Mailer: Apple Mail (2.1085)
Sender: Dirk Trossen <dt355@hermes.cam.ac.uk>
Cc: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>, icnrg <icnrg@irtf.org>
Subject: Re: [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: Tue, 06 Nov 2012 20:44:30 -0000

Hi Konstantinos,

>=20
>  |2) for the content dissemination aspect, we looked into something in
>  |this area that is more than "making CDNs better" (personally, I have
>  |doubts that this proposition would fly in any case, given the high
>  |engineering efforts to make CDNs better, faster, grander, ...).
>=20
> I think that the main point with ICN is that you can potentially offer =
all services without such a large infra and target different =
optimalities than those we go after today. CDNs are primarily serving =
large players. But I would really prefer to avoid having to continuously =
compare ICN with CDNs and what they can do today, or what they will be =
able to do tomorrow. I'm sure that a couple of decades ago many argued =
that circuit-switched was the only way to do voice. I hope we do not =
need to argue that CDN is the only way to do content dissemination in =
the future.=20

Agree which is why I suggested the story-based delivery. The high degree =
of personalisation is something that could be an interesting spin to the =
content dissemination angle, posing interesting problems to the aspect =
of 'reachability' for publishers of such individual media assets.

>=20
> <snip>
>  |that such high degree of personalisation poses a significant burden =
on
>  |production and delivery of the content. While standards such as MPEG
>  |DASH attempt to provide solutions for this at the application level,
>  |we see the fairly 'low level' realisation in an ICN as a potential
>  |differentiator in this particular "scenario space", e.g., through =
the
>=20
> I would be very interested to hear more about this, perhaps a =
paper/presentation?
>=20

Nothing published as of yet but working on a submission as we speak. The =
videos I posted as links give an insight into the current work, though. =
Sorry that it is so little for now.

Best,

Dirk

>=20
> Best Regards,
>=20
> Kostas
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg


From daveoran@orandom.net  Wed Nov  7 06:36:46 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 8566A21F89D0 for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 06:36:46 -0800 (PST)
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 Md-9ugotr1fm for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 06:36:46 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2001:470:d:21b:3c00::1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C1D21F8B2B for <icnrg@irtf.org>; Wed,  7 Nov 2012 06:36:46 -0800 (PST)
Received: from [130.129.17.107] (dhcp-116b.meeting.ietf.org [130.129.17.107]) (authenticated bits=0) by spark.crystalorb.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id qA7Eat7m012731 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <icnrg@irtf.org>; Wed, 7 Nov 2012 06:36:56 -0800
From: David R Oran <daveoran@orandom.net>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (10A523)
Message-Id: <52C6785E-AE0C-442A-93C0-1E51BB14E80E@orandom.net>
Date: Wed, 7 Nov 2012 09:36:45 -0500
To: "icnrg@irtf.org" <icnrg@irtf.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: [icnrg] Asking again: Need a jabber room minder for ICNRG meeting tomorrow
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, 07 Nov 2012 14:36:46 -0000

Can I have a volunteer from among those of you planning to be at the session?

Thanks in advance,
Dave Oran - co-chair ICNRG 

From lars@netapp.com  Wed Nov  7 11:11:17 2012
Return-Path: <lars@netapp.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 ACF4921F8957 for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 11:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.207
X-Spam-Level: 
X-Spam-Status: No, score=-10.207 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, 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 nYEpzn-bFlme for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 11:11:17 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0C66621F8878 for <icnrg@irtf.org>; Wed,  7 Nov 2012 11:11:17 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.80,731,1344236400";  d="p7s'?scan'208";a="707926723"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 07 Nov 2012 11:11:16 -0800
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id qA7JBE5r029833 for <icnrg@irtf.org>; Wed, 7 Nov 2012 11:11:16 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0318.001; Wed, 7 Nov 2012 11:11:14 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "<icnrg@irtf.org>" <icnrg@irtf.org>
Thread-Topic: the TCP evaluation scenarios paper I just mentioned
Thread-Index: AQHNvRun0stnfAH4lUStI/24DBzV8g==
Date: Wed, 7 Nov 2012 19:10:16 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9185E1D2B@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.114]
Content-Type: multipart/signed; boundary="Apple-Mail=_BECE45A2-293F-47B6-B2A0-70D52F62E53B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Subject: [icnrg] the TCP evaluation scenarios paper I just mentioned
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, 07 Nov 2012 19:11:17 -0000

--Apple-Mail=_BECE45A2-293F-47B6-B2A0-70D52F62E53B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Towards a Common TCP Evaluation Suite. Lachlan Andrew, Cesar Marcondes, =
Sally Floyd, Lawrence Dunn, Wang Gang, Lars Eggert, Sangtae Ha and =
Injong Rhee. Proc. International Workshop on Protocols for Fast =
Long-Distance Networks (PFLDnet), Manchester, UK, March 5-7, 2008. =
http://eggert.org/papers/2008-pfldnet.pdf

Lars=

--Apple-Mail=_BECE45A2-293F-47B6-B2A0-70D52F62E53B
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTEwNzE5MTExMVowIwYJKoZIhvcNAQkEMRYEFNC8
d9DC0vPF7qpyb+ZWLQTJUqqUMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBADpgGYnk
dUAUsmdJlkXI7J91t3n5WkO0ZFVw+8dwF1XMq85DDyrAD2Dm1utSBpXm61F1/pNNToWbV1C38eJj
b221C7+ancDP6UXQQPuRre5Hx90CpyMAE63t2IgGWK8K5TiI4RAdxyZGcF1yXJabr95JNLezgx6F
qwp68cXdXJqnSIk/Rz7SP+x2i9uF2f2FMvjaBgD+Ggqv9fv6R6J1ZCkEVlwubxOhFhLynB8Zk2YZ
YkCIR0fF1BGNZM2BQ9QRpJNepjJhO+CXBp3AWKy/lJAXzlp4LmFeuR9B6lS2DTFWx3pHy554K24g
g+tIE6Q/7j55de6BvT5nWKoow69I6DwAAAAAAAA=

--Apple-Mail=_BECE45A2-293F-47B6-B2A0-70D52F62E53B--

From kfall@qti.qualcomm.com  Wed Nov  7 11:44:38 2012
Return-Path: <kfall@qti.qualcomm.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 D6FB721F8C77 for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 11:44:38 -0800 (PST)
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 DgCsgnUL5fko for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 11:44:34 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id BFBFF21F8BAD for <icnrg@irtf.org>; Wed,  7 Nov 2012 11:44:27 -0800 (PST)
X-IronPort-AV: E=McAfee;i="5400,1158,6888"; a="4916587"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 07 Nov 2012 11:21:01 -0800
X-IronPort-AV: E=Sophos;i="4.80,731,1344236400"; d="scan'208,217";a="1369467"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Nov 2012 11:44:26 -0800
Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by nasanexhc08.na.qualcomm.com ([172.30.39.7]) with mapi id 14.02.0318.001; Wed, 7 Nov 2012 11:44:25 -0800
From: "Fall, Kevin" <kfall@qti.qualcomm.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: slides I presented (comparing ICN and DTN)
Thread-Index: AQHNvSBK10AMXK4mh0yhncqx+G9InA==
Date: Wed, 7 Nov 2012 19:44:24 +0000
Message-ID: <BB72E60F7A18154A9B1352D1DF6FEE571E26AC1E@NASANEXD01E.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [199.106.115.132]
Content-Type: multipart/alternative; boundary="_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC1ENASANEXD01Enaqu_"
MIME-Version: 1.0
Subject: [icnrg] slides I presented (comparing ICN and DTN)
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, 07 Nov 2012 19:44:39 -0000

--_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC1ENASANEXD01Enaqu_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


This seems to come up from time to time, so for those of you interested her=
e is a link to some slides I gave recently on comparing DTN and ICN:

http://kfall.net/ucbpage/talks/lcn-icn-dtn-keynote.pdf

regards,
- K

--_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC1ENASANEXD01Enaqu_
Content-Type: text/html; charset="us-ascii"
Content-ID: <215462BED7ACFB42AE43C95C467DEC5C@qualcomm.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div><br>
</div>
<div>This seems to come up from time to time, so for those of you intereste=
d here is a link to some slides I gave recently on comparing DTN and ICN:</=
div>
<div><br>
</div>
<div>http://kfall.net/ucbpage/talks/lcn-icn-dtn-keynote.pdf</div>
<div><br>
</div>
<div>regards,</div>
<div>- K</div>
</body>
</html>

--_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC1ENASANEXD01Enaqu_--

From dt355@hermes.cam.ac.uk  Wed Nov  7 12:36:21 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 BF1D221F8C50 for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 12:36:21 -0800 (PST)
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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 AqpeRuQKBoGK for <icnrg@ietfa.amsl.com>; Wed,  7 Nov 2012 12:36:21 -0800 (PST)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 0C27621F8C49 for <icnrg@irtf.org>; Wed,  7 Nov 2012 12:36:20 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from 5e016fd0.bb.sky.com ([94.1.111.208]:58966 helo=[192.168.1.57]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:dt355) (TLSv1:AES128-SHA:128) id 1TWCMF-0004CS-ql (Exim 4.72) for icnrg@irtf.org (return-path <dt355@hermes.cam.ac.uk>); Wed, 07 Nov 2012 20:36:19 +0000
From: Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-344-351224171
Date: Wed, 7 Nov 2012 20:36:18 +0000
Message-Id: <BDA2A932-8EA4-4A3B-8ACD-7BEDC399B664@cl.cam.ac.uk>
To: icnrg <icnrg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Sender: Dirk Trossen <dt355@hermes.cam.ac.uk>
Subject: [icnrg] New ICN prototype release v0.3 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: Wed, 07 Nov 2012 20:36:21 -0000

--Apple-Mail-344-351224171
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

All,

the development team of the PURSUIT project has just released the new =
v0.3 of the Blackadder prototype. This new release includes integration =
with ns-3 (thanks to the Click router platform basis), security features =
(including an access control implementation), improvements in the test =
bed deployment tools, and many other updates.=20

The new release is available at =
https://github.com/fp7-pursuit/blackadder - do check it out!

Best,

Dirk=

--Apple-Mail-344-351224171
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">All,<div><br></div><div>the development team of the PURSUIT project has just released the new v0.3 of the Blackadder prototype. This new release includes integration with ns-3 (thanks to the Click router platform basis), security features (including an access control implementation), improvements in the test bed deployment tools, and many other updates.&nbsp;</div><div><br></div><div>The new release is available at&nbsp;<a href="https://github.com/fp7-pursuit/blackadder">https://github.com/fp7-pursuit/blackadder</a>&nbsp;- do check it out!</div><div><br></div><div>Best,</div><div><br></div><div>Dirk</div></body></html>
--Apple-Mail-344-351224171--

From borje.ohlman@ericsson.com  Fri Nov  9 10:27:31 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 C3C5821F8758 for <icnrg@ietfa.amsl.com>; Fri,  9 Nov 2012 10:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.393
X-Spam-Level: 
X-Spam-Status: No, score=-5.393 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MPART_ALT_DIFF_COUNT=1.11, 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 jdWZI8qy40RX for <icnrg@ietfa.amsl.com>; Fri,  9 Nov 2012 10:27:30 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 872ED21F858F for <icnrg@irtf.org>; Fri,  9 Nov 2012 10:27:29 -0800 (PST)
X-AuditID: c1b4fb25-b7f926d00000661f-c2-509d4b1033ac
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 51.B1.26143.01B4D905; Fri,  9 Nov 2012 19:27:28 +0100 (CET)
Received: from abro.ki.sw.ericsson.se (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Fri, 9 Nov 2012 19:27:27 +0100
Received: from [IPv6:::1] (abro.ki.sw.ericsson.se [147.214.177.159])	by abro.ki.sw.ericsson.se (Postfix) with ESMTP id 2233C16AC669	for <icnrg@irtf.org>; Fri,  9 Nov 2012 19:27:26 +0100 (CET)
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D7F5B164-4115-407D-9A3F-BAB1707CDA27"
Date: Fri, 9 Nov 2012 19:27:25 +0100
Message-ID: <68070FD5-8DA1-416F-A2C9-6EC667E06835@ericsson.com>
To: icnrg <icnrg@irtf.org>
MIME-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyM+Jvja6A99wAg833pCx2zt7J5MDoMXnj YbYAxigum5TUnMyy1CJ9uwSujH0NWQV3exgrmveINDBOLuxi5OSQEDCRePOhnQnCFpO4cG89 WxcjF4eQwElGiSfNhxghnI2MEpemz2OBcA4zSnT2v2cFaWETcJR43LIezGYWSJJo/fWQDcQW FlCVeHnlAZjNIqAiMenvB2YQm1fAXuLqn5ksILaIgJTEpr132SDihhILm16xQZwhK7Fx+wN2 EFtIQE1ixsdHTBMY+WYhWTELSQtEXFti2cLXzBC2nsSNqVOg4jESR6f+YcVUoysx498hllmM HEC2l8ST2bkQYXuJ07vfMmMql5fY/nYOXPzMgcdMCxh5VjGy5yZm5qSXG21iBMbDwS2/VXcw 3jkncohRmoNFSZzXeusefyGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2Ms/Uf7njm88Rw6XXD 6L4PN2smWb/KPPRs0pu3XWIuWtuStpzizDqp3rfuzgLtja8TnrZufjsv1/fFklmaxacl9789 LGWh/bNYtL3cfUE8I9/+QBe7nj1HZSof7TodUXuAue9xn2+7ox73zqarsXNPPP1S0SekuNq+ OOy2eurKHRfcVjp9tZ5QocRSnJFoqMVcVJwIAC3jKW5VAgAA
Subject: [icnrg] Draft ICNRG minutes uploaded
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, 09 Nov 2012 18:27:31 -0000

--Apple-Mail=_D7F5B164-4115-407D-9A3F-BAB1707CDA27
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

The draft ICNRG minutes are now available at:
http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg

Please check, add and comment.

	B=F6rje.

-------------------------


--Apple-Mail=_D7F5B164-4115-407D-9A3F-BAB1707CDA27
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_B2A28D3C-8252-4353-AADA-8DA01A81CAEF"

--Apple-Mail=_B2A28D3C-8252-4353-AADA-8DA01A81CAEF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<html><head><base href=3D"data:"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><base href=3D"data:"><div style=3D"font-family: =
Helvetica; font-size: 12px; color: black; text-align: left; ">The draft =
ICNRG minutes are now available at:</div><a =
href=3D"http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg">http:=
//www.ietf.org/proceedings/85/minutes/minutes-85-icnrg</a><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><br class=3D"webkit-block-placeholder"></div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; ">Please check, add and comment.</div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><br></div><div style=3D"font-family: Helvetica; =
font-size: 12px; color: black; text-align: left; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>B=F6rje.</div><div style=3D"font-family: Helvetica; font-size: =
12px; color: black; text-align: left; "><br></div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; ">-------------------------</div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><span class=3D"Apple-style-span" style=3D"font-size: =
medium; "><br></span></div><div style=3D"font-family: Helvetica; =
font-size: 12px; color: black; text-align: left; "><span =
class=3D"Apple-style-span" style=3D"font-size: medium; =
"></span></div></body></html>=

--Apple-Mail=_B2A28D3C-8252-4353-AADA-8DA01A81CAEF
Content-Disposition: attachment; filename="draft-ietf85-icnrg-minutes.txt"
Content-Type: text/plain; name="draft-ietf85-icnrg-minutes.txt"
Content-Transfer-Encoding: quoted-printable

Ed note: '--' refers to the slide heading presented=0D
=0D
=0D
ICNRG@IETF85 Agenda=0D
=0D
Wednesday, November 7th 2012=0D
13:00 -- 14:30, 14:40 -- 15.40 Salon D=0D
Intro -- 5 min=0D
=0D
Note well=0D
Blue sheets=0D
*** Agenda bashing=0D
=0D
no comments=0D
=0D
*** ICNRG Work Item Status=0D
*** ICNRG Work Items -- 25 min/each=0D
=0D
-- objectives for this meeting=0D
-- interim meeting tentatively planned on 14/15 Feb 2013=0D
=0D
*** ICN Research Challenges=0D
    Fairness discussion - see wiki  (Damien Saucez)=0D
    http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnProblemStatement=0D=

    Discussion on document content and outline (All)=0D
=0D
-- Damien Saucez presents=0D
=0D
Fairness between what:=0D
-- flows=0D
-- content=0D
-- customer=0D
-- link/interface fairness=0D
-- network fairness=0D
=0D
Enforcement: end-to-end vs. hop-by-hop=0D
	     =0D
Kostas: What is end-to-end?=0D
	Is the discussion of ends "suitable"?=0D
	After all, we have a different paradigm here.=0D
	Not properly reflected in the figures made.=0D
=0D
Damien: there is also no notion of flow defined.=0D
=0D
Kostas: doesn't understand why we need to define flow.=0D
	We need a completely new understanding of fairness.=0D
=0D
Damien does want to put forward questions, not solutions.=0D
The way the slides are ordered =0D
=0D
-- Summary: =0D
   -- what is a flow?=0D
   -- what is a resource?=0D
   -- what fairness do we want to reach and how to measure it=0D
=0D
Mirja:	=0D
=0D
Karen Sollins: why is flow on this slide?=0D
      	       Flow implies a certain way of thinking about things.=0D
	       Avoid the term flow altogether.=0D
=0D
Kostas: refers to fairness in peer-to-peer networks.=0D
Boerje: a number of new types of resources comes into the picture=0D
	This presentation is about going beyond flows when discussing =
fairness.=0D
	When comparing to IP networks, we need to relate to flows.=0D
=0D
...: You need to compare this traffic to other types of traffic.=0D
     What this fairness is for is a reasonable question to ask.=0D
=0D
Lars: What is the impact of your traffic on other traffic?=0D
      Is ICN aware of the capacity sharing and Re-ECN work.=0D
=0D
Dave: Key: capability of trading off caching for bandwidth.=0D
      You may have to look at groups of users accessing content.=0D
      Some drag down content from an upstream link, others use=0D
      the stuff from the cache.  These=0D
=0D
Matt: This is about mapping content networking to a different paradigm.=0D=

      Think OS schedulers, earlier completion time, etc.  Yields a =0D
      completely different sense of fairness.=0D
=0D
Lars: Contention your access to an information object causes to others=0D=

      who want to use the same network for other stuff.  Fairness is =0D
      about how you balance this out.=0D
=0D
...: ?=0D
=0D
Dirk: comment on Damien's presentation: different ICN approaches have=0D
      different concepts for transport (and flows). We should document=0D=

      this in the survey draft. It is difficult to discuss this on a=0D
      general level.=0D
=0D
<Dirk's slides to come here -- deferred for logistics reasons>=0D
=0D
*** ICN Challenges=0D
=0D
-- document purpose=0D
   -- why?=0D
   -- how?=0D
   -- what?=0D
   -- possible results?=0D
=0D
-- input so far=0D
-- note=0D
-- proposed structure for the document=0D
   1. intro=0D
   2. problems=0D
   3. concepts=0D
   4. research challenges=0D
   5. impact on IETF work=0D
=0D
Kostas: monitoring, measurement, and instrumentation=0D
	did not have traceroute and ping from the beginning=0D
=0D
-- current status=0D
=0D
*** ICN Survey document -=0D
    Presentation of On the Content Retrieval In Information-Centric =
Network, (Will Liu)=0D
    http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval=0D
    Discussion on document content and outline (All)=0D
=0D
This is an excerpt of a summary report on ICN.=0D
=0D
-- motivation=0D
-- terminology=0D
=0D
Kevin: provider vs. author is a relevant distinction here.=0D
=0D
-- requirements and functionality=0D
=0D
-- summary (1/3)=0D
-- summary (2/3)=0D
-- summary (3/3)=0D
=0D
Kevin: some issues to consider=0D
       -- scalability in different dimensions=0D
       -- brittleness (e.g., concerning naming schemes)=0D
       -- type of persistence wrt the cache=0D
=0D
Kostas: what's persistent?=0D
	I may have content on a box, but I may not be able to get it off=0D=

=0D
Kevin: one type of persistence: if I turn of the power, will the content =
survive?=0D
       what would happen if I shut down an entire network=0D
=0D
Dave (from the floor): two dimensions at least to this problem=0D
      -- vulnerability=0D
      -- longevity=0D
=0D
Dave (chair): this may be input to some of the work items=0D
     	      how shall we take this work forward?=0D
	      is this input?  a starting point?=0D
=0D
Kostas: should this cover work in the IETF that happens?=0D
=0D
Lixia: what is the scope of the survey?=0D
       Beyond IETF and IRTF?=0D
       The presentation we just heard was about file retrieval in a =
fairly narrow=0D
       view.  Information retrieval in ICN is going to be much broader.=0D=

       What's the chairs' assessment?=0D
=0D
Dave: wants feedback from the group.=0D
=0D
Lixia: wants it broader=0D
=0D
Dave: should accommodate current research efforts=0D
      But: we are not writing a 300 page monograph.=0D
      Striking the balance is important.=0D
=0D
Lixia: broader scope; the size of the document may be function of the =
level of=0D
       detail written down.=0D
=0D
Dave: good observation.=0D
=0D
Eve: solicit input on diverse work items=0D
     the RG wants to get a baseline but also be able to compare (for a =
particular use case)=0D
     Maybe a closer look at the scenario and use cases will help.=0D
=0D
Dave: does the union of the document address Eve's concers?=0D
=0D
Karen: is concerned that there is a big elephant in the room what we =
mean by ICN.=0D
       Agrees with Lixia on the scope to be broad.  But some projects =
are less=0D
       information-centric in the strict sense.=0D
       This discussion may open up a huge can of worms.=0D
=0D
Eve: use case driven approach helps us in scoping=0D
=0D
Karen: use cases must cover a broad enough set=0D
=0D
Kostas: we should err on the side of inclusiveness.  Must be =
contribution driven.=0D
	People can best write about what they do (less about others' =
stuff).=0D
=0D
Lixia: yes, an RG is contribution driven.  But if we do a survey, it =
must be=0D
       a real survey.=0D
=0D
       Karen commented: are we doign architecture?  Lixia seconds this.=0D=

=0D
Kostas: Architecture as a 110th proposal.=0D
=0D
Lixia: what's the goal for the research group?=0D
=0D
Boerje: we are free to define our goals as we go along.  Lars confirms =
by nodding.=0D
=0D
Lars: agrees with Boerje.  A venue where people can bring there =
topic-related=0D
      research and discuss it.  Maybe somebody wants to take ideas and =
write up=0D
      an architecture.=0D
=0D
      RGs don't operate by consensus.  We may write up and discuss =
multiple ideas=0D
      at the same time and may even have multiple competing =
publications. There is=0D
      plenty of past evidence on this.=0D
=0D
      Emphasizes that the RG is contribution-driven.  RGs are probably =
worse than=0D
      WGs from this perspective.=0D
=0D
Dave: # people (mostly in academia), we are getting a fairly large =
community.=0D
      No point in having another place to do the same community stuff as =
elsewhere.=0D
      What the special place that ICN RG (that is not redundant) can =
offer.=0D
=0D
      One example: what's the measurement and comparison metrics?=0D
      Maybe a meta architecture.  How to compare different =
architectures?=0D
      How to cut through eternal arguments between groups with different =
approaches.=0D
=0D
      A survey document may provide some ground truth here.=0D
=0D
Karen: agrees: differences, strengths and weaknesses=0D
       missing: there is no group that starts to think about what do we =
mean by =0D
       this space.  We don't have a common enough understanding of what =
ICN means.=0D
       survey is a good starting point.=0D
       Probably a living document since things evolve all the time.=0D
       If you do a survey, you need to do the work.=0D
=0D
Lixia: agrees with Dave; architecture is missing; what is the unique =
value of=0D
       this group?=0D
=0D
       Agrees with Karen: define what ICN is=0D
=0D
Kevin: Doing an arch framework document first was a very useful starting =
point.=0D
       Survey isn't the same and it may not be easy to extract from =
other approaches.=0D
=0D
Lars: on the metrics: provides example for TCP; if you want to propose a =
TCP=0D
      extension, you need to run these simulations and present your =
results for=0D
      certain cases.=0D
=0D
      Maybe something similar can make sense here.  Scenario, numbers =
and=0D
      parameters.  One way to compare different architectures=0D
=0D
Dave: good point, but TCP comparison isn't perfect: TCP was around for =
15 years=0D
      when this was done.  We are at the starting point.  So, this won't =
be easy.=0D
=0D
Boerje: was it a good thing to not have done this earlier for TCP?=0D
Dave: does not know the answer.=0D
=0D
Boerje: agrees with measurements and scenarios.=0D
=0D
	An advantage over conferences is that we can talk about things =
that are=0D
	not new.=0D
=0D
...: ICN vs. CDN.=0D
=0D
Dave: Hard question: if there seems to be some emerging sense on working=0D=

      on comparison.  Who here is willing to do some work on this?=0D
      For use cases, scenarios, applications on the way towards =
evaluation frameworks:=0D
      =0D
      Bunch of hands up.=0D
=0D
Boerje: People shall sign up on the Wiki for topics and spec what they =
wanna do.=0D
	Will organize the work around subgroups.=0D
=0D
...: Defining terminology is really important, also to be even able to =
talk about=0D
     architecture framework and specific designs.=0D
=0D
Boerje agrees.  Contributions on this topic welcome.=0D
=0D
*** ICN Baseline Scenarios =0D
    Presentation of draft-pentikousis-icn-scenarios-00.txt (Kostas =
Pentikousis)=0D
    =
http://trac.tools.ietf.org/group/irtf/trac/attachment/wiki/IcnBaselineScen=
arios/draft-pentikousis-icn-scenarios-00.txt=0D
    Discussion on document content and outline (All)=0D
    Specific Proposals -- 20 min=0D
=0D
< Kostas escaped from the room just when his presentation came up :-) >=0D=

=0D
-- draft goals=0D
-- draft overview=0D
-- social networking=0D
=0D
Joen (Delft U): have a ppsp reference implementation based upon a single =
hash request=0D
=0D
-- example=0D
-- real-time=0D
-- mobility (multi-access)=0D
-- infrastructure sharing=0D
-- content distribution=0D
-- example (CURLING project)=0D
-- ee and dtn=0D
=0D
Eve: work not just in ndn also at intel labs on home management systems=0D=

     (e.g., about energy usage); considering privacy.=0D
=0D
Kostas: energy efficient ICT vs. ICT for energy efficient=0D
	this could be another scenario =0D
=0D
Eve promises a scenario.=0D
=0D
-- scenario topology=0D
-- for the record=0D
=0D
... (Huawai): more discussion on what is unique on ICN (compared to IP)=0D=

=0D
Dirk: nice collection of scenarios (thanks) -- we should be clear=0D
      about the objective. Draft abstract says it's about comparing=0D
      approaches -- current text and presentation looks more like ICN=0D
      use cases.=0D
=0D
Kostas: wants to collect feedback first=0D
=0D
Volunteers: please go to the Wiki and add your name=0D
=0D
*** Coordinated Forwarding and Caching in Information-Centric Networks =
(Xie) -- 15 min=0D
    =
http://sites.google.com/site/haiyongxie/draft-xie-icn-coordinated-caching-=
forwarding.txt =0D
    Deployment Aspects -- 30 min=0D
=0D
-- contributors=0D
-- caching=0D
-- a motivating example=0D
-- a motivating example (continued)=0D
-- coordinating caching & forwarding=0D
-- leverage content popularity info=0D
-- handle consistency=0D
-- handle consistency (continued)=0D
-- summary=0D
=0D
Damien: did you look at the problem of scalability and churn?=0D
=0D
good point.  Number of announcements by routers is kept small.=0D
=0D
Dave: Did you look at caches at certain sizes?  content popularity?=0D
      How do you know where the threshold should fall?=0D
=0D
=0D
Discussing how to deal with ICN deployment issues=0D
Discussion=0D
=0D
Presenters are not available today.  No need to spend a lot of time on =
this=0D
today.  Basically, people should think about including deployment =
aspects in=0D
one of the three documents we are currently working on.=0D
=0D
Might also become a separate work item to be worked upon later.  But =
this=0D
should not prevent us from discussing it.  Input is welcome!=0D
=0D
Boerje:=0D
   - postpone to another meeting=0D
   - separate work item, maybe later=0D
   - input and discussion welcome=0D
=0D
Spirous slide on ICN vs. CDNI points (not presented)=0D
=0D
Migration Incentives=0D
=0D
Kostas: there is an article in upcoming IEEE commag=0D
=0D
Proposed reading list:=0D
ICN vs. CDN  =
http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt =0D
Information-Centric Network in an ISP,  =
http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01 =0D
=
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf=0D
http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf=0D
=0D
Other Business -- 20 min=0D
=0D
----------------------------------------------------------------------=0D=

=0D
ICNRG interim meeting=0D
=0D
Boerje:=0D
   - want to have longer meetings than just 2 hours at IETF=0D
   - proposing meeting in February (14-15) in Stockholm, i.e. slide 1 =
day compared to previous announcement thus having it Thursday-Friday. =0D=

The co-located SAIL Efraim workshop would then be on the Wednesday.=0D
Final decision will be announced on mailing list and Wiki very soon.=0D
=0D
Dave:=0D
   - trying to avoid conflict with NSF meeting (presumably Mon, Tue)=0D
   - will assess interest to attend on Wiki=0D
=0D
comments:=0D
=0D
Lixia:=0D
   - date will be difficult for US academics to attend=0D
=0D
Dave:=0D
   - other proposals or hosting offers?=0D
=0D
Boerje: decide later about Orlando meeting=0D
=0D
   =0D
----------------------------------------------------------------------=0D=

NetInf protocol draft announcement=0D
=0D
----------------------------------------------------------------------=0D=

AOB=0D
=0D
- nothing=0D
=0D

--Apple-Mail=_B2A28D3C-8252-4353-AADA-8DA01A81CAEF
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="us-ascii"

<html><head><base href="data:"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-family: Helvetica; font-size: 12px; color: black; text-align: left; "><span class="Apple-style-span" style="font-size: medium; "></span></div></body></html>
--Apple-Mail=_B2A28D3C-8252-4353-AADA-8DA01A81CAEF--

--Apple-Mail=_D7F5B164-4115-407D-9A3F-BAB1707CDA27--

From lixia@cs.ucla.edu  Sat Nov 10 06:12:43 2012
Return-Path: <lixia@cs.ucla.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 4471021F863B for <icnrg@ietfa.amsl.com>; Sat, 10 Nov 2012 06:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.894
X-Spam-Level: 
X-Spam-Status: No, score=-105.894 tagged_above=-999 required=5 tests=[AWL=-0.706, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MPART_ALT_DIFF_COUNT=1.11, RCVD_IN_DNSWL_MED=-4,  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 WkeHMg9FSpn3 for <icnrg@ietfa.amsl.com>; Sat, 10 Nov 2012 06:12:41 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 8778B21F8650 for <icnrg@irtf.org>; Sat, 10 Nov 2012 06:12:41 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 32281A60016; Sat, 10 Nov 2012 06:12:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5jZTfNb7KQr; Sat, 10 Nov 2012 06:12:38 -0800 (PST)
Received: from [10.0.1.7] (cpe-76-174-94-152.socal.res.rr.com [76.174.94.152]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 7525CA6000D; Sat, 10 Nov 2012 06:12:38 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_64BB1F10-DDD5-4466-882A-4D77749C91E3"
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <68070FD5-8DA1-416F-A2C9-6EC667E06835@ericsson.com>
Date: Sat, 10 Nov 2012 06:12:48 -0800
Message-Id: <8DD7C791-F82E-4220-BC32-BB67001F5BEC@cs.ucla.edu>
References: <68070FD5-8DA1-416F-A2C9-6EC667E06835@ericsson.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Draft ICNRG minutes uploaded
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, 10 Nov 2012 14:12:43 -0000

--Apple-Mail=_64BB1F10-DDD5-4466-882A-4D77749C91E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman wrote:

> The draft ICNRG minutes are now available at:
> http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg
>=20
> Please check, add and comment.
>=20
> 	B=F6rje.

Hi B=F6rje, I did a pass over my part of the comments only. See attached =
below.

Lixia



--Apple-Mail=_64BB1F10-DDD5-4466-882A-4D77749C91E3
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_40140834-F7E6-466C-BAAB-5D29D3CA8534"


--Apple-Mail=_40140834-F7E6-466C-BAAB-5D29D3CA8534
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; =
"><br><div><div>On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Courier; 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"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; ">The draft ICNRG minutes are now available =
at:</div><a =
href=3D"http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg">http:=
//www.ietf.org/proceedings/85/minutes/minutes-85-icnrg</a><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><br class=3D"webkit-block-placeholder"></div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; ">Please check, add and comment.</div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><br></div><div style=3D"font-family: Helvetica; =
font-size: 12px; color: black; text-align: left; "><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>B=F6rje.</div></span></blockquote></div><br><div>Hi&nbsp;B=F6rje, =
I did a pass over my part of the comments only. See attached =
below.</div><div><br></div><div>Lixia</div><div></div></body></html>=

--Apple-Mail=_40140834-F7E6-466C-BAAB-5D29D3CA8534
Content-Disposition: attachment;
	filename=draft-ietf85-icnrg-minutes-lixia.txt
Content-Type: text/plain;
	x-mac-type=54455854;
	x-unix-mode=0644;
	name="draft-ietf85-icnrg-minutes-lixia.txt"
Content-Transfer-Encoding: quoted-printable

Ed note: '--' refers to the slide heading presented=0D
=0D
=0D
ICNRG@IETF85 Agenda=0D
=0D
Wednesday, November 7th 2012=0D
13:00 -- 14:30, 14:40 -- 15.40 Salon D=0D
Intro -- 5 min=0D
=0D
Note well=0D
Blue sheets=0D
*** Agenda bashing=0D
=0D
no comments=0D
=0D
*** ICNRG Work Item Status=0D
*** ICNRG Work Items -- 25 min/each=0D
=0D
-- objectives for this meeting=0D
-- interim meeting tentatively planned on 14/15 Feb 2013=0D
=0D
*** ICN Research Challenges=0D
    Fairness discussion - see wiki  (Damien Saucez)=0D
    http://trac.tools.ietf.org/group/irtf/trac/wiki/IcnProblemStatement=0D=

    Discussion on document content and outline (All)=0D
=0D
-- Damien Saucez presents=0D
=0D
Fairness between what:=0D
-- flows=0D
-- content=0D
-- customer=0D
-- link/interface fairness=0D
-- network fairness=0D
=0D
Enforcement: end-to-end vs. hop-by-hop=0D
	     =0D
Kostas: What is end-to-end?=0D
	Is the discussion of ends "suitable"?=0D
	After all, we have a different paradigm here.=0D
	Not properly reflected in the figures made.=0D
=0D
Damien: there is also no notion of flow defined.=0D
=0D
Kostas: doesn't understand why we need to define flow.=0D
	We need a completely new understanding of fairness.=0D
=0D
Damien does want to put forward questions, not solutions.=0D
The way the slides are ordered =0D
=0D
-- Summary: =0D
   -- what is a flow?=0D
   -- what is a resource?=0D
   -- what fairness do we want to reach and how to measure it=0D
=0D
Mirja:	=0D
=0D
Karen Sollins: why is flow on this slide?=0D
      	       Flow implies a certain way of thinking about things.=0D
	       Avoid the term flow altogether.=0D
=0D
Kostas: refers to fairness in peer-to-peer networks.=0D
Boerje: a number of new types of resources comes into the picture=0D
	This presentation is about going beyond flows when discussing =
fairness.=0D
	When comparing to IP networks, we need to relate to flows.=0D
=0D
...: You need to compare this traffic to other types of traffic.=0D
     What this fairness is for is a reasonable question to ask.=0D
=0D
Lars: What is the impact of your traffic on other traffic?=0D
      Is ICN aware of the capacity sharing and Re-ECN work.=0D
=0D
Dave: Key: capability of trading off caching for bandwidth.=0D
      You may have to look at groups of users accessing content.=0D
      Some drag down content from an upstream link, others use=0D
      the stuff from the cache.  These=0D
=0D
Matt: This is about mapping content networking to a different paradigm.=0D=

      Think OS schedulers, earlier completion time, etc.  Yields a =0D
      completely different sense of fairness.=0D
=0D
Lars: Contention your access to an information object causes to others=0D=

      who want to use the same network for other stuff.  Fairness is =0D
      about how you balance this out.=0D
=0D
...: ?=0D
=0D
Dirk: comment on Damien's presentation: different ICN approaches have=0D
      different concepts for transport (and flows). We should document=0D=

      this in the survey draft. It is difficult to discuss this on a=0D
      general level.=0D
=0D
<Dirk's slides to come here -- deferred for logistics reasons>=0D
=0D
*** ICN Challenges=0D
=0D
-- document purpose=0D
   -- why?=0D
   -- how?=0D
   -- what?=0D
   -- possible results?=0D
=0D
-- input so far=0D
-- note=0D
-- proposed structure for the document=0D
   1. intro=0D
   2. problems=0D
   3. concepts=0D
   4. research challenges=0D
   5. impact on IETF work=0D
=0D
Kostas: monitoring, measurement, and instrumentation=0D
	did not have traceroute and ping from the beginning=0D
=0D
-- current status=0D
=0D
*** ICN Survey document -=0D
    Presentation of On the Content Retrieval In Information-Centric =
Network, (Will Liu)=0D
    http://datatracker.ietf.org/doc/draft-ren-icn-content-retrieval=0D
    Discussion on document content and outline (All)=0D
=0D
This is an excerpt of a summary report on ICN.=0D
=0D
-- motivation=0D
-- terminology=0D
=0D
Kevin: provider vs. author is a relevant distinction here.=0D
=0D
-- requirements and functionality=0D
=0D
-- summary (1/3)=0D
-- summary (2/3)=0D
-- summary (3/3)=0D
=0D
Kevin: some issues to consider=0D
       -- scalability in different dimensions=0D
       -- brittleness (e.g., concerning naming schemes)=0D
       -- type of persistence wrt the cache=0D
=0D
Kostas: what's persistent?=0D
	I may have content on a box, but I may not be able to get it off=0D=

=0D
Kevin: one type of persistence: if I turn of the power, will the content =
survive?=0D
       what would happen if I shut down an entire network=0D
=0D
Dave (from the floor): two dimensions at least to this problem=0D
      -- vulnerability=0D
      -- longevity=0D
=0D
Dave (chair): this may be input to some of the work items=0D
     	      how shall we take this work forward?=0D
	      is this input?  a starting point?=0D
=0D
Kostas: should this cover work in the IETF that happens?=0D
=0D
Lixia: what is the scope of the survey?=0D
       Beyond IETF and IRTF?=0D
       The presentation we just heard was about file retrieval in a =
fairly narrow=0D
       view.  Information Centric Networking covers a much broader =
scope.=0D
       What's the chairs' assessment regarding the scope of the survey?=0D=

=0D
Dave: wants feedback from the group.=0D
=0D
Lixia: This should be a survey of ICN research activities, not a survey =
of traditional=0D
		CDNs.=0D
=0D
Dave: should accommodate current research efforts=0D
      But: we are not writing a 300 page monograph.=0D
      Striking the balance is important.=0D
=0D
Lixia: the length of the survey is a function of the level of details in =
description.=0D
		It should not change the scope of ICN definition.=0D
=0D
Dave: good observation.=0D
=0D
Eve: solicit input on diverse work items=0D
     the RG wants to get a baseline but also be able to compare (for a =
particular use case)=0D
     Maybe a closer look at the scenario and use cases will help.=0D
=0D
Dave: does the union of the document address Eve's concers?=0D
=0D
Karen: is concerned that there is a big elephant in the room what we =
mean by ICN.=0D
       Agrees with Lixia on the scope to be broad.  But some projects =
are less=0D
       information-centric in the strict sense.=0D
       This discussion may open up a huge can of worms.=0D
=0D
Eve: use case driven approach helps us in scoping=0D
=0D
Karen: use cases must cover a broad enough set=0D
=0D
Kostas: we should err on the side of inclusiveness.  Must be =
contribution driven.=0D
	People can best write about what they do (less about others' =
stuff).=0D
=0D
Lixia: yes, an RG is contribution driven. But if we do a survey, it must =
be=0D
       a real survey of all existing work, not limited to what the =
authors know=0D
       about.=0D
=0D
       Karen commented: are we doing architecture?  Lixia seconds this.=0D=

=0D
Kostas: Architecture as a 110th proposal.=0D
=0D
Lixia: what's the goal for the research group?=0D
=0D
Boerje: we are free to define our goals as we go along.  Lars confirms =
by nodding.=0D
=0D
Lars: agrees with Boerje.  A venue where people can bring there =
topic-related=0D
      research and discuss it.  Maybe somebody wants to take ideas and =
write up=0D
      an architecture.=0D
=0D
      RGs don't operate by consensus.  We may write up and discuss =
multiple ideas=0D
      at the same time and may even have multiple competing =
publications. There is=0D
      plenty of past evidence on this.=0D
=0D
      Emphasizes that the RG is contribution-driven.  RGs are probably =
worse than=0D
      WGs from this perspective.=0D
=0D
Dave: # people (mostly in academia), we are getting a fairly large =
community.=0D
      No point in having another place to do the same community stuff as =
elsewhere.=0D
      What the special place that ICN RG (that is not redundant) can =
offer.=0D
=0D
      One example: what's the measurement and comparison metrics?=0D
      Maybe a meta architecture.  How to compare different =
architectures?=0D
      How to cut through eternal arguments between groups with different =
approaches.=0D
=0D
      A survey document may provide some ground truth here.=0D
=0D
Karen: agrees: differences, strengths and weaknesses=0D
       missing: there is no group that starts to think about what do we =
mean by =0D
       this space.  We don't have a common enough understanding of what =
ICN means.=0D
       survey is a good starting point.=0D
       Probably a living document since things evolve all the time.=0D
       If you do a survey, you need to do the work.=0D
=0D
Lixia: agrees with Dave; doing architecture does not mean this RG =
defines its own;=0D
		 various designs exist but comparative evaluation is =
missing, which can be a task of this RG. The RG needs to have its unique =
value.=0D
=0D
       Agrees with Karen: providing a definition of ICN makes a good =
contribution.=0D
=0D
Kevin: Doing an arch framework document first was a very useful starting =
point.=0D
       Survey isn't the same and it may not be easy to extract from =
other approaches.=0D
=0D
Lars: on the metrics: provides example for TCP; if you want to propose a =
TCP=0D
      extension, you need to run these simulations and present your =
results for=0D
      certain cases.=0D
=0D
      Maybe something similar can make sense here.  Scenario, numbers =
and=0D
      parameters.  One way to compare different architectures=0D
=0D
Dave: good point, but TCP comparison isn't perfect: TCP was around for =
15 years=0D
      when this was done.  We are at the starting point.  So, this won't =
be easy.=0D
=0D
Boerje: was it a good thing to not have done this earlier for TCP?=0D
Dave: does not know the answer.=0D
=0D
Boerje: agrees with measurements and scenarios.=0D
=0D
	An advantage over conferences is that we can talk about things =
that are=0D
	not new.=0D
=0D
...: ICN vs. CDN.=0D
=0D
Dave: Hard question: if there seems to be some emerging sense on working=0D=

      on comparison.  Who here is willing to do some work on this?=0D
      For use cases, scenarios, applications on the way towards =
evaluation frameworks:=0D
      =0D
      Bunch of hands up.=0D
=0D
Boerje: People shall sign up on the Wiki for topics and spec what they =
wanna do.=0D
	Will organize the work around subgroups.=0D
=0D
...: Defining terminology is really important, also to be even able to =
talk about=0D
     architecture framework and specific designs.=0D
=0D
Boerje agrees.  Contributions on this topic welcome.=0D
=0D
*** ICN Baseline Scenarios =0D
    Presentation of draft-pentikousis-icn-scenarios-00.txt (Kostas =
Pentikousis)=0D
    =
http://trac.tools.ietf.org/group/irtf/trac/attachment/wiki/IcnBaselineScen=
arios/draft-pentikousis-icn-scenarios-00.txt=0D
    Discussion on document content and outline (All)=0D
    Specific Proposals -- 20 min=0D
=0D
< Kostas escaped from the room just when his presentation came up :-) >=0D=

=0D
-- draft goals=0D
-- draft overview=0D
-- social networking=0D
=0D
Joen (Delft U): have a ppsp reference implementation based upon a single =
hash request=0D
=0D
-- example=0D
-- real-time=0D
-- mobility (multi-access)=0D
-- infrastructure sharing=0D
-- content distribution=0D
-- example (CURLING project)=0D
-- ee and dtn=0D
=0D
Eve: work not just in ndn also at intel labs on home management systems=0D=

     (e.g., about energy usage); considering privacy.=0D
=0D
Kostas: energy efficient ICT vs. ICT for energy efficient=0D
	this could be another scenario =0D
=0D
Eve promises a scenario.=0D
=0D
-- scenario topology=0D
-- for the record=0D
=0D
... (Huawai): more discussion on what is unique on ICN (compared to IP)=0D=

=0D
Dirk: nice collection of scenarios (thanks) -- we should be clear=0D
      about the objective. Draft abstract says it's about comparing=0D
      approaches -- current text and presentation looks more like ICN=0D
      use cases.=0D
=0D
Kostas: wants to collect feedback first=0D
=0D
Volunteers: please go to the Wiki and add your name=0D
=0D
*** Coordinated Forwarding and Caching in Information-Centric Networks =
(Xie) -- 15 min=0D
    =
http://sites.google.com/site/haiyongxie/draft-xie-icn-coordinated-caching-=
forwarding.txt =0D
    Deployment Aspects -- 30 min=0D
=0D
-- contributors=0D
-- caching=0D
-- a motivating example=0D
-- a motivating example (continued)=0D
-- coordinating caching & forwarding=0D
-- leverage content popularity info=0D
-- handle consistency=0D
-- handle consistency (continued)=0D
-- summary=0D
=0D
Damien: did you look at the problem of scalability and churn?=0D
=0D
good point.  Number of announcements by routers is kept small.=0D
=0D
Dave: Did you look at caches at certain sizes?  content popularity?=0D
      How do you know where the threshold should fall?=0D
=0D
=0D
Discussing how to deal with ICN deployment issues=0D
Discussion=0D
=0D
Presenters are not available today.  No need to spend a lot of time on =
this=0D
today.  Basically, people should think about including deployment =
aspects in=0D
one of the three documents we are currently working on.=0D
=0D
Might also become a separate work item to be worked upon later.  But =
this=0D
should not prevent us from discussing it.  Input is welcome!=0D
=0D
Boerje:=0D
   - postpone to another meeting=0D
   - separate work item, maybe later=0D
   - input and discussion welcome=0D
=0D
Spirous slide on ICN vs. CDNI points (not presented)=0D
=0D
Migration Incentives=0D
=0D
Kostas: there is an article in upcoming IEEE commag=0D
=0D
Proposed reading list:=0D
ICN vs. CDN  =
http://tools.ietf.org/id/draft-fmn-cdni-advanced-use-cases-00.txt =0D
Information-Centric Network in an ISP,  =
http://tools.ietf.org/html/draft-li-icnrg-icn-isp-01 =0D
=
http://www.psirp.org/files/Deliverables/FP7-INFSO-ICT-216173-PSIRP-D4.6_Fi=
nalReportOnDeplIncBusinessModels.pdf=0D
http://hal.inria.fr/docs/00/68/44/58/PDF/paper.pdf=0D
=0D
Other Business -- 20 min=0D
=0D
----------------------------------------------------------------------=0D=

=0D
ICNRG interim meeting=0D
=0D
Boerje:=0D
   - want to have longer meetings than just 2 hours at IETF=0D
   - proposing meeting in February (14-15) in Stockholm, i.e. slide 1 =
day compared to previous announcement thus having it Thursday-Friday. =0D=

The co-located SAIL Efraim workshop would then be on the Wednesday.=0D
Final decision will be announced on mailing list and Wiki very soon.=0D
=0D
Dave:=0D
   - trying to avoid conflict with NSF meeting (presumably Mon, Tue)=0D
   - will assess interest to attend on Wiki=0D
=0D
comments:=0D
=0D
Lixia:=0D
   - The proposed interim meeting date can be difficult for US academics =
to attend=0D
=0D
Dave:=0D
   - other proposals or hosting offers?=0D
=0D
Boerje: decide later about Orlando meeting=0D
=0D
   =0D
----------------------------------------------------------------------=0D=

NetInf protocol draft announcement=0D
=0D
----------------------------------------------------------------------=0D=

AOB=0D
=0D
- nothing=0D
=0D

--Apple-Mail=_40140834-F7E6-466C-BAAB-5D29D3CA8534
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div></div><div><br></div></body></html>
--Apple-Mail=_40140834-F7E6-466C-BAAB-5D29D3CA8534--

--Apple-Mail=_64BB1F10-DDD5-4466-882A-4D77749C91E3--

From luca.muscariello@orange.com  Tue Nov 13 01:34:45 2012
Return-Path: <luca.muscariello@orange.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 C378C21F8648 for <icnrg@ietfa.amsl.com>; Tue, 13 Nov 2012 01:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.759
X-Spam-Level: 
X-Spam-Status: No, score=-4.759 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, 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 Im43krJwsW0Y for <icnrg@ietfa.amsl.com>; Tue, 13 Nov 2012 01:34:41 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id CB3B721F8683 for <icnrg@irtf.org>; Tue, 13 Nov 2012 01:34:37 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 511F45D9238 for <icnrg@irtf.org>; Tue, 13 Nov 2012 10:34:35 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 3EF415D9205 for <icnrg@irtf.org>; Tue, 13 Nov 2012 10:34:35 +0100 (CET)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Nov 2012 10:34:35 +0100
Received: from [10.193.161.26] ([10.193.161.26]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Nov 2012 10:34:34 +0100
Message-ID: <50A21429.2030705@orange.com>
Date: Tue, 13 Nov 2012 10:34:33 +0100
From: MUSCARIELLO Luca OLNC/OLN <luca.muscariello@orange.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: icnrg <icnrg@irtf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090303040206090802010100"
X-OriginalArrivalTime: 13 Nov 2012 09:34:34.0259 (UTC) FILETIME=[1730B630:01CDC182]
Subject: [icnrg] Call For Papers - IEEE INFOCOM Workshop on Emerging Design Choices in Name-Oriented Networking - IEEE NOMEN 2013
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: MUSCARIELLO Luca OLNC/OLN <luca.muscariello@orange.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: Tue, 13 Nov 2012 09:34:45 -0000

This is a cryptographically signed message in MIME format.

--------------ms090303040206090802010100
Content-Type: multipart/alternative;
 boundary="------------080700090801050409080208"

This is a multi-part message in MIME format.
--------------080700090801050409080208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

********* CALL FOR PAPERS - IEEE NOMEN 2013 *********

   IEEE INFOCOM Workshop on Emerging  Design Choices
            in Name-Oriented Networking

******* in conjunction with IEEE INFOCOM 2013 *******


April 19, 2013
Turin, Italy
http://infocom.di.unimi.it/index.php/nomenwksp.html


Scope of the conference

The concept of name-oriented networking (also referred to as
Content/Information-Centric Networking) has emerged in recent years
as a promising paradigm for the future Internet architecture.
Instead of address-oriented communication, as in the current
Internet architecture, a name-oriented network architecture
considers named data as first class entities and rethinks the
communication model in terms of what data to fetch instead of which
host to reach. This basic idea has spawned world-wide research
efforts in exploring various design approaches to enable
applications communicating by data names instead of host IP
addresses in a scalable, secure, and efficient manner.

Following the success of NOMEN 2012, the objective of this workshop
is to present up-to-date research advances in the field, with an
emphasis on new applications enabled by the novel paradigm and on
the evaluation and deployment challenges. More specifically, we
solicit contributions in

(1) new applications and use cases facilitated by the name-oriented
networking paradigm (for example IoT networking, enterprise
networks, supporting peer-to-peer applications, health-care
applications, vehicle networking, online gaming);

(2) implementation, scaling and deployment challenges; and

(3) methodologies for evaluating existing design choices and
comparing their respective advantages.

The workshop solicits submissions of original work that pertains to
the design, development, evaluation, and analysis of name-oriented
networks and applications. Topics of interest include, but are not
limited to, the following:

     * Business models and economic issues
     * Deployment challenges and test-bed experience
     * Methodologies for measuring and comparing system performance
     * New application designs and use cases
     * Data naming
     * Security and privacy
     * Name-oriented routing protocols
     * Forwarding strategies
     * Network management and operations
     * Mobility management
     * Delay tolerant networks
     * In-network caching techniques
     * Performance Evaluation
     * Router designs
     * Resource management and congestion control
     * Transport protocols

Manuscript submissions

All submissions must be original work that has not been published
or submitted elsewhere. The workshop will accept papers describing
completed work as well as work-in-progress; papers describing
significant experiments are especially encouraged. Reviews will be
single-blind; please include author's name and affiliation in the
submission.

* Paper Submission: Submissions must be no greater than 6 pages in length=

and in a pdf file (IEEE Infocom style).
Authors of accepted papers are expected to present their papers at
the workshop.

* Poster/demo Submission: Submissions must be no greater than 2
pages in length and in a pdf file.

* Panel Proposal Submission:  Submissions should identify the panel
chair and the complete list of panel members, with indications on
whether each proposed panelist has been contact and agreed to
participate.

Important dates

     * Paper Submission:  December 16, 2012, 11:59PM PST
     * Acceptance notification: January 16, 2013
     * Camera-ready Version: January 26, 2013

Organization

Technical Program Committee Chairs

- Giovanna Carofiglio, Bell Labs, Alcatel-Lucent, France

- Lixia Zhang, UCLA, USA

Steering Committee

- Van Jacobson, PARC, USA

- Luca Muscariello, Orange Labs, France Telecom, France

- Dave Oran, Cisco System, USA

- James Roberts, INRIA, France

- K.K. Ramakrishnan, AT&T, USA

- Anwar Walid, Bell Labs, Alcatel-Lucent, USA




--=20
France Telecom R&D - Orange Labs
MUSCARIELLO Luca - CORE/TPN/TRM
38 - 40, rue du General Leclerc
92794 Issy Les Moulineaux Cedex 9 - France
Tel : +33 (0)1 45 29 60 37
http://perso.rd.francetelecom.fr/muscariello


--------------080700090801050409080208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DISO=
-8859-1">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <font size=3D"-1">********* CALL FOR PAPERS - IEEE NOMEN 2013
      *********
<br>
      &nbsp;<br>
      &nbsp; IEEE INFOCOM Workshop on Emerging&nbsp; Design Choices
<br>
      &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in Nam=
e-Oriented Networking
<br>
      &nbsp;<br>
      ******* in conjunction with IEEE INFOCOM 2013 *******
<br>
      &nbsp;<br>
      &nbsp;<br>
      April 19, 2013
<br>
      Turin, Italy
<br>
      <a class=3D"moz-txt-link-freetext" href=3D"http://infocom.di.unimi.=
it/index.php/nomenwksp.html">http://infocom.di.unimi.it/index.php/nomenwk=
sp.html</a>
<br>
      &nbsp;<br>
      &nbsp;<br>
      Scope of the conference
<br>
      &nbsp;<br>
      The concept of name-oriented networking (also referred to as
<br>
      Content/Information-Centric Networking) has emerged in recent
      years
<br>
      as a promising paradigm for the future Internet architecture.
<br>
      Instead of address-oriented communication, as in the current
<br>
      Internet architecture, a name-oriented network architecture
<br>
      considers named data as first class entities and rethinks the
<br>
      communication model in terms of what data to fetch instead of
      which
<br>
      host to reach. This basic idea has spawned world-wide research
<br>
      efforts in exploring various design approaches to enable
<br>
      applications communicating by data names instead of host IP
<br>
      addresses in a scalable, secure, and efficient manner.
<br>
      &nbsp;<br>
      Following the success of NOMEN 2012, the objective of this
      workshop
<br>
      is to present up-to-date research advances in the field, with an
<br>
      emphasis on new applications enabled by the novel paradigm and on
<br>
      the evaluation and deployment challenges. More specifically, we
<br>
      solicit contributions in
<br>
      &nbsp;<br>
      (1) new applications and use cases facilitated by the
      name-oriented
<br>
      networking paradigm (for example IoT networking, enterprise
<br>
      networks, supporting peer-to-peer applications, health-care
<br>
      applications, vehicle networking, online gaming);
<br>
      &nbsp;<br>
      (2) implementation, scaling and deployment challenges; and
<br>
      &nbsp;<br>
      (3) methodologies for evaluating existing design choices and
<br>
      comparing their respective advantages.
<br>
      &nbsp;<br>
      The workshop solicits submissions of original work that pertains
      to
<br>
      the design, development, evaluation, and analysis of
      name-oriented
<br>
      networks and applications. Topics of interest include, but are
      not
<br>
      limited to, the following:
<br>
      &nbsp;<br>
      &nbsp;&nbsp;&nbsp; * Business models and economic issues
<br>
      &nbsp;&nbsp;&nbsp; * Deployment challenges and test-bed experience
<br>
      &nbsp;&nbsp;&nbsp; * Methodologies for measuring and comparing syst=
em
      performance
<br>
      &nbsp;&nbsp;&nbsp; * New application designs and use cases
<br>
      &nbsp;&nbsp;&nbsp; * Data naming
<br>
      &nbsp;&nbsp;&nbsp; * Security and privacy
<br>
      &nbsp;&nbsp;&nbsp; * Name-oriented routing protocols
<br>
      &nbsp;&nbsp;&nbsp; * Forwarding strategies
<br>
      &nbsp;&nbsp;&nbsp; * Network management and operations
<br>
      &nbsp;&nbsp;&nbsp; * Mobility management
<br>
      &nbsp;&nbsp;&nbsp; * Delay tolerant networks
<br>
      &nbsp;&nbsp;&nbsp; * In-network caching techniques
<br>
      &nbsp;&nbsp;&nbsp; * Performance Evaluation
<br>
      &nbsp;&nbsp;&nbsp; * Router designs
<br>
      &nbsp;&nbsp;&nbsp; * Resource management and congestion control
<br>
      &nbsp;&nbsp;&nbsp; * Transport protocols
<br>
      &nbsp;<br>
      Manuscript submissions
<br>
      &nbsp;<br>
      All submissions must be original work that has not been published
<br>
      or submitted elsewhere. The workshop will accept papers
      describing
<br>
      completed work as well as work-in-progress; papers describing
<br>
      significant experiments are especially encouraged. Reviews will
      be
<br>
      single-blind; please include author's name and affiliation in the
<br>
      submission.
<br>
      &nbsp;<br>
      * Paper Submission: Submissions must be no greater than 6 pages in
      length
<br>
      and in a pdf file (IEEE Infocom style).
<br>
      Authors of accepted papers are expected to present their papers
      at
<br>
      the workshop.
<br>
      &nbsp;<br>
      * Poster/demo Submission: Submissions must be no greater than 2
<br>
      pages in length and in a pdf file.
<br>
      &nbsp;<br>
      * Panel Proposal Submission:&nbsp; Submissions should identify the
      panel
<br>
      chair and the complete list of panel members, with indications on
<br>
      whether each proposed panelist has been contact and agreed to
<br>
      participate.
<br>
      &nbsp;<br>
      Important dates
<br>
      &nbsp;<br>
      &nbsp;&nbsp;&nbsp; * Paper Submission:&nbsp; December 16, 2012, 11:=
59PM PST
<br>
      &nbsp;&nbsp;&nbsp; * Acceptance notification: January 16, 2013
<br>
      &nbsp;&nbsp;&nbsp; * Camera-ready Version: January 26, 2013
<br>
      &nbsp;<br>
      Organization
<br>
      &nbsp;<br>
      Technical Program Committee Chairs
<br>
      &nbsp;<br>
      - Giovanna Carofiglio, Bell Labs, Alcatel-Lucent, France
<br>
      &nbsp;<br>
      - Lixia Zhang, UCLA, USA
<br>
      &nbsp;<br>
      Steering Committee
<br>
      &nbsp;<br>
      - Van Jacobson, PARC, USA
<br>
      &nbsp;<br>
      - Luca Muscariello, Orange Labs, France Telecom, France
<br>
      &nbsp;<br>
      - Dave Oran, Cisco System, USA
<br>
      &nbsp;<br>
      - James Roberts, INRIA, France
<br>
      &nbsp;<br>
      - K.K. Ramakrishnan, AT&amp;T, USA
<br>
      &nbsp;<br>
      - Anwar Walid, Bell Labs, Alcatel-Lucent, USA</font><br>
    <br>
    <br>
    <br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
France Telecom R&amp;D - Orange Labs
MUSCARIELLO Luca - CORE/TPN/TRM
38 - 40, rue du General Leclerc
92794 Issy Les Moulineaux Cedex 9 - France
Tel : +33 (0)1 45 29 60 37
<a class=3D"moz-txt-link-freetext" href=3D"http://perso.rd.francetelecom.=
fr/muscariello">http://perso.rd.francetelecom.fr/muscariello</a>

</pre>
  </body>
</html>

--------------080700090801050409080208--

--------------ms090303040206090802010100
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIISyjCC
BgQwggPsoAMCAQICAwC21jANBgkqhkiG9w0BAQUFADBMMRwwGgYDVQQDExNPcmFuZ2UgTGFi
cyBVc2VyIENBMQ4wDAYDVQQLEwVBc3BpYzEPMA0GA1UEChMGT3JhbmdlMQswCQYDVQQGEwJG
UjAeFw0xMjA3MDkxMzA2MDBaFw0xNzA3MDgxMzA2MDBaMIGPMQswCQYDVQQGEwJGUjEPMA0G
A1UEChMGT3JhbmdlMQ4wDAYDVQQLEwVBU1BJQzEZMBcGA1UEAxMQTHVjYSBNVVNDQVJJRUxM
TzEYMBYGCgmSJomT8ixkAQETCExZQU03MjYwMSowKAYJKoZIhvcNAQkBFhtsdWNhLm11c2Nh
cmllbGxvQG9yYW5nZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCMJjRJ
/7+XLCoa9o8C9hxsOZJPtdrQSL9Jp5dgmiaAN8nJYDVuM5CYZFOgB1bQjBsAYx6njidgb1ox
E6ytB3MpFS6l58Ffyn3HoPxe047rCjt4ihvGOk3STB1pyet3UVGzH0E+PgdHvLh3ZcqFoOEp
MgwuJO4AMA/prM8EpSVekWZmHD/23LcbZQf7G+CVzkh8cAkledDU/j4/2jHp3TAy+2f+ifDH
OxbfUNwgUpL8Pq++HwkN3+sNZAc8fXouEiT8P/JGA5mJ1PSSCZJny6m8Q30DvghQ1yKHXX+/
cNyhc9Twji/9IuOAoN/F3CJkcKV/OPL4dRcXshkZAZDK2BPpAgMBAAGjggGpMIIBpTAPBgNV
HQ8BAf8EBQMDBzAAMBMGA1UdJQQMMAoGCCsGAQUFBwMEMB0GA1UdDgQWBBSs7ScVec03HTtn
DagYtl29Oc/4cDBVBgNVHSMETjBMgBRjjiU37MIHhhTUjoGjH2EZAX8rMKEvgS1DTj1PcmFu
Z2UgTGFicyBVc2VyIENBLE9VPUFzcGljLE89T3JhbmdlLEM9RlKCAwCVMTCBpgYDVR0fBIGe
MIGbMDKgMKAuhixodHRwOi8vcC1wa2kucmQuZnJhbmNldGVsZWNvbS5mci91c2VyY3JsLmNy
bDAyoDCgLoYsaHR0cDovL2wtcGtpLnJkLmZyYW5jZXRlbGVjb20uZnIvdXNlcmNybC5jcmww
MaAvoC2GK2h0dHA6Ly9wa2kucmQuZnJhbmNldGVsZWNvbS5jb20vdXNlcmNybC5jcmwwEQYJ
YIZIAYb4QgEBBAQDAgUgMEsGA1UdEQREMEKBG2x1Y2EubXVzY2FyaWVsbG9Ab3JhbmdlLmNv
bYEjbHVjYS5tdXNjYXJpZWxsb0BvcmFuZ2UtZnRncm91cC5jb20wDQYJKoZIhvcNAQEFBQAD
ggIBAAUYYl7eJbhLTs/Eac/tqeX6xSbzs65amHg0OUpa5OnXBqn6dHjvJcM6YF0Qo43Id8GL
Yz4pYvJrCqbUJXnovvKPzgrdOo4XqFErEqgSP0L6C12rrH8ZSf1utrA2E+2Vphv5wSQAdWs8
NZje/bIHHkggmeH1b828T99cyzyuhTNC+o5trJA1Q9raRI7ljvKf2pyzbT0NmIGKK8JMXXwD
DqfgZOBEifXmHo600uNXyt7IPWSKu0mcw/BzLddSFOyG8c4yobCsn0QTlXLQmKLyzDXQWu2m
/CbUt3NwJq1ZPeLCfmfcj/oIbR+jnl5srXhEa6iEm8F6LN87gAirgrtnMqkI5fWST7nDrCuu
sfYOFGIm4fN97SmUPSdNaVbOWdCWu5oe0rlwXkh1XjsiC05EUrBpX2m0yPA/NAJXMarE6ZVN
yLsW5BYHwHyFHi69JuRs0xh4oLEMHlQOrBueeInpFhXH0Go9Qvx8cnzHYixF0+C1lE48o3vT
G0RgiTZut1L50nSgllHTYofe/ObRGDgxoy6Y4GKf9u9qiiS16e98VPPhZDsMwp0IhzOvcf1R
UNME5xOQp0o4gZAWNdZ7SNvPyakEiiBo6b7nnFwNZIbKvKVGPWjZ4/5xRcupNu5B5cMS52nI
3mlRrt7X23PfL+ZdZLMWUT5RmQIOnZmeOK5vzBDuMIIGSDCCBDCgAwIBAgIDALbVMA0GCSqG
SIb3DQEBBQUAMEwxHDAaBgNVBAMTE09yYW5nZSBMYWJzIFVzZXIgQ0ExDjAMBgNVBAsTBUFz
cGljMQ8wDQYDVQQKEwZPcmFuZ2UxCzAJBgNVBAYTAkZSMB4XDTEyMDcwOTEzMDYwMFoXDTE3
MDcwODEzMDYwMFowgY8xCzAJBgNVBAYTAkZSMQ8wDQYDVQQKEwZPcmFuZ2UxDjAMBgNVBAsT
BUFTUElDMRkwFwYDVQQDExBMdWNhIE1VU0NBUklFTExPMRgwFgYKCZImiZPyLGQBARMITFlB
TTcyNjAxKjAoBgkqhkiG9w0BCQEWG2x1Y2EubXVzY2FyaWVsbG9Ab3JhbmdlLmNvbTCCASIw
DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMOIUDy5iLc8zuPHsDXdC/89UNxPXt5aa5QO
M1lpWHQb2omQovyYjxUIGqoljExVsTSuv3BvA7uoO/QSsPnaAal67n5tlWljhFx+riygxg0m
6DRgAiFZB2j97e6kj8hrk4VECwEUI9JINiJeuulaqU3o/mDBBT8Z35ZmOtpsM6jiXaaEqUXw
YJ70c4Pt/xQPvrLisJ+KUPq5zoPDBskRXkQ+xfhyOyuED4w+9sV3myKycJPseH3kclqFiXNy
lrdX+n1NsK0ywCGUC8JzysOn/ZVrgWO2y1A7paJvNnKkRNE0c1hwRu5e2+e+OLzDKq/XykP8
fwqaImTw0CP1S/yq94MCAwEAAaOCAe0wggHpMA8GA1UdDwEB/wQFAwMHwAAwKQYDVR0lBCIw
IAYIKwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3FAICMB0GA1UdDgQWBBRxZS3H21UFJ+Lc
YatIcPQlz+KoPzBVBgNVHSMETjBMgBRjjiU37MIHhhTUjoGjH2EZAX8rMKEvgS1DTj1PcmFu
Z2UgTGFicyBVc2VyIENBLE9VPUFzcGljLE89T3JhbmdlLEM9RlKCAwCVMTCBpgYDVR0fBIGe
MIGbMDKgMKAuhixodHRwOi8vcC1wa2kucmQuZnJhbmNldGVsZWNvbS5mci91c2VyY3JsLmNy
bDAyoDCgLoYsaHR0cDovL2wtcGtpLnJkLmZyYW5jZXRlbGVjb20uZnIvdXNlcmNybC5jcmww
MaAvoC2GK2h0dHA6Ly9wa2kucmQuZnJhbmNldGVsZWNvbS5jb20vdXNlcmNybC5jcmwwEQYJ
YIZIAYb4QgEBBAQDAgWgMHkGA1UdEQRyMHCgLAYKKwYBBAGCNxQCA6AeDBxseWFtNzI2MEBy
ZC5mcmFuY2V0ZWxlY29tLmZygRtsdWNhLm11c2NhcmllbGxvQG9yYW5nZS5jb22BI2x1Y2Eu
bXVzY2FyaWVsbG9Ab3JhbmdlLWZ0Z3JvdXAuY29tMA0GCSqGSIb3DQEBBQUAA4ICAQA9fU7+
TpYa0PwHq+F9eAsgxtvA23ZYFI2IeGCDvqo+6puWNKE+CX6kjirKL+NPpNMauUg8zANR0dlZ
d10l49OeHRBC3SUuJrbzQPMX3efJSGSCqwRIBPi0aS8SD+YdMGTBikxi1EoUBENf0qJ/m9T2
qrtkprGetjTw3egmAIgoLLTBvs0jxtL7mqxikmCeD341IcgleT2s330SMpMwvLI2GJKuwLvC
Sm9UfjwZVWfVne3Q7DTuA0m6BRapQuTGIT+lrqpvUhBD5cFu8sQPeGAvmC0ez0heqB12yQZT
HEFs6NZE2kb7wOjWqT6BQc+tX35iqo5B8sKUPohjvLpHl1H7WA5aO1e/u0/5rJv3y9+45Tdt
YdWwuY++o2IWt6XNYJtuugvxjUD6D6TAAk4MxQ1kpfKHCToNxCLEEBKpNh/rtwSOkzt2DJex
f3hJ9NUYACtOdgzGSBcQY2xlXGEWOrTtCCmZBxR1hYWs3kROcHyxM3eb4oOL6oxVDqQGFngC
gzDPzFpnEXQLJ3aKIdLYMGASBIICPJcHSbnWiy2gSUxM67Ftz3XftjbER60vU9BWzQ22QLgD
NB+m+EY0Y9ytUXgbKopPM2GlwRRpMGVbQO0bRz0bbRZNSac/2WNPMa5ibEVNn5ddqCEBdGsS
jIYeKlg5Ku8ijEh68/8O7B3k6oprazCCBnIwggRaoAMCAQICAwCVMTANBgkqhkiG9w0BAQUF
ADBMMQswCQYDVQQGEwJGUjEcMBoGA1UEAxMTT3JhbmdlIExhYnMgUm9vdCBDQTEPMA0GA1UE
ChMGT3JhbmdlMQ4wDAYDVQQLEwVBc3BpYzAeFw0xMTA3MDgxMzMwMDBaFw0yNjA2MjkxMzMw
MDBaMEwxHDAaBgNVBAMTE09yYW5nZSBMYWJzIFVzZXIgQ0ExDjAMBgNVBAsTBUFzcGljMQ8w
DQYDVQQKEwZPcmFuZ2UxCzAJBgNVBAYTAkZSMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEAjPMmHtccQ+z0QWkL1O2HgtJfqklqw0vvUAF8zkku6Aw6aDzRq7uI9OFuZEIeAgHG
IVpH0yOkKAoExazi/q6B8brLuAs0oNiZq6gtPm5C+UnV1/sEuJSWC4MuiActRAMXpOEXuI3V
nTDz+s8d6N/Bn45cevbSvM6+ygLH0o2Nn2zVEHyN4zvRdriQv1VDUfqAo7uVjxtbzTvr4NLA
IJXUeHdAvop/Lqa1Bd4hUWyBzse8HUTV6zD84baxO7nJb7pBBeFUyhkNRmGyMg/wZJ7LeD2B
LSIZ9zY/2T7yMhc0eU+kXDePOxdN6m83P4W8TXBLFQPM7ZNz7K1YWD/XciF6ZRTExDoUsZ73
GYajPVjPgoaVQQcc7HkzfTE+YTLagIjL4BRbgq/nBUwexPoYEChQ132QFfIBkHjJz3yVzXFG
awPGeG+wYGkE+JTsrg1BlXPm6iUCtdVCIovKT2YElcV3Cm5DCI//Ccx/G1+Zu0uCjPzXvzsS
AarlhOlP/D9CohA0AIY2xkPNHWZqdeQJ5/DQxzH89D5jx9bsfPJONLQvzNSGQbjFYVyb3gf1
pBL/BtzoXOJjXetUWt3Hu0nPcMF2r8KgTs7ZcuyPbUiFPmFiWmb16ry+Ls1+w8Q1IGLNZNb6
95VHEBFQA0icw8rA4zDmozPIK6E1Fi3xyZixByXIbxUCAwEAAaOCAVswggFXMBIGA1UdEwEB
/wQIMAYBAf8CAQAwDwYDVR0PAQH/BAUDAwcGADAdBgNVHQ4EFgQUY44lN+zCB4YU1I6Box9h
GQF/KzAwVQYDVR0jBE4wTIAUVlvqwX4luyGOma/ubx1FjCuYQ7uhL4EtQz1GUixDTj1PcmFu
Z2UgTGFicyBSb290IENBLE89T3JhbmdlLE9VPUFzcGljggMAlTAwgaYGA1UdHwSBnjCBmzAy
oDCgLoYsaHR0cDovL3AtcGtpLnJkLmZyYW5jZXRlbGVjb20uZnIvcm9vdGNybC5jcmwwMqAw
oC6GLGh0dHA6Ly9sLXBraS5yZC5mcmFuY2V0ZWxlY29tLmZyL3Jvb3RjcmwuY3JsMDGgL6At
hitodHRwOi8vcGtpLnJkLmZyYW5jZXRlbGVjb20uY29tL3Jvb3RjcmwuY3JsMBEGCWCGSAGG
+EIBAQQEAwIABzANBgkqhkiG9w0BAQUFAAOCAgEASDhiLXUUbhFNYUcKznQeXbsOF73KHfjv
pt4G16yWnq9lhRnBpCwFoe1VsBdyHNQhTNaaC15rdgCJWIj3sTmfGw1/gtBZ8UmT2czrpYTs
Y5HQ4GVybq2Ra3N9tnjgOZFUQGtoezSjFbmjAI2MXMFYrHF+s2sKPyssEjuiuylTNyvFB4c0
lOF9/zTwZcJ1rPepcE9a0cFq70JhZYOVmIHMrPKaMnbaLkkuZWex2AKGkt8pXL2I95JMJ1qq
B9kOCE+cwCnCJn/G7CVnLYgZfqF+tptYUom1+QhYj/xZOmr2xBFM3CQDFMUuj15+MzdEHkUC
/CplnMloC8EsYZlB5t6oFgTgAvsjdTAzMMGGqusjg5ImbA5Er7p/XxDVuEooWyi6ogaYQuUi
RTOr+3xd+173Thb0C7eMRozihFpcddGhhvD6m819Nuv1SIf22Qr5M4jVQrcBS7rixUuqb4E8
wJfFaoCAItHcMK2/ZibXqGe/GXGzR8bZrY4/joXVdPr7vEn+EGQN15zbwS/PKazE2E86ghqF
NaSLPA44jNbRH91RRTIszHEoPfc/tyJQmgGav/7BN4fXrx0rNr+xyzx/eLOvGqCTzJq7m0M5
lM3BqAAhhWrLrviNkMbzg6pWzVvw5ThKDZJVyU0COrW7SNpuyoKscNbclhI3TaLsgpYyH38F
oSExggMTMIIDDwIBATBTMEwxHDAaBgNVBAMTE09yYW5nZSBMYWJzIFVzZXIgQ0ExDjAMBgNV
BAsTBUFzcGljMQ8wDQYDVQQKEwZPcmFuZ2UxCzAJBgNVBAYTAkZSAgMAttUwCQYFKw4DAhoF
AKCCAZUwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMTEz
MDkzNDMzWjAjBgkqhkiG9w0BCQQxFgQUhrdJPHlFAriyLKgeV4kAyVScIy8wYgYJKwYBBAGC
NxAEMVUwUzBMMRwwGgYDVQQDExNPcmFuZ2UgTGFicyBVc2VyIENBMQ4wDAYDVQQLEwVBc3Bp
YzEPMA0GA1UEChMGT3JhbmdlMQswCQYDVQQGEwJGUgIDALbWMGQGCyqGSIb3DQEJEAILMVWg
UzBMMRwwGgYDVQQDExNPcmFuZ2UgTGFicyBVc2VyIENBMQ4wDAYDVQQLEwVBc3BpYzEPMA0G
A1UEChMGT3JhbmdlMQswCQYDVQQGEwJGUgIDALbWMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZI
AWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZI
hvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEATi7k
XitY1A0Cs9YZNShcZumqBdaC+JgNB4ug/+fMbkCCuXXmaQUJG/fKe1A9SXqJrCALsi6+swrn
Gw1RvLp13ymxXLAmSJ2VwMdOoaryf8hqGNp+T4/L6ZMfRnEUbOMQd3yLhVDUHA0TEg/nzRdo
T9t1SccMWMFSvtBU5M0jOaeJbcC1ZGN2NsmcJCfL7OpmIOwvwBw65dM2FBzRN5a0umJgi3tk
Rufw68JXopY34oG3iyp6IhQPSYa2gshbKOQbeNTjWZaRqiWI3412IEVa7vE5tGhXz+xV6R84
lfVwsH3JX4M9Yj9wp+XoXmfkdZuMiQxxNNr6MCxGu+zO3ehiiwAAAAAAAA==
--------------ms090303040206090802010100--

From borje.ohlman@ericsson.com  Tue Nov 13 09:17: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 1E08121F8658 for <icnrg@ietfa.amsl.com>; Tue, 13 Nov 2012 09:17:17 -0800 (PST)
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 z6K0Wy1l6SJW for <icnrg@ietfa.amsl.com>; Tue, 13 Nov 2012 09:17:13 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8ECED21F8644 for <icnrg@irtf.org>; Tue, 13 Nov 2012 09:17:11 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1e6d000002d2c-51-50a280943af7
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 5F.89.11564.49082A05; Tue, 13 Nov 2012 18:17:09 +0100 (CET)
Received: from ESESSHC003.ericsson.se (153.88.183.27) by esessmw0247.eemea.ericsson.se (153.88.115.93) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 13 Nov 2012 18:17:08 +0100
Received: from ESESSMB107.ericsson.se ([169.254.7.89]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0318.001; Tue, 13 Nov 2012 18:17:08 +0100
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
To: Lixia Zhang <lixia@cs.ucla.edu>, icnrg <icnrg@irtf.org>
Thread-Topic: [icnrg] Draft ICNRG minutes uploaded
Thread-Index: AQHNvqfjeHjY+dCUEUq+IAhdSbFLPZfjDNkAgATqfYA=
Date: Tue, 13 Nov 2012 17:17:07 +0000
Message-ID: <2790F226-7135-46C7-9DD8-432606700A39@ericsson.com>
References: <68070FD5-8DA1-416F-A2C9-6EC667E06835@ericsson.com> <8DD7C791-F82E-4220-BC32-BB67001F5BEC@cs.ucla.edu>
In-Reply-To: <8DD7C791-F82E-4220-BC32-BB67001F5BEC@cs.ucla.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1914DB5AB1C85E41BBB5D2FCC0BC792E@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsUyM+Jvje7UhkUBBm+OsFnsnL2TyWLFnUZW ByaPR5uXs3hM3niYLYApissmJTUnsyy1SN8ugSuj+e1G1oJTbBUn975ibWCcw9rFyMkhIWAi 8XLRSjYIW0ziwr31QDYXh5DASUaJd6fesoAkhAR2Mkq8Xp8KkVjMKHHv/TewbjYBR4n3Tw+A 2SIC1hKzZt8Ds4UFDCVaJ3RDxY0kFs/6xAhhW0lcab8Eto1FQFVi3tVzYDW8AvYS11cvZodY ViJxdulNMJsTKP7sxUkmEJtRQFbiS+NqZhCbWUBc4taT+UwQVwtILNlznhnCFpV4+fgf1GeK EjvPtkPV60ncmDqFDcK2lpg4dymUrS2xbOFrZogbBCVOznwC9bCaxPEPx5gnMErMQrJuFpJR s5CMmoVk1CwkoxYwsq5iZM9NzMxJLzfcxAiMtoNbfuvuYDx1TuQQozQHi5I4L1fSfn8hgfTE ktTs1NSC1KL4otKc1OJDjEwcnFINjLIPTuhK+06azt1ofWdKU62pbPSsHcwpmY/uFWo6C9m8 j837ckW29O2sRTbnjHfsmh1dE8ToM5Vh/syOf9lPZRR7pQ7sMajiPLll8Ze1BvWp2UukP8+5 /rP6R7xZ8qT5sVOWT20591hf6uLl2P9VX+NYdS7rxxn19U5tjpzGmPVlK/9Hj8auECWW4oxE Qy3mouJEACcNgeiEAgAA
Subject: Re: [icnrg] Draft ICNRG minutes uploaded
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, 13 Nov 2012 17:17:17 -0000

I've now made an update according to Lixias comments.

Lixia,
Please double check that I got everything. I might have missed something as=
 your changes where not marked.

Everyone,
Anyone else have comments? if so please provide them before the end of the =
week. After that the minutes will be regarded as final.
If you have comments please mark explicitly which changes you would like to=
 have made to the documents.

B=F6rje

On 10 nov 2012, at 15:12, Lixia Zhang wrote:


On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman wrote:

The draft ICNRG minutes are now available at:
http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg

Please check, add and comment.

B=F6rje.

Hi B=F6rje, I did a pass over my part of the comments only. See attached be=
low.

Lixia

<draft-ietf85-icnrg-minutes-lixia.txt>


From paulo.mendes@ulusofona.pt  Wed Nov 14 07:10:39 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 1568121F84B6 for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 07:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.606
X-Spam-Level: 
X-Spam-Status: No, score=0.606 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_OBFU_TECHNOLOGIES=1.604]
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 4XrrUu7rzApZ for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 07:10:32 -0800 (PST)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by ietfa.amsl.com (Postfix) with ESMTP id D749521F84A1 for <icnrg@irtf.org>; Wed, 14 Nov 2012 07:10:31 -0800 (PST)
Received: by mail-bk0-f54.google.com with SMTP id jm19so291597bkc.13 for <icnrg@irtf.org>; Wed, 14 Nov 2012 07:10:30 -0800 (PST)
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=2BvUbPsEyJdDOhyU8iG75ReORJylFBqsqcbXIm3JOwI=; b=HxMUbr76xkmj/QgnbKMncuqH5tq4xF/8gkg0QMeDtuLnMZ5FdlIMqe5TV5k1r6TVC4 WwcVmUrEFsyvzHfqV6mt96Q7ZDSg4wDK5Mek3MVNSxaaCzxKqetpR/ThnyLbVn4FqRy1 7CtHW8V0TlIHEiHAx9aNQM/XFTGf5b+mJTh5siFkiZBMNgPiiXcKPnSeHy/+UxFh0Qja lfQJk9eP+FqJ3NbLhCZ+aA1LlrPMd0Gjndy79DMmE9vBYLCW9Lbg6BQTr4Tr7buQnZLS h+kRy29tWCHIhJ+fEN9BMxNYRhlafTTYTwvCBNBisUTN2og5Zn3BCoA03My+DjpWkRbs /aAA==
Received: by 10.204.147.212 with SMTP id m20mr4143083bkv.103.1352905830410; Wed, 14 Nov 2012 07:10:30 -0800 (PST)
Received: from unknown-f8-1e-df-e9-b9-b2.lan (89-181-195-175.net.novis.pt. [89.181.195.175]) by mx.google.com with ESMTPS id v14sm8274641bkv.10.2012.11.14.07.10.27 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 07:10:29 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_781115B5-0400-4940-A4A0-C24479EBC6A3"
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com>
Date: Wed, 14 Nov 2012 15:10:27 +0000
Message-Id: <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com>
To: <Ignacio.Solis@parc.com> <Ignacio.Solis@parc.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQm8xxUYHy8FL66KuDJ8/u8lPdLpEkXE8fG8y5NQMEl7vQPGftD7K+TYMCew4WCk8699fGVb
Cc: ngocthanhdinh@gmail.com, icnrg@irtf.org, elwynd@folly.org.uk, stephen.farrell@cs.tcd.ie, william.d.ivancic@nasa.gov
Subject: Re: [icnrg] Benefit of information centric network (ICN) compared to DTN in wireless communication
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, 14 Nov 2012 15:10:39 -0000

--Apple-Mail=_781115B5-0400-4940-A4A0-C24479EBC6A3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hello

Just saw this email now (yes, I've a email delay tolerant system :) ), =
and I think that Ignacio is making an important point.. The DTN and ICN =
research/work started from different perspectives. =46rom the DTN side, =
we have a standardization work aiming to devise one architecture. =46rom =
the ICN side we started by having different projects that follow the =
same generic ICN principles, but any of which we can be stamped as THE =
ICN reference. So, from an architectural point of view, this discussion =
is useless, and should be resumed after the ICNRG come up with some =
standard track proposal.

=46rom a general perspective, we can only try to analyze which paradigm =
brings more benefits to the end user (from whom does not matter how the =
engine works). Lets look at two aspects/requirements to start with:

a) Access to information: considering that the highest percentage of =
Internet traffic is data oriented (r.g. google, facebook, amazon, ebay, =
...) and not point-to-point (e.g. VoIP) a pull model like ICN in which =
the user "just" need to ask the network to provide the requested data =
seems more beneficial.

b) Operation in challenge scenarios: if we look at the edges of the =
Internet core (beyond the cellular, wireless, etc end points) we need a =
architecture capable to support data exchange even when there is no =
end-to-end path between any pair of nodes, or when end-to-end paths have =
ver long delays. The DTN arch was created for this scenario, based on =
persistent storage and the creation of a chain of TCP links. But since =
persistent storage is also a key element of ICN and since ICN is =
agnostic of communication links, I would say that ICN is a concept that =
can be applied to the same scenarios that DTN was initial designed to.

It is with this goal in mind (bring ICN concept to the DTN world) that =
we at SITILabs (http://siti.ulusofona.pt) are working on an modular =
architecture called ICON (Information-centric Opportunistic Networking) =
that started from the basic CCN concepts and includes a social-aware =
opportunistic routing protocol. For now the major goal is more software =
engineer oriented: we created an easy to install and use platform that =
runs in any personal device (windows, android, iphone, linux) and is =
being adjusted to embedded devices. For more info check: =
http://siti.ulusofona.pt/index.php/teechnology/182-icon-dtn-amazon-project=


So, IMO it is at all possible for a future ICNRG architecture proposal =
to be applied to any DTN scenario. It will all depend upon the =
direction/priorities that the ICNRG will set. Then we just need to show =
that such arch is also useful to set up point-to-point communications =
(see initial conceptual profs, as the 2009 VoCCN paper from Van Jacabson =
et al) :-).

Cheers
Paulo


On Sep 17, 2012, at 7:42 PM, <Ignacio.Solis@parc.com> =
<Ignacio.Solis@parc.com> wrote:

> Having worked on "all-of-the-above" I can say that the differences are =
not
> big.  I currently advise Preston and Rajesh on CBMEN (Content-Based =
Mobile
> Edge Networks) for DARPA, and I Worked on adding ICN capabilities to
> SPINDLE.
>=20
> The differences between the two "architectures" are becoming
> smaller/fewer.    Kevin's slides from Dagstuhl summarize what the =
group
> talked about in terms of ICN/DTN.
>=20
> One thing to note is that to some degree, both ICN and DTN refer to a
> group of projects or general architectures.  =46rom my point of view, =
the
> DTN community is relatively unified in the sense that it follows a few
> standards/conventions  (RFC 5050?).  =46rom the ICN perspective we =
have a
> situation where we're not unified at all. The different projects have =
made
> different tradeoffs.
>=20
> Due to this it is probably better to compare DTN to NetInf, PURSUIT, =
CCN,
> etc.   Depending on your application you might find that more than one =
has
> the features that you want.  Potentially you might want to choose one =
due
> to code maturity/production-level  or  due to future expandability.
>=20
> I would suggest that you think of the problem you're trying to solve,
> figure out the must-have and nice-to-have features and see which
> architecture/project works best for you based on:
>=20
> * what is currently implement in the code (alpha, beta, production)
> * what is the planned features in the short, medium and long-term
> * what is technically possible with the architecture   (that might =
never
> get done unless you do it yourself)
>=20
>=20
> After all, you can do everything over IP given enough services on top.
>=20
> Nacho
>=20
>=20
>=20
>=20
>=20
> --=20
> Ignacio Solis
> Networking Area Manager
> Palo Alto Research Center
> +1(650)812-4458
>=20
>=20
>=20
>=20
>=20
>=20
> On 9/14/12 4:59 PM, "Elwyn Davies" <elwynd@folly.org.uk> wrote:
>=20
>=20
>>=20
>> The US Army was (and as far as I know still are) very interested in =
DTN
>> as a way to improve throughput in what is essentially a vehicular =
ad-hoc
>> network.  Some years ago there were trials of the BBN-lead DARPA DTN
>> projects (SPINDLE) involving vehicles driving
>> round a track and comparing the performance of DTN and basic TCP. At =
one
>> point in time there was a comprehensive presentation (by Preston =
Marshall
>> if my memory is correct) of the results of this trial available on =
the
>> web, but it seems to have been withdrawn
>> - I failed to keep a copy of it and attempts to get it again have =
drawn
>> a blank.  There is some discussion of this work in the state of the =
art
>> document that I wrote for the N4C project about three years ago.  =
This
>> can be downloaded from
>> http://www.n4c.eu/Download/n4c-wp2-012-state-of-the-art-101.pdf.
>>=20
>> A Google search for something like 'us army dtn tcp vehicles' throws =
up a
>> whole raft of interesting references including mentions of the CONDOR
>> project and other stuff that is going on in vehicular ad hoc =
networking.
>> There is brief mention of CCN related topics.
>> An interesting report of more recent and complex trials can be found =
in
>> =
http://trs-new.jpl.nasa.gov/dspace/bitstream/2014/41752/1/JPL%20Pub%20D-65=

>> 838.pdf
>>=20
>> There is also an interestng perspective on combining ICN and DTN in =
this
>> talk...
>> http://rajesh-krishnan.com/talks/rkrishnan-coin-neu07.pdf
>>=20
>> Regards,
>> Elwyn
>>=20
>>=20
>> On 14/09/12 15:02, Ngoc Thanh Dinh wrote:
>>=20
>> Thank you very much!
>> That is one reason we want to implement ICN in ad-hoc vehicular =
network.
>> but we have to demonstrate it, before implementation, we have to make =
a
>> clear benefits.
>>=20
>> In high density, high mobility case, and constraint information =
(delay
>> time and location), do you think that DTN will give a not good
>> performance? (even increase delay compared to other). and ICN may be
>> better because ICN could support automatic ifnormation
>> searching and distributtion (matching interest and data) ?
>>=20
>>=20
>> We should make a clear benefit to select which one is more suitable =
for
>> this scenario.
>> Hope to have your discussion and thank you very much!
>>=20
>> 2012/9/14 Ivancic, William D. (GRC-RHN0)
>> <william.d.ivancic@nasa.gov>
>>=20
>> DTN, as is, only temporarily caches a bundle until it passes it on =
(in
>> general, but is implementation  and routing specific).  DTN, as is, =
does
>> not know what is inside the bundle (although, one could come up with
>> something
>> special to enable this).   ICN ensures that the information is cached =
at
>> the appropriate places and is available for ICN users to obtain. DTN
>> could be used to get the information to the ICN cache =
(complementary).
>> But, for DTN to be used as ICN, you have to
>> basically design ICN into DTN. DTN, as is, is complicated enough.
>>=20
>> - Will
>>=20
>> On Sep 14, 2012, at 8:52 AM, Ngoc Thanh Dinh wrote:
>>=20
>>=20
>> Yes. DTN could be a scenario which could be covered in ICN.
>> I am analyzing on the case of exchanging information among vehicles =
in
>> the ad-hoc vehicular network scenarios without infrastructure.
>> in case of long delay or disruption (main purpose of DTN), i think =
the
>> same performance could be implement based on information object and
>> caching of ICN.
>> but in the high density and high mobility case of vehicle, do you =
think
>> DTN will achieve a lower performance? (e.g. higher delay)
>>=20
>> I want to listen your discussion about the points that
>>=20
>> class 1: for information service which delayed or lost information =
does
>> not compromise safety or render the application useless (e.g. weather
>> reports,...) --> DTN capabilities can improve the quality in this =
case by
>> increasing the message delivery and reducing
>> delays in challenging scenarios.
>> And with ICN, we could also achieve this improvement, even more, =
based on
>> naming object, not destination host.
>>=20
>> class 2: for delayed information may compromise safety, application =
may
>> require realtime communication --> DTN may not improve the quality of
>> this case.
>> But ICN may make an improvement? (based on information object =
caching)
>>=20
>> Listen to your discussion and thank you very much!!!
>>=20
>>=20
>>=20
>>=20
>> 2012/9/14 Ivancic, William D. (GRC-RHN0)
>> <william.d.ivancic@nasa.gov>
>>=20
>> DTN and ICN may be complementary.  DTN is not ICN.  DTN is to move
>> information over, in some cases, long propagation delays, and in =
other
>> cases, systems that are normally disconnected, or both.  There is a
>> thought that, because
>> DTNs have to store content, that same storage could be used by the =
ICN.
>> However, trying to combine the two, IMHO, will complicate matters for
>> both ICN and DTN and hold back both.  But, that is just my opinion.
>>=20
>>=20
>> Regardless, I don't think you can compare "which one is better in the =
ad
>> hoc vehicular environment" because they are designed to do two =
different
>> things.  Perhaps the better question is "Do I need DTN for ad hoc
>> vehicular networks or will ICN suffice?"
>> What is your concept of operations?  Are you operating where 4G
>> connectivity is available?  Do i have a multi-hop DTN?  If not, DTN =
is
>> likely to buy you nothing.
>>=20
>> - Will
>>=20
>>=20
>>=20
>> On Sep 14, 2012, at 8:17 AM, Ngoc Thanh Dinh wrote:
>>=20
>>=20
>> Thank you very much!
>> Yes. I think so, ICN could cover many scenarios of DTN.
>> But to compare them in one experiment to show which one is better in =
the
>> ad-hocvehicular environment, it seems many consideration.
>> Do you have any opinion to compare performance of two approaches? on
>> delay, network resource consumption, overhead or other one?
>> I want to show that ICN is better one in the vehicular environment. =
but
>> in the partition case or in high density case, it still seems =
confusing
>> to compare.
>> Hope to have your discussion!!!
>>=20
>> thank you very much!
>>=20
>> 2012/9/14 Dirk Trossen <dirk.trossen@cl.cam.ac.uk>
>>=20
>> Let me bring back DY's email from a few days ago, pointing at Kevin
>> Fall's presentation (I included the link again, DY also sent the
>> presentation itself):
>>=20
>>  http://fif.kr/gfi-summit/11/program.htm
>>=20
>> It shows that there's more to ICN and DTN commonalities than one =
might
>> think originally
>>=20
>> Dirk
>>=20
>> On 14 Sep 2012, at 12:42, Pedro Mart=EDnez Juli=E1 wrote:
>>=20
>>> 14/09/12 08:07, Ngoc Thanh Dinh:
>>>> Dear Every one,
>>>>=20
>>>> We are discussing about the benefit of ICN and DTN in global future
>>>> internet conference these days.
>>>> I am researching in ICN and DTN in vehicular network. There are =
some
>>>> papers
>>>> in both topics for vehicular network,
>>>> both of them support naming, caching, store-and-forward,...while =
DTN
>>>> has a
>>>> longer history than ICN
>>>> Could you give me your opinions about what is benefit of ICN =
compared
>>>> to
>>>> DTN?
>>>> Did anyone make a comparison between ICN and DTN?
>>>>=20
>>>=20
>>> Conceptually, they have very different objectives. However, ICN can
>>> cover some (or even many) DTN use cases. The main difference is that =
ICN
>>> manages named or uniquely identified information while DTN is
>>> concentrated in the communication. For example, and
>> correct me if I'm wrong, ICN permits to deliver the same information
>> piece to different clients requesting it without involving the
>> information source but in DTN is the sender who decides the =
destination
>> of a message.
>>>=20
>>>> Thank you very much!
>>>>=20
>>>=20
>>> Regards,
>>> Pedro
>>>=20
>>> --
>>> Pedro Martinez-Julia
>>> Department of Communication and Information Engineering
>>> Faculty of Computer Science
>>> University of Murcia
>>> Email: pedromj@um.es
>>> ---------------------------------------------------------
>>> *** Entia non sunt multiplicanda praeter necessitatem ***
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Dinh Ngoc Thanh | PhD candidate
>> Soongsil university - Seoul Korea
>> M: (+82) 010 4197 1879
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> ******************************
>> William D. Ivancic
>> Phone 216-433-3494
>> Fax 216-433-8705
>> Networking Lab 216-433-2620
>> Mobile 440-503-4892
>> http://roland.grc.nasa.gov/~ivancic
>> <http://roland.grc.nasa.gov/%7Eivancic>
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Dinh Ngoc Thanh | PhD candidate
>> Soongsil university - Seoul Korea
>> M: (+82) 010 4197 1879
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> ******************************
>> William D. Ivancic
>> Phone 216-433-3494
>> Fax 216-433-8705
>> Networking Lab 216-433-2620
>> Mobile 440-503-4892
>> http://roland.grc.nasa.gov/~ivancic
>> <http://roland.grc.nasa.gov/%7Eivancic>
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Dinh Ngoc Thanh | PhD candidate
>> Soongsil university - Seoul Korea
>> M: (+82) 010 4197 1879
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.orghttps://www.irtf.org/mailman/listinfo/icnrg
>>=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=_781115B5-0400-4940-A4A0-C24479EBC6A3
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; =
">Hello<div><br></div><div>Just saw this email now (yes, I've a email =
delay tolerant system :) ), and I think that Ignacio is making an =
important point.. The DTN and ICN research/work started from different =
perspectives. =46rom the DTN side, we have a standardization work aiming =
to devise one architecture. =46rom the ICN side we started by having =
different projects that follow the same generic ICN principles, but any =
of which we can be stamped as THE ICN reference. So, from an =
architectural point of view, this discussion is useless, and should be =
resumed after the ICNRG come up with some standard track =
proposal.</div><div><br></div><div>=46rom a general perspective, we can =
only try to analyze which paradigm brings more benefits to the end user =
(from whom does not matter how the engine works). Lets look at two =
aspects/requirements to start with:</div><div><br></div><div>a) Access =
to information: considering that the highest percentage of Internet =
traffic is data oriented (r.g. google, facebook, amazon, ebay, ...) and =
not point-to-point (e.g. VoIP) a pull model like ICN in which the user =
"just" need to ask the network to provide the requested data seems more =
beneficial.</div><div><br></div><div>b) Operation in challenge =
scenarios: if we look at the edges of the Internet core (beyond the =
cellular, wireless, etc end points) we need a architecture capable to =
support data exchange even when there is no end-to-end path between any =
pair of nodes, or when end-to-end paths have ver long delays. The DTN =
arch was created for this scenario, based on persistent storage and the =
creation of a chain of TCP links. But since persistent storage is also a =
key element of ICN and since ICN is agnostic of communication links, I =
would say that ICN is a concept that can be applied to the same =
scenarios that DTN was initial designed to.</div><div><br></div><div>It =
is with this goal in mind (bring ICN concept to the DTN world) that we =
at SITILabs (<a =
href=3D"http://siti.ulusofona.pt">http://siti.ulusofona.pt</a>) are =
working on an modular architecture called ICON (Information-centric =
Opportunistic Networking) that started from the basic CCN concepts and =
includes a social-aware opportunistic routing protocol. For now the =
major goal is more software engineer oriented: we created an easy to =
install and use platform that runs in any personal device (windows, =
android, iphone, linux) and is being adjusted to embedded devices. For =
more info check:&nbsp;<a =
href=3D"http://siti.ulusofona.pt/index.php/teechnology/182-icon-dtn-amazon=
-project">http://siti.ulusofona.pt/index.php/teechnology/182-icon-dtn-amaz=
on-project</a></div><div><br></div><div>So, IMO it is at all possible =
for a future ICNRG architecture proposal to be applied to any DTN =
scenario. It will all depend upon the direction/priorities that the =
ICNRG will set. Then we just need to show that such arch is also useful =
to set up point-to-point communications (see initial conceptual profs, =
as the 2009 VoCCN paper from Van Jacabson et al) =
:-).</div><div><br></div><div>Cheers</div><div>Paulo</div><div><br></div><=
div><br></div><div><div><div>On Sep 17, 2012, at 7:42 PM, &lt;<a =
href=3D"mailto:Ignacio.Solis@parc.com">Ignacio.Solis@parc.com</a>&gt; =
&lt;<a =
href=3D"mailto:Ignacio.Solis@parc.com">Ignacio.Solis@parc.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Having worked on "all-of-the-above" I can say that =
the differences are not<br>big. &nbsp;I currently advise Preston and =
Rajesh on CBMEN (Content-Based Mobile<br>Edge Networks) for DARPA, and I =
Worked on adding ICN capabilities to<br>SPINDLE.<br><br>The differences =
between the two "architectures" are becoming<br>smaller/fewer. =
&nbsp;&nbsp;&nbsp;Kevin's slides from Dagstuhl summarize what the =
group<br>talked about in terms of ICN/DTN.<br><br>One thing to note is =
that to some degree, both ICN and DTN refer to a<br>group of projects or =
general architectures. &nbsp;=46rom my point of view, the<br>DTN =
community is relatively unified in the sense that it follows a =
few<br>standards/conventions &nbsp;(RFC 5050?). &nbsp;=46rom the ICN =
perspective we have a<br>situation where we're not unified at all. The =
different projects have made<br>different tradeoffs.<br><br>Due to this =
it is probably better to compare DTN to NetInf, PURSUIT, CCN,<br>etc. =
&nbsp;&nbsp;Depending on your application you might find that more than =
one has<br>the features that you want. &nbsp;Potentially you might want =
to choose one due<br>to code maturity/production-level &nbsp;or =
&nbsp;due to future expandability.<br><br>I would suggest that you think =
of the problem you're trying to solve,<br>figure out the must-have and =
nice-to-have features and see which<br>architecture/project works best =
for you based on:<br><br>* what is currently implement in the code =
(alpha, beta, production)<br>* what is the planned features in the =
short, medium and long-term<br>* what is technically possible with the =
architecture &nbsp;&nbsp;(that might never<br>get done unless you do it =
yourself)<br><br><br>After all, you can do everything over IP given =
enough services on top.<br><br>Nacho<br><br><br><br><br><br>-- =
<br>Ignacio Solis<br>Networking Area Manager<br>Palo Alto Research =
Center<br>+1(650)812-4458<br><br><br><br><br><br><br>On 9/14/12 4:59 PM, =
"Elwyn Davies" &lt;<a =
href=3D"mailto:elwynd@folly.org.uk">elwynd@folly.org.uk</a>&gt; =
wrote:<br><br><br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">The US Army was (and as far as I know still are) very =
interested in DTN<br></blockquote><blockquote type=3D"cite">as a way to =
improve throughput in what is essentially a vehicular =
ad-hoc<br></blockquote><blockquote type=3D"cite">network. &nbsp;Some =
years ago there were trials of the BBN-lead DARPA =
DTN<br></blockquote><blockquote type=3D"cite">projects (SPINDLE) =
involving vehicles driving<br></blockquote><blockquote type=3D"cite">round=
 a track and comparing the performance of DTN and basic TCP. At =
one<br></blockquote><blockquote type=3D"cite">point in time there was a =
comprehensive presentation (by Preston =
Marshall<br></blockquote><blockquote type=3D"cite">if my memory is =
correct) of the results of this trial available on =
the<br></blockquote><blockquote type=3D"cite">web, but it seems to have =
been withdrawn<br></blockquote><blockquote type=3D"cite">- I failed to =
keep a copy of it and attempts to get it again have =
drawn<br></blockquote><blockquote type=3D"cite">a blank. &nbsp;There is =
some discussion of this work in the state of the =
art<br></blockquote><blockquote type=3D"cite">document that I wrote for =
the N4C project about three years ago. =
&nbsp;This<br></blockquote><blockquote type=3D"cite">can be downloaded =
from<br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://www.n4c.eu/Download/n4c-wp2-012-state-of-the-art-101.pdf">h=
ttp://www.n4c.eu/Download/n4c-wp2-012-state-of-the-art-101.pdf</a>.<br></b=
lockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">A Google search for something like 'us army dtn tcp =
vehicles' throws up a<br></blockquote><blockquote type=3D"cite">whole =
raft of interesting references including mentions of the =
CONDOR<br></blockquote><blockquote type=3D"cite">project and other stuff =
that is going on in vehicular ad hoc =
networking.<br></blockquote><blockquote type=3D"cite">There is brief =
mention of CCN related topics.<br></blockquote><blockquote =
type=3D"cite">An interesting report of more recent and complex trials =
can be found in<br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://trs-new.jpl.nasa.gov/dspace/bitstream/2014/41752/1/JPL%20Pu=
b%20D-65">http://trs-new.jpl.nasa.gov/dspace/bitstream/2014/41752/1/JPL%20=
Pub%20D-65</a><br></blockquote><blockquote =
type=3D"cite">838.pdf<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">There is also =
an interestng perspective on combining ICN and DTN in =
this<br></blockquote><blockquote =
type=3D"cite">talk...<br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://rajesh-krishnan.com/talks/rkrishnan-coin-neu07.pdf">http://=
rajesh-krishnan.com/talks/rkrishnan-coin-neu07.pdf</a><br></blockquote><bl=
ockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Regards,<br></blockquote><blockquote =
type=3D"cite">Elwyn<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On 14/09/12 =
15:02, Ngoc Thanh Dinh wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thank you very =
much!<br></blockquote><blockquote type=3D"cite">That is one reason we =
want to implement ICN in ad-hoc vehicular =
network.<br></blockquote><blockquote type=3D"cite">but we have to =
demonstrate it, before implementation, we have to make =
a<br></blockquote><blockquote type=3D"cite">clear =
benefits.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In high =
density, high mobility case, and constraint information =
(delay<br></blockquote><blockquote type=3D"cite">time and location), do =
you think that DTN will give a not good<br></blockquote><blockquote =
type=3D"cite">performance? (even increase delay compared to other). and =
ICN may be<br></blockquote><blockquote type=3D"cite">better because ICN =
could support automatic ifnormation<br></blockquote><blockquote =
type=3D"cite">searching and distributtion (matching interest and data) =
?<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">We should make =
a clear benefit to select which one is more suitable =
for<br></blockquote><blockquote type=3D"cite">this =
scenario.<br></blockquote><blockquote type=3D"cite">Hope to have your =
discussion and thank you very much!<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">2012/9/14 =
Ivancic, William D. (GRC-RHN0)<br></blockquote><blockquote =
type=3D"cite">&lt;<a =
href=3D"mailto:william.d.ivancic@nasa.gov">william.d.ivancic@nasa.gov</a>&=
gt;<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">DTN, as is, only temporarily caches a bundle until it =
passes it on (in<br></blockquote><blockquote type=3D"cite">general, but =
is implementation &nbsp;and routing specific). &nbsp;DTN, as is, =
does<br></blockquote><blockquote type=3D"cite">not know what is inside =
the bundle (although, one could come up with<br></blockquote><blockquote =
type=3D"cite">something<br></blockquote><blockquote type=3D"cite">special =
to enable this). &nbsp;&nbsp;ICN ensures that the information is cached =
at<br></blockquote><blockquote type=3D"cite">the appropriate places and =
is available for ICN users to obtain. DTN<br></blockquote><blockquote =
type=3D"cite">could be used to get the information to the ICN cache =
(complementary).<br></blockquote><blockquote type=3D"cite">But, for DTN =
to be used as ICN, you have to<br></blockquote><blockquote =
type=3D"cite">basically design ICN into DTN. DTN, as is, is complicated =
enough.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- =
Will<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Sep 14, =
2012, at 8:52 AM, Ngoc Thanh Dinh wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Yes. DTN could =
be a scenario which could be covered in ICN.<br></blockquote><blockquote =
type=3D"cite">I am analyzing on the case of exchanging information among =
vehicles in<br></blockquote><blockquote type=3D"cite">the ad-hoc =
vehicular network scenarios without =
infrastructure.<br></blockquote><blockquote type=3D"cite">in case of =
long delay or disruption (main purpose of DTN), i think =
the<br></blockquote><blockquote type=3D"cite">same performance could be =
implement based on information object and<br></blockquote><blockquote =
type=3D"cite">caching of ICN.<br></blockquote><blockquote =
type=3D"cite">but in the high density and high mobility case of vehicle, =
do you think<br></blockquote><blockquote type=3D"cite">DTN will achieve =
a lower performance? (e.g. higher delay)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I want to =
listen your discussion about the points that<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">class 1: for =
information service which delayed or lost information =
does<br></blockquote><blockquote type=3D"cite">not compromise safety or =
render the application useless (e.g. weather<br></blockquote><blockquote =
type=3D"cite">reports,...) --&gt; DTN capabilities can improve the =
quality in this case by<br></blockquote><blockquote =
type=3D"cite">increasing the message delivery and =
reducing<br></blockquote><blockquote type=3D"cite">delays in challenging =
scenarios.<br></blockquote><blockquote type=3D"cite">And with ICN, we =
could also achieve this improvement, even more, based =
on<br></blockquote><blockquote type=3D"cite">naming object, not =
destination host.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">class 2: for =
delayed information may compromise safety, application =
may<br></blockquote><blockquote type=3D"cite">require realtime =
communication --&gt; DTN may not improve the quality =
of<br></blockquote><blockquote type=3D"cite">this =
case.<br></blockquote><blockquote type=3D"cite">But ICN may make an =
improvement? (based on information object =
caching)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Listen to your =
discussion and thank you very much!!!<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">2012/9/14 =
Ivancic, William D. (GRC-RHN0)<br></blockquote><blockquote =
type=3D"cite">&lt;<a =
href=3D"mailto:william.d.ivancic@nasa.gov">william.d.ivancic@nasa.gov</a>&=
gt;<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite">DTN and ICN may be complementary. &nbsp;DTN is not ICN. =
&nbsp;DTN is to move<br></blockquote><blockquote type=3D"cite">information=
 over, in some cases, long propagation delays, and in =
other<br></blockquote><blockquote type=3D"cite">cases, systems that are =
normally disconnected, or both. &nbsp;There is =
a<br></blockquote><blockquote type=3D"cite">thought that, =
because<br></blockquote><blockquote type=3D"cite">DTNs have to store =
content, that same storage could be used by the =
ICN.<br></blockquote><blockquote type=3D"cite">However, trying to =
combine the two, IMHO, will complicate matters =
for<br></blockquote><blockquote type=3D"cite">both ICN and DTN and hold =
back both. &nbsp;But, that is just my =
opinion.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Regardless, I =
don't think you can compare "which one is better in the =
ad<br></blockquote><blockquote type=3D"cite">hoc vehicular environment" =
because they are designed to do two =
different<br></blockquote><blockquote type=3D"cite">things. =
&nbsp;Perhaps the better question is "Do I need DTN for ad =
hoc<br></blockquote><blockquote type=3D"cite">vehicular networks or will =
ICN suffice?"<br></blockquote><blockquote type=3D"cite"> What is your =
concept of operations? &nbsp;Are you operating where =
4G<br></blockquote><blockquote type=3D"cite">connectivity is available? =
&nbsp;Do i have a multi-hop DTN? &nbsp;If not, DTN =
is<br></blockquote><blockquote type=3D"cite">likely to buy you =
nothing.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">- =
Will<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Sep 14, =
2012, at 8:17 AM, Ngoc Thanh Dinh wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Thank you very =
much!<br></blockquote><blockquote type=3D"cite">Yes. I think so, ICN =
could cover many scenarios of DTN.<br></blockquote><blockquote =
type=3D"cite">But to compare them in one experiment to show which one is =
better in the<br></blockquote><blockquote type=3D"cite">ad-hocvehicular =
environment, it seems many consideration.<br></blockquote><blockquote =
type=3D"cite">Do you have any opinion to compare performance of two =
approaches? on<br></blockquote><blockquote type=3D"cite">delay, network =
resource consumption, overhead or other one?<br></blockquote><blockquote =
type=3D"cite">I want to show that ICN is better one in the vehicular =
environment. but<br></blockquote><blockquote type=3D"cite">in the =
partition case or in high density case, it still seems =
confusing<br></blockquote><blockquote type=3D"cite">to =
compare.<br></blockquote><blockquote type=3D"cite">Hope to have your =
discussion!!!<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">thank you very =
much!<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">2012/9/14 Dirk =
Trossen &lt;<a =
href=3D"mailto:dirk.trossen@cl.cam.ac.uk">dirk.trossen@cl.cam.ac.uk</a>&gt=
;<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Let me bring back DY's email from a few days ago, pointing =
at Kevin<br></blockquote><blockquote type=3D"cite">Fall's presentation =
(I included the link again, DY also sent the<br></blockquote><blockquote =
type=3D"cite">presentation itself):<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> &nbsp;<a =
href=3D"http://fif.kr/gfi-summit/11/program.htm">http://fif.kr/gfi-summit/=
11/program.htm</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It shows that =
there's more to ICN and DTN commonalities than one =
might<br></blockquote><blockquote type=3D"cite">think =
originally<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Dirk<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On 14 Sep 2012, =
at 12:42, Pedro Mart=EDnez Juli=E1 wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">14/09/12 08:07, Ngoc Thanh =
Dinh:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Dear Every =
one,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">We are =
discussing about the benefit of ICN and DTN in global =
future<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">internet=
 conference these =
days.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">I am =
researching in ICN and DTN in vehicular network. There are =
some<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">papers<br></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">in =
both topics for vehicular =
network,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">both =
of them support naming, caching, store-and-forward,...while =
DTN<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">has =
a<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">longer =
history than ICN<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Could =
you give me your opinions about what is benefit of ICN =
compared<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">to<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">DTN?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Did =
anyone make a comparison between ICN and =
DTN?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Conceptually, they have very =
different objectives. However, ICN =
can<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">cover some (or even many) DTN use cases. The main =
difference is that ICN<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">manages named or uniquely =
identified information while DTN =
is<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">concentrated in the communication. For example, =
and<br></blockquote></blockquote><blockquote type=3D"cite">correct me if =
I'm wrong, ICN permits to deliver the same =
information<br></blockquote><blockquote type=3D"cite">piece to different =
clients requesting it without involving the<br></blockquote><blockquote =
type=3D"cite">information source but in DTN is the sender who decides =
the destination<br></blockquote><blockquote type=3D"cite">of a =
message.<br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Thank =
you very much!<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Pedro<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">--<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Pedro =
Martinez-Julia<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Department of Communication and =
Information Engineering<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Faculty of Computer =
Science<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">University of =
Murcia<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Email: <a =
href=3D"mailto:pedromj@um.es">pedromj@um.es</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote =
type=3D"cite">---------------------------------------------------------<br=
></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">*** Entia non sunt multiplicanda praeter necessitatem =
***<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-- =
<br></blockquote><blockquote type=3D"cite">Dinh Ngoc Thanh | PhD =
candidate<br></blockquote><blockquote type=3D"cite">Soongsil university =
- Seoul Korea<br></blockquote><blockquote type=3D"cite">M: (+82) 010 =
4197 1879<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">******************************<br></blockquote><blockquote =
type=3D"cite">William D. Ivancic<br></blockquote><blockquote =
type=3D"cite">Phone 216-433-3494<br></blockquote><blockquote =
type=3D"cite">Fax 216-433-8705<br></blockquote><blockquote =
type=3D"cite">Networking Lab 216-433-2620<br></blockquote><blockquote =
type=3D"cite">Mobile 440-503-4892<br></blockquote><blockquote =
type=3D"cite"><a =
href=3D"http://roland.grc.nasa.gov/~ivancic">http://roland.grc.nasa.gov/~i=
vancic</a><br></blockquote><blockquote type=3D"cite">&lt;<a =
href=3D"http://roland.grc.nasa.gov/%7Eivancic">http://roland.grc.nasa.gov/=
%7Eivancic</a>&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-- =
<br></blockquote><blockquote type=3D"cite">Dinh Ngoc Thanh | PhD =
candidate<br></blockquote><blockquote type=3D"cite">Soongsil university =
- Seoul Korea<br></blockquote><blockquote type=3D"cite">M: (+82) 010 =
4197 1879<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">******************************<br></blockquote><blockquote =
type=3D"cite">William D. Ivancic<br></blockquote><blockquote =
type=3D"cite">Phone 216-433-3494<br></blockquote><blockquote =
type=3D"cite">Fax 216-433-8705<br></blockquote><blockquote =
type=3D"cite">Networking Lab 216-433-2620<br></blockquote><blockquote =
type=3D"cite">Mobile 440-503-4892<br></blockquote><blockquote =
type=3D"cite"><a =
href=3D"http://roland.grc.nasa.gov/~ivancic">http://roland.grc.nasa.gov/~i=
vancic</a><br></blockquote><blockquote type=3D"cite">&lt;<a =
href=3D"http://roland.grc.nasa.gov/%7Eivancic">http://roland.grc.nasa.gov/=
%7Eivancic</a>&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-- =
<br></blockquote><blockquote type=3D"cite">Dinh Ngoc Thanh | PhD =
candidate<br></blockquote><blockquote type=3D"cite">Soongsil university =
- Seoul Korea<br></blockquote><blockquote type=3D"cite">M: (+82) 010 =
4197 1879<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">icnrg mailing =
list<br></blockquote><blockquote type=3D"cite">icnrg@<a =
href=3D"irtf.orghttps://www.irtf.org/mailman/listinfo/icnrg">irtf.orghttps=
://www.irtf.org/mailman/listinfo/icnrg</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><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></body></html>=

--Apple-Mail=_781115B5-0400-4940-A4A0-C24479EBC6A3--

From lars@netapp.com  Wed Nov 14 07:20:10 2012
Return-Path: <lars@netapp.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 2551C21F8413 for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 07:20:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.344
X-Spam-Level: 
X-Spam-Status: No, score=-10.344 tagged_above=-999 required=5 tests=[AWL=0.255, BAYES_00=-2.599, 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 D1oehXzekrXj for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 07:20:08 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 488DC21F8201 for <icnrg@irtf.org>; Wed, 14 Nov 2012 07:20:07 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.83,251,1352102400";  d="p7s'?scan'208";a="710054591"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 14 Nov 2012 07:20:06 -0800
Received: from vmwexceht01-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id qAEFK5cf000627; Wed, 14 Nov 2012 07:20:05 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0318.001; Wed, 14 Nov 2012 07:20:04 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Paulo Mendes <paulo.mendes@ulusofona.pt>
Thread-Topic: [icnrg] Benefit of information centric network (ICN) compared to DTN in wireless communication
Thread-Index: AQHNwno7pDWZQyEUM0WYYO3KoKC3bpfp+DGA
Date: Wed, 14 Nov 2012 15:18:34 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt>
In-Reply-To: <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_FA3A46F4-734A-4D97-B230-0A1986404781"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<icnrg@irtf.org>" <icnrg@irtf.org>, "<elwynd@folly.org.uk>" <elwynd@folly.org.uk>, "<ngocthanhdinh@gmail.com>" <ngocthanhdinh@gmail.com>, "<Ignacio.Solis@parc.com>" <Ignacio.Solis@parc.com>, "<stephen.farrell@cs.tcd.ie>" <stephen.farrell@cs.tcd.ie>, "<william.d.ivancic@nasa.gov>" <william.d.ivancic@nasa.gov>
Subject: Re: [icnrg] Benefit of information centric network (ICN) compared	to DTN in wireless communication
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, 14 Nov 2012 15:20:10 -0000

--Apple-Mail=_FA3A46F4-734A-4D97-B230-0A1986404781
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On Nov 14, 2012, at 16:10, Paulo Mendes <paulo.mendes@ulusofona.pt> =
wrote:
> =46rom the DTN side, we have a standardization work aiming to devise =
one architecture. =46rom the ICN side we started by having different =
projects that follow the same generic ICN principles, but any of which =
we can be stamped as THE ICN reference. So, from an architectural point =
of view, this discussion is useless, and should be resumed after the =
ICNRG come up with some standard track proposal.

just to clarify: IRTF research groups do not produce standards. The =
DTNRG isn't, and the ICNRG won't either. It's also not a goal to declare =
one of the current architecture proposals a "winner".

Lars=

--Apple-Mail=_FA3A46F4-734A-4D97-B230-0A1986404781
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTExNDE1MjAwNFowIwYJKoZIhvcNAQkEMRYEFJMG
gqhgq+DZWGn4Mxc7hx5b5iF/MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBADO6RSyg
Wydje1a4tYFY6Qw2Bc0XzBVaZH9gyD3qHmtJHOPSdQb7MLF07fy6aWYrFrMOtGLWV/ufleAjfVMb
OVevZ0P+UcMnG1vOOUasGJDFKGO5P65h1vbDVE5UDQg/5kcyI+EIoW+nJpQIm8p9kGeM/9gV1nRh
+/r9Vr7K+ha0SJFG0s0gFoCxMvcdNdTI79gbiayHqaRoAXdDgJ0UHSSeEudzWvsMa+/+wxL2DZKi
Tb8UD1LZ5aM+MdKvfKu/EUNzHOQG6aaDak8z9+FKRNKgX7a/BF4fwMdmwXJUJ1XwimUsfq/z5b76
mu0Nby/c7NowuXu+z8ABPcGG+DRoGKkAAAAAAAA=

--Apple-Mail=_FA3A46F4-734A-4D97-B230-0A1986404781--

From paulo.mendes@ulusofona.pt  Wed Nov 14 10:47:52 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 23DCA21F8626 for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 10:47:52 -0800 (PST)
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 u4UajlADAJxT for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 10:47:51 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id DC69021F8622 for <icnrg@irtf.org>; Wed, 14 Nov 2012 10:47:50 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id x43so319242wey.13 for <icnrg@irtf.org>; Wed, 14 Nov 2012 10:47:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:reply-to:to:cc:subject:x-mailer:references:in-reply-to :content-type:date:message-id:mime-version:x-gm-message-state; bh=dZctH57Q/AeLnubvURGUw9jm0Kx5h26gHSrJYx844Xs=; b=IFSfsH1DCzdGAvF1YveZAm+yqfoSj5UndMOaexosmksMF6G7uhSi5sYReCCGz1G2VS fmT6306MwsY+j8e+dvxo+lD3TTefbdAcW0a3VE0OJc2o3xsc5AJ+d171ZO3dVusqfmZT Rqh0yh0bsAUNYnzKC5gzhZ4vurQ2VXb0MorkXZKbPb9v4e0f40VYmRynq59otMMmfUYb ZhlCh/3SerlpLBCjciUQXQ2kv5cUXtmIHG8P1gZVwB6QLv6Aagf54GHG7sTjGhIu+U0B eEvxAuVNEXiA9KgIbxykt3yJT6HUzId97fYzTcmgVwa4/6vYmXSkGuZKhlpVHacDSU0m qshA==
Received: by 10.180.87.40 with SMTP id u8mr27537615wiz.3.1352918869719; Wed, 14 Nov 2012 10:47:49 -0800 (PST)
Received: from [10.67.66.43] ([88.214.165.43]) by mx.google.com with ESMTPS id w5sm3696350wiz.10.2012.11.14.10.47.38 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 10:47:39 -0800 (PST)
From: Paulo <paulo.mendes@ulusofona.pt>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Modest 3.2
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: multipart/alternative; boundary="=-ymF9lmHM1vhL7IGrCi8k"
Date: Wed, 14 Nov 2012 18:46:31 +0000
Message-Id: <1352918791.2935.5.camel@Nokia-N900-42-11>
Mime-Version: 1.0
X-Gm-Message-State: ALoCoQlqF+mss76I5PRGtd4RLHloEvBdDateVVxaCexL9Y3MzaDQoEAEcPvqSK7XqE5dFr/q/efB
Cc: icnrg@irtf.org, elwynd@folly.org.uk, ngocthanhdinh@gmail.com, Ignacio.Solis@parc.com, stephen.farrell@cs.tcd.ie, william.d.ivancic@nasa.gov
Subject: Re: [icnrg] Benefit of information centric network (ICN) compared	to DTN in wireless communication
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Paulo <paulo.mendes@ulusofona.pt>
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, 14 Nov 2012 18:47:52 -0000

--=-ymF9lmHM1vhL7IGrCi8k
Content-Type: text/plain; charset=utf-8
Content-ID: <1352918790.2935.2.camel@Nokia-N900-42-11>
Content-Transfer-Encoding: 7bit

Hi Lars

it is well known the IRTF does not produce standards. The word "standard" was not used in a proper way in my email. The difference that I want to highlight is that on the DTN side there is a common concensus about a general arch, which we can clearly describe, while that is not a scenario that we can find in the ICN side.
I also didn`t say that ICNRG should declare a winner among the existing proposals (ccn, netinf,...). Not at all. Does are just related work. But if we want to clearly compare DTN with ICN, we need to create a common understanding about the general characteristics of an ICN arch within ICNRG. This may be a very usefull contribution from IRTF (bring or at least try to create consensus). 

Cheers
Paulo
-- 
@N900
----------------------------------
Paulo Mendes
Sientific Director of the Informatic Systems and Tecnology Labs (SITI Labs)
Http://siti.ulusofona.pt 

----- Mensagem original -----
> Hi,
> 
> On Nov 14, 2012, at 16:10, Paulo Mendes <paulo.mendes@ulusofona.pt>
> wrote:
> > From the DTN side, we have a standardization work aiming to devise one
> > architecture. From the ICN side we started by having different
> > projects that follow the same generic ICN principles, but any of which
> > we can be stamped as THE ICN reference. So, from an architectural
> > point of view, this discussion is useless, and should be resumed after
> > the ICNRG come up with some standard track proposal.
> 
> just to clarify: IRTF research groups do not produce standards. The
> DTNRG isn't, and the ICNRG won't either. It's also not a goal to declare
> one of the current architecture proposals a "winner".
> 
> Lars


--=-ymF9lmHM1vhL7IGrCi8k
Content-Type: text/html; charset=utf-8
Content-ID: <1352918790.2935.4.camel@Nokia-N900-42-11>
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="generator" content="Osso Notes">
    <title></title></head>
<body>
<p>Hi Lars
<br>
<br>it is well known the IRTF does not produce standards. The word "standard" was not used in a proper way in my email. The difference that I want to highlight is that on the DTN side there is a common concensus about a general arch, which we can clearly describe, while that is not a scenario that we can find in the ICN side.
<br>I also didn`t say that ICNRG should declare a winner among the existing proposals (ccn, netinf,...). Not at all. Does are just related work. But if we want to clearly compare DTN with ICN, we need to create a common understanding about the general characteristics of an ICN arch within ICNRG. This may be a very usefull contribution from IRTF (bring or at least try to create consensus). 
<br>
<br>Cheers
<br>Paulo
<br><font color="#7acfff">-- </font>
<br><font color="#7acfff">@N900</font>
<br><font color="#7acfff">----------------------------------</font>
<br><font color="#7acfff">Paulo Mendes</font>
<br><font color="#7acfff">Sientific Director of the Informatic Systems and Tecnology Labs (SITI Labs)</font>
<br><font color="#7acfff"><a href="Http://siti.ulusofona.pt">Http://siti.ulusofona.pt</a> </font>
<br>
<br>----- Mensagem original -----
<br>&gt; Hi,
<br>&gt; 
<br>&gt; On Nov 14, 2012, at 16:10, Paulo Mendes &lt;<a href="mailto:paulo.mendes@ulusofona.pt">paulo.mendes@ulusofona.pt</a>&gt;
<br>&gt; wrote:
<br>&gt; &gt; From the DTN side, we have a standardization work aiming to devise one
<br>&gt; &gt; architecture. From the ICN side we started by having different
<br>&gt; &gt; projects that follow the same generic ICN principles, but any of which
<br>&gt; &gt; we can be stamped as THE ICN reference. So, from an architectural
<br>&gt; &gt; point of view, this discussion is useless, and should be resumed after
<br>&gt; &gt; the ICNRG come up with some standard track proposal.
<br>&gt; 
<br>&gt; just to clarify: IRTF research groups do not produce standards. The
<br>&gt; DTNRG isn't, and the ICNRG won't either. It's also not a goal to declare
<br>&gt; one of the current architecture proposals a "winner".
<br>&gt; 
<br>&gt; Lars
<br><br></p>
</body>
</html>

--=-ymF9lmHM1vhL7IGrCi8k--


From l.wood@surrey.ac.uk  Wed Nov 14 14:04:11 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 7ACB821F881B for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 14:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.358
X-Spam-Level: 
X-Spam-Status: No, score=-5.358 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, 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 ycWFtPZyDWkA for <icnrg@ietfa.amsl.com>; Wed, 14 Nov 2012 14:04:09 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5D43A21F8819 for <icnrg@irtf.org>; Wed, 14 Nov 2012 14:04:09 -0800 (PST)
Received: from [195.245.230.131:14657] by server-1.bemta-3.messagelabs.com id EF/B1-12169-75514A05; Wed, 14 Nov 2012 22:04:07 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1352930646!28160915!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.8; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32086 invoked from network); 14 Nov 2012 22:04:07 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 14 Nov 2012 22:04:07 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.240]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 14 Nov 2012 22:04:06 +0000
From: <l.wood@surrey.ac.uk>
To: <lars@netapp.com>, <paulo.mendes@ulusofona.pt>
Date: Wed, 14 Nov 2012 21:59:55 +0000
Thread-Topic: [icnrg] Benefit of information centric network (ICN)	compared to DTN in wireless communication
Thread-Index: AQHNwno7pDWZQyEUM0WYYO3KoKC3bpfp+DGA///pnBM=
Message-ID: <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt>, <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com>
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, elwynd@folly.org.uk, ngocthanhdinh@gmail.com, Ignacio.Solis@parc.com, stephen.farrell@cs.tcd.ie, william.d.ivancic@nasa.gov
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared	to DTN in wireless communication
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, 14 Nov 2012 22:04:11 -0000

Didn't the dtnrg declare the bundle protocol proposal the winner by fiat in=
 its charter?

Bad start to a research group, but there you go. Not so much a goal, as an =
own goal.

If icnrg did the same thing, the rewards of illusory progress could be rece=
ived in the short term.

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


________________________________________
From: icnrg-bounces@irtf.org [icnrg-bounces@irtf.org] On Behalf Of Eggert, =
Lars [lars@netapp.com]
Sent: 14 November 2012 15:18
To: Paulo Mendes
Cc: <icnrg@irtf.org>; <elwynd@folly.org.uk>; <ngocthanhdinh@gmail.com>; <Ig=
nacio.Solis@parc.com>; <stephen.farrell@cs.tcd.ie>; <william.d.ivancic@nasa=
.gov>
Subject: Re: [icnrg] Benefit of information centric network (ICN)       com=
pared        to DTN in wireless communication

Hi,

On Nov 14, 2012, at 16:10, Paulo Mendes <paulo.mendes@ulusofona.pt> wrote:
> From the DTN side, we have a standardization work aiming to devise one ar=
chitecture. From the ICN side we started by having different projects that =
follow the same generic ICN principles, but any of which we can be stamped =
as THE ICN reference. So, from an architectural point of view, this discuss=
ion is useless, and should be resumed after the ICNRG come up with some sta=
ndard track proposal.

just to clarify: IRTF research groups do not produce standards. The DTNRG i=
sn't, and the ICNRG won't either. It's also not a goal to declare one of th=
e current architecture proposals a "winner".

Lars

From paulo.mendes@ulusofona.pt  Thu Nov 15 00:05:39 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 8C3B021F875E for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2012 00:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.876
X-Spam-Level: 
X-Spam-Status: No, score=-0.876 tagged_above=-999 required=5 tests=[AWL=1.482,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
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 s2XNV1HbOotO for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2012 00:05:38 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id B4A3821F858F for <icnrg@irtf.org>; Thu, 15 Nov 2012 00:05:37 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id x43so543094wey.13 for <icnrg@irtf.org>; Thu, 15 Nov 2012 00:05:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:reply-to:to:cc:subject:x-mailer:references:in-reply-to :content-type:date:message-id:mime-version:x-gm-message-state; bh=S3B3jR6Q4Uk08XQttk3HyIk8+tqtJ0uMSbMv8pzFFkc=; b=ECxFnkdED0HlapY46etioGh9VGJ61HoVKhd4tqPX5Me5l8Ndimz34bMCbiOxXU6RKo q4rT9UF8nC76BdrSaBrCd4AFE4cftHwfDjhI2F1YkQ21EIB9ZzqLevRHJcLYINVQwTRg PZfmIRh9sFNELo9NUArPQZjIBHNZk+/YfgzjmRqLET3aE+Mr85+nIr2Pe7HqQ/IxX+wO CI6HrhhJqRzuIVmJEjqZpOqljf9wYdyIs3nxort8T65wk41G3Gt5YrDsENvBz6P3GgWL fFOZ9+XdmAV4B6Pha/tdzfp/KPRdC8uTcDGdR1MLOYZYJwQq6Rslb/kPL2s5dJcUNdK+ ZnXw==
Received: by 10.216.201.129 with SMTP id b1mr122985weo.56.1352966736255; Thu, 15 Nov 2012 00:05:36 -0800 (PST)
Received: from [192.168.1.75] ([89.181.195.175]) by mx.google.com with ESMTPS id en20sm6127345wid.4.2012.11.15.00.05.30 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 00:05:32 -0800 (PST)
From: Paulo <paulo.mendes@ulusofona.pt>
To: l.wood@surrey.ac.uk, lars@netapp.com
X-Mailer: Modest 3.2
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> , <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com> <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk>
Content-Type: multipart/alternative; boundary="=-krL+ECAhBQhqRqKwKpwF"
Date: Thu, 15 Nov 2012 08:04:24 +0000
Message-Id: <1352966664.3811.5.camel@Nokia-N900-42-11>
Mime-Version: 1.0
X-Gm-Message-State: ALoCoQkAleaTRTUXW/zZ1nIBqupUbDWRoHPmAR+e6k0v9mbZ6gddXmmBmsVQ6La3IU4Bp00c4V1Z
Cc: icnrg@irtf.org, elwynd@folly.org.uk, ngocthanhdinh@gmail.com, Ignacio.Solis@parc.com, stephen.farrell@cs.tcd.ie, william.d.ivancic@nasa.gov
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared	to DTN in wireless communication
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Paulo <paulo.mendes@ulusofona.pt>
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, 15 Nov 2012 08:05:39 -0000

--=-krL+ECAhBQhqRqKwKpwF
Content-Type: text/plain; charset=utf-8
Content-ID: <1352966663.3811.2.camel@Nokia-N900-42-11>
Content-Transfer-Encoding: 8bit

Again... I think that I´m not been clear... I didn´t say that icnrg has to "declare" a winner as a starting point. What I said was that as in any research process, it would be good to try to reach to a consensus about the generic characteristics of an ICN arch.. It main happen that, as in any reach process, we end up not being able to do so.

That will be a good contribution: to come up with a reference model, to support large scale deployment of ICN, since money will only be invested with some ensurance of large deployment.

If this effort is not a goal, why should people pay attention to ICNRG? Just as an informative effort? To list deployment scenarios, surveying soa, and identifying research challenges? Of what? Research challenges of CCN and Netinf may be veryh different due to their different characteristics (e.g. Naming system). And this was for sure already did by the peoplo that devised such approaches (e.g. NDN and SAIL projects).

As Einstein would say: if I knew that would be possible to create a ICN reference architecture, that would not be research :)

But if the creation of a ref arch is not a ICNRG goal, people expect IRTF to tell them how to interoperate all the existing and future ICN flavours.

Cheers
Paulo 

-- 
@N900
----------------------------------
Paulo Mendes
Sientific Director of the Informatic Systems and Tecnology Labs (SITI Labs)
Http://siti.ulusofona.pt 

----- Mensagem original -----
> 
> Didn't the dtnrg declare the bundle protocol proposal the winner by fiat
> in its charter?
> 
> Bad start to a research group, but there you go. Not so much a goal, as
> an own goal.
> 
> If icnrg did the same thing, the rewards of illusory progress could be
> received in the short term.
> 
> Lloyd Wood
> http://sat-net.com/L.Wood/
> 
> 
> ________________________________________
> From: icnrg-bounces@irtf.org [icnrg-bounces@irtf.org] On Behalf Of
> Eggert, Lars [lars@netapp.com] Sent: 14 November 2012 15:18
> To: Paulo Mendes
> Cc: <icnrg@irtf.org>; <elwynd@folly.org.uk>; <ngocthanhdinh@gmail.com>;
> <Ignacio.Solis@parc.com>; <stephen.farrell@cs.tcd.ie>;
> <william.d.ivancic@nasa.gov> Subject: Re: [icnrg] Benefit of information
> centric network (ICN)             compared               to DTN in wireless
> communication
> 
> Hi,
> 
> On Nov 14, 2012, at 16:10, Paulo Mendes <paulo.mendes@ulusofona.pt>
> wrote:
> > From the DTN side, we have a standardization work aiming to devise one
> > architecture. From the ICN side we started by having different
> > projects that follow the same generic ICN principles, but any of which
> > we can be stamped as THE ICN reference. So, from an architectural
> > point of view, this discussion is useless, and should be resumed after
> > the ICNRG come up with some standard track proposal.
> 
> just to clarify: IRTF research groups do not produce standards. The
> DTNRG isn't, and the ICNRG won't either. It's also not a goal to declare
> one of the current architecture proposals a "winner".
> 
> Lars


--=-krL+ECAhBQhqRqKwKpwF
Content-Type: text/html; charset=utf-8
Content-ID: <1352966663.3811.4.camel@Nokia-N900-42-11>
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="generator" content="Osso Notes">
    <title></title></head>
<body>
<p>Again... I think that I´m not been clear... I didn´t say that icnrg has to "declare" a winner as a starting point. What I said was that as in any research process, it would be good to try to reach to a consensus about the generic characteristics of an ICN arch.. It main happen that, as in any reach process, we end up not being able to do so.
<br>
<br>That will be a good contribution: to come up with a reference model, to support large scale deployment of ICN, since money will only be invested with some ensurance of large deployment.
<br>
<br>If this effort is not a goal, why should people pay attention to ICNRG? Just as an informative effort? To list deployment scenarios, surveying soa, and identifying research challenges? Of what? Research challenges of CCN and Netinf may be veryh different due to their different characteristics (e.g. Naming system). And this was for sure already did by the peoplo that devised such approaches (e.g. NDN and SAIL projects).
<br>
<br>As Einstein would say: if I knew that would be possible to create a ICN reference architecture, that would not be research :)
<br>
<br>But if the creation of a ref arch is not a ICNRG goal, people expect IRTF to tell them how to interoperate all the existing and future ICN flavours.
<br>
<br>Cheers
<br>Paulo 
<br>
<br><font color="#7acfff">-- </font>
<br><font color="#7acfff">@N900</font>
<br><font color="#7acfff">----------------------------------</font>
<br><font color="#7acfff">Paulo Mendes</font>
<br><font color="#7acfff">Sientific Director of the Informatic Systems and Tecnology Labs (SITI Labs)</font>
<br><font color="#7acfff"><a href="Http://siti.ulusofona.pt">Http://siti.ulusofona.pt</a> </font>
<br>
<br>----- Mensagem original -----
<br>&gt; 
<br>&gt; Didn't the dtnrg declare the bundle protocol proposal the winner by fiat
<br>&gt; in its charter?
<br>&gt; 
<br>&gt; Bad start to a research group, but there you go. Not so much a goal, as
<br>&gt; an own goal.
<br>&gt; 
<br>&gt; If icnrg did the same thing, the rewards of illusory progress could be
<br>&gt; received in the short term.
<br>&gt; 
<br>&gt; Lloyd Wood
<br>&gt; <a href="http://sat-net.com/L.Wood/">http://sat-net.com/L.Wood/</a>
<br>&gt; 
<br>&gt; 
<br>&gt; ________________________________________
<br>&gt; From: <a href="mailto:icnrg-bounces@irtf.org">icnrg-bounces@irtf.org</a> [<a href="mailto:icnrg-bounces@irtf.org">icnrg-bounces@irtf.org</a>] On Behalf Of
<br>&gt; Eggert, Lars [<a href="mailto:lars@netapp.com">lars@netapp.com</a>] Sent: 14 November 2012 15:18
<br>&gt; To: Paulo Mendes
<br>&gt; Cc: &lt;<a href="mailto:icnrg@irtf.org">icnrg@irtf.org</a>&gt;; &lt;<a href="mailto:elwynd@folly.org.uk">elwynd@folly.org.uk</a>&gt;; &lt;<a href="mailto:ngocthanhdinh@gmail.com">ngocthanhdinh@gmail.com</a>&gt;;
<br>&gt; &lt;<a href="mailto:Ignacio.Solis@parc.com">Ignacio.Solis@parc.com</a>&gt;; &lt;<a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>&gt;;
<br>&gt; &lt;<a href="mailto:william.d.ivancic@nasa.gov">william.d.ivancic@nasa.gov</a>&gt; Subject: Re: [icnrg] Benefit of information
<br>&gt; centric network (ICN)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &#32;compared&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &#32;to DTN in wireless
<br>&gt; communication
<br>&gt; 
<br>&gt; Hi,
<br>&gt; 
<br>&gt; On Nov 14, 2012, at 16:10, Paulo Mendes &lt;<a href="mailto:paulo.mendes@ulusofona.pt">paulo.mendes@ulusofona.pt</a>&gt;
<br>&gt; wrote:
<br>&gt; &gt; From the DTN side, we have a standardization work aiming to devise one
<br>&gt; &gt; architecture. From the ICN side we started by having different
<br>&gt; &gt; projects that follow the same generic ICN principles, but any of which
<br>&gt; &gt; we can be stamped as THE ICN reference. So, from an architectural
<br>&gt; &gt; point of view, this discussion is useless, and should be resumed after
<br>&gt; &gt; the ICNRG come up with some standard track proposal.
<br>&gt; 
<br>&gt; just to clarify: IRTF research groups do not produce standards. The
<br>&gt; DTNRG isn't, and the ICNRG won't either. It's also not a goal to declare
<br>&gt; one of the current architecture proposals a "winner".
<br>&gt; 
<br>&gt; Lars
<br><br></p>
</body>
</html>

--=-krL+ECAhBQhqRqKwKpwF--


From stephen.farrell@cs.tcd.ie  Thu Nov 15 01:32:58 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 8C71121F869C for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2012 01:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWkqS0f-inVJ for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2012 01:32:58 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 083BD21F8467 for <icnrg@irtf.org>; Thu, 15 Nov 2012 01:32:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9F4C5BDCC; Thu, 15 Nov 2012 09:32:34 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Fyis7NbtVrH; Thu, 15 Nov 2012 09:32:33 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.44.71.235]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C6C81BDC7; Thu, 15 Nov 2012 09:32:33 +0000 (GMT)
Message-ID: <50A4B6B1.3080004@cs.tcd.ie>
Date: Thu, 15 Nov 2012 09:32:33 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: Paulo <paulo.mendes@ulusofona.pt>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> , <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com> <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk> <1352966664.3811.5.camel@Nokia-N900-42-11>
In-Reply-To: <1352966664.3811.5.camel@Nokia-N900-42-11>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: icnrg@irtf.org
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared to DTN in wireless communication
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, 15 Nov 2012 09:32:58 -0000

(trimmed cc list)

On 11/15/2012 08:04 AM, Paulo wrote:
> But if the creation of a ref arch is not a ICNRG goal, people expect IRTF to tell them how to interoperate all the existing and future ICN flavours.

People really expect that? They're liable to be disappointed;-)

I don't think interop between any pair of ICN approaches is
that big a deal myself at the protocol level. If however, we
had a way in which the different approaches (and non ICN things
like maybe cdni) could use the same names for objects then I
think that would enable some good things both for research
and if there were any real deployments. That's why we're trying
to propose that ni URI thing - I'd love to know if it might
really be usable for other ICN approaches, or if not, why not.

Cheers,
S.

From paulo.mendes@ulusofona.pt  Fri Nov 16 07:59:18 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 5C54621F8797 for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 07:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=1.361,  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 id75N-sqcjwi for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 07:59:17 -0800 (PST)
Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by ietfa.amsl.com (Postfix) with ESMTP id 932F921F8521 for <icnrg@irtf.org>; Fri, 16 Nov 2012 07:59:16 -0800 (PST)
Received: by mail-ea0-f182.google.com with SMTP id c10so1429047eaa.13 for <icnrg@irtf.org>; Fri, 16 Nov 2012 07:59:14 -0800 (PST)
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=JfUucyD2KA1Ql3JPouDzo59oxL7cuapNyrcCyUe8quw=; b=go3rkfEhV1nZhvdG2+X0bCxk+ftKBkIZTDrKtWiJGn9IUwahepcX3vAiyhAGK9Fagc sscopuGOIBeObTOzohLs++RMpANUD946bnh71Hsru5f7viwrx0AfWMbxQBSK2y6p6T9r qWNcVRoqpCuDAUo0pIugAnzYMU/hWND7WYakDyohl03OSTHRiQ9pVSPo5UqKI6FzqRtR dh66rg/GRSNqYOnj9UhOMuMRTbbd7UbMRuCiFnDuOBWKfNL3tSDuH+PJKTBhTGbYxmy5 4K71V14eeDHiU1Zls/jAGP7UQUAa1O449suNva8VO6A4YCD0hOWDrF4edtxaJNx/RbHj NHlA==
Received: by 10.14.1.69 with SMTP id 45mr14762577eec.23.1353081554260; Fri, 16 Nov 2012 07:59:14 -0800 (PST)
Received: from unknown-f8-1e-df-e9-b9-b2.lan ([89.181.195.175]) by mx.google.com with ESMTPS id f2sm4256648eep.2.2012.11.16.07.59.10 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 07:59:12 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_26EEBE8C-6951-4CAB-91A0-9604488FBFFE"
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <50A4B6B1.3080004@cs.tcd.ie>
Date: Fri, 16 Nov 2012 15:59:09 +0000
Message-Id: <79B7FC4C-2802-4E68-91F5-B7A606723A7D@ulusofona.pt>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> , <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com> <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk> <1352966664.3811.5.camel@Nokia-N900-42-11> <50A4B6B1.3080004@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQmJsVUYzCKqQtu58emkXLAxaiyKRCgxnubzLyZodcMxej8XqcaaRlzYEF6Nhp6w+ntmvYzD
Cc: icnrg@irtf.org
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared to DTN in wireless communication
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, 16 Nov 2012 15:59:18 -0000

--Apple-Mail=_26EEBE8C-6951-4CAB-91A0-9604488FBFFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Stephen

See my comments inline.

On Nov 15, 2012, at 9:32 AM, Stephen Farrell wrote:

>=20
> (trimmed cc list)
>=20
> On 11/15/2012 08:04 AM, Paulo wrote:
>> But if the creation of a ref arch is not a ICNRG goal, people expect =
IRTF to tell them how to interoperate all the existing and future ICN =
flavours.
>=20
> People really expect that? They're liable to be disappointed;-)

Since there are already a considerable arch proposals for ICN, currently =
researchers have to decide which one to use based on its own evaluation, =
facing the problem of creating communication islands. There are only two =
way to avoid this situation: i) create a way to make icn proposals =
interoperable; ii) hope that one of the existing proposals will be =
elected as a de facto standard.

If option ii) is the way to go, which is not impossible if we see for =
instance all the community growing around CCN, the contributions of =
ICNRG will be just informative: survey; research statement; scenarios. =
This is a type of work that most previous projects on ICN, such as most =
EU projects may already have done, since it is normal that a 3 years =
project with a large consortium will be to create scenarios, do a survey =
and set research statement.=20

If option i) is the way to go, then the output could be very useful: =
allow the research community to use any existing (solid) proposal, since =
all of them will interoperate.

What I was proposing is something similar to what is being discussed in =
the DTNRG in relation to routing: after the creation of a large number =
of routing proposal for DTNs, with two of them being specified i DTNRG =
(ProPhet and dLife) it is being discussed the creation of a routing =
reference model to identify a common routing framework, since most =
proposal have similar grounds.  Maybe it will be impossible to create a =
reference model for ICNs. Maybe it will not be so impossible to do so =
for specific core functionally such as naming and routing. But we will =
only know the answer to this is we do some research :-).

When I proposed, before the Atlanta meeting to change the survey draft =
for a concept draft, the idea was exactly to research the possibility to =
create a reference model by analyzing the conceptual similarities =
between the existing proposal.. The conclusion of that work would give =
ICNRG information to decide about what to do after the initial three =
goals: survey, research challenges, scenarios.=20


>=20
> I don't think interop between any pair of ICN approaches is
> that big a deal myself at the protocol level.

Good. So it will not be difficult to specify it and make it available to =
the research community :). This will allow any research to save time =
deciding about the deployment issues associated to a decision about one =
of the existing ICN proposals.

> If however, we
> had a way in which the different approaches (and non ICN things
> like maybe cdni) could use the same names for objects then I
> think that would enable some good things both for research
> and if there were any real deployments. That's why we're trying
> to propose that ni URI thing - I'd love to know if it might
> really be usable for other ICN approaches, or if not, why not.

This is one of the core functionality that I mentioned above: naming... =
Then we have others, such as routing (pure name-based routing; (late) =
name resolution based routing; opportunistic for disruptive scenarios, =
etc)

Cheers
Paulo


>=20
> Cheers,
> S.

-------------------------------------------------------------
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=_26EEBE8C-6951-4CAB-91A0-9604488FBFFE
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; ">Hi =
Stephen<div><br></div><div>See my comments =
inline.</div><div><br><div><div>On Nov 15, 2012, at 9:32 AM, Stephen =
Farrell wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br>(trimmed cc list)<br><br>On 11/15/2012 08:04 AM, =
Paulo wrote:<br><blockquote type=3D"cite">But if the creation of a ref =
arch is not a ICNRG goal, people expect IRTF to tell them how to =
interoperate all the existing and future ICN =
flavours.<br></blockquote><br>People really expect that? They're liable =
to be disappointed;-)<br></div></blockquote><div><br></div><div>Since =
there are already a considerable arch proposals for ICN, currently =
researchers have to decide which one to use based on its own evaluation, =
facing the problem of creating communication islands. There are only two =
way to avoid this situation: i) create a way to make icn proposals =
interoperable; ii) hope that one of the existing proposals will be =
elected as a de facto standard.</div><div><br></div><div>If option ii) =
is the way to go, which is not impossible if we see for instance all the =
community growing around CCN, the contributions of ICNRG will be just =
informative: survey; research statement; scenarios. This is a type of =
work that most previous projects on ICN, such as most EU projects may =
already have done, since it is normal that a 3 years project with a =
large consortium will be to create scenarios, do a survey and set =
research statement.&nbsp;</div><div><br></div><div>If option i) is the =
way to go, then the output could be very useful: allow the research =
community to use any existing (solid) proposal, since all of them will =
interoperate.</div><div><br></div><div>What I was proposing is something =
similar to what is being discussed in the DTNRG in relation to routing: =
after the creation of a large number of routing proposal for DTNs, with =
two of them being specified i DTNRG (ProPhet and dLife) it is being =
discussed the creation of a routing reference model to identify a common =
routing framework, since most proposal have similar grounds. &nbsp;Maybe =
it will be impossible to create a reference model for ICNs. Maybe it =
will not be so impossible to do so for specific core functionally such =
as naming and routing. But we will only know the answer to this is we do =
some research :-).</div><div><br></div><div>When I proposed, before the =
Atlanta meeting to change the survey draft for a concept draft, the idea =
was exactly to research the possibility to create a reference model by =
analyzing the conceptual similarities between the existing proposal.. =
The conclusion of that work would give ICNRG information to decide about =
what to do after the initial three goals: survey, research challenges, =
scenarios.&nbsp;</div><div><br></div><br><blockquote =
type=3D"cite"><div><br>I don't think interop between any pair of ICN =
approaches is<br>that big a deal myself at the protocol level. =
</div></blockquote><div><br></div><div>Good. So it will not be difficult =
to specify it and make it available to the research community :). This =
will allow any research to save time deciding about the deployment =
issues associated to a decision about one of the existing ICN =
proposals.</div><br><blockquote type=3D"cite"><div>If however, we<br>had =
a way in which the different approaches (and non ICN things<br>like =
maybe cdni) could use the same names for objects then I<br>think that =
would enable some good things both for research<br>and if there were any =
real deployments. That's why we're trying<br>to propose that ni URI =
thing - I'd love to know if it might<br>really be usable for other ICN =
approaches, or if not, why =
not.<br></div></blockquote><div><br></div><div>This is one of the core =
functionality that I mentioned above: naming... Then we have others, =
such as routing (pure name-based routing; (late) name resolution based =
routing; opportunistic for disruptive scenarios, =
etc)</div><div><br></div><div>Cheers</div><div>Paulo</div><div><br></div><=
br><blockquote =
type=3D"cite"><div><br>Cheers,<br>S.<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></body></html>=

--Apple-Mail=_26EEBE8C-6951-4CAB-91A0-9604488FBFFE--

From paulo.mendes@ulusofona.pt  Fri Nov 16 08:45:42 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 E25B621F8585 for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 08:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.757,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 LEVd4VVODR4r for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 08:45:41 -0800 (PST)
Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1F021F8527 for <icnrg@irtf.org>; Fri, 16 Nov 2012 08:45:40 -0800 (PST)
Received: by mail-ee0-f54.google.com with SMTP id c13so2176142eek.13 for <icnrg@irtf.org>; Fri, 16 Nov 2012 08:45:40 -0800 (PST)
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=WeXx+o9n9OGhirwCjBkVWviXfHihvSEBG6PHjRNUQ6E=; b=Bxfi0bpg3y2QjHIXcqwsbcD1qMUIAXHFINv1DVajtVH6sXVpkWPXQGAfj+HllwCyNs J85g21F8nbTlIQy6luK0NZetwgQaygnMCwYrBH7uRZHobni2lEsfc0giQ7qcSloACEyM 69ttJndtb4Ta4CE785WPjWYauvd/q+VkU+faYapUo+N2HRzQdAx9kUr3wwuqH9jRlARg Peldd8OS2+0ngw0phVdbgvZEb948eTeDpX/4r4Ov2jgJzZ68woqNbyyGEjAa1wKgg59V PBP7B23H/Cy1/TtRAlb0t/XyBUPqKiAQq+6aEdvyMHEKPNyGqAckFeGIdpcXBiBjzdRw vxHw==
Received: by 10.14.176.68 with SMTP id a44mr15012522eem.1.1353084340043; Fri, 16 Nov 2012 08:45:40 -0800 (PST)
Received: from unknown-f8-1e-df-e9-b9-b2.lan ([89.181.195.175]) by mx.google.com with ESMTPS id e1sm4484121eem.3.2012.11.16.08.45.34 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 08:45:36 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A6A0C9B-D1F7-4347-AEE9-DEFE15578346"
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <2790F226-7135-46C7-9DD8-432606700A39@ericsson.com>
Date: Fri, 16 Nov 2012 16:45:32 +0000
Message-Id: <F2329179-6DF4-4EAF-AA5F-D7C2C9A0B456@ulusofona.pt>
References: <68070FD5-8DA1-416F-A2C9-6EC667E06835@ericsson.com> <8DD7C791-F82E-4220-BC32-BB67001F5BEC@cs.ucla.edu> <2790F226-7135-46C7-9DD8-432606700A39@ericsson.com>
To: =?iso-8859-1?Q?B=F6rje_Ohlman?= <Borje.Ohlman@ericsson.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQmqtj3+beR0mIIrjTl5KwgINkkmZ6Gu5RuQN0okh4o3Ia7+1MpwiK31vBorIpE1uwa8boZJ
Cc: icnrg <icnrg@irtf.org>, Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: [icnrg] Draft ICNRG minutes uploaded
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, 16 Nov 2012 16:45:43 -0000

--Apple-Mail=_5A6A0C9B-D1F7-4347-AEE9-DEFE15578346
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Boerje

What were the action points related to the survey draft? Was the draft =
editor identified? Was an initial toc discussed or will it be proposed =
in the mailing list? I just see your request related to the creation of =
subgroups on wiki, but no reference to the document itself. If we want =
version -00 to be in a readable shape at the interim meeting or the =
Orland meeting, we should start working on the document now. I propose a =
potential table of contents at the end of this email.

Following the discussion in Atlanta, here are my 2cents about this =
draft:

a) I would focus on the ICN major concepts (maybe avoiding the =
specificities of existing proposals) aiming to identify common =
architectural functionalities. The goal of the document would be to try =
to answer the following question: It is possible to create a reference =
model to guide current and future ICN solutions for an easy =
interoperability? If not, what is the current proposal that provides =
more qualities for the described scenarios (other ICNRG draft) and =
potential operation facing future challenges (other ICNRG draft). If =
only one solution is impossible to be identified, the document should at =
least identify what are the proposals that best suits what ICNRG thinks =
should be the behavior for certain functionalities...

IMO the survey draft (that I like to call concept draft) should NOT be =
yet another long document with unrelated description of a set of ICN =
proposals.

b) Scope of the document: the document MUST tackle any core =
functionality that the group identifies as important to be present in =
any ICN proposal, even if such functionality is still not present in any =
of the analyzed proposals. We need some time to discuss this in the =
mailing list.

c) Proposal for the structure of the document


1. Introduction=20
(IMO this document aims to allow us to answer the questions that I =
mention on point a) of my email. But first we need to agree about the =
meaning(s) of ICN)
2. Scope and terminology=20
(e.g. this doc is about ICN and not CDNs)
3. Related effort
(identify previous work on surveying ICN solutions, aiming to justify =
the need to to this work)
4. Analysis of existing proposals=20
(limiting the analysis to the essential, based on a common template to =
allow an easier comparison, assuming that we can manage to create such =
template :-), which by itself is already a challenge)
5. Mapping existing proposals to ICNRG scenarios / use cases
6. Identification of core ICN functionality=20
(the attempt to create a reference model, which does not mean to create =
yet another ICN architecture)=20
7. Mapping of existing proposals to identified core functionalities =
(reference model)
8. Conclusions
(that should try to answer: is there a reference model? is the a de =
facto standard; which existing proposals provide the best solutions to =
identified ICN issues?)

The challenges with this doc are three-fold: Definition of ICN; Creation =
of comparison template; Conceptual reference model. The problem of this =
TOC is that it makes this document somehow dependent of the work done on =
the ICNRG draft related to the scenarios.

Let me know what do you think about the proposed table of contents.

Cheers
Paulo

On Nov 13, 2012, at 5:17 PM, B=F6rje Ohlman wrote:

> I've now made an update according to Lixias comments.
>=20
> Lixia,
> Please double check that I got everything. I might have missed =
something as your changes where not marked.
>=20
> Everyone,
> Anyone else have comments? if so please provide them before the end of =
the week. After that the minutes will be regarded as final.
> If you have comments please mark explicitly which changes you would =
like to have made to the documents.
>=20
> B=F6rje
>=20
> On 10 nov 2012, at 15:12, Lixia Zhang wrote:
>=20
>=20
> On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman wrote:
>=20
> The draft ICNRG minutes are now available at:
> http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg
>=20
> Please check, add and comment.
>=20
> B=F6rje.
>=20
> Hi B=F6rje, I did a pass over my part of the comments only. See =
attached below.
>=20
> Lixia
>=20
> <draft-ietf85-icnrg-minutes-lixia.txt>
>=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=_5A6A0C9B-D1F7-4347-AEE9-DEFE15578346
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; ">Hi =
Boerje<div><br></div><div>What were the action points related to the =
survey draft? Was the draft editor identified? Was an initial toc =
discussed or will it be proposed in the mailing list? I just see your =
request related to the creation of subgroups on wiki, but no reference =
to the document itself. If we want version -00 to be in a readable shape =
at the interim meeting or the Orland meeting, we should start working on =
the document now. I propose a potential table of contents at the end of =
this email.</div><div><br></div><div>Following the discussion in =
Atlanta, here are my 2cents about this =
draft:</div><div><br></div><div>a) I would focus on the ICN major =
concepts (maybe avoiding the specificities of existing proposals) aiming =
to identify common architectural functionalities. The goal of the =
document would be to try to answer the following question: It is =
possible to create a reference model to guide current and future ICN =
solutions for an easy interoperability? If not, what is the current =
proposal that provides more qualities for the described scenarios (other =
ICNRG draft) and potential operation facing future challenges (other =
ICNRG draft). If only one solution is impossible to be identified, the =
document should at least identify what are the proposals that best suits =
what ICNRG thinks should be the behavior for certain =
functionalities...</div><div><br></div><div>IMO the survey draft (that I =
like to call concept draft) should NOT be yet another long document with =
unrelated description of a set of ICN =
proposals.</div><div><br></div><div>b) Scope of the document: the =
document MUST tackle any core functionality that the group identifies as =
important to be present in any ICN proposal, even if such functionality =
is still not present in any of the analyzed proposals. We need some time =
to discuss this in the mailing list.</div><div><br></div><div>c) =
Proposal for the structure of the =
document</div><div><br></div><div><br></div><div>1. =
Introduction&nbsp;</div><div>(IMO this document aims to allow us to =
answer the questions that I mention on point a) of my email. But first =
we need to agree about the meaning(s) of ICN)</div><div>2. Scope and =
terminology&nbsp;</div><div>(e.g. this doc is about ICN and not =
CDNs)</div><div>3. Related effort</div><div>(identify previous work on =
surveying ICN solutions, aiming to justify the need to to this =
work)</div><div>4. Analysis of existing =
proposals&nbsp;</div><div>(limiting the analysis to the essential, based =
on a common template to allow an easier comparison, assuming that we can =
manage to create such template :-), which by itself is already a =
challenge)</div><div>5. Mapping existing proposals to ICNRG scenarios / =
use cases</div><div>6. Identification of core ICN =
functionality&nbsp;</div><div>(the attempt to create a reference model, =
which does not mean to create yet another ICN =
architecture)&nbsp;</div><div>7. Mapping of existing proposals =
to&nbsp;identified core functionalities (reference model)</div><div>8. =
Conclusions</div><div>(that should try to answer: is there a reference =
model? is the a de facto standard; which existing proposals provide the =
best solutions to identified ICN issues?)</div><div><br></div><div>The =
challenges with this doc are three-fold: Definition of ICN; Creation of =
comparison template; Conceptual reference model. The problem of this TOC =
is that it makes this document somehow dependent of the work done on the =
ICNRG draft related to the scenarios.</div><div><br></div><div>Let me =
know what do you think about the proposed table of =
contents.</div><div><br></div><div>Cheers</div><div>Paulo</div><div><br><d=
iv><div>On Nov 13, 2012, at 5:17 PM, B=F6rje Ohlman wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I've =
now made an update according to Lixias comments.<br><br>Lixia,<br>Please =
double check that I got everything. I might have missed something as =
your changes where not marked.<br><br>Everyone,<br>Anyone else have =
comments? if so please provide them before the end of the week. After =
that the minutes will be regarded as final.<br>If you have comments =
please mark explicitly which changes you would like to have made to the =
documents.<br><br>B=F6rje<br><br>On 10 nov 2012, at 15:12, Lixia Zhang =
wrote:<br><br><br>On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman =
wrote:<br><br>The draft ICNRG minutes are now available at:<br><a =
href=3D"http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg">http:=
//www.ietf.org/proceedings/85/minutes/minutes-85-icnrg</a><br><br>Please =
check, add and comment.<br><br>B=F6rje.<br><br>Hi B=F6rje, I did a pass =
over my part of the comments only. See attached =
below.<br><br>Lixia<br><br>&lt;draft-ietf85-icnrg-minutes-lixia.txt&gt;<br=
><br>_______________________________________________<br>icnrg mailing =
list<br>icnrg@irtf.org<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></body></html>=

--Apple-Mail=_5A6A0C9B-D1F7-4347-AEE9-DEFE15578346--

From k.pentikousis@huawei.com  Fri Nov 16 08:58:20 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 697D421F8831 for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 08:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500,  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 RCcJSqPDFC7Q for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 08:58:19 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF6021F85FE for <icnrg@irtf.org>; Fri, 16 Nov 2012 08:58:19 -0800 (PST)
Received: from 172.24.2.119 (EHLO szxeml210-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id ASX73927; Sat, 17 Nov 2012 00:58:12 +0800 (CST)
Received: from SZXEML433-HUB.china.huawei.com (10.72.61.61) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 17 Nov 2012 00:58:06 +0800
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.6]) by szxeml433-hub.china.huawei.com ([10.72.61.61]) with mapi id 14.01.0323.003; Sat, 17 Nov 2012 00:57:52 +0800
From: Konstantinos Pentikousis <k.pentikousis@huawei.com>
To: Paulo Mendes <paulo.mendes@ulusofona.pt>
Thread-Topic: [icnrg] Benefit of information centric network (ICN)	compared to DTN in wireless communication
Thread-Index: AQHNxBnfGehl4C2EykOgoIkgFr+9fJfsrbSw
Date: Fri, 16 Nov 2012 16:57:52 +0000
Message-ID: <8D38716F0C1A444BA0CD7E96454366C23A4EF1A2@szxeml545-mbx.china.huawei.com>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> , <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com> <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk> <1352966664.3811.5.camel@Nokia-N900-42-11>	<50A4B6B1.3080004@cs.tcd.ie> <79B7FC4C-2802-4E68-91F5-B7A606723A7D@ulusofona.pt>
In-Reply-To: <79B7FC4C-2802-4E68-91F5-B7A606723A7D@ulusofona.pt>
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
Cc: "icnrg@irtf.org" <icnrg@irtf.org>
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared	to DTN in wireless communication
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, 16 Nov 2012 16:58:20 -0000

Hi Paulo,

<snip>

|Since there are already a considerable arch proposals for ICN,
|currently researchers have to decide which one to use

<snip>

I do not agree that researchers are waiting from ICNRG to tell them which a=
rch proposal to use.

Best Regards,

Kostas



From paulo.mendes@ulusofona.pt  Fri Nov 16 12:58:10 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 6C61721F84BC for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 12:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.88
X-Spam-Level: 
X-Spam-Status: No, score=-2.88 tagged_above=-999 required=5 tests=[AWL=0.718,  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 xRjC4GFn-lwj for <icnrg@ietfa.amsl.com>; Fri, 16 Nov 2012 12:58:09 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id 98B9B21F8499 for <icnrg@irtf.org>; Fri, 16 Nov 2012 12:58:06 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id x43so1408670wey.13 for <icnrg@irtf.org>; Fri, 16 Nov 2012 12:58:05 -0800 (PST)
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=godQv1UltTT3CXiqbjaCGSUS3Q2CmIOCRdVEs8sUW5c=; b=IdJjMQwDAupex7lmVS+Y9rgGwblL6BTjqwJI1b67QB81gtsooQyz1KZfJe78mUo5i1 QWCHcIp02dQei7jXC1MYjgw9630N6/fE9zeR+L8DI5vS7w3M/hEMHOBNlv3YMdAuvtZV n/0HUuCq79BngCUjdjHnPk9V7UqZMna5mVvaRavLxTfi51aOgp2H0RbtUCuhww48477C WxZ55U2Yqe4sasNjOjkIPtz8Gn4v+zBJnN3ce0qRVaDKB9hFJRPxLNKlaM8wArUZz6qJ x4v6L5Go9n/z4HRVm+FkZpMDd7+2o56ubafqZjr9eJfSQVphVRSld3ghnKur5G7zQF9z Cbpg==
Received: by 10.180.99.36 with SMTP id en4mr6873681wib.20.1353099485675; Fri, 16 Nov 2012 12:58:05 -0800 (PST)
Received: from unknown-f8-1e-df-e9-b9-b2.lan ([89.181.195.175]) by mx.google.com with ESMTPS id p2sm1604174wic.7.2012.11.16.12.57.55 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 12:57:57 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_042C4A69-EB46-460E-A249-DECE9A8E5A6C"
From: Paulo Mendes <paulo.mendes@ulusofona.pt>
In-Reply-To: <8D38716F0C1A444BA0CD7E96454366C23A4EF1A2@szxeml545-mbx.china.huawei.com>
Date: Fri, 16 Nov 2012 20:57:55 +0000
Message-Id: <DD429A24-2729-4E85-89FE-EDC931D0A479@ulusofona.pt>
References: <CC7CB9C8.10DA3%Ignacio.Solis@parc.com> <AFD0075B-5F7A-4758-B11E-230AE5ABD33D@ulusofona.pt> , <D4D47BCFFE5A004F95D707546AC0D7E9186014DE@SACEXCMBX01-PRD.hq.netapp.com> <FD7B10366AE3794AB1EC5DE97A93A37341C9B48C01@EXMB01CMS.surrey.ac.uk> <1352966664.3811.5.camel@Nokia-N900-42-11>	<50A4B6B1.3080004@cs.tcd.ie> <79B7FC4C-2802-4E68-91F5-B7A606723A7D@ulusofona.pt> <8D38716F0C1A444BA0CD7E96454366C23A4EF1A2@szxeml545-mbx.china.huawei.com>
To: Konstantinos Pentikousis <k.pentikousis@huawei.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQmnRzufEqktVzJlGaGZs7IPuHKDmp1QlP4QSmjUjoIalZiz3ZNu9LNgEcvDn/87QDXoAL+Y
Cc: "icnrg@irtf.org" <icnrg@irtf.org>
Subject: Re: [icnrg] Benefit of information centric network (ICN)	compared	to DTN in wireless communication
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, 16 Nov 2012 20:58:10 -0000

--Apple-Mail=_042C4A69-EB46-460E-A249-DECE9A8E5A6C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Kostas=20

With your statement that researchers have to pick up one of the existing =
solutions to develop ICN work, it seems that you're assuming that =
existing proposals provide already a good support (starting point) to =
identified problems/challenges...=20

More over, since these ICN proposals resulted from large projects that =
for sure already did a good survey of the state of the art, a =
description of scenarios and use cases and have (as a result of their =
work) for sure identified research challanges, it seems that the current =
icnrg goals can be accomplished with a sum up report, pointing out to =
the work done by those projects. Is this what you are saying?

If so, what would then be the propose of ICNRG?

Paulo

On Nov 16, 2012, at 4:57 PM, Konstantinos Pentikousis wrote:

> Hi Paulo,
>=20
> <snip>
>=20
> |Since there are already a considerable arch proposals for ICN,
> |currently researchers have to decide which one to use
>=20
> <snip>
>=20
> I do not agree that researchers are waiting from ICNRG to tell them =
which arch proposal to use.
>=20
> Best Regards,
>=20
> Kostas
>=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=_042C4A69-EB46-460E-A249-DECE9A8E5A6C
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; =
"><div>Kostas&nbsp;<br><br></div><div>With your statement that =
researchers have to pick up one of the existing solutions to develop ICN =
work, it seems that you're assuming that existing proposals provide =
already a good support (starting point) to identified =
problems/challenges...&nbsp;</div><div><br></div><div>More over, since =
these ICN proposals resulted from large projects that for sure already =
did a good survey of the state of the art, a description of scenarios =
and use cases and have (as a result of their work) for sure identified =
research challanges, it seems that the current icnrg goals can be =
accomplished with a sum up report, pointing out to the work done by =
those projects.&nbsp;Is this what you are saying?<br><br>If so, what =
would then be the propose of =
ICNRG?</div><div><br>Paulo</div><div><br><div><div>On Nov 16, 2012, at =
4:57 PM, Konstantinos Pentikousis wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Hi =
Paulo,<br><br>&lt;snip&gt;<br><br>|Since there are already a =
considerable arch proposals for ICN,<br>|currently researchers have to =
decide which one to use<br><br>&lt;snip&gt;<br><br>I do not agree that =
researchers are waiting from ICNRG to tell them which arch proposal to =
use.<br><br>Best =
Regards,<br><br>Kostas<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></body></html>=

--Apple-Mail=_042C4A69-EB46-460E-A249-DECE9A8E5A6C--

From borje.ohlman@ericsson.com  Tue Nov 20 06:24:28 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 858E221F84BB for <icnrg@ietfa.amsl.com>; Tue, 20 Nov 2012 06:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.514
X-Spam-Level: 
X-Spam-Status: No, score=-5.514 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
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 144HnBEyQtLS for <icnrg@ietfa.amsl.com>; Tue, 20 Nov 2012 06:24:28 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6F25121F86AD for <icnrg@irtf.org>; Tue, 20 Nov 2012 06:24:27 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1e6d000002d2c-50-50ab9299ef86
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 99.33.11564.9929BA05; Tue, 20 Nov 2012 15:24:25 +0100 (CET)
Received: from ESESSHC012.ericsson.se (153.88.183.54) by esessmw0247.eemea.ericsson.se (153.88.115.93) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 20 Nov 2012 15:24:23 +0100
Received: from ESESSMB107.ericsson.se ([169.254.7.172]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0318.001; Tue, 20 Nov 2012 15:24:22 +0100
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
To: icnrg <icnrg@irtf.org>
Thread-Topic: Announcing interim ICNRG meeting in Stockholm Feb 14-15, 2013
Thread-Index: AQHNxyq80Oydbo2pEkOWaBOOv13xFg==
Date: Tue, 20 Nov 2012 14:24:21 +0000
Message-ID: <BD858E03-4FE9-49EF-BD2A-133DA887745B@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_BD858E034FE949EFBD2A133DA887745Bericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUyM+Jvje7MSasDDDZ32VjsnL2TyYHRY/LG w2wBjFFcNimpOZllqUX6dglcGafezGQqOK5UsaN/ClMD40LZLkZODgkBE4l/E+6yQNhiEhfu rWfrYuTiEBI4yShx/tssJghnJ6PEi/eLoJwljBKTli9kBWlhE3CUeP/0AJgtIiAlsWnvXTYQ W1jATWLi5fnMEHFvie2TQJpBbD2Jr3MPg9ksAqoS2yd8AevlFbCXeL33EiOIzSggK/GlcTVY L7OAuMStJ/OZIM4TkFiy5zwzhC0q8fLxP1YIW1Fi59l2qPpkid7P06BmCkqcnPkE7DUhATWJ 4x+OMU9gFJmFZOwsJC2zkLRAxPUkbkydwgZha0ssW/iaGcLWlZjx7xBUjbVEx7bfzMhqFjBy rGJkz03MzEkvN9zECIyhg1t+6+5gPHVO5BCjNAeLkjgvV9J+fyGB9MSS1OzU1ILUovii0pzU 4kOMTBycUg2Msmt3HTubYHfUtLDl5Vk+JpmogMcyHdPDGYwOnL55cPZWIXv2BSI7HfhnrDur erZu/Tv/eZH53Jc5r0ucuPZ1nuYKT32lbSW/HCZYbkh35dtjVux3+2tHeOHBZ1te7xI5dMMm b6c8v9K1GZom1+OWPUsTXzPFSuPVzInvhJV7mWtCdxXOVTUUUmIpzkg01GIuKk4EAEWj0vNv AgAA
Subject: [icnrg] Announcing interim ICNRG meeting in Stockholm Feb 14-15, 2013
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, 20 Nov 2012 14:24:28 -0000

--_000_BD858E034FE949EFBD2A133DA887745Bericssoncom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is to announce that our planned interim meeting in Stockholm in Februa=
ry will take place and the dates are now fixed. Additional information will=
 be available early December. Any updates will be available at: http://trac=
.tools.ietf.org/group/irtf/trac/wiki/icnrg

Interim ICNRG, Kista, Stockholm, Sweden, February 14-15, 2013

  *   Meeting time: Thursday 9.00-17.00 & Friday 9.00-15.00
  *   Location: Kista, Stockholm, Sweden (exact location TBA)
  *   Agenda: TBA
  *   Meeting materials: TBD
  *   Detailed information will be available early December 2012

As previously announced there will be a related event organized in conjunct=
ion with the ICNRG meeting:

Workshop focusing on ICN for Future Media Distribution, Wednesday February =
13th

  *   This is not an ICNRG event, but it is held in conjunction with the IC=
NRG interim meeting and ICNRG participants are most welcome to participate =
in this workshop.
  *   the workshop will include the final demo of the SAIL project
  *   The workshop will have invited speakers, demos and industry discussio=
ns, including regulatory issues relating to ICN.
  *   The workshop will be organized by SAIL and a Swedish ICN project call=
ed Efraim (partners include TV broadcasters (SVT, TV4), Spotify, CDN provid=
ers (QBrick, Peeralism), Telia, Ericsson and academic parners (SICS, Acreeo=
, Lund University))
  *   Detailed information will be available early December 2012

B=F6rje

--_000_BD858E034FE949EFBD2A133DA887745Bericssoncom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <332869C7DF178240ACF46CEB4DBD3D34@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<base href=3D"data:">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<base href=3D"data:">
<div style=3D"font-family: Helvetica; font-size: 12px; color: black; text-a=
lign: left; ">
This is to announce that our planned interim meeting in Stockholm in Februa=
ry will take place and the dates are now fixed. Additional information will=
 be available early December. Any updates will be available at:&nbsp;<span =
class=3D"Apple-style-span" style=3D"font-size: medium; "><a href=3D"http://=
trac.tools.ietf.org/group/irtf/trac/wiki/icnrg">http://trac.tools.ietf.org/=
group/irtf/trac/wiki/icnrg</a></span></div>
<div style=3D"text-align: left; "><br>
<div>Interim ICNRG, Kista, Stockholm, Sweden, <strong>February 14-15, 2013<=
/strong>
<ul>
<li><strong>Meeting time: Thursday 9.00-17.00 &amp; Friday 9.00-15.00 </str=
ong></li><li>Location: Kista, Stockholm, Sweden (exact location TBA) </li><=
li>Agenda: TBA </li><li>Meeting materials: TBD </li><li>Detailed informatio=
n will be available early December 2012 </li></ul>
<div>As previously announced there will be a related event organized in con=
junction with the ICNRG meeting:</div>
</div>
</div>
<div style=3D"font-family: Helvetica; font-size: 12px; color: black; text-a=
lign: left; ">
<br>
</div>
<div style=3D"font-family: Helvetica; font-size: 12px; color: black; text-a=
lign: left; ">
Workshop focusing on <em>ICN for Future Media Distribution</em>, <b>Wednesd=
ay February 13th
</b>
<ul>
<li>This is <strong>not</strong> an ICNRG event, but it is held in conjunct=
ion with the ICNRG interim meeting and ICNRG participants are most welcome =
to participate in this workshop.
</li><li>the workshop will include the final demo of the SAIL project </li>=
<li>The workshop will have invited speakers, demos and industry discussions=
, including regulatory issues relating to ICN.
</li><li>The workshop will be organized by SAIL and a Swedish ICN project c=
alled Efraim (partners include TV broadcasters (SVT, TV4), Spotify, CDN pro=
viders (QBrick, Peeralism), Telia, Ericsson and academic parners (SICS, Acr=
eeo, Lund University))
</li><li>Detailed information will be available early December 2012 </li></=
ul>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>B=F6rj=
e</div>
</div>
</body>
</html>

--_000_BD858E034FE949EFBD2A133DA887745Bericssoncom_--

From borje.ohlman@ericsson.com  Fri Nov 30 04:44:01 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 7FA4821F88B8 for <icnrg@ietfa.amsl.com>; Fri, 30 Nov 2012 04:44:01 -0800 (PST)
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=[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 6EQtPR9iHJz1 for <icnrg@ietfa.amsl.com>; Fri, 30 Nov 2012 04:44:00 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1F35321F8A9F for <icnrg@irtf.org>; Fri, 30 Nov 2012 04:43:58 -0800 (PST)
X-AuditID: c1b4fb30-b7f936d0000018b3-43-50b8aa0d40a1
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 50.FB.06323.D0AA8B05; Fri, 30 Nov 2012 13:43:57 +0100 (CET)
Received: from ESESSHC010.ericsson.se (153.88.183.48) by esessmw0256.eemea.ericsson.se (153.88.115.96) with Microsoft SMTP Server (TLS) id 8.3.279.1; Fri, 30 Nov 2012 13:43:57 +0100
Received: from ESESSMB107.ericsson.se ([169.254.7.172]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0318.001; Fri, 30 Nov 2012 13:43:56 +0100
From: =?iso-8859-1?Q?B=F6rje_Ohlman?= <borje.ohlman@ericsson.com>
To: Paulo Mendes <paulo.mendes@ulusofona.pt>
Thread-Topic: [icnrg] Draft ICNRG minutes uploaded
Thread-Index: AQHNvqfjeHjY+dCUEUq+IAhdSbFLPZfjDNkAgATqfYCABK4sAIAVzeIA
Date: Fri, 30 Nov 2012 12:43:55 +0000
Message-ID: <CCDE67DE.326B%Borje.Ohlman@ericsson.com>
In-Reply-To: <F2329179-6DF4-4EAF-AA5F-D7C2C9A0B456@ulusofona.pt>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_CCDE67DE326BBorjeOhlmanericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM+JvjS7vqh0BBn/P6Fs8fJRusXP2TiaL 1hWP2C3+TshzYPGY8nsjq8fkjYfZPGYce8nu8bW7gyWAJYrLJiU1J7MstUjfLoEro2niB8aC ewsYKw5f2cvWwNjaydjFyMkhIWAi8XV1I5QtJnHh3no2EFtI4CSjRN9hYQh7J6PEhPNmXYxc QPYSRolnL1vBitgEHCXePz3ACmKLCOhITD73FmwQs0CWRN+0K+wgtrCAoUTrhG6oGiOJxbM+ AdVwANluEudb7EHCLAKqEo/PdoO18gqYSvRP3AdWzingIPGo8QQziM0oICvxpXE1M8R4cYlb T+YzQdwsILFkz3lmCFtU4uXjf2C9ogJ6EntW/GeDiCtK7DzbDtUbJfHl+kpWiF2CEidnPmGB +FFN4viHY8wTGMVnIVkxC0nLLCQtEHE9iRtTp7BB2NoSyxa+ZoawdSVm/DsEVWMtsWLuckZk NQsYOVYxsucmZuakl5tvYgRG8MEtvw12MG66L3aIUZqDRUmcV091v7+QQHpiSWp2ampBalF8 UWlOavEhRiYOTqkGxsA1/tvCxbnfh89VmcYku0Xks9a1c1vf+n61mWQSanWIteDO88/aIgbW /FuW5326EfKyxO9D3s8o5uZX7u93LHBICJvv1d2xkDNlmuzjmsq3PEIXUz7xphypLJwi/qX5 1turkceuZEt1PD95im0NW3bvlNU/r/XMf9uTwLYl+vAxtwyvH8X85kosxRmJhlrMRcWJAMgQ v2WuAgAA
Cc: "Dave Oran \(oran\)" <oran@cisco.com>, icnrg <icnrg@irtf.org>, Dirk Kutscher <Dirk.Kutscher@neclab.eu>
Subject: Re: [icnrg] Draft ICNRG minutes uploaded
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, 30 Nov 2012 12:44:01 -0000

--_000_CCDE67DE326BBorjeOhlmanericssoncom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Paulo,

Sorry for the long delay in responding to your mail. We have all been reall=
y busy.
As I'm not the main responsible you can expect some further comments from D=
ave and Dirk as well. But to give you my 2 cents.

On 16 nov 2012, at 17:45, Paulo Mendes <paulo.mendes@ulusofona.pt<mailto:pa=
ulo.mendes@ulusofona.pt>> wrote:

Hi Boerje

What were the action points related to the survey draft?
No specific defined. the line between the Survey and the Concepts/Problems =
drafts are still unclear. My view is that we should not bother so much abou=
t that now, but just try to collect material that we think is relevant, the=
n we can structure it into the drafts when we see what we have.

Was the draft editor identified?
No.

Was an initial toc discussed or will it be proposed in the mailing list?
Not really. Open to proposals, I personally think your's below is a good st=
art.

I just see your request related to the creation of subgroups on wiki, but n=
o reference to the document itself. If we want version -00 to be in a reada=
ble shape at the interim meeting or the Orland meeting, we should start wor=
king on the document now. I propose a potential table of contents at the en=
d of this email.
My proposal is that you go ahead and start the document and we take it from=
 there. I think the best way for you to get some constructive feedback is t=
o make a first draft proposal that we can have a discussion around.

B=F6rje


Following the discussion in Atlanta, here are my 2cents about this draft:

a) I would focus on the ICN major concepts (maybe avoiding the specificitie=
s of existing proposals) aiming to identify common architectural functional=
ities. The goal of the document would be to try to answer the following que=
stion: It is possible to create a reference model to guide current and futu=
re ICN solutions for an easy interoperability? If not, what is the current =
proposal that provides more qualities for the described scenarios (other IC=
NRG draft) and potential operation facing future challenges (other ICNRG dr=
aft). If only one solution is impossible to be identified, the document sho=
uld at least identify what are the proposals that best suits what ICNRG thi=
nks should be the behavior for certain functionalities...

IMO the survey draft (that I like to call concept draft) should NOT be yet =
another long document with unrelated description of a set of ICN proposals.

b) Scope of the document: the document MUST tackle any core functionality t=
hat the group identifies as important to be present in any ICN proposal, ev=
en if such functionality is still not present in any of the analyzed propos=
als. We need some time to discuss this in the mailing list.

c) Proposal for the structure of the document


1. Introduction
(IMO this document aims to allow us to answer the questions that I mention =
on point a) of my email. But first we need to agree about the meaning(s) of=
 ICN)
2. Scope and terminology
(e.g. this doc is about ICN and not CDNs)
3. Related effort
(identify previous work on surveying ICN solutions, aiming to justify the n=
eed to to this work)
4. Analysis of existing proposals
(limiting the analysis to the essential, based on a common template to allo=
w an easier comparison, assuming that we can manage to create such template=
 :-), which by itself is already a challenge)
5. Mapping existing proposals to ICNRG scenarios / use cases
6. Identification of core ICN functionality
(the attempt to create a reference model, which does not mean to create yet=
 another ICN architecture)
7. Mapping of existing proposals to identified core functionalities (refere=
nce model)
8. Conclusions
(that should try to answer: is there a reference model? is the a de facto s=
tandard; which existing proposals provide the best solutions to identified =
ICN issues?)

The challenges with this doc are three-fold: Definition of ICN; Creation of=
 comparison template; Conceptual reference model. The problem of this TOC i=
s that it makes this document somehow dependent of the work done on the ICN=
RG draft related to the scenarios.

Let me know what do you think about the proposed table of contents.

Cheers
Paulo

On Nov 13, 2012, at 5:17 PM, B=F6rje Ohlman wrote:

I've now made an update according to Lixias comments.

Lixia,
Please double check that I got everything. I might have missed something as=
 your changes where not marked.

Everyone,
Anyone else have comments? if so please provide them before the end of the =
week. After that the minutes will be regarded as final.
If you have comments please mark explicitly which changes you would like to=
 have made to the documents.

B=F6rje

On 10 nov 2012, at 15:12, Lixia Zhang wrote:


On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman wrote:

The draft ICNRG minutes are now available at:
http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg

Please check, add and comment.

B=F6rje.

Hi B=F6rje, I did a pass over my part of the comments only. See attached be=
low.

Lixia

<draft-ietf85-icnrg-minutes-lixia.txt>

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

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

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


--_000_CCDE67DE326BBorjeOhlmanericssoncom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <D19F93D6E6C70F4CB36D2E3CA8FC1593@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; font-size: 14px; font-family: Calibri, sans-ser=
if; ">
<div><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size:=
 medium; ">Hi Paulo,</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; "><br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; ">Sorry for the long delay in responding to your mail. We have all been =
really busy.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: mediu=
m; ">As I'm not the main responsible you can expect some further comments f=
rom Dave and Dirk as well. But to give you my 2 cents.</div>
<div style=3D"font-family: Helvetica; font-size: medium; "><br>
<div>
<div><font color=3D"#008e00">On 16 nov 2012, at 17:45, Paulo Mendes &lt;<a =
href=3D"mailto:paulo.mendes@ulusofona.pt">paulo.mendes@ulusofona.pt</a>&gt;=
 wrote:</font></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; ">
<font color=3D"#008e00">Hi Boerje</font>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">What were the action points related to the sur=
vey draft?</font></div>
</div>
</blockquote>
No specific defined. the line between the Survey and the Concepts/Problems =
drafts are still unclear. My view is that we should not bother so much abou=
t that now, but just try to collect material that we think is relevant, the=
n we can structure it into the drafts
 when we see what we have.</div>
<div><br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<font color=3D"#008e00">Was the draft editor identified?</font></div>
</blockquote>
No.</div>
<div><br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<font color=3D"#008e00">Was an initial toc discussed or will it be proposed=
 in the mailing list?</font></div>
</blockquote>
Not really. Open to proposals, I personally think your's below is a good st=
art.</div>
<div><br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<font color=3D"#008e00">I just see your request related to the creation of =
subgroups on wiki, but no reference to the document itself. If we want vers=
ion -00 to be in a readable shape at the interim meeting or the Orland meet=
ing, we should start working on the
 document now. I propose a potential table of contents at the end of this e=
mail.</font></div>
</blockquote>
My proposal is that you go ahead and start the document and we take it from=
 there. I think the best way for you to get some constructive feedback is t=
o make a first draft proposal that we can have a discussion around.</div>
<div style=3D"color: rgb(0, 0, 0); "><br>
</div>
<div style=3D"color: rgb(0, 0, 0); "><span class=3D"Apple-tab-span" style=
=3D"white-space: pre; "></span>B=F6rje</div>
<div><br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">Following the discussion in Atlanta, here are =
my 2cents about this draft:</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">a) I would focus on the ICN major concepts (ma=
ybe avoiding the specificities of existing proposals) aiming to identify co=
mmon architectural functionalities. The goal of the document would be to tr=
y to answer the following question:
 It is possible to create a reference model to guide current and future ICN=
 solutions for an easy interoperability? If not, what is the current propos=
al that provides more qualities for the described scenarios (other ICNRG dr=
aft) and potential operation facing
 future challenges (other ICNRG draft). If only one solution is impossible =
to be identified, the document should at least identify what are the propos=
als that best suits what ICNRG thinks should be the behavior for certain fu=
nctionalities...</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">IMO the survey draft (that I like to call conc=
ept draft) should NOT be yet another long document with unrelated descripti=
on of a set of ICN proposals.</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">b) Scope of the document: the document MUST ta=
ckle any core functionality that the group identifies as important to be pr=
esent in any ICN proposal, even if such functionality is still not present =
in any of the analyzed proposals.
 We need some time to discuss this in the mailing list.</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">c) Proposal for the structure of the document<=
/font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">1. Introduction&nbsp;</font></div>
<div><font color=3D"#008e00">(IMO this document aims to allow us to answer =
the questions that I mention on point a) of my email. But first we need to =
agree about the meaning(s) of ICN)</font></div>
<div><font color=3D"#008e00">2. Scope and terminology&nbsp;</font></div>
<div><font color=3D"#008e00">(e.g. this doc is about ICN and not CDNs)</fon=
t></div>
<div><font color=3D"#008e00">3. Related effort</font></div>
<div><font color=3D"#008e00">(identify previous work on surveying ICN solut=
ions, aiming to justify the need to to this work)</font></div>
<div><font color=3D"#008e00">4. Analysis of existing proposals&nbsp;</font>=
</div>
<div><font color=3D"#008e00">(limiting the analysis to the essential, based=
 on a common template to allow an easier comparison, assuming that we can m=
anage to create such template :-), which by itself is already a challenge)<=
/font></div>
<div><font color=3D"#008e00">5. Mapping existing proposals to ICNRG scenari=
os / use cases</font></div>
<div><font color=3D"#008e00">6. Identification of core ICN functionality&nb=
sp;</font></div>
<div><font color=3D"#008e00">(the attempt to create a reference model, whic=
h does not mean to create yet another ICN architecture)&nbsp;</font></div>
<div><font color=3D"#008e00">7. Mapping of existing proposals to&nbsp;ident=
ified core functionalities (reference model)</font></div>
<div><font color=3D"#008e00">8. Conclusions</font></div>
<div><font color=3D"#008e00">(that should try to answer: is there a referen=
ce model? is the a de facto standard; which existing proposals provide the =
best solutions to identified ICN issues?)</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">The challenges with this doc are three-fold: D=
efinition of ICN; Creation of comparison template; Conceptual reference mod=
el. The problem of this TOC is that it makes this document somehow dependen=
t of the work done on the ICNRG draft
 related to the scenarios.</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">Let me know what do you think about the propos=
ed table of contents.</font></div>
<div><font color=3D"#008e00"><br>
</font></div>
<div><font color=3D"#008e00">Cheers</font></div>
<div><font color=3D"#008e00">Paulo</font></div>
<div style=3D"color: rgb(0, 0, 0); "><br>
<div>
<div>On Nov 13, 2012, at 5:17 PM, B=F6rje Ohlman wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">I've now made an update according to Lixias comme=
nts.<br>
<br>
Lixia,<br>
Please double check that I got everything. I might have missed something as=
 your changes where not marked.<br>
<br>
Everyone,<br>
Anyone else have comments? if so please provide them before the end of the =
week. After that the minutes will be regarded as final.<br>
If you have comments please mark explicitly which changes you would like to=
 have made to the documents.<br>
<br>
B=F6rje<br>
<br>
On 10 nov 2012, at 15:12, Lixia Zhang wrote:<br>
<br>
<br>
On Nov 9, 2012, at 10:27 AM, B=F6rje Ohlman wrote:<br>
<br>
The draft ICNRG minutes are now available at:<br>
<a href=3D"http://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg">htt=
p://www.ietf.org/proceedings/85/minutes/minutes-85-icnrg</a><br>
<br>
Please check, add and comment.<br>
<br>
B=F6rje.<br>
<br>
Hi B=F6rje, I did a pass over my part of the comments only. See attached be=
low.<br>
<br>
Lixia<br>
<br>
&lt;draft-ietf85-icnrg-minutes-lixia.txt&gt;<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>
</blockquote>
</div>
<br>
<div apple-content-edited=3D"true"><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; border-spacing: 0px; "><span class=3D"Apple-=
style-span" style=3D"border-collapse: separate; border-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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; border=
-spacing: 0px; ">
<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></div>
<div><a href=3D"http://siti.ulusofona.pt/~pmendes">http://siti.ulusofona.pt=
/~pmendes</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></div>
</span></span></div>
<br>
</div>
</div>
_______________________________________________<br>
icnrg mailing list<br>
<a href=3D"mailto:icnrg@irtf.org" style=3D"color: rgb(0, 0, 0); ">icnrg@irt=
f.org</a><br>
https://www.irtf.org/mailman/listinfo/icnrg<br>
</blockquote>
</div>
<div style=3D"color: rgb(0, 0, 0); "><br>
</div>
</div>
</div>
</body>
</html>

--_000_CCDE67DE326BBorjeOhlmanericssoncom_--
