[Mini-NDN] Fwd: Auto-discard notification

[Lan Wang (lanwang)]

Begin forwarded message:

From: <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>>
Subject: Auto-discard notification
Date: November 19, 2018 at 11:38:20 AM CST
To: <mini-ndn-owner at lists.cs.ucla.edu<mailto:mini-ndn-owner at lists.cs.ucla.edu>>

The attached message has been automatically discarded.
From: Klaus Schneider <klaus at cs.arizona.edu<mailto:klaus at cs.arizona.edu>>
Subject: Re: [Ndn-interest] Issues in routing
Date: November 19, 2018 at 11:38:10 AM CST
To: Tanusree Chatterjee <tnsr.chatterjee at gmail.com<mailto:tnsr.chatterjee at gmail.com>>, ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>


Hey Tanusree,

I think it's useful to distinguish between 3 logical entities:

1. Router -- forwards packets towards a storage location
2. Content Store -- a temporary storage location (can be cleared at any time)
3. Content Repository -- a permanent storage location (in the same sense as today's web servers are "permanent")

These can all be on the same machine or on a different machine. For example, a core NDN router will probably have a content store, but not a content repository.

Now to answer your questions:

So, if a router is down for some reason, what about the data it
stores in its CS and the connections it hold?

Well, the content store will be unreachable. There is usually no notion of a "connection" in NDN, so other routers should be able to fetch the data from somewhere else.

If the router is
temporarily down, it can resume to its normal operations sometime later

Sure. Why not?

But if the router is permanently down and there are several data
it produce and there are no more copies of all the data.

That only matters if the last content repository is down. In this case the data might become unavailable, if all the content stores have cleared the data as well (which they are free to do).

NDN does not have the goal to permanently replicate every content piece inside the network. The content provider is still responsible for keeping their content repository up and running, and likely wants to provide some redundancy here.

NDN, however, can help with the scalability: it reduces the load on the content repository when its content objects become more popular.


Best regards,
Klaus



On 11/19/18 2:32 AM, Tanusree Chatterjee wrote:
Hello all,
In NDN the routers are the busiest and most responsible entity in the network. So, if a router is down for some reason, what about the data it stores in its CS and the connections it hold? If the router is temporarily down, it can resume to its normal operations sometime later.  But if the router is permanently down and there are several data it produce and there are no more copies of all the data. Can there be any network administrator which can have the copies of the data of a router when it is down? If it is a high connectivity node, can network administrator can play a vital roll to take care the connections of the nodes?
-- Thanks & Regards,
Tanusree Chatterjee
_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto: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/mini-ndn/attachments/20181119/3e71bd89/attachment-0001.html>