[Ndn-interest] Some questions about NDN forwarding and traffic control
dongqian at cstnet.cn
Fri Mar 31 19:15:22 PDT 2017
Dear Prof. Wang,
Thank you very much for your reply and tips. We will think about it deeply according to these papers.
发件人: "Lan Wang (lanwang)" <lanwang at memphis.edu>
发送时间: 2017年4月1日 星期六
收件人: "董谦" <dongqian at cstnet.cn>
抄送: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>, "石珊姗" <shishanshan at cstnet.cn>
主题: Re: [Ndn-interest] Some questions about NDN forwarding and traffic control
On Mar 31, 2017, at 7:18 AM, 董谦 <dongqian at cstnet.cn> wrote:
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.
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.
And, we have some questions:
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?
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 (https://named-data.net/publications/techreports/ndn-0037-1-nlsr/) or hyperbolic routing (https://named-data.net/publications/techreports/ndn-0042-1-asf/). Flooding would work but is not efficient in most cases.
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?
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?
We appreciate your reply very much.
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest