From jp at wustl.EDU  Mon Feb  1 08:43:51 2016
From: jp at wustl.EDU (Jyoti Parwatikar)
Date: Mon, 1 Feb 2016 10:43:51 -0600
Subject: [Ndn-interest] using ValidatorConfig
In-Reply-To: <52C055D9-8D8D-4628-ACD1-4F907D627ED8@cs.ucla.edu>
References: <56991C63.7050404@wustl.edu>
	<2795B60D-3C1D-4FDF-8A02-A2B078244AEE@email.arizona.edu>
	<56993894.8030406@wustl.edu>
	<EA870886-01D7-4E4E-B355-796BD048F91B@email.arizona.edu>
	<56A65160.4090303@wustl.edu>
	<56acdb01.132c620a.8cf2f.1fad@mx.google.com>
	<52C055D9-8D8D-4628-ACD1-4F907D627ED8@cs.ucla.edu>
Message-ID: <56AF8B47.8000902@wustl.edu>

Yingdi,

This is the error message.

Cannot read certificate from file: 
/users/jp/ndn/JPChronolog/cfg-files/wustl.cert

-Jyoti

On 01/31/2016 01:28 AM, Yingdi Yu wrote:
> Hi Jyoti,
>
> Could you also share the error msg? You can get that be catch 
> std::runtime_error around load() method, and the print out e.what(), e.g.,
>
> try {
>   validator.load(?);
> }
> catch (const std::runtime_error& e) {
>   std::cerr << e.what() << std::endl;
> }
>
> The error message may help us to figure out what kind of error is 
> detected. Thanks!
>
> Yingdi
>
>
>
>
>> On Jan 30, 2016, at 7:47 AM, Junxiao Shi 
>> <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> 
>> wrote:
>>
>> Hi Jyoti
>>
>> Your certificate file and Unix permissions appear to be valid.
>>
>> Can Yingdi have a look at this case?
>>
>> Yours, Junxiao
>>
>>
>> *From: *Jyoti Parwatikar <mailto:jp at wustl.edu>
>> *Sent: *Monday, January 25, 2016 09:46
>> *To: *Junxiao Shi <mailto:shijunxiao at email.arizona.edu>
>> *Cc: *ndn-interest at lists.cs.ucla.edu 
>> <mailto:ndn-interest at lists.cs.ucla.edu>
>> *Subject: *Re: [Ndn-interest] using ValidatorConfig
>>
>> Hi Junxiao,
>>
>> I just got back to working on this.
>> I suspect my certificate is probably incorrect. When I step through 
>> the code, it is failing to create the IdentityCertificate from the 
>> file in ndn::security::conf::CheckerFactory::getSigner(const 
>> ConfigSection&, const string&)
>> I can see it read in from the configuration file and it's reading the 
>> other parameters fine. It's failing when it hits the creation of the 
>> signer in the checker.
>>
>> The process is run as me. And the certificate file has permission 644.
>> First line of certificate file: 
>> Bv0C1QczCAV3dXN0bAgDS0VZCBFkc2stMTQ1Mjg3Mjk2ODQ2OAgHSUQtQ0VSVAgJ
>>
>> My configuration file:
>> rule
>> {
>>    id "h1x1 data rule"
>>    for data
>>    filter
>>    {
>>       type name
>>       name /wustl/CHRONOLOG
>>       relation is-prefix-of
>>    }
>>    checker
>>    {
>>       type fixed-signer
>>       sig-type rsa-sha256
>>       signer
>>       {
>>          type file
>>          file-name "/users/jp/ndn/JPChronolog/cfg-files/wustl.cert"
>>       }
>>    }
>> }
>>
>> -Jyoti
>>
>> On 01/15/2016 12:20 PM, Junxiao Shi wrote:
>>
>>     Hi Jyoti
>>
>>     If giving the full path still doesn?t work, reply-all with the
>>     following:
>>
>>       * the complete ValidatorConfig configuration
>>       * the code snippet that loads the configuration; in particular,
>>         is it loaded from a file or from a string
>>       * the full path of your certificate file
>>       * the first line of your certificate file (this helps
>>         determining whether you have the correct format in the
>>         certificate file)
>>       * what is the current working directory
>>       * what is the effective uid of the running program, and what
>>         Unix permissions does this uid have on the certificate file
>>
>>     Yours, Junxiao
>>
>

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

From mbahrami at ucmerced.edu  Mon Feb  1 12:34:42 2016
From: mbahrami at ucmerced.edu (Mehdi Bahrami)
Date: Mon, 1 Feb 2016 20:34:42 +0000
Subject: [Ndn-interest] Modifying NDN Data Structure
Message-ID: <BLUPR06MB611BDD7A7AC3A3B5600B225BFDE0@BLUPR06MB611.namprd06.prod.outlook.com>

Hi all,
Is anyone has an idea about the following issue:
I'm working on ndn-cxx and I want to extend the data structure of Data, but after adding a field to the Data or MetaInfo, the examples/producer.cpp gives me memory access errors as follows:
Segmenttion fault (core dumped).


To add fields into the data structures as Alex confirmed the process, you need to perform 3 steps:

- add actual field that will hold your data into the data structure

- add invocation of proper decoding into Data::wireDecode method

- add invocation of proper encoding into Data::wireEncode templated method.   Note that encoding is performed in reverse order.  So, if you added your field at the end of data packet, you need to encode it first.

Still I have the same issue.


--
Sincerely,
Mehdi Bahrami
Cloud Lab, EECS
University of California Merced
IEEE Senior Member
http://cloudlab.ucmerced.edu/~mehdi

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

From dibenede at cs.colostate.edu  Mon Feb  1 12:55:57 2016
From: dibenede at cs.colostate.edu (Steve DiBenedetto)
Date: Mon, 1 Feb 2016 13:55:57 -0700
Subject: [Ndn-interest] Modifying NDN Data Structure
In-Reply-To: <BLUPR06MB611BDD7A7AC3A3B5600B225BFDE0@BLUPR06MB611.namprd06.prod.outlook.com>
References: <BLUPR06MB611BDD7A7AC3A3B5600B225BFDE0@BLUPR06MB611.namprd06.prod.outlook.com>
Message-ID: <CAG95Nwt8pFbiB9j8FENMDUjQLaVVUi4zi4=RivVSQne3djTZGQ@mail.gmail.com>

I suspect it's a small off-by-something error in either the encoding
or decoding process. I would double check to make sure you're updating
the running total length variable. Also, if your field is optional,
make sure you're handling it appropriately.




On Mon, Feb 1, 2016 at 1:34 PM, Mehdi Bahrami <mbahrami at ucmerced.edu> wrote:
> Hi all,
>
> Is anyone has an idea about the following issue:
>
> I?m working on ndn-cxx and I want to extend the data structure of Data, but
> after adding a field to the Data or MetaInfo, the examples/producer.cpp
> gives me memory access errors as follows:
>
> Segmenttion fault (core dumped).
>
>
>
> To add fields into the data structures as Alex confirmed the process, you
> need to perform 3 steps:
>
> - add actual field that will hold your data into the data structure
>
> - add invocation of proper decoding into Data::wireDecode method
>
> - add invocation of proper encoding into Data::wireEncode templated method.
> Note that encoding is performed in reverse order.  So, if you added your
> field at the end of data packet, you need to encode it first.
>
>
>
> Still I have the same issue.
>
>
>
>
>
> --
>
> Sincerely,
>
> Mehdi Bahrami
>
> Cloud Lab, EECS
>
> University of California Merced
>
> IEEE Senior Member
>
> http://cloudlab.ucmerced.edu/~mehdi
>
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>



From Ignacio.Solis at parc.com  Mon Feb  1 13:10:31 2016
From: Ignacio.Solis at parc.com (Ignacio.Solis at parc.com)
Date: Mon, 1 Feb 2016 21:10:31 +0000
Subject: [Ndn-interest] CCNx Software on GitHub
Message-ID: <2D5CFE9E-01F0-49B2-BC5A-57BA2C55FD37@parc.com>

Hello folks.

The CCNx software is now on GitHub.

Please go to https://github.com/PARC/CCNx_Distillery for more information.

Basically:
- clone Distillery
- install dependencies (via Distillery)
- clone the different repos (via Distillery)
- compile
- test
- install.


We just did some large code re-orgs and switched over from Autotools to cmake, so there may be some kinks in the build process, but we wanted to make the software available as soon as possible.

Please use the ccnx mailing list for discussions.


The repositories are:
https://github.com/PARC/CCNx_Distillery
https://github.com/PARC/LongBow
https://github.com/PARC/Libparc
https://github.com/PARC/Libccnx-common
https://github.com/PARC/Libccnx-transport-rta
https://github.com/PARC/Libccnx-portal
https://github.com/PARC/Metis
https://github.com/PARC/Athena


Expect some updates in the following weeks, including changes in how we do continuous integration and issue tracking.  For now, feel free to use github and the mailing list to file bugs.

Cheers,

The PARC CCNx team


--
Nacho (Ignacio) Solis
Protocol Architect
Principal Scientist
Palo Alto Research Center (PARC)
+1(650)812-4458
Ignacio.Solis at parc.com
--
Nacho (Ignacio) Solis
Protocol Architect
Principal Scientist
Palo Alto Research Center (PARC)
+1(650)812-4458
Ignacio.Solis at parc.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160201/3f108362/attachment.html>

From mobinranjbar at hotmail.com  Mon Feb  1 23:15:16 2016
From: mobinranjbar at hotmail.com (Mobin Ranjbar)
Date: Tue, 2 Feb 2016 07:15:16 +0000
Subject: [Ndn-interest] Improving Content Store Paper
Message-ID: <BAY173-W2531CF86BB0C87BC90117ECEDF0@phx.gbl>

Hi All,
I am working on a paper to improve content store searching and indexing algorithm via big data tools. You can read abstract below. I am looking forward to your feedbacks. Thanks

	
	
	


Named
Data Networking (NDN) is the Future Internet Architecture that has
its roots in an earlier project, Content-Centric Networking (CCN),
which Van Jacobson first publicly presented in 2006. The NDN project
investigates Jacobson?s proposed evolution from today?s
host-centric network architecture (IP) to a data-centric network
architecture (NDN). The
Content Store is a temporary cache of Data packets the router has
received.
In
this paper, we proposed a method to improve indexing and searching process in Content
Store in NDN Routers using Lucene/Solr which is a high
performance and distributed indexing and search library for big data
use cases.
Best Regards,
________Mobin RanjbarSoftware Engineer, Big Data Evangelist and Startup GuyCo-Founder of Iran StartupsFounder of SharikshoEditor in Chief at Techly.coFounder of FaraFekr TechnologyFounder of Hadoop.irFounder of Big Data WatcherWebsite | Twitter | Linkedin | skype: mobinranjbar
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160202/7ec2fab5/attachment.html>

From aa at CS.UCLA.EDU  Tue Feb  2 11:50:14 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Tue, 2 Feb 2016 11:50:14 -0800
Subject: [Ndn-interest] using ValidatorConfig
In-Reply-To: <56AF8B47.8000902@wustl.edu>
References: <56991C63.7050404@wustl.edu>
	<2795B60D-3C1D-4FDF-8A02-A2B078244AEE@email.arizona.edu>
	<56993894.8030406@wustl.edu>
	<EA870886-01D7-4E4E-B355-796BD048F91B@email.arizona.edu>
	<56A65160.4090303@wustl.edu>
	<56acdb01.132c620a.8cf2f.1fad@mx.google.com>
	<52C055D9-8D8D-4628-ACD1-4F907D627ED8@cs.ucla.edu>
	<56AF8B47.8000902@wustl.edu>
Message-ID: <1C06C9C4-DDE4-4DCA-9A09-455D8F797D4A@cs.ucla.edu>


> On Feb 1, 2016, at 8:43 AM, Jyoti Parwatikar <jp at wustl.edu> wrote:
> 
> Yingdi,
> 
> This is the error message.
> 
> Cannot read certificate from file: /users/jp/ndn/JPChronolog/cfg-files/wustl.cert

Can you also check that the directory permissions are right (= read and execute is for user, group, and others)?

> 
> -Jyoti
> 
> On 01/31/2016 01:28 AM, Yingdi Yu wrote:
>> Hi Jyoti,
>> 
>> Could you also share the error msg? You can get that be catch std::runtime_error around load() method, and the print out e.what(), e.g.,
>> 
>> try {
>>   validator.load(?);
>> }
>> catch (const std::runtime_error& e) {
>>   std::cerr << e.what() << std::endl;
>> }
>> 
>> The error message may help us to figure out what kind of error is detected. Thanks!
>> 
>> Yingdi
>> 
>> 
>> 
>> 
>>> On Jan 30, 2016, at 7:47 AM, Junxiao Shi <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> wrote:
>>> 
>>> Hi Jyoti
>>> 
>>> Your certificate file and Unix permissions appear to be valid.
>>> 
>>> Can Yingdi have a look at this case?
>>> 
>>> Yours, Junxiao
>>> 
>>> From: Jyoti Parwatikar <mailto:jp at wustl.edu>
>>> Sent: Monday, January 25, 2016 09:46
>>> To: Junxiao Shi <mailto:shijunxiao at email.arizona.edu>
>>> Cc: ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>
>>> Subject: Re: [Ndn-interest] using ValidatorConfig
>>> 
>>> Hi Junxiao,
>>> 
>>> I just got back to working on this.
>>> I suspect my certificate is probably incorrect. When I step through the code, it is failing to create the IdentityCertificate from the file in  ndn::security::conf::CheckerFactory::getSigner(const ConfigSection&, const string&)
>>> I can see it read in from the configuration file and it's reading the other parameters fine. It's failing when it hits the creation of the signer in the checker.
>>> 
>>> The process is run as me. And the certificate file has permission 644.
>>> First line of certificate file: Bv0C1QczCAV3dXN0bAgDS0VZCBFkc2stMTQ1Mjg3Mjk2ODQ2OAgHSUQtQ0VSVAgJ
>>> 
>>> My configuration file:
>>> rule
>>> {
>>>    id "h1x1 data rule"
>>>    for data
>>>    filter
>>>    {
>>>       type name
>>>       name /wustl/CHRONOLOG
>>>       relation is-prefix-of
>>>    }
>>>    checker
>>>    {
>>>       type fixed-signer
>>>       sig-type rsa-sha256
>>>       signer
>>>       {
>>>          type file
>>>          file-name "/users/jp/ndn/JPChronolog/cfg-files/wustl.cert"
>>>       }
>>>    }
>>> }
>>> 
>>> -Jyoti
>>> 
>>> 
>>> On 01/15/2016 12:20 PM, Junxiao Shi wrote:
>>> Hi Jyoti
>>> 
>>> If giving the full path still doesn?t work, reply-all with the following:
>>> the complete ValidatorConfig configuration
>>> the code snippet that loads the configuration; in particular, is it loaded from a file or from a string
>>> the full path of your certificate file
>>> the first line of your certificate file (this helps determining whether you have the correct format in the certificate file)
>>> what is the current working directory
>>> what is the effective uid of the running program, and what Unix permissions does this uid have on the certificate file
>>> 
>>> Yours, Junxiao
>> 
> 
> _______________________________________________
> 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/20160202/570e3b86/attachment.html>
-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160202/570e3b86/attachment.bin>

From jp at wustl.edu  Wed Feb  3 04:32:58 2016
From: jp at wustl.edu (Jyoti Parwatikar)
Date: Wed, 3 Feb 2016 06:32:58 -0600
Subject: [Ndn-interest] using ValidatorConfig
In-Reply-To: <1C06C9C4-DDE4-4DCA-9A09-455D8F797D4A@cs.ucla.edu>
References: <56991C63.7050404@wustl.edu>
	<2795B60D-3C1D-4FDF-8A02-A2B078244AEE@email.arizona.edu>
	<56993894.8030406@wustl.edu>
	<EA870886-01D7-4E4E-B355-796BD048F91B@email.arizona.edu>
	<56A65160.4090303@wustl.edu>
	<56acdb01.132c620a.8cf2f.1fad@mx.google.com>
	<52C055D9-8D8D-4628-ACD1-4F907D627ED8@cs.ucla.edu>
	<56AF8B47.8000902@wustl.edu>
	<1C06C9C4-DDE4-4DCA-9A09-455D8F797D4A@cs.ucla.edu>
Message-ID: <56B1F37A.2040707@wustl.edu>

permissions are 755 for directories and 644 on wustl.cert

On 02/02/2016 01:50 PM, Alex Afanasyev wrote:
>
>> On Feb 1, 2016, at 8:43 AM, Jyoti Parwatikar <jp at wustl.edu 
>> <mailto:jp at wustl.edu>> wrote:
>>
>> Yingdi,
>>
>> This is the error message.
>>
>> Cannot read certificate from file: 
>> /users/jp/ndn/JPChronolog/cfg-files/wustl.cert
>
> Can you also check that the directory permissions are right (= read 
> and execute is for user, group, and others)?
>
>>
>> -Jyoti
>>
>> On 01/31/2016 01:28 AM, Yingdi Yu wrote:
>>> Hi Jyoti,
>>>
>>> Could you also share the error msg? You can get that be catch 
>>> std::runtime_error around load() method, and the print out e.what(), 
>>> e.g.,
>>>
>>> try {
>>> validator.load(?);
>>> }
>>> catch (const std::runtime_error& e) {
>>> std::cerr << e.what() << std::endl;
>>> }
>>>
>>> The error message may help us to figure out what kind of error is 
>>> detected. Thanks!
>>>
>>> Yingdi
>>>
>>>
>>>
>>>
>>>> On Jan 30, 2016, at 7:47 AM, Junxiao Shi 
>>>> <shijunxiao at email.arizona.edu 
>>>> <mailto:shijunxiao at email.arizona.edu>> wrote:
>>>>
>>>> Hi Jyoti
>>>> Your certificate file and Unix permissions appear to be valid.
>>>> Can Yingdi have a look at this case?
>>>> Yours, Junxiao
>>>>
>>>> *From:*Jyoti Parwatikar <mailto:jp at wustl.edu>
>>>> *Sent:*Monday, January 25, 2016 09:46
>>>> *To:*Junxiao Shi <mailto:shijunxiao at email.arizona.edu>
>>>> *Cc:*ndn-interest at lists.cs.ucla.edu 
>>>> <mailto:ndn-interest at lists.cs.ucla.edu>
>>>> *Subject:*Re: [Ndn-interest] using ValidatorConfig
>>>>
>>>> Hi Junxiao,
>>>>
>>>> I just got back to working on this.
>>>> I suspect my certificate is probably incorrect. When I step through 
>>>> the code, it is failing to create the IdentityCertificate from the 
>>>> file in ndn::security::conf::CheckerFactory::getSigner(const 
>>>> ConfigSection&, const string&)
>>>> I can see it read in from the configuration file and it's reading 
>>>> the other parameters fine. It's failing when it hits the creation 
>>>> of the signer in the checker.
>>>>
>>>> The process is run as me. And the certificate file has permission 644.
>>>> First line of certificate file: 
>>>> Bv0C1QczCAV3dXN0bAgDS0VZCBFkc2stMTQ1Mjg3Mjk2ODQ2OAgHSUQtQ0VSVAgJ
>>>>
>>>> My configuration file:
>>>> rule
>>>> {
>>>> id "h1x1 data rule"
>>>> for data
>>>> filter
>>>> {
>>>> type name
>>>> name /wustl/CHRONOLOG
>>>> relation is-prefix-of
>>>> }
>>>> checker
>>>> {
>>>> type fixed-signer
>>>> sig-type rsa-sha256
>>>> signer
>>>> {
>>>> type file
>>>> file-name "/users/jp/ndn/JPChronolog/cfg-files/wustl.cert"
>>>> }
>>>> }
>>>> }
>>>>
>>>> -Jyoti
>>>>
>>>> On 01/15/2016 12:20 PM, Junxiao Shi wrote:
>>>>
>>>>     Hi Jyoti
>>>>
>>>>     If giving the full path still doesn?t work, reply-all with the
>>>>     following:
>>>>
>>>>       * the complete ValidatorConfig configuration
>>>>       * the code snippet that loads the configuration; in
>>>>         particular, is it loaded from a file or from a string
>>>>       * the full path of your certificate file
>>>>       * the first line of your certificate file (this helps
>>>>         determining whether you have the correct format in the
>>>>         certificate file)
>>>>       * what is the current working directory
>>>>       * what is the effective uid of the running program, and what
>>>>         Unix permissions does this uid have on the certificate file
>>>>
>>>>     Yours, Junxiao
>>>>
>>>
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>

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

From abdouinf45 at gmail.com  Fri Feb  5 06:01:50 2016
From: abdouinf45 at gmail.com (abdou ben)
Date: Fri, 5 Feb 2016 15:01:50 +0100
Subject: [Ndn-interest] help interest flooding
Message-ID: <CADNPHPqgCMu0jt80zjkNtgpN9h1hTfFu0xPee1gYByv4Xu8k-A@mail.gmail.com>

I successfully installed ndnSIM and build it

But i now want to run the code for ddos attack and countermeasures in
interest flooding

Also want to do some changes and evaluate the result

I m very new to ndnSIM


Please help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160205/6b666129/attachment.html>

From david.arjona at uaslp.mx  Fri Feb  5 07:36:37 2016
From: david.arjona at uaslp.mx (=?iso-8859-1?Q?PEDRO_DAVID_ARJONA_VILLICA=D1A?=)
Date: Fri, 5 Feb 2016 09:36:37 -0600
Subject: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
Message-ID: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>

Hello Everybody,

I have been trying to install NLSR in an Ubuntu box (14.04 for desktop), but the "./waf configure" instruction always complains that it cannot find "libndn-cxx". I have tried installing other libraries and I have also run the "sudo ldconfig" instruction, but I still get the same error message. Has anybody experienced a similar problem when installing NLSR or has any ideas on how to fix this problem?

I am attaching the output from running the "./waf configure" instruction in my machine:

---------------------------------------------
OptiPlex-9010:~/NLSR-master$ ./waf configure
Setting top to                           : /home/darjona/NLSR-master 
Setting out to                           : /home/darjona/NLSR-master/build 
Checking for 'g++' (C++ compiler)        : /usr/bin/g++ 
Checking supported CXXFLAGS              : -std=c++11 
Checking supported CXXFLAGS              : -O2 -g -pedantic -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers 
Checking for program 'doxygen'           : /usr/bin/doxygen 
Checking for program 'tar'               : /bin/tar 
Checking for program 'sphinx-build'      : /usr/bin/sphinx-build 
Checking for program 'pkg-config'        : /usr/bin/pkg-config 
Checking for 'libndn-cxx'                : not found 
The configuration failed
(complete log in /home/darjona/NLSR-master/build/config.log)

OptiPlex-9010:~/NLSR-master$ ls
AUTHORS.md  log4cxx.properties.sample.in  README.md         tools
build       nlsr.conf                     src               waf
COPYING.md  nsync                         tests             wscript
docs        README-dev.md                 tests-integrated

OptiPlex-9010:~/NLSR-master$ echo $LD_LIBRARY_PATH
/usr/lib
---------------------------------------------


Thanks,

David

Dr. P. David Arjona Villica?a
Coordinador de la carrera de Ing. en Inform?tica
Av. Dr. Manuel Nava 8
Zona Universitaria, CP 78290
San Luis Potos?, S.L.P.
Tel. +52 (444) 826 2300 ext. 2112


From aa at CS.UCLA.EDU  Sat Feb  6 22:03:12 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Sat, 6 Feb 2016 22:03:12 -0800
Subject: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
In-Reply-To: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>
References: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>
Message-ID: <231820F1-8C47-47A7-B827-E8E279D20419@cs.ucla.edu>

Hi David,

On Ubuntu 14.04, you can install NFD, NLSR and dependencies from PPA (check http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux).

In you case, you seem to be missing ndn-cxx library.  Did you install it?  If you want to install from source, you can either follow installation instructions from ndn-cxx website or simply run

    export NODE_LABELS=Ubuntu
    .jenkins.d/01-dependencies.sh
    .jenkins.d/10-ndn-cxx.sh

These are scripts that are used by our continuous integration system to install and compile all necessary dependencies for NLSR.  You can copy relevant statement from the scripts instead of running them.

---
Alex

> On Feb 5, 2016, at 7:36 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
> 
> Hello Everybody,
> 
> I have been trying to install NLSR in an Ubuntu box (14.04 for desktop), but the "./waf configure" instruction always complains that it cannot find "libndn-cxx". I have tried installing other libraries and I have also run the "sudo ldconfig" instruction, but I still get the same error message. Has anybody experienced a similar problem when installing NLSR or has any ideas on how to fix this problem?
> 
> I am attaching the output from running the "./waf configure" instruction in my machine:
> 
> ---------------------------------------------
> OptiPlex-9010:~/NLSR-master$ ./waf configure
> Setting top to                           : /home/darjona/NLSR-master
> Setting out to                           : /home/darjona/NLSR-master/build
> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
> Checking supported CXXFLAGS              : -std=c++11
> Checking supported CXXFLAGS              : -O2 -g -pedantic -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
> Checking for program 'doxygen'           : /usr/bin/doxygen
> Checking for program 'tar'               : /bin/tar
> Checking for program 'sphinx-build'      : /usr/bin/sphinx-build
> Checking for program 'pkg-config'        : /usr/bin/pkg-config
> Checking for 'libndn-cxx'                : not found
> The configuration failed
> (complete log in /home/darjona/NLSR-master/build/config.log)
> 
> OptiPlex-9010:~/NLSR-master$ ls
> AUTHORS.md  log4cxx.properties.sample.in  README.md         tools
> build       nlsr.conf                     src               waf
> COPYING.md  nsync                         tests             wscript
> docs        README-dev.md                 tests-integrated
> 
> OptiPlex-9010:~/NLSR-master$ echo $LD_LIBRARY_PATH
> /usr/lib
> ---------------------------------------------
> 
> 
> Thanks,
> 
> David
> 
> Dr. P. David Arjona Villica?a
> Coordinador de la carrera de Ing. en Inform?tica
> Av. Dr. Manuel Nava 8
> Zona Universitaria, CP 78290
> San Luis Potos?, S.L.P.
> Tel. +52 (444) 826 2300 ext. 2112
> _________________________________________
-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160206/2fa72fa9/attachment.bin>

From david.arjona at uaslp.mx  Thu Feb 11 08:23:44 2016
From: david.arjona at uaslp.mx (=?iso-8859-1?Q?PEDRO_DAVID_ARJONA_VILLICA=D1A?=)
Date: Thu, 11 Feb 2016 10:23:44 -0600
Subject: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
In-Reply-To: <231820F1-8C47-47A7-B827-E8E279D20419@cs.ucla.edu>
References: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>,
	<231820F1-8C47-47A7-B827-E8E279D20419@cs.ucla.edu>
Message-ID: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563F4@uaslp1120.uaslp.local>

Hi Alex,

I have verified that I installed NFD and all NLSR dependencies. I have also verified that the ndn-cxx library is installed. I cannot see anything missing from my Ubuntu box.

It seems that my only option now is to install from source and compile. I still have one question: Do I need to remove the ndn-cxx library before installing it from source? How about NFD?

Thanks for your kind help!

David

Dr. P. David Arjona Villica?a
Coordinador de Ingenier?a en Inform?tica
Av. Dr. Manuel Nava 8
Zona Universitaria, CP 78290
San Luis Potos?, S.L.P.
Tel. +52 (444) 826 2300 ext. 6137
________________________________________
From: Alex Afanasyev [aa at cs.ucla.edu]
Sent: Sunday, February 07, 2016 12:03 AM
To: PEDRO DAVID ARJONA VILLICA?A
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx

Hi David,

On Ubuntu 14.04, you can install NFD, NLSR and dependencies from PPA (check http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux).

In you case, you seem to be missing ndn-cxx library.  Did you install it?  If you want to install from source, you can either follow installation instructions from ndn-cxx website or simply run

    export NODE_LABELS=Ubuntu
    .jenkins.d/01-dependencies.sh
    .jenkins.d/10-ndn-cxx.sh

These are scripts that are used by our continuous integration system to install and compile all necessary dependencies for NLSR.  You can copy relevant statement from the scripts instead of running them.

---
Alex

> On Feb 5, 2016, at 7:36 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
>
> Hello Everybody,
>
> I have been trying to install NLSR in an Ubuntu box (14.04 for desktop), but the "./waf configure" instruction always complains that it cannot find "libndn-cxx". I have tried installing other libraries and I have also run the "sudo ldconfig" instruction, but I still get the same error message. Has anybody experienced a similar problem when installing NLSR or has any ideas on how to fix this problem?
>
> I am attaching the output from running the "./waf configure" instruction in my machine:
>
> ---------------------------------------------
> OptiPlex-9010:~/NLSR-master$ ./waf configure
> Setting top to                           : /home/darjona/NLSR-master
> Setting out to                           : /home/darjona/NLSR-master/build
> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
> Checking supported CXXFLAGS              : -std=c++11
> Checking supported CXXFLAGS              : -O2 -g -pedantic -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
> Checking for program 'doxygen'           : /usr/bin/doxygen
> Checking for program 'tar'               : /bin/tar
> Checking for program 'sphinx-build'      : /usr/bin/sphinx-build
> Checking for program 'pkg-config'        : /usr/bin/pkg-config
> Checking for 'libndn-cxx'                : not found
> The configuration failed
> (complete log in /home/darjona/NLSR-master/build/config.log)
>
> OptiPlex-9010:~/NLSR-master$ ls
> AUTHORS.md  log4cxx.properties.sample.in  README.md         tools
> build       nlsr.conf                     src               waf
> COPYING.md  nsync                         tests             wscript
> docs        README-dev.md                 tests-integrated
>
> OptiPlex-9010:~/NLSR-master$ echo $LD_LIBRARY_PATH
> /usr/lib
> ---------------------------------------------
>
>
> Thanks,
>
> David
>
> Dr. P. David Arjona Villica?a
> Coordinador de la carrera de Ing. en Inform?tica
> Av. Dr. Manuel Nava 8
> Zona Universitaria, CP 78290
> San Luis Potos?, S.L.P.
> Tel. +52 (444) 826 2300 ext. 2112
> _________________________________________



From aa at CS.UCLA.EDU  Thu Feb 11 09:18:58 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Thu, 11 Feb 2016 09:18:58 -0800
Subject: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
In-Reply-To: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563F4@uaslp1120.uaslp.local>
References: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>
	<231820F1-8C47-47A7-B827-E8E279D20419@cs.ucla.edu>
	<6CC190F8CA9465418E8167FC7260A8A401E6A7B563F4@uaslp1120.uaslp.local>
Message-ID: <F8319FE4-1D0E-4F1C-85B9-C90AE3D3A1F3@cs.ucla.edu>


> On Feb 11, 2016, at 8:23 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
> 
> Hi Alex,
> 
> I have verified that I installed NFD and all NLSR dependencies. I have also verified that the ndn-cxx library is installed. I cannot see anything missing from my Ubuntu box.
> 
> It seems that my only option now is to install from source and compile. I still have one question: Do I need to remove the ndn-cxx library before installing it from source? How about NFD?

You should not mix source and binary installation of ndn-cxx.

Btw. When you installed from binaries, did you install ndn-cxx-dev (development package)?

> 
> Thanks for your kind help!
> 
> David
> 
> Dr. P. David Arjona Villica?a
> Coordinador de Ingenier?a en Inform?tica
> Av. Dr. Manuel Nava 8
> Zona Universitaria, CP 78290
> San Luis Potos?, S.L.P.
> Tel. +52 (444) 826 2300 ext. 6137
> ________________________________________
> From: Alex Afanasyev [aa at cs.ucla.edu]
> Sent: Sunday, February 07, 2016 12:03 AM
> To: PEDRO DAVID ARJONA VILLICA?A
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
> 
> Hi David,
> 
> On Ubuntu 14.04, you can install NFD, NLSR and dependencies from PPA (check http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux).
> 
> In you case, you seem to be missing ndn-cxx library.  Did you install it?  If you want to install from source, you can either follow installation instructions from ndn-cxx website or simply run
> 
>    export NODE_LABELS=Ubuntu
>    .jenkins.d/01-dependencies.sh
>    .jenkins.d/10-ndn-cxx.sh
> 
> These are scripts that are used by our continuous integration system to install and compile all necessary dependencies for NLSR.  You can copy relevant statement from the scripts instead of running them.
> 
> ---
> Alex
> 
>> On Feb 5, 2016, at 7:36 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
>> 
>> Hello Everybody,
>> 
>> I have been trying to install NLSR in an Ubuntu box (14.04 for desktop), but the "./waf configure" instruction always complains that it cannot find "libndn-cxx". I have tried installing other libraries and I have also run the "sudo ldconfig" instruction, but I still get the same error message. Has anybody experienced a similar problem when installing NLSR or has any ideas on how to fix this problem?
>> 
>> I am attaching the output from running the "./waf configure" instruction in my machine:
>> 
>> ---------------------------------------------
>> OptiPlex-9010:~/NLSR-master$ ./waf configure
>> Setting top to                           : /home/darjona/NLSR-master
>> Setting out to                           : /home/darjona/NLSR-master/build
>> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
>> Checking supported CXXFLAGS              : -std=c++11
>> Checking supported CXXFLAGS              : -O2 -g -pedantic -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
>> Checking for program 'doxygen'           : /usr/bin/doxygen
>> Checking for program 'tar'               : /bin/tar
>> Checking for program 'sphinx-build'      : /usr/bin/sphinx-build
>> Checking for program 'pkg-config'        : /usr/bin/pkg-config
>> Checking for 'libndn-cxx'                : not found
>> The configuration failed
>> (complete log in /home/darjona/NLSR-master/build/config.log)
>> 
>> OptiPlex-9010:~/NLSR-master$ ls
>> AUTHORS.md  log4cxx.properties.sample.in  README.md         tools
>> build       nlsr.conf                     src               waf
>> COPYING.md  nsync                         tests             wscript
>> docs        README-dev.md                 tests-integrated
>> 
>> OptiPlex-9010:~/NLSR-master$ echo $LD_LIBRARY_PATH
>> /usr/lib
>> ---------------------------------------------
>> 
>> 
>> Thanks,
>> 
>> David
>> 
>> Dr. P. David Arjona Villica?a
>> Coordinador de la carrera de Ing. en Inform?tica
>> Av. Dr. Manuel Nava 8
>> Zona Universitaria, CP 78290
>> San Luis Potos?, S.L.P.
>> Tel. +52 (444) 826 2300 ext. 2112
>> _________________________________________

-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160211/e7c59e2c/attachment.bin>

From david.arjona at uaslp.mx  Thu Feb 11 11:31:42 2016
From: david.arjona at uaslp.mx (=?iso-8859-1?Q?PEDRO_DAVID_ARJONA_VILLICA=D1A?=)
Date: Thu, 11 Feb 2016 13:31:42 -0600
Subject: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
In-Reply-To: <F8319FE4-1D0E-4F1C-85B9-C90AE3D3A1F3@cs.ucla.edu>
References: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563E1@uaslp1120.uaslp.local>
	<231820F1-8C47-47A7-B827-E8E279D20419@cs.ucla.edu>
	<6CC190F8CA9465418E8167FC7260A8A401E6A7B563F4@uaslp1120.uaslp.local>,
	<F8319FE4-1D0E-4F1C-85B9-C90AE3D3A1F3@cs.ucla.edu>
Message-ID: <6CC190F8CA9465418E8167FC7260A8A401E6A7B563F6@uaslp1120.uaslp.local>

Hi Alex,

THAT WAS IT!!!

After I installed the ndn-cxx-dev library, the "./waf configure" instruction ran successfully.

Thanks for your help!

David

Dr. P. David Arjona Villica?a
Coordinador de Ingenier?a en Inform?tica
Av. Dr. Manuel Nava 8
Zona Universitaria, CP 78290
San Luis Potos?, S.L.P.
Tel. +52 (444) 826 2300 ext. 6137
________________________________________
From: Alex Afanasyev [aa at cs.ucla.edu]
Sent: Thursday, February 11, 2016 11:18 AM
To: PEDRO DAVID ARJONA VILLICA?A
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx

> On Feb 11, 2016, at 8:23 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
>
> Hi Alex,
>
> I have verified that I installed NFD and all NLSR dependencies. I have also verified that the ndn-cxx library is installed. I cannot see anything missing from my Ubuntu box.
>
> It seems that my only option now is to install from source and compile. I still have one question: Do I need to remove the ndn-cxx library before installing it from source? How about NFD?

You should not mix source and binary installation of ndn-cxx.

Btw. When you installed from binaries, did you install ndn-cxx-dev (development package)?

>
> Thanks for your kind help!
>
> David
>
> Dr. P. David Arjona Villica?a
> Coordinador de Ingenier?a en Inform?tica
> Av. Dr. Manuel Nava 8
> Zona Universitaria, CP 78290
> San Luis Potos?, S.L.P.
> Tel. +52 (444) 826 2300 ext. 6137
> ________________________________________
> From: Alex Afanasyev [aa at cs.ucla.edu]
> Sent: Sunday, February 07, 2016 12:03 AM
> To: PEDRO DAVID ARJONA VILLICA?A
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] NLSR: ./waf configure cannot find libndn-cxx
>
> Hi David,
>
> On Ubuntu 14.04, you can install NFD, NLSR and dependencies from PPA (check http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux).
>
> In you case, you seem to be missing ndn-cxx library.  Did you install it?  If you want to install from source, you can either follow installation instructions from ndn-cxx website or simply run
>
>    export NODE_LABELS=Ubuntu
>    .jenkins.d/01-dependencies.sh
>    .jenkins.d/10-ndn-cxx.sh
>
> These are scripts that are used by our continuous integration system to install and compile all necessary dependencies for NLSR.  You can copy relevant statement from the scripts instead of running them.
>
> ---
> Alex
>
>> On Feb 5, 2016, at 7:36 AM, PEDRO DAVID ARJONA VILLICA?A <david.arjona at uaslp.mx> wrote:
>>
>> Hello Everybody,
>>
>> I have been trying to install NLSR in an Ubuntu box (14.04 for desktop), but the "./waf configure" instruction always complains that it cannot find "libndn-cxx". I have tried installing other libraries and I have also run the "sudo ldconfig" instruction, but I still get the same error message. Has anybody experienced a similar problem when installing NLSR or has any ideas on how to fix this problem?
>>
>> I am attaching the output from running the "./waf configure" instruction in my machine:
>>
>> ---------------------------------------------
>> OptiPlex-9010:~/NLSR-master$ ./waf configure
>> Setting top to                           : /home/darjona/NLSR-master
>> Setting out to                           : /home/darjona/NLSR-master/build
>> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
>> Checking supported CXXFLAGS              : -std=c++11
>> Checking supported CXXFLAGS              : -O2 -g -pedantic -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
>> Checking for program 'doxygen'           : /usr/bin/doxygen
>> Checking for program 'tar'               : /bin/tar
>> Checking for program 'sphinx-build'      : /usr/bin/sphinx-build
>> Checking for program 'pkg-config'        : /usr/bin/pkg-config
>> Checking for 'libndn-cxx'                : not found
>> The configuration failed
>> (complete log in /home/darjona/NLSR-master/build/config.log)
>>
>> OptiPlex-9010:~/NLSR-master$ ls
>> AUTHORS.md  log4cxx.properties.sample.in  README.md         tools
>> build       nlsr.conf                     src               waf
>> COPYING.md  nsync                         tests             wscript
>> docs        README-dev.md                 tests-integrated
>>
>> OptiPlex-9010:~/NLSR-master$ echo $LD_LIBRARY_PATH
>> /usr/lib
>> ---------------------------------------------
>>
>>
>> Thanks,
>>
>> David
>>
>> Dr. P. David Arjona Villica?a
>> Coordinador de la carrera de Ing. en Inform?tica
>> Av. Dr. Manuel Nava 8
>> Zona Universitaria, CP 78290
>> San Luis Potos?, S.L.P.
>> Tel. +52 (444) 826 2300 ext. 2112
>> _________________________________________




From shijunxiao at email.arizona.EDU  Thu Feb 11 16:27:51 2016
From: shijunxiao at email.arizona.EDU (Junxiao Shi)
Date: Thu, 11 Feb 2016 17:27:51 -0700
Subject: [Ndn-interest] Error when trying to build ndn-cxx on CentOS 7
In-Reply-To: <CAF7W2mng9ys-GkQTvnFyJ25tn0ayEDkv=PkNXkYBR8CYrkKn_g@mail.gmail.com>
References: <CAF7W2mng9ys-GkQTvnFyJ25tn0ayEDkv=PkNXkYBR8CYrkKn_g@mail.gmail.com>
Message-ID: <CAOFH+Obzq=5POx8-QBYh+7FH6QRfsJbDHZ2r8Uz1xQtwnPn=xg@mail.gmail.com>

Dear folks

I'm seeing a similar error related to sphinx redmine_issue when building on
OSX 10.9.
http://jenkins.named-data.net/job/NFD/3605/OS=OSX-10.9-64bit/console
Extension error: Could not import extension redmine_issue (exception: No
module named redmine_issue)

Yours, Junxiao
On Nov 12, 2015 20:46, "Alexander Ni" <alexni1992 at gmail.com> wrote:

> Hi all,
>
> I have problem with ndn-cxx library building,
> when use:
> ./waf configure
> Setting top to                           : /home/kim/ndn-cxx
> Setting out to                           : /home/kim/ndn-cxx/build
> Building static library                  : no
> Building shared library                  : yes
> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
> Checking supported CXXFLAGS              : -std=c++11
> Checking supported CXXFLAGS              : -pedantic -Wall -O2 -g
> Checking for program 'doxygen'           : /usr/bin/doxygen
> Checking for program 'tar'               : /usr/bin/tar
> Checking for program 'sphinx-build'      : /usr/local/bin/sphinx-build
> Checking for std::is_default_constructible : yes
> Checking for std::is_nothrow_move_constructible : yes
> Checking for std::is_nothrow_move_assignable    : yes
> Checking for friend typename-specifier          : yes
> Checking for override and final specifiers      : yes
> Checking for std::to_string                     : yes
> Checking for std::vector::insert with const_iterator : no
> Checking for program 'sh'                            : /usr/bin/sh
> Checking for library pthread                         : yes
> Checking for library rt                              : yes
> Checking for function getpass                        : yes
> Checking for rtnetlink                               : yes
> Checking for program 'pkg-config'                    : /usr/bin/pkg-config
> Checking for 'sqlite3'                               : yes
> Checking Crypto++ lib                                : 562
> Checking if CryptoPP library works                   : yes
> Checking boost includes                              : 1.53.0
> Checking boost libs                                  : ok
> Checking for boost linkage                           : ok
> 'configure' finished successfully (4.702s)
>
> ./waf
>
> I get next:
>
> [ 28/140] Processing sphinx_build [man]: docs/manpages/ndn-client.conf.rst
> docs/manpages/ndnsec-cert-dump.rst docs/manpages/ndnsec-cert-gen.rst
> docs/manpages/ndnsec-cert-install.rst docs/manpages/ndnsec-cert-revoke.rst
> docs/manpages/ndnsec-delete.rst docs/manpages/ndnsec-dsk-gen.rst
> docs/manpages/ndnsec-export.rst docs/manpages/ndnsec-get-default.rst
> docs/manpages/ndnsec-import.rst docs/manpages/ndnsec-key-gen.rst
> docs/manpages/ndnsec-list.rst docs/manpages/ndnsec-set-acl.rst
> docs/manpages/ndnsec-set-default.rst docs/manpages/ndnsec-sign-req.rst
> docs/manpages/ndnsec-unlock-tpm.rst docs/manpages/ndnsec.rst
> docs/manpages/tlvdump.rst docs/conf.py -> build/docs/manpages/ndnsec.1
> build/docs/manpages/ndnsec-cert-dump.1
> build/docs/manpages/ndnsec-cert-gen.1
> build/docs/manpages/ndnsec-cert-revoke.1
> build/docs/manpages/ndnsec-cert-instal.1
> build/docs/manpages/ndnsec-delete.1 build/docs/manpages/ndnsec-export.1
> build/docs/manpages/ndnsec-get-default.1
> build/docs/manpages/ndnsec-import.1 build/docs/manpages/ndnsec-key-gen.1
> build/docs/manpages/ndnsec-list.1 build/docs/manpages/ndnsec-set-acl.1
> build/docs/manpages/ndnsec-set-default.1
> build/docs/manpages/ndnsec-sign-req.1
> build/docs/manpages/ndnsec-unlock-tpm.1
> build/docs/manpages/ndnsec-validator.conf.5 build/docs/manpages/tlvdump.1
> build/docs/manpages/ndn-client.conf.5
>
> 21:45:56 runner (exec) /usr/local/bin/sphinx-build -D version=0.4.0-beta1
> -D release=0.4.0-beta1 -q -b man -d
> /home/kim/ndn-cxx/build/docs/manpages/.doctrees /home/kim/ndn-cxx/docs
> /home/kim/ndn-cxx/build/docs/manpages
> 21:45:56 runner_env kw={'shell': False, 'cwd': '/home/kim/ndn-cxx/build',
> 'env': None}
>
> Exception occurred:
>   File "/usr/local/lib/python3.4/site-packages/sphinx/application.py",
> line 429, in setup_extension
>     mod = __import__(extension, None, None, ['setup'])
>   File "/home/kim/ndn-cxx/docs/redmine_issue.py", line 53
>     except AttributeError, err:
>                          ^
> SyntaxError: invalid syntax
> The full traceback has been saved in /tmp/sphinx-err-roag11_6.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at <
> https://github.com/sphinx-doc/sphinx/issues>. Thanks!
>
> Waf: Leaving directory `/home/kim/ndn-cxx/build'
>   File "./waf", line 165, in <module>
>     Scripting.waf_entry_point(cwd, VERSION, wafdir)
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py",
> line 103, in waf_entry_point
>     run_commands()
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py",
> line 164, in run_commands
>     ctx=run_command(cmd_name)
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py",
> line 155, in run_command
>     ctx.execute()
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py",
> line 366, in execute
>     return execute_method(self)
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py",
> line 106, in execute
>     self.execute_build()
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py",
> line 113, in execute_build
>     self.compile()
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Tools/errcheck.py",
> line 124, in check_compile
>     ret=self.orig_compile()
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py",
> line 184, in compile
>     raise Errors.BuildError(self.producer.error)
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Errors.py",
> line 25, in __init__
>     WafError.__init__(self,self.format_error())
>
> Build failed
>  -> task in '' failed (exit status 1):
>         {task 19312784: sphinx_build
> ndn-client.conf.rst,ndnsec-cert-dump.rst,ndnsec-cert-gen.rst,ndnsec-cert-install.rst,ndnsec-cert-revoke.rst,ndnsec-delete.rst,ndnsec-dsk-gen.rst,ndnsec-export.rst,ndnsec-get-default.rst,ndnsec-import.rst,ndnsec-key-gen.rst,ndnsec-list.rst,ndnsec-set-acl.rst,ndnsec-set-default.rst,ndnsec-sign-req.rst,ndnsec-unlock-tpm.rst,ndnsec.rst,tlvdump.rst,conf.py
> ->
> ndnsec.1,ndnsec-cert-dump.1,ndnsec-cert-gen.1,ndnsec-cert-revoke.1,ndnsec-cert-instal.1,ndnsec-delete.1,ndnsec-export.1,ndnsec-get-default.1,ndnsec-import.1,ndnsec-key-gen.1,ndnsec-list.1,ndnsec-set-acl.1,ndnsec-set-default.1,ndnsec-sign-req.1,ndnsec-unlock-tpm.1,ndnsec-validator.conf.5,tlvdump.1,ndn-client.conf.5}
> ['/usr/local/bin/sphinx-build', '-D', 'version=0.4.0-beta1', '-D',
> 'release=0.4.0-beta1', '-q', '-b', 'man', '-d',
> '/home/kim/ndn-cxx/build/docs/manpages/.doctrees',
> '/home/kim/ndn-cxx/docs', '/home/kim/ndn-cxx/build/docs/manpages']
>   File "./waf", line 165, in <module>
>         Scripting.waf_entry_point(cwd, VERSION, wafdir)
>   File
> "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py",
> line 107, in waf_entry_point
>         Logs.error(e.msg)
>
> As I understand that there is some problem with python platform but I
> don't really understand how can I specify which version of python should be
> used. Can somebody explain me this?
>
> When I by force change the sphinx-build location in "build/c4che/_cache.py"
> (I do this just to check) and it builds ok.
>
> Best Regards,
> Alexander Ni
>
>
> _______________________________________________
> 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/20160211/6b39ac27/attachment.html>

From aa at CS.UCLA.EDU  Thu Feb 11 16:41:28 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Thu, 11 Feb 2016 16:41:28 -0800
Subject: [Ndn-interest] Error when trying to build ndn-cxx on CentOS 7
In-Reply-To: <CAOFH+Obzq=5POx8-QBYh+7FH6QRfsJbDHZ2r8Uz1xQtwnPn=xg@mail.gmail.com>
References: <CAF7W2mng9ys-GkQTvnFyJ25tn0ayEDkv=PkNXkYBR8CYrkKn_g@mail.gmail.com>
	<CAOFH+Obzq=5POx8-QBYh+7FH6QRfsJbDHZ2r8Uz1xQtwnPn=xg@mail.gmail.com>
Message-ID: <2168D07D-AB5E-4BAF-A451-A0D2597D7052@cs.ucla.edu>

The error on jenkins is because something went wrong during repository checkout / caching of /tmp/ndn-cxx.  Should not be related to Alexander's problem.

I think Alexander's problem related to Python version.  Alexander, can you check your python version?  Is it <2.6 or >=3.0

---
Alex

> On Feb 11, 2016, at 4:27 PM, Junxiao Shi <shijunxiao at email.arizona.EDU> wrote:
> 
> Dear folks
> 
> I'm seeing a similar error related to sphinx redmine_issue when building on OSX 10.9.
> http://jenkins.named-data.net/job/NFD/3605/OS=OSX-10.9-64bit/console <http://jenkins.named-data.net/job/NFD/3605/OS=OSX-10.9-64bit/console>
> Extension error: Could not import extension redmine_issue (exception: No module named redmine_issue)
> 
> Yours, Junxiao
> 
> On Nov 12, 2015 20:46, "Alexander Ni" <alexni1992 at gmail.com <mailto:alexni1992 at gmail.com>> wrote:
> Hi all,
> 
> I have problem with ndn-cxx library building,
> when use:
> ./waf configure
> Setting top to                           : /home/kim/ndn-cxx
> Setting out to                           : /home/kim/ndn-cxx/build
> Building static library                  : no
> Building shared library                  : yes
> Checking for 'g++' (C++ compiler)        : /usr/bin/g++
> Checking supported CXXFLAGS              : -std=c++11
> Checking supported CXXFLAGS              : -pedantic -Wall -O2 -g
> Checking for program 'doxygen'           : /usr/bin/doxygen
> Checking for program 'tar'               : /usr/bin/tar
> Checking for program 'sphinx-build'      : /usr/local/bin/sphinx-build
> Checking for std::is_default_constructible : yes
> Checking for std::is_nothrow_move_constructible : yes
> Checking for std::is_nothrow_move_assignable    : yes
> Checking for friend typename-specifier          : yes
> Checking for override and final specifiers      : yes
> Checking for std::to_string                     : yes
> Checking for std::vector::insert with const_iterator : no
> Checking for program 'sh'                            : /usr/bin/sh
> Checking for library pthread                         : yes
> Checking for library rt                              : yes
> Checking for function getpass                        : yes
> Checking for rtnetlink                               : yes
> Checking for program 'pkg-config'                    : /usr/bin/pkg-config
> Checking for 'sqlite3'                               : yes
> Checking Crypto++ lib                                : 562
> Checking if CryptoPP library works                   : yes
> Checking boost includes                              : 1.53.0
> Checking boost libs                                  : ok
> Checking for boost linkage                           : ok
> 'configure' finished successfully (4.702s)
> 
> ./waf
> 
> I get next:
> 
> [ 28/140] Processing sphinx_build [man]: docs/manpages/ndn-client.conf.rst docs/manpages/ndnsec-cert-dump.rst docs/manpages/ndnsec-cert-gen.rst docs/manpages/ndnsec-cert-install.rst docs/manpages/ndnsec-cert-revoke.rst docs/manpages/ndnsec-delete.rst docs/manpages/ndnsec-dsk-gen.rst docs/manpages/ndnsec-export.rst docs/manpages/ndnsec-get-default.rst docs/manpages/ndnsec-import.rst docs/manpages/ndnsec-key-gen.rst docs/manpages/ndnsec-list.rst docs/manpages/ndnsec-set-acl.rst docs/manpages/ndnsec-set-default.rst docs/manpages/ndnsec-sign-req.rst docs/manpages/ndnsec-unlock-tpm.rst docs/manpages/ndnsec.rst docs/manpages/tlvdump.rst docs/conf.py -> build/docs/manpages/ndnsec.1 build/docs/manpages/ndnsec-cert-dump.1 build/docs/manpages/ndnsec-cert-gen.1 build/docs/manpages/ndnsec-cert-revoke.1 build/docs/manpages/ndnsec-cert-instal.1 build/docs/manpages/ndnsec-delete.1 build/docs/manpages/ndnsec-export.1 build/docs/manpages/ndnsec-get-default.1 build/docs/manpages/ndnsec-import.1 build/docs/manpages/ndnsec-key-gen.1 build/docs/manpages/ndnsec-list.1 build/docs/manpages/ndnsec-set-acl.1 build/docs/manpages/ndnsec-set-default.1 build/docs/manpages/ndnsec-sign-req.1 build/docs/manpages/ndnsec-unlock-tpm.1 build/docs/manpages/ndnsec-validator.conf.5 build/docs/manpages/tlvdump.1 build/docs/manpages/ndn-client.conf.5
> 
> 21:45:56 runner (exec) /usr/local/bin/sphinx-build -D version=0.4.0-beta1 -D release=0.4.0-beta1 -q -b man -d /home/kim/ndn-cxx/build/docs/manpages/.doctrees /home/kim/ndn-cxx/docs /home/kim/ndn-cxx/build/docs/manpages
> 21:45:56 runner_env kw={'shell': False, 'cwd': '/home/kim/ndn-cxx/build', 'env': None}
> 
> Exception occurred:
>   File "/usr/local/lib/python3.4/site-packages/sphinx/application.py", line 429, in setup_extension
>     mod = __import__(extension, None, None, ['setup'])
>   File "/home/kim/ndn-cxx/docs/redmine_issue.py", line 53
>     except AttributeError, err:
>                          ^
> SyntaxError: invalid syntax
> The full traceback has been saved in /tmp/sphinx-err-roag11_6.log, if you want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error message can be provided next time.
> A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues <https://github.com/sphinx-doc/sphinx/issues>>. Thanks!
> 
> Waf: Leaving directory `/home/kim/ndn-cxx/build'
>   File "./waf", line 165, in <module>
>     Scripting.waf_entry_point(cwd, VERSION, wafdir)
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py", line 103, in waf_entry_point
>     run_commands()
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py", line 164, in run_commands
>     ctx=run_command(cmd_name)
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py", line 155, in run_command
>     ctx.execute()
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py", line 366, in execute
>     return execute_method(self)
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py", line 106, in execute
>     self.execute_build()
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py", line 113, in execute_build
>     self.compile()
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Tools/errcheck.py", line 124, in check_compile
>     ret=self.orig_compile()
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Build.py", line 184, in compile
>     raise Errors.BuildError(self.producer.error)
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Errors.py", line 25, in __init__
>     WafError.__init__(self,self.format_error())
> 
> Build failed
>  -> task in '' failed (exit status 1):
>         {task 19312784: sphinx_build ndn-client.conf.rst,ndnsec-cert-dump.rst,ndnsec-cert-gen.rst,ndnsec-cert-install.rst,ndnsec-cert-revoke.rst,ndnsec-delete.rst,ndnsec-dsk-gen.rst,ndnsec-export.rst,ndnsec-get-default.rst,ndnsec-import.rst,ndnsec-key-gen.rst,ndnsec-list.rst,ndnsec-set-acl.rst,ndnsec-set-default.rst,ndnsec-sign-req.rst,ndnsec-unlock-tpm.rst,ndnsec.rst,tlvdump.rst,conf.py -> ndnsec.1,ndnsec-cert-dump.1,ndnsec-cert-gen.1,ndnsec-cert-revoke.1,ndnsec-cert-instal.1,ndnsec-delete.1,ndnsec-export.1,ndnsec-get-default.1,ndnsec-import.1,ndnsec-key-gen.1,ndnsec-list.1,ndnsec-set-acl.1,ndnsec-set-default.1,ndnsec-sign-req.1,ndnsec-unlock-tpm.1,ndnsec-validator.conf.5,tlvdump.1,ndn-client.conf.5}
> ['/usr/local/bin/sphinx-build', '-D', 'version=0.4.0-beta1', '-D', 'release=0.4.0-beta1', '-q', '-b', 'man', '-d', '/home/kim/ndn-cxx/build/docs/manpages/.doctrees', '/home/kim/ndn-cxx/docs', '/home/kim/ndn-cxx/build/docs/manpages']
>   File "./waf", line 165, in <module>
>         Scripting.waf_entry_point(cwd, VERSION, wafdir)
>   File "/home/kim/ndn-cxx/.waf-1.8.9-849024857bd41c3cf8e87dc01ecf79b0/waflib/Scripting.py", line 107, in waf_entry_point
>         Logs.error(e.msg)
> 
> As I understand that there is some problem with python platform but I don't really understand how can I specify which version of python should be used. Can somebody explain me this?
> 
> When I by force change the sphinx-build location in "build/c4che/_cache.py" (I do this just to check) and it builds ok.
> 
> Best Regards,
> Alexander Ni
> 
> 
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160211/b8dbf72f/attachment.html>
-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160211/b8dbf72f/attachment.bin>

From M.AbdollahiSabet at mail.sbu.ac.ir  Fri Feb 12 09:35:36 2016
From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet)
Date: Fri, 12 Feb 2016 21:05:36 +0330
Subject: [Ndn-interest] Local hub discovery procedure
Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir>

Hello everyone,

As far as I understood, according to:
http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html
http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm

When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub. Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data. If I'm wrong some where, please correct me.

Right now I have these two multiaccess faces:
-udp4://224.0.23.170:56363
-ether://[01:00:5e:00:17:aa]
I know the former is IANA assigned, but I don't know the latter. My question are:
1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.

Thanks,
Sabet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160212/487a35d7/attachment.html>

From aa at CS.UCLA.EDU  Fri Feb 12 12:47:58 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Fri, 12 Feb 2016 12:47:58 -0800
Subject: [Ndn-interest] [NDN-TR] NDN-0038 revision 1: Challenges in IoT
	Networking via TCP/IP Architecture
Message-ID: <7A5A801A-4B52-4BC2-92CC-39753EDEB115@cs.ucla.edu>

A new NDN Technical Report (initial revision) is now available on NDN website.
Comments and suggestions are highly welcome.

   Title         : Challenges in IoT Networking via TCP/IP Architecture
   Authors       : Wentao Shang, Yingdi Yu, Ralph Droms, Lixia Zhang
   Number        : NDN-0038
   Revision      : 1
   Revision Date : February 10, 2016

Abstract:
    ?Internet of Things? (IoT), networking (potentially) a large number of
    resource-constrained devices, is gaining popularity in recent
    years. Today?s IoT systems are largely based on the use of the TCP/IP
    protocols (IPv6 in particular). However, the observations so far
    suggest that the TCP/IP protocol stack, as originally designed, is not
    a good fit to the IoT environment. Over the last several years the
    IETF has spent significant amount of effort in modifying the protocol
    stack to fit IoT deployment scenarios. These efforts have resulted in
    extensions to existing protocols in the TCP/IP protocol suite as well
    as development of multiple new protocols. Yet new problems
    continuously occur. In this paper we analyze the technical challenges
    in applying TCP/IP to the IoT environment and review various solutions
    proposed by the IETF. We argue that existing IP-based solutions are
    either inefficient or insufficient in supporting IoT applications, and
    that a more effective solution would embrace the Information Centric
    Network architecture.

Information page for this TR:
    http://named-data.net/publications/techreports/ndn-0038-1-challenges-iot/

Direct link to PDF:
    http://named-data.net/wp-content/uploads/2016/02/ndn-0038-1-challenges-iot.pdf

Other NDN Technical Reports:
    http://named-data.net/publications/techreports/

-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160212/e871b949/attachment.bin>

From aa at CS.UCLA.EDU  Fri Feb 12 13:01:01 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Fri, 12 Feb 2016 13:01:01 -0800
Subject: [Ndn-interest] [NDN-TR] NDN-0034 revision 2: Name-Based Access
	Control
Message-ID: <BE107808-2087-4288-B212-C4CBEB6165EB@cs.ucla.edu>

A new revision of NDN Technical report is now available on NDN website.
Comments and suggestions are highly welcome.

   Title         : Name-Based Access Control
   Authors       : Yingdi Yu, Alexander Afanasyev, Lixia Zhang
   Number        : NDN-0034
   Revision      : 2
   Revision Date : January 11, 2016

Abstract:
   This paper presents a content-based access control access control model for
   content stored in network storage. The model enforces the access control directly
   over content through encrypting content at the time of production, rather than
   re- lying on a third party (such as data storage) as traditional perimeter-based
   access control model. We present the de- sign of Name-based Access Control (NAC),
   which implements the content-based access control model in Named Data Networking
   (NDN). We demonstrate how to make use of naming convention to explicitly convey
   access control policy and efficiently distribute access control keys, thus
   enabling effective access control. We evaluate the scalability of NAC against
   CCN-AC, another encryption-based access control scheme. The results suggest that
   NAC is more suitable for large scale distributed data production and consumption.

Information page for this TR:
    http://named-data.net/publications/techreports/ndn-0034-2-nac/

Direct link to PDF:
    http://named-data.net/wp-content/uploads/2016/02/ndn-0034-2-nac.pdf

Other NDN Technical Reports:
    http://named-data.net/publications/techreports/

-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160212/80100345/attachment.bin>

From aa at CS.UCLA.EDU  Fri Feb 12 13:35:14 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Fri, 12 Feb 2016 13:35:14 -0800
Subject: [Ndn-interest] Local hub discovery procedure
In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir>
References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir>
Message-ID: <3589BC92-6B29-4E09-942D-3141B8B7BB56@cs.ucla.edu>


> On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
> 
> Hello everyone,
> 
> As far as I understood, according to:
> http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html <http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html>
> http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm <http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm>
> 
> When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub.
> 
Dear Sabet,

The above correctly describes the basic NDN-native procedure.  Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity.  While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (http://redmine.named-data.net/issues/3465 <http://redmine.named-data.net/issues/3465>).  Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.
> Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data.
> 
Correct, but just to clarify.  As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes.  There is an extension of this mechanism (http://redmine.named-data.net/issues/3145 <http://redmine.named-data.net/issues/3145>) in which local NFD will be expressing such interests.
> If I'm wrong some where, please correct me.
> 
> Right now I have these two multiaccess faces:
> -udp4://224.0.23.170:56363
> -ether://[01:00:5e:00:17:aa]
> I know the former is IANA assigned, but I don't know the latter. My question are:
> 1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
> 
224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).

The shorter answer to your question is most likely yes.  Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.
> 2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.
> 
This is a multicast Ethernet address.  It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (https://technet.microsoft.com/en-us/library/cc957928.aspx <https://technet.microsoft.com/en-us/library/cc957928.aspx>).

Sincerely,
Alex


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160212/f00ee102/attachment.html>
-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160212/f00ee102/attachment.bin>

From M.AbdollahiSabet at mail.sbu.ac.ir  Fri Feb 12 14:00:06 2016
From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet)
Date: Sat, 13 Feb 2016 01:30:06 +0330
Subject: [Ndn-interest] Local hub discovery procedure
References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir>
	<3589BC92-6B29-4E09-942D-3141B8B7BB56@cs.ucla.edu>
Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F6@m-pdc.sbu.ac.ir>

Alex,

Firstly, thank you so much.
Secondly, how is auto-configure-server supposed to work then? This server should somehow receive interests for /localhop/ndn-autoconf/hub. While it's face uri is not on multiaccess faces list, I don't see how it is supposed to work. Actually I tested this. I mean I tried autoconfig-client side on a node which was configured for being autoconfig-server, and needless to say that I got error code 408. Am I to run some multicast capability in my home network to be able to use autoconfig client-server system?
Third, assuming the above issues have passed, if I poke for /localhop/nfd/rib/routable-prefixes, I(an application) should receive available prefix(es) for publishing data, right?

Thanks,
Sabet 

-----Original Message-----
From: Alex Afanasyev [mailto:aa at cs.ucla.edu]
Sent: Sat 2/13/2016 1:05 AM
To: Muhammad Hosain Abdollahi Sabet
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure
 

> On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
> 
> Hello everyone,
> 
> As far as I understood, according to:
> http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html <http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html>
> http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm <http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm>
> 
> When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub.
> 
Dear Sabet,

The above correctly describes the basic NDN-native procedure.  Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity.  While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (http://redmine.named-data.net/issues/3465 <http://redmine.named-data.net/issues/3465>).  Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.
> Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data.
> 
Correct, but just to clarify.  As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes.  There is an extension of this mechanism (http://redmine.named-data.net/issues/3145 <http://redmine.named-data.net/issues/3145>) in which local NFD will be expressing such interests.
> If I'm wrong some where, please correct me.
> 
> Right now I have these two multiaccess faces:
> -udp4://224.0.23.170:56363
> -ether://[01:00:5e:00:17:aa]
> I know the former is IANA assigned, but I don't know the latter. My question are:
> 1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
> 
224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).

The shorter answer to your question is most likely yes.  Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.
> 2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.
> 
This is a multicast Ethernet address.  It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (https://technet.microsoft.com/en-us/library/cc957928.aspx <https://technet.microsoft.com/en-us/library/cc957928.aspx>).

Sincerely,
Alex



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

From M.AbdollahiSabet at mail.sbu.ac.ir  Sun Feb 14 00:45:49 2016
From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet)
Date: Sun, 14 Feb 2016 12:15:49 +0330
Subject: [Ndn-interest] Local hub discovery procedure
References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir><3589BC92-6B29-4E09-942D-3141B8B7BB56@cs.ucla.edu>
	<4AC03A6244C3C34BB52A7EC60B799C4C03CC29F6@m-pdc.sbu.ac.ir>
Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29FA@m-pdc.sbu.ac.ir>

Hi again,
 
Additional to questions below, I have some others:
How an application is going to choose one prefix? I mean, is there any specefic message the application should send through NFD to autoconfig server, so that the server knows which prefix(es) is(are) allocated and not available anymore? Is there a mechanism for applications to release the prefix(es) they were using for publishing data?
How a router is supposed to know the location of optained prefixes in a LAN? Is there any mechanism available between a autoconfig server and a router or an application and a router to announce obtained prefixes to the router?
 
Thanks,
Sabet

________________________________

From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet
Sent: Sat 2/13/2016 1:30 AM
To: Alex Afanasyev
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure



Alex,

Firstly, thank you so much.
Secondly, how is auto-configure-server supposed to work then? This server should somehow receive interests for /localhop/ndn-autoconf/hub. While it's face uri is not on multiaccess faces list, I don't see how it is supposed to work. Actually I tested this. I mean I tried autoconfig-client side on a node which was configured for being autoconfig-server, and needless to say that I got error code 408. Am I to run some multicast capability in my home network to be able to use autoconfig client-server system?
Third, assuming the above issues have passed, if I poke for /localhop/nfd/rib/routable-prefixes, I(an application) should receive available prefix(es) for publishing data, right?

Thanks,
Sabet

-----Original Message-----
From: Alex Afanasyev [mailto:aa at cs.ucla.edu]
Sent: Sat 2/13/2016 1:05 AM
To: Muhammad Hosain Abdollahi Sabet
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure


> On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
>
> Hello everyone,
>
> As far as I understood, according to:
> http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html <http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html>
> http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm <http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm>
>
> When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub.
>
Dear Sabet,

The above correctly describes the basic NDN-native procedure.  Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity.  While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (http://redmine.named-data.net/issues/3465 <http://redmine.named-data.net/issues/3465>).  Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.
> Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data.
>
Correct, but just to clarify.  As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes.  There is an extension of this mechanism (http://redmine.named-data.net/issues/3145 <http://redmine.named-data.net/issues/3145>) in which local NFD will be expressing such interests.
> If I'm wrong some where, please correct me.
>
> Right now I have these two multiaccess faces:
> -udp4://224.0.23.170:56363
> -ether://[01:00:5e:00:17:aa]
> I know the former is IANA assigned, but I don't know the latter. My question are:
> 1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
>
224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).

The shorter answer to your question is most likely yes.  Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.
> 2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.
>
This is a multicast Ethernet address.  It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (https://technet.microsoft.com/en-us/library/cc957928.aspx <https://technet.microsoft.com/en-us/library/cc957928.aspx>).

Sincerely,
Alex





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

From susmit at cs.colostate.edu  Mon Feb 15 15:33:21 2016
From: susmit at cs.colostate.edu (Susmit)
Date: Mon, 15 Feb 2016 17:33:21 -0600
Subject: [Ndn-interest] 2nd NDN Hackathon Call for Hacks
Message-ID: <CAM4XVkpMfcKRyXQ9nV3rY15X+X6smsdLHTgPeMAa6WrOPgNrPg@mail.gmail.com>

======================================
CALL FOR HACKS
The 2nd Named Data Networking (NDN) Hackathon
March 20-21, UC San Diego Campus, La Jolla, CA
======================================

------------------------------------------
IMPORTANT DATES
------------------------------------------
Submission deadline: March 6, 2016
Acceptance notification: March 13, 2016

------------------------------------------
WEBSITE
------------------------------------------
http://2nd-ndn-hackathon.named-data.net

------------------------------------------
Call for Hacks
------------------------------------------

The NDN Team is organizing our 2nd NDN Hackathon to be held on March 20-21,
2016 at the UC San Diego Campus in La Jolla, CA.  We solicit Hackathon
project proposals that advance the state of NDN.  Participants will have
approximately **12 hours** to work on the projects.

We encourage projects that:

 - directly address NDN research needs,
 - create new NDN tools or modify existing tools,
 - create or improve documentation and how-to guides.

------------------------------------------
SUBMISSION GUIDELINES
------------------------------------------

Proposals should be submitted via email to <2nd-ndn-hackathon at named-data.net>.
Submission templates are available on the Hackathon website.

The submissions should include:

- 1 page description PDF, including contact information of submitter
  and project leader(s), problem statement, approach, contribution to
  NDN, planned tasks to accomplish, knowledge requirements, and what is
  the expected outcome by the end of the Hackathon.

- 1 or 2 PPTx slides, listing the project leader(s) and summarizing the
  problem, contribution, tasks, required knowledge, and expected outcome.

All submitted proposals will be reviewed by the Hacking Committee.
If accepted, the project leader is expected to give a 5 minute ?pitch?
presentation at the beginning of the Hackathon, soliciting participation
from attendees.

Projects will be judged by a panel for the "Best of Hackathon" prize. We
hope that this hackathon will be a fun event for everyone and that projects
will lead to collaborations extending beyond the Hackathon.

------------------------------------------
ORGANIZING COMMITTEE
------------------------------------------

- Alex Afanasyev (University of California, Los Angeles)
- Susmit Shannigrahi (Colorado State University)

------------------------------------------
HACKING COMMITTEE
------------------------------------------

- Davide Pesavento (LIP6 / University Pierre & Marie Curie,
  Sorbonne University)
- Vince Lenhman (University of Memphis)
- Eric Newberry (University of Arizona)
- Wentao Shang (University of California, Los Angeles)
- Hila Ben Abraham (Washington University in St. Louis)
- Peter Gusev (REMAP / University of California, Los Angeles)



From M.AbdollahiSabet at mail.sbu.ac.ir  Tue Feb 16 06:06:42 2016
From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet)
Date: Tue, 16 Feb 2016 17:36:42 +0330
Subject: [Ndn-interest] Local hub discovery procedure
References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir><3589BC92-6B29-4E09-942D-3141B8B7BB56@cs.ucla.edu><4AC03A6244C3C34BB52A7EC60B799C4C03CC29F6@m-pdc.sbu.ac.ir>
	<4AC03A6244C3C34BB52A7EC60B799C4C03CC29FA@m-pdc.sbu.ac.ir>
Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29FB@m-pdc.sbu.ac.ir>

Update!

In 2nd email, answer to 3rd question is yes. Although I still wonder how autoconfig-server supposed to be found natively, having manually created a face to autoconfig-server and registered /localhop/ on it I could run autoconfig. And I got answer(a data packet consisting of an available prefix).

Questions in 3rd email remains unanswered.

Thanks,
Sabet

-----Original Message-----
From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet
Sent: Sun 2/14/2016 12:15 PM
To: Alex Afanasyev
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure
 
Hi again,
 
Additional to questions below, I have some others:
How an application is going to choose one prefix? I mean, is there any specefic message the application should send through NFD to autoconfig server, so that the server knows which prefix(es) is(are) allocated and not available anymore? Is there a mechanism for applications to release the prefix(es) they were using for publishing data?
How a router is supposed to know the location of optained prefixes in a LAN? Is there any mechanism available between a autoconfig server and a router or an application and a router to announce obtained prefixes to the router?
 
Thanks,
Sabet

________________________________

From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet
Sent: Sat 2/13/2016 1:30 AM
To: Alex Afanasyev
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure



Alex,

Firstly, thank you so much.
Secondly, how is auto-configure-server supposed to work then? This server should somehow receive interests for /localhop/ndn-autoconf/hub. While it's face uri is not on multiaccess faces list, I don't see how it is supposed to work. Actually I tested this. I mean I tried autoconfig-client side on a node which was configured for being autoconfig-server, and needless to say that I got error code 408. Am I to run some multicast capability in my home network to be able to use autoconfig client-server system?
Third, assuming the above issues have passed, if I poke for /localhop/nfd/rib/routable-prefixes, I(an application) should receive available prefix(es) for publishing data, right?

Thanks,
Sabet

-----Original Message-----
From: Alex Afanasyev [mailto:aa at cs.ucla.edu]
Sent: Sat 2/13/2016 1:05 AM
To: Muhammad Hosain Abdollahi Sabet
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Local hub discovery procedure


> On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
>
> Hello everyone,
>
> As far as I understood, according to:
> http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html <http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html>
> http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm <http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm>
>
> When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub.
>
Dear Sabet,

The above correctly describes the basic NDN-native procedure.  Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity.  While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (http://redmine.named-data.net/issues/3465 <http://redmine.named-data.net/issues/3465>).  Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.
> Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data.
>
Correct, but just to clarify.  As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes.  There is an extension of this mechanism (http://redmine.named-data.net/issues/3145 <http://redmine.named-data.net/issues/3145>) in which local NFD will be expressing such interests.
> If I'm wrong some where, please correct me.
>
> Right now I have these two multiaccess faces:
> -udp4://224.0.23.170:56363
> -ether://[01:00:5e:00:17:aa]
> I know the former is IANA assigned, but I don't know the latter. My question are:
> 1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
>
224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).

The shorter answer to your question is most likely yes.  Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.
> 2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.
>
This is a multicast Ethernet address.  It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (https://technet.microsoft.com/en-us/library/cc957928.aspx <https://technet.microsoft.com/en-us/library/cc957928.aspx>).

Sincerely,
Alex







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

From aa at CS.UCLA.EDU  Tue Feb 16 11:10:51 2016
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Tue, 16 Feb 2016 11:10:51 -0800
Subject: [Ndn-interest] Local hub discovery procedure
In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29FB@m-pdc.sbu.ac.ir>
References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC29F5@m-pdc.sbu.ac.ir>
	<3589BC92-6B29-4E09-942D-3141B8B7BB56@cs.ucla.edu>
	<4AC03A6244C3C34BB52A7EC60B799C4C03CC29F6@m-pdc.sbu.ac.ir>
	<4AC03A6244C3C34BB52A7EC60B799C4C03CC29FA@m-pdc.sbu.ac.ir>
	<4AC03A6244C3C34BB52A7EC60B799C4C03CC29FB@m-pdc.sbu.ac.ir>
Message-ID: <D4351C34-F244-4FBA-A030-7360F0FA1442@cs.ucla.edu>

Hi Sabet,

Let me try to answer your questions.

1/ How ndn-autoconfig-server receives interests

ndn-autoconfig-server registers with the local NFD two prefixes: /localhop/ndn-autoconf/hub and /localhop/nfd/rib/routable-prefixes.  This means that whenever local NFD receives interests for data name with this prefix, this interests (unless satisfied by cache) will be demultiplexed to the ndn-autoconfig-server process.

Note that it does not matter at all how (on which face) such interests got into the local NFD.  It is job of remote NFDs to properly forward interests.  Or, saying in different way, /localhop/ndn-autoconf/hub should be registered to multicast faces only at the remote NFD.

While it is kind of pointless to run autoconfig-client and autoconfig-server on the same machine, it is a legitimate operations:

--
?  10:42 ~ $ ndn-autoconfig-server -p /hello tcp://spurs.cs.ucla.edu
--
?  10:42 ~ $ ndn-autoconfig
Trying multicast discovery...
About to connect to: tcp4://131.179.196.46:6363
Successfully created face: ControlParameters(FaceId: 267, Uri: tcp4://131.179.196.46:6363, )
Successful in name registration: ControlParameters(Name: /ndn, FaceId: 267, Origin: 66, Cost: 100, Flags: 1, ExpirationPeriod: 9223372036854775807 milliseconds, )
Successful in name registration: ControlParameters(Name: /localhop/nfd, FaceId: 267, Origin: 66, Cost: 100, Flags: 1, ExpirationPeriod: 9223372036854775807 milliseconds, )
--

What happens is that ndn-autoconfig sends an interest, which (in addition to be forwarded out) is immediately dispatched to the local ndn-autoconfig-server, which replies with information about hub URI.

2/ Poking /localhop/nfd/rib/routable-prefixes

If you (application) sends interest for /localhop/nfd/rib/routable-prefixes, it will receive a list of (configured) prefixes that are globally routable towards the hub (= announced in the routing system).  The list does not immediately imply that the application can directly publish under any of those prefixes.

3/ Choosing prefix from /localhop/nfd/rib/routable-prefixes data

There isn't a single answer to this question.  It depends on the use case.

To publish under a name prefix, application should hold a valid key for that namespace.  While the generalization of obtaining keys is an ongoing research and engineering effort, we have developed a few cases of (semi-)automated process.  One of them is ndncert system (http://ndncert.named-data.net/).  There is also an mHealth application specific certification system that has more automation built in.

Therefore, one way to choose prefix is to check whether there is a corresponding certificate and private key for the presented namespace.  Another way would be to pick any of the prefixes and invoke (currently undefined) procedure of obtaining certification for a sub-namespace of the selected prefix.

There is also a third answer to this question: don't pick, but take all of them.  This is the use case of forwarding using LINK objects (http://named-data.net/publications/snamp-ndn-scalability/):  an application registers its own prefix, while notifying others explicitly or via a mapping system that to retrieve data one needs to use a specific LINK object containing one or more delegations (aka globally reachable prefixes).   Note that the presumption that the application needs to have certificate and key still stays.  The difference is in namespaces: application-specific namespace vs. namespace(s) provided by the point-of-attachment NDN hub.

4/ Mechanism between app and router

Just to clear up the picture.  There are two routers in it: one local NFD and zero or many remote NFDs.

Between application and local NFD, we have RIB management protocol: http://redmine.named-data.net/projects/nfd/wiki/FibMgmt.  This enables local NFD to demultiplex incoming interests to the application.

Between local NFD and remote NFD(s).  Currently, we have designed and implemented two mechanisms: routing protocol (NLSR) and automatic prefix propagation (there is an unpublished draft with detailed description that we will make available soon).

With the routing protocol, local NFD makes announcements to the routing system.  The current limitation is that the announced prefixes need to be manually configured.  They may be injected to the routing based on local registrations, though there are several research and engineering questions how exactly it should be done.

Automatic prefix propagation is a simplistic routing-like protocol that applicable in home network-like scenarios (NFD on NDN hub <---> local NFD <---> application).  When properly configured with certificates, the RIB registration from application to local NFD will be automatically "propagated" towards NDN hub.

---
Alex

> On Feb 16, 2016, at 6:06 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
> 
> Update!
> 
> In 2nd email, answer to 3rd question is yes. Although I still wonder how autoconfig-server supposed to be found natively, having manually created a face to autoconfig-server and registered /localhop/ on it I could run autoconfig. And I got answer(a data packet consisting of an available prefix).
> 
> Questions in 3rd email remains unanswered.
> 
> Thanks,
> Sabet
> 
> -----Original Message-----
> From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet
> Sent: Sun 2/14/2016 12:15 PM
> To: Alex Afanasyev
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Local hub discovery procedure
> 
> Hi again,
> 
> Additional to questions below, I have some others:
> How an application is going to choose one prefix? I mean, is there any specefic message the application should send through NFD to autoconfig server, so that the server knows which prefix(es) is(are) allocated and not available anymore? Is there a mechanism for applications to release the prefix(es) they were using for publishing data?
> How a router is supposed to know the location of optained prefixes in a LAN? Is there any mechanism available between a autoconfig server and a router or an application and a router to announce obtained prefixes to the router?
> 
> Thanks,
> Sabet
> 
> ________________________________
> 
> From: Ndn-interest on behalf of Muhammad Hosain Abdollahi Sabet
> Sent: Sat 2/13/2016 1:30 AM
> To: Alex Afanasyev
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Local hub discovery procedure
> 
> 
> 
> Alex,
> 
> Firstly, thank you so much.
> Secondly, how is auto-configure-server supposed to work then? This server should somehow receive interests for /localhop/ndn-autoconf/hub. While it's face uri is not on multiaccess faces list, I don't see how it is supposed to work. Actually I tested this. I mean I tried autoconfig-client side on a node which was configured for being autoconfig-server, and needless to say that I got error code 408. Am I to run some multicast capability in my home network to be able to use autoconfig client-server system?
> Third, assuming the above issues have passed, if I poke for /localhop/nfd/rib/routable-prefixes, I(an application) should receive available prefix(es) for publishing data, right?
> 
> Thanks,
> Sabet
> 
> -----Original Message-----
> From: Alex Afanasyev [mailto:aa at cs.ucla.edu]
> Sent: Sat 2/13/2016 1:05 AM
> To: Muhammad Hosain Abdollahi Sabet
> Cc: ndn-interest at lists.cs.ucla.edu
> Subject: Re: [Ndn-interest] Local hub discovery procedure
> 
> 
> > On Feb 12, 2016, at 9:35 AM, Muhammad Hosain Abdollahi Sabet <M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
> >
> > Hello everyone,
> >
> > As far as I understood, according to:
> > http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html <http://named-data.net/doc/NFD/current/misc/local-prefix-discovery.html>
> > http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm <http://named-data.net/doc/NFD/current/manpages/ndn-autoconfig.htm>
> >
> > When I run ndn-autoconfig, NFD will send an interest to /localhop/ndn-autoconf/hub over a multicast face. After that assuming there is some autoconfig server behind one of the node's multiaccess faces, the node receives a data packet including the face uri of a localhub.
> >
> Dear Sabet,
> 
> The above correctly describes the basic NDN-native procedure.  Just to extend it, as you saw in the documentation, there are two additional stages to help with configuring IP-overlay NDN connectivity.  While not yet formally defined, we are also planning to extend the stages to include discovery using mDNS/DNS-SD protocols (http://redmine.named-data.net/issues/3465 <http://redmine.named-data.net/issues/3465>).  Anecdotally, mDNS queries have higher chances to work than other protocols, even though they utilize the same IP multicast.
> > Then after registering /localhop/ prefix on the very face that it has got from the localhub, the node will again send an interest this time for /localhop/nfd/rib/routable-prefixes and awaits for a data packet including some prefixes which it(interest sender application) can register for publishing data.
> >
> Correct, but just to clarify.  As of right now, "node" in this sentence is any NDN application that wants to obtain information about routable prefixes.  There is an extension of this mechanism (http://redmine.named-data.net/issues/3145 <http://redmine.named-data.net/issues/3145>) in which local NFD will be expressing such interests.
> > If I'm wrong some where, please correct me.
> >
> > Right now I have these two multiaccess faces:
> > -udp4://224.0.23.170:56363
> > -ether://[01:00:5e:00:17:aa]
> > I know the former is IANA assigned, but I don't know the latter. My question are:
> > 1- The reason my machine's NFD is not receiving anything form 224.0.23.170 is that this IP is not globally routable, and I don't have any autoconfig server in my local network having this IP and being up and running. Right?
> >
> 224.0.23.170 is a multicast IP address and how far interests sent over such face will propagate depends on your networking environment (e.g., whether or not your WiFI access point allows multicast, whether you're running multicast routing protocol on your routers, etc.).
> 
> The shorter answer to your question is most likely yes.  Not getting any reply most likely mean that you don't have NFD and associated autoconfig server running in your local network.
> > 2- What is the second one? I've checked my host machine's virtual NICs(NFD is on a VM). It's not any of their MACs.
> >
> This is a multicast Ethernet address.  It is not yet assigned, but it is effectively a mapping of 224.0.23.170 to ethernet address range (https://technet.microsoft.com/en-us/library/cc957928.aspx <https://technet.microsoft.com/en-us/library/cc957928.aspx>).
> 
> Sincerely,
> Alex
> 
> 
> 
> 
> 
> 
> 
> 

-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160216/dc9f511b/attachment.bin>

From s.h.ahmed at ieee.org  Tue Feb 16 20:56:02 2016
From: s.h.ahmed at ieee.org (Syed Hassan Ahmed)
Date: Wed, 17 Feb 2016 13:56:02 +0900
Subject: [Ndn-interest] Chunk level Data Retrieval in mobile NDN
In-Reply-To: <CAJeX4qe5Uyc55YsSfbvEFQWZ=Shr5RE7Jh1KhTt7jER7Q_n1=g@mail.gmail.com>
References: <CAJeX4qe5Uyc55YsSfbvEFQWZ=Shr5RE7Jh1KhTt7jER7Q_n1=g@mail.gmail.com>
Message-ID: <CAJeX4qdw6e9KD0rFnt32CDeyYYKGk2v1m2QUHNpmFV_B2=KsHg@mail.gmail.com>

Hi everyone,

I am writing to check the validity of my previous question, is it out of
scope of this mailing list? or the question itself is invalid?

Requesting for a comment from the community.

Thanks in advance.

?
Best Regards,
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
*Syed Hassan Ahmed *(??)
Kyungpook National University,
Daegu City, Republic of Korea.
Cell: +82-10-9883-0786
https://sites.google.com/site/shahmedknu/

On Wed, Jan 27, 2016 at 4:02 PM, Syed Hassan Ahmed <s.h.ahmed at ieee.org>
wrote:

> Hello Dear Colleagues and Seniors,
>
> I have a simple query regarding Chunk level retrieval in NDN enabled
> mobile networks such as VANETs, MANETs, etc.
>
> Let's consider one scenario:
>
> We have a consumer (C), looking for an Interest (i), and the current
> neighboring node (n) is not the provider of (i). In this case, the (n) will
> forward the (i) depending on any forwarding strategy. Now lets say, the
> very next hop to (n) is the provider (P) of (i) and the chunk level data
> retrieval starts in multi-hop fashion. However, after the successful
> delivery of few chunks (e.g. 5 out of 15 chunks), the (n) moves out between
> the (C) and (P), given that we have always caching on.
>
> What will happen to those 5 chunks cached in the memory of (n)? How they
> can be used? And if not, is there any scheme or mechanism defined in the
> current NDN to discard them? Or they will be discarded straight away?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160217/ca6be6a4/attachment.html>

From lixia at CS.UCLA.EDU  Tue Feb 16 21:13:41 2016
From: lixia at CS.UCLA.EDU (Lixia Zhang)
Date: Tue, 16 Feb 2016 21:13:41 -0800
Subject: [Ndn-interest] Chunk level Data Retrieval in mobile NDN
In-Reply-To: <CAJeX4qdw6e9KD0rFnt32CDeyYYKGk2v1m2QUHNpmFV_B2=KsHg@mail.gmail.com>
References: <CAJeX4qe5Uyc55YsSfbvEFQWZ=Shr5RE7Jh1KhTt7jER7Q_n1=g@mail.gmail.com>
	<CAJeX4qdw6e9KD0rFnt32CDeyYYKGk2v1m2QUHNpmFV_B2=KsHg@mail.gmail.com>
Message-ID: <123DB22C-9C97-4638-9965-24349BFF0B4A@cs.ucla.edu>


> On Feb 16, 2016, at 8:56 PM, Syed Hassan Ahmed <s.h.ahmed at ieee.org> wrote:
> 
> Hi everyone, 
> 
> I am writing to check the validity of my previous question, is it out of scope of this mailing list? or the question itself is invalid? 

apology for the delay in reply.

my personal answer to your question:

> What will happen to those 5 chunks cached in the memory of (n)? How they can be used? And if not, is there any scheme or mechanism defined in the current NDN to discard them? Or they will be discarded straight away?


1/ how the 5 chunks may be used: assume they are not private data, it is up to whether (n) receives interests for them from any other consumers as (n) moves along.

2/ regarding removing them from the cache: this is a cache management question.  NDN does not define a standard cache management scheme; individual nodes/routers can define their own cache management schemes based on their specific application and network environments (for example, a node in VANET can have big cache size, but connectivity may be intermittent, so its cache management may differ from that of a smartphone)

Lixia

> On Wed, Jan 27, 2016 at 4:02 PM, Syed Hassan Ahmed <s.h.ahmed at ieee.org <mailto:s.h.ahmed at ieee.org>> wrote:
> Hello Dear Colleagues and Seniors, 
> 
> I have a simple query regarding Chunk level retrieval in NDN enabled mobile networks such as VANETs, MANETs, etc. 
> 
> Let's consider one scenario: 
> 
> We have a consumer (C), looking for an Interest (i), and the current neighboring node (n) is not the provider of (i). In this case, the (n) will forward the (i) depending on any forwarding strategy. Now lets say, the very next hop to (n) is the provider (P) of (i) and the chunk level data retrieval starts in multi-hop fashion. However, after the successful delivery of few chunks (e.g. 5 out of 15 chunks), the (n) moves out between the (C) and (P), given that we have always caching on.
> 
> What will happen to those 5 chunks cached in the memory of (n)? How they can be used? And if not, is there any scheme or mechanism defined in the current NDN to discard them? Or they will be discarded straight away?
> _______________________________________________
> 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/20160216/e2f13f77/attachment.html>

From Navdeep.Uniyal at neclab.eu  Thu Feb 18 01:43:57 2016
From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal)
Date: Thu, 18 Feb 2016 09:43:57 +0000
Subject: [Ndn-interest] NDN Adaptive traffic generator
Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384CD70@Hydra.office.hd>

Hi All,

I have been looking for a traffic generator for testing my forwarding strategy in NDN. Currently I am using NDN traffic generator but I am looking for an adaptive traffic generator which varies the sending rate automatically based on congestion. Is there one available. Please advise.


Regards,
Navdeep Uniyal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160218/d2fe35be/attachment.html>

From lixia at CS.UCLA.EDU  Thu Feb 18 17:53:56 2016
From: lixia at CS.UCLA.EDU (Lixia Zhang)
Date: Thu, 18 Feb 2016 17:53:56 -0800
Subject: [Ndn-interest] NDN Adaptive traffic generator
In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384CD70@Hydra.office.hd>
References: <15421E67B274CD4AB5F6AEA46A684C370384CD70@Hydra.office.hd>
Message-ID: <731F4AAD-CE4F-4664-BAF6-92C301E3E5C6@cs.ucla.edu>


> On Feb 18, 2016, at 1:43 AM, Navdeep Uniyal <navdeep.uniyal at neclab.eu> wrote:
> 
> Hi All,
>  
> I have been looking for a traffic generator for testing my forwarding strategy in NDN. Currently I am using NDN traffic generator but I am looking for an adaptive traffic generator which varies the sending rate automatically based on congestion.

wonder if you mean the consumer would slow down interest sending rate upon congestion?

that would first require some notification of congestion (I assume NACK is in ndnSIM now?)

> Is there one available. Please advise.
>  
>  
> Regards,
> Navdeep Uniyal
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <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/20160218/4e0b2295/attachment.html>

From tailinchu at gmail.com  Sat Feb 20 16:09:42 2016
From: tailinchu at gmail.com (Tai-Lin Chu)
Date: Sat, 20 Feb 2016 16:09:42 -0800
Subject: [Ndn-interest] go-ndn 1.3 is released today
Message-ID: <CABf5LwDErXwT0ySDoGSpqTi5Ld3T+yF3eeFCo2pU7jrjDBoUzA@mail.gmail.com>

This release comes with ndn-raft [1]. Raft is a protocol by which a cluster
of nodes can maintain a replicated state machine. The state machine is kept
in sync through the use of a replicated log. NDN enables Raft leader to
share its log content efficiently with its followers. ndn-raft is a
reference implementation for go-ndn REST-like service, and an real-world
example to show how to easily prepare data packet before interest [2]. For
a more detailed explanation on the failover process and election terms,
please see the full paper describing the protocol: In Search of an
Understandable Consensus Algorithm [3].


Major:

   - add mux.Publisher to publish data packets easily to content store with
   middleware. Now mux.Middleware is used by Fetcher, Router and Publisher.
   - reduce go GC pressure for longest-prefix match lookup
   - reduce number of runnable goroutines for event like PIT timeout


Backward-incompatible change:

   - There is a significant design change for mux.Notify and mux.Listener
   after these APIs are used in production (see ndn-raft for the most recent
   example)



[1]: https://github.com/go-ndn/raft

[2]: https://github.com/go-ndn/example/blob/master/before-interest.md

[3]: https://ramcloud.stanford.edu/raft.pdf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160220/f97847d0/attachment.html>

From tnsr.chatterjee at gmail.com  Sun Feb 21 01:18:34 2016
From: tnsr.chatterjee at gmail.com (Tanusree Chatterjee)
Date: Sun, 21 Feb 2016 14:48:34 +0530
Subject: [Ndn-interest] ndn architecture
Message-ID: <CAOeyPyTXKHLf23rTNJEB3wY8n=NVN+H1A4HfGUn1vq4gYa=iQQ@mail.gmail.com>

Hello,

I am new to NDN. I felt some difficulty to understand the NDN hourglass
architecture thoroughly in contrast with IP architecture layers that is
given in the ndn project site. Is it the today's NDN architecture which
work on IP/UDP channel (in contrast with the link layer in IP)? In future
it is assumed to not to work upon IP/UDP channel? And what about the 'file
stream' module? Please send me a good documentation which clearly describes
the modules of the NDN architecture in contrast with the same of IP.


-- Regards,
Tanusree Chatterjee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160221/f89300f2/attachment.html>

From christos at colostate.edu  Sun Feb 21 07:22:55 2016
From: christos at colostate.edu (Christos Papadopoulos)
Date: Sun, 21 Feb 2016 08:22:55 -0700
Subject: [Ndn-interest] ndn architecture
In-Reply-To: <CAOeyPyTXKHLf23rTNJEB3wY8n=NVN+H1A4HfGUn1vq4gYa=iQQ@mail.gmail.com>
References: <CAOeyPyTXKHLf23rTNJEB3wY8n=NVN+H1A4HfGUn1vq4gYa=iQQ@mail.gmail.com>
Message-ID: <56C9D64F.1080202@colostate.edu>

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

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

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

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

Hope this helps.

Christos.


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

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

From Navdeep.Uniyal at neclab.eu  Tue Feb 23 03:14:33 2016
From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal)
Date: Tue, 23 Feb 2016 11:14:33 +0000
Subject: [Ndn-interest] NDN Traffic Generator fields.
Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384D79D@Hydra.office.hd>

Hi All,

Can someone please describe briefly the usage of the following optional fields in NDN traffic generator client tool and their impact.
Will "NameAppendBytes" append random n number of bytes on the interest name. If yes, will it have any impact on how data is named at the server. Will it be able to fetch data with the same name. Please clarify.

#NameAppendBytes=NNI [>0]
#NameAppendSequenceNumber=NNI [>=0]
#MinSuffixComponents=NNI
#MaxSuffixComponents=NNI
#ExcludeBefore=NDN Name Component
#ExcludeAfter=NDN Name Component
#ExcludeBeforeBytes=NNI [>0]
#ExcludeAfterBytes=NNI [>0]

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

From woodc1 at uci.edu  Wed Feb 24 13:50:58 2016
From: woodc1 at uci.edu (Christopher Wood)
Date: Wed, 24 Feb 2016 13:50:58 -0800
Subject: [Ndn-interest] Accounting in CCN
Message-ID: <CAFPbCdHpPKehVMSfzBJboZ+9hoEpMAMhSDZa_Sa39DhTjg-PEw@mail.gmail.com>

Hi all,

To follow up on Cesar's previous announcement, the information and a link
to the camera-ready version of this paper are below.


   - C. Ghali, G. Tsudik, C. A. Wood, E. Yeh, Practical Accounting in
   Content-Centric Networking
   <http://sprout.ics.uci.edu/projects/ndn/papers/ndn-accounting.pdf>, to
   appear in *the IEEE/IFIP Network Operations and Management Symposium
   (NOMS)*, Istanbul, Turkey, 2016.

http://sprout.ics.uci.edu/projects/ndn/papers/ndn-accounting.pdf

Any comments or feedback would be appreciated.

Cheers,
Chris

On Wed, Oct 7, 2015 at 5:45 PM, Cesar Ghali <cghali at uci.edu> wrote:

> Hi all,
>
> Some of you might be interested in the following paper:
>
> Cesar Ghali, Gene Tsudik, Christopher A. Wood, Edmund Yeh,
> Practical Accounting in Content-Centric Networking,
> arXiv: 1510.01852, October 7, 2015.
> URL: http://arxiv.org/pdf/1510.01852v1.pdf
>
> Comments and feedbacks are appreciated.
>
> Cheers,
> Cesar
>
> --
> PGP Key: http://www.cesarghali.info/contact.html
> PGP Key ID: 0x455D8052
>
>
> _______________________________________________
> 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/20160224/470e6d5e/attachment.html>

From mblehmann at inf.ufrgs.br  Mon Feb 29 04:57:37 2016
From: mblehmann at inf.ufrgs.br (Matheus Lehmann)
Date: Mon, 29 Feb 2016 09:57:37 -0300
Subject: [Ndn-interest] Producer Mobility Support in NDN/CCN
Message-ID: <CAK6DrFcnobXEzpzEHA0VFjuky4FLTSs6GRaEt6R2guKxvH4=xQ@mail.gmail.com>

Hello all,

Some of you might be interested in the following paper:

M. B. Lehmann, M. P. Barcellos, A. Mauthe, Providing Producer Mobility
Support in NDN
Through Proactive Data Replication, to appear in *the IEEE/IFIP Network
Operations and Management Symposium (NOMS)*, Istanbul, Turkey, 2016.

The camera-ready version of this paper can be found at
http://inf.ufrgs.br/~mblehmann/ndn-mobility-NOMS.pdf

Any comment or feedback would be appreciated.

Best regards,

-- 
Matheus Lehmann
http://inf.ufrgs.br/~mblehmann/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160229/5efaaa63/attachment.html>

From Navdeep.Uniyal at neclab.eu  Mon Feb 29 05:52:42 2016
From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal)
Date: Mon, 29 Feb 2016 13:52:42 +0000
Subject: [Ndn-interest] NLSR Error
Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>

Hi everyone,

I am using minindn to run my experiments, I am finding few errors in the NLSR log. Due to which packet loss is occurring. Below is the snippet of the error and attached is the log file. Please if someone can help resolving the issue.

20160229054020045 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020045 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hb
20160229054020049 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020533 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054020533 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hc
20160229054020535 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054111562 FATAL: [Main] ERROR: error while receiving data from socket (End of file)
20160229054111562 DEBUG: [Fib] Fib::clean called




Regards,
Navdeep Uniyal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160229/2de5427f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nlsr.log
Type: application/octet-stream
Size: 924612 bytes
Desc: nlsr.log
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160229/2de5427f/attachment.obj>

From vslehman at memphis.edu  Mon Feb 29 07:47:50 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Mon, 29 Feb 2016 15:47:50 +0000
Subject: [Ndn-interest] [Mini-NDN] NLSR Error
In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
Message-ID: <C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>

Hi Navdeep,

This error is usually caused by the NFD process on the node terminating; NLSR is unable to receive data from NFD?s Unix socket.

Can you check or share NFD?s log to see the reason for the process? termination? It could be something wrong with the configuration or if you are using ctl^c to kill a process on the Mini-NDN command-line, this can sometimes kill NFD processes also.

--
Vince Lehman

On Feb 29, 2016, at 7:52 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

Hi everyone,

I am using minindn to run my experiments, I am finding few errors in the NLSR log. Due to which packet loss is occurring. Below is the snippet of the error and attached is the log file. Please if someone can help resolving the issue.

20160229054020045 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020045 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hb
20160229054020049 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020533 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054020533 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hc
20160229054020535 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054111562 FATAL: [Main] ERROR: error while receiving data from socket (End of file)
20160229054111562 DEBUG: [Fib] Fib::clean called




Regards,
Navdeep Uniyal
<nlsr.log>_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn

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

From josh at caida.org  Mon Feb 29 17:04:32 2016
From: josh at caida.org (Josh Polterock)
Date: Mon, 29 Feb 2016 17:04:32 -0800
Subject: [Ndn-interest] Named Data Networking (NDN) Project Monthly
 Newsletter for February 2016
Message-ID: <20160301010432.GB94668@caida.org>

Named Data Networking (NDN) Project Newsletter for February 2016

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

* Mark your calendars for 20-23 March 2016 when we plan to hold
  the next NDN Hackathon (open to the public) and Project Retreat
  (open to NDN Consortium members). We will host the retreat on the
  University of California at San Diego campus in La Jolla, CA.
  This retreat will focus on science applications, technical
  discussions with a focus on NFD development, autoconfiguration
  IoT over NDN, and architectural principles and I/UCRC proposal
  planning.  For registration information, agenda, and more see the
  web page at http://www.caida.org/workshops/ndn/1603/ .

TECHNICAL NEWS

* We published an updated alpha version of NFD on Android to Google
  Play store, based on the recently released NFD version 0.4.0.
  This first release has limited documentation. We welcome help in
  any form: bug reports and feature requests submitted to redmine
  (http://redmine.named-data.net/projects/nfd-android/issues),
  patches, bug fixes, feature implementations, documentation and
  updates.  To opt-in to the alpha testing and to download the NFD
  app, open https://play.google.com/apps/testing/net.named_data.nfd
  on your Android device.  Source code for the port is available
  on GitHub: https://github.com/named-data-mobile/NFD-android

* The NDN Testbed has grown to 31 Nodes with 84 links. Since our
  last newsletter, four new sites have connected to the NDN Testbed;
  University of Goettingen, University of Indonesia, Osaka University,
  and the University of Minho in Portugal. See the complete list
  at http://named-data.net/ndn-testbed/.

* We released a new version of PyNDN, the NDN Common Client Library
  for Python. The main change is to use the ?cryptography?  package
  which has the following advantages:
   
  *   Faster - up to 7 times faster for RSA signing
  *   The code is under active maintenance
  *   Supports elliptic curve ECDSA 
  *   More uniform support for Python 2 vs. 3. 

  To install the cryptography package on your platform, please see
  the INSTALL file:
  https://github.com/named-data/PyNDN2/blob/master/INSTALL.md

NDN PUBLICATIONS, PRESENTATIONS, and TECHNICAL REPORTS

* Gusev, P., Z. Wang, J. Burke, L. Zhang, T. Yoneda, R. Ohinishi,
  E.  Muramoto. "Real-time Streaming Data Delivery over Named Data
  Networking," to appear in IEICE Transactions*, 2016.  This paper,
  accepted for publication by the Japanese IEICE, generalizes and
  expands on the description of the current NDN-RTC approach.

* W. Shang, A. Bannis, T. Liang, Z. Wang, Y. Yu, A. Afanasyev, J.
  Thompson, J. Burke, B. Zhang, and L. Zhang. "Named Data Networking
  of Things  (Invited Paper)."  IEEE IoTDI 2016, April 4-8, Berlin,
  Germany. This paper surveys the challenges to Internet of Things
  (IoT) using TCP/IP and explores how Named Data Networking (NDN)
  can help achieve the IoT vision in a more secure, straightforward,
  and innovation-friendly manner. The paper discusses  short- and
  long-term scenarios for employing NDN to enable the IoT.

* NDN TR-0038 Revision 1: Wentao Shang, Yingdi Yu, Ralph Droms,
  Lixia Zhang.  "Challenges in IoT Networking via TCP/IP Architecture"
  analyzes the technical challenges in applying TCP/IP to the IoT
  environment and reviews various solutions. The paper argues that
  existing IP-based solutions are either inefficient or insufficient
  in supporting IoT applications, and that a more effective solution
  would embrace the Information Centric Network architecture.
  http://named-data.net/publications/techreports/ndn-0038-1-challenges-iot/

SEMINARS

* Our NDN Seminar series continued in February.  The NDN seminars
  are internally focused. If you would like to participate in the
  NDN Seminars, please contact the new PoC, UCLA PhD. candidate
  Spyridon Mastorakis <Spiros.mastorakis at gmail.com> for the most
  up-to-date information regarding upcoming seminars.

   - 10 February 2016 Yingdi Yu (UCLA), "Schematizing Trust in Named Data Networking"
   - 24 February 2016 Peter Gusev (UCLA REMAP) "Real-Time Videoconferencing over NDN"
   -  2 March 2016 Susmit Shannigrahi (Colorado State University) "Scientific Data Applications in NDN"

For more information about the Named Data Networking (NDN) Project
please visit http://www.named-data.net/.