From nano at remap.ucla.edu Sat Aug 1 15:10:41 2015 From: nano at remap.ucla.edu (Alex Horn) Date: Sat, 1 Aug 2015 17:10:41 -0500 Subject: [Ndn-interest] how to set freshnessSecond? Message-ID: note that another pattern often seen for 'getLatestContent' is using child selectors ( answeroriginkind & rightmostchild) & versioning - essentially using an incrementing value as the last name component, using interest selectors to 'ask the network' for the latest version, and using excludes for content you already have. (if you don't get a reply before a timeout, it's the latest :) this was used in initial ndnvideo (paper explains mechanism in detail), and many others... perhaps most recently in ndn-rtc (paper ) (also explains mechanism) On Wed, Jul 29, 2015 at 9:48 PM, ndn ndn wrote: > Dear Steve, > > Thanks for you reply,I think I misunderstood "Must be fresh" literally. > In my point of view,"Must be fresh" means ndn Interests must get the > newest data from publisher. Set a freshness period can help me to solve > it.At first,I didn't find any way to set freshness value,but now I find it > though you help.just using Data. getMetaInfo() and set it. > MemoryContentCache is a good way to acheive it,I will try it. > > > Thanks for your help and reply, forgive my poor english spell. > qhsong > > 2015-07-30 10:15 GMT+08:00 Steve DiBenedetto : > >> >> >> On Wed, Jul 29, 2015 at 7:58 PM, ndn ndn wrote: >> >>> Hello everyone, >>> I'm using NDN-CCL to writing a NDN application. But I find a problem >>> about data cache. >>> In NDN network ,all data can store in CS.But in my application,some >>> content always changing in 5 seconds,so I think setting a freshnessSecond >>> will help me solve this problem. >>> I try to setMustBefresh value,but it not works.The app also receive the >>> cached value. >>> But in NDN-CCL,I didn't find any method to set this?how to set it? >>> >>> hope you give me some reply. >>> >>> thanks. >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndn at sqh.me Sun Aug 2 05:50:10 2015 From: ndn at sqh.me (ndn ndn) Date: Sun, 2 Aug 2015 20:50:10 +0800 Subject: [Ndn-interest] how to set freshnessSecond? In-Reply-To: References: Message-ID: Ok?I will read it and get further understand.Thanks for you reply. 2015-08-02 6:10 GMT+08:00 Alex Horn : > note that another pattern often seen for 'getLatestContent' is using child > selectors > > ( answeroriginkind & rightmostchild) & versioning > - > essentially using an incrementing value as the last name component, using > interest selectors to 'ask the network' for the latest version, and using > excludes for content you already have. > > (if you don't get a reply before a timeout, it's the latest :) > > this was used in initial ndnvideo (paper > explains > mechanism in detail), and many others... > perhaps most recently in ndn-rtc (paper > ) > (also explains mechanism) > > > On Wed, Jul 29, 2015 at 9:48 PM, ndn ndn wrote: > >> Dear Steve, >> >> Thanks for you reply,I think I misunderstood "Must be fresh" literally. >> In my point of view,"Must be fresh" means ndn Interests must get the >> newest data from publisher. Set a freshness period can help me to solve >> it.At first,I didn't find any way to set freshness value,but now I find it >> though you help.just using Data. getMetaInfo() and set it. >> MemoryContentCache is a good way to acheive it,I will try it. >> >> >> Thanks for your help and reply, forgive my poor english spell. >> qhsong >> >> 2015-07-30 10:15 GMT+08:00 Steve DiBenedetto : >> >>> >>> >>> On Wed, Jul 29, 2015 at 7:58 PM, ndn ndn wrote: >>> >>>> Hello everyone, >>>> I'm using NDN-CCL to writing a NDN application. But I find a problem >>>> about data cache. >>>> In NDN network ,all data can store in CS.But in my application,some >>>> content always changing in 5 seconds,so I think setting a freshnessSecond >>>> will help me solve this problem. >>>> I try to setMustBefresh value,but it not works.The app also receive the >>>> cached value. >>>> But in NDN-CCL,I didn't find any method to set this?how to set it? >>>> >>>> hope you give me some reply. >>>> >>>> thanks. >>>> >>> > _______________________________________________ > 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: From ndn at sqh.me Sun Aug 2 06:20:47 2015 From: ndn at sqh.me (ndn ndn) Date: Sun, 2 Aug 2015 21:20:47 +0800 Subject: [Ndn-interest] How to calculate max data bytes per packet? Message-ID: Hello everyone, Recently,I want to send a large packet via NDN.When I using NDN-CCL,face.getMaxNdnPacketSize() can get the max packet size in NDN network. But I use data.setContent() to set face.getMaxNdnPacketSize() bytes data,the program crashed,it tells me the size of data is too large than max NDN packet size. So,How to get the max data size I can send?It make me confuse for a long time. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Aug 2 19:34:57 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Sun, 2 Aug 2015 19:34:57 -0700 Subject: [Ndn-interest] How to calculate max data bytes per packet? In-Reply-To: References: Message-ID: <55bed353.0a1a450a.c97c6.fffffe3a@mx.google.com> Hi Qihan face.getMaxNdnPacketSize() gives the practical limit of NDN packet length. For a Data packet, this length not only includes the Content payload, but also includes the Name, MetaInfo, and Signature. There?s no general algorithm to compute the limit of payload size, because Signature is generated after Content is prepared, and theoretically its length can depend on the Content (although all defined signing algorithms don?t do that). In most cases, it?s safe to limit your Content payload to be half of that practical limit. On the other hand, I notice a problem in ndn-ccl-api description for getMaxNdnPacketSize: This is a static method to get the practical limit of the size of a network-layer packet. If a packet is larger than this, the library or application MAY drop it. This description permits the library to drop the packet when limit is exceeded instead of crashing, but you are observing a crash. You may file a bug on the Redmine site of the specific library you are using (eg. ndn-cpp). Yours, Junxiao From: ndn ndn Sent: Sunday, August 2, 2015 06:21 To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] How to calculate max data bytes per packet? Hello everyone, Recently,I want to send a large packet via NDN.When I using NDN-CCL,face.getMaxNdnPacketSize() can get the max packet size in NDN network. But I use data.setContent() to set face.getMaxNdnPacketSize() bytes data,the program crashed,it tells me the size of data is too large than max NDN packet size. So,How to get the max data size I can send?It make me confuse for a long time. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndn at sqh.me Mon Aug 3 00:44:31 2015 From: ndn at sqh.me (ndn ndn) Date: Mon, 3 Aug 2015 15:44:31 +0800 Subject: [Ndn-interest] How to calculate max data bytes per packet? In-Reply-To: <55bed353.0a1a450a.c97c6.fffffe3a@mx.google.com> References: <55bed353.0a1a450a.c97c6.fffffe3a@mx.google.com> Message-ID: Dear Junxiao? After seen your email, I test my program again. I found I have something wrong in my memory. The problem isn't crash, It just *gives me a exception message*. I make a mistake. Sorry for that. Limit the content payload in half of practical limit can not make best efficient in transmission.Why not to set a function to get the max content payload? As a application programmer, We shoul 2015-08-03 10:34 GMT+08:00 Junxiao Shi : > Hi Qihan > > > > face.getMaxNdnPacketSize() gives the practical limit of NDN packet length. > > For a Data packet, this length not only includes the Content payload, but > also includes the Name, MetaInfo, and Signature. > > There?s no general algorithm to compute the limit of payload size, because > Signature is generated after Content is prepared, and theoretically its > length can depend on the Content (although all defined signing algorithms > don?t do that). > > In most cases, *it?s safe to limit your Content payload to be half of > that practical limit*. > > > > > > On the other hand, I notice a problem in ndn-ccl-api description for > getMaxNdnPacketSize: > > This is a static method to get the practical limit of the size of a > network-layer packet. If a packet is larger than this, the library or > application MAY drop it. > > This description permits the library to drop the packet when limit is > exceeded instead of crashing, but you are observing a crash. > > You may file a bug on the Redmine site of the specific library you are > using (eg. ndn-cpp). > > > > Yours, Junxiao > > > > > *From: *ndn ndn > *Sent: *Sunday, August 2, 2015 06:21 > *To: *ndn-interest at lists.cs.ucla.edu > *Subject: *[Ndn-interest] How to calculate max data bytes per packet? > > > > > > Hello everyone, > > Recently,I want to send a large packet via NDN.When I using > NDN-CCL,face.getMaxNdnPacketSize() can get the max packet size in NDN > network. > > But I use data.setContent() to set face.getMaxNdnPacketSize() bytes > data,the program crashed,it tells me the size of data is too large than max > NDN packet size. > > > > So,How to get the max data size I can send?It make me confuse for a long > time. > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndn at sqh.me Mon Aug 3 00:48:28 2015 From: ndn at sqh.me (ndn ndn) Date: Mon, 3 Aug 2015 15:48:28 +0800 Subject: [Ndn-interest] How to calculate max data bytes per packet? In-Reply-To: References: <55bed353.0a1a450a.c97c6.fffffe3a@mx.google.com> Message-ID: We should consider data segment,Why NDN protocol to consider it , just like IP? Sorry for make this email divided into two parts. Thank you for Junxiao. yours,qhsong 2015-08-03 15:44 GMT+08:00 ndn ndn : > Dear Junxiao? > After seen your email, I test my program again. I found I have something > wrong in my memory. The problem isn't crash, It just *gives me a > exception message*. I make a mistake. Sorry for that. > > Limit the content payload in half of practical limit can not make > best efficient in transmission.Why not to set a function to get the max > content payload? As a application programmer, We shoul > > 2015-08-03 10:34 GMT+08:00 Junxiao Shi : > >> Hi Qihan >> >> >> >> face.getMaxNdnPacketSize() gives the practical limit of NDN packet >> length. >> >> For a Data packet, this length not only includes the Content payload, but >> also includes the Name, MetaInfo, and Signature. >> >> There?s no general algorithm to compute the limit of payload size, >> because Signature is generated after Content is prepared, and theoretically >> its length can depend on the Content (although all defined signing >> algorithms don?t do that). >> >> In most cases, *it?s safe to limit your Content payload to be half of >> that practical limit*. >> >> >> >> >> >> On the other hand, I notice a problem in ndn-ccl-api description for >> getMaxNdnPacketSize: >> >> This is a static method to get the practical limit of the size of a >> network-layer packet. If a packet is larger than this, the library or >> application MAY drop it. >> >> This description permits the library to drop the packet when limit is >> exceeded instead of crashing, but you are observing a crash. >> >> You may file a bug on the Redmine site of the specific library you are >> using (eg. ndn-cpp). >> >> >> >> Yours, Junxiao >> >> >> >> >> *From: *ndn ndn >> *Sent: *Sunday, August 2, 2015 06:21 >> *To: *ndn-interest at lists.cs.ucla.edu >> *Subject: *[Ndn-interest] How to calculate max data bytes per packet? >> >> >> >> >> >> Hello everyone, >> >> Recently,I want to send a large packet via NDN.When I using >> NDN-CCL,face.getMaxNdnPacketSize() can get the max packet size in NDN >> network. >> >> But I use data.setContent() to set face.getMaxNdnPacketSize() bytes >> data,the program crashed,it tells me the size of data is too large than max >> NDN packet size. >> >> >> >> So,How to get the max data size I can send?It make me confuse for a long >> time. >> >> >> >> >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Aug 3 16:27:28 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 3 Aug 2015 16:27:28 -0700 Subject: [Ndn-interest] How to calculate max data bytes per packet? In-Reply-To: References: <55bed353.0a1a450a.c97c6.fffffe3a@mx.google.com> Message-ID: <55bff8e3.4681440a.4b19b.16f6@mx.google.com> Hi Qihan There?s no general algorithm to compute the limit of payload size, because Signature is generated after Content is prepared, and theoretically its length can depend on the Content (although all defined signing algorithms don?t do that). An application could detect the payload size by feedback loop: try different Content lengths, use a binary search to find out what?s the maximum size. I haven?t seen any application doing this, because repeatedly signing is very slow. I?ve seen ?half of 8800?; I?ve also seen ?8000 octets?. Yours, Junxiao From: ndn ndn Sent: Monday, August 3, 2015 00:44 To: Junxiao Shi Cc: ndn-interest at lists.cs.ucla.edu;ndn-lib at lists.cs.ucla.edu Subject: Re: [Ndn-interest] How to calculate max data bytes per packet? Limit the content payload in half of?practical limit can not make best?efficient in transmission.Why not to?set a function ?to get the max content payload? As a application?programmer, We should consider data segment,Why NDN protocol to consider it , just like IP? 2015-08-03 10:34 GMT+08:00 Junxiao Shi : face.getMaxNdnPacketSize() gives the practical limit of NDN packet length. For a Data packet, this length not only includes the Content payload, but also includes the Name, MetaInfo, and Signature. There?s no general algorithm to compute the limit of payload size, because Signature is generated after Content is prepared, and theoretically its length can depend on the Content (although all defined signing algorithms don?t do that). In most cases, it?s safe to limit your Content payload to be half of that practical limit.? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmmurphy at memphis.edu Thu Aug 6 11:49:27 2015 From: bmmurphy at memphis.edu (Benjamin M Murphy (bmmurphy)) Date: Thu, 6 Aug 2015 18:49:27 +0000 Subject: [Ndn-interest] NDN traffic generator hosting Message-ID: Hello all, I'm working with an in-house Android app to test performance of NFD-Android. We've been hosting the NDN traffic generator (https://github.com/named-data/ndn-traffic-generator) on one of the machines in the lab for the tests. This weights the test results a bit unfairly toward the fast end, since the testing device and server are pretty close together. Is there anybody who is currently hosting or would be willing to host the traffic generator on one of their servers to aid in testing? Thanks, Ben Murphy -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.abencherou at gmail.com Fri Aug 7 08:55:19 2015 From: a.abencherou at gmail.com (ahmed abencherou) Date: Fri, 7 Aug 2015 17:55:19 +0200 Subject: [Ndn-interest] Questions about jNDN Message-ID: Hi all, I have two questions related to jNDN: 1. Does the current version support Nack interest i.e. can I send a nack interest whether the requested content does not exist ? 2. I want to get the length of each TLV in Data packet, I means the number of bytes that type, length and value occupy. Does it provide a function to get this ? Thanks -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.ucla.edu Fri Aug 7 09:23:24 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Fri, 7 Aug 2015 16:23:24 +0000 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: Hi Ahmed, See inline. I have two questions related to jNDN: 1. Does the current version support Nack interest i.e. can I send a nack interest whether the requested content does not exist ? No not yet, 1. I want to get the length of each TLV in Data packet, I means the number of bytes that type, length and value occupy. Does it provide a function to get this ? You can get the size of the entire data packet TLV with: data.wireEncode().size() Thanks, - Jeff T -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.abencherou at gmail.com Fri Aug 7 09:36:34 2015 From: a.abencherou at gmail.com (ahmed abencherou) Date: Fri, 7 Aug 2015 18:36:34 +0200 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: Thank you Jeff But if I want to get the length of Name, MetaInfo or Signature TLVs in Data packet not the size of the entire packet?? 2015-08-07 18:23 GMT+02:00 Thompson, Jeff : > Hi Ahmed, See inline. > > I have two questions related to jNDN: > > 1. > > Does the current version support Nack interest i.e. can I send a nack > interest whether the requested content does not exist ? > > No not yet, > > 1. > > I want to get the length of each TLV in Data packet, I means the > number of bytes that type, length and value occupy. Does it provide a > function to get this ? > > You can get the size of the entire data packet TLV with: > data.wireEncode().size() > > Thanks, > - Jeff T > -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.ucla.edu Fri Aug 7 09:46:55 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Fri, 7 Aug 2015 16:46:55 +0000 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: These are not exposed in the API, as the API is abstracted from the encoding details which change frequently. May I ask why your application needs to know, for example, the MetaInfo encoding length? Maybe we can find a way to meet your application needs. (The API provides some mechanism for manipulating TLV encodings.) - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 9:36:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN Thank you Jeff But if I want to get the length of Name, MetaInfo or Signature TLVs in Data packet not the size of the entire packet?? 2015-08-07 18:23 GMT+02:00 Thompson, Jeff >: Hi Ahmed, See inline. I have two questions related to jNDN: 1. Does the current version support Nack interest i.e. can I send a nack interest whether the requested content does not exist ? No not yet, 1. I want to get the length of each TLV in Data packet, I means the number of bytes that type, length and value occupy. Does it provide a function to get this ? You can get the size of the entire data packet TLV with: data.wireEncode().size() Thanks, - Jeff T -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.abencherou at gmail.com Fri Aug 7 10:01:08 2015 From: a.abencherou at gmail.com (ahmed abencherou) Date: Fri, 7 Aug 2015 19:01:08 +0200 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: With my application, I don't want to generate a fixed length for the content field in the Data packet. So I want to know in advance the length of the other TLVs and set the content size to the remaining bytes. 2015-08-07 18:46 GMT+02:00 Thompson, Jeff : > These are not exposed in the API, as the API is abstracted from the > encoding details which change frequently. > > May I ask why your application needs to know, for example, the MetaInfo > encoding length? Maybe we can find a way to meet your application needs. > (The API provides some mechanism for manipulating TLV encodings.) > > - Jeff T > > From: ahmed abencherou > Date: Friday, August 7, 2015 at 9:36:00 > To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN > > Thank you Jeff > > But if I want to get the length of Name, MetaInfo or Signature TLVs in > Data packet not the size of the entire packet?? > > > > 2015-08-07 18:23 GMT+02:00 Thompson, Jeff : > >> Hi Ahmed, See inline. >> >> I have two questions related to jNDN: >> >> 1. >> >> Does the current version support Nack interest i.e. can I send a nack >> interest whether the requested content does not exist ? >> >> No not yet, >> >> 1. >> >> I want to get the length of each TLV in Data packet, I means the >> number of bytes that type, length and value occupy. Does it provide a >> function to get this ? >> >> You can get the size of the entire data packet TLV with: >> data.wireEncode().size() >> >> Thanks, >> - Jeff T >> > > > > -- > ABENCHEROU Ahmed > > -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.ucla.edu Fri Aug 7 10:29:58 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Fri, 7 Aug 2015 17:29:58 +0000 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: The length depends on many things, for example the length of the key name in the KeyLocator, and the length of the signature (depending on the key size of the signing key). In your application, is every data packet signed with the same key? If so, can you encode one data packet where the content is zero length, and use this as a base line? - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 10:01:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN With my application, I don't want to generate a fixed length for the content field in the Data packet. So I want to know in advance the length of the other TLVs and set the content size to the remaining bytes. 2015-08-07 18:46 GMT+02:00 Thompson, Jeff >: These are not exposed in the API, as the API is abstracted from the encoding details which change frequently. May I ask why your application needs to know, for example, the MetaInfo encoding length? Maybe we can find a way to meet your application needs. (The API provides some mechanism for manipulating TLV encodings.) - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 9:36:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN Thank you Jeff But if I want to get the length of Name, MetaInfo or Signature TLVs in Data packet not the size of the entire packet?? 2015-08-07 18:23 GMT+02:00 Thompson, Jeff >: Hi Ahmed, See inline. I have two questions related to jNDN: 1. Does the current version support Nack interest i.e. can I send a nack interest whether the requested content does not exist ? No not yet, 1. I want to get the length of each TLV in Data packet, I means the number of bytes that type, length and value occupy. Does it provide a function to get this ? You can get the size of the entire data packet TLV with: data.wireEncode().size() Thanks, - Jeff T -- ABENCHEROU Ahmed -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.abencherou at gmail.com Fri Aug 7 10:48:38 2015 From: a.abencherou at gmail.com (ahmed abencherou) Date: Fri, 7 Aug 2015 19:48:38 +0200 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: For the signature I use what is used in the following code : https://github.com/named-data/jndn/blob/master/examples/src/net/named_data/jndn/tests/TestPublishAsyncNfd.java 2015-08-07 19:29 GMT+02:00 Thompson, Jeff : > The length depends on many things, for example the length of the key name > in the KeyLocator, and the length of the signature (depending on the key > size of the signing key). In your application, is every data packet signed > with the same key? If so, can you encode one data packet where the content > is zero length, and use this as a base line? > > - Jeff T > > From: ahmed abencherou > Date: Friday, August 7, 2015 at 10:01:00 > > To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN > > With my application, I don't want to generate a fixed length for the > content field in the Data packet. > > So I want to know in advance the length of the other TLVs and set the > content size to the remaining bytes. > > 2015-08-07 18:46 GMT+02:00 Thompson, Jeff : > >> These are not exposed in the API, as the API is abstracted from the >> encoding details which change frequently. >> >> May I ask why your application needs to know, for example, the MetaInfo >> encoding length? Maybe we can find a way to meet your application needs. >> (The API provides some mechanism for manipulating TLV encodings.) >> >> - Jeff T >> >> From: ahmed abencherou >> Date: Friday, August 7, 2015 at 9:36:00 >> To: Jeff Thompson >> Cc: "ndn-interest at lists.cs.ucla.edu" >> Subject: Re: [Ndn-interest] Questions about jNDN >> >> Thank you Jeff >> >> But if I want to get the length of Name, MetaInfo or Signature TLVs in >> Data packet not the size of the entire packet?? >> >> >> >> 2015-08-07 18:23 GMT+02:00 Thompson, Jeff : >> >>> Hi Ahmed, See inline. >>> >>> I have two questions related to jNDN: >>> >>> 1. >>> >>> Does the current version support Nack interest i.e. can I send a >>> nack interest whether the requested content does not exist ? >>> >>> No not yet, >>> >>> 1. >>> >>> I want to get the length of each TLV in Data packet, I means the >>> number of bytes that type, length and value occupy. Does it provide a >>> function to get this ? >>> >>> You can get the size of the entire data packet TLV with: >>> data.wireEncode().size() >>> >>> Thanks, >>> - Jeff T >>> >> >> >> >> -- >> ABENCHEROU Ahmed >> >> > > > -- > ABENCHEROU Ahmed > > -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.ucla.edu Fri Aug 7 15:41:06 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Fri, 7 Aug 2015 22:41:06 +0000 Subject: [Ndn-interest] Questions about jNDN In-Reply-To: References: Message-ID: This signs with the same key each time, so I think you could encode one data packet where the content is zero length, and use this as a base line. Would this work for you? - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 10:48:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN For the signature I use what is used in the following code : https://github.com/named-data/jndn/blob/master/examples/src/net/named_data/jndn/tests/TestPublishAsyncNfd.java 2015-08-07 19:29 GMT+02:00 Thompson, Jeff >: The length depends on many things, for example the length of the key name in the KeyLocator, and the length of the signature (depending on the key size of the signing key). In your application, is every data packet signed with the same key? If so, can you encode one data packet where the content is zero length, and use this as a base line? - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 10:01:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN With my application, I don't want to generate a fixed length for the content field in the Data packet. So I want to know in advance the length of the other TLVs and set the content size to the remaining bytes. 2015-08-07 18:46 GMT+02:00 Thompson, Jeff >: These are not exposed in the API, as the API is abstracted from the encoding details which change frequently. May I ask why your application needs to know, for example, the MetaInfo encoding length? Maybe we can find a way to meet your application needs. (The API provides some mechanism for manipulating TLV encodings.) - Jeff T From: ahmed abencherou > Date: Friday, August 7, 2015 at 9:36:00 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Questions about jNDN Thank you Jeff But if I want to get the length of Name, MetaInfo or Signature TLVs in Data packet not the size of the entire packet?? 2015-08-07 18:23 GMT+02:00 Thompson, Jeff >: Hi Ahmed, See inline. I have two questions related to jNDN: 1. Does the current version support Nack interest i.e. can I send a nack interest whether the requested content does not exist ? No not yet, 1. I want to get the length of each TLV in Data packet, I means the number of bytes that type, length and value occupy. Does it provide a function to get this ? You can get the size of the entire data packet TLV with: data.wireEncode().size() Thanks, - Jeff T -- ABENCHEROU Ahmed -- ABENCHEROU Ahmed -- ABENCHEROU Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Sat Aug 8 08:28:57 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Sat, 8 Aug 2015 19:58:57 +0430 Subject: [Ndn-interest] (no subject) References: <4AC03A6244C3C34BB52A7EC60B799C4C03F43000@m-pdc.sbu.ac.ir> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2982@m-pdc.sbu.ac.ir> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2984@m-pdc.sbu.ac.ir> Hi again, Again about the 1st question I guess retrieving content(s) by its publisher could be some kind of a function. I'm not so familiar with details of NFN but I think that can be achieved, let alone whether such a function was not predicted in the architecture. Am I right, Christian? Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet Sent: Wed 7/29/2015 9:22 PM To: fatemeh goudarzi; ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] (no subject) Hi, With regard to question 1 I think yes. Retrieving content by publisher name/id is a kind of filter anticipated in the packet format. At least I haven't seen the latter interpretation yet, and haven't considered it. But I don't think there would be an architectural prevention for applications to answer an interest in which no specific content is defined, but a publisher id is given. Of course there may be some privacy considerations, but that is application developers' decision on what violates privacy and how to protect that. Unfortunately I have nothing to say about the 2nd question and the 3rd. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of fatemeh goudarzi Sent: Mon 7/27/2015 10:38 AM To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] (no subject) Hello everyone, I'm a newcomer to NDN and having read some basic papers, I've come to have some question mostly in the security realm: 1. It is indicated(Jacobson, et al. 2009) that retrieving a content by its publisher is possible as well as by its name. Is it some sort of security mechanism in case of retrieving data which is corrupted by someone, or some alternative for retrieving by name? If latter, is there any vision how Interest/Data is going to be like in that case? I mean it is clear how NDN works by using contents' names. Routing protocols (eg, NLSR) use names. There is also a naming convention for contents as well. But how about publishers? 2. On evidence-based security. Is it something like reputation based trust mechanisms in Bittorrent protocol? If so, how are consumers supposed know of a content's reputation or a publisher's trustworthiness? Actually I'm not sure if I perceived meaning of _secure_ link correctly. Could you elaborate on these a little bit, please? 3. Do we have a definition for the notion of _Identity framework_? As a matter of fact, I don't understand when some one(Van) says privacy and trust frameworks are semantically derived form identity model. What are the specifications, or expectations maybe, that the community has about identity framework? I will be very thankful If you could have a saying. ? Thanks, Fatemeh Goudarzi? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Sat Aug 8 12:07:42 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Sat, 8 Aug 2015 19:07:42 +0000 Subject: [Ndn-interest] NDN Video FAQ #8 on NDN Research Challenges Message-ID: Hi everyone, The NDN Video FAQ has been updated: NDN-FAQ-0008 "What are some research challenges for NDN?" - kc claffy, Principal Investigator, CAIDA https://vimeo.com/channels/ndnvfaq Best, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Sun Aug 9 06:09:08 2015 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Sun, 9 Aug 2015 13:09:08 +0000 Subject: [Ndn-interest] NDNComm Call for Student Travel Grant Application Message-ID: Travel support is available for students attending the NDN Community Meeting (NDNComm 2015) and NDN Hackathon. Funds for these travel grants are provided by the NDN Consortium. A. Travel Grant Application Grants are available only for full-time students registered for the meeting. Minority and women students from diverse institutions are particularly encouraged to apply. Preference will be given to those presenting at the meeting. To apply and compete for a travel grant, the student applicant should email the following to ndn-registration at caida.org: - The student vita - An application letter which should include: * A brief summary of the student research interests and accomplishments to date * A statement about why the NDNComm attendance is important to the student * An estimate of the following costs of attending NDNComm: airfare, hotel and meals. It is anticipated that travel grants will partially cover these costs of attendance. * A statement of whether you have registered for the meeting and proposed to present a paper, poster, etc. in the registration form (registration deadline is August 15, 2015). A recommendation letter from the advisor of the student applicant is also required. The letter should provide the following: - A confirmation that the student is a bona fide Ph.D. candidate or a M.Sc./B.Sc. student in good academic standing at the given institution. - An indication about how the student applicant would benefit from attending NDNComm. - A statement of financial commitment to pay the remainder of the student applicants' travel cost not covered by the grant. The advisor's letter should be emailed to ndn-registration at caida.org. B. Important Dates Travel Grant Application Submission Deadline: August 21, 2015 Travel Grant Award Notification: August 28, 2015 Deadline to Accept/Decline Travel Grant Award: September 4, 2015 Lan (on behalf of the NDNComm organizers) ************************************************ Lan Wang Associate Professor, Graduate Coordinator Department of Computer Science University of Memphis Memphis, TN 38152 Phone: 901-678-2727 URL: http://www.cs.memphis.edu/~lanwang *********************************************** From jburke at remap.ucla.edu Mon Aug 10 09:16:41 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Mon, 10 Aug 2015 16:16:41 +0000 Subject: [Ndn-interest] FW: [Ndn-app] Announcing ChronoChat-js v0.3, updated to use ChronoSync2013 In-Reply-To: References: Message-ID: <4229DBCF-62F0-4F6E-938D-91C123532880@remap.ucla.edu> This online example may be of interest - From: Ndn-app on behalf of "Thompson, Jeff" Date: Sunday, August 9, 2015 at 2:22 PM To: "ndn-app at lists.cs.ucla.edu" Subject: [Ndn-app] Announcing ChronoChat-js v0.3, updated to use ChronoSync2013 Hello all, ChronoChat-js is a JavaScript chat application for the browser, built on NDN-JS and using the ChronoSync protocol. https://github.com/named-data/ChronoChat-js The original ChronoChat-js code was generalized to create the ChronoSync2013 class, and ported to all the CCL libraries in C++, Python, Java and JavaScript. Its API and a description of the protocol are documented here: http://named-data.net/doc/ndn-ccl-api/chrono-sync2013.html Now to come full circle, ChronoChat-js version v0.3 has been updated to use the ChronoSync2013 class in NDN-JS. It can register with a remote NFD if NFD is configured to allow localhop. There is an online demo which uses NFD on memoria.ndn.ucla.edu. You can open two browser windows, choose two user names and give chat a try: http://named-data.net/apps/live/chat/ Thank you, - Jeff T -------------- next part -------------- An HTML attachment was scrubbed... URL: From sulfathgins at gmail.com Wed Aug 12 03:43:34 2015 From: sulfathgins at gmail.com (Sulfath Jins) Date: Wed, 12 Aug 2015 13:43:34 +0300 Subject: [Ndn-interest] ndn interest In-Reply-To: References: Message-ID: Dear.. Iam an Mphil student and like to select the subject as ndn for my research. .I have little knowledge in ndn.now I like to know some areas of ndn that i can do my Research .hope u people will help me forward. On 30 Jul 2015 07:46, wrote: Send Ndn-interest mailing list submissions to ndn-interest at lists.cs.ucla.edu To subscribe or unsubscribe via the World Wide Web, visit http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest or, via email, send a message with subject or body 'help' to ndn-interest-request at lists.cs.ucla.edu You can reach the person managing the list at ndn-interest-owner at lists.cs.ucla.edu When replying, please edit your Subject line so it is more specific than "Re: Contents of Ndn-interest digest..." Today's Topics: 1. Re: What is difference between FIB and RIB? (Spyridon (Spyros) Mastorakis) 2. Re: What is difference between FIB and RIB? (ndn ndn) 3. (no subject) (fatemeh goudarzi) 4. Re: (no subject) (Muhammad Hosain Abdollahi Sabet) 5. how to set freshnessSecond? (ndn ndn) 6. Re: how to set freshnessSecond? (Steve DiBenedetto) ---------------------------------------------------------------------- Message: 1 Date: Sun, 19 Jul 2015 22:55:29 -0700 From: "Spyridon (Spyros) Mastorakis" To: ndn ndn Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] What is difference between FIB and RIB? Message-ID: Content-Type: text/plain; charset=utf-8 Hello, I will try to elaborate on this a little bit. You can think of FIB as the FIB of IP with the following difference: Instead of IP address prefixes, it contains name prefixes and instead of a single outgoing interface, each entry may contain a list of outgoing faces. RIB stands for ?Routing Information Base? and it is mainly populated by routing protocols (e.g., NLSR). Technically speaking, RIB can also be populated by applications for prefix registration or manually by the network administrator. FIB entries come from RIB entries. That is, FIB updates are triggered by RIB updates. The goal is, based on the RIB entries, to create a consistent forwarding table. This is done by the RIB management module. One RIB update may also generate a number of FIB updates. For more technical details, I would suggest that you take a look at the latest version of the NFD developer guide: http://named-data.net/wp-content/uploads/2015/05/ndn-0021-4-nfd-developer-guide.pdf -- Spyridon (Spyros) Mastorakis Personal Website: http://cs.ucla.edu/~mastorakis/ Internet Research Laboratory PhD Computer Science UCLA > On Jul 19, 2015, at 7:39 PM, ndn ndn wrote: > > FIB is Forward Information base,I think it just like a route table in IP protocol.But I got confused when I see RIB,It seems like FIB.So, What difference between them? > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest ------------------------------ Message: 2 Date: Mon, 20 Jul 2015 14:45:40 +0800 From: ndn ndn To: "Spyridon (Spyros) Mastorakis" Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] What is difference between FIB and RIB? Message-ID: Content-Type: text/plain; charset="utf-8" The explain is clear,I think I understand it.I will read NFD developer guide for find more information. BTW: if I run command nfdc create or nfd-autoreg,is it means that application will add a route entry in RIB not FIB.And after that, FIB was updated by RIB trigger. thanks for your reply. 2015-07-20 13:55 GMT+08:00 Spyridon (Spyros) Mastorakis < spiros.mastorakis at gmail.com>: > Hello, > > I will try to elaborate on this a little bit. > > You can think of FIB as the FIB of IP with the following difference: > > Instead of IP address prefixes, it contains name prefixes and instead of a > single outgoing interface, each entry may contain a list of outgoing faces. > > RIB stands for ?Routing Information Base? and it is mainly populated by > routing protocols (e.g., NLSR). Technically speaking, RIB can also be > populated by applications for prefix registration or manually by the > network administrator. > > FIB entries come from RIB entries. That is, FIB updates are triggered by > RIB updates. The goal is, based on the RIB entries, to create a consistent > forwarding table. This is done by the RIB management module. One RIB update > may also generate a number of FIB updates. > > For more technical details, I would suggest that you take a look at the > latest version of the NFD developer guide: > > > http://named-data.net/wp-content/uploads/2015/05/ndn-0021-4-nfd-developer-guide.pdf > > -- > Spyridon (Spyros) Mastorakis > Personal Website: http://cs.ucla.edu/~mastorakis/ > Internet Research Laboratory > PhD Computer Science > UCLA > > > > > > On Jul 19, 2015, at 7:39 PM, ndn ndn wrote: > > > > FIB is Forward Information base,I think it just like a route table in IP > protocol.But I got confused when I see RIB,It seems like FIB.So, What > difference between them? > > _______________________________________________ > > 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/20150720/f4984f0a/attachment-0001.html > ------------------------------ Message: 3 Date: Mon, 27 Jul 2015 10:38:48 +0430 From: "fatemeh goudarzi" To: Subject: [Ndn-interest] (no subject) Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03F43000 at m-pdc.sbu.ac.ir> Content-Type: text/plain; charset="iso-8859-1" Hello everyone, I'm a newcomer to NDN and having read some basic papers, I've come to have some question mostly in the security realm: 1. It is indicated(Jacobson, et al. 2009) that retrieving a content by its publisher is possible as well as by its name. Is it some sort of security mechanism in case of retrieving data which is corrupted by someone, or some alternative for retrieving by name? If latter, is there any vision how Interest/Data is going to be like in that case? I mean it is clear how NDN works by using contents' names. Routing protocols (eg, NLSR) use names. There is also a naming convention for contents as well. But how about publishers? 2. On evidence-based security. Is it something like reputation based trust mechanisms in Bittorrent protocol? If so, how are consumers supposed know of a content's reputation or a publisher's trustworthiness? Actually I'm not sure if I perceived meaning of _secure_ link correctly. Could you elaborate on these a little bit, please? 3. Do we have a definition for the notion of _Identity framework_? As a matter of fact, I don't understand when some one(Van) says privacy and trust frameworks are semantically derived form identity model. What are the specifications, or expectations maybe, that the community has about identity framework? I will be very thankful If you could have a saying. ? Thanks, Fatemeh Goudarzi? -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150727/b405560b/attachment-0001.html > ------------------------------ Message: 4 Date: Wed, 29 Jul 2015 21:22:47 +0430 From: "Muhammad Hosain Abdollahi Sabet" To: "fatemeh goudarzi" , Subject: Re: [Ndn-interest] (no subject) Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2982 at m-pdc.sbu.ac.ir> Content-Type: text/plain; charset="iso-8859-1" Hi, With regard to question 1 I think yes. Retrieving content by publisher name/id is a kind of filter anticipated in the packet format. At least I haven't seen the latter interpretation yet, and haven't considered it. But I don't think there would be an architectural prevention for applications to answer an interest in which no specific content is defined, but a publisher id is given. Of course there may be some privacy considerations, but that is application developers' decision on what violates privacy and how to protect that. Unfortunately I have nothing to say about the 2nd question and the 3rd. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of fatemeh goudarzi Sent: Mon 7/27/2015 10:38 AM To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] (no subject) Hello everyone, I'm a newcomer to NDN and having read some basic papers, I've come to have some question mostly in the security realm: 1. It is indicated(Jacobson, et al. 2009) that retrieving a content by its publisher is possible as well as by its name. Is it some sort of security mechanism in case of retrieving data which is corrupted by someone, or some alternative for retrieving by name? If latter, is there any vision how Interest/Data is going to be like in that case? I mean it is clear how NDN works by using contents' names. Routing protocols (eg, NLSR) use names. There is also a naming convention for contents as well. But how about publishers? 2. On evidence-based security. Is it something like reputation based trust mechanisms in Bittorrent protocol? If so, how are consumers supposed know of a content's reputation or a publisher's trustworthiness? Actually I'm not sure if I perceived meaning of _secure_ link correctly. Could you elaborate on these a little bit, please? 3. Do we have a definition for the notion of _Identity framework_? As a matter of fact, I don't understand when some one(Van) says privacy and trust frameworks are semantically derived form identity model. What are the specifications, or expectations maybe, that the community has about identity framework? I will be very thankful If you could have a saying. ? Thanks, Fatemeh Goudarzi? -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150729/308beab9/attachment-0001.html > ------------------------------ Message: 5 Date: Thu, 30 Jul 2015 09:58:38 +0800 From: ndn ndn To: "ndn-interest at lists.cs.ucla.edu" Subject: [Ndn-interest] how to set freshnessSecond? Message-ID: Content-Type: text/plain; charset="utf-8" Hello everyone, I'm using NDN-CCL to writing a NDN application. But I find a problem about data cache. In NDN network ,all data can store in CS.But in my application,some content always changing in 5 seconds,so I think setting a freshnessSecond will help me solve this problem. I try to setMustBefresh value,but it not works.The app also receive the cached value. But in NDN-CCL,I didn't find any method to set this?how to set it? hope you give me some reply. thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150730/fe7ed144/attachment-0001.html > ------------------------------ Message: 6 Date: Wed, 29 Jul 2015 20:15:40 -0600 From: Steve DiBenedetto To: ndn ndn Cc: "ndn-interest at lists.cs.ucla.edu" Subject: Re: [Ndn-interest] how to set freshnessSecond? Message-ID: Content-Type: text/plain; charset="utf-8" On Wed, Jul 29, 2015 at 7:58 PM, ndn ndn wrote: > Hello everyone, > I'm using NDN-CCL to writing a NDN application. But I find a problem about > data cache. > In NDN network ,all data can store in CS.But in my application,some > content always changing in 5 seconds,so I think setting a freshnessSecond > will help me solve this problem. > I try to setMustBefresh value,but it not works.The app also receive the > cached value. > But in NDN-CCL,I didn't find any method to set this?how to set it? > > hope you give me some reply. > > thanks. > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > Please correct me if I'm wrong, but it sounds like you're trying to ensure the retrieving application always gets the latest data. "Must be fresh" tells NDN nodes to to return Data that have not yet expired. Data with a freshness period of 5 seconds will satisfy a "must be fresh" Interests for 5 seconds. The timer is with respect to when the Data arrived at the node. Depending on the details of your application, you can try a couple things: 1. Set a conservative freshness period (e.g. 1 second). This will result in more Interests reaching the publisher, but mitigate stale Data retrieval. 2. Minimize the freshness period (e.g. 0 ms) so that the content is effectively never fresh. You can combine either approach with the CCL's publisher cache: http://named-data.net/doc/ndn-ccl-api/memory-content-cache.html . Your application can insert Data packets into this application content cache and then query it as Interests arrive. Note, you may need to set the cleanup timer value to something big to prevent it from removing the technically stale Data packets. However, this should simplify the publisher's implementation and keeping your consumers up to date. Hope that helps, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150729/f79d39e8/attachment.html > ------------------------------ Subject: Digest Footer _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest ------------------------------ End of Ndn-interest Digest, Vol 16, Issue 6 ******************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Thu Aug 13 04:20:49 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Thu, 13 Aug 2015 15:50:49 +0430 Subject: [Ndn-interest] topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2986@m-pdc.sbu.ac.ir> Hi, There are some summarized explanations about NDNFit in annual progress report 2015 which I'm not sure if I've understood well. I've seen https://github.com/remap/ndn-netenv-techreports/blob/master/Open_mHealth/ndn-netenv-Open_mHealth.pdf too, but that is an older version. There is this notion of _topology-independent namespace_ in 2.6 which is a mean to allow mobile producers to publish contents without the need for changing prefixes. According to Fig.2.6 b this namespace would be􀀗􀀄 _org/openmhealth_. In 2.2.1 there is a mention of _autoconfiguration support_, the NDN equivalent for DHCP. Fig. 2.7 says it's going to _provide temporary namespace and key for publishing while roaming._ First, what is the difference between topology independent and this temporary namespaces? Second, Is this service going to be an application specific and how to find the correspondent server would be preconfigured? There are some other questions which are dependent to answers of the ones above. Thanks, Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Thu Aug 13 09:13:13 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Thu, 13 Aug 2015 16:13:13 +0000 Subject: [Ndn-interest] topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2986@m-pdc.sbu.ac.ir> References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2986@m-pdc.sbu.ac.ir> Message-ID: Sabet, A good starting point for the current auto-configuration support is here: http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.html There are some plans to extend it in the future, which I imagine will be documented in a future tech report. In some scenarios, auto configuration could be envisioned to provide a device with one or more namespaces under which it can publish and have interests from the global internet (or the enterprise, or...) reach it. This is I think what a "temporary" namespace referred to in this case. The term "topology-independent" was used in this use case to describe a namespace used for mhealth data that may or may not be globally routable. It could be communicated by 1) globally routing the namespace 2) using the namespace in local communication 3) encapsulating data named using it within one or more globally routable namespaces and using a link-type object to provide one level of indirection for requestors. The motivation in the Open mHealth scenario is to created a long-lived namespace that is provider-independent (analogous, say, to registering a domain or subdomain but being able to switch hosting provider). This is early work and will be fleshed out further in the coming months. How these types of namespaces could be used together in something like the Open mHealth scenario is a little more involved and something that hopefully will be written up in a tech report later in the Fall. Jeff From: Muhammad Hosain Abdollahi Sabet Date: Thursday, August 13, 2015 at 4:20 AM To: "ndn-interest at lists.cs.ucla.edu", Jeff Burke Subject: topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. Hi, There are some summarized explanations about NDNFit in annual progress report 2015 which I'm not sure if I've understood well. I've seen https://github.com/remap/ndn-netenv-techreports/blob/master/Open_mHealth/ndn-netenv-Open_mHealth.pdf too, but that is an older version. There is this notion of _topology-independent namespace_ in 2.6 which is a mean to allow mobile producers to publish contents without the need for changing prefixes. According to Fig.2.6 b this namespace would be􀀗􀀄 _org/openmhealth_. In 2.2.1 there is a mention of _autoconfiguration support_, the NDN equivalent for DHCP. Fig. 2.7 says it's going to _provide temporary namespace and key for publishing while roaming._ First, what is the difference between topology independent and this temporary namespaces? Second, Is this service going to be an application specific and how to find the correspondent server would be preconfigured? There are some other questions which are dependent to answers of the ones above. Thanks, Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.h.ahmed at ieee.org Thu Aug 13 23:10:28 2015 From: s.h.ahmed at ieee.org (Syed Hassan Ahmed) Date: Fri, 14 Aug 2015 02:10:28 -0400 Subject: [Ndn-interest] Few New Contributions Message-ID: Dear All, I hope this short email will find you in the best of your health and work. Today, I would like to share a few of the latest articles published in the field of vehicular ICN/CCN/NDN: [1] Syed Hassan Ahmed, Safdar Hussain Bouk and Dongkyun Kim ?RUFS: RobUst Forwarder Selection in Vehicular Content-centric Networks? IEEE Communications Letters, July, 2015. http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392 [2] S. H. Bouk, Syed Hassan Ahmed and Dongkyun Kim "Vehicular Content Centric Network (VCCN): A Survey and Research Challenges" ACM Symposium on Applied Computing, (ACM SAC), Salamanca, Spain, 2015. http://dl.acm.org/citation.cfm?doid=2695664.2695844? [3] S. H. Bouk, Syed Hassan Ahmed and Dongkyun Kim "Hierarchical and Hash-based Naming Scheme for Vehicular Information Centric Networks", IEEE International Conference on Connected Vehicles and Expo, (ICCVE), Austria, 2014. ?In addition, I would like to request honorable NDN web page organizers/leaders to let these papers and upcoming papers from my side on their website and also I would like to request to let me know the path to be a part of this future internet community. Since, I am looking forward to have my career in this research field. Thanks advance for the positive feedback from the community and senior members. ? Kind Regards, ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ *Syed Hassan Ahmed* ??? ?? ???? PhD Research Scholar, MoNeT Wireless Lab, Kyungpook National University, Daegu City, Republic of Korea. Cell: +82-10-9883-0786 https://sites.google.com/site/shahmedknu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Sat Aug 15 05:11:49 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Sat, 15 Aug 2015 16:41:49 +0430 Subject: [Ndn-interest] ndn interest Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2988@m-pdc.sbu.ac.ir> Hi Sulfath, Actually there are many interesting areas to focus on. Maybe you'd better take a look at some basic works. If you've seen 2009 paper, then I suggest you to take a look at these two, to keep up with current research directions. http://named-data.net/wp-content/uploads/2014/10/named_data_networking_ccr.pdf http://named-data.net/wp-content/uploads/2015/06/ndn-ar2015.pdf Thanks, Sabet. ?? On Wed, Aug 12, 2015 at 3:13 PM, Sulfath Jins wrote: Dear.. Iam an Mphil student and like to select the subject as ndn for my research. .I have little knowledge in ndn.now I like to know some areas of ndn that i can do my Research .hope u people will help me forward. On 30 Jul 2015 07:46, wrote: Send Ndn-interest mailing list submissions to ndn-interest at lists.cs.ucla.edu To subscribe or unsubscribe via the World Wide Web, visit http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest or, via email, send a message with subject or body 'help' to ndn-interest-request at lists.cs.ucla.edu You can reach the person managing the list at ndn-interest-owner at lists.cs.ucla.edu When replying, please edit your Subject line so it is more specific than "Re: Contents of Ndn-interest digest..." Today's Topics: 1. Re: What is difference between FIB and RIB? (Spyridon (Spyros) Mastorakis) 2. Re: What is difference between FIB and RIB? (ndn ndn) 3. (no subject) (fatemeh goudarzi) 4. Re: (no subject) (Muhammad Hosain Abdollahi Sabet) 5. how to set freshnessSecond? (ndn ndn) 6. Re: how to set freshnessSecond? (Steve DiBenedetto) ---------------------------------------------------------------------- Message: 1 Date: Sun, 19 Jul 2015 22:55:29 -0700 From: "Spyridon (Spyros) Mastorakis" To: ndn ndn Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] What is difference between FIB and RIB? Message-ID: Content-Type: text/plain; charset=utf-8 Hello, I will try to elaborate on this a little bit. You can think of FIB as the FIB of IP with the following difference: Instead of IP address prefixes, it contains name prefixes and instead of a single outgoing interface, each entry may contain a list of outgoing faces. RIB stands for ?Routing Information Base? and it is mainly populated by routing protocols (e.g., NLSR). Technically speaking, RIB can also be populated by applications for prefix registration or manually by the network administrator. FIB entries come from RIB entries. That is, FIB updates are triggered by RIB updates. The goal is, based on the RIB entries, to create a consistent forwarding table. This is done by the RIB management module. One RIB update may also generate a number of FIB updates. For more technical details, I would suggest that you take a look at the latest version of the NFD developer guide: http://named-data.net/wp-content/uploads/2015/05/ndn-0021-4-nfd-developer-guide.pdf -- Spyridon (Spyros) Mastorakis Personal Website: http://cs.ucla.edu/~mastorakis/ Internet Research Laboratory PhD Computer Science UCLA > On Jul 19, 2015, at 7:39 PM, ndn ndn wrote: > > FIB is Forward Information base,I think it just like a route table in IP protocol.But I got confused when I see RIB,It seems like FIB.So, What difference between them? > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest ------------------------------ Message: 2 Date: Mon, 20 Jul 2015 14:45:40 +0800 From: ndn ndn To: "Spyridon (Spyros) Mastorakis" Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] What is difference between FIB and RIB? Message-ID: Content-Type: text/plain; charset="utf-8" The explain is clear,I think I understand it.I will read NFD developer guide for find more information. BTW: if I run command nfdc create or nfd-autoreg,is it means that application will add a route entry in RIB not FIB.And after that, FIB was updated by RIB trigger. thanks for your reply. 2015-07-20 13:55 GMT+08:00 Spyridon (Spyros) Mastorakis < spiros.mastorakis at gmail.com>: > Hello, > > I will try to elaborate on this a little bit. > > You can think of FIB as the FIB of IP with the following difference: > > Instead of IP address prefixes, it contains name prefixes and instead of a > single outgoing interface, each entry may contain a list of outgoing faces. > > RIB stands for ?Routing Information Base? and it is mainly populated by > routing protocols (e.g., NLSR). Technically speaking, RIB can also be > populated by applications for prefix registration or manually by the > network administrator. > > FIB entries come from RIB entries. That is, FIB updates are triggered by > RIB updates. The goal is, based on the RIB entries, to create a consistent > forwarding table. This is done by the RIB management module. One RIB update > may also generate a number of FIB updates. > > For more technical details, I would suggest that you take a look at the > latest version of the NFD developer guide: > > > http://named-data.net/wp-content/uploads/2015/05/ndn-0021-4-nfd-developer-guide.pdf > > -- > Spyridon (Spyros) Mastorakis > Personal Website: http://cs.ucla.edu/~mastorakis/ > Internet Research Laboratory > PhD Computer Science > UCLA > > > > > > On Jul 19, 2015, at 7:39 PM, ndn ndn wrote: > > > > FIB is Forward Information base,I think it just like a route table in IP > protocol.But I got confused when I see RIB,It seems like FIB.So, What > difference between them? > > _______________________________________________ > > 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: ------------------------------ Message: 3 Date: Mon, 27 Jul 2015 10:38:48 +0430 From: "fatemeh goudarzi" To: Subject: [Ndn-interest] (no subject) Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03F43000 at m-pdc.sbu.ac.ir> Content-Type: text/plain; charset="iso-8859-1" Hello everyone, I'm a newcomer to NDN and having read some basic papers, I've come to have some question mostly in the security realm: 1. It is indicated(Jacobson, et al. 2009) that retrieving a content by its publisher is possible as well as by its name. Is it some sort of security mechanism in case of retrieving data which is corrupted by someone, or some alternative for retrieving by name? If latter, is there any vision how Interest/Data is going to be like in that case? I mean it is clear how NDN works by using contents' names. Routing protocols (eg, NLSR) use names. There is also a naming convention for contents as well. But how about publishers? 2. On evidence-based security. Is it something like reputation based trust mechanisms in Bittorrent protocol? If so, how are consumers supposed know of a content's reputation or a publisher's trustworthiness? Actually I'm not sure if I perceived meaning of _secure_ link correctly. Could you elaborate on these a little bit, please? 3. Do we have a definition for the notion of _Identity framework_? As a matter of fact, I don't understand when some one(Van) says privacy and trust frameworks are semantically derived form identity model. What are the specifications, or expectations maybe, that the community has about identity framework? I will be very thankful If you could have a saying. ? Thanks, Fatemeh Goudarzi? -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Wed, 29 Jul 2015 21:22:47 +0430 From: "Muhammad Hosain Abdollahi Sabet" To: "fatemeh goudarzi" , Subject: Re: [Ndn-interest] (no subject) Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2982 at m-pdc.sbu.ac.ir> Content-Type: text/plain; charset="iso-8859-1" Hi, With regard to question 1 I think yes. Retrieving content by publisher name/id is a kind of filter anticipated in the packet format. At least I haven't seen the latter interpretation yet, and haven't considered it. But I don't think there would be an architectural prevention for applications to answer an interest in which no specific content is defined, but a publisher id is given. Of course there may be some privacy considerations, but that is application developers' decision on what violates privacy and how to protect that. Unfortunately I have nothing to say about the 2nd question and the 3rd. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of fatemeh goudarzi Sent: Mon 7/27/2015 10:38 AM To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] (no subject) Hello everyone, I'm a newcomer to NDN and having read some basic papers, I've come to have some question mostly in the security realm: 1. It is indicated(Jacobson, et al. 2009) that retrieving a content by its publisher is possible as well as by its name. Is it some sort of security mechanism in case of retrieving data which is corrupted by someone, or some alternative for retrieving by name? If latter, is there any vision how Interest/Data is going to be like in that case? I mean it is clear how NDN works by using contents' names. Routing protocols (eg, NLSR) use names. There is also a naming convention for contents as well. But how about publishers? 2. On evidence-based security. Is it something like reputation based trust mechanisms in Bittorrent protocol? If so, how are consumers supposed know of a content's reputation or a publisher's trustworthiness? Actually I'm not sure if I perceived meaning of _secure_ link correctly. Could you elaborate on these a little bit, please? 3. Do we have a definition for the notion of _Identity framework_? As a matter of fact, I don't understand when some one(Van) says privacy and trust frameworks are semantically derived form identity model. What are the specifications, or expectations maybe, that the community has about identity framework? I will be very thankful If you could have a saying. ? Thanks, Fatemeh Goudarzi? -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 5 Date: Thu, 30 Jul 2015 09:58:38 +0800 From: ndn ndn To: "ndn-interest at lists.cs.ucla.edu" Subject: [Ndn-interest] how to set freshnessSecond? Message-ID: Content-Type: text/plain; charset="utf-8" Hello everyone, I'm using NDN-CCL to writing a NDN application. But I find a problem about data cache. In NDN network ,all data can store in CS.But in my application,some content always changing in 5 seconds,so I think setting a freshnessSecond will help me solve this problem. I try to setMustBefresh value,but it not works.The app also receive the cached value. But in NDN-CCL,I didn't find any method to set this?how to set it? hope you give me some reply. thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 6 Date: Wed, 29 Jul 2015 20:15:40 -0600 From: Steve DiBenedetto To: ndn ndn Cc: "ndn-interest at lists.cs.ucla.edu" Subject: Re: [Ndn-interest] how to set freshnessSecond? Message-ID: Content-Type: text/plain; charset="utf-8" On Wed, Jul 29, 2015 at 7:58 PM, ndn ndn wrote: > Hello everyone, > I'm using NDN-CCL to writing a NDN application. But I find a problem about > data cache. > In NDN network ,all data can store in CS.But in my application,some > content always changing in 5 seconds,so I think setting a freshnessSecond > will help me solve this problem. > I try to setMustBefresh value,but it not works.The app also receive the > cached value. > But in NDN-CCL,I didn't find any method to set this?how to set it? > > hope you give me some reply. > > thanks. > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > Please correct me if I'm wrong, but it sounds like you're trying to ensure the retrieving application always gets the latest data. "Must be fresh" tells NDN nodes to to return Data that have not yet expired. Data with a freshness period of 5 seconds will satisfy a "must be fresh" Interests for 5 seconds. The timer is with respect to when the Data arrived at the node. Depending on the details of your application, you can try a couple things: 1. Set a conservative freshness period (e.g. 1 second). This will result in more Interests reaching the publisher, but mitigate stale Data retrieval. 2. Minimize the freshness period (e.g. 0 ms) so that the content is effectively never fresh. You can combine either approach with the CCL's publisher cache: http://named-data.net/doc/ndn-ccl-api/memory-content-cache.html . Your application can insert Data packets into this application content cache and then query it as Interests arrive. Note, you may need to set the cleanup timer value to something big to prevent it from removing the technically stale Data packets. However, this should simplify the publisher's implementation and keeping your consumers up to date. Hope that helps, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest ------------------------------ End of Ndn-interest Digest, Vol 16, Issue 6 ******************************************* _______________________________________________ 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: From a.abencherou at gmail.com Mon Aug 17 11:33:32 2015 From: a.abencherou at gmail.com (ahmed abencherou) Date: Mon, 17 Aug 2015 20:33:32 +0200 Subject: [Ndn-interest] NDN over Ethernet Message-ID: Hi all, Can an NDN application send data directly over Ethernet ? If yes which version of NFD does support this feature ? Thanks. -- Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Aug 17 21:14:34 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 17 Aug 2015 21:14:34 -0700 Subject: [Ndn-interest] NDN over Ethernet In-Reply-To: References: Message-ID: <55d2b12e.c385460a.beb8.ffffcc11@mx.google.com> Hi Ahmed NFD 0.3 contain EthernetFace and is capable of multicast communication directly over Ethernet. If you type ?nfd-status -f?, you may see an ?ether:? multi-access face for every NIC that is capable of Ethernet communication. Register a route onto one of those faces with ?nfdc register / ? would allow you to send Interest onto and receive Data from an EthernetFace. Yours, Junxiao From: ahmed abencherou Sent: Monday, August 17, 2015 11:35 To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] NDN over Ethernet Hi all, Can an NDN application send data directly over Ethernet ? If yes which version of NFD does support this feature ? Thanks. -- Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From ray.vanbrandenburg at tno.nl Wed Aug 19 11:12:18 2015 From: ray.vanbrandenburg at tno.nl (Brandenburg, R. (Ray) van) Date: Wed, 19 Aug 2015 18:12:18 +0000 Subject: [Ndn-interest] Multiple Ethernet faces Message-ID: Hi, I've been playing around with NDN Ethernet support and bumped into two issues. 1) If I have a machine with multiple NICs, NFD will list them as separate faces (since they have different local endpoints). However, they will have the same remote endpoint, i.e the ethernet multicast address listed in nfd.conf. Is there anyway to make sure each Ethernet face has it's own distinct multicast address? 2) I'd like to run NLSR directly over Ethernet. Since the conf file only allows me to specify face-uri per neighbor (instead of face-id), and doesn't support 'dev://ethX' scheme, I thought to use the 'ether://' scheme to specify the face I'd like to use for a particular neighbor. However, when I do that, NLSR tries to create that face, which fails since NFD doesn't allow one to create Ethernet faces. The same problem occurs irrespective of whether I use the ethernet multicast address as listed in NFD or the actual hardware ethernet address. I was expecting NLSR to only try to create a face if it doesn't already exist. Is this intended behavior, or am I doing something wrong? Is there any other way of using NLSR over Ethernet? Thanks! Ray This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. From dibenede at cs.colostate.edu Wed Aug 19 19:57:14 2015 From: dibenede at cs.colostate.edu (Steve DiBenedetto) Date: Wed, 19 Aug 2015 20:57:14 -0600 Subject: [Ndn-interest] NDNcomm 2015 Hackathon Call for Projects Message-ID: NDNcomm 2015 Hackathon Call for Projects Proposals Due: Aug. 31, 2015. Hackathon: Sept. 26-27, 2015. The NDNcomm 2015 Hackathon solicits project proposals that advance the state of NDN. We are looking for projects that: * directly address a research need, * create new NDN tools or modify existing tools, and/or * create or improve documentation and how-to guides. Participants will have approximately 12 hours to work on the projects (see http://ndncomm.github.io for additional details). - How open-ended should proposals be? - Ideally, project proposals should include room for discussion and cooperative design during the hackathon, but may be entirely planned in advance (e.g. a new NFD feature). We ask that proposals avoid larger projects that are completely open to design. The significance of the contribution is more important than spectacle. - Who will work on the projects? - Hackathon projects will be developed by small teams (< 8) and should be able to show measurable progress after two days. Participants will be encouraged to regroup and refresh overnight. The hackathon welcomes all interested participants, regardless of NDN experience, so we are seeking projects that are suitable for experienced NDN developers as well as those approachable by newcomers. For example, a project could decompose into tasks of varying skill levels or, alternatively, be specifically targeted. - What languages, libraries, etc. are allowed? - Project proposals should declare any programming language, library, platform requirements, and so forth. For new projects, we ask you to consider how the specifics, such as language choice, may impact the ability to attract participants. The hackathon organizers will provide proposal feedback and assistance to ensure projects have a concrete path to implementation. - If I propose a project, do I have to go to the Hackathon? - Proposals must specify one or more representatives who will attend the hackathon to pitch their idea and guide its development over the duration of the hackathon (hacking optional). Representatives will have 10 minutes to present their idea to attendees at the event opening. The pitch should emphasize the project's motivation and use cases. - FORMAT - Proposals should adhere to the following format: * 1 page max. (plain text) * contact information of submitters * contact information of project representative(s) * distinct sections for the: * motivation, * approach and/or concept, * contributions to NDN, * functional requirements, and * metrics (how progress can be measured). Please remember that participants will have a limited amount of time (see http://ndncomm.github.io) to work on their project. All proposals will be reviewed by the hackathon organizers. Projects will be judged by a panel (TBD) for the ?Best of Hackathon? prize. We hope that the hackathon will be a fun event for all and that projects will lead to collaborations extending beyond NDNcomm. - DEADLINE - Email proposal to ndncomm2015-hackathon at named-data.net Proposal submission deadline: Monday, August 31, 2015 Notification: Monday, September 7, 2015 - Hackathon Information and Schedule - Website: http://ndncomm.github.io Solicitation: https://docs.google.com/document/d/1zoqb8_IzEirISS5vJqUB2qpBlq8vFXE_T6DLwS1gdyw/edit?usp=sharing Open: Saturday, September 26, 2015 @ 9am - 8pm Close: Sunday, September 27, 2015 @ 9am - 6pm Judging & Awards: Sunday, September 27, 2015 @ 6pm - 8pm Post Projects on Website: Monday, September 28, 2015 - Organizers - Alex Afanasyev (UCLA) Steve DiBenedetto (Colorado State University) Vince Lehman (University of Memphis) Jeff Thompson (UCLA) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Wed Aug 19 22:03:53 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Thu, 20 Aug 2015 05:03:53 +0000 Subject: [Ndn-interest] NDN over Ethernet In-Reply-To: <55d2b12e.c385460a.beb8.ffffcc11@mx.google.com> References: <55d2b12e.c385460a.beb8.ffffcc11@mx.google.com> Message-ID: Hi Junxiao, Can you please provide a pointer to the documentation where one can learn such things? Jeff From: Ndn-interest on behalf of Junxiao Shi Date: Monday, August 17, 2015 at 9:14 PM To: ahmed abencherou, "ndn-interest at lists.cs.ucla.edu" Subject: Re: [Ndn-interest] NDN over Ethernet Hi Ahmed NFD 0.3 contain EthernetFace and is capable of multicast communication directly over Ethernet. If you type ?nfd-status -f?, you may see an ?ether:? multi-access face for every NIC that is capable of Ethernet communication. Register a route onto one of those faces with ?nfdc register / ? would allow you to send Interest onto and receive Data from an EthernetFace. Yours, Junxiao From: ahmed abencherou Sent: Monday, August 17, 2015 11:35 To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] NDN over Ethernet Hi all, Can an NDN application send data directly over Ethernet ? If yes which version of NFD does support this feature ? Thanks. -- Ahmed -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Thu Aug 20 07:16:43 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Thu, 20 Aug 2015 18:46:43 +0430 Subject: [Ndn-interest] topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2986@m-pdc.sbu.ac.ir> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC298B@m-pdc.sbu.ac.ir> Jeff, Thanks for the reference. So I suppose there should be something like using method 3 mentioned in the link. Then the node will obtain a topology-independent prefix mentioned earlier to have the ability to publish data and be accessed from local or global(via NDNS and Link obj) network, right? Since the publisher mobility is my focus, I'm more interested in dealing with topology-independent namespaces. As far as I understand, topology-independency, which brings us naming consistency -and that's crucial for publisher mobility- is achieved in the cost of having non-aggregatable names. So we will probably have some prefixes(for other applications like mHealth) in intermediate FIBs which each of those are responsible -in the worst case- maybe just for one user, right? Isn't it sound more burden on routing system? Are these topology-independent names FIB records going to have lifetime or something? If not so, with publisher being relocated, interests may be routed to invalid paths. p.s: What is the need for encapsulating data packets? Data packets could return following breadcrumbs. Previous versions of SNAMP talks about encapsulating _Interest_ packets, which is disregarded in the last version. Thanks, Sabet -----Original Message----- From: Burke, Jeff [mailto:jburke at remap.ucla.edu] Sent: Thu 8/13/2015 8:43 PM To: Muhammad Hosain Abdollahi Sabet; ndn-interest at lists.cs.ucla.edu Subject: Re: topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. Sabet, A good starting point for the current auto-configuration support is here: http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.html There are some plans to extend it in the future, which I imagine will be documented in a future tech report. In some scenarios, auto configuration could be envisioned to provide a device with one or more namespaces under which it can publish and have interests from the global internet (or the enterprise, or...) reach it. This is I think what a "temporary" namespace referred to in this case. The term "topology-independent" was used in this use case to describe a namespace used for mhealth data that may or may not be globally routable. It could be communicated by 1) globally routing the namespace 2) using the namespace in local communication 3) encapsulating data named using it within one or more globally routable namespaces and using a link-type object to provide one level of indirection for requestors. The motivation in the Open mHealth scenario is to created a long-lived namespace that is provider-independent (analogous, say, to registering a domain or subdomain but being able to switch hosting provider). This is early work and will be fleshed out further in the coming months. How these types of namespaces could be used together in something like the Open mHealth scenario is a little more involved and something that hopefully will be written up in a tech report later in the Fall. Jeff From: Muhammad Hosain Abdollahi Sabet Date: Thursday, August 13, 2015 at 4:20 AM To: "ndn-interest at lists.cs.ucla.edu", Jeff Burke Subject: topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit. Hi, There are some summarized explanations about NDNFit in annual progress report 2015 which I'm not sure if I've understood well. I've seen https://github.com/remap/ndn-netenv-techreports/blob/master/Open_mHealth/ndn-netenv-Open_mHealth.pdf too, but that is an older version. There is this notion of _topology-independent namespace_ in 2.6 which is a mean to allow mobile producers to publish contents without the need for changing prefixes. According to Fig.2.6 b this namespace would be􀀗􀀄 _org/openmhealth_. In 2.2.1 there is a mention of _autoconfiguration support_, the NDN equivalent for DHCP. Fig. 2.7 says it's going to _provide temporary namespace and key for publishing while roaming._ First, what is the difference between topology independent and this temporary namespaces? Second, Is this service going to be an application specific and how to find the correspondent server would be preconfigured? There are some other questions which are dependent to answers of the ones above. Thanks, Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Thu Aug 20 15:57:53 2015 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Thu, 20 Aug 2015 22:57:53 +0000 Subject: [Ndn-interest] Multiple Ethernet faces In-Reply-To: References: Message-ID: <67D90752-2144-4B5A-B084-D09ECEC1E4AE@memphis.edu> Hi Ray, I can try to answer the second question. Currently, NLSR does indeed try to create a Face regardless of type; in the case of EthernetFace, this causes the error you see. So I think it is not an error on your part, but instead a logic error in NLSR. Instead, NLSR should query for the FaceId associated with the Ethernet hardware address. If a FaceId is returned, NLSR should use the existing Face instead of attempting to create a new one. Maybe someone more familiar with Face management in NFD can confirm. -- Vince Lehman On Aug 19, 2015, at 1:12 PM, Brandenburg, R. (Ray) van > wrote: Hi, I've been playing around with NDN Ethernet support and bumped into two issues. 1) If I have a machine with multiple NICs, NFD will list them as separate faces (since they have different local endpoints). However, they will have the same remote endpoint, i.e the ethernet multicast address listed in nfd.conf. Is there anyway to make sure each Ethernet face has it's own distinct multicast address? 2) I'd like to run NLSR directly over Ethernet. Since the conf file only allows me to specify face-uri per neighbor (instead of face-id), and doesn't support 'dev://ethX' scheme, I thought to use the 'ether://' scheme to specify the face I'd like to use for a particular neighbor. However, when I do that, NLSR tries to create that face, which fails since NFD doesn't allow one to create Ethernet faces. The same problem occurs irrespective of whether I use the ethernet multicast address as listed in NFD or the actual hardware ethernet address. I was expecting NLSR to only try to create a face if it doesn't already exist. Is this intended behavior, or am I doing something wrong? Is there any other way of using NLSR over Ethernet? Thanks! Ray This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. _______________________________________________ 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: From shijunxiao at email.arizona.edu Thu Aug 20 19:49:14 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Thu, 20 Aug 2015 19:49:14 -0700 Subject: [Ndn-interest] Multiple Ethernet faces In-Reply-To: References: Message-ID: <55d691ab.4366460a.5165a.077f@mx.google.com> Hi Ray No, NFD does not allow distinct ?remote endpoint? among Ethernet multicast faces. The rationale of using the same ?remote endpoint? for all Ethernet multicast faces is: this address is a well-known address, so that every node can join the same multicast group. It?s expected that all nodes are configured to use the same Ethernet multicast address, known as ALL-NDN-SYSTEMS. In the long term, this multicast address would be registered with IANA, and then become hard-coded. Having a single ALL-NDN-SYSTEMS multicast address allows a network to work out-of-box without requiring an administrator to manually configure a distinct multicast address for each link, and without any negotiation or discovery. If all nodes on a link are NDN nodes, this multicast group is effectively broadcast. We use the ALL-NDN-SYSTEMS multicast group so that NDN nodes can co-exist with non-NDN nodes, and non-NDN nodes don?t have to receive NDN traffic. The discussion above is also applicable to UDP multicast faces. NFD does not require ?remote endpoint? of faces to be distinct. >From an application, you may use FaceId to identify individual faces; to search for a face, run Face query operation with both ?remote endpoint? and ?local endpoint? conditions. Yours, Junxiao From: Brandenburg, R. (Ray) van Sent: Wednesday, August 19, 2015 11:12 To: ndn-interest at lists.cs.ucla.edu Cc: shijunxiao at email.arizona.edu Subject: Multiple Ethernet faces 1) If I have a machine with multiple NICs, NFD will list them as separate faces (since they have different local endpoints). However, they will have the same remote endpoint, i.e the ethernet multicast address listed in nfd.conf. Is there anyway to make sure each Ethernet face has it's own distinct multicast address? -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Thu Aug 20 19:59:03 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Thu, 20 Aug 2015 19:59:03 -0700 Subject: [Ndn-interest] NDN over Ethernet In-Reply-To: References: <55d2b12e.c385460a.beb8.ffffcc11@mx.google.com> Message-ID: <55d693f7.a39c420a.c6566.120c@mx.google.com> Hi Jeff The information given in my answer below is available on NFD homepage. Specifically, ? Ethernet face is mentioned in ?NFD configuration file format? ? ?nfd-status -f? appears in ?manpages ? nfd-status? ? ?ether:? is declared in ?NFD Management protocol ? Face Management ? FaceUri? ? ?nfdc register / ? appears in ?manpages ? nfdc? Yours, Junxiao From: Burke, Jeff Sent: Wednesday, August 19, 2015 22:03 To: Junxiao Shi;ahmed abencherou;ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] NDN over Ethernet Hi Junxiao, Can you please provide a pointer to the documentation where one can learn such things?? Jeff From: Ndn-interest on behalf of Junxiao Shi Date: Monday, August 17, 2015 at 9:14 PM To: ahmed abencherou, "ndn-interest at lists.cs.ucla.edu" Subject: Re: [Ndn-interest] NDN over Ethernet Hi Ahmed ? NFD 0.3 contain EthernetFace and is capable of multicast communication directly over Ethernet. ? If you type ?nfd-status -f?, you may see an ?ether:? multi-access face for every NIC that is capable of Ethernet communication. Register a route onto one of those faces with ?nfdc register / ? would allow you to send Interest onto and receive Data from an EthernetFace. ? Yours, Junxiao ? From: ahmed abencherou Sent: Monday, August 17, 2015 11:35 To: ndn-interest at lists.cs.ucla.edu Subject: [Ndn-interest] NDN over Ethernet ? ? Hi all, Can an NDN application send data directly over Ethernet ? If yes which version of NFD does support this feature ? Thanks. -- Ahmed ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From matti.lorenzen at tum.de Sun Aug 23 23:17:18 2015 From: matti.lorenzen at tum.de (Matti Lorenzen) Date: Mon, 24 Aug 2015 06:17:18 +0000 Subject: [Ndn-interest] Question regarding setup (ndn-cxx vs. ndn tools) Message-ID: Hello, I just started to use NDN, so I installed the 0.3.2 Version as indicated in http://named-data.net/codebase/platform/ . I installed all parts as instructed but stumbled upon the ndn-tlv-ping which is marked as deprecated. Instead, the installation of ndntools is recommended. However, the ./waf command (I am running Ubuntu 14.04) fails as the file ndn-cxx/src/security/signing-helpers.hpp is required. This file is only in ndn-cxx 0.3.3 on github and not part of the 0.3.2 release. Can I just use the newer ndn-cxx without any loss of compatability? Best regards, Matti Lorenzen _________________________________________________________________ Matti Lorenzen IAESTE LC M?nchen - Outgoing IAESTE Central European Region - Vice Trainings Coordinator -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Mon Aug 24 07:52:53 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Mon, 24 Aug 2015 07:52:53 -0700 Subject: [Ndn-interest] Question regarding setup (ndn-cxx vs. ndn tools) In-Reply-To: References: Message-ID: Hi Matti, To use ndn-tools, you need to download and install the latest version (release 0.3.3 or the current master branch) of ndn-cxx library. As you discovered, it doesn't work with prior versions. Do you have a specific reason to use 0.3.2? The new version has a few API changes (check changelog to see if you're affected). --- Alex > On Aug 23, 2015, at 11:17 PM, Matti Lorenzen wrote: > > Hello, > > > > I just started to use NDN, so I installed the 0.3.2 Version as indicated in http://named-data.net/codebase/platform/ . > > I installed all parts as instructed but stumbled upon the ndn-tlv-ping which is marked as deprecated. > Instead, the installation of ndntools is recommended. > > However, the ./waf command (I am running Ubuntu 14.04) fails as the file ndn-cxx/src/security/signing-helpers.hpp is required. This file is only in ndn-cxx 0.3.3 on github and not part of the 0.3.2 release. Can I just use the newer ndn-cxx without any loss of compatability? > > > > Best regards, > > Matti Lorenzen > > > > _________________________________________________________________ > > Matti Lorenzen > IAESTE LC M?nchen - Outgoing > IAESTE Central European Region - Vice Trainings Coordinator > > _______________________________________________ > 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: From chawla.aniesh at gmail.com Mon Aug 24 06:12:28 2015 From: chawla.aniesh at gmail.com (aniesh chawla) Date: Mon, 24 Aug 2015 18:42:28 +0530 Subject: [Ndn-interest] Question regarding consistency Message-ID: Hello Everyone, I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. The question is: How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. Is my understanding correct or am I missing something here? Thanks a lot Regards Aniesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From tailinchu at gmail.com Mon Aug 24 09:45:51 2015 From: tailinchu at gmail.com (Tai-Lin Chu) Date: Mon, 24 Aug 2015 09:45:51 -0700 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: References: Message-ID: You can use "selectors" for data discovery. http://named-data.net/doc/ndn-tlv/interest.html#selectors On Mon, Aug 24, 2015 at 6:12 AM, aniesh chawla wrote: > Hello Everyone, > > I have a very basic doubt which I could not resolve while reading > documentation of NDN. I would like to also take this as research topic if my > doubt is valid. > > The question is: > How is the consistency of data maintained in the network? Since, NDN is > "pull" based networking and lets say there is change in file version at one > of the node and not in other nodes. I can see the this can be achieved > through NDNFS, but still the other nodes will not have change in version of > the file. So, how will the new node who is requesting for that file will get > to know which version to ask for? If we use NDNS to resolve every such query > and we use time stamp as version then also it should be propagated > throughout the network? I also see that Chrono-sync does something like this > but it has waiting timer for propagation delays. So either NDNS is talking > to every node in the whole network or some other way. > > Is my understanding correct or am I missing something here? > > Thanks a lot > > Regards > Aniesh > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From alexander.afanasyev at ucla.edu Mon Aug 24 10:31:52 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Mon, 24 Aug 2015 10:31:52 -0700 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: References: Message-ID: <9E4AE661-A06F-4A3F-A4B1-33B1B0002C80@ucla.edu> > On Aug 24, 2015, at 6:12 AM, aniesh chawla wrote: > > Hello Everyone, > > I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. > > The question is: > How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. To discover that a newer version of some data is available, you need to have additional mechanisms to discover newer name (version) of the data. What you have mentioned is correct: you can rely on ChronSync to notify about new published data items, you can use manifest and manifest-like mechanisms (e.g., NDNFS, NDNS) where consumers when desired retrieve information about current ("fresh") status of published data. In either case, what you get is exact name of new data, including version number. Selector mechanism that Tai-Lin mentioned is a way to get different data from what you already have. It can be used for newer version discovery, though it can have additional implications from packet processing perspective. -- Alex > Is my understanding correct or am I missing something here? > > Thanks a lot > > Regards > Aniesh -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From mhasabet at gmail.com Mon Aug 24 11:16:34 2015 From: mhasabet at gmail.com (Muhammad Hosain Abdollahi Sabet) Date: Mon, 24 Aug 2015 22:46:34 +0430 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: <9E4AE661-A06F-4A3F-A4B1-33B1B0002C80@ucla.edu> References: <9E4AE661-A06F-4A3F-A4B1-33B1B0002C80@ucla.edu> Message-ID: Alex, If all the replicas of the requested data, run chrono-sync among themselves, there shouldn't be any problem but the one with waiting timer, right? So the consumer can find the final version using mustbefresh. Aniesh, I didn't understand your question about NDNS. If there isn't any delegation(e.g publisher doesn't need/want to publish content globally), NDNS won't resolve names. ?? ?Thanks, Sabet? On Mon, Aug 24, 2015 at 10:01 PM, Alex Afanasyev < alexander.afanasyev at ucla.edu> wrote: > > > On Aug 24, 2015, at 6:12 AM, > ?? > aniesh chawla wrote: > > > > Hello Everyone, > > > > I have a very basic doubt which I could not resolve while reading > documentation of NDN. I would like to also take this as research topic if > my doubt is valid. > > > > The question is: > > How is the consistency of data maintained in the network? Since, NDN is > "pull" based networking and lets say there is change in file version at one > of the node and not in other nodes. I can see the this can be achieved > through NDNFS, but still the other nodes will not have change in version of > the file. So, how will the new node who is requesting for that file will > get to know which version to ask for? If we use NDNS to resolve every such > query and we use time stamp as version then also it should be propagated > throughout the network? I also see that Chrono-sync does something like > this but it has waiting timer for propagation delays. So either NDNS is > talking to every node in the whole network or some other way. > > To discover that a newer version of some data is available, you need to > have additional mechanisms to discover newer name (version) of the data. > What you have mentioned is correct: you can rely on ChronSync to notify > about new published data items, you can use manifest and manifest-like > mechanisms (e.g., NDNFS, NDNS) where consumers when desired retrieve > information about current ("fresh") status of published data. In either > case, what you get is exact name of new data, including version number. > > Selector mechanism that Tai-Lin mentioned is a way to get different data > from what you already have. It can be used for newer version discovery, > though it can have additional implications from packet processing > perspective. > > -- > Alex > > > Is my understanding correct or am I missing something here? > > > > Thanks a lot > > > > Regards > > Aniesh > > _______________________________________________ > 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: From lixia at CS.UCLA.EDU Mon Aug 24 12:36:33 2015 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Mon, 24 Aug 2015 12:36:33 -0700 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: References: Message-ID: <50BC05D2-0A89-4CE7-BE73-1ABF3E96AB4A@cs.ucla.edu> > On Aug 24, 2015, at 6:12 AM, aniesh chawla wrote: > > Hello Everyone, > > I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. > > The question is: > How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. > > Is my understanding correct or am I missing something here? Let me step up a level: 1/ in developing NDN applications, the first and most important thing is to get the naming design right. If your files change over time, you would consider to put a version number as part of the file name to allow you to tell different versions. 2/ Keep in mind that NDN is a network protocol; each produced NDN data packet is immutable. Therefore there is no "consistency" issue about "data maintained in the network". 3/ Maybe your question is about "how do end consumers learn that a new version of the file has been produced?" - this question has nothing to do with NDNS (my view) - there can be multiple solutions here, running Sync, periodically pull the file with the next version number, some notification service, etc. Lixia From wentaoshang at gmail.com Mon Aug 24 20:52:21 2015 From: wentaoshang at gmail.com (Wentao Shang) Date: Mon, 24 Aug 2015 20:52:21 -0700 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: References: Message-ID: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> > On Aug 24, 2015, at 6:12 AM, aniesh chawla wrote: > > Hello Everyone, > > I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. > > The question is: > How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? Hi Aniesh, As Lixia said in her reply, NDN is a layer-3 protocol. While it moves some of the application layer functionalities into the network layer, it cannot solve every problem the application faces. NDNFS is a piece of software that demonstrates the idea of integrating application data unit (i.e., file blocks) with network data unit (i.e., NDN data packets). It was originally designed to be a local file system without any remote replication. Therefore the data consistency issue was conveniently ignored. If you need synchronization across multiple copies of the data, you may run your application on top of ChronoSync, which gives you some form of eventual consistency. Best, Wentao > If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. > > Is my understanding correct or am I missing something here? > > Thanks a lot > > Regards > Aniesh > _______________________________________________ > 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: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From chawla.aniesh at gmail.com Mon Aug 24 22:00:21 2015 From: chawla.aniesh at gmail.com (aniesh chawla) Date: Tue, 25 Aug 2015 10:30:21 +0530 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> References: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> Message-ID: Thanks everyone. Lixia, you were right, I was looking for the third point. Wentao, Thanks for the clarification about NDNFS So If I run ChronoSync, it will provide me with eventual consistency but there are timers associated with them which might make things bit difficult and complex. Do you think that is timers(as in ChornoSync) is the right way to go forward or was it more like Proof Of Concept to showcase that synchronization is possible? Personally I don't like timers which are associated with network (in this case propagation delay), I had really bad experience when I did beacon synchronization which was almost like the one mentioned in ChronoSync in my earlier project and every time we end up changing the timers. Regards Aniesh On Tue, Aug 25, 2015 at 9:22 AM, Wentao Shang wrote: > > > On Aug 24, 2015, at 6:12 AM, aniesh chawla > wrote: > > > > Hello Everyone, > > > > I have a very basic doubt which I could not resolve while reading > documentation of NDN. I would like to also take this as research topic if > my doubt is valid. > > > > The question is: > > How is the consistency of data maintained in the network? Since, NDN is > "pull" based networking and lets say there is change in file version at one > of the node and not in other nodes. I can see the this can be achieved > through NDNFS, but still the other nodes will not have change in version of > the file. So, how will the new node who is requesting for that file will > get to know which version to ask for? > > Hi Aniesh, > > As Lixia said in her reply, NDN is a layer-3 protocol. While it moves some > of the application layer functionalities into the network layer, it cannot > solve every problem the application faces. > > NDNFS is a piece of software that demonstrates the idea of integrating > application data unit (i.e., file blocks) with network data unit (i.e., NDN > data packets). It was originally designed to be a local file system without > any remote replication. Therefore the data consistency issue was > conveniently ignored. > > If you need synchronization across multiple copies of the data, you may > run your application on top of ChronoSync, which gives you some form of > eventual consistency. > > Best, > Wentao > > > If we use NDNS to resolve every such query and we use time stamp as > version then also it should be propagated throughout the network? I also > see that Chrono-sync does something like this but it has waiting timer for > propagation delays. So either NDNS is talking to every node in the whole > network or some other way. > > > > Is my understanding correct or am I missing something here? > > > > Thanks a lot > > > > Regards > > Aniesh > > _______________________________________________ > > 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: From lixia at CS.UCLA.EDU Mon Aug 24 22:22:17 2015 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Mon, 24 Aug 2015 22:22:17 -0700 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: References: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> Message-ID: <5BD6EE50-ADCF-4691-A723-997C51E291B7@cs.ucla.edu> > On Aug 24, 2015, at 10:00 PM, aniesh chawla wrote: > > Thanks everyone. > > Lixia, > you were right, I was looking for the third point. > > Wentao, > Thanks for the clarification about NDNFS > > So If I run ChronoSync, it will provide me with eventual consistency but there are timers associated with them which might make things bit difficult and complex. Do you think that is timers(as in ChornoSync) is the right way to go forward or was it more like Proof Of Concept to showcase that synchronization is possible? Personally I don't like timers which are associated with network (in this case propagation delay), I had really bad experience when I did beacon synchronization which was almost like the one mentioned in ChronoSync in my earlier project and every time we end up changing the timers. > > Regards > Aniesh I am not sure what/which ChronoSync "timers" you are concerned about ... Sync is not just "possible", it's an importance piece in the architecture. Would be interested in hearing more about your lessons from your beacon sync. The specific design of ChronoSync, as described in ICNP 2013 paper, has its limitations; a revision has been worked on, hope to make it solid enough to share soon. Lixia > On Tue, Aug 25, 2015 at 9:22 AM, Wentao Shang > wrote: > > > On Aug 24, 2015, at 6:12 AM, aniesh chawla > wrote: > > > > Hello Everyone, > > > > I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. > > > > The question is: > > How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? > > Hi Aniesh, > > As Lixia said in her reply, NDN is a layer-3 protocol. While it moves some of the application layer functionalities into the network layer, it cannot solve every problem the application faces. > > NDNFS is a piece of software that demonstrates the idea of integrating application data unit (i.e., file blocks) with network data unit (i.e., NDN data packets). It was originally designed to be a local file system without any remote replication. Therefore the data consistency issue was conveniently ignored. > > If you need synchronization across multiple copies of the data, you may run your application on top of ChronoSync, which gives you some form of eventual consistency. > > Best, > Wentao > > > If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. > > > > Is my understanding correct or am I missing something here? > > > > Thanks a lot > > > > Regards > > Aniesh > > _______________________________________________ > > Ndn-interest mailing list > > Ndn-interest at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > _______________________________________________ > 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: From M.AbdollahiSabet at mail.sbu.ac.ir Mon Aug 24 22:59:45 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Tue, 25 Aug 2015 10:29:45 +0430 Subject: [Ndn-interest] Question regarding consistency References: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> <5BD6EE50-ADCF-4691-A723-997C51E291B7@cs.ucla.edu> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC298F@m-pdc.sbu.ac.ir> Aniesh, You mean most of the time Tw(as ChronoSync named it) expired and your nodes did processing of a corresponding sync interest, so missed some others-generated data? Sabet -----Original Message----- From: Ndn-interest on behalf of Lixia Zhang Sent: Tue 8/25/2015 9:52 AM To: aniesh chawla Cc: ndn-interest Subject: Re: [Ndn-interest] Question regarding consistency > On Aug 24, 2015, at 10:00 PM, aniesh chawla wrote: > > Thanks everyone. > > Lixia, > you were right, I was looking for the third point. > > Wentao, > Thanks for the clarification about NDNFS > > So If I run ChronoSync, it will provide me with eventual consistency but there are timers associated with them which might make things bit difficult and complex. Do you think that is timers(as in ChornoSync) is the right way to go forward or was it more like Proof Of Concept to showcase that synchronization is possible? Personally I don't like timers which are associated with network (in this case propagation delay), I had really bad experience when I did beacon synchronization which was almost like the one mentioned in ChronoSync in my earlier project and every time we end up changing the timers. > > Regards > Aniesh I am not sure what/which ChronoSync "timers" you are concerned about ... Sync is not just "possible", it's an importance piece in the architecture. Would be interested in hearing more about your lessons from your beacon sync. The specific design of ChronoSync, as described in ICNP 2013 paper, has its limitations; a revision has been worked on, hope to make it solid enough to share soon. Lixia > On Tue, Aug 25, 2015 at 9:22 AM, Wentao Shang > wrote: > > > On Aug 24, 2015, at 6:12 AM, aniesh chawla > wrote: > > > > Hello Everyone, > > > > I have a very basic doubt which I could not resolve while reading documentation of NDN. I would like to also take this as research topic if my doubt is valid. > > > > The question is: > > How is the consistency of data maintained in the network? Since, NDN is "pull" based networking and lets say there is change in file version at one of the node and not in other nodes. I can see the this can be achieved through NDNFS, but still the other nodes will not have change in version of the file. So, how will the new node who is requesting for that file will get to know which version to ask for? > > Hi Aniesh, > > As Lixia said in her reply, NDN is a layer-3 protocol. While it moves some of the application layer functionalities into the network layer, it cannot solve every problem the application faces. > > NDNFS is a piece of software that demonstrates the idea of integrating application data unit (i.e., file blocks) with network data unit (i.e., NDN data packets). It was originally designed to be a local file system without any remote replication. Therefore the data consistency issue was conveniently ignored. > > If you need synchronization across multiple copies of the data, you may run your application on top of ChronoSync, which gives you some form of eventual consistency. > > Best, > Wentao > > > If we use NDNS to resolve every such query and we use time stamp as version then also it should be propagated throughout the network? I also see that Chrono-sync does something like this but it has waiting timer for propagation delays. So either NDNS is talking to every node in the whole network or some other way. > > > > Is my understanding correct or am I missing something here? > > > > Thanks a lot > > > > Regards > > Aniesh > > _______________________________________________ > > Ndn-interest mailing list > > Ndn-interest at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > _______________________________________________ > 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: From chawla.aniesh at gmail.com Tue Aug 25 00:30:10 2015 From: chawla.aniesh at gmail.com (aniesh chawla) Date: Tue, 25 Aug 2015 13:00:10 +0530 Subject: [Ndn-interest] Question regarding consistency In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC298F@m-pdc.sbu.ac.ir> References: <8D5A34CB-0F43-4E75-A00A-E48CA6D73DA2@gmail.com> <5BD6EE50-ADCF-4691-A723-997C51E291B7@cs.ucla.edu> <4AC03A6244C3C34BB52A7EC60B799C4C03CC298F@m-pdc.sbu.ac.ir> Message-ID: Hi Sabet, Yes, in my network setup of earlier project(not NDN) there were issues with synchronization timers across nodes, as there was not just propagation delay which were deterrent. I was working on WiMAX over WiFi networks and the wireless has more issues other than just propagation delay. We had to deal with channel access delays, queuing delays, congestion delays, packetization delays and we kept on mathematically model our timers. Lixia, Thank for your update. Can we have a peek into the new synchronization protocol? I would love to work on it if possible? Regards On Tue, Aug 25, 2015 at 11:29 AM, Muhammad Hosain Abdollahi Sabet < M.AbdollahiSabet at mail.sbu.ac.ir> wrote: > Aniesh, > You mean most of the time Tw(as ChronoSync named it) expired and your > nodes did processing of a corresponding sync interest, so missed some > others-generated data? > > Sabet > > > -----Original Message----- > From: Ndn-interest on behalf of Lixia Zhang > Sent: Tue 8/25/2015 9:52 AM > To: aniesh chawla > Cc: ndn-interest > Subject: Re: [Ndn-interest] Question regarding consistency > > > > On Aug 24, 2015, at 10:00 PM, aniesh chawla > wrote: > > > > Thanks everyone. > > > > Lixia, > > you were right, I was looking for the third point. > > > > Wentao, > > Thanks for the clarification about NDNFS > > > > So If I run ChronoSync, it will provide me with eventual consistency but > there are timers associated with them which might make things bit difficult > and complex. Do you think that is timers(as in ChornoSync) is the right way > to go forward or was it more like Proof Of Concept to showcase that > synchronization is possible? Personally I don't like timers which are > associated with network (in this case propagation delay), I had really bad > experience when I did beacon synchronization which was almost like the one > mentioned in ChronoSync in my earlier project and every time we end up > changing the timers. > > > > Regards > > Aniesh > > I am not sure what/which ChronoSync "timers" you are concerned about ... > Sync is not just "possible", it's an importance piece in the architecture. > > Would be interested in hearing more about your lessons from your beacon > sync. > > The specific design of ChronoSync, as described in ICNP 2013 paper, has > its limitations; a revision has been worked on, hope to make it solid > enough to share soon. > > Lixia > > > On Tue, Aug 25, 2015 at 9:22 AM, Wentao Shang mailto:wentaoshang at gmail.com >> wrote: > > > > > On Aug 24, 2015, at 6:12 AM, aniesh chawla mailto:chawla.aniesh at gmail.com >> wrote: > > > > > > Hello Everyone, > > > > > > I have a very basic doubt which I could not resolve while reading > documentation of NDN. I would like to also take this as research topic if > my doubt is valid. > > > > > > The question is: > > > How is the consistency of data maintained in the network? Since, NDN > is "pull" based networking and lets say there is change in file version at > one of the node and not in other nodes. I can see the this can be achieved > through NDNFS, but still the other nodes will not have change in version of > the file. So, how will the new node who is requesting for that file will > get to know which version to ask for? > > > > Hi Aniesh, > > > > As Lixia said in her reply, NDN is a layer-3 protocol. While it moves > some of the application layer functionalities into the network layer, it > cannot solve every problem the application faces. > > > > NDNFS is a piece of software that demonstrates the idea of integrating > application data unit (i.e., file blocks) with network data unit (i.e., NDN > data packets). It was originally designed to be a local file system without > any remote replication. Therefore the data consistency issue was > conveniently ignored. > > > > If you need synchronization across multiple copies of the data, you may > run your application on top of ChronoSync, which gives you some form of > eventual consistency. > > > > Best, > > Wentao > > > > > If we use NDNS to resolve every such query and we use time stamp as > version then also it should be propagated throughout the network? I also > see that Chrono-sync does something like this but it has waiting timer for > propagation delays. So either NDNS is talking to every node in the whole > network or some other way. > > > > > > Is my understanding correct or am I missing something here? > > > > > > Thanks a lot > > > > > > Regards > > > Aniesh > > > _______________________________________________ > > > Ndn-interest mailing list > > > Ndn-interest at lists.cs.ucla.edu > > > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest < > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest> > > > > > > _______________________________________________ > > 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: From matti.lorenzen at tum.de Wed Aug 26 18:01:48 2015 From: matti.lorenzen at tum.de (Matti Lorenzen) Date: Thu, 27 Aug 2015 01:01:48 +0000 Subject: [Ndn-interest] Package Fragmentation in NDN Message-ID: Dear all, I have a question regarding the payload of Data packets. I used ndnpeek and ndnpoke in order to submit an interest for a file and successfully received a data packet in return. However, this data packets were only returned to me if the file contained was very small (1,5kB). Is there any way to send larger files through another tool? By my understanding, peek and poke are used only for exactly one packet and are hence limited regarding data transfer. I know that data is segmented and all segments of a file would be aligned underneath the file in the naming hierarchy. However, the size of these segments is not so small that they would fit in a Data packet, right? Otherwise large files would have a very high amount of segments. Thank you in advance, best regards, Matti Lorenzen -------------- next part -------------- An HTML attachment was scrubbed... URL: From aniesh at sanctumnetworks.com Wed Aug 26 21:30:36 2015 From: aniesh at sanctumnetworks.com (aniesh chawla) Date: Thu, 27 Aug 2015 10:00:36 +0530 Subject: [Ndn-interest] Package Fragmentation in NDN In-Reply-To: References: Message-ID: Hi Matti, ndnputfile/ndngetfile comes from repo-gn, you might have to install it. You can also check out ndnputchunk3, this will also do what you want. If you want I have created a text file sender/receiver by (modifying earlier producer/sender code) for large chunks of data, more like bulk transfer. I have tested my code for one sender and one receiver and haven't tested for more than one receiver(maybe some optimization have to done there) Regards Aniesh On Thu, Aug 27, 2015 at 9:48 AM, Matti Lorenzen wrote: > Dear Aniesh, > this sounds a lot like what I am looking for. Thank you. > I'm running ndn-cxx and NFD version 0.3.3 on Ubuntu 14.04. - if i see > correctly, ndnputfile is a part of NDNx, is it complatible with my current > setup? > > Best regards from Tokyo, > Matti > > _________________________________________________________________ > > *Matti Lorenzen* > IAESTE LC M?nchen - *Outgoing* > IAESTE Central European Region - > *Vice Trainings Coordinator* > > > ------------------------------ > Date: Thu, 27 Aug 2015 09:40:30 +0530 > Subject: Re: [Ndn-interest] Package Fragmentation in NDN > From: aniesh at sanctumnetworks.com > To: matti.lorenzen at tum.de > > > Hi Matti, > I think you are looking for putting more number of segments. The largest > segment allowed in NDN is 8800(last I checked). > In order to put the file you have a tool called ndnputfile, and to get > there is tool ndngetfile. > check this out: > http://named-data.net/doc/0.1/manpages/ndnputfile.1.html > > Regards > Aniesh > > On Thu, Aug 27, 2015 at 6:31 AM, Matti Lorenzen > wrote: > > Dear all, > > I have a question regarding the payload of Data packets. > I used ndnpeek and ndnpoke in order to submit an interest for a file and > successfully received a data packet in return. However, this data packets > were only returned to me if the file contained was very small (1,5kB). Is > there any way to send larger files through another tool? By my > understanding, peek and poke are used only for exactly one packet and are > hence limited regarding data transfer. > > I know that data is segmented and all segments of a file would be aligned > underneath the file in the naming hierarchy. However, the size of these > segments is not so small that they would fit in a Data packet, right? > Otherwise large files would have a very high amount of segments. > > Thank you in advance, > best regards, > Matti Lorenzen > > _______________________________________________ > 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: From M.AbdollahiSabet at mail.sbu.ac.ir Wed Aug 26 21:42:06 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Thu, 27 Aug 2015 09:12:06 +0430 Subject: [Ndn-interest] Package Fragmentation in NDN References: Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2992@m-pdc.sbu.ac.ir> Hi Matti, Actually there is/will be fragmentation in NDN. You can take look at this: http://named-data.net/wp-content/uploads/2015/05/ndn-0032-1-ndn-memo-fragmentation.pdf This is just a memo, but it has reviewed the problem and solutions well enough. But the need for fragmentation in above comes from the fact that MTUs may differ throughout the network. I don't think having large amounts of segments(you say names) be a problem. They could be aggregated easily. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of aniesh chawla Sent: Thu 8/27/2015 9:00 AM To: Matti Lorenzen; ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Package Fragmentation in NDN Hi Matti, ndnputfile/ndngetfile comes from repo-gn, you might have to install it. You can also check out ndnputchunk3, this will also do what you want. If you want I have created a text file sender/receiver by (modifying earlier producer/sender code) for large chunks of data, more like bulk transfer. I have tested my code for one sender and one receiver and haven't tested for more than one receiver(maybe some optimization have to done there) Regards Aniesh On Thu, Aug 27, 2015 at 9:48 AM, Matti Lorenzen wrote: > Dear Aniesh, > this sounds a lot like what I am looking for. Thank you. > I'm running ndn-cxx and NFD version 0.3.3 on Ubuntu 14.04. - if i see > correctly, ndnputfile is a part of NDNx, is it complatible with my current > setup? > > Best regards from Tokyo, > Matti > > _________________________________________________________________ > > *Matti Lorenzen* > IAESTE LC M?nchen - *Outgoing* > IAESTE Central European Region - > *Vice Trainings Coordinator* > > > ------------------------------ > Date: Thu, 27 Aug 2015 09:40:30 +0530 > Subject: Re: [Ndn-interest] Package Fragmentation in NDN > From: aniesh at sanctumnetworks.com > To: matti.lorenzen at tum.de > > > Hi Matti, > I think you are looking for putting more number of segments. The largest > segment allowed in NDN is 8800(last I checked). > In order to put the file you have a tool called ndnputfile, and to get > there is tool ndngetfile. > check this out: > http://named-data.net/doc/0.1/manpages/ndnputfile.1.html > > Regards > Aniesh > > On Thu, Aug 27, 2015 at 6:31 AM, Matti Lorenzen > wrote: > > Dear all, > > I have a question regarding the payload of Data packets. > I used ndnpeek and ndnpoke in order to submit an interest for a file and > successfully received a data packet in return. However, this data packets > were only returned to me if the file contained was very small (1,5kB). Is > there any way to send larger files through another tool? By my > understanding, peek and poke are used only for exactly one packet and are > hence limited regarding data transfer. > > I know that data is segmented and all segments of a file would be aligned > underneath the file in the naming hierarchy. However, the size of these > segments is not so small that they would fit in a Data packet, right? > Otherwise large files would have a very high amount of segments. > > Thank you in advance, > best regards, > Matti Lorenzen > > _______________________________________________ > 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: From iliamo at CS.UCLA.EDU Thu Aug 27 06:45:22 2015 From: iliamo at CS.UCLA.EDU (Ilya Moiseenko) Date: Thu, 27 Aug 2015 09:45:22 -0400 Subject: [Ndn-interest] Package Fragmentation in NDN In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2992@m-pdc.sbu.ac.ir> References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2992@m-pdc.sbu.ac.ir> Message-ID: <73F54AF5-B63F-4593-BBC2-B93D746719F0@cs.ucla.edu> Hi everyone in this thread, Please, don?t confuse a segmentation of the content into NDN Data packets with the fragmentation of NDN packets into the link layer frames. Fragmentation is needed to pass a single Data packet over the physical link. Segmentation is needed to convert any content that doesn?t fit into a single Data packet into multiple Data packets. Since the original question was about segmentation, I suggest to look into Consumer / Producer API https://github.com/iliamo/Consumer-Producer-API There are a lot of examples in this repo, but for the documentation you can refer to the attached paper. Ilya On Aug 27, 2015, at 12:42 AM, Muhammad Hosain Abdollahi Sabet wrote: > Hi Matti, > > Actually there is/will be fragmentation in NDN. You can take look at this: > http://named-data.net/wp-content/uploads/2015/05/ndn-0032-1-ndn-memo-fragmentation.pdf > This is just a memo, but it has reviewed the problem and solutions well enough. > > But the need for fragmentation in above comes from the fact that MTUs may differ throughout the network. I don't think having large amounts of segments(you say names) be a problem. They could be aggregated easily. > > Thanks, > Sabet > > -----Original Message----- > From: Ndn-interest on behalf of aniesh chawla > Sent: Thu 8/27/2015 9:00 AM > To: Matti Lorenzen; ndn-interest at lists.cs.ucla.edu > Subject: Re: [Ndn-interest] Package Fragmentation in NDN > > Hi Matti, > > ndnputfile/ndngetfile comes from repo-gn, you might have to install it. > You can also check out ndnputchunk3, this will also do what you want. If > you want I have created a text file sender/receiver by (modifying earlier > producer/sender code) for large chunks of data, more like bulk transfer. I > have tested my code for one sender and one receiver and haven't tested for > more than one receiver(maybe some optimization have to done there) > > Regards > Aniesh > > On Thu, Aug 27, 2015 at 9:48 AM, Matti Lorenzen > wrote: > > > Dear Aniesh, > > this sounds a lot like what I am looking for. Thank you. > > I'm running ndn-cxx and NFD version 0.3.3 on Ubuntu 14.04. - if i see > > correctly, ndnputfile is a part of NDNx, is it complatible with my current > > setup? > > > > Best regards from Tokyo, > > Matti > > > > _________________________________________________________________ > > > > *Matti Lorenzen* > > IAESTE LC M?nchen - *Outgoing* > > IAESTE Central European Region - > > *Vice Trainings Coordinator* > > > > > > ------------------------------ > > Date: Thu, 27 Aug 2015 09:40:30 +0530 > > Subject: Re: [Ndn-interest] Package Fragmentation in NDN > > From: aniesh at sanctumnetworks.com > > To: matti.lorenzen at tum.de > > > > > > Hi Matti, > > I think you are looking for putting more number of segments. The largest > > segment allowed in NDN is 8800(last I checked). > > In order to put the file you have a tool called ndnputfile, and to get > > there is tool ndngetfile. > > check this out: > > http://named-data.net/doc/0.1/manpages/ndnputfile.1.html > > > > Regards > > Aniesh > > > > On Thu, Aug 27, 2015 at 6:31 AM, Matti Lorenzen > > wrote: > > > > Dear all, > > > > I have a question regarding the payload of Data packets. > > I used ndnpeek and ndnpoke in order to submit an interest for a file and > > successfully received a data packet in return. However, this data packets > > were only returned to me if the file contained was very small (1,5kB). Is > > there any way to send larger files through another tool? By my > > understanding, peek and poke are used only for exactly one packet and are > > hence limited regarding data transfer. > > > > I know that data is segmented and all segments of a file would be aligned > > underneath the file in the naming hierarchy. However, the size of these > > segments is not so small that they would fit in a Data packet, right? > > Otherwise large files would have a very high amount of segments. > > > > Thank you in advance, > > best regards, > > Matti Lorenzen > > > > _______________________________________________ > > Ndn-interest mailing list > > Ndn-interest at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > > > > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: icn09-moiseenko.pdf Type: application/pdf Size: 591853 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Mon Aug 31 12:14:35 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Mon, 31 Aug 2015 12:14:35 -0700 Subject: [Ndn-interest] NFD 0.3.4 and ndn-cxx 0.3.4 released Message-ID: <4355E950-F0EA-46B7-A49A-E95CC955E677@ucla.edu> Dear all, We are pleased to announce release of version 0.3.4 of Named Data Networking Forwarding Daemon (NFD) and ndn-cxx library. The detailed notes for the releases: - for NFD: http://named-data.net/doc/NFD/0.3.4/RELEASE_NOTES.html - for ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.3.4/RELEASE_NOTES.html Source code, instruction how to install pre-compiled binaries on Ubuntu Linux (12.04, 14.04, and 15.04), how to install NDN software using MacPort packages or HomeBrew on OS X, tutorials, HOWTOs, a FAQ and other useful resources are available on official webpages of NFD and ndn-cxx: - http://named-data.net/doc/NFD/0.3.4/ - http://named-data.net/doc/ndn-cxx/0.3.4/ NFD developer's guide: - http://named-data.net/publications/techreports/ndn-0021-4-nfd-developer-guide/. * * * The NDN/NFD Team: Alexander Afanasyev, Junxiao Shi, Beichuan Zhang, Lixia Zhang, Ilya Moiseenko, Yingdi Yu, Wentao Shang, Yanbiao Li, Spyridon Mastorakis, Yi Huang, Jerald Paul Abraham, Steve DiBenedetto, Chengyu Fan, Christos Papadopoulos, Davide Pesavento, Giulio Grassi, Giovanni Pau, Hang Zhang, Tian Song, Haowei Yuan, Hila Ben Abraham, Patrick Crowley, Syed Obaid Amin, Vince Lehman, Lan Wang, Eric Newberry, and others (http://named-data.net/project/participants/) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From aa at CS.UCLA.EDU Mon Aug 31 12:12:51 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Mon, 31 Aug 2015 12:12:51 -0700 Subject: [Ndn-interest] NFD 0.3.4 and ndn-cxx 0.3.4 released Message-ID: <0EC03A2A-B181-4524-8FB8-F275913971EC@cs.ucla.edu> Dear all, We are pleased to announce release of version 0.3.4 of Named Data Networking Forwarding Daemon (NFD) and ndn-cxx library. The detailed notes for the releases: - for NFD: http://named-data.net/doc/NFD/0.3.4/RELEASE_NOTES.html - for ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.3.4/RELEASE_NOTES.html Source code, instruction how to install pre-compiled binaries on Ubuntu Linux (12.04, 14.04, and 15.04), how to install NDN software using MacPort packages or HomeBrew on OS X, tutorials, HOWTOs, a FAQ and other useful resources are available on official webpages of NFD and ndn-cxx: - http://named-data.net/doc/NFD/0.3.4/ - http://named-data.net/doc/ndn-cxx/0.3.4/ NFD developer's guide: - http://named-data.net/publications/techreports/ndn-0021-4-nfd-developer-guide/. * * * The NDN/NFD Team: Alexander Afanasyev, Junxiao Shi, Beichuan Zhang, Lixia Zhang, Ilya Moiseenko, Yingdi Yu, Wentao Shang, Yanbiao Li, Spyridon Mastorakis, Yi Huang, Jerald Paul Abraham, Steve DiBenedetto, Chengyu Fan, Christos Papadopoulos, Davide Pesavento, Giulio Grassi, Giovanni Pau, Hang Zhang, Tian Song, Haowei Yuan, Hila Ben Abraham, Patrick Crowley, Syed Obaid Amin, Vince Lehman, Lan Wang, Eric Newberry, and others (http://named-data.net/project/participants/) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From josh at caida.org Mon Aug 31 17:24:19 2015 From: josh at caida.org (Josh Polterock) Date: Mon, 31 Aug 2015 17:24:19 -0700 Subject: [Ndn-interest] Named Data Networking (NDN) Project Monthly Newsletter for August 2015 Message-ID: <20150901002419.GB28090@caida.org> Named Data Networking (NDN) Project Monthly Newsletter for August 2015 The NDN project team compiles and publishes this newsletter monthly to inform the community about recent activities, technical news, meetings, publications, presentations, code releases, and upcoming events. You can find these newsletters posted on the Named Data Networking Project blog. COMMUNITY OUTREACH * Plans and agenda continue to firm up for the NDN Community Meeting (NDNComm 2015) to be held at the University of California at Los Angeles campus in the Little Theater, MacGowan Hall, UCLA on 28-29 September 2015. While registration remains open on the web at http://www.caida.org/workshops/ndn/1509/ we cannot guarantee support further requests to present. * Hackathon: 26-27 September 2015. We are excited to announce the first NDN hackathon scheduled prior to the upcoming NDNComm 2015. Project proposals were due today 31 August 2015. For questions, please email Steve DiBenedetto (dibenede at cs.colostate.edu). Project representatives will pitch their ideas to hackathon attendees and act as guides/mentors. We also plan projects suitable for NDN newcomers. Please stay tuned to http://www.caida.org/workshops/ndn/1509/#hackathon . We hope to see you in LA! TECHNICAL NEWS * We announced the release of version 0.3.4 of Named Data Networking Forwarding Daemon (NFD) and ndn-cxx library. Please find detailed release notes: - NFD: http://named-data.net/doc/NFD/0.3.4/RELEASE_NOTES.html - ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.3.4/RELEASE_NOTES.html More details about NFD, source code, install instructions, tutorials, HOWTOs, a FAQ and other useful resources are available on the official webpages of NFD and ndn-cxx: - http://named-data.net/doc/NFD/0.3.4/ - http://named-data.net/doc/ndn-cxx/0.3.4/ The latest version of NFD developer's guide: - http://named-data.net/publications/techreports/ndn-0021-4-nfd-developer-guide/ * We posted a new version of NdnCon v0.4.3 (v0.4.3). We do not yet recommend it as a reliable subsitute for existing conferencing tools, however, we hope to soon satisfy the NDN NP project's immediate needs (reliable audio prioritized over smooth HD video). * ChronoChat-js version v0.3 has been updated to use the ChronoSync2013 class in NDN-JS. https://github.com/named-data/ChronoChat-js It can register with a remote NFD if NFD is configured to allow localhop. You can try the online demo: http://named-data.net/apps/live/chat/ NDN PUBLICATIONS, PRESENTATIONS, and TECHNICAL REPORTS * A. Afanasyev, Z. Zhu, Y. Yu, L. Wang, and L. Zhang, "The Story of ChronoShare, or How NDN Brought Distributed Secure File Sharing Back," in IEEE MASS 2015 Workshop on Content-Centric Networks (accepted), October 2015. NDN SEMINARS * Our NDN Seminar series continued during August. The NDN seminars are internally focused. We usually hold these seminars on Wednesday from 2-3p (PST). So, if you would like to be included in the NDN Seminars, please contact Jongdeog Lee for the most up-to-date information regarding upcoming seminars. - August 12th Susmit Shannigrahi and Chengyu Fan (Colorado State Univ.) presented: NDN for Scientific Data Applications - August 26th Eva M. Castro and Pedro de las Heras Quiros (Universidad Rey Juan Carlos, Spain) presented: Redesign of ChronoSync For more information about the Named Data Networking (NDN) Project please visit http://www.named-data.net/.