Subject: [Icn-interest] CFP: ACM SIGCOMM-2012 Workshop on Information-Centric Networking (ICN-2012)
From: Dirk.Kutscher at neclab.eu (Dirk Kutscher)
Date: Wed, 21 Dec 2011 10:17:25 +0000

[apologies if you receive multiple copies of this message]

======================================================================
                        ACM SIGCOMM Workshop on
                Information-Centric Networking (ICN-2012)

                           August 13 or 17, 2012
                             Helsinki, Finland

                       http://www.neclab.eu/icn-2012/
======================================================================

                            Call For Papers
                            ---------------

The rapid development of Information-Centric Networking (ICN) concepts
in the last few years is one of the significant results from multiple
international Future Internet research activities. Based on the ICN
concepts, the principal communication paradigm is no longer end-to-end
data delivery between hosts as in the current Internet
architecture. Instead, ICN-based network architectures focus directly
on retrieving information objects securely, reliably, scalably, and
efficiently.  These architectural design efforts aim to directly
address the network challenges that arise from the increasing demand
for highly scalable content distribution, from accelerated growths of
mobile devices, and from wide deployment of Internet-of-things (IoT).

The resulting network architectures are expected to leverage
in-network storage, multiparty communication through replication and
interaction models to provide effective and efficient data
distribution in the communication services, and to provide effective
solutions in securing the network infrastructure as well as user data.

Important research topics for ICN include: naming and addressing (how
to name information objects, how to represent location information),
routing and resolution (deciding on how to forward "interest" in
information and actual information objects, whether and how to resolve
information object names to lower layer identifiers during that
process), resource management (implications of in-network caching and
paradigms such as receiver-orientation to resource sharing, congestion
control etc.) and security (privacy, data protection and key
distribution have to be adapted to the new communication models).

This workshop invites original contributions on Information-Centric
Networking architecture topics, specific algorithms and protocols, as
well as on results from implementations and experimentation.

                       ICN-2012 topics of Interest
                       ---------------------------

* Naming and addressing
* Routing and name resolution
* Routing and name resolution scalability
* Support for mobility
* Support for / avoidance of middle boxes
* Models and/or compensation schemes for user contribution to network
  resources (bandwidth, storage for caching, battery, processing, name
  resolution, etc.)
* Resource management (caching strategies, congestion control)
* Security, privacy and trust
* Testbeds and simulations frameworks
* Metadata and network extensions
* Real-time traffic over ICN (voice, video, etc)
* PDUs, fragmentation and ???packet size??? implications on design
* Should ICN be an overlay or an underlay
* Performance evaluation
* Inter-domain operations (protocols, policies, etc.)
* Limitations of ICNs

                         Submission instructions
                         ------------------------

All submissions must be original work that has not been submitted to
any other workshop, conference, or journal. The workshop will accept
papers describing completed work as well as work-in-progress and
ongoing experiments. Papers describing practical experiments are
especially invited.  Submissions must be no greater than 6 pages in
length and must be in PDF format. Reviews will be single-blind: please
include authors name and affiliation in the submission.

Submission website:  http://www.neclab.eu/icn-2012/

                             Important Dates
                             ---------------

Abstract registration:  March 18, 2012
Submissions due:        March 25, 2012
Notification:           May 7 2012
Camera ready due:       May 25, 2012
Date of the Workshop:   August 13 or 17, 2012

                          Steering Committee
                <icn2012-organizers at listserv.netlab.nec.de>
                -------------------------------------------

Dirk Kutscher, NEC Laboratories Europe -  Germany
Giacomo Morabito, University of Catania - Italy
Boerje Ohlman, Ericsson - Sweden
George C. Polyzos, AUEB - Greece
Ignacio Solis, PARC - USA
Lixia Zhang, UCLA - USA

                         Technical Program Chairs
                         ------------------------

* Dirk Kutscher, NEC Laboratories Europe
* B??rje Ohlman, Ericsson
* Ignacio Solis, PARC

                       Technical program committee
                       ---------------------------

* Bengt Ahlgren, SICS
* Hitoshi Asaeda, Keio University
* Tohru Asami, The University of Tokyo
* Jun Bi, Tsinghua University
* Nicola Blefari-Melazzi, U Rome
* Giovanna Carofiglio, ALU
* Yanghee Choi, Seoul Nat. U
* Dave Clark, MIT
* Costas Courcoubetis, AUEB
* Andrea Detti, U Rome
* Stephen Farrell, Trinity College Dublin
* Volker Hilt, ALU
* Jussi Kangasharju, Helsinki University
* Holger Karl, Universitaet Paderborn
* Gunnar Karlsson, KTH
* Teemu Koponen, Nicira
* Anders Lindgren, SICS
* Daniel Massey, Colorado SU
* Christos Papadopoulos, Colorado SU
* George Pavlou, UCL
* Dave Oran, Cisco
* Joerg Ott, Aalto University
* Max Ott, NICTA
* Jarno Rajahalme, NSN
* Thomas Schmidt, HAW Hamburg
* Scott Shenker, ICSI
* Karen Sollins, MIT
* Sasu Tarkoma, University of Helsinki
* Dirk Trossen, Cambridge Univ.
* Ryuji Wakikawa, Toyota ITC
* Lan Wang, U Memphis
* George Xylomenos, AUEB
* Tomohiko Yagyu, NEC
* Beichuan Zhang, U Arizona

                                 Contact
                                 -------
<icn2012-organizers at listserv.netlab.nec.de>

From: chesteve at dca.fee.unicamp.br (Christian Esteve Rothenberg)
Date: Mon, 19 Dec 2011 18:19:44 -0200
Subject: [Icn-interest] CoNEXT 11 posters on CCN
Message-ID: <[email-masked]>

A Step toward Practical Deployment of  the Content-Centric
Networking Architecture
http://conferences.sigcomm.org/co-next/2011/workshops/StudentWorkshop/papers/1569501059.pdf

CANA: One Step From IP Networking Toward Content
Networking
http://conferences.sigcomm.org/co-next/2011/workshops/StudentWorkshop/papers/1569500965.pdf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listserv.netlab.nec.de/mailman/private/icn-interest/attachments/20111219/e7ccc8a4/attachment.htm>

From: [email-masked] ()
Date: Tue, 13 Dec 2011 09:00:05 -0000
Subject: No subject
Message-ID: <[email-masked]>

ve the CDN benefits. I think that CDNs will survive with ICN but they can r=
ely on a simpler delivery protocol that will increase the overall performan=
ce by, at least, reducing the steps of a client to reach a content.<br>

<br>
Just my two cents.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Thanks,<br>
Yaogong<br>
<br>
</blockquote>
<br>
Regards,<br>
Pedro<br>
<br>
</blockquote>
<br>
<br>
-- <br></div>
------------------------------<u></u>------------------------------<u></u>-=
----------<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ruidong Li (Ph. D.)<br>
Network Architecture Labrotary, Photonic Network Research Institute,<br>
National Institute of Information and Communications Technology (NICT),<br>
4-2-1 Nukui-kita Machi, Koganei City, Tokyo, 184-8795, Japan<br>
Tel: <a href=3D"tel:%2B81-42-327-5813" value=3D"+81423275813" target=3D"_bl=
ank">+81-42-327-5813</a> Fax: <a href=3D"tel:%2B81-42-327-6680" value=3D"+8=
1423276680" target=3D"_blank">+81-42-327-6680</a><br>
Email: <a href=3D"mailto:lrd at nict.go.jp" target=3D"_blank">lrd at nict.go.jp</=
a> ------------------------------<u></u>------------------------------<u></=
u>-----------</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
Icn-interest mailing list<br>
<a href=3D"mailto:Icn-interest at listserv.netlab.nec.de" target=3D"_blank">Ic=
n-interest at listserv.netlab.<u></u>nec.de</a><br>
<a href=3D"https://listserv.netlab.nec.de/mailman/listinfo/icn-interest" ta=
rget=3D"_blank">https://listserv.netlab.nec.<u></u>de/mailman/listinfo/icn-=
<u></u>interest</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>Yaogong Wang, PhD candidate<br>Department of Computer Science<br>North Car=
olina State University<br><a href=3D"http://www4.ncsu.edu/~ywang15/" target=
=3D"_blank">http://www4.ncsu.edu/~ywang15/</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>
</div>

--e89a8f23464921e8da04b5dd40c3--

From: [email-masked] ()
Date: Tue, 13 Dec 2011 09:00:05 -0000
Subject: No subject
Message-ID: <[email-masked]>

ve the CDN benefits. I think that CDNs will survive with ICN but they can r=
ely on a simpler delivery protocol that will increase the overall performan=
ce by, at least, reducing the steps of a client to reach a content.<br>

<br>
Just my two cents.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Thanks,<br>
Yaogong<br>
<br>
</blockquote>
<br>
Regards,<br>
Pedro<br>
<br>
</blockquote>
<br>
<br>
-- <br></div>
------------------------------<u></u>------------------------------<u></u>-=
----------<span><font color=3D"#888888"><br>
Ruidong Li (Ph. D.)<br>
Network Architecture Labrotary, Photonic Network Research Institute,<br>
National Institute of Information and Communications Technology (NICT),<br>
4-2-1 Nukui-kita Machi, Koganei City, Tokyo, 184-8795, Japan<br>
Tel: <a href=3D"tel:%2B81-42-327-5813" value=3D"+81423275813" target=3D"_bl=
ank">+81-42-327-5813</a> Fax: <a href=3D"tel:%2B81-42-327-6680" value=3D"+8=
1423276680" target=3D"_blank">+81-42-327-6680</a><br>
Email: <a href=3D"mailto:lrd at nict.go.jp" target=3D"_blank">lrd at nict.go.jp</=
a> ------------------------------<u></u>------------------------------<u></=
u>-----------</font></span><div><div><br>
<br>
<br>
______________________________<u></u>_________________<br>
Icn-interest mailing list<br>
<a href=3D"mailto:Icn-interest at listserv.netlab.nec.de" target=3D"_blank">Ic=
n-interest at listserv.netlab.<u></u>nec.de</a><br>
<a href=3D"https://listserv.netlab.nec.de/mailman/listinfo/icn-interest" ta=
rget=3D"_blank">https://listserv.netlab.nec.<u></u>de/mailman/listinfo/icn-=
<u></u>interest</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>Yaogong Wang, PhD candidate<br>Department of Computer Science<br>North Car=
olina State University<br><a href=3D"http://www4.ncsu.edu/~ywang15/" target=
=3D"_blank">http://www4.ncsu.edu/~ywang15/</a><br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>
</div>
_______________________________________________<br>Icn-interest mailing lis=
t<br><a href=3D"mailto:Icn-interest at listserv.netlab.nec.de" target=3D"_blan=
k">Icn-interest at listserv.netlab.nec.de</a><br><a href=3D"https://listserv.n=
etlab.nec.de/mailman/listinfo/icn-interest" target=3D"_blank">https://lists=
erv.netlab.nec.de/mailman/listinfo/icn-interest</a><br>
</blockquote></div><br></div></div>________________________________________=
_______<br>Icn-interest mailing list<br><a href=3D"mailto:Icn-interest at list=
serv.netlab.nec.de" target=3D"_blank">Icn-interest at listserv.netlab.nec.de</=
a><br>
<a href=3D"https://listserv.netlab.nec.de/mailman/listinfo/icn-interest" ta=
rget=3D"_blank">https://listserv.netlab.nec.de/mailman/listinfo/icn-interes=
t</a><br></blockquote></div></div></div><br></div><br>_____________________=
__________________________<br>

Icn-interest mailing list<br>
<a href=3D"mailto:Icn-interest at listserv.netlab.nec.de">Icn-interest at listser=
v.netlab.nec.de</a><br>
<a href=3D"https://listserv.netlab.nec.de/mailman/listinfo/icn-interest" ta=
rget=3D"_blank">https://listserv.netlab.nec.de/mailman/listinfo/icn-interes=
t</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Yaogo=
ng Wang, PhD candidate<br>Department of Computer Science<br>North Carolina =
State University<br><a href=3D"http://www4.ncsu.edu/~ywang15/" target=3D"_b=
lank">http://www4.ncsu.edu/~ywang15/</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>
</div>

--e89a8f8389e99f763b04b5de8e2a--

From: [email-masked] ()
Date: Tue, 13 Dec 2011 09:00:05 -0000
Subject: No subject
Message-ID: <[email-masked]>

can ask the same question to any network security design, ICN or not.

Second, I think NDN routing is not as good as IP in adapting to network
dynamics. Since the Interest and Data packet follow the same path, then if
some node on the path fails (or if the related PIT entry in a node on the
path is lost) when the data comes back to content requester(s) , the data
packet will not be forwarded and the requester(s) have to solicit it again.
While in IP networking, the routing may adapt to the node failure fast and
redirect the data packet to the requester. What do you think?

If NDN runs the same routing protocol as IP's, then they converge at the sa=
me time (roughly). So what you want to compare is
the packet delivery performance before routing has converged.

In NDN, if a link or node fails, the downstream node will send the interest=
 to other interfaces, and when this interest hits
one of the cached copies of data upstream, it'll bring data back and the do=
wnstream node will keep sending interests that way.
Thus the repair happens inside the network most of the time, and it benefit=
s from NDN's multipath capability and loop prevention.
IP forwards packets using the best path in the routing table, which is in f=
lux during convergence period, and many studies have
shown that there're significant packet losses and delays. There's IP fast r=
erouting work, which uses backup routes to get around of failures
quickly, but they need pre-configured based on the topology and expected fa=
ilure scenarios.

Another point is that there're faults that IP routing cannot even see, e.g.=
, during prefix hijacking or congestion, from IP routing's point of view,
everything is fine and it keeps sending traffic to the faulty place. But ND=
N will notice the problems due to interest timeout and send the interest
to other faces. My view is that NDN will have better packet delivery perfor=
mance than IP due to naming the packets and maintaining states in the route=
r.
We're doing some simulation studies along this line.

Thanks,

---
beichuan

ps: if this list is not an appropriate place, we can take the discussion of=
fline.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Beichuan,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Don&#8217;t worry, techni=
cal discussions are more welcome.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dirk<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> icn-inte=
rest-bounces at listserv.netlab.nec.de [mailto:icn-interest-bounces at listserv.n=
etlab.nec.de]
<b>On Behalf Of </b>Beichuan Zhang<br>
<b>Sent:</b> Dienstag, 10. Januar 2012 21:52<br>
<b>To:</b> icn-interest at listserv.netlab.nec.de<br>
<b>Subject:</b> Re: [Icn-interest] Icn-interest Digest, Vol 11, Issue 6<o:p=
></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Not sure if this list is an appropriate place for te=
chnical discussions of a specific ICN design, but my comments inline anyway=
.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:13.5pt;font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">Date=
: Tue, 10 Jan 2012 16:07:10 &#43;0800</span></span><span style=3D"font-size=
:13.5pt;font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;"><br>
<span class=3D"apple-style-span">From: xiaoyan Hu &lt;<a href=3D"mailto:xhb=
reezehu at gmail.com">xhbreezehu at gmail.com</a>&gt;</span><br>
<span class=3D"apple-style-span">Subject: [Icn-interest] questions about ND=
N data signature and routing</span><br>
<span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <=
/span><span class=3D"apple-style-span">adaptability in network dynamic</spa=
n><br>
<span class=3D"apple-style-span">To:</span><span class=3D"apple-converted-s=
pace">&nbsp;</span><span class=3D"apple-style-span"><a href=3D"mailto:icn-i=
nterest at listserv.netlab.nec.de">icn-interest at listserv.netlab.nec.de</a></sp=
an><br>
<br>
<span class=3D"apple-style-span">Dear all,</span><br>
<br>
<span class=3D"apple-style-span">I have two questions for NDN.</span><br>
<span class=3D"apple-style-span">First, one question about the verification=
 of data signature in NDN if the</span><br>
<span class=3D"apple-style-span">key pair of some publisher is renewed: for=
 example, in NDN, a publisher use</span><br>
<span class=3D"apple-style-span">some private-public key pair for data sign=
ature in a period; then the key</span><br>
<span class=3D"apple-style-span">pair is deprecated later. My question is t=
hat whether other Internet users</span><br>
<span class=3D"apple-style-span">can locate the old public key. If not, how=
 can the old content (content</span><br>
<span class=3D"apple-style-span">signed by the old private key) be validate=
d? And I think it is infeasible</span><br>
<span class=3D"apple-style-span">to sign each piece of old content with the=
 new private key. But if yes, I</span><br>
<span class=3D"apple-style-span">think the old key pair would be abused by =
malicious attackers (if I am</span><br>
<span class=3D"apple-style-span">wrong, please correct me). Do you guys hav=
e any thought about this?</span><br>
<br>
</span><o:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The publisher can use the new key to sign a content =
object that binds the new key and the old key.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">From your description I don't see why this is an NDN=
 specific problem. You can ask the same question to any network security de=
sign, ICN or not.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
lvetica&quot;,&quot;sans-serif&quot;"><br>
<span class=3D"apple-style-span">Second, I think NDN routing is not as good=
 as IP in adapting to network</span><br>
<span class=3D"apple-style-span">dynamics. Since the Interest and Data pack=
et follow the same path, then if</span><br>
<span class=3D"apple-style-span">some node on the path fails (or if the rel=
ated PIT entry in a node on the</span><br>
<span class=3D"apple-style-span">path is lost) when the data comes back to =
content requester(s) , the data</span><br>
<span class=3D"apple-style-span">packet will not be forwarded and the reque=
ster(s) have to solicit it again.</span><br>
<span class=3D"apple-style-span">While in IP networking, the routing may ad=
apt to the node failure fast and</span><br>
<span class=3D"apple-style-span">redirect the data packet to the requester.=
 What do you think?</span><br>
<br>
</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If NDN runs the same routing protocol as IP's, then =
they converge at the same time (roughly). So what you want to compare is<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">the packet delivery performance before routing has c=
onverged.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In NDN, if a link or node fails, the downstream node=
 will send the interest to other interfaces, and when this interest hits<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">one of the cached copies of data upstream, it'll bri=
ng data back and the downstream node will keep sending interests that way.&=
nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thus the repair happens inside the network most of t=
he time,&nbsp;and it benefits from NDN's multipath capability and loop prev=
ention.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">IP forwards packets using the best path in the routi=
ng table, which is in flux during convergence period, and many studies have=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">shown that there're significant packet losses and de=
lays. There's IP fast rerouting work, which uses backup routes to get aroun=
d of failures<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">quickly, but they need pre-configured based on the t=
opology and expected failure scenarios.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Another point is that there're faults that IP routin=
g cannot even see, e.g., during prefix hijacking or congestion, from IP rou=
ting's point of view,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">everything is fine and it keeps sending traffic to t=
he faulty place. But NDN will notice the problems due to interest timeout a=
nd send the interest<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">to other faces. My view is that NDN will have better=
 packet delivery performance than IP due to naming the packets and maintain=
ing states in the router.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">We're doing some simulation studies along this line.=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">---<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">beichuan<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">ps: if this list is not an appropriate place, we can=
 take the discussion offline.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_82AB329A76E2484D934BBCA77E9F524924BC5217PALLENEofficehd_--