<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Kuo,<br>
this seems to me again the plain old scalability problem of
NDN/CCN that I (re)-observed in the mailing list some days ago
(see my mails or Locator hints, updated cisco packet format
draft).<br>
<br>
I proposed the introduction of a ContentLocator TLV field (aka
locator hint, routing info, forwarding alias, etc. ) which
contains a set of names used to help routing in those contexts
where pure routing by object name practically does not scale.
ContentLocator is used by an NDN/CCN router when FIB is unable to
forward on (Object) name.<br>
<br>
Thus in your case the Interest fields would be:<br>
<br>
(Object) Name : Foo<br>
ContentLocator : {ndn/tw/sinica/Foo; ndn/edu/ucla/Foo} <br>
<br>
The NDN strategy layer chooses which is the better serving
location between ndn/tw/sinica/Foo and ndn/edu/ucla/Foo<br>
<br>
Only ndn/tw/sinica/ and ndn/edu/ucla/ are advertized on the global
routing plane, thus reducing the FIB entries to the (e.g.) number
of Autonomous Systems. Plain old locator identifier split approach
proposed by several researchers before me.<br>
<br>
Clearly, you need a secure, reliable and scalable resolution
system (as properly observed by DaveO) to obtain the
ContentLocator field at the communication session start. And also
a name management system that authorizes you tho name an object as
Foo.<br>
<br>
I guess that
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
sooner or later people mostly involved in defining the NDN/CCN
protocol will face this old scalability problem (I apologize if
you already solved this scalability issue and I miss some
information) .<br>
<br>
Conversely, as now it seems to me, this technology can be used
only in small closed environments, that however could be an
interesting use-case too, albeit with a little bit smaller impact
with respect to the original global scope: "Information-centric
networking (ICN) is an approach to evolve the Internet
infrastructure" (citing ICNRG home page) <br>
<br>
Andrea<br>
<br>
<br>
<br>
On 01/16/2015 03:52 AM, AnChe Kuo wrote:<br>
</div>
<blockquote
cite="mid:CAD7pYU3ZPTm9socrevkHZWBSx3FhJnENPuYDmrkSFsdSo7b9wg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Dear Sir or Madam</div>
<div><br>
</div>
<div>I am an intern at Academia Sinica and a student at NCTU,
Taiwan, </div>
<div>and I have been studying NDN for a few month now.</div>
<div><br>
</div>
<div>If I wrote an application and call it "Foo", then can I
simply register "Foo" into the global NDN network? Given
current architecture, each router administrator is allowed to
register only names satisfying certain pattern that is
assigned to them, right? So if Academia Sinica now joins NDN
network, we might get a prefix "ndn/tw/sinica", which means I
can only register my application as "ndn/tw/sinica/Foo".</div>
<div><br>
</div>
<div>But this present a problem. If some one in UCLA decided
that she loves this application, and also runs a producer
there, she would have to register it as "<span
style="color:rgb(51,51,51);font-family:'Helvetica
Neue',Helvetica,Arial,sans-serif;font-size:14px;line-height:20px">/ndn/edu/ucla/Foo".
Now how can a client in China get the content that is </span><font
color="#333333" face="Helvetica Neue, Helvetica, Arial,
sans-serif"><span style="font-size:14px;line-height:20px">closest
to him if he only knows the application name "Foo"? If he
sends an interest named "Foo", then longest prefix match
won't find anything. If he has to know the full name </span></font>"<span
style="color:rgb(51,51,51);font-family:'Helvetica
Neue',Helvetica,Arial,sans-serif;font-size:14px;line-height:20px">/ndn/edu/ucla/Foo",
then we have lost the </span><font color="#333333"
face="Helvetica Neue, Helvetica, Arial, sans-serif"><span
style="font-size:14px;line-height:20px">benefit of
NDN architecture, because it is almost equivalent to an
exact source, not just a content name.</span></font></div>
<div><font color="#333333" face="Helvetica Neue, Helvetica,
Arial, sans-serif"><span
style="font-size:14px;line-height:20px"><br>
</span></font></div>
<div><span
style="font-size:14px;line-height:20px;color:rgb(51,51,51);font-family:'Helvetica
Neue',Helvetica,Arial,sans-serif">So how does NDN intend to
solve the problem?</span></div>
<div><span
style="font-size:14px;line-height:20px;color:rgb(51,51,51);font-family:'Helvetica
Neue',Helvetica,Arial,sans-serif">1. If NDN only focus on a
small </span><font color="#333333" face="Helvetica Neue,
Helvetica, Arial, sans-serif"><span
style="font-size:14px;line-height:20px">network, with
applications for IoT or M2M can register their names
freely, then what are the benefits of NDN other then its
more natural architecture for related application? If we
look at efficiency, then TCP/IP is probably enough for a
small area network, will NDN offer the improvement that is
necessary?</span></font></div>
<div><font color="#333333" face="Helvetica Neue, Helvetica,
Arial, sans-serif"><span
style="font-size:14px;line-height:20px">2. If we release
the top level namespace for all applications to register,
so that we may register "Foo" into global routers, with
these top level namespace managed by some organization
(similar to ICANN), then will we suffer from routing table
explosion? Because now we have each unique URLs, and
millions of different applications registered at the top
level to serve the global users.</span></font></div>
<div><font color="#333333" face="Helvetica Neue, Helvetica,
Arial, sans-serif"><span
style="font-size:14px;line-height:20px"><br>
</span></font></div>
<div><font color="#333333" face="Helvetica Neue, Helvetica,
Arial, sans-serif"><span
style="font-size:14px;line-height:20px">So far these are
my concerns. I understand I might be having the wrong
question, because it might no be the intended use of NDN
or the current objective of the whole NDN project. But
either way I would love to hear from your feedback, or any
critique on my question is welcomed.</span></font></div>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Best Wishes,
<div>郭安哲<br>
<div>Kuo, AnChe(Schwannden)</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ndn-interest mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a>
<a class="moz-txt-link-freetext" href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a>
</pre>
</blockquote>
<br>
</body>
</html>