[Ndn-interest] ndn architecture

[Christos Papadopoulos]

At the risk of oversimplifying, here is one way to think about it:

NDN does for content what IP did for hosts. In other words, IP gave us a 
uniform interface by which to address every host in the Internet. NDN 
gives us a uniform interface by which to address every content object in 
the Internet.

NDN does not need TCP/UDP/IP, it runs directly on top of any link layer 
that IP does. For NDN, TCP/UDP/IP is just another lower layer, just like 
Ethernet. We can demonstrate such operation now, where you connect two 
hosts running NFD and retrieve content from one to the other directly 
over Ethernet, without the data ever getting into an IP packet.

I am not sure what the file stream module is, but just like IP, you can 
build all sorts of abstractions over NDN.

Hope this helps.

Christos.


On 02/21/2016 02:18 AM, Tanusree Chatterjee wrote:
> Hello,
>
> I am new to NDN. I felt some difficulty to understand the NDN 
> hourglass architecture thoroughly in contrast with IP architecture 
> layers that is given in the ndn project site. Is it the today's NDN 
> architecture which work on IP/UDP channel (in contrast with the link 
> layer in IP)? In future it is assumed to not to work upon IP/UDP 
> channel? And what about the 'file stream' module? Please send me a 
> good documentation which clearly describes the modules of the NDN 
> architecture in contrast with the same of IP.
>
>
> -- Regards,
> Tanusree Chatterjee
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160221/32e20711/attachment.html>