From chenatu2006 at gmail.com Sun Mar 1 22:54:32 2015 From: chenatu2006 at gmail.com (Shuo Chen) Date: Mon, 2 Mar 2015 14:54:32 +0800 Subject: [Ndn-interest] running problems about nlsr Message-ID: Dear all, I have installed nlsr and try to configure it. However, the prefixes are found not to be advertised properly. Is there any setting like allowing certain port? Before using nlsr, nfdc is used and everything works well. Could someone help me check the problem? My configurations are below: 3 routers are connected to each other: /thu/elop1/%C1.Router/router1 /thu/elop2/%C1.Router/router2 and /thu/elop3/%C1.Router/router3 The results of nfd-status -r is as below: *RIB:* * /localhost/nfd/rib route={faceid=258 (origin=0 cost=0 ChildInherit)}* * /thu/elop3/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 RibCapture)}* * /thu/elop2/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 RibCapture)}* * /thu/elop1/%C1.Router/router1 route={faceid=270 (origin=0 cost=0 RibCapture)}* * /thu/elop/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 RibCapture)} (This name is from old settings)* * /thu/elop/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 RibCapture)} (**This name is from old settings**)* * /thu/NLSR/sync route={faceid=260 (origin=128 cost=25 RibCapture), faceid=261 (origin=128 cost=30 RibCapture)}* * /thu/NLSR/LSA/elop1/%C1.Router/router1 route={faceid=270 (origin=0 cost=0 RibCapture)}* * /thu/NLSR/LSA route={faceid=260 (origin=128 cost=25 RibCapture), faceid=261 (origin=128 cost=30 RibCapture)}* * /ndn/broadcast/KEYS route={faceid=260 (origin=128 cost=25 RibCapture), faceid=261 (origin=128 cost=30 RibCapture), faceid=270 (origin=0 cost=0 RibCapture)}* The prefixes manager by router1 is not shown in this rib which is * /thu/elop1/server-1/repo/1* * /thu/elop1/server-1/data/1* config file of router1 is as below *; nlsr.conf starts here* *; the general section contains all the general settings for router* *general* *{* * ; mandatory configuration command section network, site and router* * network /thu/ ; name of the network the router belongs to in ndn URI format* * site /elop1/ ; name of the site the router belongs to in ndn URI format* * router /%C1.Router/router1 ; name of the network the router belongs to in ndn URI format* * ; lsa-refresh-time is the time in seconds, after which router will refresh its LSAs* * lsa-refresh-time 1800 ; default value 1800. Valid values 240-7200* * ; InterestLifetime (in seconds) for LSA fetching* * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* * ; log-level is to set the levels of log for NLSR* * log-level INFO ; default value INFO, valid value DEBUG, INFO* * log-dir /var/log/nlsr/* * seq-dir /var/lib/nlsr/* *}* *; the neighbors section contains the configuration for router's neighbors and hello's behavior* *neighbors* *{* * ; in case hello interest timed out, router will try 'hello-retries' times at 'hello-time-out'* * ; seconds interval before giving up for any neighbors (deciding link is down)* * hello-retries 3 ; interest retries number in integer. Default value 3* * ; valid values 1-10* * hello-timeout 1 ; interest time out value in integer. Default value 1* * ; Valid values 1-15* * hello-interval 60 ; interest sending interval in seconds. Default value 60* * ; valid values 30-90* * ; neighbor command is used to configure router's neighbor. Each neighbor will need* * ; one block of neighbor command* * neighbor* * {* * name /thu/elop3/%C1.Router/router3 ; name prefix of the neighbor router consists* * ; of network, site-name and router-name* * face-uri udp4://52.1.251.14 ; face uri of the face connected to the neighbor* * link-cost 25 ; cost of the connecting link to neighbor* * }* * neighbor* * {* * name /thu/elop2/%C1.Router/router2 ; name prefix of the neighbor router consists* * ; of network, site-name and router-name* * face-uri udp4://54.152.174.232 ; face uri of the face connected to the neighbor* * link-cost 30 ; cost of the connecting link to neighbor* * }* *}* *; the hyperbolic section contains the configuration settings of enabling a router to calculate* *; routing table using `hyperbolic routing table calculation`_ method* *hyperbolic* *{* * ; commands in this section follows a strict order* * ; the switch is used to set hyperbolic routing calculation in NLSR* * state off ; default value 'off', set value 'on' to enable hyperbolic routing table* * ; calculation which turns link state routing 'off'. set value to 'dry-run'* * ; to test hyperbolic routing and compare with link state routing.* * radius 123.456 ; radius of the router in hyperbolic coordinate system* * angle 1.45 ; angle of the router in hyperbolic coordinate system* *}* *; the fib section is used to configure fib entry's type to ndn FIB updated by NLSR* *fib* *{* * ; the max-faces-per-prefix is used to limit the number of faces for each name prefixes* * ; by NLSR in ndn FIB* * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By default (value 0) NLSR adds* * ; all available faces for each reachable name prefixes in NDN FIB* *}* *; the advertising section contains the configuration settings of the name prefixes* *; hosted by this router* *advertising* *{* * ; the ndnname is used to advertised name from the router. To advertise each name prefix* * ; configure one block of ndnname configuration command for every name prefix.* * prefix /thu/elop1/server-1/repo/1* * prefix /thu/elop1/server-1/data/1* *}* config file of router2 is as below: *; nlsr.conf starts here* *; the general section contains all the general settings for router* *general* *{* * ; mandatory configuration command section network, site and router* * network /thu/ ; name of the network the router belongs to in ndn URI format* * site /elop2/ ; name of the site the router belongs to in ndn URI format* * router /%C1.Router/router2 ; name of the network the router belongs to in ndn URI format* * ; lsa-refresh-time is the time in seconds, after which router will refresh its LSAs* * lsa-refresh-time 1800 ; default value 1800. Valid values 240-7200* * ; InterestLifetime (in seconds) for LSA fetching* * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* * ; log-level is to set the levels of log for NLSR* * log-level INFO ; default value INFO, valid value DEBUG, INFO* * log-dir /var/log/nlsr/* * seq-dir /var/lib/nlsr/* *}* *; the neighbors section contains the configuration for router's neighbors and hello's behavior* *neighbors* *{* * ; in case hello interest timed out, router will try 'hello-retries' times at 'hello-time-out'* * ; seconds interval before giving up for any neighbors (deciding link is down)* * hello-retries 3 ; interest retries number in integer. Default value 3* * ; valid values 1-10* * hello-timeout 1 ; interest time out value in integer. Default value 1* * ; Valid values 1-15* * hello-interval 60 ; interest sending interval in seconds. Default value 60* * ; valid values 30-90* * ; neighbor command is used to configure router's neighbor. Each neighbor will need* * ; one block of neighbor command* * neighbor* * {* * name /thu/elop3/%C1.Router/router3 ; name prefix of the neighbor router consists* * ; of network, site-name and router-name* * face-uri udp://52.1.251.14 ; face uri of the face connected to the neighbor* * link-cost 25 ; cost of the connecting link to neighbor* * }* * neighbor* * {* * name /thu/elop1/%C1.Router/router1 ; name prefix of the neighbor router consists* * ; of network, site-name and router-name* * face-uri udp://54.152.123.79 ; face uri of the face connected to the neighbor* * link-cost 30 ; cost of the connecting link to neighbor* * }* *}* *; the hyperbolic section contains the configuration settings of enabling a router to calculate* *; routing table using `hyperbolic routing table calculation`_ method* *hyperbolic* *{* * ; commands in this section follows a strict order* * ; the switch is used to set hyperbolic routing calculation in NLSR* * state off ; default value 'off', set value 'on' to enable hyperbolic routing table* * ; calculation which turns link state routing 'off'. set value to 'dry-run'* * ; to test hyperbolic routing and compare with link state routing.* * radius 123.456 ; radius of the router in hyperbolic coordinate system* * angle 1.45 ; angle of the router in hyperbolic coordinate system* *}* *; the fib section is used to configure fib entry's type to ndn FIB updated by NLSR* *fib* *{* * ; the max-faces-per-prefix is used to limit the number of faces for each name prefixes* * ; by NLSR in ndn FIB* * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By default (value 0) NLSR adds* * ; all available faces for each reachable name prefixes in NDN FIB* *}* *; the advertising section contains the configuration settings of the name prefixes* *; hosted by this router* *advertising* *{* * ; the ndnname is used to advertised name from the router. To advertise each name prefix* * ; configure one block of ndnname configuration command for every name prefix.* * prefix /thu/elop2/server-2/repo/1* * prefix /thu/elop2/server-2/data/1* *}* ---- Shuo Chen Tsinghua University -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Mar 1 23:06:15 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 2 Mar 2015 00:06:15 -0700 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: Hi Shuo Did you create certificates for root, site, operator, and each router? If you still have problems, please post configuration files *without comments*, so that it's easier to read. This can be obtained by: sed -e 's/;.*//' -e'/^\s*$/d' /etc/ndn/nlsr/nlsr.conf Please also attach NLSR logs. It's located in /var/log/ndn/nlsr/. Yours, Junxiao On Sun, Mar 1, 2015 at 11:54 PM, Shuo Chen wrote: > Dear all, > I have installed nlsr and try to configure it. However, the > prefixes are found not to be advertised properly. Is there any setting like > allowing certain port? Before using nlsr, nfdc is used and everything works > well. Could someone help me check the problem? > > My configurations are below: > 3 routers are connected to each other: /thu/elop1/%C1.Router/router1 > /thu/elop2/%C1.Router/router2 and /thu/elop3/%C1.Router/router3 > > The results of nfd-status -r is as below: > *RIB:* > * /localhost/nfd/rib route={faceid=258 (origin=0 cost=0 ChildInherit)}* > * /thu/elop3/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 > RibCapture)}* > * /thu/elop2/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 > RibCapture)}* > * /thu/elop1/%C1.Router/router1 route={faceid=270 (origin=0 cost=0 > RibCapture)}* > * /thu/elop/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 > RibCapture)} (This name is from old settings)* > * /thu/elop/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 > RibCapture)} (**This name is from old settings**)* > * /thu/NLSR/sync route={faceid=260 (origin=128 cost=25 RibCapture), > faceid=261 (origin=128 cost=30 RibCapture)}* > * /thu/NLSR/LSA/elop1/%C1.Router/router1 route={faceid=270 (origin=0 > cost=0 RibCapture)}* > * /thu/NLSR/LSA route={faceid=260 (origin=128 cost=25 RibCapture), > faceid=261 (origin=128 cost=30 RibCapture)}* > * /ndn/broadcast/KEYS route={faceid=260 (origin=128 cost=25 RibCapture), > faceid=261 (origin=128 cost=30 RibCapture), faceid=270 (origin=0 cost=0 > RibCapture)}* > > The prefixes manager by router1 is not shown in this rib which is > * /thu/elop1/server-1/repo/1* > * /thu/elop1/server-1/data/1* > > > config file of router1 is as below > > *; nlsr.conf starts here* > *; the general section contains all the general settings for router* > > *general* > *{* > * ; mandatory configuration command section network, site and router* > * network /thu/ ; name of the network the router belongs to in > ndn URI format* > * site /elop1/ ; name of the site the router belongs to in ndn URI > format* > * router /%C1.Router/router1 ; name of the network the router > belongs to in ndn URI format* > > * ; lsa-refresh-time is the time in seconds, after which router will > refresh its LSAs* > * lsa-refresh-time 1800 ; default value 1800. Valid values > 240-7200* > > * ; InterestLifetime (in seconds) for LSA fetching* > * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* > > * ; log-level is to set the levels of log for NLSR* > * log-level INFO ; default value INFO, valid value DEBUG, INFO* > * log-dir /var/log/nlsr/* > * seq-dir /var/lib/nlsr/* > *}* > > *; the neighbors section contains the configuration for router's neighbors > and hello's behavior* > > *neighbors* > *{* > * ; in case hello interest timed out, router will try 'hello-retries' > times at 'hello-time-out'* > * ; seconds interval before giving up for any neighbors (deciding link > is down)* > > * hello-retries 3 ; interest retries number in > integer. Default value 3* > * ; valid values 1-10* > > * hello-timeout 1 ; interest time out value in > integer. Default value 1* > * ; Valid values 1-15* > > * hello-interval 60 ; interest sending interval in > seconds. Default value 60* > * ; valid values 30-90* > * ; neighbor command is used to configure router's neighbor. Each > neighbor will need* > * ; one block of neighbor command* > > * neighbor* > * {* > * name /thu/elop3/%C1.Router/router3 ; name prefix of the > neighbor router consists* > * ; of network, > site-name and router-name* > > * face-uri udp4://52.1.251.14 ; face uri of > the face connected to the neighbor* > * link-cost 25 ; cost of the connecting link > to neighbor* > * }* > > * neighbor* > * {* > * name /thu/elop2/%C1.Router/router2 ; name prefix of the > neighbor router consists* > * ; of network, site-name > and router-name* > > * face-uri udp4://54.152.174.232 ; face > uri of the face connected to the neighbor* > * link-cost 30 ; cost of the connecting link > to neighbor* > * }* > *}* > > *; the hyperbolic section contains the configuration settings of enabling > a router to calculate* > *; routing table using `hyperbolic routing table calculation`_ method* > > *hyperbolic* > *{* > * ; commands in this section follows a strict order* > * ; the switch is used to set hyperbolic routing calculation in NLSR* > > * state off ; default value 'off', set value 'on' to enable > hyperbolic routing table* > * ; calculation which turns link state routing > 'off'. set value to 'dry-run'* > * ; to test hyperbolic routing and compare with > link state routing.* > > > * radius 123.456 ; radius of the router in hyperbolic > coordinate system* > * angle 1.45 ; angle of the router in hyperbolic coordinate > system* > *}* > > > *; the fib section is used to configure fib entry's type to ndn FIB > updated by NLSR* > > *fib* > *{* > * ; the max-faces-per-prefix is used to limit the number of faces for > each name prefixes* > * ; by NLSR in ndn FIB* > > * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By > default (value 0) NLSR adds* > * ; all available faces for each reachable > name prefixes in NDN FIB* > > *}* > > *; the advertising section contains the configuration settings of the name > prefixes* > *; hosted by this router* > > *advertising* > *{* > * ; the ndnname is used to advertised name from the router. To > advertise each name prefix* > * ; configure one block of ndnname configuration command for every name > prefix.* > > * prefix /thu/elop1/server-1/repo/1* > * prefix /thu/elop1/server-1/data/1* > *}* > > config file of router2 is as below: > > *; nlsr.conf starts here* > *; the general section contains all the general settings for router* > > *general* > *{* > * ; mandatory configuration command section network, site and router* > * network /thu/ ; name of the network the router belongs to in > ndn URI format* > * site /elop2/ ; name of the site the router belongs to in ndn URI > format* > * router /%C1.Router/router2 ; name of the network the router > belongs to in ndn URI format* > > * ; lsa-refresh-time is the time in seconds, after which router will > refresh its LSAs* > * lsa-refresh-time 1800 ; default value 1800. Valid values > 240-7200* > > * ; InterestLifetime (in seconds) for LSA fetching* > * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* > > * ; log-level is to set the levels of log for NLSR* > * log-level INFO ; default value INFO, valid value DEBUG, INFO* > * log-dir /var/log/nlsr/* > * seq-dir /var/lib/nlsr/* > *}* > > *; the neighbors section contains the configuration for router's neighbors > and hello's behavior* > > *neighbors* > *{* > * ; in case hello interest timed out, router will try 'hello-retries' > times at 'hello-time-out'* > * ; seconds interval before giving up for any neighbors (deciding link > is down)* > > * hello-retries 3 ; interest retries number in > integer. Default value 3* > * ; valid values 1-10* > > * hello-timeout 1 ; interest time out value in > integer. Default value 1* > * ; Valid values 1-15* > > * hello-interval 60 ; interest sending interval in > seconds. Default value 60* > * ; valid values 30-90* > * ; neighbor command is used to configure router's neighbor. Each > neighbor will need* > * ; one block of neighbor command* > > * neighbor* > * {* > * name /thu/elop3/%C1.Router/router3 ; name prefix of the > neighbor router consists* > * ; of network, > site-name and router-name* > > * face-uri udp://52.1.251.14 ; face uri of the > face connected to the neighbor* > * link-cost 25 ; cost of the connecting link > to neighbor* > * }* > > * neighbor* > * {* > * name /thu/elop1/%C1.Router/router1 ; name prefix of the > neighbor router consists* > * ; of network, site-name > and router-name* > > * face-uri udp://54.152.123.79 ; face uri > of the face connected to the neighbor* > * link-cost 30 ; cost of the connecting link > to neighbor* > * }* > *}* > > *; the hyperbolic section contains the configuration settings of enabling > a router to calculate* > *; routing table using `hyperbolic routing table calculation`_ method* > > *hyperbolic* > *{* > * ; commands in this section follows a strict order* > * ; the switch is used to set hyperbolic routing calculation in NLSR* > > * state off ; default value 'off', set value 'on' to enable > hyperbolic routing table* > * ; calculation which turns link state routing > 'off'. set value to 'dry-run'* > * ; to test hyperbolic routing and compare with > link state routing.* > > > * radius 123.456 ; radius of the router in hyperbolic > coordinate system* > * angle 1.45 ; angle of the router in hyperbolic coordinate > system* > *}* > > > *; the fib section is used to configure fib entry's type to ndn FIB > updated by NLSR* > > *fib* > *{* > * ; the max-faces-per-prefix is used to limit the number of faces for > each name prefixes* > * ; by NLSR in ndn FIB* > > * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By > default (value 0) NLSR adds* > * ; all available faces for each reachable > name prefixes in NDN FIB* > > *}* > > *; the advertising section contains the configuration settings of the name > prefixes* > *; hosted by this router* > > *advertising* > *{* > * ; the ndnname is used to advertised name from the router. To > advertise each name prefix* > * ; configure one block of ndnname configuration command for every name > prefix.* > > * prefix /thu/elop2/server-2/repo/1* > * prefix /thu/elop2/server-2/data/1* > *}* > > ---- > Shuo Chen > Tsinghua University > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenatu2006 at gmail.com Sun Mar 1 23:24:29 2015 From: chenatu2006 at gmail.com (Shuo Chen) Date: Mon, 2 Mar 2015 15:24:29 +0800 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: I did not create any certificates. The log file is created but it is empty The config file of router1 is as below general { network /thu/ site /elop1/ router /%C1.Router/router1 lsa-refresh-time 1800 lsa-interest-lifetime 4 log-level INFO log-dir /var/log/nlsr/ seq-dir /var/lib/nlsr/ } neighbors { hello-retries 3 hello-timeout 1 hello-interval 60 neighbor { name /thu/elop3/%C1.Router/router3 face-uri udp4://52.1.251.14 link-cost 25 } neighbor { name /thu/elop2/%C1.Router/router2 face-uri udp4://54.152.174.232 link-cost 30 } } hyperbolic { state off radius 123.456 angle 1.45 } fib { max-faces-per-prefix 3 } advertising { prefix /thu/elop1/server-1/repo/1 prefix /thu/elop1/server-1/data/1 } ?????????????????????????????????????????????? The config file of router2 is as below: general { network /thu/ site /elop2/ router /%C1.Router/router2 lsa-refresh-time 1800 lsa-interest-lifetime 4 log-level INFO log-dir /var/log/nlsr/ seq-dir /var/lib/nlsr/ } neighbors { hello-retries 3 hello-timeout 1 hello-interval 60 neighbor { name /thu/elop3/%C1.Router/router3 face-uri udp://52.1.251.14 link-cost 25 } neighbor { name /thu/elop1/%C1.Router/router1 face-uri udp://54.152.123.79 link-cost 30 } } hyperbolic { state off radius 123.456 angle 1.45 } fib { max-faces-per-prefix 3 } advertising { prefix /thu/elop2/server-2/repo/1 prefix /thu/elop2/server-2/data/1 } On Mon, Mar 2, 2015 at 3:06 PM, Junxiao Shi wrote: > Hi Shuo > > Did you create certificates for root, site, operator, and each router? > > If you still have problems, please post configuration files *without > comments*, so that it's easier to read. > This can be obtained by: sed -e 's/;.*//' -e'/^\s*$/d' > /etc/ndn/nlsr/nlsr.conf > > Please also attach NLSR logs. It's located in /var/log/ndn/nlsr/. > > Yours, Junxiao > > On Sun, Mar 1, 2015 at 11:54 PM, Shuo Chen wrote: > >> Dear all, >> I have installed nlsr and try to configure it. However, the >> prefixes are found not to be advertised properly. Is there any setting like >> allowing certain port? Before using nlsr, nfdc is used and everything works >> well. Could someone help me check the problem? >> >> My configurations are below: >> 3 routers are connected to each other: /thu/elop1/%C1.Router/router1 >> /thu/elop2/%C1.Router/router2 and /thu/elop3/%C1.Router/router3 >> >> The results of nfd-status -r is as below: >> *RIB:* >> * /localhost/nfd/rib route={faceid=258 (origin=0 cost=0 ChildInherit)}* >> * /thu/elop3/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 >> RibCapture)}* >> * /thu/elop2/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 >> RibCapture)}* >> * /thu/elop1/%C1.Router/router1 route={faceid=270 (origin=0 cost=0 >> RibCapture)}* >> * /thu/elop/%C1.Router/router3 route={faceid=260 (origin=128 cost=25 >> RibCapture)} (This name is from old settings)* >> * /thu/elop/%C1.Router/router2 route={faceid=261 (origin=128 cost=30 >> RibCapture)} (**This name is from old settings**)* >> * /thu/NLSR/sync route={faceid=260 (origin=128 cost=25 RibCapture), >> faceid=261 (origin=128 cost=30 RibCapture)}* >> * /thu/NLSR/LSA/elop1/%C1.Router/router1 route={faceid=270 (origin=0 >> cost=0 RibCapture)}* >> * /thu/NLSR/LSA route={faceid=260 (origin=128 cost=25 RibCapture), >> faceid=261 (origin=128 cost=30 RibCapture)}* >> * /ndn/broadcast/KEYS route={faceid=260 (origin=128 cost=25 RibCapture), >> faceid=261 (origin=128 cost=30 RibCapture), faceid=270 (origin=0 cost=0 >> RibCapture)}* >> >> The prefixes manager by router1 is not shown in this rib which is >> * /thu/elop1/server-1/repo/1* >> * /thu/elop1/server-1/data/1* >> >> >> config file of router1 is as below >> >> *; nlsr.conf starts here* >> *; the general section contains all the general settings for router* >> >> *general* >> *{* >> * ; mandatory configuration command section network, site and router* >> * network /thu/ ; name of the network the router belongs to in >> ndn URI format* >> * site /elop1/ ; name of the site the router belongs to in ndn URI >> format* >> * router /%C1.Router/router1 ; name of the network the router >> belongs to in ndn URI format* >> >> * ; lsa-refresh-time is the time in seconds, after which router will >> refresh its LSAs* >> * lsa-refresh-time 1800 ; default value 1800. Valid values >> 240-7200* >> >> * ; InterestLifetime (in seconds) for LSA fetching* >> * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* >> >> * ; log-level is to set the levels of log for NLSR* >> * log-level INFO ; default value INFO, valid value DEBUG, INFO* >> * log-dir /var/log/nlsr/* >> * seq-dir /var/lib/nlsr/* >> *}* >> >> *; the neighbors section contains the configuration for router's >> neighbors and hello's behavior* >> >> *neighbors* >> *{* >> * ; in case hello interest timed out, router will try 'hello-retries' >> times at 'hello-time-out'* >> * ; seconds interval before giving up for any neighbors (deciding link >> is down)* >> >> * hello-retries 3 ; interest retries number in >> integer. Default value 3* >> * ; valid values 1-10* >> >> * hello-timeout 1 ; interest time out value in >> integer. Default value 1* >> * ; Valid values 1-15* >> >> * hello-interval 60 ; interest sending interval in >> seconds. Default value 60* >> * ; valid values 30-90* >> * ; neighbor command is used to configure router's neighbor. Each >> neighbor will need* >> * ; one block of neighbor command* >> >> * neighbor* >> * {* >> * name /thu/elop3/%C1.Router/router3 ; name prefix of the >> neighbor router consists* >> * ; of network, >> site-name and router-name* >> >> * face-uri udp4://52.1.251.14 ; face uri of >> the face connected to the neighbor* >> * link-cost 25 ; cost of the connecting link >> to neighbor* >> * }* >> >> * neighbor* >> * {* >> * name /thu/elop2/%C1.Router/router2 ; name prefix of the >> neighbor router consists* >> * ; of network, site-name >> and router-name* >> >> * face-uri udp4://54.152.174.232 ; face >> uri of the face connected to the neighbor* >> * link-cost 30 ; cost of the connecting link >> to neighbor* >> * }* >> *}* >> >> *; the hyperbolic section contains the configuration settings of enabling >> a router to calculate* >> *; routing table using `hyperbolic routing table calculation`_ method* >> >> *hyperbolic* >> *{* >> * ; commands in this section follows a strict order* >> * ; the switch is used to set hyperbolic routing calculation in NLSR* >> >> * state off ; default value 'off', set value 'on' to >> enable hyperbolic routing table* >> * ; calculation which turns link state routing >> 'off'. set value to 'dry-run'* >> * ; to test hyperbolic routing and compare with >> link state routing.* >> >> >> * radius 123.456 ; radius of the router in hyperbolic >> coordinate system* >> * angle 1.45 ; angle of the router in hyperbolic >> coordinate system* >> *}* >> >> >> *; the fib section is used to configure fib entry's type to ndn FIB >> updated by NLSR* >> >> *fib* >> *{* >> * ; the max-faces-per-prefix is used to limit the number of faces for >> each name prefixes* >> * ; by NLSR in ndn FIB* >> >> * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By >> default (value 0) NLSR adds* >> * ; all available faces for each reachable >> name prefixes in NDN FIB* >> >> *}* >> >> *; the advertising section contains the configuration settings of the >> name prefixes* >> *; hosted by this router* >> >> *advertising* >> *{* >> * ; the ndnname is used to advertised name from the router. To >> advertise each name prefix* >> * ; configure one block of ndnname configuration command for every >> name prefix.* >> >> * prefix /thu/elop1/server-1/repo/1* >> * prefix /thu/elop1/server-1/data/1* >> *}* >> >> config file of router2 is as below: >> >> *; nlsr.conf starts here* >> *; the general section contains all the general settings for router* >> >> *general* >> *{* >> * ; mandatory configuration command section network, site and router* >> * network /thu/ ; name of the network the router belongs to in >> ndn URI format* >> * site /elop2/ ; name of the site the router belongs to in ndn URI >> format* >> * router /%C1.Router/router2 ; name of the network the router >> belongs to in ndn URI format* >> >> * ; lsa-refresh-time is the time in seconds, after which router will >> refresh its LSAs* >> * lsa-refresh-time 1800 ; default value 1800. Valid values >> 240-7200* >> >> * ; InterestLifetime (in seconds) for LSA fetching* >> * lsa-interest-lifetime 4 ; default value 4. Valid values 1-60* >> >> * ; log-level is to set the levels of log for NLSR* >> * log-level INFO ; default value INFO, valid value DEBUG, INFO* >> * log-dir /var/log/nlsr/* >> * seq-dir /var/lib/nlsr/* >> *}* >> >> *; the neighbors section contains the configuration for router's >> neighbors and hello's behavior* >> >> *neighbors* >> *{* >> * ; in case hello interest timed out, router will try 'hello-retries' >> times at 'hello-time-out'* >> * ; seconds interval before giving up for any neighbors (deciding link >> is down)* >> >> * hello-retries 3 ; interest retries number in >> integer. Default value 3* >> * ; valid values 1-10* >> >> * hello-timeout 1 ; interest time out value in >> integer. Default value 1* >> * ; Valid values 1-15* >> >> * hello-interval 60 ; interest sending interval in >> seconds. Default value 60* >> * ; valid values 30-90* >> * ; neighbor command is used to configure router's neighbor. Each >> neighbor will need* >> * ; one block of neighbor command* >> >> * neighbor* >> * {* >> * name /thu/elop3/%C1.Router/router3 ; name prefix of the >> neighbor router consists* >> * ; of network, >> site-name and router-name* >> >> * face-uri udp://52.1.251.14 ; face uri of >> the face connected to the neighbor* >> * link-cost 25 ; cost of the connecting link >> to neighbor* >> * }* >> >> * neighbor* >> * {* >> * name /thu/elop1/%C1.Router/router1 ; name prefix of the >> neighbor router consists* >> * ; of network, site-name >> and router-name* >> >> * face-uri udp://54.152.123.79 ; face >> uri of the face connected to the neighbor* >> * link-cost 30 ; cost of the connecting link >> to neighbor* >> * }* >> *}* >> >> *; the hyperbolic section contains the configuration settings of enabling >> a router to calculate* >> *; routing table using `hyperbolic routing table calculation`_ method* >> >> *hyperbolic* >> *{* >> * ; commands in this section follows a strict order* >> * ; the switch is used to set hyperbolic routing calculation in NLSR* >> >> * state off ; default value 'off', set value 'on' to >> enable hyperbolic routing table* >> * ; calculation which turns link state routing >> 'off'. set value to 'dry-run'* >> * ; to test hyperbolic routing and compare with >> link state routing.* >> >> >> * radius 123.456 ; radius of the router in hyperbolic >> coordinate system* >> * angle 1.45 ; angle of the router in hyperbolic >> coordinate system* >> *}* >> >> >> *; the fib section is used to configure fib entry's type to ndn FIB >> updated by NLSR* >> >> *fib* >> *{* >> * ; the max-faces-per-prefix is used to limit the number of faces for >> each name prefixes* >> * ; by NLSR in ndn FIB* >> >> * max-faces-per-prefix 3 ; default value 0. Valid value 0-60. By >> default (value 0) NLSR adds* >> * ; all available faces for each reachable >> name prefixes in NDN FIB* >> >> *}* >> >> *; the advertising section contains the configuration settings of the >> name prefixes* >> *; hosted by this router* >> >> *advertising* >> *{* >> * ; the ndnname is used to advertised name from the router. To >> advertise each name prefix* >> * ; configure one block of ndnname configuration command for every >> name prefix.* >> >> * prefix /thu/elop2/server-2/repo/1* >> * prefix /thu/elop2/server-2/data/1* >> *}* >> >> ---- >> Shuo Chen >> Tsinghua University >> >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Mar 1 23:30:12 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 2 Mar 2015 00:30:12 -0700 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: Hi Shuo Follow this manual to create certificates. http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html It's critical to get the certificate chain right. This thread has some command lines: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html Yours, Junxiao On Mar 2, 2015 12:24 AM, "Shuo Chen" wrote: > > I did not create any certificates. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenatu2006 at gmail.com Sun Mar 1 23:44:08 2015 From: chenatu2006 at gmail.com (Shuo Chen) Date: Mon, 2 Mar 2015 15:44:08 +0800 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: Can I temporarily turn off the security function by adding the config below? security { validator { trust-anchor { type any } } } On Mon, Mar 2, 2015 at 3:30 PM, Junxiao Shi wrote: > Hi Shuo > > Follow this manual to create certificates. > http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html > > It's critical to get the certificate chain right. This thread has some > command lines: > http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html > > Yours, Junxiao > > On Mar 2, 2015 12:24 AM, "Shuo Chen" wrote: > > > > I did not create any certificates. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Mar 2 00:02:02 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 2 Mar 2015 01:02:02 -0700 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: Hi Shuo I don't know whether that's possible, but this is a bad idea in any production deployment. Yours, Junxiao On Mar 2, 2015 12:44 AM, "Shuo Chen" wrote: > Can I temporarily turn off the security function by adding the config > below? > > security > { > validator > { > trust-anchor { > type any > } > } > } > > On Mon, Mar 2, 2015 at 3:30 PM, Junxiao Shi > wrote: > >> Hi Shuo >> >> Follow this manual to create certificates. >> http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html >> >> It's critical to get the certificate chain right. This thread has some >> command lines: >> http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html >> >> Yours, Junxiao >> >> On Mar 2, 2015 12:24 AM, "Shuo Chen" wrote: >> > >> > I did not create any certificates. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Mon Mar 2 00:40:40 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Mon, 2 Mar 2015 12:10:40 +0330 Subject: [Ndn-interest] Data Accessibility in VM Live Migration over NDN References: <3921f845.1342a.14bcfabe795.Coremail.dejiang_zhou@163.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293D@m-pdc.sbu.ac.ir> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> Hi, Let assume we have tow copies and the MAP-AND-ENCAP mechanism implemented. Which route would be selected? I mean, the edge router sends the interest to both addresses(the old one, and the new old received from NDNS), right? Then depending on the measurements done by itself(the edge router), future interest will be sent to the designated route, and the endpoint application won't notify any of this. Am I right? Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Xiaoke Jiang Sent: Sat 2/28/2015 9:38 PM To: Dejiang Zhou Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN Hi Dejiang, Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem 1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ 2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests. Xiaoke (Shock) > On 28 Feb, 2015, at 2:12 am, Dejiang Zhou wrote: > > Hi everyone, > I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed. > VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be "/ndn/cn/edu/tongji/vm/ping". However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix "/ndn/cn/edu/tongji". In contrast, Interest with name "/ndn/cn/edu/tongji/vm/ping" cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich". > Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration. > Best regards, > Dejiang Zhou > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.EDU Mon Mar 2 08:01:06 2015 From: vslehman at memphis.EDU (Vince Lehman (vslehman)) Date: Mon, 2 Mar 2015 16:01:06 +0000 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: Message-ID: <860CBA53-2A10-49D7-B11C-FEA6444C970D@memphis.edu> Hi Shuo, If you would like to make sure that security is the issue, you can disable security by commenting out the below lines and changing the type to ?any": ... trust-anchor { type any ;file-name "root.cert" } ... ;cert-to-publish "router.cert" ; required, a file containing the router certificate. It is important though that you leave the rest of the security section unmodified. -- Vince Lehman On Mar 2, 2015, at 2:02 AM, Junxiao Shi > wrote: Hi Shuo I don't know whether that's possible, but this is a bad idea in any production deployment. Yours, Junxiao On Mar 2, 2015 12:44 AM, "Shuo Chen" > wrote: Can I temporarily turn off the security function by adding the config below? security { validator { trust-anchor { type any } } } On Mon, Mar 2, 2015 at 3:30 PM, Junxiao Shi > wrote: Hi Shuo Follow this manual to create certificates. http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html It's critical to get the certificate chain right. This thread has some command lines: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html Yours, Junxiao On Mar 2, 2015 12:24 AM, "Shuo Chen" > wrote: > > I did not create any certificates. _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Mar 2 08:07:01 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 2 Mar 2015 09:07:01 -0700 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: <860CBA53-2A10-49D7-B11C-FEA6444C970D@memphis.edu> References: <860CBA53-2A10-49D7-B11C-FEA6444C970D@memphis.edu> Message-ID: Hi Vince If I set "any" trust anchor, do I still need to create the certificates? Will the router create certificates automatically? If certificates are created automatically but I later revert the trust anchor setting, I'll need to delete those untrusted certificates, correct? Yours, Junxiao On Mar 2, 2015 9:03 AM, "Vince Lehman (vslehman)" wrote: > Hi Shuo, > > If you would like to make sure that security is the issue, you can > disable security by commenting out the below lines and changing the type to > ?any": > > ... > trust-anchor > { > type any > ;file-name "root.cert" > } > ... > > ;cert-to-publish "router.cert" ; required, a file containing the router > certificate. > > It is important though that you leave the rest of the security section > unmodified. > > -- > Vince Lehman > > On Mar 2, 2015, at 2:02 AM, Junxiao Shi > wrote: > > Hi Shuo > > I don't know whether that's possible, but this is a bad idea in any > production deployment. > > Yours, Junxiao > On Mar 2, 2015 12:44 AM, "Shuo Chen" wrote: > >> Can I temporarily turn off the security function by adding the config >> below? >> >> security >> { >> validator >> { >> trust-anchor { >> type any >> } >> } >> } >> >> On Mon, Mar 2, 2015 at 3:30 PM, Junxiao Shi > > wrote: >> >>> Hi Shuo >>> >>> Follow this manual to create certificates. >>> http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html >>> >>> It's critical to get the certificate chain right. This thread has some >>> command lines: >>> http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html >>> >>> Yours, Junxiao >>> >>> On Mar 2, 2015 12:24 AM, "Shuo Chen" wrote: >>> > >>> > I did not create any certificates. >>> >> >> _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengy.fan at gmail.com Mon Mar 2 08:48:49 2015 From: chengy.fan at gmail.com (Chengyu Fan) Date: Mon, 2 Mar 2015 09:48:49 -0700 Subject: [Ndn-interest] How to add the SecRuleRelative Rules in validator-regex? In-Reply-To: <5C834D2E-8F04-4731-A42E-B5B9EE41F676@ucla.edu> References: <3AE5D813-81E9-449D-8FF9-045D0DD007F3@ucla.edu> <5C834D2E-8F04-4731-A42E-B5B9EE41F676@ucla.edu> Message-ID: Hi Alex, Thanks for the reply. Further questions in line. On Sat, Feb 28, 2015 at 4:45 PM, Alex Afanasyev < alexander.afanasyev at ucla.edu> wrote: > Hi Chengyu, > > I assumed there is a documentation for this method, but the commit that > adds it is not yet merged. Here is the description we will have soon: > > /** > * @brief Construct the rule > * @param packetRegex regular expression to match the packet name that > is qualified for the > * the rule (e.g., `^(<.*>)$`) > * @param signerRegex regular expression to match the the KeyLocator of > the packet (e.g., > * `^(<.*>)(<.*>)<>$`) > * @param comparator Defines the way expanded signer's name is matched > against expanded > * packet's name. Possible values are: > * - "is-prefix-of" > * - "is-strict-prefix-of" > * - "equal" > Which symbol refers to which value? > * @param packetExpand Expansion rule for packet's name (e.g., `\1`) > * @param signerExpand Expansion rule for signer's name (e.g., `\1\2`) > * @param isPositive flag denoting whether the rule is positive or > negative > * > * @note A packet complies with the rule only if both \p packetRegex > matches the packet name > * and \p signerRegex matches the KeyLocator name > According to the comparator description, I think this function also needs to test if the expanded signer's name matched against the expanded packet's name? > */ > > > On Feb 27, 2015, at 7:59 PM, Chengyu Fan wrote: > > Could you tell me how the SecRuleRelative Rule works? > > Specifically, what's the meaning of each parameter? What conditions the > rule will test to make a incoming data satisfy the rule? > ndn::SecRuleRelative::SecRuleRelative > > (const std::string & dataRegex,const std::string & signerRegex,const > std::string & op,const std::string & dataExpand,const std::string & > signerExpand,bool isPositive ) > > > > On Fri, Feb 27, 2015 at 1:59 PM, Alex Afanasyev < > alexander.afanasyev at ucla.edu> wrote: > >> >> On Feb 27, 2015, at 12:10 PM, Chengyu Fan wrote: >> >> Hi, >> >> I'm trying to use the validator-regex to validate the incoming data, but >> I stuck at how to add the SecRuleRelative Rule. >> >> Can somebody tell me some clues? >> >> Specifically, I find the example in SecurityLibrary( >> http://redmine.named-data.net/projects/ndn-cxx/wiki/SecurityLibrary), >> but I don't understand the RuleRelative rule below ... >> >> SecRuleRelative rule("^(<>*)$", "^([^]*)(<>*)$", >> ">", "\\1", "\\1\\2", true); >> >> What's the meaning of ">", "\\1", "\\1\\2" ? Can someone give me an >> example? >> >> >> This is just a regular expression rules. \\1 (\1, it?s just \ needs to >> be escaped in c++) refer to th first group of the regular expression, \\2 refer >> to the second group, etc. >> >> There are many documentation sources about regexps, e.g., >> http://www.boost.org/doc/libs/1_57_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html >> . >> >> The only difference in our regular expressions is the fact that it is >> defined over name components, not just strings. There is a documentation >> for this at >> http://named-data.net/doc/ndn-cxx/current/tutorials/utils-ndn-regex.html >> >> ? >> Alex >> >> >> > > > -- > Thanks, > > Chengyu > > > -- Thanks, Chengyu -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Mon Mar 2 09:40:37 2015 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Mon, 2 Mar 2015 17:40:37 +0000 Subject: [Ndn-interest] running problems about nlsr In-Reply-To: References: <860CBA53-2A10-49D7-B11C-FEA6444C970D@memphis.edu> Message-ID: <7B1AC089-F948-4B62-8631-C4D6A580452C@memphis.edu> Junxiao, If I set "any" trust anchor, do I still need to create the certificates? No, you would not need to create the certificates. Will the router create certificates automatically? If certificates are created automatically but I later revert the trust anchor setting, I'll need to delete those untrusted certificates, correct? The router will not automatically create certificates so you will not need to remove untrusted certificates when changing the trust anchor settings. -- Vince Lehman On Mar 2, 2015, at 10:07 AM, Junxiao Shi > wrote: Hi Vince If I set "any" trust anchor, do I still need to create the certificates? Will the router create certificates automatically? If certificates are created automatically but I later revert the trust anchor setting, I'll need to delete those untrusted certificates, correct? Yours, Junxiao On Mar 2, 2015 9:03 AM, "Vince Lehman (vslehman)" > wrote: Hi Shuo, If you would like to make sure that security is the issue, you can disable security by commenting out the below lines and changing the type to ?any": ... trust-anchor { type any ;file-name "root.cert" } ... ;cert-to-publish "router.cert" ; required, a file containing the router certificate. It is important though that you leave the rest of the security section unmodified. -- Vince Lehman On Mar 2, 2015, at 2:02 AM, Junxiao Shi > wrote: Hi Shuo I don't know whether that's possible, but this is a bad idea in any production deployment. Yours, Junxiao On Mar 2, 2015 12:44 AM, "Shuo Chen" > wrote: Can I temporarily turn off the security function by adding the config below? security { validator { trust-anchor { type any } } } On Mon, Mar 2, 2015 at 3:30 PM, Junxiao Shi > wrote: Hi Shuo Follow this manual to create certificates. http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html It's critical to get the certificate chain right. This thread has some command lines: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-November/000616.html Yours, Junxiao On Mar 2, 2015 12:24 AM, "Shuo Chen" > wrote: > > I did not create any certificates. _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From shock.jiang at gmail.com Mon Mar 2 09:47:07 2015 From: shock.jiang at gmail.com (Xiaoke Jiang) Date: Mon, 2 Mar 2015 09:47:07 -0800 Subject: [Ndn-interest] Data Accessibility in VM Live Migration over NDN In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> References: <3921f845.1342a.14bcfabe795.Coremail.dejiang_zhou@163.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293D@m-pdc.sbu.ac.ir> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> Message-ID: Basically, that is right. But in fact, I think the mobility scenario is more complicated when the content name itself is routeable. 1) link will not be prepended to Interest since the content name can find a match prefix; 2) even if link is prepended actively by end consumer, it will not make difference since content name is in a higher priority during forwarding. My understanding is that link object delegates a name to another name in the purpose of forwarding/routing, and the content should not be forwarded according to the content name or its name aggregation any more. NDN Routers have to be aware of this delegation and avoid unwanted forwarding. Xiaoke (Shock) > On 2 Mar, 2015, at 12:40 am, Muhammad Hosain Abdollahi Sabet wrote: > > Hi, > Let assume we have tow copies and the MAP-AND-ENCAP mechanism implemented. Which route would be selected? I mean, the edge router sends the interest to both addresses(the old one, and the new old received from NDNS), right? Then depending on the measurements done by itself(the edge router), future interest will be sent to the designated route, and the endpoint application won't notify any of this. Am I right? > > Thanks, > Sabet > > -----Original Message----- > From: Ndn-interest on behalf of Xiaoke Jiang > Sent: Sat 2/28/2015 9:38 PM > To: Dejiang Zhou > Cc: ndn-interest at lists.cs.ucla.edu > Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN > > Hi Dejiang, > Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem > 1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ > > 2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf > > > p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests. > > Xiaoke (Shock) > > > > > On 28 Feb, 2015, at 2:12 am, Dejiang Zhou wrote: > > > > Hi everyone, > > I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed. > > VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be "/ndn/cn/edu/tongji/vm/ping". However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix "/ndn/cn/edu/tongji". In contrast, Interest with name "/ndn/cn/edu/tongji/vm/ping" cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich". > > Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration. > > Best regards, > > Dejiang Zhou > > > > > > _______________________________________________ > > Ndn-interest mailing list > > Ndn-interest at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Mon Mar 2 10:13:08 2015 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Mon, 2 Mar 2015 18:13:08 +0000 Subject: [Ndn-interest] Data Accessibility in VM Live Migration over NDN In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> References: <3921f845.1342a.14bcfabe795.Coremail.dejiang_zhou@163.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293D@m-pdc.sbu.ac.ir> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> Message-ID: <030C7CA2-F6FF-4998-B519-37170C2ADF8D@memphis.edu> This depends on the strategy. It could work in the way you described. Or the edge router could forward the interest using one of the delegated names. It should bring back data. If there's no data back, then it could try another one of the delegated names. Note that in NDN, the delegated names are names too, not addresses. For example, /ndnsim/net could be delegated to /com/att/user/alex/ndnsim. Lan On Mar 2, 2015, at 2:40 AM, Muhammad Hosain Abdollahi Sabet > wrote: Hi, Let assume we have tow copies and the MAP-AND-ENCAP mechanism implemented. Which route would be selected? I mean, the edge router sends the interest to both addresses(the old one, and the new old received from NDNS), right? Then depending on the measurements done by itself(the edge router), future interest will be sent to the designated route, and the endpoint application won't notify any of this. Am I right? Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Xiaoke Jiang Sent: Sat 2/28/2015 9:38 PM To: Dejiang Zhou Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN Hi Dejiang, Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem 1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ 2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests. Xiaoke (Shock) > On 28 Feb, 2015, at 2:12 am, Dejiang Zhou > wrote: > > Hi everyone, > I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed. > VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be "/ndn/cn/edu/tongji/vm/ping". However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix "/ndn/cn/edu/tongji". In contrast, Interest with name "/ndn/cn/edu/tongji/vm/ping" cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich". > Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration. > Best regards, > Dejiang Zhou > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengy.fan at gmail.com Mon Mar 2 10:19:30 2015 From: chengy.fan at gmail.com (Chengyu Fan) Date: Mon, 2 Mar 2015 11:19:30 -0700 Subject: [Ndn-interest] How to add the SecRuleRelative Rules in validator-regex? In-Reply-To: References: <3AE5D813-81E9-449D-8FF9-045D0DD007F3@ucla.edu> <5C834D2E-8F04-4731-A42E-B5B9EE41F676@ucla.edu> Message-ID: Hi Alex, I wrote a toy example to use the SecRuleRelative (the code is listed below ) . I thought the data should satisfy the rule, but I always get "unsatisfied" on my ubuntu 14.04.1 ... Could you tell me what's wrong with the code? ================= Name dataName("/test/site2/user2"); dataName.append("testApp"); // the *data name* is */test/site2/user2/testApp* // Create Data packet static const std::string content = "HELLO WORLD"; shared_ptr data = make_shared(); data->setName(dataName); data->setFreshnessPeriod(time::seconds(10)); data->setContent(reinterpret_cast(content.c_str()), content.size()); Name producerId("/test/site2/user2"); m_keyChain.signByIdentity(*data, producerId); // now the *keyLocator* is */test/site2/user2/KEY/ksk-1425277773626/ID-CERT* SecRuleRelative rule("*^(<>*)$*", "*^([^]*)(<>*)$*", *">", "\\1", "\\1\\2", true*); /* */test/site2/user2/testApp *should match the packetRegex "*^(<>*)$, *expand is */test/site2/user2/testApp* */test/site2/user2/KEY/ksk-1425277773626/ID-CERT* should match the signerRegex, expand is */test/site2/user2/* The data name* /test/site2/user2/testApp *is* under *the signer's namespace */test/site2/user2/* * */* if (rule.satisfy(*data)) std::cout << "satisfied" << std::endl; else { std::cout << "unsatisfied" << std::endl; } ================= On Mon, Mar 2, 2015 at 9:48 AM, Chengyu Fan wrote: > Hi Alex, > > Thanks for the reply. > > Further questions in line. > > On Sat, Feb 28, 2015 at 4:45 PM, Alex Afanasyev < > alexander.afanasyev at ucla.edu> wrote: > >> Hi Chengyu, >> >> I assumed there is a documentation for this method, but the commit that >> adds it is not yet merged. Here is the description we will have soon: >> >> /** >> * @brief Construct the rule >> * @param packetRegex regular expression to match the packet name that >> is qualified for the >> * the rule (e.g., `^(<.*>)$`) >> * @param signerRegex regular expression to match the the KeyLocator of >> the packet (e.g., >> * `^(<.*>)(<.*>)<>$`) >> * @param comparator Defines the way expanded signer's name is matched >> against expanded >> * packet's name. Possible values are: >> * - "is-prefix-of" >> * - "is-strict-prefix-of" >> * - "equal" >> > > Which symbol refers to which value? > > >> * @param packetExpand Expansion rule for packet's name (e.g., `\1`) >> * @param signerExpand Expansion rule for signer's name (e.g., `\1\2`) >> * @param isPositive flag denoting whether the rule is positive or >> negative >> * >> * @note A packet complies with the rule only if both \p packetRegex >> matches the packet name >> * and \p signerRegex matches the KeyLocator name >> > > According to the comparator description, I think this function also needs > to test if the expanded signer's name matched against the expanded packet's > name? > > >> */ >> >> >> On Feb 27, 2015, at 7:59 PM, Chengyu Fan wrote: >> >> Could you tell me how the SecRuleRelative Rule works? >> >> Specifically, what's the meaning of each parameter? What conditions the >> rule will test to make a incoming data satisfy the rule? >> ndn::SecRuleRelative::SecRuleRelative >> >> (const std::string & dataRegex,const std::string & signerRegex,const >> std::string & op,const std::string & dataExpand,const std::string & >> signerExpand,bool isPositive ) >> >> >> >> On Fri, Feb 27, 2015 at 1:59 PM, Alex Afanasyev < >> alexander.afanasyev at ucla.edu> wrote: >> >>> >>> On Feb 27, 2015, at 12:10 PM, Chengyu Fan wrote: >>> >>> Hi, >>> >>> I'm trying to use the validator-regex to validate the incoming data, but >>> I stuck at how to add the SecRuleRelative Rule. >>> >>> Can somebody tell me some clues? >>> >>> Specifically, I find the example in SecurityLibrary( >>> http://redmine.named-data.net/projects/ndn-cxx/wiki/SecurityLibrary), >>> but I don't understand the RuleRelative rule below ... >>> >>> SecRuleRelative rule("^(<>*)$", "^([^]*)(<>*)$", >>> ">", "\\1", "\\1\\2", true); >>> >>> What's the meaning of ">", "\\1", "\\1\\2" ? Can someone give me an >>> example? >>> >>> >>> This is just a regular expression rules. \\1 (\1, it?s just \ needs to >>> be escaped in c++) refer to th first group of the regular expression, >>> \\2 refer to the second group, etc. >>> >>> There are many documentation sources about regexps, e.g., >>> http://www.boost.org/doc/libs/1_57_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html >>> . >>> >>> The only difference in our regular expressions is the fact that it is >>> defined over name components, not just strings. There is a documentation >>> for this at >>> http://named-data.net/doc/ndn-cxx/current/tutorials/utils-ndn-regex.html >>> >>> ? >>> Alex >>> >>> >>> >> >> >> -- >> Thanks, >> >> Chengyu >> >> >> > > > -- > Thanks, > > Chengyu > -- Thanks, Chengyu -------------- next part -------------- An HTML attachment was scrubbed... URL: From yingdi at CS.UCLA.EDU Mon Mar 2 11:19:40 2015 From: yingdi at CS.UCLA.EDU (Yingdi Yu) Date: Mon, 2 Mar 2015 11:19:40 -0800 Subject: [Ndn-interest] How to add the SecRuleRelative Rules in validator-regex? In-Reply-To: References: <3AE5D813-81E9-449D-8FF9-045D0DD007F3@ucla.edu> <5C834D2E-8F04-4731-A42E-B5B9EE41F676@ucla.edu> Message-ID: The regex for key locator require ?dsk-?? but the signing key is ?ksk-??. Yingdi > On Mar 2, 2015, at 10:19 AM, Chengyu Fan wrote: > > Hi Alex, > > I wrote a toy example to use the SecRuleRelative (the code is listed below ) . > > I thought the data should satisfy the rule, but I always get "unsatisfied" on my ubuntu 14.04.1 ... Could you tell me what's wrong with the code? > > ================= > Name dataName("/test/site2/user2"); > dataName.append("testApp"); // the data name is /test/site2/user2/testApp > > // Create Data packet > static const std::string content = "HELLO WORLD"; > shared_ptr data = make_shared(); > data->setName(dataName); > data->setFreshnessPeriod(time::seconds(10)); > data->setContent(reinterpret_cast(content.c_str()), content.size()); > > Name producerId("/test/site2/user2"); > m_keyChain.signByIdentity(*data, producerId); // now the keyLocator is /test/site2/user2/KEY/ksk-1425277773626/ID-CERT > > SecRuleRelative rule("^(<>*)$", > "^([^]*)(<>*)$", > ">", "\\1 ", "\\1\\2 ", true); > /* /test/site2/user2/testApp should match the packetRegex "^(<>*)$, expand is /test/site2/user2/testApp > /test/site2/user2/KEY/ksk-1425277773626/ID-CERT should match the signerRegex, expand is /test/site2/user2/ > The data name /test/site2/user2/testApp is under the signer's namespace /test/site2/user2/ > */ > > if (rule.satisfy(*data)) > std::cout << "satisfied" << std::endl; > else { > std::cout << "unsatisfied" << std::endl; > } > ================= > > On Mon, Mar 2, 2015 at 9:48 AM, Chengyu Fan > wrote: > Hi Alex, > > Thanks for the reply. > > Further questions in line. > > On Sat, Feb 28, 2015 at 4:45 PM, Alex Afanasyev > wrote: > Hi Chengyu, > > I assumed there is a documentation for this method, but the commit that adds it is not yet merged. Here is the description we will have soon: > > /** > * @brief Construct the rule > * @param packetRegex regular expression to match the packet name that is qualified for the > * the rule (e.g., `^(<.*>)$`) > * @param signerRegex regular expression to match the the KeyLocator of the packet (e.g., > * `^(<.*>)(<.*>)<>$`) > * @param comparator Defines the way expanded signer's name is matched against expanded > * packet's name. Possible values are: > * - "is-prefix-of" > * - "is-strict-prefix-of" > * - "equal" > > Which symbol refers to which value? > > * @param packetExpand Expansion rule for packet's name (e.g., `\1`) > * @param signerExpand Expansion rule for signer's name (e.g., `\1\2`) > * @param isPositive flag denoting whether the rule is positive or negative > * > * @note A packet complies with the rule only if both \p packetRegex matches the packet name > * and \p signerRegex matches the KeyLocator name > > According to the comparator description, I think this function also needs to test if the expanded signer's name matched against the expanded packet's name? > > */ > > >> On Feb 27, 2015, at 7:59 PM, Chengyu Fan > wrote: >> >> Could you tell me how the SecRuleRelative Rule works? >> >> Specifically, what's the meaning of each parameter? What conditions the rule will test to make a incoming data satisfy the rule? >> ndn::SecRuleRelative::SecRuleRelative ( const std::string & dataRegex, >> const std::string & signerRegex, >> const std::string & op, >> const std::string & dataExpand, >> const std::string & signerExpand, >> bool isPositive >> ) >> >> >> >> On Fri, Feb 27, 2015 at 1:59 PM, Alex Afanasyev > wrote: >> >>> On Feb 27, 2015, at 12:10 PM, Chengyu Fan > wrote: >>> >>> Hi, >>> >>> I'm trying to use the validator-regex to validate the incoming data, but I stuck at how to add the SecRuleRelative Rule. >>> >>> Can somebody tell me some clues? >>> >>> Specifically, I find the example in SecurityLibrary(http://redmine.named-data.net/projects/ndn-cxx/wiki/SecurityLibrary ), but I don't understand the RuleRelative rule below ... >>> SecRuleRelative rule("^(<>*)$", "^([^]*)(<>*)$", >>> ">", "\\1", "\\1\\2", true); >>> >>> What's the meaning of ">", "\\1", "\\1\\2" ? Can someone give me an example? >> >> This is just a regular expression rules. \\1 <> (\1, it?s just \ needs to be escaped in c++) refer to th first group of the regular expression, \\2 <> refer to the second group, etc. >> >> There are many documentation sources about regexps, e.g., http://www.boost.org/doc/libs/1_57_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html . >> >> The only difference in our regular expressions is the fact that it is defined over name components, not just strings. There is a documentation for this at http://named-data.net/doc/ndn-cxx/current/tutorials/utils-ndn-regex.html >> >> ? >> Alex >> >> >> >> >> >> -- >> Thanks, >> >> Chengyu > > > > > -- > Thanks, > > Chengyu > > > > -- > Thanks, > > Chengyu > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengy.fan at gmail.com Mon Mar 2 11:34:44 2015 From: chengy.fan at gmail.com (Chengyu Fan) Date: Mon, 2 Mar 2015 12:34:44 -0700 Subject: [Ndn-interest] How to add the SecRuleRelative Rules in validator-regex? In-Reply-To: References: <3AE5D813-81E9-449D-8FF9-045D0DD007F3@ucla.edu> <5C834D2E-8F04-4731-A42E-B5B9EE41F676@ucla.edu> Message-ID: Oh, I didn't notice it. I run the code on another machine that didn't install the correct key. Thanks Yingdi. On Mon, Mar 2, 2015 at 12:19 PM, Yingdi Yu wrote: > The regex for key locator require ?dsk-?? but the signing key is ?ksk-??. > > Yingdi > > > > > On Mar 2, 2015, at 10:19 AM, Chengyu Fan wrote: > > Hi Alex, > > I wrote a toy example to use the SecRuleRelative (the code is listed > below ) . > > I thought the data should satisfy the rule, but I always get "unsatisfied" > on my ubuntu 14.04.1 ... Could you tell me what's wrong with the code? > > ================= > Name dataName("/test/site2/user2"); > dataName.append("testApp"); // the *data name* is > */test/site2/user2/testApp* > > // Create Data packet > static const std::string content = "HELLO WORLD"; > shared_ptr data = make_shared(); > data->setName(dataName); > data->setFreshnessPeriod(time::seconds(10)); > data->setContent(reinterpret_cast(content.c_str()), > content.size()); > > Name producerId("/test/site2/user2"); > m_keyChain.signByIdentity(*data, producerId); // now the *keyLocator* > is */test/site2/user2/KEY/ksk-1425277773626/ID-CERT* > > SecRuleRelative rule("*^(<>*)$*", > "*^([^]*)(<>*)$*", > *">", "\\1", "\\1\\2", true*); > /* */test/site2/user2/testApp *should match the packetRegex " > *^(<>*)$, *expand is */test/site2/user2/testApp* > */test/site2/user2/KEY/ksk-1425277773626/ID-CERT* should match > the signerRegex, expand is */test/site2/user2/* > The data name* /test/site2/user2/testApp *is* under *the signer's > namespace */test/site2/user2/* > * */* > > if (rule.satisfy(*data)) > std::cout << "satisfied" << std::endl; > else { > std::cout << "unsatisfied" << std::endl; > } > ================= > > On Mon, Mar 2, 2015 at 9:48 AM, Chengyu Fan wrote: > >> Hi Alex, >> >> Thanks for the reply. >> >> Further questions in line. >> >> On Sat, Feb 28, 2015 at 4:45 PM, Alex Afanasyev < >> alexander.afanasyev at ucla.edu> wrote: >> >>> Hi Chengyu, >>> >>> I assumed there is a documentation for this method, but the commit that >>> adds it is not yet merged. Here is the description we will have soon: >>> >>> /** >>> * @brief Construct the rule >>> * @param packetRegex regular expression to match the packet name that >>> is qualified for the >>> * the rule (e.g., `^(<.*>)$`) >>> * @param signerRegex regular expression to match the the KeyLocator >>> of the packet (e.g., >>> * `^(<.*>)(<.*>)<>$`) >>> * @param comparator Defines the way expanded signer's name is matched >>> against expanded >>> * packet's name. Possible values are: >>> * - "is-prefix-of" >>> * - "is-strict-prefix-of" >>> * - "equal" >>> >> >> Which symbol refers to which value? >> >> >>> * @param packetExpand Expansion rule for packet's name (e.g., `\1`) >>> * @param signerExpand Expansion rule for signer's name (e.g., `\1\2`) >>> * @param isPositive flag denoting whether the rule is positive or >>> negative >>> * >>> * @note A packet complies with the rule only if both \p packetRegex >>> matches the packet name >>> * and \p signerRegex matches the KeyLocator name >>> >> >> According to the comparator description, I think this function also needs >> to test if the expanded signer's name matched against the expanded packet's >> name? >> >> >>> */ >>> >>> >>> On Feb 27, 2015, at 7:59 PM, Chengyu Fan wrote: >>> >>> Could you tell me how the SecRuleRelative Rule works? >>> >>> Specifically, what's the meaning of each parameter? What conditions the >>> rule will test to make a incoming data satisfy the rule? >>> ndn::SecRuleRelative::SecRuleRelative >>> >>> (const std::string & dataRegex,const std::string & signerRegex,const >>> std::string & op,const std::string & dataExpand,const std::string & >>> signerExpand,bool isPositive ) >>> >>> >>> >>> On Fri, Feb 27, 2015 at 1:59 PM, Alex Afanasyev < >>> alexander.afanasyev at ucla.edu> wrote: >>> >>>> >>>> On Feb 27, 2015, at 12:10 PM, Chengyu Fan wrote: >>>> >>>> Hi, >>>> >>>> I'm trying to use the validator-regex to validate the incoming data, >>>> but I stuck at how to add the SecRuleRelative Rule. >>>> >>>> Can somebody tell me some clues? >>>> >>>> Specifically, I find the example in SecurityLibrary( >>>> http://redmine.named-data.net/projects/ndn-cxx/wiki/SecurityLibrary), >>>> but I don't understand the RuleRelative rule below ... >>>> >>>> SecRuleRelative rule("^(<>*)$", "^([^]*)(<>*)$", >>>> ">", "\\1", "\\1\\2", true); >>>> >>>> What's the meaning of ">", "\\1", "\\1\\2" ? Can someone give me an >>>> example? >>>> >>>> >>>> This is just a regular expression rules. \\1 (\1, it?s just \ needs >>>> to be escaped in c++) refer to th first group of the regular expression, >>>> \\2 refer to the second group, etc. >>>> >>>> There are many documentation sources about regexps, e.g., >>>> http://www.boost.org/doc/libs/1_57_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html >>>> . >>>> >>>> The only difference in our regular expressions is the fact that it is >>>> defined over name components, not just strings. There is a documentation >>>> for this at >>>> http://named-data.net/doc/ndn-cxx/current/tutorials/utils-ndn-regex.html >>>> >>>> ? >>>> Alex >>>> >>>> >>>> >>> >>> >>> -- >>> Thanks, >>> >>> Chengyu >>> >>> >>> >> >> >> -- >> Thanks, >> >> Chengyu >> > > > > -- > Thanks, > > Chengyu > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > -- Thanks, Chengyu -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Mon Mar 2 12:00:37 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Mon, 2 Mar 2015 23:30:37 +0330 Subject: [Ndn-interest] Data Accessibility in VM Live Migration over NDN References: <3921f845.1342a.14bcfabe795.Coremail.dejiang_zhou@163.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293D@m-pdc.sbu.ac.ir> <4AC03A6244C3C34BB52A7EC60B799C4C03CC293E@m-pdc.sbu.ac.ir> <030C7CA2-F6FF-4998-B519-37170C2ADF8D@memphis.edu> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC293F@m-pdc.sbu.ac.ir> Thanks for the correction. I forgot to mention. I doubt the Kite solution would do any significant good in such applications. Moving the VM to another AS is a kind of long term relocation to me. Regardless of using home anchor, alert service anchor or rendezvous anchor point, I guess it will end up with triangle routing. Unless there would be some fading/removing anchor point process, which I haven't seen it in Kite. Thanks Sabet -----Original Message----- From: Lan Wang (lanwang) [mailto:lanwang at memphis.edu] Sent: Mon 02/03/2015 21:43 To: Muhammad Hosain Abdollahi Sabet Cc: Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN This depends on the strategy. It could work in the way you described. Or the edge router could forward the interest using one of the delegated names. It should bring back data. If there's no data back, then it could try another one of the delegated names. Note that in NDN, the delegated names are names too, not addresses. For example, /ndnsim/net could be delegated to /com/att/user/alex/ndnsim. Lan On Mar 2, 2015, at 2:40 AM, Muhammad Hosain Abdollahi Sabet > wrote: Hi, Let assume we have tow copies and the MAP-AND-ENCAP mechanism implemented. Which route would be selected? I mean, the edge router sends the interest to both addresses(the old one, and the new old received from NDNS), right? Then depending on the measurements done by itself(the edge router), future interest will be sent to the designated route, and the endpoint application won't notify any of this. Am I right? Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Xiaoke Jiang Sent: Sat 2/28/2015 9:38 PM To: Dejiang Zhou Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Data Accessibility in VM Live Migration over NDN Hi Dejiang, Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem 1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ 2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests. Xiaoke (Shock) > On 28 Feb, 2015, at 2:12 am, Dejiang Zhou > wrote: > > Hi everyone, > I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed. > VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be "/ndn/cn/edu/tongji/vm/ping". However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix "/ndn/cn/edu/tongji". In contrast, Interest with name "/ndn/cn/edu/tongji/vm/ping" cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich". > Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration. > Best regards, > Dejiang Zhou > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Mon Mar 2 16:45:29 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Mon, 2 Mar 2015 16:45:29 -0800 Subject: [Ndn-interest] ChronoChat and its default RIB entries In-Reply-To: <2AB56CF2-6F8A-4432-81E1-C1B1F6E57F5E@ucla.edu> References: <2AB56CF2-6F8A-4432-81E1-C1B1F6E57F5E@ucla.edu> Message-ID: Hi Alex, Can you please elaborate little bit more on inline comments below? On Fri, Feb 27, 2015 at 3:41 PM, Alex Afanasyev < alexander.afanasyev at ucla.edu> wrote: > Hi Anil, > > I think you?re mixing a couple of things. The face that ChronoChat > application uses is just a channel between the application and NFD. It is > normally unix socket face, but it doesn?t really matter, as it is not > related to you being able to chat with other people. > > Besides having a face that points to a remote chat node, you need to > instruct NFD (RIB manager specifically) that specific data can be reached > through this face. > As you confirmed earlier, we need to configure the routable prefix of the remote users so that a local user can fetch the message data (after sync is updated) from remote party. You also mentioned below to register "/" prefix and I think by virtue of it, my chat call flow worked without configuring the actual name prefix of the chat participants (i.e. /ndn/edu/ucls/irl/). Configuration of "/" IMHO would be an overkill as it will potentially increase the Interest traffic, right? What are the implication of NOT registering "/" here? Can you please elaborate? .......(1) > In your specific face, you may start by registering /ndn/broadcast prefix > for your multicast udp face: > > nfdc register /ndn/broadcast 294 > > This will tell NFD that data packets with prefix /ndn/broadcast can be > retrieved if interest send out through face 294. > I did not quite get the rational behind this? I thought first to specify the faceId of the UDP tunnel we created to connect with remote NFD, but in above command you have quoted 294, which is the face between local chat client its NFD. Can you please clarify this? > You can also register / prefix, which will essentially mean that NFD can > try this face to fetch all kind of data packets. > Same as (1) above. > > ? > Alex > > On Feb 27, 2015, at 1:22 PM, Anil Jangam wrote: > > Hi, > > When I start the ChronoChat client, it creates certain default entries > into the RIB as follows. > > /ndn/broadcast/chronochat/chatroom-list route={faceid=294 (origin=0 cost=0 > ChildInherit)} > /ndn/broadcast/ChronoChat/chatroom-e8745dec route={faceid=294 (origin=0 > cost=0 ChildInherit)} > /ndn/broadcast/%F0./chronochat-tmp-identity/f4e4ea96/CHRONOCHAT-INVITATION > route={faceid=294 (origin=0 cost=0 ChildInherit)} > > > I checked the faceId 294, and it is a non udp/tcp type of face. > > faceid=294 remote=fd://23 local=unix:///run/nfd.sock counters={in={70i 6d > 16223B} out={0i 6d 5145B}} local on-demand point-to-point > > In what way I can program the ChronoChat client to use the specific face? > may be through some configuration file or so? > > I have configured a face which points to the remote user in the Chat. I > guess this local client should be using this interface (257) instead of > 294, correct? > > faceid=257 remote=udp4://224.0.23.170:56363 local=udp4:// > 133.164.60.154:56363 counters={in={0i 0d 0B} out={0i 0d 0B}} non-local > persistent point-to-point > > > /anil. > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dejiang_zhou at 163.com Tue Mar 3 04:09:22 2015 From: dejiang_zhou at 163.com (Dejiang Zhou) Date: Tue, 3 Mar 2015 20:09:22 +0800 (CST) Subject: [Ndn-interest] Data Accessibility in VM Live Migration over NDN In-Reply-To: References: <3921f845.1342a.14bcfabe795.Coremail.dejiang_zhou@163.com> Message-ID: <73d587d1.d494.14bdf8a60c1.Coremail.dejiang_zhou@163.com> Hi Xiaoke, Thank you for your advice. I looked on the papers you mentioned these days. I think both two ways are good solutions for problem of producer mobility. We will try to use it in our VM live migration experiment for checking if it works. In some times, we should start VM live migration because source host becomes overload. Therefore, the VM in source host need shut down after VM migration. Dejiang Zhou 2015-3-3 At 2015-03-01 02:08:16, "Xiaoke Jiang" wrote: Hi Dejiang, Here is my opinion to your question. What mentioned here seems to be producer mobility support, which is on-going research among NDN. A straightforward solution is to let UMICH router announce the a prefix /ndn/cn/edu/tongji/vm/ping to routing system. Besides the routing approach, there are some proposals too address this problem 1) Kite: http://named-data.net/publications/techreports/tr-ndn20-kite/ 2) LINK+ Map-and-Encap: may also helps but need more efforts: http://named-data.net/techreport/ndn-0004-3-scaling-ndn-routing.pdf p.s., I wonder why not keep the original copy of the vm after migration, therefore you would have two copies can serve future requests. Xiaoke (Shock) On 28 Feb, 2015, at 2:12 am, Dejiang Zhou wrote: Hi everyone, I have been studying VM live migration over NDN for mouths and taking some experiments in NDN testbed. VM is migrated from China to America with source host connecting NDN testbed node of Tongji and destination host in America connecting UMICH testbed node. Data in VM can be accessed by other host at the beginning. Name of Data can be ?/ndn/cn/edu/tongji/vm/ping?. However, this Data cannot be accessed after migration because the name of Data is not registered to FIB of other host. Other host is able to access the Data before migration because Interest can be forwarded to Tongji University by name prefix ?/ndn/cn/edu/tongji?. In contrast, Interest with name ?/ndn/cn/edu/tongji/vm/ping? cannot be forwarded to VM after migration because VM is behind UMICH testbed node but name prefix of the requested Data is not "/ndn/edu/umich". Does anyone have an idea for solving the problem? I think the rule of the solution is that name of Data in VM should not be changed after migration. Best regards, Dejiang Zhou _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Tue Mar 3 07:33:30 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Tue, 3 Mar 2015 19:03:30 +0330 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2942@m-pdc.sbu.ac.ir> Considering the fact that caching is an architectural attribute in NDN and again considering NDN trust model features, like cryptographic policies in command interest(public key-private key), is it ok for NDN to work in WSN scenarios? The need for designing a forwarding strategy seems clear. But having in mind that we have serious challenges for energy management in wireless sensors, couldn't we just ignore CS and PIT table for some applications, and have a simpler NFD? I've already seen the paper about securing the campus BMS on the website. It has said: "Our initial deployment collects sensing data from existing industry-standard sensors and gateways that employ legacy BMS protocols. Consequently, our design includes gateway devices that read data (through an internal IP network) from sensor devices running legacy BMS protocols and publish the resulting data in an NDN network." Well, I don't mean like that. I want to read data from sensors which running NDN protocols. I will be glad to read your ideas. Thanks Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Tue Mar 3 08:16:13 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Tue, 3 Mar 2015 16:16:13 +0000 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? Message-ID: Hello Sabet, A sensor can certainly receive an NDN interest and return a data packet using a client library. If the sensor's microcontroller is too small to sign the data packet with public key cryptography, it can use symmetric authentication, for example as described in section IV - D of "Securing Building Management Systems Using Named Data Networking". http://named-data.net/publications/securing_building_management_ndn/ Is it enough for your sensors to receive an interest and respond with a data packet? May I ask what is the memory and program storage size of your target microcontroller? (We have some experience with Arduino-based microcontrollers.) Thanks, - Jeff T From: Muhammad Hosain Abdollahi Sabet > Date: Tuesday, March 3, 2015 at 7:33 To: "Ndn-interest at lists.cs.ucla.edu" > Subject: [Ndn-interest] NDN architecture in wireless sensor networks? Considering the fact that caching is an architectural attribute in NDN and again considering NDN trust model features, like cryptographic policies in command interest(public key-private key), is it ok for NDN to work in WSN scenarios? The need for designing a forwarding strategy seems clear. But having in mind that we have serious challenges for energy management in wireless sensors, couldn't we just ignore CS and PIT table for some applications, and have a simpler NFD? I've already seen the paper about securing the campus BMS on the website. It has said: "Our initial deployment collects sensing data from existing industry-standard sensors and gateways that employ legacy BMS protocols. Consequently, our design includes gateway devices that read data (through an internal IP network) from sensor devices running legacy BMS protocols and publish the resulting data in an NDN network." Well, I don't mean like that. I want to read data from sensors which running NDN protocols. I will be glad to read your ideas. Thanks Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Tue Mar 3 08:33:43 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Tue, 3 Mar 2015 08:33:43 -0800 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? In-Reply-To: References: Message-ID: Sabet, You may want to take a look at this optimized ccn stack for WSN. I don't know however what footprint it works on. http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6529776&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6529776 /anil. On Mar 3, 2015 8:17 AM, "Thompson, Jeff" wrote: > Hello Sabet, > > A sensor can certainly receive an NDN interest and return a data packet > using a client library. If the sensor's microcontroller is too small to > sign the data packet with public key cryptography, it can use symmetric > authentication, for example as described in section IV - D of "Securing > Building Management Systems Using Named Data Networking". > http://named-data.net/publications/securing_building_management_ndn/ > > Is it enough for your sensors to receive an interest and respond with a > data packet? May I ask what is the memory and program storage size of your > target microcontroller? (We have some experience with Arduino-based > microcontrollers.) > > Thanks, > - Jeff T > > From: Muhammad Hosain Abdollahi Sabet > Date: Tuesday, March 3, 2015 at 7:33 > To: "Ndn-interest at lists.cs.ucla.edu" > Subject: [Ndn-interest] NDN architecture in wireless sensor networks? > > Considering the fact that caching is an architectural attribute in NDN > and again considering NDN trust model features, like cryptographic policies > in command interest(public key-private key), is it ok for NDN to work in > WSN scenarios? The need for designing a forwarding strategy seems clear. > But having in mind that we have serious challenges for energy management in > wireless sensors, couldn't we just ignore CS and PIT table for some > applications, and have a simpler NFD? > I've already seen the paper about securing the campus BMS on the website. > It has said: > > "Our initial deployment collects sensing data from existing > industry-standard sensors and > gateways that employ legacy BMS protocols. Consequently, our design > includes gateway devices that read data (through an internal IP network) > from sensor devices running legacy > BMS protocols and publish the resulting data in an NDN network." > > Well, I don't mean like that. I want to read data from sensors which > running NDN protocols. > > I will be glad to read your ideas. > > Thanks > Sabet > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.edu Tue Mar 3 09:23:56 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Tue, 3 Mar 2015 17:23:56 +0000 Subject: [Ndn-interest] File transfer application over NFD Message-ID: Hi, I am trying to do a simple file transfer over using NFD and ndn-cxx. I have a setup of two Virtual Machines and have tested the peek and poke applications to verify connectivity. Most available applications like ChronoShare, NDNFS etc seem to be implemented over ccnx or the old version of NDN >0.2. Is there any application available which runs with the latest version of NFS? Thank you. Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst From wangzhehao410305 at gmail.com Tue Mar 3 10:28:37 2015 From: wangzhehao410305 at gmail.com (Zhehao Wang) Date: Tue, 3 Mar 2015 10:28:37 -0800 Subject: [Ndn-interest] File transfer application over NFD In-Reply-To: References: Message-ID: Hi Divyashri, We do have a newer version of NDNFS available here , which is based on Wentao and Qiuhan's earlier work (Code base , tech report ). This newer version works with NFD (tested with release 0.2.0 ), but is built with ndn-cpp . If you want to try with ndn-cxx, we might need to modify the source a little bit; or alternatively, you can install ndn-cpp library. Please send me an email if any questions. Thanks, Zhehao On Tue, Mar 3, 2015 at 9:23 AM, Divyashri Bhat wrote: > Hi, > > I am trying to do a simple file transfer over using NFD and ndn-cxx. I > have a setup of two Virtual Machines and have tested the peek and poke > applications to verify connectivity. Most available applications like > ChronoShare, NDNFS etc seem to be implemented over ccnx or the old version > of NDN >0.2. > Is there any application available which runs with the latest version of > NFS? > > Thank you. > > Thank you. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Tue Mar 3 11:44:04 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Tue, 3 Mar 2015 23:14:04 +0330 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? References: Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2944@m-pdc.sbu.ac.ir> Jeff, Thanks for the reply. Actually we haven't experienced anything yet, not that I know of. I'm just the ndn-guy of the team, who is encouraging his colleagues to consider NDN for implementing their WSN scenario(I guess the reason why I'm here, is clear now:). My teammate will show up soon. She probably knows about the micro-controller specs. But in my humble assumption, it should be a kind of Arduino-based ones. The sensors which are used in Anil's suggested paper are ATxmega128A1 microcontrollers. What about the caching? In some star-like topologies most(if not all) of the sensors are not intermediate, and don't need content store, thus there is no need to check it, right? So why bother? Anil, Thank you so much. I will take a full look at that. Maybe we should consider some CCN-NDN differences then. Thanks, Sabet -----Original Message----- From: Anil Jangam [mailto:anilj.mailing at gmail.com] Sent: Tue 3/3/2015 8:03 PM To: Thompson, Jeff Cc: ndn-interest at lists.cs.ucla.edu; Muhammad Hosain Abdollahi Sabet Subject: Re: [Ndn-interest] NDN architecture in wireless sensor networks? Sabet, You may want to take a look at this optimized ccn stack for WSN. I don't know however what footprint it works on. http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6529776&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6529776 /anil. On Mar 3, 2015 8:17 AM, "Thompson, Jeff" wrote: > Hello Sabet, > > A sensor can certainly receive an NDN interest and return a data packet > using a client library. If the sensor's microcontroller is too small to > sign the data packet with public key cryptography, it can use symmetric > authentication, for example as described in section IV - D of "Securing > Building Management Systems Using Named Data Networking". > http://named-data.net/publications/securing_building_management_ndn/ > > Is it enough for your sensors to receive an interest and respond with a > data packet? May I ask what is the memory and program storage size of your > target microcontroller? (We have some experience with Arduino-based > microcontrollers.) > > Thanks, > - Jeff T > > From: Muhammad Hosain Abdollahi Sabet > Date: Tuesday, March 3, 2015 at 7:33 > To: "Ndn-interest at lists.cs.ucla.edu" > Subject: [Ndn-interest] NDN architecture in wireless sensor networks? > > Considering the fact that caching is an architectural attribute in NDN > and again considering NDN trust model features, like cryptographic policies > in command interest(public key-private key), is it ok for NDN to work in > WSN scenarios? The need for designing a forwarding strategy seems clear. > But having in mind that we have serious challenges for energy management in > wireless sensors, couldn't we just ignore CS and PIT table for some > applications, and have a simpler NFD? > I've already seen the paper about securing the campus BMS on the website. > It has said: > > "Our initial deployment collects sensing data from existing > industry-standard sensors and > gateways that employ legacy BMS protocols. Consequently, our design > includes gateway devices that read data (through an internal IP network) > from sensor devices running legacy > BMS protocols and publish the resulting data in an NDN network." > > Well, I don't mean like that. I want to read data from sensors which > running NDN protocols. > > I will be glad to read your ideas. > > Thanks > Sabet > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Tue Mar 3 12:02:07 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 3 Mar 2015 13:02:07 -0700 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang wrote: > Dear Junxiao, > > I'm Feixiong, a phd student from Rutgers University. I also work on > information-centric network and I'm trying to investigate content delivery > scenario in NDN. I look at the NDN prototype and come across some > questions. It would be great if you could provide me some guidance. > > As a first step, I'm trying to build a simple NDN testbed with four nodes > (A -- B -- C -- D). A is a NDN content server, B and C are NDN routers, D > is a NDN requester. Is there any related example of such content delivery > scenario? > > I have a few other questions for the setup (pardon me as I'm newbie to NDN > prototype..) : > > 1. how to configure network interfaces in nfd? > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they > share some code and both provide library for application usage. what's the > different between these two? > > I would appreciate a lot if you could give me some guidance. thanks a lot! > > Best Regards. > Feixiong > > -- > Feixiong Zhang, PhD candidate, > WINLAB, Rutgers University, New Jersey > *http://winlab.rutgers.edu/~feixiong/ > * > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Tue Mar 3 13:02:17 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Tue, 3 Mar 2015 21:02:17 +0000 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API changes more rapidly since it is used to research the latest NDN architectural ideas and is the library for NFD. ndn-cpp is an NDN client library for C++ which shares the same "Common Client Libraries" API with the other client libraries for Python, JavaScript and Java. The client libraries incorporate stable features from ndn-cxx and aim to support NDN applications on a range of platforms and languages. Thanks, - Jeff T From: Junxiao Shi > Date: Tuesday, March 3, 2015 at 12:02 To: "ndn-interest at lists.cs.ucla.edu" > Cc: Feixiong Zhang > Subject: Re: [Ndn-interest] question about NDN prototype On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang > wrote: Dear Junxiao, I'm Feixiong, a phd student from Rutgers University. I also work on information-centric network and I'm trying to investigate content delivery scenario in NDN. I look at the NDN prototype and come across some questions. It would be great if you could provide me some guidance. As a first step, I'm trying to build a simple NDN testbed with four nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN routers, D is a NDN requester. Is there any related example of such content delivery scenario? I have a few other questions for the setup (pardon me as I'm newbie to NDN prototype..) : 1. how to configure network interfaces in nfd? 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? I would appreciate a lot if you could give me some guidance. thanks a lot! Best Regards. Feixiong -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Tue Mar 3 13:10:57 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Tue, 3 Mar 2015 21:10:57 +0000 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2944@m-pdc.sbu.ac.ir> References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2944@m-pdc.sbu.ac.ir> Message-ID: Hi Sabet, > What about the caching? In some star-like topologies most(if not all) of the sensors are not intermediate, and don't need content store, thus there is no need to check it, right? So why bother? When you say "no need to check it" I assume you mean "no need to check if the cache already has a data packet for the interest." In your topoplogy, there would be a more powerful node that can run a forwarder with a cache. This should actually help the low-power sensors since they only have to answer the interest once since the returned data packet is cached in a forwarder. Future interests for the same sensor data would be answered from the cache in the forwarder, saving the low-power sensor from doing it. (I hope I understood your question correctly.) - Jeff T From: Muhammad Hosain Abdollahi Sabet > Date: Tuesday, March 3, 2015 at 11:44 To: Anil Jangam >, Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: RE: [Ndn-interest] NDN architecture in wireless sensor networks? Jeff, Thanks for the reply. Actually we haven't experienced anything yet, not that I know of. I'm just the ndn-guy of the team, who is encouraging his colleagues to consider NDN for implementing their WSN scenario(I guess the reason why I'm here, is clear now:). My teammate will show up soon. She probably knows about the micro-controller specs. But in my humble assumption, it should be a kind of Arduino-based ones. The sensors which are used in Anil's suggested paper are ATxmega128A1 microcontrollers. What about the caching? In some star-like topologies most(if not all) of the sensors are not intermediate, and don't need content store, thus there is no need to check it, right? So why bother? Anil, Thank you so much. I will take a full look at that. Maybe we should consider some CCN-NDN differences then. Thanks, Sabet -----Original Message----- From: Anil Jangam [mailto:anilj.mailing at gmail.com] Sent: Tue 3/3/2015 8:03 PM To: Thompson, Jeff Cc: ndn-interest at lists.cs.ucla.edu; Muhammad Hosain Abdollahi Sabet Subject: Re: [Ndn-interest] NDN architecture in wireless sensor networks? Sabet, You may want to take a look at this optimized ccn stack for WSN. I don't know however what footprint it works on. http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6529776&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6529776 /anil. On Mar 3, 2015 8:17 AM, "Thompson, Jeff" > wrote: > Hello Sabet, > > A sensor can certainly receive an NDN interest and return a data packet > using a client library. If the sensor's microcontroller is too small to > sign the data packet with public key cryptography, it can use symmetric > authentication, for example as described in section IV - D of "Securing > Building Management Systems Using Named Data Networking". > http://named-data.net/publications/securing_building_management_ndn/ > > Is it enough for your sensors to receive an interest and respond with a > data packet? May I ask what is the memory and program storage size of your > target microcontroller? (We have some experience with Arduino-based > microcontrollers.) > > Thanks, > - Jeff T > > From: Muhammad Hosain Abdollahi Sabet > > Date: Tuesday, March 3, 2015 at 7:33 > To: "Ndn-interest at lists.cs.ucla.edu" > > Subject: [Ndn-interest] NDN architecture in wireless sensor networks? > > Considering the fact that caching is an architectural attribute in NDN > and again considering NDN trust model features, like cryptographic policies > in command interest(public key-private key), is it ok for NDN to work in > WSN scenarios? The need for designing a forwarding strategy seems clear. > But having in mind that we have serious challenges for energy management in > wireless sensors, couldn't we just ignore CS and PIT table for some > applications, and have a simpler NFD? > I've already seen the paper about securing the campus BMS on the website. > It has said: > > "Our initial deployment collects sensing data from existing > industry-standard sensors and > gateways that employ legacy BMS protocols. Consequently, our design > includes gateway devices that read data (through an internal IP network) > from sensor devices running legacy > BMS protocols and publish the resulting data in an NDN network." > > Well, I don't mean like that. I want to read data from sensors which > running NDN protocols. > > I will be glad to read your ideas. > > Thanks > Sabet > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From feixiong at winlab.rutgers.EDU Tue Mar 3 13:49:53 2015 From: feixiong at winlab.rutgers.EDU (Feixiong Zhang) Date: Tue, 3 Mar 2015 16:49:53 -0500 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: thanks for the clarification! It helps a lot! for the NFD configuration of a router, for example the router has four network interfaces, I want to bind two specific interfaces for NFD. how could I achieve this? Is there any documents on such configuration? thanks. On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff wrote: > > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they > share some code and both provide library for application usage. what's the > different between these two? > > ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API > changes more rapidly since it is used to research the latest NDN > architectural ideas and is the library for NFD. > > ndn-cpp is an NDN client library for C++ which shares the same "Common > Client Libraries" API with the other client libraries for Python, > JavaScript and Java. The client libraries incorporate stable features from > ndn-cxx and aim to support NDN applications on a range of platforms and > languages. > > Thanks, > - Jeff T > > From: Junxiao Shi > Date: Tuesday, March 3, 2015 at 12:02 > To: "ndn-interest at lists.cs.ucla.edu" > Cc: Feixiong Zhang > Subject: Re: [Ndn-interest] question about NDN prototype > > > > On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang < > feixiong at winlab.rutgers.edu> wrote: > >> Dear Junxiao, >> >> I'm Feixiong, a phd student from Rutgers University. I also work on >> information-centric network and I'm trying to investigate content delivery >> scenario in NDN. I look at the NDN prototype and come across some >> questions. It would be great if you could provide me some guidance. >> >> As a first step, I'm trying to build a simple NDN testbed with four >> nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN >> routers, D is a NDN requester. Is there any related example of such content >> delivery scenario? >> >> I have a few other questions for the setup (pardon me as I'm newbie to >> NDN prototype..) : >> >> 1. how to configure network interfaces in nfd? >> 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they >> share some code and both provide library for application usage. what's the >> different between these two? >> >> I would appreciate a lot if you could give me some guidance. thanks a lot! >> >> Best Regards. >> Feixiong >> >> -- >> Feixiong Zhang, PhD candidate, >> WINLAB, Rutgers University, New Jersey >> *http://winlab.rutgers.edu/~feixiong/ >> * >> > > -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey *http://winlab.rutgers.edu/~feixiong/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Tue Mar 3 16:10:49 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Wed, 4 Mar 2015 00:10:49 +0000 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: Take a look at the "Connecting to remote NFDs" section of the NFD Getting Started Guide which describes what "nfdc register" does: http://named-data.net/doc/NFD/current/INSTALL.html See the nfdc man page for more details: http://named-data.net/doc/NFD/current/manpages/nfdc.html - Jeff T From: Feixiong Zhang > Date: Tuesday, March 3, 2015 at 13:49 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] question about NDN prototype thanks for the clarification! It helps a lot! for the NFD configuration of a router, for example the router has four network interfaces, I want to bind two specific interfaces for NFD. how could I achieve this? Is there any documents on such configuration? thanks. On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff > wrote: > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API changes more rapidly since it is used to research the latest NDN architectural ideas and is the library for NFD. ndn-cpp is an NDN client library for C++ which shares the same "Common Client Libraries" API with the other client libraries for Python, JavaScript and Java. The client libraries incorporate stable features from ndn-cxx and aim to support NDN applications on a range of platforms and languages. Thanks, - Jeff T From: Junxiao Shi > Date: Tuesday, March 3, 2015 at 12:02 To: "ndn-interest at lists.cs.ucla.edu" > Cc: Feixiong Zhang > Subject: Re: [Ndn-interest] question about NDN prototype On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang > wrote: Dear Junxiao, I'm Feixiong, a phd student from Rutgers University. I also work on information-centric network and I'm trying to investigate content delivery scenario in NDN. I look at the NDN prototype and come across some questions. It would be great if you could provide me some guidance. As a first step, I'm trying to build a simple NDN testbed with four nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN routers, D is a NDN requester. Is there any related example of such content delivery scenario? I have a few other questions for the setup (pardon me as I'm newbie to NDN prototype..) : 1. how to configure network interfaces in nfd? 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? I would appreciate a lot if you could give me some guidance. thanks a lot! Best Regards. Feixiong -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.edu Tue Mar 3 16:35:53 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Wed, 4 Mar 2015 00:35:53 +0000 Subject: [Ndn-interest] File transfer application over NFD In-Reply-To: References: Message-ID: Hi Zhehao, That worked great. I was able to setup the NDNFS on a server. The instructions ask me to install the Firefox plugin as a client application. On the old version of NDNFS, I saw the test client application as part of the NDNFS repo. In the latest version which you pointed me to its says this client application is under development. Since, I am limited by a CLI, I am looking for a simple application like client.cc to test the File transfer. Is there anything you would recommend? Or will the client application be ready soon? Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 3 Mar 2015, at 13:28, Zhehao Wang > wrote: Hi Divyashri, We do have a newer version of NDNFS available here, which is based on Wentao and Qiuhan's earlier work (Code base, tech report). This newer version works with NFD (tested with release 0.2.0), but is built with ndn-cpp. If you want to try with ndn-cxx, we might need to modify the source a little bit; or alternatively, you can install ndn-cpp library. Please send me an email if any questions. Thanks, Zhehao On Tue, Mar 3, 2015 at 9:23 AM, Divyashri Bhat > wrote: Hi, I am trying to do a simple file transfer over using NFD and ndn-cxx. I have a setup of two Virtual Machines and have tested the peek and poke applications to verify connectivity. Most available applications like ChronoShare, NDNFS etc seem to be implemented over ccnx or the old version of NDN >0.2. Is there any application available which runs with the latest version of NFS? Thank you. Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From wangzhehao410305 at gmail.com Tue Mar 3 16:59:44 2015 From: wangzhehao410305 at gmail.com (Zhehao Wang) Date: Tue, 3 Mar 2015 16:59:44 -0800 Subject: [Ndn-interest] File transfer application over NFD In-Reply-To: References: Message-ID: Hi Divyashri, Thanks for trying this out. There is a sample client application ready in that repository, (source code ), which is not updated in the readme. Please stand by and I'll send you a note with instructions and updates in Github readme. Thanks, Zhehao On Tue, Mar 3, 2015 at 4:35 PM, Divyashri Bhat wrote: > Hi Zhehao, > > That worked great. I was able to setup the NDNFS on a server. The > instructions ask me to install the Firefox plugin as a client application. > On the old version of NDNFS, I saw the test client application as part of > the NDNFS repo. In the latest version which you pointed me to its says this > client application is under development. Since, I am limited by a CLI, I am > looking for a simple application like client.cc to test > the File transfer. Is there anything you would recommend? Or will the > client application be ready soon? > > Thank you. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > On 3 Mar 2015, at 13:28, Zhehao Wang wangzhehao410305 at gmail.com>> wrote: > > Hi Divyashri, > > We do have a newer version of NDNFS available here< > https://github.com/remap/ndnfs-port>, which is based on Wentao and > Qiuhan's earlier work (Code base< > https://github.com/named-data/ndnfs/tree/sqlite>, tech report< > http://named-data.net/wp-content/uploads/2014/10/ndn-tr-27-ndnfs.pdf>). > > This newer version works with NFD (tested with release 0.2.0< > https://github.com/named-data/NFD/releases/tag/NFD-0.2.0>), but is built > with ndn-cpp. If you want to try > with ndn-cxx, we might need to modify the source a little bit; or > alternatively, you can install ndn-cpp library. > > Please send me an email if any questions. > > Thanks, > Zhehao > > On Tue, Mar 3, 2015 at 9:23 AM, Divyashri Bhat dbhat at umass.edu>> wrote: > Hi, > > I am trying to do a simple file transfer over using NFD and ndn-cxx. I > have a setup of two Virtual Machines and have tested the peek and poke > applications to verify connectivity. Most available applications like > ChronoShare, NDNFS etc seem to be implemented over ccnx or the old version > of NDN >0.2. > Is there any application available which runs with the latest version of > NFS? > > Thank you. > > Thank you. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Tue Mar 3 17:13:02 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Tue, 3 Mar 2015 17:13:02 -0800 Subject: [Ndn-interest] ChronoChat and its default RIB entries In-Reply-To: References: <2AB56CF2-6F8A-4432-81E1-C1B1F6E57F5E@ucla.edu> Message-ID: I presume you didn't get chance to look at my further comments. Can you please provide your comments? /anil On Mar 2, 2015 4:45 PM, "Anil Jangam" wrote: > Hi Alex, Can you please elaborate little bit more on inline comments below? > > On Fri, Feb 27, 2015 at 3:41 PM, Alex Afanasyev < > alexander.afanasyev at ucla.edu> wrote: > >> Hi Anil, >> >> I think you?re mixing a couple of things. The face that ChronoChat >> application uses is just a channel between the application and NFD. It is >> normally unix socket face, but it doesn?t really matter, as it is not >> related to you being able to chat with other people. >> >> Besides having a face that points to a remote chat node, you need to >> instruct NFD (RIB manager specifically) that specific data can be reached >> through this face. >> > As you confirmed earlier, we need to configure the routable prefix of the > remote users so that a local user can fetch the message data (after sync is > updated) from remote party. You also mentioned below to register "/" prefix > and I think by virtue of it, my chat call flow worked without configuring > the actual name prefix of the chat participants (i.e. /ndn/edu/ucls/irl/). > > Configuration of "/" IMHO would be an overkill as it will potentially > increase the Interest traffic, right? What are the implication of NOT > registering "/" here? Can you please elaborate? .......(1) > > >> In your specific face, you may start by registering /ndn/broadcast prefix >> for your multicast udp face: >> >> nfdc register /ndn/broadcast 294 >> > >> This will tell NFD that data packets with prefix /ndn/broadcast can be >> retrieved if interest send out through face 294. >> > I did not quite get the rational behind this? I thought first to specify > the faceId of the UDP tunnel we created to connect with remote NFD, but in > above command you have quoted 294, which is the face between local chat > client its NFD. Can you please clarify this? > > >> You can also register / prefix, which will essentially mean that NFD >> can try this face to fetch all kind of data packets. >> > Same as (1) above. > >> >> ? >> Alex >> >> On Feb 27, 2015, at 1:22 PM, Anil Jangam wrote: >> >> Hi, >> >> When I start the ChronoChat client, it creates certain default entries >> into the RIB as follows. >> >> /ndn/broadcast/chronochat/chatroom-list route={faceid=294 (origin=0 >> cost=0 ChildInherit)} >> /ndn/broadcast/ChronoChat/chatroom-e8745dec route={faceid=294 (origin=0 >> cost=0 ChildInherit)} >> /ndn/broadcast/%F0./chronochat-tmp-identity/f4e4ea96/CHRONOCHAT-INVITATION >> route={faceid=294 (origin=0 cost=0 ChildInherit)} >> >> >> I checked the faceId 294, and it is a non udp/tcp type of face. >> >> faceid=294 remote=fd://23 local=unix:///run/nfd.sock counters={in={70i >> 6d 16223B} out={0i 6d 5145B}} local on-demand point-to-point >> >> In what way I can program the ChronoChat client to use the specific face? >> may be through some configuration file or so? >> >> I have configured a face which points to the remote user in the Chat. I >> guess this local client should be using this interface (257) instead of >> 294, correct? >> >> faceid=257 remote=udp4://224.0.23.170:56363 local=udp4:// >> 133.164.60.154:56363 counters={in={0i 0d 0B} out={0i 0d 0B}} non-local >> persistent point-to-point >> >> >> /anil. >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From feixiong at winlab.rutgers.edu Tue Mar 3 18:05:55 2015 From: feixiong at winlab.rutgers.edu (Feixiong Zhang) Date: Tue, 3 Mar 2015 21:05:55 -0500 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: thanks a lot for the reference! On Tue, Mar 3, 2015 at 7:10 PM, Thompson, Jeff wrote: > Take a look at the "Connecting to remote NFDs" section of the NFD > Getting Started Guide which describes what "nfdc register" does: > http://named-data.net/doc/NFD/current/INSTALL.html > > See the nfdc man page for more details: > http://named-data.net/doc/NFD/current/manpages/nfdc.html > > - Jeff T > > From: Feixiong Zhang > Date: Tuesday, March 3, 2015 at 13:49 > To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > > Subject: Re: [Ndn-interest] question about NDN prototype > > thanks for the clarification! It helps a lot! > > for the NFD configuration of a router, for example the router has four > network interfaces, I want to bind two specific interfaces for NFD. how > could I achieve this? Is there any documents on such configuration? thanks. > > On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff > wrote: > >> > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they >> share some code and both provide library for application usage. what's the >> different between these two? >> >> ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API >> changes more rapidly since it is used to research the latest NDN >> architectural ideas and is the library for NFD. >> >> ndn-cpp is an NDN client library for C++ which shares the same "Common >> Client Libraries" API with the other client libraries for Python, >> JavaScript and Java. The client libraries incorporate stable features from >> ndn-cxx and aim to support NDN applications on a range of platforms and >> languages. >> >> Thanks, >> - Jeff T >> >> From: Junxiao Shi >> Date: Tuesday, March 3, 2015 at 12:02 >> To: "ndn-interest at lists.cs.ucla.edu" >> Cc: Feixiong Zhang >> Subject: Re: [Ndn-interest] question about NDN prototype >> >> >> >> On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang < >> feixiong at winlab.rutgers.edu> wrote: >> >>> Dear Junxiao, >>> >>> I'm Feixiong, a phd student from Rutgers University. I also work on >>> information-centric network and I'm trying to investigate content delivery >>> scenario in NDN. I look at the NDN prototype and come across some >>> questions. It would be great if you could provide me some guidance. >>> >>> As a first step, I'm trying to build a simple NDN testbed with four >>> nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN >>> routers, D is a NDN requester. Is there any related example of such content >>> delivery scenario? >>> >>> I have a few other questions for the setup (pardon me as I'm newbie to >>> NDN prototype..) : >>> >>> 1. how to configure network interfaces in nfd? >>> 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they >>> share some code and both provide library for application usage. what's the >>> different between these two? >>> >>> I would appreciate a lot if you could give me some guidance. thanks a >>> lot! >>> >>> Best Regards. >>> Feixiong >>> >>> -- >>> Feixiong Zhang, PhD candidate, >>> WINLAB, Rutgers University, New Jersey >>> *http://winlab.rutgers.edu/~feixiong/ >>> * >>> >> >> > > > -- > Feixiong Zhang, PhD candidate, > WINLAB, Rutgers University, New Jersey > *http://winlab.rutgers.edu/~feixiong/ > * > -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey *http://winlab.rutgers.edu/~feixiong/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Tue Mar 3 19:18:27 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Wed, 4 Mar 2015 06:48:27 +0330 Subject: [Ndn-interest] NDN architecture in wireless sensor networks? References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2944@m-pdc.sbu.ac.ir> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2945@m-pdc.sbu.ac.ir> Hi Jeff, Exactly! Intermediate nodes with higher capacity in storage and energy would run a forwarder with cach, and as you pointed out, whole system (overall) whould enjoy its benefits. When I said "why bother" I meant for tiny weak nodes in leaves which are connected only to one of those powerdul ones. Thanks, Sabet Hi Sabet, > What about the caching? In some star-like topologies most(if not all) of the sensors are not intermediate, and don't need content store, thus there is no need to check it, right? So why bother? When you say "no need to check it" I assume you mean "no need to check if the cache already has a data packet for the interest." In your topoplogy, there would be a more powerful node that can run a forwarder with a cache. This should actually help the low-power sensors since they only have to answer the interest once since the returned data packet is cached in a forwarder. Future interests for the same sensor data would be answered from the cache in the forwarder, saving the low-power sensor from doing it. (I hope I understood your question correctly.) - Jeff T From: Muhammad Hosain Abdollahi Sabet > Date: Tuesday, March 3, 2015 at 11:44 To: Anil Jangam >, Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: RE: [Ndn-interest] NDN architecture in wireless sensor networks? Jeff, Thanks for the reply. Actually we haven't experienced anything yet, not that I know of. I'm just the ndn-guy of the team, who is encouraging his colleagues to consider NDN for implementing their WSN scenario(I guess the reason why I'm here, is clear now:). My teammate will show up soon. She probably knows about the micro-controller specs. But in my humble assumption, it should be a kind of Arduino-based ones. The sensors which are used in Anil's suggested paper are ATxmega128A1 microcontrollers. What about the caching? In some star-like topologies most(if not all) of the sensors are not intermediate, and don't need content store, thus there is no need to check it, right? So why bother? Anil, Thank you so much. I will take a full look at that. Maybe we should consider some CCN-NDN differences then. Thanks, Sabet -----Original Message----- From: Anil Jangam [mailto:anilj.mailing at gmail.com] Sent: Tue 3/3/2015 8:03 PM To: Thompson, Jeff Cc: ndn-interest at lists.cs.ucla.edu; Muhammad Hosain Abdollahi Sabet Subject: Re: [Ndn-interest] NDN architecture in wireless sensor networks? Sabet, You may want to take a look at this optimized ccn stack for WSN. I don't know however what footprint it works on. http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6529776&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6529776 /anil. On Mar 3, 2015 8:17 AM, "Thompson, Jeff" > wrote: > Hello Sabet, > > A sensor can certainly receive an NDN interest and return a data packet > using a client library. If the sensor's microcontroller is too small to > sign the data packet with public key cryptography, it can use symmetric > authentication, for example as described in section IV - D of "Securing > Building Management Systems Using Named Data Networking". > http://named-data.net/publications/securing_building_management_ndn/ > > Is it enough for your sensors to receive an interest and respond with a > data packet? May I ask what is the memory and program storage size of your > target microcontroller? (We have some experience with Arduino-based > microcontrollers.) > > Thanks, > - Jeff T > > From: Muhammad Hosain Abdollahi Sabet > > Date: Tuesday, March 3, 2015 at 7:33 > To: "Ndn-interest at lists.cs.ucla.edu" > > Subject: [Ndn-interest] NDN architecture in wireless sensor networks? > > Considering the fact that caching is an architectural attribute in NDN > and again considering NDN trust model features, like cryptographic policies > in command interest(public key-private key), is it ok for NDN to work in > WSN scenarios? The need for designing a forwarding strategy seems clear. > But having in mind that we have serious challenges for energy management in > wireless sensors, couldn't we just ignore CS and PIT table for some > applications, and have a simpler NFD? > I've already seen the paper about securing the campus BMS on the website. > It has said: > > "Our initial deployment collects sensing data from existing > industry-standard sensors and > gateways that employ legacy BMS protocols. Consequently, our design > includes gateway devices that read data (through an internal IP network) > from sensor devices running legacy > BMS protocols and publish the resulting data in an NDN network." > > Well, I don't mean like that. I want to read data from sensors which > running NDN protocols. > > I will be glad to read your ideas. > > Thanks > Sabet > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Tue Mar 3 21:58:56 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Tue, 3 Mar 2015 21:58:56 -0800 Subject: [Ndn-interest] NFD/ndn-cxx 0.3.1 released Message-ID: <12E58E77-2BDC-4477-ABEF-924D6BA27B7A@ucla.edu> Dear all, We are pleased to announce release of version 0.3.1 of Named Data Networking Forwarding Daemon (NFD) and ndn-cxx library. The detailed release notes: - for NFD: http://named-data.net/doc/NFD/0.3.1/RELEASE_NOTES.html - for ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.3.1/RELEASE_NOTES.html More details about NFD, tutorials, HOWTOs, a FAQ and other useful resources are available on official webpages of NFD and ndn-cxx: - http://named-data.net/doc/NFD/0.3.1/ - http://named-data.net/doc/ndn-cxx/0.3.1/ * * * The NFD Team: Alex Afanasyev, Junxiao Shi, Beichuan Zhang, Lixia Zhang, Ilya Moiseenko, Yingdi Yu, Wentao Shang, Yi Huang, Spyridon Mastorakis, Jerald Paul Abraham, Steve DiBenedetto, Chengyu Fan, Christos Papadopoulos, Davide Pesavento, Giulio Grassi, Giovanni Pau, Hang Zhang, Tian Song, Haowei Yuan, Hila Ben Abraham, Patrick Crowley, Syed Obaid Amin, Vince Lehman, Minsheng Zhang, Lan Wang From feixiong at winlab.rutgers.edu Wed Mar 4 14:50:02 2015 From: feixiong at winlab.rutgers.edu (Feixiong Zhang) Date: Wed, 4 Mar 2015 17:50:02 -0500 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: Message-ID: Dear Jeff and others, I read through the nfdc and ndn-tlv-ping example, and I'm a bit confused that why the ping client needs to explicitly configure the route to the ping server. my understanding(guess) of the ndn-tlv-ping is that when the ping server advertises a name prefix, this advertisement is announced to the network and corresponding FIB routing entries should already be built by the routing protocol. Therefore, the ping client just needs to ping the name prefix without specifying the ping server's location, and the ICN routing infrastructure would forward the ping interest packet to the server. Please correct me where I'm wrong. btw, if I want to generate a specific network topology, do I always need to configure all the routing route for each node? It would be great if any of you could clarify my confusion. thanks a lot! On Tue, Mar 3, 2015 at 9:05 PM, Feixiong Zhang wrote: > thanks a lot for the reference! > > On Tue, Mar 3, 2015 at 7:10 PM, Thompson, Jeff > wrote: > >> Take a look at the "Connecting to remote NFDs" section of the NFD >> Getting Started Guide which describes what "nfdc register" does: >> http://named-data.net/doc/NFD/current/INSTALL.html >> >> See the nfdc man page for more details: >> http://named-data.net/doc/NFD/current/manpages/nfdc.html >> >> - Jeff T >> >> From: Feixiong Zhang >> Date: Tuesday, March 3, 2015 at 13:49 >> To: Jeff Thompson >> Cc: "ndn-interest at lists.cs.ucla.edu" >> >> Subject: Re: [Ndn-interest] question about NDN prototype >> >> thanks for the clarification! It helps a lot! >> >> for the NFD configuration of a router, for example the router has four >> network interfaces, I want to bind two specific interfaces for NFD. how >> could I achieve this? Is there any documents on such configuration? thanks. >> >> On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff >> wrote: >> >>> > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems >>> they share some code and both provide library for application usage. what's >>> the different between these two? >>> >>> ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API >>> changes more rapidly since it is used to research the latest NDN >>> architectural ideas and is the library for NFD. >>> >>> ndn-cpp is an NDN client library for C++ which shares the same "Common >>> Client Libraries" API with the other client libraries for Python, >>> JavaScript and Java. The client libraries incorporate stable features from >>> ndn-cxx and aim to support NDN applications on a range of platforms and >>> languages. >>> >>> Thanks, >>> - Jeff T >>> >>> From: Junxiao Shi >>> Date: Tuesday, March 3, 2015 at 12:02 >>> To: "ndn-interest at lists.cs.ucla.edu" >>> Cc: Feixiong Zhang >>> Subject: Re: [Ndn-interest] question about NDN prototype >>> >>> >>> >>> On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang < >>> feixiong at winlab.rutgers.edu> wrote: >>> >>>> Dear Junxiao, >>>> >>>> I'm Feixiong, a phd student from Rutgers University. I also work on >>>> information-centric network and I'm trying to investigate content delivery >>>> scenario in NDN. I look at the NDN prototype and come across some >>>> questions. It would be great if you could provide me some guidance. >>>> >>>> As a first step, I'm trying to build a simple NDN testbed with four >>>> nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN >>>> routers, D is a NDN requester. Is there any related example of such content >>>> delivery scenario? >>>> >>>> I have a few other questions for the setup (pardon me as I'm newbie >>>> to NDN prototype..) : >>>> >>>> 1. how to configure network interfaces in nfd? >>>> 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they >>>> share some code and both provide library for application usage. what's the >>>> different between these two? >>>> >>>> I would appreciate a lot if you could give me some guidance. thanks a >>>> lot! >>>> >>>> Best Regards. >>>> Feixiong >>>> >>>> -- >>>> Feixiong Zhang, PhD candidate, >>>> WINLAB, Rutgers University, New Jersey >>>> *http://winlab.rutgers.edu/~feixiong/ >>>> * >>>> >>> >>> >> >> >> -- >> Feixiong Zhang, PhD candidate, >> WINLAB, Rutgers University, New Jersey >> *http://winlab.rutgers.edu/~feixiong/ >> * >> > > > > -- > Feixiong Zhang, PhD candidate, > WINLAB, Rutgers University, New Jersey > *http://winlab.rutgers.edu/~feixiong/ > * > -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey *http://winlab.rutgers.edu/~feixiong/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Wed Mar 4 14:58:28 2015 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Wed, 4 Mar 2015 22:58:28 +0000 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: References: , Message-ID: <643D638C-D53E-412D-9580-B592B1F085B5@memphis.edu> The ping server registers the prefix with its local NFD, which will not advertise the prefix to other nodes. The registration simply makes sure that NFD will send an interest to the server if it matches the name prefix. You need to run a routing protocol, eg nlsr, to advertise the prefix. Lan On Mar 4, 2015, at 4:51 PM, Feixiong Zhang > wrote: Dear Jeff and others, I read through the nfdc and ndn-tlv-ping example, and I'm a bit confused that why the ping client needs to explicitly configure the route to the ping server. my understanding(guess) of the ndn-tlv-ping is that when the ping server advertises a name prefix, this advertisement is announced to the network and corresponding FIB routing entries should already be built by the routing protocol. Therefore, the ping client just needs to ping the name prefix without specifying the ping server's location, and the ICN routing infrastructure would forward the ping interest packet to the server. Please correct me where I'm wrong. btw, if I want to generate a specific network topology, do I always need to configure all the routing route for each node? It would be great if any of you could clarify my confusion. thanks a lot! On Tue, Mar 3, 2015 at 9:05 PM, Feixiong Zhang > wrote: thanks a lot for the reference! On Tue, Mar 3, 2015 at 7:10 PM, Thompson, Jeff > wrote: Take a look at the "Connecting to remote NFDs" section of the NFD Getting Started Guide which describes what "nfdc register" does: http://named-data.net/doc/NFD/current/INSTALL.html See the nfdc man page for more details: http://named-data.net/doc/NFD/current/manpages/nfdc.html - Jeff T From: Feixiong Zhang > Date: Tuesday, March 3, 2015 at 13:49 To: Jeff Thompson > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] question about NDN prototype thanks for the clarification! It helps a lot! for the NFD configuration of a router, for example the router has four network interfaces, I want to bind two specific interfaces for NFD. how could I achieve this? Is there any documents on such configuration? thanks. On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff > wrote: > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API changes more rapidly since it is used to research the latest NDN architectural ideas and is the library for NFD. ndn-cpp is an NDN client library for C++ which shares the same "Common Client Libraries" API with the other client libraries for Python, JavaScript and Java. The client libraries incorporate stable features from ndn-cxx and aim to support NDN applications on a range of platforms and languages. Thanks, - Jeff T From: Junxiao Shi > Date: Tuesday, March 3, 2015 at 12:02 To: "ndn-interest at lists.cs.ucla.edu" > Cc: Feixiong Zhang > Subject: Re: [Ndn-interest] question about NDN prototype On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang > wrote: Dear Junxiao, I'm Feixiong, a phd student from Rutgers University. I also work on information-centric network and I'm trying to investigate content delivery scenario in NDN. I look at the NDN prototype and come across some questions. It would be great if you could provide me some guidance. As a first step, I'm trying to build a simple NDN testbed with four nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN routers, D is a NDN requester. Is there any related example of such content delivery scenario? I have a few other questions for the setup (pardon me as I'm newbie to NDN prototype..) : 1. how to configure network interfaces in nfd? 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two? I would appreciate a lot if you could give me some guidance. thanks a lot! Best Regards. Feixiong -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey http://winlab.rutgers.edu/~feixiong/ _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From feixiong at winlab.rutgers.edu Wed Mar 4 17:50:56 2015 From: feixiong at winlab.rutgers.edu (Feixiong Zhang) Date: Wed, 4 Mar 2015 20:50:56 -0500 Subject: [Ndn-interest] question about NDN prototype In-Reply-To: <643D638C-D53E-412D-9580-B592B1F085B5@memphis.edu> References: <643D638C-D53E-412D-9580-B592B1F085B5@memphis.edu> Message-ID: thanks for the explanation! On Wed, Mar 4, 2015 at 5:58 PM, Lan Wang (lanwang) wrote: > The ping server registers the prefix with its local NFD, which will not > advertise the prefix to other nodes. The registration simply makes sure > that NFD will send an interest to the server if it matches the name > prefix. You need to run a routing protocol, eg nlsr, to advertise the > prefix. > > Lan > > On Mar 4, 2015, at 4:51 PM, Feixiong Zhang > wrote: > > Dear Jeff and others, > > I read through the nfdc and ndn-tlv-ping example, and I'm a bit confused > that why the ping client needs to explicitly configure the route to the > ping server. > > my understanding(guess) of the ndn-tlv-ping is that when the ping server > advertises a name prefix, this advertisement is announced to the network > and corresponding FIB routing entries should already be built by the > routing protocol. Therefore, the ping client just needs to ping the name > prefix without specifying the ping server's location, and the ICN routing > infrastructure would forward the ping interest packet to the server. Please > correct me where I'm wrong. > > btw, if I want to generate a specific network topology, do I always need > to configure all the routing route for each node? > > It would be great if any of you could clarify my confusion. thanks a lot! > > > > On Tue, Mar 3, 2015 at 9:05 PM, Feixiong Zhang < > feixiong at winlab.rutgers.edu> wrote: > >> thanks a lot for the reference! >> >> On Tue, Mar 3, 2015 at 7:10 PM, Thompson, Jeff >> wrote: >> >>> Take a look at the "Connecting to remote NFDs" section of the NFD >>> Getting Started Guide which describes what "nfdc register" does: >>> http://named-data.net/doc/NFD/current/INSTALL.html >>> >>> See the nfdc man page for more details: >>> http://named-data.net/doc/NFD/current/manpages/nfdc.html >>> >>> - Jeff T >>> >>> From: Feixiong Zhang >>> Date: Tuesday, March 3, 2015 at 13:49 >>> To: Jeff Thompson >>> Cc: "ndn-interest at lists.cs.ucla.edu" >>> >>> Subject: Re: [Ndn-interest] question about NDN prototype >>> >>> thanks for the clarification! It helps a lot! >>> >>> for the NFD configuration of a router, for example the router has four >>> network interfaces, I want to bind two specific interfaces for NFD. how >>> could I achieve this? Is there any documents on such configuration? thanks. >>> >>> On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff >>> wrote: >>> >>>> > 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems >>>> they share some code and both provide library for application usage. what's >>>> the different between these two? >>>> >>>> ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API >>>> changes more rapidly since it is used to research the latest NDN >>>> architectural ideas and is the library for NFD. >>>> >>>> ndn-cpp is an NDN client library for C++ which shares the same >>>> "Common Client Libraries" API with the other client libraries for Python, >>>> JavaScript and Java. The client libraries incorporate stable features from >>>> ndn-cxx and aim to support NDN applications on a range of platforms and >>>> languages. >>>> >>>> Thanks, >>>> - Jeff T >>>> >>>> From: Junxiao Shi >>>> Date: Tuesday, March 3, 2015 at 12:02 >>>> To: "ndn-interest at lists.cs.ucla.edu" >>>> Cc: Feixiong Zhang >>>> Subject: Re: [Ndn-interest] question about NDN prototype >>>> >>>> >>>> >>>> On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang < >>>> feixiong at winlab.rutgers.edu> wrote: >>>> >>>>> Dear Junxiao, >>>>> >>>>> I'm Feixiong, a phd student from Rutgers University. I also work on >>>>> information-centric network and I'm trying to investigate content delivery >>>>> scenario in NDN. I look at the NDN prototype and come across some >>>>> questions. It would be great if you could provide me some guidance. >>>>> >>>>> As a first step, I'm trying to build a simple NDN testbed with four >>>>> nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN >>>>> routers, D is a NDN requester. Is there any related example of such content >>>>> delivery scenario? >>>>> >>>>> I have a few other questions for the setup (pardon me as I'm newbie >>>>> to NDN prototype..) : >>>>> >>>>> 1. how to configure network interfaces in nfd? >>>>> 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they >>>>> share some code and both provide library for application usage. what's the >>>>> different between these two? >>>>> >>>>> I would appreciate a lot if you could give me some guidance. thanks a >>>>> lot! >>>>> >>>>> Best Regards. >>>>> Feixiong >>>>> >>>>> -- >>>>> Feixiong Zhang, PhD candidate, >>>>> WINLAB, Rutgers University, New Jersey >>>>> *http://winlab.rutgers.edu/~feixiong/ >>>>> * >>>>> >>>> >>>> >>> >>> >>> -- >>> Feixiong Zhang, PhD candidate, >>> WINLAB, Rutgers University, New Jersey >>> *http://winlab.rutgers.edu/~feixiong/ >>> * >>> >> >> >> >> -- >> Feixiong Zhang, PhD candidate, >> WINLAB, Rutgers University, New Jersey >> *http://winlab.rutgers.edu/~feixiong/ >> * >> > > > > -- > Feixiong Zhang, PhD candidate, > WINLAB, Rutgers University, New Jersey > *http://winlab.rutgers.edu/~feixiong/ > * > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -- Feixiong Zhang, PhD candidate, WINLAB, Rutgers University, New Jersey *http://winlab.rutgers.edu/~feixiong/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From sulfathgins at gmail.com Sat Mar 7 09:28:06 2015 From: sulfathgins at gmail.com (Sulfath Jins) Date: Sat, 7 Mar 2015 22:58:06 +0530 Subject: [Ndn-interest] About NDN In-Reply-To: References: Message-ID: Hai.. This is Sulfath from India intrested to knw more abt NDN. 1:What is the role of servers in Ndn.....what will happen? 2: what about existing protocols... -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhasabet at gmail.com Sat Mar 7 11:43:47 2015 From: mhasabet at gmail.com (Muhammad Sabet) Date: Sat, 7 Mar 2015 23:13:47 +0330 Subject: [Ndn-interest] About NDN In-Reply-To: References: Message-ID: Hi Sulfath, What do you mean by *"servers"*? You mean first publishers? If so, the role would be the same, but load would be much less. I can say that for sure. I guess there are other things that I don't know about. Thanks, Sabet On Sat, Mar 7, 2015 at 8:58 PM, Sulfath Jins wrote: > Hai.. > This is Sulfath from India intrested to knw more abt NDN. > 1:What is the role of servers in Ndn.....what will happen? > > 2: what about existing protocols... > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -- ????? ????? ?? ???? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sulfathgins at gmail.com Sat Mar 7 17:00:13 2015 From: sulfathgins at gmail.com (Sulfath Jins) Date: Sun, 8 Mar 2015 06:30:13 +0530 Subject: [Ndn-interest] About NDN Message-ID: My question is... if NDN implemented, is there any role to our server computers presently we r using. Or is there any client server architecture exist. ..in NDN -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Sat Mar 7 17:14:58 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Sun, 8 Mar 2015 01:14:58 +0000 Subject: [Ndn-interest] About NDN In-Reply-To: Message-ID: Sulfath, To get a better sense of things, you might take a look at these references, then post a follow up here: NDN Frequently Asked Questions (FAQ) http://named-data.net/project/faq/ NDN Video FAQ https://vimeo.com/channels/ndnvfaq NDN architecture overview http://named-data.net/project/archoverview/ "World on NDN" Tech Report NDN-0018 http://named-data.net/publications/techreports/world-on-ndn-11apr2014/ Specific app examples - ChronosChat Multi-user chat (Tech Report NDN-0008) http://named-data.net/publications/techreports/trchronos/ Video publisher/consumer example (Tech Report NDN-0017) http://named-data.net/publications/techreports/trstreaming/ Jeff From: Sulfath Jins > Date: Sun, 8 Mar 2015 06:30:13 +0530 To: > Subject: [Ndn-interest] About NDN My question is... if NDN implemented, is there any role to our server computers presently we r using. Or is there any client server architecture exist. ..in NDN _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Mon Mar 9 06:07:26 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Mon, 9 Mar 2015 13:07:26 +0000 Subject: [Ndn-interest] Adding HMAC to available NDN signature types In-Reply-To: References: <7BB03D9C-A407-444F-A07E-4EB2370DF504@cs.ucla.edu> <6F30B27A-8E53-4B36-9557-E07D16A57EBE@cs.ucla.edu> Message-ID: Hi Yingdi, Following up to your message (6 months ago): > Moreover, how to definition of KeyDigest is important in the validation part, so that data consumers can determine which symmetric key should be used to verify the HMAC. I agree with Marc that, for key longer than the block size, we can use the digest of digest of the key as the key id because the digest of the key is the actual key in this case. Agreed for KeyDigest. The KeyLocator can also a key Name but normally a key Name is used to fetch a certificate which has more info. But there is not certificate for HMAC so would you agree that we only describe a KeyDigest for the KeyLocator? Thanks, - Jeff T From: Yingdi Yu > Date: Tuesday, September 23, 2014 at 9:51 To: Jeff Thompson > Cc: Adeola Bannis >, "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Adding HMAC to available NDN signature types Hi Jeff, On Sep 22, 2014, at 10:02 AM, Thompson, Jeff > wrote: Hash output length vs. block size? Marc is right. The HmacWithSha256 algorithm hashes the key when it is longer than the block size (64 bytes), not the hash output length (32 bytes). So we would prohibit keys longer than 64 bytes (not 32 bytes). In Adeola's spec, the block size is not required to be 64 bytes. The RFC does not require the block size to be 64. I wonder if we should clarify that in the spec? Also, most applications will use a crypto library's HMAC function which should automatically hash the key if it is longer than the block size. It could be confusing to put this in the spec since the application writer may unnecessarily has the key when the crypto library will do it anyway, and more efficiently. I think the purpose of this spec is not only for application developers, but also for library developers, especially if we want to have good interoperability. So I think it would be better to clearly specify what is the requirement of generating a signature, how to generate a signature and what should be put into the SignatureInfo. Moreover, how to definition of KeyDigest is important in the validation part, so that data consumers can determine which symmetric key should be used to verify the HMAC. I agree with Marc that, for key longer than the block size, we can use the digest of digest of the key as the key id because the digest of the key is the actual key in this case. Yingdi -------------- next part -------------- An HTML attachment was scrubbed... URL: From cghali at uci.edu Mon Mar 9 18:14:12 2015 From: cghali at uci.edu (Cesar Ghali) Date: Mon, 9 Mar 2015 18:14:12 -0700 Subject: [Ndn-interest] NACKs in ICN Message-ID: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> Hi all, Some of you might be interested in the following report: A. Compagno, M. Conti, C. Ghali, G. Tsudik, To NACK or not to NACK? Negative Acknowledgments in Information-Centric Networking, arXiv: 1503.02123, March 7, 2015. URL: http://arxiv.org/pdf/1503.02123v1.pdf Of course, comments are appreciated. Thanks, Cesar -- PGP Key: http://www.cesarghali.info/contact.html PGP Key ID: 0x455D8052 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjs at cisco.com Tue Mar 10 07:15:41 2015 From: mjs at cisco.com (Mark Stapp) Date: Tue, 10 Mar 2015 10:15:41 -0400 Subject: [Ndn-interest] NACKs in ICN In-Reply-To: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> References: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> Message-ID: <54FEFC8D.3080107@cisco.com> Thanks for sending this around, Cesar. It's certainly good to see some details confirming the intuition that it would be costly for producers to try to use public-key operations on adversary-selected inputs as a means of denial-of-existence. but ... the paper doesn't explore many alternative schemes - we presented five, I think, at the last icnrg meeting. the conclusion of the paper - that NACKs have security problems - seems a little strong, based on the small number of approaches considered. It would be very interesting to see whether your analytical tools might be able to be applied to some of the other approaches. Thanks, Mark On 3/9/15 9:14 PM, Cesar Ghali wrote: > Hi all, > > Some of you might be interested in the following report: > > A. Compagno, M. Conti, C. Ghali, G. Tsudik, > To NACK or not to NACK? Negative Acknowledgments in Information-Centric > Networking, > arXiv: 1503.02123, March 7, 2015. > URL: http://arxiv.org/pdf/1503.02123v1.pdf > > Of course, comments are appreciated. > > Thanks, > 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 > From gts at ics.uci.EDU Tue Mar 10 08:37:03 2015 From: gts at ics.uci.EDU (GTS) Date: Tue, 10 Mar 2015 08:37:03 -0700 Subject: [Ndn-interest] NACKs in ICN In-Reply-To: <54FEFC8D.3080107@cisco.com> References: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> <54FEFC8D.3080107@cisco.com> Message-ID: <54FF0F9F.4060700@ics.uci.edu> Mark: is there a paper or presentation describing your 5 alternatives? BTW: as you probably noticed, our paper concerns only network-layer NACKs. We make no judgement about higher-layer NACKs. Cheers, Gene On 3/10/15 7:15 AM, Mark Stapp wrote: > Thanks for sending this around, Cesar. It's certainly good to see some > details confirming the intuition that it would be costly for producers > to try to use public-key operations on adversary-selected inputs as a > means of denial-of-existence. but ... the paper doesn't explore many > alternative schemes - we presented five, I think, at the last icnrg > meeting. the conclusion of the paper - that NACKs have security > problems - seems a little strong, based on the small number of > approaches considered. > > It would be very interesting to see whether your analytical tools > might be able to be applied to some of the other approaches. > > Thanks, > Mark > > On 3/9/15 9:14 PM, Cesar Ghali wrote: >> Hi all, >> >> Some of you might be interested in the following report: >> >> A. Compagno, M. Conti, C. Ghali, G. Tsudik, >> To NACK or not to NACK? Negative Acknowledgments in Information-Centric >> Networking, >> arXiv: 1503.02123, March 7, 2015. >> URL: http://arxiv.org/pdf/1503.02123v1.pdf >> >> Of course, comments are appreciated. >> >> Thanks, >> 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 >> > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjs at cisco.com Tue Mar 10 08:48:18 2015 From: mjs at cisco.com (Mark Stapp) Date: Tue, 10 Mar 2015 11:48:18 -0400 Subject: [Ndn-interest] NACKs in ICN In-Reply-To: <54FF0F9F.4060700@ics.uci.edu> References: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> <54FEFC8D.3080107@cisco.com> <54FF0F9F.4060700@ics.uci.edu> Message-ID: <54FF1242.3020200@cisco.com> Hi Gene, sure - I wasn't making a judgement either, quite the opposite - glad to see some interest in the topic. The slides I used at the icnrg interim meeting in January are here: http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-1.pptx I'm hoping to present some more info at the upcoming Dallas ietf, keep the issue alive. Thanks, Mark On 3/10/15 11:37 AM, GTS wrote: > Mark: > > is there a paper or presentation describing your 5 alternatives? > > BTW: as you probably noticed, our paper concerns only network-layer NACKs. > We make no judgement about higher-layer NACKs. > > Cheers, > Gene > > > On 3/10/15 7:15 AM, Mark Stapp wrote: >> Thanks for sending this around, Cesar. It's certainly good to see some >> details confirming the intuition that it would be costly for producers >> to try to use public-key operations on adversary-selected inputs as a >> means of denial-of-existence. but ... the paper doesn't explore many >> alternative schemes - we presented five, I think, at the last icnrg >> meeting. the conclusion of the paper - that NACKs have security >> problems - seems a little strong, based on the small number of >> approaches considered. >> >> It would be very interesting to see whether your analytical tools >> might be able to be applied to some of the other approaches. >> >> Thanks, >> Mark >> >> On 3/9/15 9:14 PM, Cesar Ghali wrote: >>> Hi all, >>> >>> Some of you might be interested in the following report: >>> >>> A. Compagno, M. Conti, C. Ghali, G. Tsudik, >>> To NACK or not to NACK? Negative Acknowledgments in Information-Centric >>> Networking, >>> arXiv: 1503.02123, March 7, 2015. >>> URL: http://arxiv.org/pdf/1503.02123v1.pdf >>> >>> Of course, comments are appreciated. >>> >>> Thanks, >>> 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 >>> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> > From Marc.Mosko at parc.com Tue Mar 10 09:09:57 2015 From: Marc.Mosko at parc.com (Marc.Mosko at parc.com) Date: Tue, 10 Mar 2015 16:09:57 +0000 Subject: [Ndn-interest] NACKs in ICN In-Reply-To: <54FEFC8D.3080107@cisco.com> References: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> <54FEFC8D.3080107@cisco.com> Message-ID: <61F1A1C5-E386-4DA8-84EE-6B7DE7362356@parc.com> I?ll second Mark?s opinion that it?s great to get a lot of these issues with cnacks and fnacks written up and public. I agree that cnaks pose potential computational DoS attacks and when cached content DoS. As to a solution to safely use cnacks, I think it will depend a lot on how the interests are being used. For example, using Interests for content discovery where you issue a long-standing interest waiting for the next item would probably use a different cnack approach than someone trying to do something else. I think in the case of fnacks, having a secure neighbor protocol and local key exchange in ccnx/ndn would go a long way towards making fnacks practical. This seems like a much lower barrier than cnacks. In section IV.E (experimenting with cnacks), did this include an signing time too or was it from cache pollution? It wasn?t clear what specifically contributed to the increased time. Also, if a producer will issue a cnack for plausible content and not random names, isn?t that a big information leak for someone name scanning? That?s like a firewall sending an ICMP packets to let a hacker know when they?re on the right track (well, I guess its the opposite, as a bad firewall sending prohibited is for bad ports and a cnack for a plausible name is for a good name). Marc On Mar 10, 2015, at 7:15 AM, Mark Stapp wrote: > Thanks for sending this around, Cesar. It's certainly good to see some details confirming the intuition that it would be costly for producers to try to use public-key operations on adversary-selected inputs as a means of denial-of-existence. but ... the paper doesn't explore many alternative schemes - we presented five, I think, at the last icnrg meeting. the conclusion of the paper - that NACKs have security problems - seems a little strong, based on the small number of approaches considered. > > It would be very interesting to see whether your analytical tools might be able to be applied to some of the other approaches. > > Thanks, > Mark > > On 3/9/15 9:14 PM, Cesar Ghali wrote: >> Hi all, >> >> Some of you might be interested in the following report: >> >> A. Compagno, M. Conti, C. Ghali, G. Tsudik, >> To NACK or not to NACK? Negative Acknowledgments in Information-Centric >> Networking, >> arXiv: 1503.02123, March 7, 2015. >> URL: http://arxiv.org/pdf/1503.02123v1.pdf >> >> Of course, comments are appreciated. >> >> Thanks, >> 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 >> > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From cghali at uci.edu Tue Mar 10 15:05:09 2015 From: cghali at uci.edu (Cesar Ghali) Date: Tue, 10 Mar 2015 15:05:09 -0700 Subject: [Ndn-interest] NACKs in ICN In-Reply-To: <61F1A1C5-E386-4DA8-84EE-6B7DE7362356@parc.com> References: <7C0EEAFE-2506-4B32-B0C7-1E5C3C2636D0@uci.edu> <54FEFC8D.3080107@cisco.com> <61F1A1C5-E386-4DA8-84EE-6B7DE7362356@parc.com> Message-ID: <54FF6A95.90209@uci.edu> Hi Marc, The experiments that we did in Section IV.E were to measure the performance of serving existing content by a producer under cnacks DoS attack. Benign consumers always request existing content, and at the same time, malicious consumers are requesting non-existing content forcing the producer to generate and sign cnacks. We only measure the time required by the producer to reply to interests by benign consumers. The more non-sensical interests processed by the producer the more time it needs to process interests requesting existing content. Specifically the increased time of processing benign consumers interests is because the producer is busy with signing a lot of cnacks. Also in this case, the producer is serving per-generated static content objects, i.e. no run-time signing of existing content. Thanks, Cesar On 03/10/2015 09:09 AM, Marc.Mosko at parc.com wrote: > I?ll second Mark?s opinion that it?s great to get a lot of these issues with cnacks and fnacks written up and public. > > I agree that cnaks pose potential computational DoS attacks and when cached content DoS. As to a solution to safely use cnacks, I think it will depend a lot on how the interests are being used. For example, using Interests for content discovery where you issue a long-standing interest waiting for the next item would probably use a different cnack approach than someone trying to do something else. > > I think in the case of fnacks, having a secure neighbor protocol and local key exchange in ccnx/ndn would go a long way towards making fnacks practical. This seems like a much lower barrier than cnacks. > > In section IV.E (experimenting with cnacks), did this include an signing time too or was it from cache pollution? It wasn?t clear what specifically contributed to the increased time. > > Also, if a producer will issue a cnack for plausible content and not random names, isn?t that a big information leak for someone name scanning? That?s like a firewall sending an ICMP packets to let a hacker know when they?re on the right track (well, I guess its the opposite, as a bad firewall sending prohibited is for bad ports and a cnack for a plausible name is for a good name). > > Marc > > On Mar 10, 2015, at 7:15 AM, Mark Stapp wrote: > >> Thanks for sending this around, Cesar. It's certainly good to see some details confirming the intuition that it would be costly for producers to try to use public-key operations on adversary-selected inputs as a means of denial-of-existence. but ... the paper doesn't explore many alternative schemes - we presented five, I think, at the last icnrg meeting. the conclusion of the paper - that NACKs have security problems - seems a little strong, based on the small number of approaches considered. >> >> It would be very interesting to see whether your analytical tools might be able to be applied to some of the other approaches. >> >> Thanks, >> Mark >> >> On 3/9/15 9:14 PM, Cesar Ghali wrote: >>> Hi all, >>> >>> Some of you might be interested in the following report: >>> >>> A. Compagno, M. Conti, C. Ghali, G. Tsudik, >>> To NACK or not to NACK? Negative Acknowledgments in Information-Centric >>> Networking, >>> arXiv: 1503.02123, March 7, 2015. >>> URL: http://arxiv.org/pdf/1503.02123v1.pdf >>> >>> Of course, comments are appreciated. >>> >>> Thanks, >>> 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 >>> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -- cesarghali.info From anilj.mailing at gmail.com Sun Mar 15 14:47:34 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 14:47:34 -0700 Subject: [Ndn-interest] NFD Issues. Message-ID: Today, I noticed an issue with starting the NFD service. Apparently, it is crashing since the process Id it shows after nfd-start does not exist any more in process status. However, when I try to restart it again, it says, "start: Job is already running: nfd". There are multiple issues here. When I do nfd-status, it is not able to connect to the NFD. Some of the logs are attached below. ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start nfd start/running, process 5942 ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start start: Job is already running: nfd ndnusr1 at ndnhost1:~/sandbox/NFD$ ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status ERROR: error while receiving data from socket (Connection reset by peer) ndnusr1 at ndnhost1:~/sandbox/NFD$ I also tried compiling a new version of the NFD from source, and was stopped by the following compilation error. Is this new or am I missing something in my environment? ndnusr1 at ndnhost1:~/sandbox/NFD$ ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' [ 3/121] Compiling core/city-hash.cpp [ 5/121] Compiling core/global-io.cpp [ 6/121] Compiling core/network-interface.cpp [ 8/121] Compiling core/privilege-helper.cpp [ 9/121] Compiling core/random.cpp [ 12/121] Compiling core/logger.cpp [ 15/121] Compiling daemon/face/multicast-udp-face.cpp [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp ../core/logger.cpp: In static member function ?static const char* nfd::Logger::now()?: ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is incompatible with microseconds::rep static_assert(std::is_same::value, ^ ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type ?long int?, but argument 4 has type ?boost::chrono::duration >::rep {aka long long int}? [-Wformat=] microsecondsSinceEpoch % ONE_SECOND); ^ ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type ?long int?, but argument 5 has type ?boost::chrono::duration >::rep {aka long long int}? [-Wformat=] ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type ?long int?, but argument 4 has type ?boost::chrono::duration >::rep {aka long long int}? [-Wformat=] ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type ?long int?, but argument 5 has type ?boost::chrono::duration >::rep {aka long long int}? [-Wformat=] Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' Build failed -> task in 'core-objects' failed (exit status 1): {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-fPIC', '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', '-I/home/ndnusr1/sandbox/NFD/build/core', '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', '../core/logger.cpp', '-c', '-o', '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] Regards, /anil. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Mar 15 14:55:02 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Sun, 15 Mar 2015 14:55:02 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Anil What operating system version is running? What Boost version is installed? Yours, Junxiao On Mar 15, 2015 2:48 PM, "Anil Jangam" wrote: > Today, I noticed an issue with starting the NFD service. Apparently, it is > crashing since the process Id it shows after nfd-start does not exist any > more in process status. However, when I try to restart it again, it says, > "start: Job is already running: nfd". > > There are multiple issues here. When I do nfd-status, it is not able to > connect to the NFD. Some of the logs are attached below. > > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start > nfd start/running, process 5942 > > ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 > ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 > > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start > start: Job is already running: nfd > > ndnusr1 at ndnhost1:~/sandbox/NFD$ > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status > ERROR: error while receiving data from socket (Connection reset by peer) > ndnusr1 at ndnhost1:~/sandbox/NFD$ > > > I also tried compiling a new version of the NFD from source, and was > stopped by the following compilation error. Is this new or am I missing > something in my environment? > > ndnusr1 at ndnhost1:~/sandbox/NFD$ > ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf > Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' > [ 3/121] Compiling core/city-hash.cpp > [ 5/121] Compiling core/global-io.cpp > [ 6/121] Compiling core/network-interface.cpp > [ 8/121] Compiling core/privilege-helper.cpp > [ 9/121] Compiling core/random.cpp > [ 12/121] Compiling core/logger.cpp > [ 15/121] Compiling daemon/face/multicast-udp-face.cpp > [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp > ../core/logger.cpp: In static member function ?static const char* > nfd::Logger::now()?: > ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is > incompatible with microseconds::rep > static_assert(std::is_same::value, > ^ > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 4 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > microsecondsSinceEpoch % ONE_SECOND); > ^ > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 5 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 4 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 5 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > > Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' > Build failed > -> task in 'core-objects' failed (exit status 1): > {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} > ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-fPIC', > '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', > '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', > '-I/home/ndnusr1/sandbox/NFD/build/core', > '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', > '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', > '../core/logger.cpp', '-c', '-o', > '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] > > Regards, > /anil. > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sun Mar 15 14:55:37 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 14:55:37 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: I am having version 0.3.1 ndnusr1 at ndnhost1:~/sandbox/NFD$ nfdc -V 0.3.1 /anil. On Sun, Mar 15, 2015 at 2:47 PM, Anil Jangam wrote: > Today, I noticed an issue with starting the NFD service. Apparently, it is > crashing since the process Id it shows after nfd-start does not exist any > more in process status. However, when I try to restart it again, it says, > "start: Job is already running: nfd". > > There are multiple issues here. When I do nfd-status, it is not able to > connect to the NFD. Some of the logs are attached below. > > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start > nfd start/running, process 5942 > > ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 > ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 > > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start > start: Job is already running: nfd > > ndnusr1 at ndnhost1:~/sandbox/NFD$ > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status > ERROR: error while receiving data from socket (Connection reset by peer) > ndnusr1 at ndnhost1:~/sandbox/NFD$ > > > I also tried compiling a new version of the NFD from source, and was > stopped by the following compilation error. Is this new or am I missing > something in my environment? > > ndnusr1 at ndnhost1:~/sandbox/NFD$ > ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf > Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' > [ 3/121] Compiling core/city-hash.cpp > [ 5/121] Compiling core/global-io.cpp > [ 6/121] Compiling core/network-interface.cpp > [ 8/121] Compiling core/privilege-helper.cpp > [ 9/121] Compiling core/random.cpp > [ 12/121] Compiling core/logger.cpp > [ 15/121] Compiling daemon/face/multicast-udp-face.cpp > [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp > ../core/logger.cpp: In static member function ?static const char* > nfd::Logger::now()?: > ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is > incompatible with microseconds::rep > static_assert(std::is_same::value, > ^ > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 4 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > microsecondsSinceEpoch % ONE_SECOND); > ^ > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 5 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 4 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type > ?long int?, but argument 5 has type ?boost::chrono::duration boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] > > Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' > Build failed > -> task in 'core-objects' failed (exit status 1): > {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} > ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-fPIC', > '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', > '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', > '-I/home/ndnusr1/sandbox/NFD/build/core', > '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', > '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', > '../core/logger.cpp', '-c', '-o', > '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] > > Regards, > /anil. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sun Mar 15 14:57:51 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 14:57:51 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Junxiao, Boost library version: ndnusr1 at ndnhost1:~/sandbox/NFD$ dpkg --get-selections | grep -v deinstall | grep -i boost libboost-all-dev install libboost-atomic-dev:amd64 install libboost-atomic1.54-dev:amd64 install libboost-atomic1.54.0:amd64 install libboost-chrono-dev:amd64 install OS version: ndnusr1 at ndnhost1:~/sandbox/NFD$ uname -a Linux ndnhost1 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Ubuntu version: ndnusr1 at ndnhost1:~/sandbox/NFD$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty /anil. On Sun, Mar 15, 2015 at 2:55 PM, Junxiao Shi wrote: > Hi Anil > > What operating system version is running? > > What Boost version is installed? > > Yours, Junxiao > On Mar 15, 2015 2:48 PM, "Anil Jangam" wrote: > >> Today, I noticed an issue with starting the NFD service. Apparently, it >> is crashing since the process Id it shows after nfd-start does not exist >> any more in process status. However, when I try to restart it again, it >> says, "start: Job is already running: nfd". >> >> There are multiple issues here. When I do nfd-status, it is not able to >> connect to the NFD. Some of the logs are attached below. >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >> nfd start/running, process 5942 >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 >> ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >> start: Job is already running: nfd >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status >> ERROR: error while receiving data from socket (Connection reset by peer) >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> >> >> I also tried compiling a new version of the NFD from source, and was >> stopped by the following compilation error. Is this new or am I missing >> something in my environment? >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf >> Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' >> [ 3/121] Compiling core/city-hash.cpp >> [ 5/121] Compiling core/global-io.cpp >> [ 6/121] Compiling core/network-interface.cpp >> [ 8/121] Compiling core/privilege-helper.cpp >> [ 9/121] Compiling core/random.cpp >> [ 12/121] Compiling core/logger.cpp >> [ 15/121] Compiling daemon/face/multicast-udp-face.cpp >> [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp >> ../core/logger.cpp: In static member function ?static const char* >> nfd::Logger::now()?: >> ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is >> incompatible with microseconds::rep >> static_assert(std::is_same::value, >> ^ >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 4 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> microsecondsSinceEpoch % ONE_SECOND); >> ^ >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 5 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 4 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 5 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> >> Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' >> Build failed >> -> task in 'core-objects' failed (exit status 1): >> {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} >> ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', >> '-fPIC', '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', >> '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', >> '-I/home/ndnusr1/sandbox/NFD/build/core', >> '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', >> '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', >> '../core/logger.cpp', '-c', '-o', >> '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] >> >> Regards, >> /anil. >> >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Mar 15 15:02:12 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Sun, 15 Mar 2015 15:02:12 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Anil I need to know the version of operating system and compiler, not just NFD. Also, NFD configuration file is incompatible between versions. Purge the old configuration and create them again. Choose "maintainer version" during future upgrades. Yours, Junxiao On Mar 15, 2015 2:56 PM, "Anil Jangam" wrote: > I am having version 0.3.1 > > ndnusr1 at ndnhost1:~/sandbox/NFD$ nfdc -V > 0.3.1 > > > /anil. > > > On Sun, Mar 15, 2015 at 2:47 PM, Anil Jangam > wrote: > >> Today, I noticed an issue with starting the NFD service. Apparently, it >> is crashing since the process Id it shows after nfd-start does not exist >> any more in process status. However, when I try to restart it again, it >> says, "start: Job is already running: nfd". >> >> There are multiple issues here. When I do nfd-status, it is not able to >> connect to the NFD. Some of the logs are attached below. >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >> nfd start/running, process 5942 >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 >> ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >> start: Job is already running: nfd >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status >> ERROR: error while receiving data from socket (Connection reset by peer) >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> >> >> I also tried compiling a new version of the NFD from source, and was >> stopped by the following compilation error. Is this new or am I missing >> something in my environment? >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ >> ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf >> Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' >> [ 3/121] Compiling core/city-hash.cpp >> [ 5/121] Compiling core/global-io.cpp >> [ 6/121] Compiling core/network-interface.cpp >> [ 8/121] Compiling core/privilege-helper.cpp >> [ 9/121] Compiling core/random.cpp >> [ 12/121] Compiling core/logger.cpp >> [ 15/121] Compiling daemon/face/multicast-udp-face.cpp >> [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp >> ../core/logger.cpp: In static member function ?static const char* >> nfd::Logger::now()?: >> ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is >> incompatible with microseconds::rep >> static_assert(std::is_same::value, >> ^ >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 4 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> microsecondsSinceEpoch % ONE_SECOND); >> ^ >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 5 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 4 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >> ?long int?, but argument 5 has type ?boost::chrono::duration> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >> >> Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' >> Build failed >> -> task in 'core-objects' failed (exit status 1): >> {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} >> ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', >> '-fPIC', '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', >> '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', >> '-I/home/ndnusr1/sandbox/NFD/build/core', >> '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', >> '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', >> '../core/logger.cpp', '-c', '-o', >> '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] >> >> Regards, >> /anil. >> >> > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sun Mar 15 15:04:32 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 15:04:32 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Compiler version is: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) What is "maintainer version" and how to invoke it? /anil. On Sun, Mar 15, 2015 at 3:02 PM, Junxiao Shi wrote: > Hi Anil > > I need to know the version of operating system and compiler, not just NFD. > > Also, NFD configuration file is incompatible between versions. > Purge the old configuration and create them again. > Choose "maintainer version" during future upgrades. > > Yours, Junxiao > On Mar 15, 2015 2:56 PM, "Anil Jangam" wrote: > >> I am having version 0.3.1 >> >> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfdc -V >> 0.3.1 >> >> >> /anil. >> >> >> On Sun, Mar 15, 2015 at 2:47 PM, Anil Jangam >> wrote: >> >>> Today, I noticed an issue with starting the NFD service. Apparently, it >>> is crashing since the process Id it shows after nfd-start does not exist >>> any more in process status. However, when I try to restart it again, it >>> says, "start: Job is already running: nfd". >>> >>> There are multiple issues here. When I do nfd-status, it is not able to >>> connect to the NFD. Some of the logs are attached below. >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >>> nfd start/running, process 5942 >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 >>> ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >>> start: Job is already running: nfd >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status >>> ERROR: error while receiving data from socket (Connection reset by peer) >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>> >>> >>> I also tried compiling a new version of the NFD from source, and was >>> stopped by the following compilation error. Is this new or am I missing >>> something in my environment? >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf >>> Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' >>> [ 3/121] Compiling core/city-hash.cpp >>> [ 5/121] Compiling core/global-io.cpp >>> [ 6/121] Compiling core/network-interface.cpp >>> [ 8/121] Compiling core/privilege-helper.cpp >>> [ 9/121] Compiling core/random.cpp >>> [ 12/121] Compiling core/logger.cpp >>> [ 15/121] Compiling daemon/face/multicast-udp-face.cpp >>> [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp >>> ../core/logger.cpp: In static member function ?static const char* >>> nfd::Logger::now()?: >>> ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is >>> incompatible with microseconds::rep >>> static_assert(std::is_same::value, >>> ^ >>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >>> ?long int?, but argument 4 has type ?boost::chrono::duration>> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>> microsecondsSinceEpoch % ONE_SECOND); >>> ^ >>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >>> ?long int?, but argument 5 has type ?boost::chrono::duration>> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >>> ?long int?, but argument 4 has type ?boost::chrono::duration>> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of type >>> ?long int?, but argument 5 has type ?boost::chrono::duration>> boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>> >>> Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' >>> Build failed >>> -> task in 'core-objects' failed (exit status 1): >>> {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} >>> ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', >>> '-fPIC', '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', >>> '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', >>> '-I/home/ndnusr1/sandbox/NFD/build/core', >>> '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', >>> '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', >>> '../core/logger.cpp', '-c', '-o', >>> '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] >>> >>> Regards, >>> /anil. >>> >>> >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sun Mar 15 15:19:34 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 15:19:34 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Junxiao, After recreating nfd.conf file, I am able to start nfd process. However, the compilation issue still exist. But I have my previously installed nfd instance for now. /anil. On Sun, Mar 15, 2015 at 3:04 PM, Anil Jangam wrote: > Compiler version is: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) > > What is "maintainer version" and how to invoke it? > > /anil. > > > On Sun, Mar 15, 2015 at 3:02 PM, Junxiao Shi > wrote: > >> Hi Anil >> >> I need to know the version of operating system and compiler, not just NFD. >> >> Also, NFD configuration file is incompatible between versions. >> Purge the old configuration and create them again. >> Choose "maintainer version" during future upgrades. >> >> Yours, Junxiao >> On Mar 15, 2015 2:56 PM, "Anil Jangam" wrote: >> >>> I am having version 0.3.1 >>> >>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfdc -V >>> 0.3.1 >>> >>> >>> /anil. >>> >>> >>> On Sun, Mar 15, 2015 at 2:47 PM, Anil Jangam >>> wrote: >>> >>>> Today, I noticed an issue with starting the NFD service. Apparently, it >>>> is crashing since the process Id it shows after nfd-start does not exist >>>> any more in process status. However, when I try to restart it again, it >>>> says, "start: Job is already running: nfd". >>>> >>>> There are multiple issues here. When I do nfd-status, it is not able to >>>> connect to the NFD. Some of the logs are attached below. >>>> >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >>>> nfd start/running, process 5942 >>>> >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ ps -ef | grep 5942 >>>> ndnusr1 5974 3772 0 14:39 pts/11 00:00:00 grep 5942 >>>> >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-start >>>> start: Job is already running: nfd >>>> >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ nfd-status >>>> ERROR: error while receiving data from socket (Connection reset by peer) >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>>> >>>> >>>> I also tried compiling a new version of the NFD from source, and was >>>> stopped by the following compilation error. Is this new or am I missing >>>> something in my environment? >>>> >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ >>>> ndnusr1 at ndnhost1:~/sandbox/NFD$ ./waf >>>> Waf: Entering directory `/home/ndnusr1/sandbox/NFD/build' >>>> [ 3/121] Compiling core/city-hash.cpp >>>> [ 5/121] Compiling core/global-io.cpp >>>> [ 6/121] Compiling core/network-interface.cpp >>>> [ 8/121] Compiling core/privilege-helper.cpp >>>> [ 9/121] Compiling core/random.cpp >>>> [ 12/121] Compiling core/logger.cpp >>>> [ 15/121] Compiling daemon/face/multicast-udp-face.cpp >>>> [ 17/121] Compiling daemon/face/ndnlp-partial-message-store.cpp >>>> ../core/logger.cpp: In static member function ?static const char* >>>> nfd::Logger::now()?: >>>> ../core/logger.cpp:61:3: error: static assertion failed: PRIdLEAST64 is >>>> incompatible with microseconds::rep >>>> static_assert(std::is_same::value, >>>> ^ >>>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of >>>> type ?long int?, but argument 4 has type ?boost::chrono::duration>>> int, boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>>> microsecondsSinceEpoch % ONE_SECOND); >>>> ^ >>>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of >>>> type ?long int?, but argument 5 has type ?boost::chrono::duration>>> int, boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of >>>> type ?long int?, but argument 4 has type ?boost::chrono::duration>>> int, boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>>> ../core/logger.cpp:67:47: warning: format ?%ld? expects argument of >>>> type ?long int?, but argument 5 has type ?boost::chrono::duration>>> int, boost::ratio<1ll, 1000000ll> >::rep {aka long long int}? [-Wformat=] >>>> >>>> Waf: Leaving directory `/home/ndnusr1/sandbox/NFD/build' >>>> Build failed >>>> -> task in 'core-objects' failed (exit status 1): >>>> {task 139803716150992: cxx logger.cpp -> logger.cpp.2.o} >>>> ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', >>>> '-fPIC', '-include', '/home/ndnusr1/sandbox/NFD/build/core-objects.2', >>>> '-I/home/ndnusr1/sandbox/NFD/build', '-I/home/ndnusr1/sandbox/NFD', >>>> '-I/home/ndnusr1/sandbox/NFD/build/core', >>>> '-I/home/ndnusr1/sandbox/NFD/core', '-I/usr/include', >>>> '-I/usr/local/include', '-DNDEBUG', '-DHAVE_NDN_CXX=1', >>>> '../core/logger.cpp', '-c', '-o', >>>> '/home/ndnusr1/sandbox/NFD/build/core/logger.cpp.2.o'] >>>> >>>> Regards, >>>> /anil. >>>> >>>> >>> >>> _______________________________________________ >>> Ndn-interest mailing list >>> Ndn-interest at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Sun Mar 15 16:15:36 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Sun, 15 Mar 2015 16:15:36 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Anil Please also provide: * operating system version * Boost version To use maintainer's NFD configuration: cd /etc/ndn cp nfd.conf.sample nfd.conf Yours, Junxiao On Mar 15, 2015 3:04 PM, "Anil Jangam" wrote: > > Compiler version is: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) > > What is "maintainer version" and how to invoke it? > > /anil. -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sun Mar 15 16:32:37 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 16:32:37 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: I already provided it. Boost library version: ndnusr1 at ndnhost1:~/sandbox/NFD$ dpkg --get-selections | grep -v deinstall | grep -i boost libboost-all-dev install libboost-atomic-dev:amd64 install libboost-atomic1.54-dev:amd64 install libboost-atomic1.54.0:amd64 install libboost-chrono-dev:amd64 install OS version: ndnusr1 at ndnhost1:~/sandbox/NFD$ uname -a Linux ndnhost1 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Ubuntu version: ndnusr1 at ndnhost1:~/sandbox/NFD$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty /anil. On Sun, Mar 15, 2015 at 4:15 PM, Junxiao Shi wrote: > Hi Anil > > Please also provide: > > * operating system version > * Boost version > > To use maintainer's NFD configuration: > > cd /etc/ndn > cp nfd.conf.sample nfd.conf > > Yours, Junxiao > > On Mar 15, 2015 3:04 PM, "Anil Jangam" wrote: > > > > Compiler version is: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) > > > > What is "maintainer version" and how to invoke it? > > > > /anil. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Sun Mar 15 16:33:34 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Mon, 16 Mar 2015 00:33:34 +0100 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: On Mon, Mar 16, 2015 at 12:15 AM, Junxiao Shi wrote: > Hi Anil > > Please also provide: > > * operating system version > * Boost version > http://www.lists.cs.ucla.edu/pipermail/ndn-interest/2015-March/000550.html From anilj.mailing at gmail.com Sun Mar 15 18:53:35 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sun, 15 Mar 2015 18:53:35 -0700 Subject: [Ndn-interest] NLSR dumping core... in nlsr::SyncLogicHandler::publishRoutingUpdate Message-ID: Hi, I have built a three node setup to test the NLSR functionality. In the neighborhood configuration, do we have to explicitly configure the port number? on Router-1 (ndnr1) the configuration is as follows. .... ; lsa-refresh-time is the time in seconds, after which router will refresh its LSAs lsa-refresh-time 240 ; default value 1800. Valid values 240-7200 .... .... hello-interval 30 ; interest sending interval in seconds. Default value 60 ; valid values 30-90 .... neighbor { name /ndn/fj/ndnhost2/%C1.Router/icn/ndnr2 ; name prefix of the neighbor router consists ; of network, site-name and router-name face-uri udp://133.164.60.158:6060 ; face uri of the face connected to the neighbor link-cost 30 ; cost of the connecting link to neighbor } neighbor { name /ndn/fj/ndnhost4/%C1.Router/icn/ndnr4 ; name prefix of the neighbor router consists ; of network, site-name and router-name face-uri udp://133.164.60.156:6060 ; face uri of the face connected to the neighbor link-cost 25 ; cost of the connecting link to neighbor } I see 8 set of INFO message exchanges (30 seconds hello interval) between all three router nodes. However at the end of 8th set, all three NLSR processes crashes at the same time!! I presume this is because something wrong happening when LSA refresh is being done (LSA refresh is 240 secs). I am not sure whats wrong, if any, in my configuration. Questions: - Do we have to configure the port number in the face-uri value? - I presume this port number must be different than the NFD port number (6363). Some of the other observations: - I do not think we have to explicitly configure the FIB by registering the prefix. I actually did it and observed that those entries are cleared from FIB at run-time. Is this a valid behavior? - I am not sure if we have to explicitly add the FACES by creating them on NFD. I actually did create them, but observed that they are removed/cleared at run-time. Is this a valid behavior? I have attached the stack trace of the core dump file for further analysis. Kindly please comment. /anil. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ndnusr1 at ndnhost1:~/sandbox/NLSR$ gdb build/bin/nlsr core GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from build/bin/nlsr...done. [New LWP 21359] [New LWP 21370] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `./build/bin/nlsr -f nlsr.conf'. Program terminated with signal SIGSEGV, Segmentation fault. #0 Sync::SyncSocket::publishData (this=0x0, prefix=..., session=session at entry=0, buf=buf at entry=0x23add48 "NoData", len=len at entry=6, freshness=freshness at entry=1000, seq=seq at entry=41781477507102) at ../nsync/sync-socket.cc:72 72 m_face->getIoService().post(bind(&SyncSocket::publishDataInternal, this, (gdb) where #0 Sync::SyncSocket::publishData (this=0x0, prefix=..., session=session at entry=0, buf=buf at entry=0x23add48 "NoData", len=len at entry=6, freshness=freshness at entry=1000, seq=seq at entry=41781477507102) at ../nsync/sync-socket.cc:72 #1 0x000000000045a3e0 in nlsr::SyncLogicHandler::publishSyncUpdate (this=0x7fff39a218a0, updatePrefix=..., seqNo=41781477507102) at ../src/communication/sync-logic-handler.cpp:278 #2 0x000000000045a5ab in nlsr::SyncLogicHandler::publishRoutingUpdate (this=) at ../src/communication/sync-logic-handler.cpp:259 #3 0x0000000000478f6f in nlsr::Lsdb::exprireOrRefreshNameLsa (this=0x7fff39a21740, lsaKey=..., seqNo=) at ../src/lsdb.cpp:654 #4 0x0000000000550772 in operator() (this=0x7fff39a20ee0) at /usr/include/c++/4.8/functional:2464 #5 ndn::util::scheduler::Scheduler::onEvent (this=0x7fff39a21310, error=...) at ../src/util/scheduler.cpp:182 #6 0x0000000000550990 in operator() (__object=, this=0x7fff39a20f90) at /usr/include/c++/4.8/functional:601 #7 __call (__args=, this=0x7fff39a20f90) at /usr/include/c++/4.8/functional:1296 #8 operator() (this=0x7fff39a20f90) at /usr/include/c++/4.8/functional:1355 #9 operator() (this=0x7fff39a20f90) at /usr/local/include/boost/asio/detail/bind_handler.hpp:46 #10 asio_handler_invoke(ndn::util::scheduler::Scheduler*, std::_Placeholder<1>)>, boost::system::error_code> > ( function=) at /usr/local/include/boost/asio/handler_invoke_hook.hpp:64 #11 invoke(ndn::util::scheduler::Scheduler*, std::_Placeholder<1>)>, boost::system::error_code>, std::_Bind(ndn::util::scheduler::Scheduler*, std::_Placeholder<1>)> > (context=..., function=...) at /usr/local/include/boost/asio/detail/handler_invoke_helpers.hpp:39 #12 boost::asio::detail::wait_handler (ndn::util::scheduler::Scheduler*, std::_Placeholder<1>)> >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long) (owner=0x2371a00, base=0x23a60a0) at /usr/local/include/boost/asio/detail/wait_handler.hpp:69 #13 0x00000000004d88bf in complete (bytes_transferred=, ec=..., owner=..., this=0x23a60a0) at /usr/local/include/boost/asio/detail/task_io_service_operation.hpp:37 #14 do_run_one (ec=..., this_thread=..., lock=..., this=0x2371a00) at /usr/local/include/boost/asio/detail/impl/task_io_service.ipp:412 #15 boost::asio::detail::task_io_service::run (this=0x2371a00, ec=...) at /usr/local/include/boost/asio/detail/impl/task_io_service.ipp:153 ---Type to continue, or q to quit--- #16 0x00000000004d4255 in run (this=0x7fff39a21260) at /usr/local/include/boost/asio/impl/io_service.ipp:59 #17 ndn::Face::processEvents (this=0x7fff39a212d0, timeout=..., keepThread=keepThread at entry=false) at ../src/face.cpp:435 #18 0x0000000000482889 in nlsr::Nlsr::startEventLoop (this=this at entry=0x7fff39a21390) at ../src/nlsr.cpp:296 #19 0x00000000004403f1 in nlsr::main (argc=3, argv=) at ../src/main.cpp:87 #20 0x00007fc678c87ec5 in __libc_start_main (main=0x4406f0 , argc=3, argv=0x7fff39a21e78, init=, fini=, rtld_fini=, stack_end=0x7fff39a21e68) at libc-start.c:287 #21 0x000000000044fd92 in _start () (gdb) From vslehman at memphis.edu Mon Mar 16 08:22:46 2015 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Mon, 16 Mar 2015 15:22:46 +0000 Subject: [Ndn-interest] NLSR dumping core... in nlsr::SyncLogicHandler::publishRoutingUpdate In-Reply-To: References: Message-ID: Hi Anil, * Do we have to configure the port number in the face-uri value? * I presume this port number must be different than the NFD port number (6363). The port number in the face-uri should be the port that the remote NFD is using. If you do not specify a port number, NLSR will use the default NFD port (6363). Some of the other observations: * I do not think we have to explicitly configure the FIB by registering the prefix. I actually did it and observed that those entries are cleared from FIB at run-time. Is this a valid behavior? * I am not sure if we have to explicitly add the FACES by creating them on NFD. I actually did create them, but observed that they are removed/cleared at run-time. Is this a valid behavior? Yes, you do not need to manually configure the FIB or add Faces, both will be done automatically by NLSR. When you added the FIB entries and created the Faces, did you do this before you ran NLSR or while it was running? NLSR should not destroy faces at runtime, but it will remove FIB entries due to connectivity changes. I will need to look into the segfault issue as it seems to be an problem with the sync protocol publishing empty data. -- Vince Lehman On Mar 15, 2015, at 8:53 PM, Anil Jangam > wrote: * Do we have to configure the port number in the face-uri value? * I presume this port number must be different than the NFD port number (6363). Some of the other observations: * I do not think we have to explicitly configure the FIB by registering the prefix. I actually did it and observed that those entries are cleared from FIB at run-time. Is this a valid behavior? * I am not sure if we have to explicitly add the FACES by creating them on NFD. I actually did create them, but observed that they are removed/cleared at run-time. Is this a valid behavior? -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Mon Mar 16 16:58:14 2015 From: anilj.mailing at gmail.com (Anil Jangam) Date: Mon, 16 Mar 2015 16:58:14 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Junxiao, Is this (compilation failure) a valid issue? /anil. On Sun, Mar 15, 2015 at 4:15 PM, Junxiao Shi wrote: > Hi Anil > > Please also provide: > > * operating system version > * Boost version > > To use maintainer's NFD configuration: > > cd /etc/ndn > cp nfd.conf.sample nfd.conf > > Yours, Junxiao > > On Mar 15, 2015 3:04 PM, "Anil Jangam" wrote: > > > > Compiler version is: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) > > > > What is "maintainer version" and how to invoke it? > > > > /anil. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Mar 16 22:41:33 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 16 Mar 2015 22:41:33 -0700 Subject: [Ndn-interest] NFD Issues. In-Reply-To: References: Message-ID: Hi Anil Your report seems valid. I have entered this Bug to Redmine: http://redmine.named-data.net/issues/2651 Please watch this issue on Redmine, and promptly reply to posted questions. Yours, Junxiao On Mon, Mar 16, 2015 at 4:58 PM, Anil Jangam wrote: > Hi Junxiao, > > Is this (compilation failure) a valid issue? > > /anil. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jefft0 at remap.UCLA.EDU Tue Mar 17 12:29:45 2015 From: jefft0 at remap.UCLA.EDU (Thompson, Jeff) Date: Tue, 17 Mar 2015 19:29:45 +0000 Subject: [Ndn-interest] Adding HMAC to available NDN signature types In-Reply-To: References: <7BB03D9C-A407-444F-A07E-4EB2370DF504@cs.ucla.edu> <6F30B27A-8E53-4B36-9557-E07D16A57EBE@cs.ucla.edu> Message-ID: I submitted a pull request for adding SignatureHmacWithSha256 https://github.com/named-data/NDN-TLV/pull/1 For convenience, the text is below. I am especially interest in feedback on the languages about provenance: "Provided that the signature verifies, this type of signature ensures provenance that the Data packet was signed by one of the parties which holds the shared Key. The key is identified using a KeyDigest as described above. It is the application?s responsibility to establish the identities of the parties who hold the shared Key." - Jeff T SignatureHmacWithSha256 SignatureHmacWithSha256 defines a hash-based message authentication code that is calculated over the Name, MetaInfo, Content, and SignatureInfo TLVs, using SHA256 as the hashing function. The signature algorithm is defined in Section 2 in RFC 2104. SignatureInfo ::= SIGNATURE-INFO-TYPE TLV-LENGTH SIGNATURE-TYPE-TYPE TLV-LENGTH(=1) 4 KeyLocator SignatureValue ::= SIGNATURE-VALUE-TYPE TLV-LENGTH(=32) BYTE++(=SHA256({KeyValue XOR opad, SHA256({KeyValue XOR ipad, Name, MetaInfo, Content, SignatureInfo})})) where opad = 0x5c5c5c...5c5c5c (repeated 64 times) ipad = 0x363636...363636 (repeated 64 times) Key is a shared key known to the sender and receiver of the signed packet. KeyValue is derived from a shared Key as follows. If the byte length of Key is less than the SHA256 block length (64 bytes) then append zeros to the end of the Key to create the 64-byte KeyValue. If the byte length of Key is greater than 64 bytes then hash it with SHA256 to produce a 32-byte value then append 32 zeros to the end to create the 64-byte KeyValue. (The HMAC functions in most cryptographic libraries are supplied the Key and will internally derive the KeyValue in this way.) Note Key is not included in the signature. It is the application?s responsibility to ensure that the receiver already knows the shared Key. It can be identified using a KeyDigest as the KeyLocator block in the SignatureInfo block of SignatureHmacWithSha256 as follows. If the byte length of Key is less than or equal to the SHA256 block length (64 bytes) then the KeyDigest is SHA256(Key). But if the byte length of Key is greater than 64 bytes, the KeyValue is already SHA256(Key) with zeros appended, so in this case KeyDigest is SHA256(SHA256(Key)). Note As stated in in Section 3 of RFC 2104 , keys shorter than the SHA256 output byte length (32 bytes) are strongly discouraged. Provided that the signature verifies, this type of signature ensures provenance that the Data packet was signed by one of the parties which holds the shared Key. The key is identified using a KeyDigest as described above. It is the application?s responsibility to establish the identities of the parties who hold the shared Key. From: , Jeff Thompson > Date: Monday, March 9, 2015 at 6:07 To: Yingdi Yu > Cc: "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Adding HMAC to available NDN signature types Hi Yingdi, Following up to your message (6 months ago): > Moreover, how to definition of KeyDigest is important in the validation part, so that data consumers can determine which symmetric key should be used to verify the HMAC. I agree with Marc that, for key longer than the block size, we can use the digest of digest of the key as the key id because the digest of the key is the actual key in this case. Agreed for KeyDigest. The KeyLocator can also a key Name but normally a key Name is used to fetch a certificate which has more info. But there is not certificate for HMAC so would you agree that we only describe a KeyDigest for the KeyLocator? Thanks, - Jeff T From: Yingdi Yu > Date: Tuesday, September 23, 2014 at 9:51 To: Jeff Thompson > Cc: Adeola Bannis >, "ndn-interest at lists.cs.ucla.edu" > Subject: Re: [Ndn-interest] Adding HMAC to available NDN signature types Hi Jeff, On Sep 22, 2014, at 10:02 AM, Thompson, Jeff > wrote: Hash output length vs. block size? Marc is right. The HmacWithSha256 algorithm hashes the key when it is longer than the block size (64 bytes), not the hash output length (32 bytes). So we would prohibit keys longer than 64 bytes (not 32 bytes). In Adeola's spec, the block size is not required to be 64 bytes. The RFC does not require the block size to be 64. I wonder if we should clarify that in the spec? Also, most applications will use a crypto library's HMAC function which should automatically hash the key if it is longer than the block size. It could be confusing to put this in the spec since the application writer may unnecessarily has the key when the crypto library will do it anyway, and more efficiently. I think the purpose of this spec is not only for application developers, but also for library developers, especially if we want to have good interoperability. So I think it would be better to clearly specify what is the requirement of generating a signature, how to generate a signature and what should be put into the SignatureInfo. Moreover, how to definition of KeyDigest is important in the validation part, so that data consumers can determine which symmetric key should be used to verify the HMAC. I agree with Marc that, for key longer than the block size, we can use the digest of digest of the key as the key id because the digest of the key is the actual key in this case. Yingdi -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Thu Mar 19 09:10:08 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Thu, 19 Mar 2015 19:40:08 +0330 Subject: [Ndn-interest] Disabling NDN's in-network caching Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2946@m-pdc.sbu.ac.ir> Hi, In "A case for stateful forwarding plane", in the simulation part it said "Since we focus out evaluation on the effectiveness of stageful adaptive forwarding, we disabled NDN's in-network caching in the simulation." The question is: Is it possible to disable in-network caching in real NFD? Thanks, Sabet -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Thu Mar 19 09:33:44 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Thu, 19 Mar 2015 09:33:44 -0700 Subject: [Ndn-interest] Disabling NDN's in-network caching In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2946@m-pdc.sbu.ac.ir> References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2946@m-pdc.sbu.ac.ir> Message-ID: Hi Muhammad Yes, you may disable in-network caching by *setting ContentStore capacity to zero*. The relevant configuration option is tables.cs_max_packets in /usr/local/etc/ndn/nfd.conf. However, this is an *unsupported configuration*. In particular, - StatusDataset and Notification in NFD Management won't work before # 2182 , which implies nfd-status won't work. - Remote prefix registration won't work before #1529 . There could be other limitations as well. Yours, Junxiao On Thu, Mar 19, 2015 at 9:10 AM, Muhammad Hosain Abdollahi Sabet < M.AbdollahiSabet at mail.sbu.ac.ir> wrote: > Hi, > In "A case for stateful forwarding plane", in the simulation part it said > "Since we focus out evaluation on the effectiveness of stageful adaptive > forwarding, we disabled NDN's in-network caching in the simulation." The > question is: Is it possible to disable in-network caching in real NFD? > > Thanks, > Sabet > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Thu Mar 19 09:52:48 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Thu, 19 Mar 2015 20:22:48 +0330 Subject: [Ndn-interest] Disabling NDN's in-network caching References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2946@m-pdc.sbu.ac.ir> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2947@m-pdc.sbu.ac.ir> Hmmm. By setting the capacity to zero, the logic would be the same. I mean, still there would be a ContentStore checking in the process which is not needed then, right? Thanks, Sabet -----Original Message----- From: Junxiao Shi [mailto:shijunxiao at email.arizona.edu] Sent: Thu 3/19/2015 8:03 PM To: Muhammad Hosain Abdollahi Sabet Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Disabling NDN's in-network caching Hi Muhammad Yes, you may disable in-network caching by *setting ContentStore capacity to zero*. The relevant configuration option is tables.cs_max_packets in /usr/local/etc/ndn/nfd.conf. However, this is an *unsupported configuration*. In particular, - StatusDataset and Notification in NFD Management won't work before # 2182 , which implies nfd-status won't work. - Remote prefix registration won't work before #1529 . There could be other limitations as well. Yours, Junxiao On Thu, Mar 19, 2015 at 9:10 AM, Muhammad Hosain Abdollahi Sabet < M.AbdollahiSabet at mail.sbu.ac.ir> wrote: > Hi, > In "A case for stateful forwarding plane", in the simulation part it said > "Since we focus out evaluation on the effectiveness of stageful adaptive > forwarding, we disabled NDN's in-network caching in the simulation." The > question is: Is it possible to disable in-network caching in real NFD? > > Thanks, > Sabet > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Thu Mar 19 09:58:15 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Thu, 19 Mar 2015 09:58:15 -0700 Subject: [Ndn-interest] Disabling NDN's in-network caching In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2947@m-pdc.sbu.ac.ir> References: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2946@m-pdc.sbu.ac.ir> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2947@m-pdc.sbu.ac.ir> Message-ID: Hi Muhammad Yes, logic remains the same. ContentStore lookup and insertion will still happen, but insertion should be a no-op because every inserted CS entry is immediately evicted. Yours, Junxiao On Thu, Mar 19, 2015 at 9:52 AM, Muhammad Hosain Abdollahi Sabet < M.AbdollahiSabet at mail.sbu.ac.ir> wrote: > Hmmm. By setting the capacity to zero, the logic would be the same. I > mean, still there would be a ContentStore checking in the process which is > not needed then, right? > > Thanks, > Sabet > > -----Original Message----- > From: Junxiao Shi [mailto:shijunxiao at email.arizona.edu > ] > Sent: Thu 3/19/2015 8:03 PM > To: Muhammad Hosain Abdollahi Sabet > Cc: ndn-interest at lists.cs.ucla.edu > Subject: Re: [Ndn-interest] Disabling NDN's in-network caching > > Hi Muhammad > > Yes, you may disable in-network caching by *setting ContentStore capacity > to zero*. > The relevant configuration option is tables.cs_max_packets in > /usr/local/etc/ndn/nfd.conf. > > However, this is an *unsupported configuration*. > In particular, > > - StatusDataset and Notification in NFD Management won't work before # > 2182 , which implies > nfd-status won't work. > - Remote prefix registration won't work before #1529 > . > > There could be other limitations as well. > > Yours, Junxiao > > On Thu, Mar 19, 2015 at 9:10 AM, Muhammad Hosain Abdollahi Sabet < > M.AbdollahiSabet at mail.sbu.ac.ir> wrote: > > > Hi, > > In "A case for stateful forwarding plane", in the simulation part it said > > "Since we focus out evaluation on the effectiveness of stageful adaptive > > forwarding, we disabled NDN's in-network caching in the simulation." The > > question is: Is it possible to disable in-network caching in real NFD? > > > > Thanks, > > Sabet > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.edu Fri Mar 20 07:06:45 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Fri, 20 Mar 2015 14:06:45 +0000 Subject: [Ndn-interest] NLSR and ndn-cxx : Compiler version? Message-ID: <672FB5D5-B53F-4B8D-AB48-B8CC706548A2@umass.edu> Hi, I am trying to configure the NLSR routing tool at https://github.com/named-data/NLSR for a Ubuntu 12.04 machine. However, I am running into compiler version problems while doing so. I upgraded to gcc-4.8 g++4.8 and was able to get rid of some errors such as ?std=c++11 not found? but I still have an error that says: ?g++: error: unrecognized command line option ?-stdlib=libc++?? . As far as I understand NLSR depends on nan-cxx which I obtained from https://github.com/named-data/ndn-cxx. What is the correct procedure for configuring and building NLSR? Thanks. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst From shijunxiao at email.arizona.edu Fri Mar 20 07:18:04 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Fri, 20 Mar 2015 07:18:04 -0700 Subject: [Ndn-interest] NLSR and ndn-cxx : Compiler version? In-Reply-To: <672FB5D5-B53F-4B8D-AB48-B8CC706548A2@umass.edu> References: <672FB5D5-B53F-4B8D-AB48-B8CC706548A2@umass.edu> Message-ID: Hi Divyashri Bug 2209 has a similar error message. Does the system happen to have clang? If yes, uninstall clang and try again. Otherwise, please post: * which project has build errors, ndn-cxx or NLSR? * the exact waf configure line you used * the complete output of configure step * the contents of build/config.log * the complete output of `./waf -v` Yours, Junxiao On Mar 20, 2015 7:10 AM, "Divyashri Bhat" wrote: > Hi, > > I am trying to configure the NLSR routing tool at > https://github.com/named-data/NLSR for a Ubuntu 12.04 machine. However, I > am running into compiler version problems while doing so. I upgraded to > gcc-4.8 g++4.8 and was able to get rid of some errors such as ?std=c++11 > not found? but I still have an error that says: ?g++: error: unrecognized > command line option ?-stdlib=libc++?? . > > As far as I understand NLSR depends on nan-cxx which I obtained from > https://github.com/named-data/ndn-cxx. > > What is the correct procedure for configuring and building NLSR? > > Thanks. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Fri Mar 20 07:49:01 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Fri, 20 Mar 2015 15:49:01 +0100 Subject: [Ndn-interest] NLSR and ndn-cxx : Compiler version? In-Reply-To: References: <672FB5D5-B53F-4B8D-AB48-B8CC706548A2@umass.edu> Message-ID: Hi Divya, Yes, part of the problem is outlined in bug #2209, after note-8. We should have reverted the commit as I requested in note-12. This case is slightly different however. I'm assuming you are exporting CXX=/path/to/g++4.8 to the environment, and that confuses the logic that waf uses for compiler detection. In any case, Ubuntu 12.04 is a supported platform, therefore I'm wondering why you had to upgrade the compiler. That shouldn't have been necessary. What error did you get with the stock compiler (which should be gcc-4.6)? Thanks, Davide On Fri, Mar 20, 2015 at 3:18 PM, Junxiao Shi wrote: > Hi Divyashri > > Bug 2209 has a similar error > message. Does the system happen to have clang? If yes, uninstall clang and > try again. > > Otherwise, please post: > > * which project has build errors, ndn-cxx or NLSR? > * the exact waf configure line you used > * the complete output of configure step > * the contents of build/config.log > * the complete output of `./waf -v` > > Yours, Junxiao > > On Mar 20, 2015 7:10 AM, "Divyashri Bhat" wrote: >> >> Hi, >> >> I am trying to configure the NLSR routing tool at >> https://github.com/named-data/NLSR for a Ubuntu 12.04 machine. However, I am >> running into compiler version problems while doing so. I upgraded to gcc-4.8 >> g++4.8 and was able to get rid of some errors such as ?std=c++11 not found? >> but I still have an error that says: ?g++: error: unrecognized command line >> option ?-stdlib=libc++?? . >> >> As far as I understand NLSR depends on nan-cxx which I obtained from >> https://github.com/named-data/ndn-cxx. >> >> What is the correct procedure for configuring and building NLSR? >> >> Thanks. >> Regards, >> Divyashri Bhat >> dbhat at umass.edu >> Graduate Student >> Department of Electrical and Computer Engineering, >> University of Massachusetts, Amherst >> >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From dbhat at umass.edu Fri Mar 20 12:30:09 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Fri, 20 Mar 2015 19:30:09 +0000 Subject: [Ndn-interest] NLSR and ndn-cxx : Compiler version? In-Reply-To: References: <672FB5D5-B53F-4B8D-AB48-B8CC706548A2@umass.edu> Message-ID: Hi Davide, Junxiao, Thank you for getting back to me so quickly! I tried installing ndn-cxx, NFD and NLSR on a new VM and this time it was successful. On my previous installation I wrongly assumed I had to update the gcc because of an error message I saw in build/config.log of NLSR that said something like "g++: error: unrecognized command line option ?-std=c++11?? The problem is now solved with a fresh installation. Turns out I did not have to update the gcc after all! Thanks! Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst > On 20 Mar 2015, at 10:49, Davide Pesavento wrote: > > Hi Divya, > > Yes, part of the problem is outlined in bug #2209, after note-8. We > should have reverted the commit as I requested in note-12. > > This case is slightly different however. I'm assuming you are > exporting CXX=/path/to/g++4.8 to the environment, and that confuses > the logic that waf uses for compiler detection. > > In any case, Ubuntu 12.04 is a supported platform, therefore I'm > wondering why you had to upgrade the compiler. That shouldn't have > been necessary. What error did you get with the stock compiler (which > should be gcc-4.6)? > > Thanks, > Davide > > On Fri, Mar 20, 2015 at 3:18 PM, Junxiao Shi > wrote: >> Hi Divyashri >> >> Bug 2209 has a similar error >> message. Does the system happen to have clang? If yes, uninstall clang and >> try again. >> >> Otherwise, please post: >> >> * which project has build errors, ndn-cxx or NLSR? >> * the exact waf configure line you used >> * the complete output of configure step >> * the contents of build/config.log >> * the complete output of `./waf -v` >> >> Yours, Junxiao >> >> On Mar 20, 2015 7:10 AM, "Divyashri Bhat" wrote: >>> >>> Hi, >>> >>> I am trying to configure the NLSR routing tool at >>> https://github.com/named-data/NLSR for a Ubuntu 12.04 machine. However, I am >>> running into compiler version problems while doing so. I upgraded to gcc-4.8 >>> g++4.8 and was able to get rid of some errors such as ?std=c++11 not found? >>> but I still have an error that says: ?g++: error: unrecognized command line >>> option ?-stdlib=libc++?? . >>> >>> As far as I understand NLSR depends on nan-cxx which I obtained from >>> https://github.com/named-data/ndn-cxx. >>> >>> What is the correct procedure for configuring and building NLSR? >>> >>> Thanks. >>> Regards, >>> Divyashri Bhat >>> dbhat at umass.edu >>> Graduate Student >>> Department of Electrical and Computer Engineering, >>> University of Massachusetts, Amherst >>> >>> >>> _______________________________________________ >>> Ndn-interest mailing list >>> Ndn-interest at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> >> >> _______________________________________________ >> Ndn-interest mailing list >> Ndn-interest at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >> From tailinchu at gmail.com Sat Mar 28 19:39:52 2015 From: tailinchu at gmail.com (Tai-Lin Chu) Date: Sat, 28 Mar 2015 19:39:52 -0700 Subject: [Ndn-interest] go-ndn milestone 4 Message-ID: Dear all, It has been more than half a year since the last release. This release focuses on overall code quality and performance improvements. As a result, packet encoding/decoding speed has improved at least 100%, and go-nfd forwarding speed has improved at least 40%. https://github.com/go-ndn/ndn changelog: * all: reduce most small memory allocations * all: increase test coverage to at least 70% in most packages * tlv: finally remove bufio dependency in package decode * tlv: use low-level binary.ByteOrder interface{} * tlv: support encoding.BinaryMarshaler/BinaryUnmarshaler for special field like ndn.Exclude * ndn: remove ndn.SignKey as an exported variable * ndn: explicitly sign packets * lpm: add lock-less implementation * ndn-cert-gen: add ecdsa key and self-sign cert generation Cheers! From dbhat at umass.edu Sat Mar 28 22:43:02 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Sun, 29 Mar 2015 05:43:02 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? Message-ID: Hi, I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: 1) Does this work over Ethernet? If yes, is the source code available? 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Thank you. [1] http://www.named-data.net/techreport/TR007-streaming.pdf [2] https://github.com/remap/ndnvideo Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst From jburke at remap.UCLA.EDU Sun Mar 29 00:30:52 2015 From: jburke at remap.UCLA.EDU (Burke, Jeff) Date: Sun, 29 Mar 2015 07:30:52 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: Message-ID: On 3/28/15, 10:43 PM, "Divyashri Bhat" wrote: >Hi, > >I came across a technical report a few years ago that describes a working >implementation of Video Streaming over Information Centric Networks using >CCNx [1]. This report also mentions video streaming over Ethernet. I have >two questions: > >1) Does this work over Ethernet? If yes, is the source code available? The application works over NDN (specifically, NDNx - https://github.com/named-data/ndnx/). If the underlying daemon supports Ethernet, than the application should work over Ethernet. Some proof-of-concept tests over Ethernet were done using NDNLP, I believe, but I don't remember the details. https://github.com/named-data/NDNLP >2) The implementation at the Github link [2] appears to be over CCNx and >as far as I understand Ethernet faces don?t work well over CCNx. Is there >a plan to port this to NDN? There is no immediate plan to port NDNVideo to the current NDN platform. However, there is the ndnrtc project - https://github.com/remap/ndnrtc / https://github.com/peetonn/ndncon - as well as some other video projects (e.g., https://github.com/iliamo/video-prototype) that others can speak to. These, should, I suppose, work over ethernet in NFD using its now internal version of NDNLP. http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV. I am not sure of the status of this support, but others in this list should be. If you are able to get them to work over Ethernet, I'd love to hear about it. Jeff > >Thank you. > >[1] http://www.named-data.net/techreport/TR007-streaming.pdf >[2] https://github.com/remap/ndnvideo >Regards, >Divyashri Bhat >dbhat at umass.edu >Graduate Student >Department of Electrical and Computer Engineering, >University of Massachusetts, Amherst > > >_______________________________________________ >Ndn-interest mailing list >Ndn-interest at lists.cs.ucla.edu >http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From davide.pesavento at lip6.fr Sun Mar 29 07:16:00 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Sun, 29 Mar 2015 16:16:00 +0200 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: On Sun, Mar 29, 2015 at 9:30 AM, Burke, Jeff wrote: > > > On 3/28/15, 10:43 PM, "Divyashri Bhat" wrote: > >>2) The implementation at the Github link [2] appears to be over CCNx and >>as far as I understand Ethernet faces don?t work well over CCNx. Is there >>a plan to port this to NDN? > > There is no immediate plan to port NDNVideo to the current NDN platform. > However, there is the ndnrtc project - https://github.com/remap/ndnrtc / > https://github.com/peetonn/ndncon - as well as some other video projects > (e.g., https://github.com/iliamo/video-prototype) that others can speak > to. These, should, I suppose, work over ethernet in NFD using its now > internal version of NDNLP. > http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV. I am not sure > of the status of this support, but others in this list should be. If you > are able to get them to work over Ethernet, I'd love to hear about it. > Ethernet support is expected to work well in NFD >= 0.3.0. This includes fragmentation/reassembly using NDNLP and jumbo frames support. If you encounter any unexpected behavior it could be a bug, and you should report it on NFD redmine at http://redmine.named-data.net/projects/nfd/issues/new . Thanks, Davide From dbhat at umass.EDU Sun Mar 29 07:53:51 2015 From: dbhat at umass.EDU (Divyashri Bhat) Date: Sun, 29 Mar 2015 14:53:51 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: <9AA3F411-DB00-438F-AC12-AA61A593FE6C@umass.edu> Jeff, Thank you for the information. This is great news. I will get started with the existing projects and let you know where I get from there. Davide, Thank you. I have used NDNLP with NFD and can say that it worked great on the two Ubuntu 12.04 VMs I used. Zhehao was kind enough to fix the bugs in NDNFS application for Ethernet support. Since I am trying to set this up on a network, I looked for routing protocols and found NLSR [3] which is great to get me started. 1) Are there any others that I may have missed? 2) What is the general experience of using NLSR over Ethernet? [3] https://github.com/named-data/NLSR Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 29 Mar 2015, at 10:16, Davide Pesavento > wrote: On Sun, Mar 29, 2015 at 9:30 AM, Burke, Jeff > wrote: On 3/28/15, 10:43 PM, "Divyashri Bhat" > wrote: 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? There is no immediate plan to port NDNVideo to the current NDN platform. However, there is the ndnrtc project - https://github.com/remap/ndnrtc / https://github.com/peetonn/ndncon - as well as some other video projects (e.g., https://github.com/iliamo/video-prototype) that others can speak to. These, should, I suppose, work over ethernet in NFD using its now internal version of NDNLP. http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV. I am not sure of the status of this support, but others in this list should be. If you are able to get them to work over Ethernet, I'd love to hear about it. Ethernet support is expected to work well in NFD >= 0.3.0. This includes fragmentation/reassembly using NDNLP and jumbo frames support. If you encounter any unexpected behavior it could be a bug, and you should report it on NFD redmine at http://redmine.named-data.net/projects/nfd/issues/new . Thanks, Davide From M.AbdollahiSabet at mail.sbu.ac.ir Sun Mar 29 10:20:21 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Sun, 29 Mar 2015 21:50:21 +0430 Subject: [Ndn-interest] NDNVideo: Available over NFD? References: <9AA3F411-DB00-438F-AC12-AA61A593FE6C@umass.edu> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2948@m-pdc.sbu.ac.ir> Is NDN supposed to have/support fragmentation at all? I mean, recently I saw some presentation slides for icnrg presented by Alex(I guess), in which said fragmentation, if necessary, will be done on the hosts(endpoints). Thanks, ?? Sabet -----Original Message----- From: Ndn-interest on behalf of Divyashri Bhat Sent: Sun 3/29/2015 7:23 PM To: Davide Pesavento Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] NDNVideo: Available over NFD? Jeff, Thank you for the information. This is great news. I will get started with the existing projects and let you know where I get from there. Davide, Thank you. I have used NDNLP with NFD and can say that it worked great on the two Ubuntu 12.04 VMs I used. Zhehao was kind enough to fix the bugs in NDNFS application for Ethernet support. Since I am trying to set this up on a network, I looked for routing protocols and found NLSR [3] which is great to get me started. 1) Are there any others that I may have missed? 2) What is the general experience of using NLSR over Ethernet? [3] https://github.com/named-data/NLSR Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 29 Mar 2015, at 10:16, Davide Pesavento > wrote: On Sun, Mar 29, 2015 at 9:30 AM, Burke, Jeff > wrote: On 3/28/15, 10:43 PM, "Divyashri Bhat" > wrote: 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? There is no immediate plan to port NDNVideo to the current NDN platform. However, there is the ndnrtc project - https://github.com/remap/ndnrtc / https://github.com/peetonn/ndncon - as well as some other video projects (e.g., https://github.com/iliamo/video-prototype) that others can speak to. These, should, I suppose, work over ethernet in NFD using its now internal version of NDNLP. http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV. I am not sure of the status of this support, but others in this list should be. If you are able to get them to work over Ethernet, I'd love to hear about it. Ethernet support is expected to work well in NFD >= 0.3.0. This includes fragmentation/reassembly using NDNLP and jumbo frames support. If you encounter any unexpected behavior it could be a bug, and you should report it on NFD redmine at http://redmine.named-data.net/projects/nfd/issues/new . Thanks, Davide _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From lixia at CS.UCLA.EDU Sun Mar 29 10:59:32 2015 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Sun, 29 Mar 2015 10:59:32 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> > On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: > > Hi, > > I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: > > 1) Does this work over Ethernet? If yes, is the source code available? > 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Jeff already mentioned about ndnrtc effort. Another project has re-implemented NDNvideo using a new API. The video is done by Lijing Wang. The new API is Ilya's thesis work. As I heard last Friday, they have been running testing over NDN testbed. I copied both of them on this reply, hoping they could help offer more details. Lixia From lixia at CS.UCLA.EDU Sun Mar 29 11:05:09 2015 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Sun, 29 Mar 2015 11:05:09 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2948@m-pdc.sbu.ac.ir> References: <9AA3F411-DB00-438F-AC12-AA61A593FE6C@umass.edu> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2948@m-pdc.sbu.ac.ir> Message-ID: > On Mar 29, 2015, at 10:20 AM, Muhammad Hosain Abdollahi Sabet wrote: > > Is NDN supposed to have/support fragmentation at all? I mean, recently I saw some presentation slides for icnrg presented by Alex(I guess), in which said fragmentation, if necessary, will be done on the hosts(endpoints). I believe you are referring to the following presentation: http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-15.pdf It says clearly that, if necessary, NDN network performs packet fragmentation on a hop-by-hop basis (definitely not by ?endpoints? ? when a consumer retrieves some specific data, they may come from anywhere) Lixia -------------- next part -------------- An HTML attachment was scrubbed... URL: From ooofreedom at gmail.com Sun Mar 29 12:04:40 2015 From: ooofreedom at gmail.com (Lijing) Date: Sun, 29 Mar 2015 12:04:40 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> Message-ID: <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> Hi, Divyashri Now we have a very prototype testing over NDN testbed. About this project you can find more details here, https://github.com/PhdLoLi/VideoFile . If you have any other question, please don?t hesitate to ask me. Lijing > On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: > > >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: >> >> Hi, >> >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >> >> 1) Does this work over Ethernet? If yes, is the source code available? >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia > -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.AbdollahiSabet at mail.sbu.ac.ir Sun Mar 29 13:20:01 2015 From: M.AbdollahiSabet at mail.sbu.ac.ir (Muhammad Hosain Abdollahi Sabet) Date: Mon, 30 Mar 2015 00:50:01 +0430 Subject: [Ndn-interest] NDNVideo: Available over NFD? References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> Message-ID: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> I believe you are referring to the following presentation: http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-15.pdf It says clearly that, if necessary, NDN network performs packet fragmentation on a hop-by-hop basis (definitely not by ?endpoints? ? when a consumer retrieves some specific data, they may come from anywhere) -------------------------------------------------------------------------------- That?s the exact file I referred to. You?re right. It?s mentioned hop-by-hop fragmentation. But after counting its issues, in the conclusion part (last page) it says (I?m quoting): ?Host by host fragmentation is the only option for NDN? Maybe there is something attached to this file which I haven?t seen it yet. But for the time being I see some differences between p7, 8 and p9 which I don't understand. Do we consider intermediate nodes (e.g. routers) host here? I don?t think so. Really sorry if I?m disturbing Divyashri?s question. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Lijing Sent: Sun 3/29/2015 11:34 PM To: Lixia Zhang Cc: Ilya W Moiseenko; Ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] NDNVideo: Available over NFD? Hi, Divyashri Now we have a very prototype testing over NDN testbed. About this project you can find more details here, https://github.com/PhdLoLi/VideoFile . If you have any other question, please don't hesitate to ask me. Lijing > On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: > > >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: >> >> Hi, >> >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >> >> 1) Does this work over Ethernet? If yes, is the source code available? >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don't work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.edu Sun Mar 29 13:29:27 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Sun, 29 Mar 2015 20:29:27 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> Message-ID: Lijing, Thank you for the link. I am in the process of installing it now. Sabet, Thank you for the insight. I am also looking at routing and have been using NDNLP a little bit. Your comments are very useful to me. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 29 Mar 2015, at 16:20, Muhammad Hosain Abdollahi Sabet > wrote: I believe you are referring to the following presentation: http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-15.pdf It says clearly that, if necessary, NDN network performs packet fragmentation on a hop-by-hop basis (definitely not by ?endpoints? ? when a consumer retrieves some specific data, they may come from anywhere) -------------------------------------------------------------------------------- That?s the exact file I referred to. You?re right. It?s mentioned hop-by-hop fragmentation. But after counting its issues, in the conclusion part (last page) it says (I?m quoting): ?Host by host fragmentation is the only option for NDN? Maybe there is something attached to this file which I haven?t seen it yet. But for the time being I see some differences between p7, 8 and p9 which I don't understand. Do we consider intermediate nodes (e.g. routers) host here? I don?t think so. Really sorry if I?m disturbing Divyashri?s question. Thanks, Sabet -----Original Message----- From: Ndn-interest on behalf of Lijing Sent: Sun 3/29/2015 11:34 PM To: Lixia Zhang Cc: Ilya W Moiseenko; Ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] NDNVideo: Available over NFD? Hi, Divyashri Now we have a very prototype testing over NDN testbed. About this project you can find more details here, https://github.com/PhdLoLi/VideoFile . If you have any other question, please don't hesitate to ask me. Lijing > On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: > > >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: >> >> Hi, >> >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >> >> 1) Does this work over Ethernet? If yes, is the source code available? >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don't work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia > _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From lanwang at memphis.edu Sun Mar 29 13:45:00 2015 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Sun, 29 Mar 2015 20:45:00 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <9AA3F411-DB00-438F-AC12-AA61A593FE6C@umass.edu> References: <9AA3F411-DB00-438F-AC12-AA61A593FE6C@umass.edu> Message-ID: <7BB11C1E-DD4F-4F17-8B17-9DAF4CBDF8B4@memphis.edu> On Mar 29, 2015, at 9:53 AM, Divyashri Bhat wrote: > Jeff, > > Thank you for the information. This is great news. I will get started with the existing projects and let you know where I get from there. > > > Davide, > > Thank you. I have used NDNLP with NFD and can say that it worked great on the two Ubuntu 12.04 VMs I used. Zhehao was kind enough to fix the bugs in NDNFS application for Ethernet support. > > > Since I am trying to set this up on a network, I looked for routing protocols and found NLSR [3] which is great to get me started. > 1) Are there any others that I may have missed? > 2) What is the general experience of using NLSR over Ethernet? NLSR works over point-to-point links right now. Ethernet support is on our todo list. Lan > > [3] https://github.com/named-data/NLSR > > > Thank you. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > On 29 Mar 2015, at 10:16, Davide Pesavento > wrote: > > On Sun, Mar 29, 2015 at 9:30 AM, Burke, Jeff > wrote: > > > On 3/28/15, 10:43 PM, "Divyashri Bhat" > wrote: > > 2) The implementation at the Github link [2] appears to be over CCNx and > as far as I understand Ethernet faces don?t work well over CCNx. Is there > a plan to port this to NDN? > > There is no immediate plan to port NDNVideo to the current NDN platform. > However, there is the ndnrtc project - https://github.com/remap/ndnrtc / > https://github.com/peetonn/ndncon - as well as some other video projects > (e.g., https://github.com/iliamo/video-prototype) that others can speak > to. These, should, I suppose, work over ethernet in NFD using its now > internal version of NDNLP. > http://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV. I am not sure > of the status of this support, but others in this list should be. If you > are able to get them to work over Ethernet, I'd love to hear about it. > > > Ethernet support is expected to work well in NFD >= 0.3.0. This > includes fragmentation/reassembly using NDNLP and jumbo frames > support. If you encounter any unexpected behavior it could be a bug, > and you should report it on NFD redmine at > http://redmine.named-data.net/projects/nfd/issues/new . > > Thanks, > Davide > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From lixia at CS.UCLA.EDU Sun Mar 29 16:02:55 2015 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Sun, 29 Mar 2015 16:02:55 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> Message-ID: > On Mar 29, 2015, at 1:20 PM, Muhammad Hosain Abdollahi Sabet wrote: > > > I believe you are referring to the following presentation: > http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-15.pdf > > It says clearly that, if necessary, NDN network performs packet fragmentation on a hop-by-hop basis (definitely not by ?endpoints? ? when a consumer retrieves some specific data, they may come from anywhere) > -------------------------------------------------------------------------------- > > That?s the exact file I referred to. You?re right. It?s mentioned hop-by-hop fragmentation. But after counting its issues, in the conclusion part (last page) it says (I?m quoting): > ?Host by host fragmentation is the only option for NDN? > maybe a typo? that ought to be/really means ?hop-by-hop fragmentation and reassembly" > Maybe there is something attached to this file which I haven?t seen it yet. But for the time being I see some differences between p7, 8 and p9 which I don't understand. Do we consider intermediate nodes (e.g. routers) host here? I don?t think so. > > Really sorry if I?m disturbing Divyashri?s question. > > Thanks, > Sabet > > > > -----Original Message----- > From: Ndn-interest on behalf of Lijing > Sent: Sun 3/29/2015 11:34 PM > To: Lixia Zhang > Cc: Ilya W Moiseenko; Ndn-interest at lists.cs.ucla.edu > Subject: Re: [Ndn-interest] NDNVideo: Available over NFD? > > Hi, Divyashri > Now we have a very prototype testing over NDN testbed. > About this project you can find more details here, https://github.com/PhdLoLi/VideoFile >. > If you have any other question, please don't hesitate to ask me. > > Lijing > > > On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: > > > > > >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: > >> > >> Hi, > >> > >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: > >> > >> 1) Does this work over Ethernet? If yes, is the source code available? > >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don't work well over CCNx. Is there a plan to port this to NDN? > > > > Jeff already mentioned about ndnrtc effort. > > > > Another project has re-implemented NDNvideo using a new API. > > The video is done by Lijing Wang. > > The new API is Ilya's thesis work. > > As I heard last Friday, they have been running testing over NDN testbed. > > I copied both of them on this reply, hoping they could help offer more details. > > > > Lixia > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Sun Mar 29 16:23:16 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Sun, 29 Mar 2015 16:23:16 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> Message-ID: <3A413472-999D-4F6F-B6BB-2C8631FB7042@ucla.edu> > > On Mar 29, 2015, at 4:02 PM, Lixia Zhang wrote: > > >> On Mar 29, 2015, at 1:20 PM, Muhammad Hosain Abdollahi Sabet > wrote: >> >> >> I believe you are referring to the following presentation: >> http://www.ietf.org/proceedings/interim/2015/01/13/icnrg/slides/slides-interim-2015-icnrg-1-15.pdf >> >> It says clearly that, if necessary, NDN network performs packet fragmentation on a hop-by-hop basis (definitely not by ?endpoints? ? when a consumer retrieves some specific data, they may come from anywhere) >> -------------------------------------------------------------------------------- >> >> That?s the exact file I referred to. You?re right. It?s mentioned hop-by-hop fragmentation. But after counting its issues, in the conclusion part (last page) it says (I?m quoting): >> ?Host by host fragmentation is the only option for NDN? >> > maybe a typo? > that ought to be/really means ?hop-by-hop fragmentation and reassembly? yes. this is a typo that we didn?t catch before. The conclusion meant to highlight that *hop-by-hop* fragmentation is the only viable option for NDN. ? Alex >> Maybe there is something attached to this file which I haven?t seen it yet. But for the time being I see some differences between p7, 8 and p9 which I don't understand. Do we consider intermediate nodes (e.g. routers) host here? I don?t think so. >> >> Really sorry if I?m disturbing Divyashri?s question. >> >> Thanks, >> Sabet >> >> >> >> -----Original Message----- >> From: Ndn-interest on behalf of Lijing >> Sent: Sun 3/29/2015 11:34 PM >> To: Lixia Zhang >> Cc: Ilya W Moiseenko; Ndn-interest at lists.cs.ucla.edu >> Subject: Re: [Ndn-interest] NDNVideo: Available over NFD? >> >> Hi, Divyashri >> Now we have a very prototype testing over NDN testbed. >> About this project you can find more details here, https://github.com/PhdLoLi/VideoFile >. >> If you have any other question, please don't hesitate to ask me. >> >> Lijing >> >> > On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: >> > >> > >> >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: >> >> >> >> Hi, >> >> >> >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >> >> >> >> 1) Does this work over Ethernet? If yes, is the source code available? >> >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don't work well over CCNx. Is there a plan to port this to NDN? >> > >> > Jeff already mentioned about ndnrtc effort. >> > >> > Another project has re-implemented NDNvideo using a new API. >> > The video is done by Lijing Wang. >> > The new API is Ilya's thesis work. >> > As I heard last Friday, they have been running testing over NDN testbed. >> > I copied both of them on this reply, hoping they could help offer more details. >> > >> > Lixia >> > >> >> >> > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From gts at ics.uci.EDU Sun Mar 29 16:28:02 2015 From: gts at ics.uci.EDU (GTS) Date: Sun, 29 Mar 2015 17:28:02 -0600 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <3A413472-999D-4F6F-B6BB-2C8631FB7042@ucla.edu> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> <3A413472-999D-4F6F-B6BB-2C8631FB7042@ucla.edu> Message-ID: <55188A82.4050508@ics.uci.edu> I disagree with the categorical statement below. Hop-by-hop fragmentation is indeed an option for NDN, but it's *not* the only one. One way to do secure cut-through (end-based and intermediate) (re-)fragmentation is described here: http://arxiv.org/abs/1405.2861 Gene On 3/29/15 5:23 PM, Alex Afanasyev wrote: >> .... >> maybe a typo? >> that ought to be/really means ?hop-by-hop fragmentation and reassembly? > > yes. this is a typo that we didn?t catch before. The conclusion meant > to highlight that *hop-by-hop* fragmentation is the only viable option > for NDN. > > ? > A -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Sun Mar 29 17:24:21 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Sun, 29 Mar 2015 17:24:21 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <55188A82.4050508@ics.uci.edu> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> <3A413472-999D-4F6F-B6BB-2C8631FB7042@ucla.edu> <55188A82.4050508@ics.uci.edu> Message-ID: In my opinion, cut-through forwarding of segments is a possible optimization of hop-by-hop fragmentation which can be applied only for some of the data packets: only those that are not requested with security constraints (e.g., when neither interest name doesn?t contain implicit digest nor interest doesn?t include data packet signature constraint). Also, cut-through optimization is meaningful when router connect networks with similar (same) MTU characteristics. --- Alex > On Mar 29, 2015, at 4:28 PM, GTS wrote: > > I disagree with the categorical statement below. Hop-by-hop > fragmentation is indeed an option for NDN, but it's *not* the only one. > One way to do secure cut-through (end-based and intermediate) > (re-)fragmentation is described here: > http://arxiv.org/abs/1405.2861 > > Gene > > > > On 3/29/15 5:23 PM, Alex Afanasyev wrote: >>> .... >>> maybe a typo? >>> that ought to be/really means ?hop-by-hop fragmentation and reassembly? >> >> yes. this is a typo that we didn?t catch before. The conclusion meant to highlight that *hop-by-hop* fragmentation is the only viable option for NDN. >> >> ? >> A > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From gts at ics.uci.EDU Sun Mar 29 17:35:50 2015 From: gts at ics.uci.EDU (Gene Tsudik) Date: Sun, 29 Mar 2015 17:35:50 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4AC03A6244C3C34BB52A7EC60B799C4C03CC2949@m-pdc.sbu.ac.ir> <3A413472-999D-4F6F-B6BB-2C8631FB7042@ucla.edu> <55188A82.4050508@ics.uci.edu> Message-ID: Alex, If you look closely at the referenced paper, you will see that it *indeed* shows how to do secure cut-through fragmentation and re fragmentation. "Secure" means that both hash and signature verification in routers is supported. Gene On Mar 29, 2015 6:24 PM, "Alex Afanasyev" wrote: > In my opinion, cut-through forwarding of segments is a possible > optimization of hop-by-hop fragmentation which can be applied only for some > of the data packets: only those that are not requested with security > constraints (e.g., when neither interest name doesn?t contain implicit > digest nor interest doesn?t include data packet signature constraint). > Also, cut-through optimization is meaningful when router connect networks > with similar (same) MTU characteristics. > > --- > Alex > > On Mar 29, 2015, at 4:28 PM, GTS wrote: > > I disagree with the categorical statement below. Hop-by-hop > fragmentation is indeed an option for NDN, but it's *not* the only one. > One way to do secure cut-through (end-based and intermediate) > (re-)fragmentation is described here: > http://arxiv.org/abs/1405.2861 > > Gene > > > > On 3/29/15 5:23 PM, Alex Afanasyev wrote: > > .... > maybe a typo? > that ought to be/really means ?hop-by-hop fragmentation and reassembly? > > > yes. this is a typo that we didn?t catch before. The conclusion meant > to highlight that *hop-by-hop* fragmentation is the only viable option for > NDN. > > ? > A > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iliamo at CS.UCLA.EDU Sun Mar 29 19:32:30 2015 From: iliamo at CS.UCLA.EDU (Ilya Moiseenko) Date: Sun, 29 Mar 2015 19:32:30 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> Message-ID: <8BFAA8A5-BAFB-492B-9A20-D4FAD9815643@cs.ucla.edu> Hi Divyashri, The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API Hopefully, this branch will be merged in not so distant future. Ilya On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: >> >> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: >> >> Hi, >> >> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >> >> 1) Does this work over Ethernet? If yes, is the source code available? >> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.UCLA.EDU Sun Mar 29 20:09:07 2015 From: jburke at remap.UCLA.EDU (Burke, Jeff) Date: Mon, 30 Mar 2015 03:09:07 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <8BFAA8A5-BAFB-492B-9A20-D4FAD9815643@cs.ucla.edu> Message-ID: Hi Divyashri, The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). Hm, can you explain more? :) To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API Hopefully, this branch will be merged in not so distant future. Ilya On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: Hi, I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: 1) Does this work over Ethernet? If yes, is the source code available? 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Jeff already mentioned about ndnrtc effort. Another project has re-implemented NDNvideo using a new API. The video is done by Lijing Wang. The new API is Ilya's thesis work. As I heard last Friday, they have been running testing over NDN testbed. I copied both of them on this reply, hoping they could help offer more details. Lixia _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From iliamo at CS.UCLA.EDU Sun Mar 29 20:39:50 2015 From: iliamo at CS.UCLA.EDU (Ilya Moiseenko) Date: Sun, 29 Mar 2015 20:39:50 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: On Mar 29, 2015, at 8:09 PM, Burke, Jeff wrote: >> >> Hi Divyashri, >> The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). > > > Hm, can you explain more? :) Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). > >> >> To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API >> Hopefully, this branch will be merged in not so distant future. >> >> Ilya >> >> On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: >> >>>> >>>> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: >>>> >>>> Hi, >>>> >>>> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >>>> >>>> 1) Does this work over Ethernet? If yes, is the source code available? >>>> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? >>> >>> Jeff already mentioned about ndnrtc effort. >>> >>> Another project has re-implemented NDNvideo using a new API. >>> The video is done by Lijing Wang. >>> The new API is Ilya's thesis work. >>> As I heard last Friday, they have been running testing over NDN testbed. >>> I copied both of them on this reply, hoping they could help offer more details. >>> >>> Lixia >> >> _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.UCLA.EDU Sun Mar 29 20:46:23 2015 From: jburke at remap.UCLA.EDU (Burke, Jeff) Date: Mon, 30 Mar 2015 03:46:23 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: Message-ID: On Mar 29, 2015, at 8:09 PM, Burke, Jeff > wrote: Hi Divyashri, The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). Hm, can you explain more? :) Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). Not sure that is not the "true NDN way" or not. What Derek did was partially a consequence of supporting the gstreamer pipeline, which had other advantages, not necessarily a holdover from IP. What a/v framework are you using for capture/playback? I couldn't tell from a quick look at the code. Another reason there was a separate timecode namespace was to allow random seek in unpredictable frame rates and using an application/user understandable expression of time. Does the new code support timecode (not frame #) as well as drop-frame / variable frame rate? These things get a little tricky. Would be interested to know how you are handling it. If there's a namespace doc, I could just look at that... Thanks! Jeff To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API Hopefully, this branch will be merged in not so distant future. Ilya On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: Hi, I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: 1) Does this work over Ethernet? If yes, is the source code available? 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Jeff already mentioned about ndnrtc effort. Another project has re-implemented NDNvideo using a new API. The video is done by Lijing Wang. The new API is Ilya's thesis work. As I heard last Friday, they have been running testing over NDN testbed. I copied both of them on this reply, hoping they could help offer more details. Lixia _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From iliamo at CS.UCLA.EDU Sun Mar 29 20:59:07 2015 From: iliamo at CS.UCLA.EDU (Ilya Moiseenko) Date: Sun, 29 Mar 2015 20:59:07 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: On Mar 29, 2015, at 8:46 PM, Burke, Jeff wrote: > > >> >> On Mar 29, 2015, at 8:09 PM, Burke, Jeff wrote: >> >>>> >>>> Hi Divyashri, >>>> The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). >>> >>> >>> Hm, can you explain more? :) >> >> Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. >> >> Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). > > > Not sure that is not the "true NDN way" or not. What Derek did was partially a consequence of supporting the gstreamer pipeline, which had other advantages, not necessarily a holdover from IP. What a/v framework are you using for capture/playback? I couldn't tell from a quick look at the code. We use Gstreamer 1.4. Lijing found some way to work with its pipelines using frames. > > Another reason there was a separate timecode namespace was to allow random seek in unpredictable frame rates and using an application/user understandable expression of time. Does the new code support timecode (not frame #) as well as drop-frame / variable frame rate? These things get a little tricky. Would be interested to know how you are handling it. If there's a namespace doc, I could just look at that? We use constant frame-rate encoding, so it?s easy to figure out to which frame to jump (or drop). Lijing is making a tech report these days. > > Thanks! > Jeff > > >> >>> >>> >>> To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API >>> Hopefully, this branch will be merged in not so distant future. >>> >>> Ilya >>> >>> On Mar 29, 2015, at 10:59 AM, Lixia Zhang wrote: >>> >>>>> >>>>> On Mar 28, 2015, at 10:43 PM, Divyashri Bhat wrote: >>>>> >>>>> Hi, >>>>> >>>>> I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: >>>>> >>>>> 1) Does this work over Ethernet? If yes, is the source code available? >>>>> 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? >>>> >>>> Jeff already mentioned about ndnrtc effort. >>>> >>>> Another project has re-implemented NDNvideo using a new API. >>>> The video is done by Lijing Wang. >>>> The new API is Ilya's thesis work. >>>> As I heard last Friday, they have been running testing over NDN testbed. >>>> I copied both of them on this reply, hoping they could help offer more details. >>>> >>>> Lixia >>> >>> _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.edu Sun Mar 29 22:42:14 2015 From: dbhat at umass.edu (Divyashri Bhat) Date: Mon, 30 Mar 2015 05:42:14 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: References: Message-ID: <6900942C-DEB4-448D-9484-C07D06F8172B@umass.edu> Hi, What is the version of boost required for compiling Consumer-Producer API [4]? I am using Ubuntu 12.04 and get the following error on build: ~/Consumer-Producer-API$ ./waf Waf: Entering directory `/users/dbhat/Consumer-Producer-API/build' [ 4/127] Compiling src/contexts/consumer-context.cpp In file included from ../src/contexts/consumer-context.cpp:9:0: ../src/contexts/consumer-context.hpp:28:36: fatal error: boost/lockfree/queue.hpp: No such file or directory compilation terminated. Waf: Leaving directory `/users/dbhat/Consumer-Producer-API/build' Build failed -> task in 'ndn-cxx' failed (exit status 1): {task 22345552: cxx consumer-context.cpp -> consumer-context.cpp.2.o} ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++0x', '-fPIC', '-include', '/users/dbhat/Consumer-Producer-API/build/ndn-cxx.2', '-I/users/dbhat/Consumer-Producer-API/build', '-I/users/dbhat/Consumer-Producer-API', '-I/users/dbhat/Consumer-Producer-API/build/src', '-I/users/dbhat/Consumer-Producer-API/src', '-I/usr/include', '-D_GLIBCXX_USE_NANOSLEEP', '-DNDEBUG', '../src/contexts/consumer-context.cpp', '-c', '-o', '/users/dbhat/Consumer-Producer-API/build/src/contexts/consumer-context.cpp.2.o'] [4] https://github.com/iliamo/Consumer-Producer-API Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 29 Mar 2015, at 23:59, Ilya Moiseenko > wrote: On Mar 29, 2015, at 8:46 PM, Burke, Jeff > wrote: On Mar 29, 2015, at 8:09 PM, Burke, Jeff > wrote: Hi Divyashri, The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). Hm, can you explain more? :) Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). Not sure that is not the "true NDN way" or not. What Derek did was partially a consequence of supporting the gstreamer pipeline, which had other advantages, not necessarily a holdover from IP. What a/v framework are you using for capture/playback? I couldn't tell from a quick look at the code. We use Gstreamer 1.4. Lijing found some way to work with its pipelines using frames. Another reason there was a separate timecode namespace was to allow random seek in unpredictable frame rates and using an application/user understandable expression of time. Does the new code support timecode (not frame #) as well as drop-frame / variable frame rate? These things get a little tricky. Would be interested to know how you are handling it. If there's a namespace doc, I could just look at that? We use constant frame-rate encoding, so it?s easy to figure out to which frame to jump (or drop). Lijing is making a tech report these days. Thanks! Jeff To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API Hopefully, this branch will be merged in not so distant future. Ilya On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: Hi, I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: 1) Does this work over Ethernet? If yes, is the source code available? 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Jeff already mentioned about ndnrtc effort. Another project has re-implemented NDNvideo using a new API. The video is done by Lijing Wang. The new API is Ilya's thesis work. As I heard last Friday, they have been running testing over NDN testbed. I copied both of them on this reply, hoping they could help offer more details. Lixia _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From iliamo at CS.UCLA.EDU Sun Mar 29 22:45:20 2015 From: iliamo at CS.UCLA.EDU (Ilya Moiseenko) Date: Sun, 29 Mar 2015 22:45:20 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <6900942C-DEB4-448D-9484-C07D06F8172B@umass.edu> References: <6900942C-DEB4-448D-9484-C07D06F8172B@umass.edu> Message-ID: Should compile with 1.57 On Mar 29, 2015, at 10:42 PM, Divyashri Bhat wrote: > Hi, > > What is the version of boost required for compiling Consumer-Producer API [4]? I am using Ubuntu 12.04 and get the following error on build: > > ~/Consumer-Producer-API$ ./waf > Waf: Entering directory `/users/dbhat/Consumer-Producer-API/build' > [ 4/127] Compiling src/contexts/consumer-context.cpp > In file included from ../src/contexts/consumer-context.cpp:9:0: > ../src/contexts/consumer-context.hpp:28:36: fatal error: boost/lockfree/queue.hpp: No such file or directory > compilation terminated. > Waf: Leaving directory `/users/dbhat/Consumer-Producer-API/build' > Build failed > -> task in 'ndn-cxx' failed (exit status 1): > {task 22345552: cxx consumer-context.cpp -> consumer-context.cpp.2.o} > ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++0x', '-fPIC', '-include', '/users/dbhat/Consumer-Producer-API/build/ndn-cxx.2', '-I/users/dbhat/Consumer-Producer-API/build', '-I/users/dbhat/Consumer-Producer-API', '-I/users/dbhat/Consumer-Producer-API/build/src', '-I/users/dbhat/Consumer-Producer-API/src', '-I/usr/include', '-D_GLIBCXX_USE_NANOSLEEP', '-DNDEBUG', '../src/contexts/consumer-context.cpp', '-c', '-o', '/users/dbhat/Consumer-Producer-API/build/src/contexts/consumer-context.cpp.2.o'] > > > [4] https://github.com/iliamo/Consumer-Producer-API > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > On 29 Mar 2015, at 23:59, Ilya Moiseenko > wrote: > > > On Mar 29, 2015, at 8:46 PM, Burke, Jeff > wrote: > > > > > On Mar 29, 2015, at 8:09 PM, Burke, Jeff > wrote: > > > Hi Divyashri, > The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). > > Hm, can you explain more? :) > > Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. > > Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). > > Not sure that is not the "true NDN way" or not. What Derek did was partially a consequence of supporting the gstreamer pipeline, which had other advantages, not necessarily a holdover from IP. What a/v framework are you using for capture/playback? I couldn't tell from a quick look at the code. > We use Gstreamer 1.4. Lijing found some way to work with its pipelines using frames. > > > Another reason there was a separate timecode namespace was to allow random seek in unpredictable frame rates and using an application/user understandable expression of time. Does the new code support timecode (not frame #) as well as drop-frame / variable frame rate? These things get a little tricky. Would be interested to know how you are handling it. If there's a namespace doc, I could just look at that? > > We use constant frame-rate encoding, so it?s easy to figure out to which frame to jump (or drop). > Lijing is making a tech report these days. > > > Thanks! > Jeff > > > > > > To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API > Hopefully, this branch will be merged in not so distant future. > > Ilya > > On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: > > > On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: > > Hi, > > I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: > > 1) Does this work over Ethernet? If yes, is the source code available? > 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia > > _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From ooofreedom at gmail.com Sun Mar 29 22:51:27 2015 From: ooofreedom at gmail.com (Lijing) Date: Sun, 29 Mar 2015 22:51:27 -0700 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <6900942C-DEB4-448D-9484-C07D06F8172B@umass.edu> References: <6900942C-DEB4-448D-9484-C07D06F8172B@umass.edu> Message-ID: First, for the NDNVideo project, I developed it on Mac OS, and the Gstreamer is very platform-sensitive. I also have tried Ubuntu 12.04. The playing back won?t work on Linux(because of Gstreamer). But if you want to try the Consumer/Producer API, for Ubuntu 12.04, you can use boost 1.53.0. It works for me. Lijing Address: FIT 4-305, Tsinghua University,Beijing,China > On Mar 29, 2015, at 10:42 PM, Divyashri Bhat wrote: > > Hi, > > What is the version of boost required for compiling Consumer-Producer API [4]? I am using Ubuntu 12.04 and get the following error on build: > > ~/Consumer-Producer-API$ ./waf > Waf: Entering directory `/users/dbhat/Consumer-Producer-API/build' > [ 4/127] Compiling src/contexts/consumer-context.cpp > In file included from ../src/contexts/consumer-context.cpp:9:0: > ../src/contexts/consumer-context.hpp:28:36: fatal error: boost/lockfree/queue.hpp: No such file or directory > compilation terminated. > Waf: Leaving directory `/users/dbhat/Consumer-Producer-API/build' > Build failed > -> task in 'ndn-cxx' failed (exit status 1): > {task 22345552: cxx consumer-context.cpp -> consumer-context.cpp.2.o} > ['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++0x', '-fPIC', '-include', '/users/dbhat/Consumer-Producer-API/build/ndn-cxx.2', '-I/users/dbhat/Consumer-Producer-API/build', '-I/users/dbhat/Consumer-Producer-API', '-I/users/dbhat/Consumer-Producer-API/build/src', '-I/users/dbhat/Consumer-Producer-API/src', '-I/usr/include', '-D_GLIBCXX_USE_NANOSLEEP', '-DNDEBUG', '../src/contexts/consumer-context.cpp', '-c', '-o', '/users/dbhat/Consumer-Producer-API/build/src/contexts/consumer-context.cpp.2.o'] > > > [4] https://github.com/iliamo/Consumer-Producer-API > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > On 29 Mar 2015, at 23:59, Ilya Moiseenko > wrote: > > > On Mar 29, 2015, at 8:46 PM, Burke, Jeff > wrote: > > > > > On Mar 29, 2015, at 8:09 PM, Burke, Jeff > wrote: > > > Hi Divyashri, > The link to the repo that Lijing has provided is essentially a working directory now. Eventually, all code will be split into two projects: 1) video hosting like Youtube and 2) live video broadcasting like ustream.tv. The previous NDN-video supported both of these functions, but the namespace design was not implemented correctly (in true NDN way). > > Hm, can you explain more? :) > > Derek didn?t split video and audio streams into frames, and had segmentation over the whole video track and the whole audio track, which is essentially the same as it would be implemented in TCP/IP. Because of that, he had to keep another namespace that matches playback time to segment number. > > Lijing?s project produces and consumes video and audio frame-by-frame (in parallel). > > Not sure that is not the "true NDN way" or not. What Derek did was partially a consequence of supporting the gstreamer pipeline, which had other advantages, not necessarily a holdover from IP. What a/v framework are you using for capture/playback? I couldn't tell from a quick look at the code. > We use Gstreamer 1.4. Lijing found some way to work with its pipelines using frames. > > > Another reason there was a separate timecode namespace was to allow random seek in unpredictable frame rates and using an application/user understandable expression of time. Does the new code support timecode (not frame #) as well as drop-frame / variable frame rate? These things get a little tricky. Would be interested to know how you are handling it. If there's a namespace doc, I could just look at that? > > We use constant frame-rate encoding, so it?s easy to figure out to which frame to jump (or drop). > Lijing is making a tech report these days. > > > Thanks! > Jeff > > > > > > To build Lijing?s project you need a custom branch of ndn-cxx library here https://github.com/iliamo/Consumer-Producer-API > Hopefully, this branch will be merged in not so distant future. > > Ilya > > On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: > > > On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: > > Hi, > > I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: > > 1) Does this work over Ethernet? If yes, is the source code available? > 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more details. > > Lixia > > _______________________________________________ Ndn-interest mailing list Ndn-interest at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dbhat at umass.EDU Mon Mar 30 23:08:47 2015 From: dbhat at umass.EDU (Divyashri Bhat) Date: Tue, 31 Mar 2015 06:08:47 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> Message-ID: <4E367BD7-2330-47EE-821E-BCE73777F0BF@umass.edu> Hi Lijing, I am using a Ubuntu 12.04 VM with NFD and ndn-cxx installed. When I install repo-ng, I get the following error: ndnvid:~/repo-ng$ ./waf Waf: Entering directory `/users/dbhat/repo-ng/build' [ 1/22] Compiling src/handles/base-handle.cpp [ 2/22] Compiling src/handles/delete-handle.cpp [ 3/22] Compiling src/handles/read-handle.cpp [ 4/22] Compiling src/handles/tcp-bulk-insert-handle.cpp ../src/handles/tcp-bulk-insert-handle.cpp: In member function ?void repo::detail::TcpBulkInsertClient::handleReceive(const boost::system::error_code&, std::size_t, const std::shared_ptr&)?: ../src/handles/tcp-bulk-insert-handle.cpp:166:99: error: no matching function for call to ?ndn::Block::fromBuffer(uint8_t*, std::size_t)? ../src/handles/tcp-bulk-insert-handle.cpp:166:99: note: candidates are: /usr/local/include/ndn-cxx/encoding/block.hpp:160:3: note: static bool ndn::Block::fromBuffer(const ConstBufferPtr&, size_t, ndn::Block&) /usr/local/include/ndn-cxx/encoding/block.hpp:160:3: note: candidate expects 3 arguments, 2 provided /usr/local/include/ndn-cxx/encoding/block.hpp:170:3: note: static bool ndn::Block::fromBuffer(const uint8_t*, size_t, ndn::Block&) /usr/local/include/ndn-cxx/encoding/block.hpp:170:3: note: candidate expects 3 arguments, 2 provided Waf: Leaving directory `/users/dbhat/repo-ng/build' Build failed -> task in 'ndn-repo-objects' failed (exit status 1): {task 38332368: cxx tcp-bulk-insert-handle.cpp -> tcp-bulk-insert-handle.cpp.1.o} ['/usr/bin/g++', '-std=c++0x', '-pedantic', '-Wall', '-O2', '-g', '-fPIC', '-I/users/dbhat/repo-ng/build/src', '-I/users/dbhat/repo-ng/src', '-I/usr/local/include', '-I/usr/include', '-DHAVE_NDN_CXX=1', '-DHAVE_SQLITE3=1', '../src/handles/tcp-bulk-insert-handle.cpp', '-c', '-o', '/users/dbhat/repo-ng/build/src/handles/tcp-bulk-insert-handle.cpp.1.o?] Did I miss something in the installation? Could you help out here please? Thank you. Regards, Divyashri Bhat dbhat at umass.edu Graduate Student Department of Electrical and Computer Engineering, University of Massachusetts, Amherst On 29 Mar 2015, at 15:04, Lijing > wrote: Hi, Divyashri Now we have a very prototype testing over NDN testbed. About this project you can find more details here, https://github.com/PhdLoLi/VideoFile. If you have any other question, please don?t hesitate to ask me. Lijing On Mar 29, 2015, at 10:59 AM, Lixia Zhang > wrote: On Mar 28, 2015, at 10:43 PM, Divyashri Bhat > wrote: Hi, I came across a technical report a few years ago that describes a working implementation of Video Streaming over Information Centric Networks using CCNx [1]. This report also mentions video streaming over Ethernet. I have two questions: 1) Does this work over Ethernet? If yes, is the source code available? 2) The implementation at the Github link [2] appears to be over CCNx and as far as I understand Ethernet faces don?t work well over CCNx. Is there a plan to port this to NDN? Jeff already mentioned about ndnrtc effort. Another project has re-implemented NDNvideo using a new API. The video is done by Lijing Wang. The new API is Ilya's thesis work. As I heard last Friday, they have been running testing over NDN testbed. I copied both of them on this reply, hoping they could help offer more details. Lixia From ooofreedom at gmail.com Mon Mar 30 23:36:00 2015 From: ooofreedom at gmail.com (Lijing Wang) Date: Tue, 31 Mar 2015 06:36:00 +0000 Subject: [Ndn-interest] NDNVideo: Available over NFD? In-Reply-To: <4E367BD7-2330-47EE-821E-BCE73777F0BF@umass.edu> References: <99CBDE60-A12F-4D31-90DF-D2482655C801@cs.ucla.edu> <2431644D-025B-4A5A-808A-7CAB995D1A42@gmail.com> <4E367BD7-2330-47EE-821E-BCE73777F0BF@umass.edu> Message-ID: Could you tell me how you install NFD and ndn-cxx? I install NFD by apt-get. I just use consumer and producer API instead of ndn-cxx. When I compiled repo, I didn't meet this error. Maybe because of the version of ndn-cxx? You can just use consumer/producer API, compile and install it to overwrite the previous ndn-cxx. Then try to compile repo. Hope this can help. Lijing On Mon, Mar 30, 2015 at 11:08 PM Divyashri Bhat wrote: > Hi Lijing, > > I am using a Ubuntu 12.04 VM with NFD and ndn-cxx installed. When I > install repo-ng, I get the following error: > > > ndnvid:~/repo-ng$ ./waf > Waf: Entering directory `/users/dbhat/repo-ng/build' > [ 1/22] Compiling src/handles/base-handle.cpp > [ 2/22] Compiling src/handles/delete-handle.cpp > [ 3/22] Compiling src/handles/read-handle.cpp > [ 4/22] Compiling src/handles/tcp-bulk-insert-handle.cpp > ../src/handles/tcp-bulk-insert-handle.cpp: In member function ?void > repo::detail::TcpBulkInsertClient::handleReceive(const > boost::system::error_code&, std::size_t, const > std::shared_ptr&)?: > ../src/handles/tcp-bulk-insert-handle.cpp:166:99: error: no matching > function for call to ?ndn::Block::fromBuffer(uint8_t*, std::size_t)? > ../src/handles/tcp-bulk-insert-handle.cpp:166:99: note: candidates are: > /usr/local/include/ndn-cxx/encoding/block.hpp:160:3: note: static bool > ndn::Block::fromBuffer(const ConstBufferPtr&, size_t, ndn::Block&) > /usr/local/include/ndn-cxx/encoding/block.hpp:160:3: note: candidate > expects 3 arguments, 2 provided > /usr/local/include/ndn-cxx/encoding/block.hpp:170:3: note: static bool > ndn::Block::fromBuffer(const uint8_t*, size_t, ndn::Block&) > /usr/local/include/ndn-cxx/encoding/block.hpp:170:3: note: candidate > expects 3 arguments, 2 provided > Waf: Leaving directory `/users/dbhat/repo-ng/build' > Build failed > -> task in 'ndn-repo-objects' failed (exit status 1): > {task 38332368: cxx tcp-bulk-insert-handle.cpp -> > tcp-bulk-insert-handle.cpp.1.o} > ['/usr/bin/g++', '-std=c++0x', '-pedantic', '-Wall', '-O2', '-g', '-fPIC', > '-I/users/dbhat/repo-ng/build/src', '-I/users/dbhat/repo-ng/src', > '-I/usr/local/include', '-I/usr/include', '-DHAVE_NDN_CXX=1', > '-DHAVE_SQLITE3=1', '../src/handles/tcp-bulk-insert-handle.cpp', '-c', > '-o', '/users/dbhat/repo-ng/build/src/handles/tcp-bulk-insert- > handle.cpp.1.o?] > > Did I miss something in the installation? > > Could you help out here please? > > Thank you. > Regards, > Divyashri Bhat > dbhat at umass.edu > Graduate Student > Department of Electrical and Computer Engineering, > University of Massachusetts, Amherst > > On 29 Mar 2015, at 15:04, Lijing oofreedom at gmail.com>> wrote: > > Hi, Divyashri > Now we have a very prototype testing over NDN testbed. > About this project you can find more details here, > https://github.com/PhdLoLi/VideoFile. > If you have any other question, please don?t hesitate to ask me. > > Lijing > > On Mar 29, 2015, at 10:59 AM, Lixia Zhang a at cs.ucla.edu>> wrote: > > > On Mar 28, 2015, at 10:43 PM, Divyashri Bhat dbhat at umass.edu>> wrote: > > Hi, > > I came across a technical report a few years ago that describes a working > implementation of Video Streaming over Information Centric Networks using > CCNx [1]. This report also mentions video streaming over Ethernet. I have > two questions: > > 1) Does this work over Ethernet? If yes, is the source code available? > 2) The implementation at the Github link [2] appears to be over CCNx and > as far as I understand Ethernet faces don?t work well over CCNx. Is there a > plan to port this to NDN? > > Jeff already mentioned about ndnrtc effort. > > Another project has re-implemented NDNvideo using a new API. > The video is done by Lijing Wang. > The new API is Ilya's thesis work. > As I heard last Friday, they have been running testing over NDN testbed. > I copied both of them on this reply, hoping they could help offer more > details. > > Lixia > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: