Dear Prof. Wang,<div><br></div><div>Thank you very much for your reply and tips. We will think about it deeply according to these papers.<div><br><span>Best wishes,</span></div><div><br></div><div>Dong Qian</div></div><br><br><br><blockquote name="replyContent" style="padding-left:5px;margin-left:5px;border-left:#b6b6b6 2px solid;margin-right:0">-----原始邮件-----<br>
<b>发件人:</b> "Lan Wang (lanwang)" <lanwang@memphis.edu><br>
<b>发送时间:</b> 2017年4月1日 星期六<br>
<b>收件人:</b> "董谦" <dongqian@cstnet.cn><br>
<b>抄送:</b> "ndn-interest@lists.cs.ucla.edu" <ndn-interest@lists.cs.ucla.edu>, "石珊姗" <shishanshan@cstnet.cn><br>
<b>主题:</b> Re: [Ndn-interest] Some questions about NDN forwarding and traffic control<br><br>
<div class="">
<div style="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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">
<div style="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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">
<span class="Apple-style-span" style="border-collapse: separate; line-height: normal; border-spacing: 0px; text-size-adjust: auto;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">
<br class="">
</div>
</span></div>
</div>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Mar 31, 2017, at 7:18 AM, 董谦 <<a href="mailto:dongqian@cstnet.cn" class="" target="_blank">dongqian@cstnet.cn</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Dear <span style="white-space: pre-wrap;" class="">community</span>,</div>
<div class=""><br class="">
</div>
<div class="">We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.</div>
<div class=""><br class="">
</div>
<div class="">As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine
grained Name information, so we get the FIB table. When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop). On the other hand, Data will be forwarded by checking PIT in an intermidiate
router.</div>
<div class=""><br class="">
</div>
<div class="">And, we have some questions:</div>
<div class=""><br class="">
</div>
<div class="">1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the r! outing pr otocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because
the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name? For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding?
Using flooding method to detect or maybe some active signals from the new Content located nodes?</div>
</div>
</blockquote>
<div><br class="">
</div>
The FIB establishment is also based on name. To establish the FIB entry for a new name prefix, you can use a name based routing protocol such as NLSR (<a href="https://named-data.net/publications/techreports/ndn-0037-1-nlsr/" class="" target="_blank">https://named-data.net/publications/techreports/ndn-0037-1-nlsr/</a>)
or hyperbolic routing (<a href="https://named-data.net/publications/techreports/ndn-0042-1-asf/" class="" target="_blank">https://named-data.net/publications/techreports/ndn-0042-1-asf/</a>). Flooding would work but is not efficient in most cases. </div>
<div><br class="">
</div>
<div>Lan</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
</div>
<div class="">2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces? Do Data chunks have any size range? Is it necessory to consider In-network collaborative
or non-collaborative cache? </div>
<div class=""><br class="">
</div>
<div class="">3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/! PIT and a dd global factor?</div>
<div class=""><br class="">
</div>
<div class="">We appreciate your reply very much.</div>
<div class=""><br class="">
</div>
<div class="">Best regards.</div>
<div class=""><br class="">
</div>
<div class="">Dong Qian</div>
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Ndn-interest mailing list<br class="">
<a href="mailto:Ndn-interest@lists.cs.ucla.edu" class="" target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br class="">
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest<br class="">
</div>
</blockquote>
</div>
<br class="">
</blockquote><br><br><br>