[ndnSIM] CCN Segmentation

[Alex Afanasyev]

Hi Wali,

In the available reference applications, such as ConsumerCbr, it is assumed that each Interest requesting a unique piece of content object.  This uniqueness is achieved by adding a sequence number to the end of the configured prefix.

This request pattern can be interpreted in many other ways. For example Saeid's example can be considered as a series of Interests for one big file, which is split into 250 content objects.

I'm not entirely sure why you're saying that "...we cannot have very large objects which will be requested with multiple interest packets and satisfied with corresponding data packets..."  Each interest corresponds to one content object.   Which sequence numbers represent a particular data can be totally independent.  

In addition, if you have specific needs, you can always write a custom application, as explained here http://ndnsim.net/applications.html#custom-applications, which gives you a full control over what will be in requests (Interests) and what will be in replies (ContentObjects).  

Sincerely,
Alex

PS

Recently a lot of things got renamed, so the code that Saeid gave would look a little bit differently:

std::string prefix = "/prefix";

ndn::AppHelper consumerHelper ("ns3::ndn::ConsumerCbr");
consumerHelper.SetPrefix (prefix);
consumerHelper.SetAttribute ("Frequency", StringValue ("10")); // 10 interests a second
consumerHelper.SetAttribute ("MaxSeq", StringValue("250")); 



On Dec 28, 2012, at 1:42 AM, Saeid Montazeri <saeid.montazeri at gmail.com> wrote:

> Hi Wali,
> 
> I have a little bit experience in ndnSIM. 
> 
> Alex please correct me if I am wrong.
> 
> You can have a content with several packets by setting MaxSeq attribute of CcnxAppHelper class.
> For example I have added the bold line bellow to the code in ndn-grid.cc. By the line, I asked CcnxAllHelper to generate Interest for 250 Data packets of the content with name "/prefix". ("/prefix/0", "/prefix/1", .. "/prefix/249")
> 
> std::string prefix = "/prefix";
> 
> CcnxAppHelper consumerHelper ("ns3::CcnxConsumerCbr");
> consumerHelper.SetPrefix (prefix);
> consumerHelper.SetAttribute ("Frequency", StringValue ("10")); // 10 interests a second
> consumerHelper.SetAttribute ("MaxSeq", StringValue("250")); 
> 
> 
> Best Regards,
> Saeid
> 
> 
> On Fri, Dec 28, 2012 at 4:37 PM, Wali <ahmed.waliullah.kazi at gmail.com> wrote:
> Hi Alex,
> 
> I was skimming through the ndnSIIM documentation. I did not find reference to any notion of segmentation. Is the present implementation following the simple model of one interest packet for one object, which is satisfied by one data packet? Hence, presently, we cannot have very large objects which will be requested with multiple interest packets and satisfied with corresponding data packets? 
> 
> Thank you very much for your time.
> 
> Best regards,
> Wali.
> 
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
> 
> 
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20121228/69837188/attachment.html>