[Ndn-interest] NDN Stack

[Klaus Schneider]

On 8/5/19 1:33 PM, Ahmed BENMOUSSA wrote:
> Hello everyone,
> 
> I am sending you to ask about the NDN stack.
> In some papers, researchers include a "/Transport/" layer to the NDN 
> stack as follows:
> ======================
> \ *Application */
>   +--------------------------------------+
>    \ *Transport */
>     +----------------------------------+
>       \ *NDN */
>        +-----------------------------+
>       / *Link-layer*      \
>     +----------------------------------+
>    / *Physical* \
>    =====================
> 
> Other researches don't include it in their papers.

Maybe you can give a couple links to these papers?

I don't think this transport layer is part of the mainstream NDN 
consensus, which would be closer to 
https://conferences.sigcomm.org/co-next/2009/papers/Jacobson.pdf

In general, I wouldn't read too much into these NDN layers. They seem 
more conceptual (e.g. "Security") rather than specific solutions for 
tunneling or NDN-over-IP deployment.

Best regards,
Klaus


> 
> My question is: What is the role of the "/Transport/" layer in this case?
> Knowing that the "Link-layer" includes any communication protocol that 
> NDN could use as a tunnel to send and receive traffic, why a 
> "/Transport/" layer is added?
> 
> Is this layer added to support future NDN deployment? (When native NDN 
> communications are used instead of IP overlays). Or does it have other 
> roles?
> 
> What NDN stack should I consider in my papers and presentations? (with 
> or without the Transport layer).
> 
> Thank you in advance.
> 
> Kind regards,
> Ahmed. B.
> 
> 
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 45792 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20190805/21ac342a/attachment-0001.png>